I downloaded the boot CD from the same Seagate Support site above, burned it to disk, and tried it out. To save both me and my gracious host (who’s starting to suspect my computer-fixin’ skills now) some time, I decided to try the boot CD method, rather than pounding my head trying to see why the updater was lying. And in fact, this particular drive still reported firmware SD15, the broken one. Despite its claims, if you were on a stock setup Dell T5400 (or perhaps other models as well), this will prove that the updater is a lying scumbag. #Crystaldiskinfo says ssd has tens of thousands update#At the end of the process, it will report “firmware downloaded” and “SUCCESSFUL” or some variant thereof, and automatically reboot back into Windows.Īt this point, I advise you to use the SeaTools utility to verify that the firmware update actually applied. non-Seagate, non-Barracuda, etc.) drives, but it’ll still try them out first. To its credit, it’ll skip the non-qualifying (i.e. #Crystaldiskinfo says ssd has tens of thousands Patch#It will automatically reboot to a Seagate Loader screen, which attempts to apply the patch to all eligible SATA drives. The firmware updater will give a bunch of scary warnings and then reboot the machine. In fact, it took 3 hours of my life to find out just how deep this rabbit hole goes. I popped in the drive, fired up Windows XP, downloaded the Windows-based Firmware Update Utility, double-clicked, and thought it was the (triumphant) end. Since this thing can run two drives at once, I can use the first method (a Windows-based firmware updater), though I burned a boot CD for the second method just in case. The fellow owns a nice if aging Dell Precision T5400, which comes with two SATA bays (so I don’t have to inflict undue harm onto the existing system). Half a year passes, and I finally find a sucker good friend who’s gullible awesome enough for me to try this procedure on his machine. Sadly, most of my friends who still own desktops would not trust me that far. I have to find a desktop, open it up, jam this baby in (possibly in place of the existing drive if there’s only one bay), update the firmware, and put everything back together. I asked whether they would handle a mail-in repair, given that I have no easy access to such a desktop. That makes technical sense - but of course, it doesn’t work for me. It must be plugged into an internal SATA controller in order to update the drive.įair enough. Unfortunately, due to the nature of firmware updates and the way external drives work, the firmware update program cannot directly communicate with the drive in the manner it needs to in order to be able to upload the new firmware to the drive. In communication with Seagate support, a representative confirmed that for those of us without a desktop tower that has a SATA bay, we’re hosed: #Crystaldiskinfo says ssd has tens of thousands install#Seagate did in fact issue a firmware update - SD1A - that supposedly addressed this issue, but of course, there’s one catch: you can’t install the firmware through an external drive enclosure. I had the unfortunate experience of buying such a hard drive - the ST31000340AS - as a scratch disk for my main machine, a MacBook Pro with a mere 240 GB internal drive (a pre-unibody revision, where the HD is insanely difficult to replace). So perhaps you have heard of Seagate’s little manufacturing issue with its internal 3.5-inch Barracuda 7200.11 1TB drives a while back - namely, that some drives shipping with SD15 firmware are dying horribly. If the Seagate patcher doesn’t work, make sure to use Legacy mode on SATA in the BIOS, instead of the more modern AHCI mode. #Crystaldiskinfo says ssd has tens of thousands upgrade#TL DR: If you’re applying firmware upgrade SD1A to Seagate drives, you need to double-check the firmware actually applied properly.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |