Description of problem:
I installed F8 on my PS3. Once all packages were installed I was asked to reboot
the system, which I did. Upon reboot, I got this:
Red Hat nash version 6.0.19 starting
Unable to access fesume device (LABEL=SWAP-ps3da2)
mount: could not find filesystem '/dev/root'
setuproot: moving /dev/ failed: No such file or directory
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install F8, using a custom partition layout, on PS3
The final installation steps (configuration) fail, as the system doesn't reboot.
(I read somewhere that with F8 partitions are required to be labeled. I can't
remember having explicitely specified labels when creating my partitions. FWIW.)
How did you partition the system?
/sbin/blkid confirms that I have three partitions (ps3da[1,2,3]), with labels
"/", "swap", and "/home". I partitioned the disk during installation.
I'm not sure why the boot process is looking for a "SWAP-ps3da2" label, and what
the failure to "find filesystem /dev/root" means. (/dev/root exists on the "/"
partition, and is a regular block-device read/writable by root.
Sorry, I spoke to quickly. My swap partition does in fact have a "SWAP-ps3da2"
label. (I misinterpreted the "TYPE" field in my previous post.)
That looks like everything is right. Do you see the ps3 disk module getting
loaded prior to that?
I'm not sure. However, if, at the kboot prompt I type "linux root=/dev/ps3da1"
everything works fine. This makes it sound as if the problem is related to the
way the partitions are by default addressed in the boot loader. (By the way, I
was looking for the kboot.conf file in /etc/, but couldn't find it.)
(Someone on irc://irc.oftc.net/cell just suggested the fact that I don't have a
/etc/kboot.config and the boot problems might be related. Apparently, a
'builtin' kboot.conf file gets used of no /etc/kboot.conf file was found.
And indeed, "cat //etc/kboot.conf" on the kboot prompt does print some content...)
So, may be the bug is that my F8 installation didn't create /etc/kboot.conf ?
Can you try installing F9 to see if you run into the same problem?
The information we've requested above is required in order
to review this problem report further and diagnose or fix the
issue if it is still present. Since it has been thirty days or
more since we first requested additional information, we're assuming
the problem is either no longer present in the current Fedora release, or
that there is no longer any interest in tracking the problem.
Setting status to "CLOSED: INSUFFICIENT_DATA". If you still
experience this problem after updating to our latest Fedora
release and can provide the information previously requested,
please feel free to reopen the bug report.
Thank you in advance.