PS3 Odd behaviour after SSD upgrade

Good afternoon, friends

I'll explain in as much relevant detail as I can, but I'll also put a TL;DR at the bottom.

I've tried my best to resolve this on my own, but it seems it's time to ask for help. I have a CECH-25XX running Evilnat Cobra 4.70 on its current hard-drive. There was a sale recently on SSDs in my area and I got an ADATA SU630 480GB to give the console a little upgrade. I didn't need anything backed up off the hard-drive that was already in, so I just popped it out, put the SSD in, put a new PS3UPDAT.PUP on a FAT32 MBR formatted flash drive and turned the PS3 on.

Here's where the odd heaviour begins - at first, it would simply refuse to accept the SSD. It'd turn on, stay on a black screen for up to a full minute, then spit out an error saying:
"Cannot start.
The appropriate system storage was not found."

I read a bunch online and some people were saying that the PS3 can be a little iffy with brand new storage, so I used a SATA to USB adapter to format it (using fat32format gui, and rufus on 2 separate occasions). fat32format didn't do the trick, but once Rufus was explicitly told to convert to MBR not GPT, the PS3 recognised the SSD and gave the usual error that there's on OS on there. Great - I went through the usual SELECT+START installation process and all went well. The progress bar gets to 100%, the system restarts as usual, but then spits out the same error as above about appropriate system storage not being found. What's really odd is that if I restart it a bunch of times, it recognises it without issue and will go through the install (I've tried a bunch of CFWs and OFWs), but once it restarts afterwards - error.

I tried booting into recovery mode, which only works about 50% of the time. Once I successfully booted into that, I tried pretty much all the options there one by one, nothing helped.

The SSD is seated well in the slot in the PS3 and I've checked it for any errors on my PC - nothing unusual was found, it works as expected. I'm kind of lost as to what to even try next. If I plug in my old HDD now, it works completely fine as if nothing's ever happened.

I'd appreciate any input whatsoever. Thanks guys.

TL;DR: PS3 won't accept new SSD, occasionally detects it as it should, but if any firmware install is attempted, it'll go through successfully, restart and stop recognising it once again.
 
How odd is that I've used adata 240gb no problems, I would instal an OS on it and run it for abit with a fair few reboots to see if issue arrives on pc, I've never had issues with ssds upto 1tb so it's definitely a thinker lol
 
For unknown reasons, some SSDs works fine, some doesn't. Logic structure corruptions randomly appears on some.

And parallel situation to it is that for some really odd and also unknown reasons, some devices (HDD/SHDD/SSD) aren't recognized until user set FAT32 partition on MBR. It is ridiculous because PS3 fw not using it for internal drive, instead using completely different structure (custom partition table, various of partitions, encrypting them etc. etc.) so MBR is for her just empty drive. But You are not first who claims that. Very strange.

You can do nothing about it, nothing but use another device at the moment.
 
I've come back with a BIG update!!

It seems it was a skill issue after all. I wanted to reply to the thread and give an update in case people find this in the future and it potentially helps. The issue in my case specifically was that when wiping the SSD and connecting it through the SATA adapter, I'd initialise it with MBR (that's okay), but then I'd autopilot and create a new partition from all the empty space. It's such a default thing I do that I didn't even consider it a step that could be changed, but after trying for what felt like the 10th time - I got to that step and it hit me like a truck.

Just to be sure, I used DISKPART in CMD and the clean command to completely wipe the SSD. I then initialised it with no partitions on it, just empty space. I proceeded with the installation on the PS3 as per usual and I got to the actual proper firmware installation! It finished in about 3 minutes and after an extremely tense restart......

I got the same error.

I was a little sad, but I thought 'Alright, at least we have some progress!'. I restarted the console and...

...it just boots into the OS. And everything's fine? I've been using it for 2 days now and I did get that weird error only one time afterwards, the first time I used ReactPSN, but it's basically been smooth sailing ever since. I don't know what to say, this has to be the most temperamental system I've ever used, but I'm glad it worked out in the end.

Thank you for the replies!
 

Similar threads

Back
Top