Ubuntu Servers :: Stuck At Boot With Raid (non Boot) In Fstab = Useless?
Nov 1, 2010
Forgive the terseness. I'm frazzled with this issue, perhaps I should have asked earlier. Every weekend for the past 2 months has been an endless cycle of 'repair broken system' off the install disk.
Installed from Ubuntu server 10.04LTS x86_64, + xfce-desktop Here is uname -a Linux ournas 2.6.32-25-server #45-Ubuntu SMP Sat Oct 16 20:06:58 UTC 2010 x86_64 GNU/Linux If I add my raid + lvm to the fstab file, the boot stalls, (no error it, just hangs waiting, forever). So that's a not very user friendly to start with.
I've tried the suggestions about UUID in fstab tried using LABEL instead, or even /dev/xxx. Every time it hangs. I've googled this endlessly and not found a solution. So don't ask why... since I seem to have tried every odd suggestion to fix this, I've lost track. There seems to be some consensus that whoever gave us plymouth laid an egg. Forgive me if I'm wrong, but did we need a better graphical boot if it breaks everything else?
I recently formatted my HDD and installed Ubuntu Server 10.04 x64. This is actually the 4th install in the past week because I was testing some things. But I had this problem on at least the previous install which made me want to start fresh again. The problem I'm having is Ubuntu will not boot if I add any of my drives to fstab. If I leave it with the standard proc, /, and swap lines it works fine. As soon as I add a line for one of my RAID arrays or an NTFS formatted partition the system hangs on bootup. It doesn't matter if I have the extra drives operating or not.
The last thing I see before it hangs is: Code: /dev/sda1: clean, 69351/4358144 files, 583945/17401600 blocks Here is what the fstab currently looks like:
The other two lines which also made it hang included one which was almost exactly the same as the /dev/md0 line except it was md1 with a different mount point and another which used a UUID and was ntfs-3g. I know they work because all 3 of them were mounted by "mount -a" after putting them into fstab and they're pretty much the same as what I was using with 9.04 server.
I have the following two lines at the bottom of my /etc/fstab
Quote: //172.16.6.15/e /tmp/e cifs _netdev,iocharset=utf8,credentials=/root/.smbcredentials,gid=0 0 0 //172.16.6.15/e/Public /var/www/index/pub cifs _netdev,iocharset=utf8,credentials=/root/.smbcredentials,gid=0 0 0 My server address is 172.16.6.1.
If the destination (which is my workstation desktop) 172.16.6.15 is offline when the server tries to boot, the entire boot procedure halts with the following message: Unable to find suitable address. mountall: mount <destination> terminated with status 2 The problem is that my server runs headlessly, and every time something silly like this happens where you'd normally expect the OS to continue regardless, I'm forced to plug a monitor in and diagnose on console
So my question: Is there any way to make it proceed with the boot normally despite the host being unreachable? I could probably chuck a mount command into crontab or /etc/rc.local or a /etc/network/if-up.d script, but isn't this the way it really should be done (/etc/fstab)? If so, then we shouldn't expect the entire boot to halt just because a network share can't be mounted, right? While on the topic of a headless ubuntu server 10.10 not booting without some kind of intervention, I have yet another issue: If the server goes down without proper shutdown (power failure, for example) the grub menu displays the kernel choices and there's no countdown timer. Instead, I have to manually press enter to continue the boot. Is there any way around this? Clearly this should not be the case for a server distribution
all is well on my headless Lucid server until a recent apt-get upgrade && shutdown -R now ... it did not come back up? after i moved a screen to the other side of the house, i found fcsk waiting for input during the boot process errors on / ... (I)gnore / (F)ix " ...so i had to attach a keyboard just to push <F> i could change /etc/fstab so it never runs fsck, but this doesn't seem wise. how can i make it <F>ix automatically ? ( or maybe after Xsec )
I have tried different methods to auto start wpa_supplicant at boot on Ubuntu Lucid server on a laptop which can't be connected to Ethernet.
The only thing that worked is adding the wpa_supplicant command before exit0 in rc.local. It solve my problem of wpa_supplicant auto start and annoyance on not be able to ssh before local login. But the screen stuck at Ubuntu Logo. How can i get pass Ubuntu logo screen to regular tty or xbmc in future?
I was having this issue with my server when I tried upgrading (fresh install) to 10.04 from 9.04. But to test it out after going back to 9.04 I installed 10.04 server in a virtual machine and found the same issues. I was using the AMD64 version for everything. In the virtual machine I chose openssh and samba server in the initial configuration. After the install I ran a dist-upgrade and installed mdadm. I then created an fd partition on 3 virtual disks and created a RAID5 array using the following command:
This is the same command I ran on my physical RAID5 quite a while ago which has been working fine ever since. After running a --detail --scan >> mdadm.conf (and changing the metadata from 00.90 to 0.90) I rebooted and found that the array was running with only one drive which was marked as a spare. On the physical server I kept having this issue with one drive which would always be left out when I assembled the array and would work fine after resyncing until I rebooted. After I rebooted the array would show the remaining 6 drives (of 7) as spares.
I updated mdadm to 3.1.1 using a deb from debian experimental and the RAID was working fine afterward. But then the boot problems started again. As soon as I added /dev/md0 to the fstab the system would hang on boot displaying the following before hanging:
I have Ubuntu 10.10 (maverick) and I'm using mdadm 3.1.4. I have created a RAID 10 using imsm as the metadata, and this runs successfully if I assemble the RAID from the command line. My question is: How do I get the RAID to auto assemble when I boot the system? I would like to be able to mount the RAID when the system starts up (but the OS is on a separate disk altogether). What I've found out so far is that I must do a Code: update-initramfs -k all -u AFTER I've modified the /etc/mdadm/mdadm.conf file. This is what I've got in my configuration file:
[Code]....
BUT what happens is that when I reboot my server, and then do "ls -l /dev/md*" there is no listing at all for any RAID devices. I actually have to run the assemble command on command line and that is when I see listings for RAID devices under /dev. What am I missing?
I have been working in my spare time over the last few days, Had problems with the whole grub2 not installing on RAID 1. Then I found out that I had to have a separate non raid Ext4 partition on one drive with "/Boot" as mount point and install went though fine.
My question is, will the developers FIX this. I mean if I only have 2 x 2tb drives in teh pc as RAID 1, and the one fails with the boot partition the whole machine goes down. Kinda defeats the whole RAID feature huh.
I USED to run a windows network with RAID 5 servers, and windows never had a problem installing everything on the RAID. Or even setting up RAID 1 in the bios on the PC and installing XP or NT4 on the RAID 1. There was never a need for a separate non raid boot partition.
Do we need a separate RAID friendly/enabled Grub? I guess for now I will get a 250gb drive and install the Server OS to it, and setup RAID1 manually after the server OS boots. Then will make a ghost type image of the server in case that drive fails so I can quickly install a new drive and restore the image and get it back up and running again.
Ran 'do-release-upgrade -d'on my server running Hardy.No problems during the upgrade.Rebooted after the upgrade completed, and I was presented with the new plymouth screen. This sucks for servers.It sat there displaying the logo for ~5 minutes.Hit CTRL+ALT+F1 through F8 and didn't see anything on the virtual consoles.Finally figured out that I had to hit ESC on the plymouth screen to actually see what was going on.It said /dev/sdi1 had problems along with /dev/md0.It sat there forever with no fsck status and no HDD lights blinking.
SysRq+REISUB and tweaked the boot parameter to remove 'quiet splash' and appended 'S' for single-user mode.Got the attached screenshot.The box has been sitting like this for ~15 minutes.Not entirely sure what to report a bug against at the moment. Plus the somewhat-new requirement of running 'ubuntu-bug' is pretty retarded in this situation. (Yeah, I know I can add some string to the URL to get around it.Why is it such a pain in the *** to report a bug?)I'm going to do some more digging to try and find out what is dying during boot.The new boot process is a bit of a mystery to me still, so if anyone has pointers or any devs want more detailed information,
i installed ubuntu server on a 4-hard disk system, i installed with the RAID 10 support that comes with 10.04 server optioon. my raid swap is /dev/md0 and my raid data partition is /dev/md1
hard drives are /dev/sda /dev/sdb /dev/sdc /dev/sdd
the instalation goes fine, from the 8TB im getting 4TB mirrored which is what i want, but the instalation setup goes up to the point where it asks me to install grub boot loader, There i choose the default option and it does a fatal error.
my main goal is just to make it bootable, any method is welcome. this went beyond my RAID knowledge (more conceptual than technical)
I've got a couple of new hard disks that I have partitioned (3 partitions per disk) and set up in a mirrored software raid array using mdadm. They've synced, I've put file systems on them (1 x ext4, 2 x luks + ext4) and I can mount them. I've checked the partitions using fdisk. I've checked the filesystems using fsck. So far so good. Next step is that I'd like mdadm to automatically assemble them on boot. (Not bothered about mounting and crypttabing yet.)
I've used sudo /usr/share/mdadm/mkconf to generate a new mdadm.conf with the appropriate UUIDs for the new partitions. I've checked that this matches the output of sudo mdadm --detail --scan
I have an SiI hardware SATA RAID card, with two 500GB disks in mirrored RAID configuration. When I first plugged them in and set it up, things seemed to work ok, but on boot the raid controller told me that the RAID needed rebuilding, and it would happen automatically after POST. So I didn't worry about it, and the drive mounted fine, and it's been that way for years. I just went in and manually on-line rebuilt the RAID in the controller's BIOS, and now when I boot into Ubuntu, both disks show up in fdisk, but neither show up in /dev/disk/by-uuid. Am I missing something?
I have installed Ubuntu on my m1530 since 8.04 and currently dual boot Win7 and 10.10. I would like to dual boot on my PC, but I have run into a problem. I am not a pro at Ubuntu, but this problem I can not solve by reading forums like I have in the past.
I realize this is a common problem, but I have noticed people having success.
I have a M4A87TD EVO MB with two Seagate drives in Raid 0. (The raid controller is a SB850 on that MB) I use the raid utility to create the raid drive that Windows7x64 uses. I have 2 partitions and 1 unused space. Partition 1 is Windows, partition 2 is for media, and the remaining unused space is for Ubuntu.
I am running ubuntu-10.10-desktop-amd64 off a Cruzer 16GB flash drive that was installed via Universal-USB-Installer-1.8.1.4.
My problem like so many others is that when I load into Ubuntu, gparted detects two separate hard drives instead of the raid. I read that this is because kpartx is not installed on 10.10. I then went in LiveCD mode and downloaded kpartx from Synaptic Manager. Gparted still reported two drives. I opened terminal and run a few commands with kpartx. I received an error. (Forgive me I didn't write it down, but I believe it said something about a communication error. I will try again later and see.)
Currently I am reflashing the Cruzer with a persistence of 4GB. I am not familiar with this process, but I understand that my LiveCD boot will save information I download to it. I decided to try this method because I was going to install kpartx and reboot to see if this made a difference.
I am looking for any suggestions on a different method or perhaps someone to tell me that the raid controller or some hardware isn't supported. I did install ubuntu-10.10-alternate-amd64 on my flash drive, but fail to get past detecting my CD-ROM drive since it's not plugged in. If this method is viable, I will plug it in. I also watched the ..... video were a guy creates Raid 0 with the alternated CD, but it wasn't a dual boot and didn't use a raid controller from a MB.
I have an external hdd that I have added to the fstab so it will mount when I boot. But every time I add the line to fstab and reboot, it hangs during the boot process and says something about ureadahead-other status 4. here is my line in fstab..
/dev/sdc1 /NAS ext3 defaults 0 0
Is there anything wrong with that? I couldn't remember what fs I chose when I formatted it so I did "sudo parted /dev/sdc print" and it said it was ext3.
I made a mistake in my fstab. I know what the problem is and how the fstab needs to be changed. However, since the system will not boot I'm having diffeculty getting in to edit it.The system is running Ubuntu 10.4 64 Bit with LVM2.I have both 10.4 64Bit Server and 10.4 32Bit Desktop cds currently and could burn others if needed. With 32Bit Desktop I'm able to get to a live cd prompt but my hard disks are not mounted.if I try mounting /dev/sda5 to a dummy directory I created it tells me it doesn't know the type of 'LVM2_member'.
I was able to successfully create a small, fixed-size "ram disk" just for kicks, via:
Code: sudo mkfs -t ext3 -q /dev/ram1 65536 sudo mkdir -p /media/ramdisk sudo mount /dev/ram1 /media/ramdisk -o defaults,rw However, I wanted it to auto-boot, so I added the line to fstab:
Code: /dev/ram1 /media/ramdisk ext3 defaults 0 0
This, however, rendered Ubuntu unbootable and I had to repair the fstab by removing the line via a Live CD. I had enough patience to boot through the CD an extra time to see if just deleting "ext3" would work, but it did not. What would cause this to make the system unbootable and how I could make it work?
[URL] and instead of a fat32 I added a ntfs 2 tb hd to my computer. But it doesnt like it, so now when I boot I get
init: ureadahead-other main process (1234) terminated with status 4
I searched and people are mentioning logging into the terminal and what not, but I cant get to a terminal so that kind of silly. People also talking about updating their video cards for this issue, which also is not my problem.
No Boot started w/auto check of drives and it failed on my Virtual C: drive. I know,... but I edited /etc/fstab and now I have nothing available to get a command line. I have grub2 and don't know how or can't get to a boot menu either. Is this a reinstall?
I really need some help here, this is driving me mad. I edited my fstab file to boot a partition on start up, only instead of typing sda7 I typed sda1 by mistake and now can't boot. The problem that is driving me mad is I cannot save changes to fstab from a live cd because I do not have root permissions. I am relatively new to Linux and have no idea how to use the fedora install disk or the commands to use or if it will let me save changes to the file. I cannot believe something so easy to fix does not appear to be possible because i can't save changes to the fstab on my fedora install.
On reboot, the system complains there is some problem (I can't advise what the problem is, because the display scrolls up too fast to read!), and I'm left with a root command prompt.
Its a /etc/fstab problem, presumably. I've used vi to edit /etc/fstab to remove the two lines mentioned above, but on quit and save, I'm told I have a read-only file system!
1. How can I mount a read-write file system so I can edit /etc/fstab?
2. What's wrong with my two new entries in /etc/fstab? After formatting /dev/sdb1 and /dev/sdb2, I checked the they were mountable with # mount /dev/sdbn /bakn (n = 1, 2) before editing fstab.
I have a removable SATA Mobilerack which i use to play with.It has redhat linux loaded on a 500GB disk and i made a new partition using fdisk and then made an ext3 filesystem with mkfs. I then tried to edit fstab to add the new partition but have obviously stuffed it up. When I tried to reboot I get the error fsck ext3: UNABLE TO RESOLVE `LABEL=/mnt'.
I "upgraded" to Karmic and now my computer won't start. It shows the grub menu, I select the first Ubuntu option, and it shows the white logo. Underneath the logo these words appear, and it does nothing:Quote:One or more of the mounts listed in /etc/fstab cannot yet be mounted: /boot: waiting for UUID=338c820e..Press ESC to enter a recovery shell
I'm trying to add a line to fstab to mount a share on every boot. I can mount the share manually using
sudo mount -t nfs 192.168.2.1:/x_machine /mnt/test I've added the line 192.168.2.1:/x_machine /mnt/test nfs rw,hard,intr 0 0
to my /etc/fstab file, but it doesn't seem to mount on boot. What am I missing. I tried looking in the log files for an error, but couldn't find anything. Ubuntu 10.04 x64 desktop edition.
I have ntfs partition installed bran new ubuntu system. I have some problem with unrar utf8 character zip files.Then i change my fstab file that uses files in D:ubuntudisks oot.disk and i added with out no fearless Code: ,utf8 and after all now i can't boot my linux system it does not allow me to change anything in fstab file. Although i use as a prefix sudo or as a root "sudo -i" commands I dont have any right to change it.
Could any RAID gurus kindly assist me on the following RAID-5 issue?I have an mdadm-created RAID5 array consisting of 4 discs. One of the discs was dropping out, so I decided to replace it. Somehow, this went terribly wrong and I succeeded in marking two of the drives as faulty, and the re-adding them as spare.
Now the array is (logically) no longer able to start:
mdadm: Not enough devices to start the array.Degraded and can't create RAID ,auto stop RAID [md1]
Code: mdadm --create --assume-clean --level=5 --raid-devices=4 /dev/sda2 /dev/sdb2 /dev/sdc2 /dev/sdd2 As I don't want to ruin the maybe small chance I have left to rescue my data, I would like to hear the input of this wise community.
It's been a real battle, but I am getting close.I won't go into all the details of the fight that I have had, but I've almost made it to the finish line. Here is the set up. ASUS Z8PE-D18 mother board 2 CPU, 8 Gig Ram. I recently added an OCZ Agility SSD, defined a raid 1 virtual disk on the 1 terabyte WD HDD drives, which will holds all of my user data, the SSD is for executables.The bios is set to AHCI. Windows 7 installed fine, recognizes the raid VD just fine.
I installed Ubuntu 10.04 by first booting into try and mode, then opening a terminal and issuing a "sudo dmraid -ay" command. Then performing the install. I told it to install the raid components, and told it to let me specify the partitions manually. When setting up the partitions, I told it to use the free space I set aside on the SSD from the Windows 7 install as ext4 and to mount root there. Ubuntu installed just fine, grub2 comes up just fine, and Windows 7 boots with out a hitch, recognizing the mirrored partition as I indicated previously. When I tell grub to boot linux however, it pauses and I get the "no block devices found" message. It will then boot, but it does not recognize the raid array. After Ubuntu starts up I can run "dmraid -ay" and it recognizes the raid array, but shows the two component disks of the raid array as well. It will not allow the component disks to be mounted, but they show up which is annoying. (I can live with that if I have to)
I have fixed a similar problem before by setting up a dmraid script in /etc/initramfs-tools/scripts/local-top ... following the instructions found at the bottom of this blog:[URL].. To recap: My problem is that after grub2 fires up Ubuntu 10.04.1 LTS (Lucid Lynx), it pauses, and I get "no block devices found" It then boots but does not recognize the raid array untill I manually run "dmraid -ay". I've hunted around for what to do but I have not found anything. It may be some timing issue or something, but I am so tired of beating my head against this wall.
I've just started playing around with a Sheevaplug running a very light version of Ubuntu. I'm planning to run it with an SD card to store all my server data and a USB stick to regularly back up some of it.My problem is that the 2 partitions on my SD card mount fine at boot, but my USB stick's single partition does not. Could it be that the mounts specified in fstab are done before my USB device has finished getting alive? Mounting the USB stick manually works perfectly well.
Code: ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver orion-ehci orion-ehci.0: Marvell Orion EHCI orion-ehci orion-ehci.0: new USB bus registered, assigned bus number 1 orion-ehci orion-ehci.0: irq 19, io mem 0xf1050000 orion-ehci orion-ehci.0: USB 2.0 started, EHCI 1.00 usb usb1: configuration #1 chosen from 1 choice hub 1-0:1.0: USB hub found hub 1-0:1.0: 1 port detected Initializing USB Mass Storage driver.....
In the dmesg Code: usb-storage: device scan complete comes after
Code: EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended which makes me think the USB stick has missed the fstab train the 2 SD card partitions are on. And changing the order of the entries in fstab does not make any difference either.
I'm not planning to reboot my Sheevaplug every 5 minutes, but I like things to be nice and clean.
shut down my RHEL 4 system with an error still present in the /etc/fstab file. Current symptom: When I now try to boot, everything hangs when "Enabling swap space". Highly likely, the reason is the failure to "Mount local filesystems" in the previous step (i.e. "mount point 0 does not exist" = error due to my incorrect line in the /etc/fstab file).Question: Is there any way that I can still boot my system, such that I can remove the incorrect line in the /etc/fstab file?
