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@xxxxxxxxx> 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.
--
fedora-test-list mailing list
fedora-test-list@xxxxxxxxxx
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list