eject should work after you do umount /dev/bdvd

AAAHHH!! Linux commands, who knew!

It turns out neither the power button nor the eject button work in the petitboot.

eject should work after you do umount /dev/bdvd

It turns out neither the power button nor the eject button work in the petitboot. I won't worry about it, just an extra step I need to do, not a complete deal breaker (I'd honestly rather deal with that then have to read those damn small codes on the discs!).

I'll ask around to see if I can move to a newer CFW.

Thanks again jamjam.

root@ps3-linux:/# mount /temp/petitboot/mnt/sda1 -o rw/remount
warning: can't open /etc/fstab: No such file or directory
mount: can't find /temp/petitboot/mnt/sda1 in /etc/fstab or /etc/mtab

If there's a problem with /etc/fstab I can't help, not overly qualified with linux. It could just be that the stick is no longer sda1, it might have changed (it can change just by unplugging and replugging). Or maybe you've said temp when it should be tmp (mine isn't setup so can't check).

edit:

Doubt it, haven't tried. To be honest as soon as I got it working I daren't mess with it further, the ps3 is on its last legs anyway and I don't want to push it over the edge.

So the eject button definitely doesn't work in PS3Linux. Not a huge deal, but it's really annoying to have to reboot after each dump.

As of this morning I am getting a new error message (third line):

root@ps3-linux:/# mount /temp/petitboot/mnt/sda1 -o rw/remount
warning: can't open /etc/fstab: No such file or directory
mount: can't find /temp/petitboot/mnt/sda1 in /etc/fstab or /etc/mtab

Another question that popped in my head this morning, am I able to move to a different CFW, like Rogero?

1. Is there a way to eject the Blu-ray from the drive so I do not need to go back into the PS3 OS (I notice the eject button doesn't work in PS3 Linux).

My eject button works fine on a fat. Try holding the eject button for 20 seconds, it should do an eject cycle.

Yes. Half the time I get that, I turn the ps3 off by holding the power button. I don't think it's anything to worry about, unless perhaps you have to reboot for every disc (I do them in batches).

I don't understand the question, so have some scattershot answers that might help

• It doesn't verify isos, it makes them useful by being able to decrypt them. The PS3 section stagnated for years because the dumps weren't usable, now if the disc key is present they are (decrypt and re-encrypt with PS3Dec).

• Currently the dats do not contain the key. What we have now is not the most automated way to do things, maybe something can be done in the future (like a small download with the disc key, or putting the disc keys in the dat)

• The metadata does not have a confirmation orb on it's page so technically does not need to be verified, although really it should be. Someone else can get the metadata with their disc to check it, or decrypt the image with the key on the redump page to check it.

root@ps3-linux:/# mount /tmp/petitboot/mnt/sda1 -o rw,remount
warning: can't open /etc/fstab: No such file or directory (I ignore this warning as it does show rw after the command)
root@ps3-linux:/# cd /tmp/petitboot/mnt/sda1/GetKey
root@ps3-linux:/tmp/petitboot/mnt/sda1/GetKey# ./GetKey 3Dump.bin big.pic >output.txt

Thank you all for the help! Now I have a few follow up questions.

1. Is there a way to eject the Blu-ray from the drive so I do not need to go back into the PS3 OS (I notice the eject button doesn't work in PS3 Linux).
2. When I do a "reboot" command the PS3 complains "The system was not turned off properly the last time it was used". Is this normal?
3. How will this be used to verify ISO dumps; Is there a way for the .dats to verify this info in ISO?

You'll know if something went wrong because it will say WARNING instead of SUCCESS at the end.

GetKey r2
Load keys
Test unit ready: return value of ioctl indicates success
Read pic: return value of ioctl indicates success
get dec key
  establish session keys:
    do send key: return value of ioctl indicates success
    do report key: return value of ioctl indicates success
    calculate session keys
    do send key: return value of ioctl indicates success
  get data
    do unknown e1:
    unknown e1 cdb: e1005400e1349bfeae77479b
    return value of ioctl indicates success
    do unknown e0:     unknown e0 cdb: e00034000dab640312a47c3a
    return value of ioctl indicates success
get_dec_key succeeded!

disc_key = 60b5bf3fa5567a56f389287ead01f251

disc_id = 00000000000000ff00020003XXXXXXXX
PIC:
10020000444901080000200042444f01
1101010000000000006fbbff00100000
006fbbfe000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
00000000

SUCCESS: Everything was correctly dumped.

edit: And you should write ./GetKey not GetKey (you need to execute by path, ./ means relative to where you are now, GetKey can't be executed like cd and ls because it's not in the PATH)

root@ps3-linux:/temp/petitboot/mnt/sda1/GetKey# GetKey 3Dump.bin >output.txt
/bin/ash: can't create output.txt: Read-only file system
/bin/ash: GetKey: not found

If I do a ls in the GetKey director it shows:
3Dump.bin   GetKey

So close I can taste it...and it tastes like victory!

cd /tmp/petitboot/mnt
ls

Some files are listed, one of which should be the usb stick (likely usb names are something like sda1 sdb1 etc). Try them all by going in and listing them until you find your stick. Then you just put a disc in and do this:

./GetKey 3Dump.bin >output.txt

This dumps the disc key, disc id and pic and puts it into file output.txt in the same directory as getkey. You could also grab the full pic if you'd like by doing this:

./GetKey 3Dump.bin big.pic >output.txt

output.txt is the same as before, what's new is big.pic, which is the full pic. It's not required by redump, but it doesn't take much to store it, and who knows it may be useful later.

But before you do any of that, you need 3Dump.bin and put it in same directory as GetKey (easiest is both in root of usb stick), get it by running a pkg as described in the guide.