Description of problem: Just after the installation (and reboot), the boot process fails with this message VFS: cannot open rood device "sda1" or unknown-block(0,0) Please append a correct "root=" boot option Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Version-Release number of selected component (if applicable): anaconda-11.1.0.89-1.x86_64.rpm kernel-2.6.17-1.2617.2.1.fc6.x86_64.rpm grub-0.97-11.x86_64.rpm How reproducible: Everytime Steps to Reproduce: 1. Install Rawhide (this *might* be the one which will fo for fc6t3 freeze) 2. Reboot as mentioned in the end of install process 3. Kernel Panic! Actual results: Kernel Panic Expected results: Correct bootup Additional info: I have an AMD athlon 64 bit processor (3500+), SATA disk & performed a network installation. I also changed the default name "Fedora Core" in the boot menu (during install) to "Rawhide". Following was my disk structure /dev/sda1 - / - 80000 M - EXT3 /dev/sda2 - swap - 512 M /dev/sda3 - /data - ~=70000M - EXT3
*** Bug 205348 has been marked as a duplicate of this bug. ***
please attach /etc/modprobe.conf and /etc/fstab
Hi Dave, How can I attach the /etc/modprobe.conf and /etc/fstab files when the OS is not booting? :) Moreover, i've installed fc6t3 now & its working.
I get the exact same error as Jain after installing FC6test3 (from the dvd image from torrent.fedoraproject.org) on my new laptop. This is on a Core2Duo (T5600) and SATA disk. kernel version is 2.6.17-1.2630.fc6 My disk looks like the one above: /dev/sda1 59GB ext3 /dev/sda2 1GB linux-swap /etc/modprobe.conf: alias scsi_hostadapter ata_piix /etc/fstab: LABEL=/ / ext3 defaults 1 1 devpts /dev/pts devpts gid=5,mode=620 0 0 tmpfs /dev/shm tmpfs defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0 /dev/sda2 swap swap defaults 0 0
Just a bit of more information. My computer is a ZNote 6015, based on Intel 945-GM/ICH7-M chipset. When starting in rescue mode from the disc the hd works just fine. The modules that are loaded in rescue mode are (at least the ones that seems like they could be relevant to me...): raid456 157057 0 raid1 58449 0 raid0 41153 0 ata_piix 48841 3 libata 146801 1 ata_piix iscsi_tcp 59073 0 libiscsi 61649 1 iscsi_tcp scsi_transport_iscsi 67289 2 iscsi_tcp,libiscsi sr_mod 52837 0 sd_mod 56513 3 scsi_mod 195217 6 libata,iscsi_tcp,libiscsi,scsi_transport_iscsi,sd_mod_sd_mod
Ok. Upgrading to latest rawhide kernel (2.6.17-1.2647.fc6) fixed this for me...
Sorry for the bombing here, but I just realized what was nagging me the whole time (though I stupidly enough didn't realize what it was). My default grub.conf after the installation had no initrd in it! No wonder the modules wasn't loaded like they should. Could this be the same issue as the reporter above was experiencing? That upon installation the initrd is never added to grub.conf, but it is upon upgrading? I upgraded my kernel using "-Uvh" (Yes I know. That's not the best way. But it worked ;-).
Hi Daniel, I have no way of checking that now... as I have done a clean installation of fc6t3 & its working as expected. :) Mayank
I just installed FC6t3 (64bit version) on my SATA disk and got the same results. This excerpt from /root/install.log might be interesting (booted to rescue mode to see this): ... Installing mkinitrd - 5.1.15-1.i386 Installing kernel - 2.6.17-1.2630.fc6.x86_64 /sbin/mkinitrd: line 282: /sbin/nash: No such file or directory /sbin/mkinitrd: line 282: echo: write error: Broken pipe /sbin/mkinitrd: line 282: /sbin/nash: No such file or directory /sbin/mkinitrd: line 282: /sbin/nash: No such file or directory /sbin/mkinitrd: line 282: /sbin/nash: No such file or directory no temporary directory could be found. mkinitrd failed error: %post(kernel-2.6.17-1.2630.fc6.x86_64) scriptlet failed, exit status 1 ... ... Installing mkinitrd - 5.1.15-1.x86_64 ... (/mnt/sysimage)/sbin/nash is in its correct location at the moment, but it may not have been there during installation. /sbin/nash is apparently provided by mkinitrd. There is no mention of initrd in /boot/grub/grub.conf after installation. I wonder if this is somehow related to using 64bit version of Fedora? Daniel didn't mention which variant he used, but at least his laptop would be capable of running x86_64. I'm also wondering why mkinitrd-x86_64 is installed only after installing mkinitrd-i386 and the kernel, I'd guess the proper variant of mkinitrd would need to be already installed before installing the kernel.
(In reply to comment #9) > I wonder if this is somehow related to using 64bit version of Fedora? Daniel > didn't mention which variant he used, but at least his laptop would be capable > of running x86_64. Oh, sorry. Yes, I'm on x86_64. A Core2Duo actually.
Bug 206453 has much more information about this bug. I'd even suggest marking this as a duplicate of that bug, although this bug was filed earlier..
*** This bug has been marked as a duplicate of 206453 ***