[Bug 576001] Re: kernel 2.6.32-32 makes machine hang during boot

Charles Auer auer.charles at gmail.com
Wed Jun 30 06:28:14 UTC 2010


I did a clean install using the x64 version of Lucid, kernel 2.6.32-31.
The only thing I did before upgrading to the new kernel (2.6.32-32) was
build the drivers for my RAID card (Highpoint Technologies RocketRAID
2640x1) and added an entry to fstab to mount the array on boot.

It's now sitting at the same thing it was in the original bug report:
fsck /dev/sda1 clean...

I booted into the previous kernel and commented out the fstab entry for
my RAID array and rebooted into the new kernel.

I was met with a logon prompt, as expected.

I hooked up an external USB hard drive to the machine, added an entry to
fstab and rebooted. It came up fine.

Disconnected the USB drive and rebooted, it hung again. I tried
rebooting into the previous kernel with the drive disconnected and it
hung at fsck /dev/sda1 clean.. until I hit "s" then it continued to boot
and came up as normal.

Booted into the new kernel and hit "s" even though it was just sitting
at a blinking cursor, and arrived at a logon prompt.

Did the same after uncommenting the RAID volume, same thing happened.
After hitting "s", I got "skipping /array at user's request" that device
is set to be mounted on /array in fstab.

My guess is that it's not showing the press "s" to skip, etc if is
cannot find a device listed in fstab.

It sounds like there is something causing the OS to not display if there
is an entry in fstab, but the disk doesn't exist.

There was a thread about a similar thing happening on Ubuntu desktop, except they were prompted to hit "s" or "m"
http://ubuntuforums.org/showthread.php?t=1520413

Also, I just wanted to note: I went thru many, kernel upgrades on Karmic
without having to comment out the fstab entry in order for the machine
to boot. All I needed to do was build the drivers after I booted into
the new kernel and then reboot and all was well.

I hope this helps; it sounds like the -server kernel handles mounting
fstab differently somehow. I don't know.

-- 
kernel 2.6.32-32 makes machine hang during boot
https://bugs.launchpad.net/bugs/576001
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to linux in ubuntu.




More information about the kernel-bugs mailing list