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 arman95

Profile Information

  • OS
    none specified
  1. The "basic error" (besides the various attempts you made - particularly erasing the G-list), is/was to assume that an unbricked disk: still has a perfectly functional filesystem can still boot a "complex" OS like a NT one as it did before the bricking Both the above are gratuitious assumptions. The whole point is WHY did it "brick itself" originally, if it bricked because of the original issue with the log entry, then those assumptions may be correct, if it bricked itself for any other reason those are VERY unlikely to represent reality. The only thing that you can do (and that you should have done BEFORE attempting booting from the disk and before attempting accessing files on it's filesystem) is to image the disk on another disk (you will need a slightly larger disk, NTFS formatted (if using Windows) or EXT3/4 formatted (if using Linux) or clone it to a similarly sized disk, surely functional. You would normally use datarescuedd (Windows) or dd_rescue or ddrescue (Linux) and try to image the whole disk, if needed in "chunks". Once the filesystem has been transferred (hopefully successfully and the whole of it) on a surely functional media, then you start attempting recovery of the filesystem (if possible) or recovery of the files in it (still as possible). If you need help in doing the above, please start a new thread, as once the disk is not anymore BSY or LBA0, it exits the scope of the present thread. jaclaz Dear jaclaz, thank you for your answer! Seems like you are the only person who is still helping in this thread! Maybe I should explain what happened first.. On a night I turned off my computer... In the next day I came back home and whoops, my drive was not shown in BIOS! And then everything happened like I wrote earlier.. Now back to my drive.. The main confusing part is that, first my drive will not shown in the bios (everytime) but when I restart over CTRL+ALT+DEL than it will shown up.. I really don't understand that.. And now I started the other drive, which is working.. But in the device manager is not shown any other drive.. What now? I really don't know what to do.. Please help! Thanks much! Kind regards Arman!
  2. Dear MSFN Users, I have also some of these very awesome piece of sh** hard drives.. Now I have first swapped my PCB, but with a Firmware Swap. That means that I have my EEPROM chip resoldered to the new Board. But then I noticed, it is not the Board maybe its the BSY Bug! Soo.. Then I bought an CA-42 cable and followed this tutorial: I noticed after that, nothing.. Still in the BIOS was shown nothing.. I pressed CTRL+ALT+DEL to restart and then abrakadabra.. There it is! (It is kinda confusing me so much) So I have boot it finally up. After a quite while, I noticed, that it was veryyyyyyyyyyyy slow! And then I thought it has stuck on the boot process, so I shut my PC down and start it again.. And then again, in the BIOS was nothing -.- So after a quite while I noticed that thing here, the G-List step! So I tried the whole BSY fix with the commands in this thread again.. Still same s*** with BIOS and CTRL+ALT+DEL! Now it does not even boot, it stucks after a while and there is written an Windows 7 Boot Load Error! Then I thought hmm maybe some files are corrupt, let's try a Live-CD of Ubuntu! So it boot after a quite while finally up and the drive was also shown in Ubuntu but when I try to open it over Nautilus I get the Error: Cannot access on it because it is in use.. Or kinda like that error.. So I start again.. Searched and searched.. Nothing.. In the end I also tried that Tutorial again: http://www.mapleleafmountain.com/seagatebrick.html After that same problem.. Nothing happened... I'm quite tired.. I was sitting here now 6-7 hours just for fixing it.. The whole costs of the drive fixing were now on 50€! And still nothing.. I just want some files back.. Cannot I do anything else? Like upgrading the firmware or something else with the Hyperterminal? Please help me.. Kind regards Arman! Sorry for my bad English, I'm German..