[Cbe-oss-dev] help need: cannot boot after FC7 update on PS3

[Guo Tang]

Thanks Patrick,

If I reinstall my system with only
ext3 and swap. This should work, right?

Do you know whether IBM Cell SDK 3.0 can work on FC8? The SDK 
is the only thing I am trying to get to work in PS3. 

Thanks,
Guo

On Thu, 13 Dec 2007, Patrick Mansfield wrote:

> On Wed, Dec 12, 2007 at 07:20:25PM -0800, Guo Tang wrote:
> > Hi,
> > 
> > I installed FC7 from DVD. It works fine. Then I used "yum update" to 
> > update my FC7. Yum picked up a new kernel. Unfortunatly the box cannot 
> > boot anymore after the update. 
> > 
> > I read Geoff's how-to recovery guide. It is talking about kboot there. 
> > The boot loader I am using is yaboot. Could anyone tell me how to fix the 
> > yaboot? Or should I switch to kboot?
> 
> kboot is normally the otheros.bld, it parses the yaboot.conf file.
> 
> You should also be able to tab through at the boot prompt, and boot the
> previous F7 kernel.
> 
> > Here is the boot message on the screen:
> 
> Since you have LVM modules in your initrd, you probably have root fs on
> LVM, and are hitting this bug:
> 
> 	https://bugzilla.redhat.com/show_bug.cgi?id=249672
> 
> LVM does not recognize the ps3d disk name change. Still looks like no F7
> update for the fix. Not much you can easily do to workaround the bug.
> 
> If you re-install you might as well move to F8 - note the nash bug with
> F8, modify yaboot.conf and/or boot with root=/dev/psdaN. You could also
> try a yum upgrade to F8, that requires other hacks.
> 
> > loading ext3.ko module
> > usb 1-2: USB disconnect, address 2
> > Loading ps3stor_lib.ko module
> > Loading ps3disk.ko module
> > ps3disk_init:609: registered block deice major 253
> > ps3_system_bus_match:354: dev=8(sb_01), drv=6(ps3disk):miss
> > ps3_system_bus_match:354: dev=7(sb_02), drv=6(ps3disk): miss
> > ps3_system_bus_match:354: dev-6(sb_03), drv=6(ps3disk):match
> > ->ps3_system_bus_probe:365:sb_03
> > ->dma_sb_region_create:656:
> > ps3disk sb_03: First accessible region has index 3 start 25165848 size 
> > 52974312
> > ps3disk sb_03: s3da is a Hitachi HTS541640J9SA00 (38164 MiB total, 25866 
> > MiB for other OS)
> > ps3da:ps3da1 ps3da2
> > <-ps3_system_bus_probe:376: sb_03
> > ps3_system_bus_match:354: dev=3(sb_04), drv=6(ps3disk):miss
> > ps3_system_bus_match:354:dev=9(ioc0_03),drv=6(ps3disk):miss
> > loading ps3disk.ko module
> > insmode: error inserting '/lib/ps3disk.ko': -1 File exists
> > loading dm-mod.ko module
> > device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: 
> > dm-devel at redhat.com
> > loading dm-mirror.ko module
> > loading dm-zero.ko module
> > loading dm-snapshot.ko module
> > Making device-mapper control node
> > Making device-mapper control node
> > Scanning logical volumes
> >  reading all physical volumes, this may take a while
> >  No volume grups found
> > Activatiing logical volumes
> > Volume group "volgroup00" not found
> > Trying to resume from /dev/volgroup00/logvol01
> > usb 3-2: new high speed usb device using ps3-ehci-driver and address 2
> > unable to access resume device (/dev/volgroup00/logvol01)
> > creating root device.
> > Mouting 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, mouting 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.
> > usb 3-2: configuration #1 chosen from 1 choice
> > hub 3-2:1.0: usb hub found
> > hub 3-2:1.0: 4 ports detected
> > unmount old /dev
> > unmount old /proc
> > unmount old /sys
> > switchroot: mount failed: no such file or directory
> > Booting has failed.
> > kernel panic - not syncing: attempted to kill init!
> 
> -- Patrick Mansfield
>