KBOOT no root fs was found after install PS3 UBUTU 9.04 alternate powerpc Jaunty release

Bug #376674 reported by LostSoul
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu PS3 Port
New
Undecided
Jezzus

Bug Description

I have seen this bug reported for different releases of UBUNTU, but not for the Jaunty ubuntu-9.04-alternate-powerpc+ps3. Sadly, I'm not a linux guy... yet. This is my first experience with linux in a home application (Use it at work, but I have all the commands I need right in my manual)

The odd thing is that I have successflully loaded UBUTU once or twice, but then when I reboot for whatever reason, this is what I get.

mount: mounting none on /dev/pts failed
/init /init:923: dropbear: not found
Ubuntu Ps3 KBoot Loader.

No defualt root fs was found, or one was found and it didn't containg a message = congig file.

If no rootfs was found. you can enter the shell here with 'sh'. Exiting will return you to this promt. In the shell you can mount your rootfs as
/mnt/root/.

Reasons this may have happened include:
-No drive with a rootfs was actually found.
-your rootfs does not have the correct volume label of "/"
-Your rootfs is corrupt (use the rescue cd to fix this).

Kboot:_

I have treid at least 5 different "fixes or workarounds" that were vastly different in the commands used. The last one I tried was:

e2lable /dev/ps3da1 in both KBOOT and Shell

I even tried using petiteloader .2, but all I got was a pretty blank gui with no options other than resolution settings and rebooting. Someone suggested installing KBOOT 11. That didn't work either.

I have redownloaded 3 times, reburned on new discs 4 times, and reinstalled 6 times. I must say I'm at a loss. Any suggestions?

Revision history for this message
Arnaud Jeansen (ajeans) wrote :

I have not seen this bug in Jaunty, so before anything else, can you please:
- Check that you followed the steps described here to do your install
http://psubuntu.com/wiki/InstallUbuntu (this is for XUbuntu 8.10, but works fine for Ubuntu 9.04)
- Make sure your PS3 is using the latest firmware

Thanks

Revision history for this message
LostSoul (glschiller) wrote :

Yes I did follow that guide. It's pretty straight forward, but I did use it. I'm wondering if there is a manual way that I can force it to boot up? I have tried a couple of approaches, but I'm open to a step by step "if/then" approach if anyone has any ideas.

Revision history for this message
LostSoul (glschiller) wrote :

I finally found a workaround that seems to work so far.

1. I installed the experimental petitboot using a thumb drive
2. Rebooted in XMB with DEFAULT OS
3. I downloaded, burned, then inserted pdaXrom-ng-ps3-20090312 (Live boot disk)
4. Rebooted (Yes, I know it would seem that this was unnecessary, but I did it anyway)
5. In the petitboot GUI, I navigated to the livecd and chose the 1080p option
6. Screen went black, I freaked out, threw things around the room, cursed like a sailor (I'm a Marine), and rebooted
7. Back in the petitboot GUI now, I see my Linux OS and I booted to it...
8. SUCCESS!!!!! I know this is not the way it was intended to work, but it's acceptable to me until someone can figure the real solution.

In closing, I would not consider this "fixed" I would say that this might work for others have the same frustrating issues that I was having.

OH!!! I forgot to mention that I'm on the 80 gig PS3 upgraded to 320hd running the latest Sony update.

Revision history for this message
Hugo D (defpy) wrote :

It usually happens when you force a shutdown using the power button or ctrl+alt+del. Just power off the system completely or boot to game-os, then select otheros again.

It's been like this for the past versions.

Revision history for this message
kgoosie (kgoosie) wrote :

I have the same problem as LostSoul but I tried installing 8.10 twice. I first tried the server install and then tried the alternate. Alternate install worked for a minimum of a few hours. It booted up fine after restart. I shut it down using the proper shut down procedures from within Ubuntu. I tried to boot up this morning and recieved same error as before, LostSoul's first post. So, if anyone know of a solution that would be awesome.

Revision history for this message
Arnaud Jeansen (ajeans) wrote :

@kgoosie:
- Did you keep the standard bootloader (kboot) ?
- Did you keep the standard filesystem type (ext3)
- No changes to partitions after install (resizing, reordering, ...)?

If the answer is no to all three, your best shot is to open a bash shell from the boot loader and look at device nodes (if you need instructions on this, I could look it up tonight on my PS3).

Revision history for this message
kgoosie (kgoosie) wrote :

@Arnaud Jeansen

-Did you keep the standard bootloader (kboot)? Yes
-Did you keep the standard filesystem type (ext3)? Yes
-No changes to partitions after install (resizing, reordering, ...)? No

Right after the install the system restarted and everything booted up normal. I tried restarting this morning and received the same message as LostSoul.

Revision history for this message
Arnaud Jeansen (ajeans) wrote :

Sorry I couldn't reply before.

Can you, from kboot get into busybox (type 'sh' at the kboot prompt) and check a few things
1) is your root filesystem mounted read only or is it not mounted at all:
$ cat /proc/mounts
2) Do you have the hdd nodes available on your system
$ ls /dev/ps3da*
3) Finally, what is the label on the root partition
$ e2label /dev/ps3da1

If you can provide the output of these three commands, it might help me see what is wrong for your config.

Thanks

Revision history for this message
Aaron (poolroom) wrote :

Hello,

I've just experienced this same error and managed to get the system working. I'm not a kboot expert but my take on this is, by default, Ubuntu 9.04 is installing itself on a LVM partitioned drive and kboot does not support LVM.

So the fix for me was to:

1. Re-install Unbuntu
2. Choose Manual Partition at the disk partitioning stage (don't choose Guided Partition)
3. Create a partitioning scheme, using filesystems, that kboot can read.
4. Continue the install as normal.

The drive layout I choose was:

/dev/ps3da1 = Primary partition, 10.2 GB, ext3 filesystem (created at end of drive space)
/dev/ps3da2 = Extended partition
/dev/ps3da5 = Logical partition, remaining space (about 522 MB) swap filesystem.

After going through the install the system rebooted and Ubuntu is working.

Note that the dropbear error still occurs at the kboot stage, I have no thoughts on that. Also kboot has a long timeout (100) so when you reboot, be sure to press <ENTER> at the kboot prompt to get it to boot Ubuntu straight away.

For the record my PS3 has an upgraded hard drive (Samsung HM500LI 500GB). I mention this because I have seen others mention it in relation to this problem. However I don't think it's a drive or size recognition issue causing the problem, just a filesystem support mismatch with kboot.

I hope this helps.

Aaron

Revision history for this message
MHAQS (mhaqsb) wrote :

The only reason for the PS3 to show that error is because PS3 can't read ext4. Format your drive to ext3 and reinstall ubuntu.

Revision history for this message
RAul (slugbug) wrote :

Thanks Aaron. I know you posted this 2 yrs ago! but I just installed Ubuntu 10.04 onto my ps3! works great!
I made my primary and swap file just as you said.
However, make sure you leave the cd in the cd rom drive and your golden!!

Revision history for this message
Aaron (poolroom) wrote : Re: [Bug 376674] Re: KBOOT no root fs was found after install PS3 UBUTU 9.04 alternate powerpc Jaunty release

Hi RAul,

Thanks for the email. It's good to know I've helped others with this problem.

Two years already hey! Doesn't feel that long. ;)

Aaron

On 12/10/2011, at 6:38 PM, RAul <email address hidden> wrote:

> Thanks Aaron. I know you posted this 2 yrs ago! but I just installed Ubuntu 10.04 onto my ps3! works great!
> I made my primary and swap file just as you said.
> However, make sure you leave the cd in the cd rom drive and your golden!!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/376674
>
> Title:
> KBOOT no root fs was found after install PS3 UBUTU 9.04 alternate
> powerpc Jaunty release
>
> Status in Ubuntu PS3 Port:
> New
>
> Bug description:
> I have seen this bug reported for different releases of UBUNTU, but
> not for the Jaunty ubuntu-9.04-alternate-powerpc+ps3. Sadly, I'm not
> a linux guy... yet. This is my first experience with linux in a home
> application (Use it at work, but I have all the commands I need right
> in my manual)
>
> The odd thing is that I have successflully loaded UBUTU once or twice,
> but then when I reboot for whatever reason, this is what I get.
>
> mount: mounting none on /dev/pts failed
> /init /init:923: dropbear: not found
> Ubuntu Ps3 KBoot Loader.
>
> No defualt root fs was found, or one was found and it didn't containg
> a message = congig file.
>
> If no rootfs was found. you can enter the shell here with 'sh'. Exiting will return you to this promt. In the shell you can mount your rootfs as
> /mnt/root/.
>
> Reasons this may have happened include:
> -No drive with a rootfs was actually found.
> -your rootfs does not have the correct volume label of "/"
> -Your rootfs is corrupt (use the rescue cd to fix this).
>
> Kboot:_
>
>
> I have treid at least 5 different "fixes or workarounds" that were vastly different in the commands used. The last one I tried was:
>
> e2lable /dev/ps3da1 in both KBOOT and Shell
>
> I even tried using petiteloader .2, but all I got was a pretty blank
> gui with no options other than resolution settings and rebooting.
> Someone suggested installing KBOOT 11. That didn't work either.
>
> I have redownloaded 3 times, reburned on new discs 4 times, and
> reinstalled 6 times. I must say I'm at a loss. Any suggestions?
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-ps3-port/+bug/376674/+subscriptions

Jezzus (jurien33)
Changed in ubuntu-ps3-port:
assignee: nobody → Jezzus (jurien33)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.