I know this is from years ago but I have been working on this recently and finally solved the issue, bringing my SSD back to life.
Let’s start by defining the issue: it is a common problem with old SSDs using '''SandForce''' controllers. Because of incorrect instruction management, these occasionally freeze up and deny system detection. The only thing that you may see if a '''~30kb''' drive named '''SandForce{200026BB}''' , either in the '''BIOS''' or in the '''System Report'''.
What you have to do in order to solve it is pretty lengthy and complex, and you will not be able to save the files you have on your SSDs: it will all be gone. Having this in mind, I wouldn’t personally proceed unless you are very eager to bring your SSD back to life as a new drive.
Before starting this procedure, you can always try to forcefully issue some SATA wakeup commands to the SSD, by plugging it in a PC (You need a BIOS) and performing the following steps:
# Leave everything shut down for 2 minutes
# Boot and head straight to the BIOS, where you should see your device as '''SandForce{200026BB}'''
# Just wait on the BIOS screen for ~5 minutes
# Shut down and wait some more 2 minutes
''I have tried the above multiple times, it was not helpful so I had to reflash the SSD controller. In your case it might work, so it is preferrable to try it before destroying the contents of your drive irriversibly.''
If you are still willing to proceed, then, you will need to work on Linux ('''Fedora 32bits'''). The procedure consists in determining, retrieving and lastly correctly flashing a compatible firmware onto your SSD’s controller. As mentioned, it is a very lengthy procedure, and not very well documented at all. [link|https://computerlounge.it/how-to-fix-a-broken-ssd-the-infamous-sandforce-bug/#!|This] guide describes the steps in '''English'''.
Make sure that you operate the 32bits version of Fedora, and that you also have a free SATA port. USB adapters '''will not work''' and the proceduere won’t work on Fedora versions other than '''14.0 32bits'''.
I know this is from years ago but I have been working on this recently and finally solved the issue, bringing my SSD back to life.
Let’s start by defining the issue: it is a common problem with old SSDs using '''SandForce''' controllers. Because of incorrect instruction management, these occasionally freeze up and deny system detection. The only thing that you may see if a '''~30kb''' drive named '''SandForce{200026BB}''' , either in the '''BIOS''' or in the '''System Report'''.
What you have to do in order to solve it is pretty lengthy and complex, and you will not be able to save the files you have on your SSDs: it will all be gone. Having this in mind, I wouldn’t personally proceed unless you are very eager to bring your SSD back to life as a new drive.
Before starting this procedure, you can always try to forcefully issue some SATA wakeup commands to the SSD, by plugging it in a PC (You need a BIOS) and performing the following steps:
# Leave everything shut down for 2 minutes
# Boot and head straight to the BIOS, where you should see your device as '''SandForce{200026BB}'''
# Just wait on the BIOS screen for ~5 minutes
# Shut down and wait some more 2 minutes
''I have tried the above multiple times, it was not helpful so I had to reflash the SSD controller. In your case it might work, so it is preferrable to try it before destroying the contents of your drive irriversibly.''
If you are still willing to proceed, then, you will need to work on Linux ('''Fedora 32bits'''). The procedure consists in determining, retrieving and lastly correctly flashing a compatible firmware onto your SSD’s controller. As mentioned, it is a very lengthy procedure, and not very well documented at all. [link|https://computerlounge.it/how-to-fix-a-broken-ssd-the-infamous-sandforce-bug/#!|This] guide describes the steps in '''English'''.
Make sure that you operate the 32bits version of Fedora, and that you also have a free SATA port. USB adapters '''will not work''' and the proceduere won’t work on Fedora versions other than '''14.0 32bits'''.
I know this is from years ago but I have been working on this recently and finally solved the issue, bringing my SSD back to life.
Let’s start by defining the issue: it is a common problem with old SSDs using '''SandForce''' controllers. Because of incorrect instruction management, these occasionally freeze up and deny system detection. The only thing that you may see if a '''~30kb''' drive named '''SandForce{200026BB}''' , either in the '''BIOS''' or in the '''System Report'''.
What you have to do in order to solve it is pretty lengthy and complex, and you will not be able to save the files you have on your SSDs: it will all be gone. Having this in mind, I wouldn’t personally proceed unless you are very eager to bring your SSD back to life as a new drive.
Before starting this procedure, you can always try to forcefully issue some SATA wakeup commands to the SSD, by plugging it in a PC (You need a BIOS) and performing the following steps:
# Leave everything shut down for 2 minutes
# Boot and head straight to the BIOS, where you should see your device as '''SandForce{200026BB}'''
# Just wait on the BIOS screen for ~5 minutes
# Shut down and wait some more 2 minutes
''I have tried the above multiple times, it was not helpful so I had to reflash the SSD controller. In your case it might work, so it is preferrable to try it before destroying the contents of your drive irriversibly.''
If you are still willing to proceed, then, you will need to work on Linux ('''Fedora 32bits'''). The procedure consists in determining, retrieving and lastly correctly flashing a compatible firmware onto your SSD’s controller. As mentioned, it is a very lengthy procedure, and not very well documented at all. [link|https://computerlounge.it/how-to-fix-a-broken-ssd-the-infamous-sandforce-bug/#!|This] guide describes the steps in '''English'''.
Make sure that you operate the 32bits version of Fedora, and that you also have a free SATA port. USB adapters '''will not work''' and the proceduere won’t work on Fedora versions other than '''14.0 32bits'''.