Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

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. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Marnault

  1. Well I got my drive back! Thank you to everyone who has posted info here, and special thanks to the original poster of the guide. I had the BSY error with my 1TB Seagate 7200.11 340AS, i used a FT232RL which I was was able to pickup locally from here: http://www.hvwtech.com/products_view.asp?ProductID=925. It worked flawlessly even though I had to substitute jumpers and headers for thumbtacks with a wire soldered to it, it didn't look pretty but it worked. As an added bonus I didn't need to hook up the 3.3/5 Volt, as it was powered through the USB, it was definatly worth the $15! At first after the spin down when I entered the command for the spinup I got: "F3 2>U (insert clicking noise here & me panicking) Error 1009 DETSEC 00006008 Spin Error" (it also said some amount of time like 19s and i think, 2 read and 2 write errors, but missed copying the whole error message) I was trying the card trick, which worked for me just keeping the motor separated from the PCB. I found the issue was that the PCB wasn't screwed back in tight enough and wasn't making proper contact. So if anyone else has that error when spinning up make sure the pcb is nice and tight. So fortunately it was a simple fix. After the last step I popped the drive back in my computer and it fired up like nothing ever happened, all files seem to be there and intact. Currently copying everything from the drive in case it wants to brick it self again, but hopfuly new firmware will prevent that. So once again a big THANK YOU to everyone who has contributed to solving this issue.