MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically.
@jaclaz: Thank you for the link. It doesn't tell me anything I didn't already read over the last 4 weeks of trying to solve this issue. Not being of a highly technical profession (IT, Programming, etc.) I came here looking for someone to clarify MY specific set of variables and advise me if they had anything to do with the two known issues. Lack of spin and beeping have been mentioned on various other sites as "possibly" being related symptoms. I registered here to list my progress (and failure) for advice as the members of this forum appeared more mature than most others. Please take a moment to look over http://www.overclock.net/hard-drives-storage/457286-seagate-bricked-firmware-drive-fix-pics-5.html starting with post #48. jroymd's situation sounds the same as mine. Thoughts? Thanks MSFN for the opportunity to seek aid. You have a nice community here
ST31000333AS Firmware: SD35 No spin. Beeping Sound. I can terminal to the drive but fail to make any headway beyond spin down with the board physically separated from the drive. Plz help Update: ASCII Diag mode F3 T>/2 F3 2>Z Spin Down Complete Elapsed Time 0.106 msecs F3 2>U And the beeping returns It's been over 3 minutes and nothing new has popped up in my terminal session. Thoughts? Update 2: Finally something popped up and the drive stopped beeping: DiagError 00006008 Spin Error Elapsed Time 6 mins 58 secs R/W Status 2 R/W Error 84150180 Update 3: My drive NOW appears on Seagate's list of needing a firmware update (It wasn't on the list when I checked the other week). I downloaded the exe which caused XP to restart. The install failed because it couldn't detect my drive which had resumed beeping as soon as the computer started powering up. The only good thing to come out of the attempt was that with a SATA data cable connected at the time, the computer now showed the brick under Device Manager. It showed up as a 0mb drive which I believe is the other plague affecting these hard drives. Regardless, I tried to input the m0.2,2,0,0,0,0,22 command as show and was greeted with LED:blah blah blah error we all know and love. I removed the power from the brick to make it stop beeping so I could reestablish telenet communication but that only caused the drive to drop out of Device Manager. I'd welcome a prescribed course of action as I'm afraid my attempts could really kill this drive or hurt my pc. Thanks