The current disc is empty or not recognized as an SACD, please re-insert.

[GoogleCodeExporter]

What steps will reproduce the problem?
1. successfully build any version of SACD-Ripper

2. install latest OtherOS+++ CFW 3.55 recommended for PS3 models with NAND:

* Filename: CFW355-OTHEROS++-22GB.PUP
* MD5 Hash: 0aed8e6a77e0a0aed8f41bcc51db3e8c

3. install SACD-Ripper

What is the expected output? What do you see instead?

SACD disc is inserted (i tried all SACD discs i have), but instead the 
following error message is displayed:

"The current disc is empty or not recognized as an SACD, please re-insert."

XMB (GameOS) recognizes the disc as SACD (both stereo and multi-channel) and 
can play it.

What version of the product are you using? On what operating system?

0.20, but it's the same with any older version - i go back to older versions 
from over one month

Please provide any additional information below.

also, installed "analysis_dump.pkg", but 2MB dumps created are just empty 
files: all bytes are 0 - checked that with hex editor.

Original issue reported on code.google.com by sheridan...@hotmail.com on 1 Jul 2011 at 11:09

[GoogleCodeExporter]

interesting issue. it seems the hybrid layer is selected by default on your 
PS3. you are the first person to report this. Sorry I need to ask as your 
probably did, you did re-insert the disc while SACD-Ripper was running didn't 
you?

I need to find the ATAPI call that selects the data layer.

Original comment by mr_wic...@hotmail.com on 2 Jul 2011 at 6:31

[GoogleCodeExporter]

Could you also attach sacd_log.txt after you've inserted a disc? that would be 
in the root of your USB disc/stick..

Original comment by mr_wic...@hotmail.com on 2 Jul 2011 at 6:46

[GoogleCodeExporter]

here is the content of sacd_log.txt:

17236112[0x1070090]: Initializing SPUs
17236112[0x1070090]: syscall sys_raw_spu_create...
17236112[0x1070090]: succeeded. raw_spu number is 0
17236112[0x1070090]: syscall sys_raw_spu_load: 
/dev_hdd0/game/SACDRIP01/USRDIR/sac_module.spu.elf
17236112[0x1070090]: succeeded. entry d0
17236112[0x1070090]: Establishing the interrupt tag on the interrupt PPU thread.
17236112[0x1070090]: ioctl_report_key1[45002901] ffffffff
17236112[0x1070090]: sac_exec_key_exchange (0xffffffff)

Original comment by sheridan...@hotmail.com on 2 Jul 2011 at 7:58

[GoogleCodeExporter]

this is a very strange log as "ioctl_report_key1" only executes on user request 
when the ripping process needs to start. I'm suspecting your binary that has 
been created is  corrupt, please google for a sacd-ripper.pkg that someone else 
has created, check that result, and report back.

Original comment by mr_wic...@hotmail.com on 2 Jul 2011 at 8:16

[GoogleCodeExporter]

using the analysis_dump tool, did you eject the disc in advance? It should be 
empty on startup and inserted when the analysis tool has started.

Original comment by mr_wic...@hotmail.com on 2 Jul 2011 at 8:18

[GoogleCodeExporter]

yes, i follow the on-screen instructions of analysis_dump tool and so the drive 
was empty on startup. anyway, i made another log and this time i got different 
output:

16908381[0x102005d]: sys storage_open 0 45002b01
16908381[0x102005d]: sys storage_read 8001002f 45002b01 0
16908381[0x102005d]: sys storage_close 0 45002b01

which is the same as the issue here:

http://code.google.com/p/sacd-ripper/issues/detail?id=11

but in that case OtherOS+++ CFW 3.55 wasn't use and that was the problem.

also, googled, downloaded and installed new sacd-ripper.pkg package with md5: 
7f4ed925da6ee667f06e23cf15c2d97b (not built by me), but without any change.

Original comment by sheridan...@hotmail.com on 2 Jul 2011 at 8:46

[GoogleCodeExporter]

Ok, now we're getting somewhere. The 8001002f error means it hasn't properly 
patched the necessary syscall to reset the BD drive. Which means there is 
something wrong with the firmware that has been used.. 

Original comment by mr_wic...@hotmail.com on 2 Jul 2011 at 8:57

[GoogleCodeExporter]

I've installed the normal 3.55 CFW (5c8e202e2a405f3b28a6bf10db4e9c0b) moments 
ago, SACD-Ripper runs just fine. I advice you to do the same. Where did you 
find the information the 22GB is there for the NAND models?

Original comment by mr_wic...@hotmail.com on 2 Jul 2011 at 9:19

[GoogleCodeExporter]

i don't see much options then, because i installed latest OtherOS++ CFW 3.55 
release from June 7, 2011, as i mentioned it's :

* Filename: CFW355-OTHEROS++-22GB.PUP
* MD5 Hash: 0aed8e6a77e0a0aed8f41bcc51db3e8c

which i believe is the second release with OtherOS support for PS3 models with 
NAND and AFAIK the only different from the first release is that it uses 22GB 
partition for OtherOS instead half of the hard disk. 

so, as i can see it, there is only one option left to try - some of the older 
OtherOS+++ CFW 3.55 releases that support OtherOS functionality only for PS3 
models with VFLASH. anyway, i will try that and report back in few hours. in 
any case it's very interesting what inside OtherOS++ CFW 3.55 release i'm using 
could possibly trigger the issue, because if not all OtherOS++ CFW 3.55 
releases are good then we need to at least create list of working PUP files 
with their MD5 Hash.

Original comment by sheridan...@hotmail.com on 2 Jul 2011 at 9:20

[GoogleCodeExporter]

First try the 'latest' normal CFW with (5c8e202e2a405f3b28a6bf10db4e9c0b), 
that's what I'm running as we speak..

Original comment by mr_wic...@hotmail.com on 2 Jul 2011 at 9:24

[GoogleCodeExporter]

my information about "*22GB" version is from discussion directly with the 
developers on Gitbrew IRC channel that i read some time ago - many people 
complained the initial version, which added NAND models support allocates half 
of the hard disk size for OtherOS installation and that's why they changed it 
to partition of 22GB. it's even more interesting that you confirmed PUP with 
MD5 of 5c8e202e2a405f3b28a6bf10db4e9c0b is working, because it's supposed that 
the only difference with "*22GB" version is half disk size versus 22GB for 
OtherOS installation. anyway, i'm going to install the same PUP as you did and 
we will see...

Original comment by sheridan...@hotmail.com on 2 Jul 2011 at 9:31

[GoogleCodeExporter]

ok, thank you for that information. I will try the 22GB as well, and let you 
know how it works for me. There should indeed be no difference at all!

Original comment by mr_wic...@hotmail.com on 2 Jul 2011 at 9:34

[GoogleCodeExporter]

confirmed - it's firmware fault:

* Filename: CFW355-OTHEROS++-22GB.PUP
* MD5 Hash: 0aed8e6a77e0a0aed8f41bcc51db3e8c
* Status: BAD for SACD-Ripper

* Filename: CFW355-OTHEROS++.PUP
* MD5 Hash: 5c8e202e2a405f3b28a6bf10db4e9c0b
* Status: GOOD for SACD-Ripper

i've just changed the firmware and SACD-Ripper stated to work fine. it looks 
like that information is essential, because latest OtherOS+++ CFW 3.55 PUP file 
has something that makes it incompatible with SACD-Ripper. 

Original comment by sheridan...@hotmail.com on 2 Jul 2011 at 11:33

[GoogleCodeExporter]

Good that you've got it working. I would need to find out why that 22GB 
firmware is not working (probably something to do with LV2 patching functions 
missing..)

Original comment by mr_wic...@hotmail.com on 2 Jul 2011 at 1:29

[GoogleCodeExporter]

actually, i've already done some investigation in that direction - i used 
PS3MFW to 'unpack' (i'm not sure if that is the correct word) the PUP files and 
compare with hex editor and it seems to me 22GB firmware is missing: "Allow 
access to all SS services (Needed for ps3dm-utils)" patch. i guess it was 
removed in that newer 22GB version, because of the long discussion it causes 
game incompatibility - the famous trophy error 80010505 with OtherOS++. 
however, it seems it's necessary for SACD-Ripper to function properly. so, it's 
a trade-off - if you need to backup SACDs you need to install firmware with 
which most games can't work (i'm talking about original games you purchased and 
not illegal copies - i don't know about them) and vice-versa if you install 
firmware with which games can work then SACD-Ripper is not working. however, 
that's not real issue since you can switched between those 3.55 firmware 
releases relatively easy, but it's good to keep it in mind. 

Original comment by sheridan...@hotmail.com on 2 Jul 2011 at 1:41

[GoogleCodeExporter]

thanks for checking! you've saved me time by not having to dive into this. too 
bad the SS services patch is causing this 80010505 error..

Original comment by mr_wic...@hotmail.com on 2 Jul 2011 at 1:48

[GoogleCodeExporter]

I'll hereby close this issue..

Original comment by mr_wic...@hotmail.com on 2 Jul 2011 at 1:48

• Changed state: WontFix