PS3 My PS3 isn't booting after being off for a long time

Psycho77

Forum Noob
Hi, guys! So I bought a used PS3, put it a Evilnat CFW and now when it's off for some time, it just doesn't boot even in safe mode. I can only boot it normal when I unplug the power and wait 30 seconds and then boot it in safe mode. Some curiosity that I noticed is that every time that this happens webMAN gets invisible or uninstalled and simply don't work until I reinstall it. I'm really eager to play some games in my PS3, but this problem is becoming annoying. I didn't find some other case in the internet, so if you can help, I'd be so thankful. Thanks in advance.
 
I would start with the hard drive
There's a way to verify the hard drive? I don't want to wipe off everything without knowing for sure that is the hard drive. I would have to download everything back and make a backup of my save files, it seems like a pain in the ass
 
HDD and PSU
I just plugged my hdd into my computer and checked with CrystalDiskInfo and my hdd is healthy. When i have time i'm gonna test the PSU but is there any chance that the fault is the cfw? I made another discovery too, it's not some type of procedure that turns on the ps3 when it's frozen, it's more like a random thing? idk. i really just wanted to play in the ps3 after a day of work...

Wiping a bad HDD won't fix anything. @Ganjo told you to try a different HDD.
Unfortunately i dont have another hdd to test, but i tested with crystaldiskinfo and was healthy
 
Last edited by a moderator:
I just plugged my hdd into my computer and checked with CrystalDiskInfo and my hdd is healthy. When i have time i'm gonna test the PSU but is there any chance that the fault is the cfw? I made another discovery too, it's not some type of procedure that turns on the ps3 when it's frozen, it's more like a random thing? idk. i really just wanted to play in the ps3 after a day of work...

CFW has already been tested a lot, so it's not expected to be the main cause here. If you want to rule that out, try downgrading to Rebug 4.84.

Unfortunately i dont have another hdd to test, but i tested with crystaldiskinfo and was healthy

You must try another HDD to rule out if the SATA port or the controller is damaged.
 
So, CrystalDiskInfo tells you about the SMART info and failures. A majority of the time a block just takes longer to access but it hasnt been marked as bad. The system freaks out because it cant get the data it needs. Normal access times are under 10ms a slow block can take a second or more.

You can download Victoria to do a surface scan. Just search Victoria HDD or Victoria for windows. Another option is MHDD on ultimate boot CD or WHDD if you have a linux box
 
Back
Top