F5F Stay Refreshed Hardware Desktop Error on SSD PS3111 during BIOS setup

Error on SSD PS3111 during BIOS setup

Error on SSD PS3111 during BIOS setup

D
Drayden_
Member
Find
181
05-12-2016, 04:11 PM
#1
I recently organized my cable setup and cleared out some space (definitely needed). Everything is back in place and I checked the BIOS to confirm everything works. My system has three drives: an NVMe SSD for booting, a 2.5 SSD as a secondary drive, and an HDD for storage. All are recognized, but when I view the 2.5 SSD in the BIOS it displays as PS3111 0.0GB. I’ve looked into the issue myself and many others on forums believe the SSD is dead or the controller failed. However, my drive works perfectly when plugged into an external enclosure. The problem arises when I connect it internally to my system, triggering this error. I tested the SATA cable in another setup with the SSD and it worked fine there. I also checked the SATA ports on my motherboard, which functioned correctly with the other drive. It seems the issue lies with how the drives interact together inside my system. If you have any advice or experienced similar problems, please share a solution—I’m really puzzled. Thanks!
Reply
Reply
D
Drayden_
05-12-2016, 04:11 PM #1

I recently organized my cable setup and cleared out some space (definitely needed). Everything is back in place and I checked the BIOS to confirm everything works. My system has three drives: an NVMe SSD for booting, a 2.5 SSD as a secondary drive, and an HDD for storage. All are recognized, but when I view the 2.5 SSD in the BIOS it displays as PS3111 0.0GB. I’ve looked into the issue myself and many others on forums believe the SSD is dead or the controller failed. However, my drive works perfectly when plugged into an external enclosure. The problem arises when I connect it internally to my system, triggering this error. I tested the SATA cable in another setup with the SSD and it worked fine there. I also checked the SATA ports on my motherboard, which functioned correctly with the other drive. It seems the issue lies with how the drives interact together inside my system. If you have any advice or experienced similar problems, please share a solution—I’m really puzzled. Thanks!

Reply
Reply