Unable to mount root after upgrade from FC4->FC5t3
Dave Atkins
thedave at ix.netcom.com
Wed Mar 1 00:36:14 UTC 2006
I mentioned this a while back and got no response, I was waiting for
someone else to confirm before I bugzilled it.
So, I suppose it's time for reporting it as a true bug.
>From David Atkins, 01 Feb 2006 - "Did something happen to mkinitrd?"
> OK, I might be going crazy, but didn't mkinitrd use to include the
> modules and dependencies aliased as scsi_host_adapter
> in /etc/modprobe.conf?
>
> I've got a USB hard drive that I use as part of my home directories,
> that need to be fsck'ed and mounted at boot.
>
> I thought I fixed this by adding the following lines
> to /etc/modprobe.conf:
> alias scsi_hostadapter ehci_hcd
> alias scsi_hostadapter sd_mod
> alias scsi_hostadapter usb_storage
>
> The disk is mounted as (/etc/fstab):
> LABEL=storage /media/storage ext3 defaults,noatime 1 1
>
> I fiddled with this for a while earlier in testing, and I thought that
> these mod's would cause new kernel installs to run mkinitrd and
> include the appropriate modules so that these drives would be
> available as soon as udev loads (like it does for the root drive).
>
> I've kind of glossed over the MAKEDEV traffic on the list because I
> thought it didn't pertain to me. Could this be a part of that
> craziness?
>
> Thanks,
> Dave.
>
> PS - This is the output of: mkinitrd -v -f
> initrd-2.6.15-1.1884_FC5smp.img 2.6.15-1.1884_FC5smp
> Creating initramfs
> Looking for deps of module sd_mod: scsi_mod
> Looking for deps of module scsi_mod
> Looking for deps of module ehci_hcd
> Looking for deps of module usb_storage
> Looking for deps of module ide-disk
> Looking for driver for device sda2
> Looking for deps of module libata: scsi_mod
> Looking for deps of module ata_piix: libata scsi_mod
> Looking for deps of module ext3: jbd
> Looking for deps of module jbd
> Looking for deps of module dm-mod
> Looking for deps of module dm-mirror: dm-mod
> Looking for deps of module dm-zero: dm-mod
> Looking for deps of module dm-snapshot: dm-mod
> Using
> modules: /lib/modules/2.6.15-1.1884_FC5smp/kernel/drivers/scsi/scsi_mod.ko /lib/modules/2.6.15-1.1884_FC5smp/kernel/drivers/scsi/sd_mod.ko /lib/modules/2.6.15-1.1884_FC5smp/kernel/drivers/scsi/libata.ko /lib/modules/2.6.15-1.1884_FC5smp/kernel/drivers/scsi/ata_piix.ko /lib/modules/2.6.15-1.1884_FC5smp/kernel/fs/jbd/jbd.ko /lib/modules/2.6.15-1.1884_FC5smp/kernel/fs/ext3/ext3.ko /lib/modules/2.6.15-1.1884_FC5smp/kernel/drivers/md/dm-mod.ko /lib/modules/2.6.15-1.1884_FC5smp/kernel/drivers/md/dm-mirror.ko /lib/modules/2.6.15-1.1884_FC5smp/kernel/drivers/md/dm-zero.ko /lib/modules/2.6.15-1.1884_FC5smp/kernel/drivers/md/dm-snapshot.ko
> /sbin/nash -> /tmp/initrd.Z10326/bin/nash
> /sbin/insmod.static -> /tmp/initrd.Z10326/bin/insmod
> copy from
> `/lib/modules/2.6.15-1.1884_FC5smp/kernel/drivers/scsi/scsi_mod.ko' [elf32-i386] to `/tmp/initrd.Z10326/lib/scsi_mod.ko' [elf32-i386]
> copy from
> `/lib/modules/2.6.15-1.1884_FC5smp/kernel/drivers/scsi/sd_mod.ko' [elf32-i386] to `/tmp/initrd.Z10326/lib/sd_mod.ko' [elf32-i386]
> copy from
> `/lib/modules/2.6.15-1.1884_FC5smp/kernel/drivers/scsi/libata.ko' [elf32-i386] to `/tmp/initrd.Z10326/lib/libata.ko' [elf32-i386]
> copy from
> `/lib/modules/2.6.15-1.1884_FC5smp/kernel/drivers/scsi/ata_piix.ko' [elf32-i386] to `/tmp/initrd.Z10326/lib/ata_piix.ko' [elf32-i386]
> copy from
> `/lib/modules/2.6.15-1.1884_FC5smp/kernel/fs/jbd/jbd.ko' [elf32-i386] to `/tmp/initrd.Z10326/lib/jbd.ko' [elf32-i386]
> copy from
> `/lib/modules/2.6.15-1.1884_FC5smp/kernel/fs/ext3/ext3.ko' [elf32-i386] to `/tmp/initrd.Z10326/lib/ext3.ko' [elf32-i386]
> copy from
> `/lib/modules/2.6.15-1.1884_FC5smp/kernel/drivers/md/dm-mod.ko' [elf32-i386] to `/tmp/initrd.Z10326/lib/dm-mod.ko' [elf32-i386]
> copy from
> `/lib/modules/2.6.15-1.1884_FC5smp/kernel/drivers/md/dm-mirror.ko' [elf32-i386] to `/tmp/initrd.Z10326/lib/dm-mirror.ko' [elf32-i386]
> copy from
> `/lib/modules/2.6.15-1.1884_FC5smp/kernel/drivers/md/dm-zero.ko' [elf32-i386] to `/tmp/initrd.Z10326/lib/dm-zero.ko' [elf32-i386]
> copy from
> `/lib/modules/2.6.15-1.1884_FC5smp/kernel/drivers/md/dm-snapshot.ko' [elf32-i386] to `/tmp/initrd.Z10326/lib/dm-snapshot.ko' [elf32-i386]
> /sbin/lvm.static -> /tmp/initrd.Z10326/bin/lvm
> /etc/lvm -> /tmp/initrd.Z10326/etc/lvm
> `/etc/lvm/lvm.conf' -> `/tmp/initrd.Z10326/etc/lvm/lvm.conf'
> Adding module scsi_mod
> Adding module sd_mod
> Adding module libata
> Adding module ata_piix
> Adding module jbd
> Adding module ext3
> Adding module dm-mod
> Adding module dm-mirror
> Adding module dm-zero
> Adding module dm-snapshot
>
On Sat, 2006-02-25 at 11:05 +0100, Vladimir Vukicevic wrote:
> Problem solved -- the initrd image didn't include sd_mod.ko! Hence,
> no sd* devices were available, and thus no root. Running mkinitrd
> with --with=sd_mod fixed things -- I'm not sure why mkinitrd isn't
> picking up on this? I was running a non-FC kernel beforehand, where I
> had compiled in ata_piix and the various scsi modules while futzing
> around with trying to get suspend/hibernate to work, so my
> modprobe.conf and friends had no mention of ata_piix or any of the
> scsi bits, not sure if that had an effect on the installer.
>
> - Vlad
>
> On 2/25/06, Vladimir Vukicevic <vladimirv at gmail.com> wrote:
> > After doing an installer-based upgrade from FC4 to FC5t3, at boot I see:
> >
> > scsi0 : ata_piix
> > [...]
> > Loading ahci.ko module
> > Creating root device.
> > Mounting root filesystem.
> > mount: could not find filesystem '/dev/root'
> > Setting up other filesystems.
> > Setting up new root fs
> > setuproot: moving /dev failed: No such file or directory
> > no fstab.sys, mounting internal defaults
> > setuproot: error mounting /proc: No such file or directory
> > setuproot: error mounting /sys: No such file or directory
> > Switching to new root and running init.
> > unmounting old /dev
> > unmounting old /proc
> > unmounting old /sys
> > switchroot: mount failed: No such file or directory
> > Kernel panic - not syncing: Attempted to kill init!
> >
> > Any idea what the issue is? I can't find any info on what's changed
> > in the boot process (I'm still able to boot my previous 2.6.14 kernels
> > fine), nor do I seem to be able to get a shell in the initrd via
> > init=/bin/sh (just seems to ignore the init kernel option). Note that
> > at upgrade time, I told the installer to not touch my grub config; it
> > just added the new kernel as an option.
>
More information about the fedora-test-list
mailing list