FS#6562 - Module ext3 not loaded on boot

Attached to Project: Arch Linux
Opened by Johannes Jordan (FoPref) - Friday, 09 March 2007, 14:28 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 17 March 2007, 13:10 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture not specified
Severity Critical
Priority Normal
Reported Version 0.7.2 Gimmick
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After recent kernel update to
Linux fsi 2.6.20-ARCH #1 SMP PREEMPT Wed Feb 28 21:59:38 CET 2007 i686 Intel(R) Pentium(R) 4 CPU 2.00GHz GenuineIntel GNU/Linux

the machine didn't boot up. Module ext3 was not loaded so the root filesystem could not be mounted.

This is a server machine :-(((


I really love your efforts in providing a great, decent kernel experience. But I have to say, I'm disturbed about all the changes made lately which several times lead to a state where the system could not boot properly. This is a showstopper for every server usage! Let's see the reasons involved:
* RAID didn't work properly
* RAID again didn't work properly
* Intel busmaster driver didn't work without some strange kernel addon
* System hangs on UDEV startup, randomly
* ext3 could not be mounted (current)
...

Please be a little bit more conservative about the boot process.


Workaround: Rebuild mkinitcpio with explicit mention of ext3 module in mkinitcpio.conf
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Saturday, 17 March 2007, 13:58 GMT
Reason for closing:  Fixed
Comment by cristian (fancris3) - Friday, 09 March 2007, 16:59 GMT
I have 2 ide hdd whit 1 reiserfs, 2 ext3 (/ and /home), 2 ntfs and for sure 1 swap.
1 hdd whit ntfs primary and reiserfs and swap in extended.
Second hdd whith 1 ntfs and 2 ext3 all primary.
I'm using all the time the last kernel and Arch work without any error.All mount to boot.
I don't remember the last time when i did have trouble whit the kernel.
Maybe i'm lucky whit common hardware in my pc? Maybe because i'm reading the messages,news and forum?
I don't remember the last time when i have troble whit Arch "whithout my help".
HOOKS="base udev autodetect ide filesystems usplash" and earlymodule=piix in menu.lst works for my.
Comment by Johannes Jordan (FoPref) - Friday, 09 March 2007, 17:15 GMT
I didn't want to say this is a common problem, although there is another bug report which looks similiar (according to the comment of the reporting user):
http://bugs.archlinux.org/task/6550

If Arch works fine for you, great. It works fine for me on my other 3 systems, too. Insulting me, claiming I'm just too stupid (RTFM) won't fix this problem. Please only comment if you have something to say about the bug. This is not a forum but a bug reporting system.
Comment by cristian (fancris3) - Friday, 09 March 2007, 17:26 GMT
OK.Sorry i don't want to insulting you.
Comment by Tobias Powalowski (tpowa) - Friday, 09 March 2007, 20:55 GMT
my raid systems all run fine, probably the autodetection is again bugged.
which initcpio version you use?
Comment by Johannes Jordan (FoPref) - Saturday, 10 March 2007, 13:42 GMT
Mkinitcpio version:

current/mkinitcpio 0.5.13-1

Here is what made the boot successful:
MODULES="piix ext3"

boot line:
kernel /vmlinuz26 root=/dev/md1 md=1,/dev/hda2,/dev/hdc2

some interesting dmesg output:
ICH2: IDE controller at PCI slot 0000:00:1f.1
ICH2: chipset revision 5
ICH2: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xb800-0xb807, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xb808-0xb80f, BIOS settings: hdc:DMA, hdd:pio
Probing IDE interface ide0...
hda: MAXTOR 6L040J2, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: MAXTOR 6L040J2, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15

md: bind<hda2>
md: bind<hdc2>
raid1: raid set md1 active with 2 out of 2 mirrors
kjournald starting. Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.

md: md0 stopped.
md: bind<hda1>
md: bind<hdc1>
raid1: raid set md0 active with 2 out of 2 mirrors
EXT3 FS on md1, internal journal

btw, would you suggest to always use the fallback image on a server system or not?
Comment by Tobias Powalowski (tpowa) - Saturday, 10 March 2007, 14:19 GMT
misconfiguration bug not an issue, closing this one now
Comment by Tobias Powalowski (tpowa) - Saturday, 17 March 2007, 13:58 GMT
i cannot find any reason why this fails, i close it now again, if it happens again we need to debug this extensivly.
did here a couple of reboots on my raid1 machines no error at all with latest kernel

Loading...