Description of problem: Install of Fedora 10 ppc64 on an IBM 9111-520 (Power5 CPU) fails to boot with error: /pci@800000020000003/pci@2,4/pci1069,b166@1/scsi@0/sd@8,0:-1,/etc/yaboot.conf: Unknown or corrupt filesystem Can't open config file Welcome to yaboot version 1.3.14 (Red Hat 1.3.14-6.fc10) Version-Release number of selected component (if applicable): yaboot 1.3.14-6.fc10 How reproducible: Install in the way I did. Steps to Reproduce: 1. System has 4 x 73 GB hard disks and I wanted some redundancy so I partitioned like so: (identical across sd[a-d]): 1 - PPC PReP 2 - 196 MB software RAID 3 - 2048 MB software RAID 4 - Extended 5 - Rest of disk software RAID md0 /boot - RAID1 sd[a-d]2 with 1 hot spare md1 swap - RAID5 sd[a-d]3 with 1 hot spare md2 / - RAID5 sd[a-d]5 with 1 hot spare 2. Install went fine (using a serial console) 3. Install finishes but wont boot Actual results: Error on console when trying to boot: /pci@800000020000003/pci@2,4/pci1069,b166@1/scsi@0/sd@8,0:-1,/etc/yaboot.conf: Unknown or corrupt filesystem Can't open config file Welcome to yaboot version 1.3.14 (Red Hat 1.3.14-6.fc10) Expected results: System should boot. Additional info: I created a PPC PReP partition on each of the 4 system disks. I imagine that this is the problem. Booting the DVD and doing a "linux rescue" will successfully mount the system image under /mnt/sysimage so I can see the /etc/yaboot.conf. How can I now manually re-write yaboot.conf and re-install yaboot into the PPC PReP partitions so I can boot.
In rescue mode, there should be vi. Look at "man yaboot.conf". To reinstall use ybin.
I've looked at /etc/yaboot.conf and it seems fine. I've re-installed yaboot using "mkofboot -v" whilst chrooted into /mnt/sysimage however the system still wont boot. Does yaboot support /boot being an md device ? My /etc/yaboot.conf is: # yaboot.conf generated by anaconda boot=/dev/sdd1 /dev/sdc1 /dev/sdb1 /dev/sda1 init-message="Welcome to Fedora!\nHit <TAB> for boot options" partition=2 timeout=80 install=/usr/lib/yaboot/yaboot delay=5 enablecdboot enableofboot enablenetboot nonvram fstype=raw image=/vmlinuz-2.6.27.5-117.fc10.ppc64 label=linux read-only initrd=/initrd-2.6.27.5-117.fc10.ppc64.img append="console=hvsi0 rhgb quiet root=UUID=eaa80722-0bb6-44f6-ac0a-df2489543d1d"
(In reply to comment #0) > Steps to Reproduce: > 1. System has 4 x 73 GB hard disks and I wanted some redundancy so I > partitioned like so: > > (identical across sd[a-d]): > > 1 - PPC PReP > 2 - 196 MB software RAID > 3 - 2048 MB software RAID > 4 - Extended > 5 - Rest of disk software RAID > > md0 /boot - RAID1 sd[a-d]2 with 1 hot spare To the best of my knowledge yaboot will not boot from an md device. Can you try dismantling the RAID and using plain /dev/sda2 for /boot? > 2. Install went fine (using a serial console)> Additional info: > > I created a PPC PReP partition on each of the 4 system disks. I imagine that > this is the problem. This isn't a problem per.se. but will not work as you expect. On my systems I generally have one PReP partition and manually keep /boot "in sync" with dd. If the system fails netboot is a very relaiable way to get into a rescue kernel. > How can I now manually re-write yaboot.conf and re-install yaboot into the PPC > PReP partitions so I can boot. Something like: for p in sdb1 sdc1 sdd1 ; do dd if=/dev/sda1 of=/dev/$p ; done umount /boot ;for p in sdb2 sdc2 sdd2 ; do dd if=/dev/sda2 of=/dev/$p ; done ; mount /boot
I think this may be a problem with the boot device set via SMS (System Management... like a BIOS). I did actually get it booting with a single PPC PReP partition and an ext2 /boot on sda only. I'm trying to test a different config but currently have problems with anaconda crashing and giving me a backtrace when I ask it to review and modify the existing partitioning after I've set a boot device in SMS (read BIOS). Will update tomorrow... time to go home in my timezone +10:30
I have confirmed that this was a problem with the boot device setting in SMS (think BIOS). Fedora 10 and yaboot are working fine in my initial configuration. That is: 4 PPC PReP partitions (one per physical disk). RAID1 /boot RAID5 swap and / Thanks guys for a great system. Sorry for the false alarm.