I have some scan results here from past couple of days which I've not posted yet ... I have also (compressed - each between 2 and 2.5 MB) full images of drives in case you'd like to compare / view results. So - even if you don't want to fiddle with you PS3 drive you can still participate ... :smilew
I've used 2 of the smallest hard drive the PS3 can still handle - 2.6 GB & 3.2 GB. It's optimal due to the faster scanning and imaging and less disk space to go through when you're looking for some specific signatures / data.
I've performed various tests resulting in different images / scan results. Each disk went through 5 stages described bellow:
1. Wiped / zeroed - called
Init0 (there is no scan neither image as far as it's simply full of zeroes).
2. Initialization / formating by PS3 up to the prompt "Press x to restart". At this point the PS3 was powered off by the back power switch! (Of course AFTER all the disk activity finished) - called
Init1.
3. The same like in point 2 but this time the PS3 was shut down using the front panel power button. There is definitely some disk activity AFTER the power button is pressed but both default scans shows the same results so we need to compare the whole images to seek differences - called
Init2.
4.The PS3 is restarted using the x as prompted and SWITCHED OFF at the moment when the XMB shows up and the start up sound finish. It needs to be BEFORE the ps3 will connect online - I've also disconnected the network cable for that - called
Init3.
5. The PS3 is restarted using the x as prompted and let to connect online then switched off using the front panel power button - called
Init4.
There are clear differences between Init2 and Init3 as well as between Init3 and Init4.
Also - apparently due to the limited space on the hard drive - the PS3 will actually (despite the initial formating without any errors) not start up correctly with 2.6 GB hard drive ... :Important It will "fiddle" with the disk for a while (which results in even longer scan results in Init3 than for 3.2 GB drive) and then simply beep 3 times and shut itself down to "red flashing mode" ... :eek2
This is also the reason why there is no Init4 scan result for 2.6 GB drive.
>HanSooloo:
Another couple of additions to scan program:
1. Can you implement the
-c command line from my last version?
2. Also - it would be useful to include in the results file the first 16 bytes of every reported block (especially when you're looking for NOT matching signatures).
3. And finally - as already mentioned before) - the size of the drive.
I'll finish the scan of remaining drives and post result here as well. As agreed it will be the "Init2" type.
Then I'm heading toward filling up the drives (mainly the smallest ones) with some pre-defined files and I'll be looking for them in the images.