Bug 7174
Summary: | init run before all EXT3 drives are detected, stopping init | ||
---|---|---|---|
Product: | File System | Reporter: | Alex Berry (ajberry) |
Component: | ext3 | Assignee: | Andrew Morton (akpm) |
Status: | REJECTED INVALID | ||
Severity: | low | ||
Priority: | P2 | ||
Hardware: | i386 | ||
OS: | Linux | ||
Kernel Version: | 2.6.18 | Subsystem: | |
Regression: | --- | Bisected commit-id: | |
Attachments: | Kernel Config File |
Description
Alex Berry
2006-09-20 14:18:17 UTC
For got to add. Runing EM64T kernel on a Core 2 Duo 6300 Created attachment 9060 [details]
Kernel Config File
(Switched from bugzilla to email. Please retaain all cc's). On Wed, 20 Sep 2006 14:27:56 -0700 bugme-daemon@bugzilla.kernel.org wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=7174 > > Summary: init run before all EXT3 drives are detected, stopping > init > Kernel Version: 2.6.18 > Status: NEW > Severity: low > Owner: akpm@osdl.org > Submitter: ajberry@usa.net > > > Most recent kernel where this bug did not occur: > Distribution: > Hardware Environment: > Intel DG965MS (ICH8) > 2 GB Ram > 200GB Sata II Hard Drive 2 ext3 partitions, 1 swap > > Software Environment: > Ubuntu 6.06.1 Desktop > All of EXT3 and SATA is Build into the kernel, no initrd at boottime. > > Problem Description: > When booting init starts running fsck and /dev/sda2 is "no such file or > directory". Boot stops and Control-D must be pressed. After this the partition > is dectected and the drive comes up and is properly mounted. I can boot 2.6.15 > with out this problem (but with acpi=off). I have not run into this on other > systems with similar configurations with 2.6.16/17. > > Excpert From Console Log: > * Checking all filesystems... [80G fsck.ext3: No such file or directory > while trying to open /dev/sda2 > > /dev/sda2: > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the superblock > is corrupt, and you might try running e2fsck with an alternate superblock: > e2fsck -b 8193 <device> > > > [74G[ ok ] > [31m*[39;49m File system check failed. Please repair manually. > [31m*[39;49m CONTROL-D will exit from this shell and continue syste[ > 68.657843] e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex > m startup. > root@ubuntu:~# [ 70.313668] NET: Registered protocol family 10 > [ 70.318177] lo: Disabled Privacy Extensions > [ 70.322825] IPv6 over IPv4 tunneling driver > exit > [ 77.191994] kjournald starting. Commit interval 5 seconds > [ 77.192165] EXT3 FS on sda2, internal journal > [ 77.192170] EXT3-fs: mounted filesystem with ordered data mode. > [ 77.234688] Adding 1036184k swap on /dev/sda3. Priority:-1 extents:1 > across:1036184k > * Configuring network interfaces... [80G > [74G[ ok ] > > * INIT: Entering runlevel: 2 > What version of udev are you running? All I can think of is that udev was too slow in creating the /dev/sda2 device node. I could understand that happening if the sata drivers were modular (perhaps), but you have CONFIG_SCSI_SATA=y CONFIG_SCSI_SATA_AHCI=y, CONFIG_SCSI_ATA_PIIX=y. [ lots snipped - it's at http://bugzilla.kernel.org/show_bug.cgi?id=7174 ] Im using 079-0ubuntu34. I also noticed that if I hit Control-D before [ 70.313668] NET: Registered protocol family 10 [ 70.318177] lo: Disabled Privacy Extensions [ 70.322825] IPv6 over IPv4 tunneling driver occur, sda2 doesnt get mounted. /alex b I ended up putting a "sleep 5;" in my checkfs script. While not the best solution. I think it is something else that is out of date. So im still looking into it. /alex b |