我轉左 Fedora 9 部機既 hardware 之後, 就因為咁 boot 唔起:
Readling all physical volumes.
No volume groups found
Volume group “VolGroup00″ not found
Unable to access resume device (/dev/VolGroup00/LogVol01)
mount: could not find fileysstem ‘/dev/root’
setuproot: moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Mount failed for selinuxfs on /selinux: No such file or directory
switchroot: mount failed: No such file or directory
好明顯個 kernel 認唔到隻 harddisk, 解決方法:
http://www.justlinux.com/forum/showthread.php?threadid=151883
It may be that your new motherboard uses a different SATA chipset. Fedora builds a ramdisk with a list of drivers determined at install time. It wouldn’t work if you moved to a chipset whose driver wasn’t included on that ramdisk. The rescue mode installer will probe for supported hardware by trying every driver it knows about and so will pick up the disks.
If this is indeed the case you will need to add the name of the correct kernel module to Fedora’s ramdisk. You can find this by booting into rescue mode and seeing which modules are loaded. SATA disks show up as SCSI so
Code:dmesg | grep ^scsi[0-9]
may be helpful.
The rest of the procedure must be carried out chrooted to your system. Fedora rescue mode mounts the existing system on /mnt/sysimage so you can access it with
Code:chroot /mnt/sysimage /bin/bash -login
Now you must add the module as an alias to scsi_hostadapter in /etc/modprobe.conf. For example, if you determined that you needed the ahci module you would add
Code:alias scsi_hostadapter ahci
Add it below any existing scsi_hostadapter lines. They will all be picked up.
Finally you need to create the new ramdisk. Fedora has a script to do this:
Code:/sbin/new-kernel-pkg –update –mkinitrd
where
is your kernel version. Normally you would use uname -r to find this but the kernel you have on your system may not be the same as on the rescue CD. To be safe you should look at /boot/grub/grub.conf. For example, on one of my systems I have this:
Code:default=0 … title Fedora (2.6.25.3-18.fc9.i686) … title Fedora (2.6.25.14.fc9.i686)
Grub is set to boot the first kernel in the list (because default is 0) and so the kernel version is 2.6.25.3-18.fc9.i686. Of course you could repeat new-kernel-pkg for every installed kernel to eliminate all doubt.
即係要整隻救機碟
orz