ok this is out of order but it belongs here.
If you "hack" the fstab and change ext3 to ext2 and reboot it will still have ext3 errors because the mkinitrd uses the /etc/fstab at build time to determine modules. So to get it to load ext2 instead of ext3 you need to change fstab then do a new initrd so that it knows the changes and loads the right drivers for the partition.
-----Original Message----- From: fedora-list-bounces@redhat.com [mailto:fedora-list-bounces@redhat.com]On Behalf Of Terry Polzin Sent: Thursday, December 02, 2004 2:27 PM To: For users of Fedora Core releases Subject: Re: FC3 SMP builds do NOT contain ext3 drivers in the build!!!!
On Thursday 02 December 2004 14:14, Fred Skrotzki wrote:
# grub.conf generated by anaconda # # Note that you do not have to rerun grub after making changes to this file # NOTICE: You have a /boot partition. This means that # all kernel and initrd paths are relative to /boot/, eg. # root (hd0,0) # kernel /vmlinuz-version ro root=/dev/sda2 # initrd /initrd-version.img #boot=/dev/sda default=1 timeout=5 splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title Fedora Core (2.6.9-1.681_FC3) root (hd0,0) kernel /vmlinuz-2.6.9-1.681_FC3 ro root=LABEL=/1 initrd /initrd-2.6.9-1.681_FC3.img title Fedora Core (2.6.9-1.681_FC3smp) root (hd0,0) kernel /vmlinuz-2.6.9-1.681_FC3smp ro root=LABEL=/1 initrd /initrd-2.6.9-1.681_FC3smp.img title Fedora Core (2.6.9-1.667smp) root (hd0,0) kernel /vmlinuz-2.6.9-1.667smp ro root=LABEL=/1 initrd /initrd-2.6.9-1.667smp.img title Fedora Core-up (2.6.9-1.667) root (hd0,0) kernel /vmlinuz-2.6.9-1.667 ro root=LABEL=/1 initrd /initrd-2.6.9-1.667.img
-----Original Message----- From: fedora-list-bounces@redhat.com [mailto:fedora-list-bounces@redhat.com]On Behalf Of Terry Polzin Sent: Thursday, December 02, 2004 2:07 PM To: For users of Fedora Core releases Subject: Re: FC3 SMP builds do NOT contain ext3 drivers in the build!!!!
On Thursday 02 December 2004 14:02, Fred Skrotzki wrote:
Drive was low level formatted and verified before and after 3 builds. It boots and works fine under single proc. I even build it on another drive just to be sure.
BOX is a full blown server class system. hot swap drives, etc... HP LP2000r dual 1.0 Ghz P4 1 gig ram
here is the drive config Device Boot Start End Blocks Id System /dev/sda1 * 1 13 104391 83 Linux /boot ext3 /dev/sda2 14 1548 12329887+ 83 Linux / ext3 /dev/sda3 1549 1809 2096482+ 82 Linux swap swap /dev/sda4 1810 4427 21029085 5 Extended /dev/sda5 1810 2070 2096451 83 Linux /var/log ext3
fstab LABEL=/1 / ext3 defaults 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /dev/shm tmpfs defaults 0 0 none /proc proc defaults 0 0 none /sys sysfs defaults 0 0 LABEL=/var/log1 /var/log ext3 defaults 1 2 LABEL=SWAP-sda3 swap swap defaults 0 0
Here is what is left on the screen when booting using SMP:
ext3: unknown symbol journal_get_write_access ext3: unknown symbol journal_undo_access ext3: unknown symbol journal_create_access ext3: unknown symbol journal_destroy ext3: unknown symbol journal_clear_error ext3: unknown symbol journal_stop ext3: unknown symbol journal_init_inode ext3: unknown symbol journal_start ext3: unknown symbol log_wait_command ext3: unknown symbol journal_release_buffer ext3: unknown symbol journal_check_available_features ext3: unknown symbol journal_abort ext3: unknown symbol journal_restart insmod: error inserting '/lib/ext2.ko": -1 unknown symbol in module ERROR: /sbin/udevstart exited abnormally creating root drive umount /sys failed: 16 Mounting root file system mount: error 19 mounting ext3 mount: error 2 mounting none switching to new root switchroot: mount failed: 22 umount /initrd/dev failed: 2 Kernel panic - not syncing......
Would you send on a copy of your grub.conf.
Like Ed Wilts suggested, doctor the fs tab and make the root partition ext2 and boot smp. Sounds like the journal is hosed.