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. 


Gradius2

The Solution for Seagate 7200.11 HDDs

Recommended Posts

The disk seems fine (in the sense that the data copied by dd makes sense, it is not 00's or F6's).

The partition table is "normal":
#0 07 00 0 32 33 1023 254 63   2048 976766976

the MBR boot code is GRUB (possibly GRUB2) and extends up to sector LBA 104 (which is unusual, as normally that would be contained within sector 62 to allow partitioning with CHS alignment), anyway the disk is MB aligned (i.e. PBR is on sector LBA 2048), so it's fine.

The PBR is a "normal" NTFS one invoking BOOTMGR, to be picky it is the version "NT62" i.e. the one coming with Windows 8/8.1, and it is just fine.

The address of the $MFT is in the "usual" position on cluster 786432, which is also "fine" and "normal".

Most probably there is some corruption in the NTFS filesystem itself, it is not common (but it can happen), the "resetting" procedure may alter the P-list (or the G-list, or both) and if one or more remapped sectors is "lost" AND it is a "vital" one the result is an unreadable volume.

Standard/suggested procedure:
1) procure yourself a 750 GB (or larger) hard disk (if you have or can afford a 1.5 or 2 TB one, better)
2) dd the whole failed disk to an image file (if possible make a second copy of the image)
3) try accessing the image with DMDE:
https://dmde.com/

(though not exactly for the newbie/faint of heart) in case of (relatively) simple issues it can be used also by a non-expert of NTFS, it is read-only by default so it is safe.

Usually (not always but usually) DMDE is able to allow the recovery of files (without "fixing" the underlying NTFS) keeping the folder structures and names, so assuming that the disk was not full up to the brim and you can use a 1.5 or 2 TB disk, you should have enough space on it to salvage the relevant files.

Then, once these are "safe", we may talk of analyzing and hopefully fix the NTFS.

To do this - should you need assistance - start a new thread as that would be off topic here (and the thread is long enough already.

jaclaz 

Share this post


Link to post
Share on other sites

Hello all,

Glad you are still talking about the Seagate problem but also sorry that we have to. I have a Barracuda 7200.11 ST31000333AS with firmware SD35, P/N 9FZ136-568. It has gone AWOL with the BSY bug twice (out of warranty, of course) and been resurrected both times with the USB serial cable and HyperTerminal, the second time just two weeks ago. I tried to update the firmware to SD1A and SD1B using both the exe and the ISO but failed. I have since found that I need the Brinks-3D6H-SD3B firmware to flash my drive but haven't found it. Does anyone here know where I could get it? Thanks!

Share this post


Link to post
Share on other sites

Well, what do you know? I have found what I believe to be the proper LOD file to upgrade my drive firmware at HDDGuru. Now to try and figure out the command to force the update.

Share this post


Link to post
Share on other sites
On 11/16/2018 at 7:09 PM, NoNothing said:

Well, what do you know? I have found what I believe to be the proper LOD file to upgrade my drive firmware at HDDGuru. Now to try and figure out the command to force the update.

If you want the actual Brinks-3D6H-SD3B.ISO, find it attached :)

jaclaz

 

Brinks-3D6H-SD3B.ISO

  • Like 1

Share this post


Link to post
Share on other sites
7 minutes ago, NoNothing said:

My hero!! Thank you so much for this! I will try it after the holiday.

Good :)

If you can, let us know how it went.

jaclaz

Share this post


Link to post
Share on other sites

Grazie mille to jaclaz for the ISO file!:worship: I used it successfully to update the firmware on my ST31000333AS hdd. None of the backup files stored on the disk were harmed, either. Hopefully, the drive won't die from some other cause anytime soon.;) Thanks again!

Share this post


Link to post
Share on other sites
12 hours ago, NoNothing said:

Grazie mille to jaclaz for the ISO file!:worship: I used it successfully to update the firmware on my ST31000333AS hdd. None of the backup files stored on the disk were harmed, either. Hopefully, the drive won't die from some other cause anytime soon.;) Thanks again!

You are welcome.

Another happy bunny in the basket :):

http://www.msfn.org/board/topic/128727-cant-access-repair-my-pc-option-via-f8-startup/?p=828512

jaclaz

Share this post


Link to post
Share on other sites

Hi everybody. Still here in 2019 trying to recover these ill-fated 7200.11 drives...

Six months ago I got one of them from a colleague, ST31000333AS with SD35 firmware, in BSY state. I got an USB-to-RS232 cable from eBay, installed the drivers, set everything up and restored it in less than an hour. All data were still there... complete success.

Last month a friend asked me to fix his HD, same model and same firmware. I thought "that's an easy one, I've already done it". And of course something went wrong. My fear is that at the very end of the process I made a mistake turning off the power too soon... Now the BIOS can see the hd, with the right 1 Tb capacity, but the partition is not recognized. I repeated the whole process many times, but after the "m0..." command the results are not as expected: I have to wait 10-12 minutes, then I get this message

"User Partition Format   4% complete, Zone 00, Pass 00, LBA 00004AA5, ErrCode 00000080, Elapsed Time 0 mins 30 secs        
User Partition Format Successful - Elapsed Time 0 mins 30 secs        
Zone re-format was skipped."

Do you think it's bricked without hope, or is there still a chance to get it back to work? Many thanks in advance for your suggestions.

Share this post


Link to post
Share on other sites

Quick recap:
1) if it is "LBA0", it is bricked
2) if it is "BUSY", it is bricked
3) if the BIOS sees it, possibly with its full capacity, then it is NOT bricked (anymore)

The state in which it is is definitely "NOT bricked", but this doesn't mean that there is not some other issue (hopefully a small corruption that can be sometimes - but not alwasy - fixed ).

See an example of success:

 

and one of failure:

In case, start a NEW thread asking for help to attempt recovering the partition(s) on the disk.

jaclaz

Edited by jaclaz

Share this post


Link to post
Share on other sites

Thanks for your answer, Jaclaz. BTW, it's somewhat funny to communicate in English... since we're both from Italy :rolleyes:

For the record, I ran TestDisk to check if the partition was corrupted, but there was definitely something wrong. After I chose the drive in the selection page, it took a LOT of time to open the next one (Partition Table). Then I checked one option after another, getting always the same answer: bad partition. Doing a QuickSearch caused the app to freeze after a few sectors (327680). Doesn't seem like a good sign to me.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...