Hi, folks,
This is an FC5 specific question.
I have an AMD Quad opteron system that has all of its partitions on
RAID-1 (from sda and sdb SATA disks through Si3114 + libata driver).
All partitions are XFS, except for the /boot, which is ext3 (FC5
refused to create an XFS boot partition, which BTW works on many other
systems i have under FC3).
When booting in the latest 2.6.17 FC5 kernel, I get the following
message:
--------
mount: could not find filestystem '/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
BTW, I get similar (but not identical) error when booting in the older
2.6.15 kernel.
-------
The / partition is on /dev/md1, and it has type of XFS. See below the
/etc/fstab. I have an initrd image that I believe is OK (but maybe not).
I tried booting with the default = grub, but then I got frustrated, and
moved to lilo (22.7, also pretty intelligent about RAID, XFS, and all
that stuff). No difference -- so i may as well go back to grub. The
system boots in fine from the rescue CD followed by a chroot
/mnt/sysimage.
Here is /etc/fstab:
/dev/md1 / xfs defaults 1 1
/dev/md0 /boot ext3 defaults 1 2
devpts /dev/pts devpts gid=5,mode=620 0 0
tmpfs /dev/shm tmpfs defaults 0 0
/dev/md5 /home xfs defaults 1 2
/dev/md4 /myroot xfs defaults 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs defaults 0 0
/dev/md2 /usr/local xfs defaults 1 2
/dev/md3 /var xfs defaults 1 2
LABEL=SWAP-sdb3 swap swap defaults 0 0
LABEL=SWAP-sda3 swap swap defaults 0 0
( With the rescue CD the swap partitions also come up nice. )
-------------------
Here is initrd:
initrd/
|-- bin
| |-- insmod
| |-- modprobe
| -- nash
|-- dev
| -- mapper
|-- etc
|-- init
|-- lib
| |-- ext3.ko
| |-- jbd.ko
| |-- libata.ko
| |-- raid1.ko
| |-- sata_nv.ko
| |-- scsi_mod.ko
| |-- sd_mod.ko
| -- xfs.ko
|-- proc
|-- sbin
| |-- insmod
| |-- modprobe
| -- nash
|-- sys
-- sysroot
I made several attempts to re-create initrd myself after the failures
with default one. I thought maybe the SATA drivers or XFS, or ext3 or
whatever is missing.
For example:
mkinitrd -f -v --preload ext3 --preload xfs /boot/initrd-2.6.17.img 2.6.17
But it seems to me that all essential components are in the initrd/ .
----------------
HEre is lilo.conf:
prompt
timeout=100
default=2.6.17_FC5
boot=/dev/md0
map=/boot/map
install=/boot/boot.b
#message=/boot/message
raid-extra-boot=mbr-only
image=/boot/vmlinuz-2.6.17-1.2145_FC5smp
label=2.6.17_FC5smp
initrd=/boot/initrd-2.6.17-1.2145_FC5smp.img
read-only
root=/dev/md1
image=/boot/vmlinuz-2.6.17-1.2145_FC5
label=2.6.17_FC5
initrd=/boot/initrd-2.6.17-1.2145_FC5.img
read-only
root=/dev/md1
append="init=/sbin/init"
....
-----------------
And here is grub.conf:
default=0
timeout=15
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.17-1.2145_FC5smp)
root (hd0,0)
kernel /vmlinuz-2.6.17-1.2145_FC5smp ro root=/dev/md1 rhgb quiet
initrd /initrd-2.6.17-1.2145_FC5smp.img
title Fedora Core (2.6.17-1.2145_FC5)
root (hd0,0)
kernel /vmlinuz-2.6.17-1.2145_FC5 ro root=/dev/md1 rhgb quiet
initrd /initrd-2.6.17-1.2145_FC5.img
There must be a simple solution but i have a hard time finding it.
Let me know if you can help.
Gaspar
