View Full Version : [ubuntu] why does boot fsck hang with 2.6.23-2[2-4]?

August 24th, 2010, 06:44 PM
My system has two kernels: 2.6.32-21 (came with 10.04) and 2.6.32-24 (pushed by update). when I boot the first, everything works fine. when I boot the second, fsck just hangs. I can ctrl-alt-del, but it just doesn't continue. Ctrl-C does nothing.

now, I know that the boot process stops on an fsck for a /dev/md1 device (identified via uuid). (these kernels are the -server varieties of the kernels). I can see just before the screen flashes by that RAID6 was loaded. (It goes by too quickly, so I cannot see whether the RAID1 module is loaded, and/or whether /dev/md1 exists or what /dev/disk/by-uuid/* are.)

How do I get the fsck.ext4 during boot to be a lot more verbose about what it thinks it is doing??
How do I get a simple program (fdisk -l /dev/md1) to be executed the instant just before the fsck? (this must be after the screen resolution switches, which happens just before the fsck.)
How do I keep the boot.log from being overwritten? the problem is that I cannot copy it, of course, when it hangs.

help appreciated.


ian dobson
August 24th, 2010, 07:02 PM

Maybe try starting with the noplymouth and noquiet kernel command line options (edit them in grub).

This might help, or maybe try booting in recovery mode with a serial console attached (another pc with null modem cable).

Ian Dobson

August 24th, 2010, 08:15 PM
Hit "s" to see it continues. It's probably failing to mount a device.

August 26th, 2010, 12:56 PM
thank you, everyone.

Charles---you were right. the 'S' hint is what I needed. It allowed me to get to a prompt. interesting, when verbose is set (which I have), so that I see the kernel messages, it never tells me about 'S'. this would have been a nice hint there.



August 30th, 2010, 11:43 AM
FYI I am seeing the same behaviour. No visual feedback what so ever when booting as a "normal" user. Booting in recovery mode on the older kernel shows a (non-blocking) fsck error.

FYI these bugs might be related and anyone experiencing this error should consider contributing to their resolution:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/563916 (for servers)