Starting Point When Drive Size Isn't Recognized

  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

drivedead

New member
Dec 16, 2024
2
1
Drive Details: Seagate Exos 16TB (ST16000NM001G - 2KK103) HDD
Age: Installed May 2019
Usage: Should have around 5-6TB of data

Yesterday morning this drive was at 100 activity without any read/write actions taking place. I initially thought a process had locked up the drive, so I restarted the machine. When that did nothing, I performed a CHKDSK and began a virus scan and defrag. Both of them froze, probably because the drive was already at 100% activity. This was when I remembered SpinRite from all the SecurityNow podcasts and decided that I should give it a try. I figured SpinRite would easily fix the problem as the drive was online and 'accessible'. I installed SpinRite to a USB drive and set it for a level 2 scan on the Seagate. After an hour or two the SpinRite threw an error saying 'the hard drive is no longer responding to commands' at 0.0230% complete at sector 7,184,807. I attempted to run SpinRite again from this location, but am now presented with the errors shown in the pictures.

I have also booted the machine back into Windows 11 and the affected drive will show in disk management, but says its not initialized. An Ubuntu live disk says nearly the same thing with 'cannot read superblock'.

How do I get past this error and get SpinRite to attempt to recover the data on this drive?

I appreicate your time and help.
Dan
 

Attachments

  • 20241216_063410.jpg
    20241216_063410.jpg
    74.3 KB · Views: 77
  • 20241216_063354.jpg
    20241216_063354.jpg
    85.5 KB · Views: 67
Something is very wrong with that drive. I recommend shutting down your computer, disconnecting both of the cables to that drive for 1 minute, then plugging it back in and trying again. If that doesn't help, it's probably dead.

I'd love to get a debug log if you're willing to share. Launch SpinRite with the DIAGS parameter, then exit. ZIP up everything in your SRLOGS folder and upload it here.

 
Thank you for the quick response! I disconnected, reconnected with the cables attached, tried different cables, and an enclosure. I ended up sending the drive to a professional service to recover the data.
 
  • Like
Reactions: ColbyBouma
I actually have a different disk size problem and I hope someone has a suggestion how to fix this. I have a 5 terabyte drive (see picture) with a SATA interface. However, SpinRite only recognizes the drive as 500 gigabytes (see picture). EaseUS also only recognizes 500 gigabytes. I used to see more space on the drive but did some manipulation with various partition programs and now the rest of the drive does not appear to be there. I ran CHKDSK /f and nothing changed. Does anyone have any suggestions?
 
Thanks so much for the responses. I did not realize the file attachment limit was 500 kb. I have resized my pictures and attached them. Again, my disk is 5 terabytes but the computer only shows 500 gigabytes. Shadow- - you suspect this is a firmware problem, but where? I get the same result no matter which computer I attach this external drive to. My original thought was some sort of corruption in the root directory of the disk but I am not familiar enough with the low level structure of disks to fix this. Any suggestions would be greatly appreciated.
SpinRite.jpg
Disk.jpg
 
I suspect you may be connecting the wrong drive to the computer. The 5 TB drive is a Seagate, but SpinRite sees a 500 GB Western Digital drive. How are you connecting the Seagate to the computer running SpinRite?
 
I have seen one drive's ID somehow get transferred to
another drive, an idiopathic DRIVE firmware overwrite, so
the 5TB Seagate could have a 500GB WD identity
somehow overwritten into it's firmware . . . though
I cannot imagine how to do such a thing again or on
purpose.

More likely is the presence of a 500GB WD drive while
intending to test a 5TB Seagate drive.

Simplify.

Remove ALL drives EXCEPT the 5TB Seagate drive
intended for testing.

If the 5TB Seagate 'shows up' as a 500GB WD, then the
5TB Seagate drive's FIRMWARE has been somehow
corrupted.

Field service might get to the data by swapping in an
identical drive circuit card from a matching 5TB
Seagate.

Otherwise, it's off to a Seagate recovery service.
 
The big question... Is this actual lost data that needs recovering, or just letting SpinRite check drive? Because if it's lost data you really need to reach out to a data recovery lab, such as https://www.300dollardatarecovery.com/

Other options available here: https://www.datarecoveryprofessionals.org/member-listing

I'm always happy to help UK based people with data recovery, often for free if the drive still works. But outside the UK the postal costs are just too high.
 
Last edited:
In an attempt to solve my problem I tried cloning another drive to this one. This is probably how the firmware got corrupted. Does anyone know of a way to fix the firmware on this hard drive or is my only choice to find another 5 terabyte Seagate drive to clone to this one?
 
The firmware is in the service area, that's not accessible without special tools, so you won't be able to fix it with normal drive to drive cloning. What is your primary goal here for this drive?

If you are trying to recover data, don't do random things that will make the drive worse.

Why not take another pic of drive and how it's being connected, just to double check things.
 
Last edited:
Since my last post, I went to the Seagate site and downloaded the firmware update. The update process is complicated, so I will try to do it in the next few days if I have time. In the meantime, I currently have no useful data on this drive, so it is not a tragedy if I cannot fix this. Nevertheless, I would like to get the whole 5 terabyte capacity if possible.
 
At the Seagate site, I downloaded their tools and ran the quick test on this drive. As you can see from the image (disk 4), the serial number and firmware are blank. Therefore, the firmware has been corrupted and I am hopeful an update will fix it.
 

Attachments

  • Seagate.png
    Seagate.png
    84.7 KB · Views: 13
I have a clone dock that clones without a PC, and it
copied the source drive info to the target drive,
firmware and all - ouch.

How did you clone?
 
Last edited:
I also have a clone dock that clones a drive independently. I tried it late this week by using a multiterabyte drive as the source but it also did not work.
 
At the Seagate site, I downloaded their tools and ran the quick test on this drive. As you can see from the image (disk 4), the serial number and firmware are blank. Therefore, the firmware has been corrupted and I am hopeful an update will fix it.
What’s curious is that the drive is detected to be connected over USB? That should be listed as SCSI, SATA or SAS…

Don’t apply firmware if it’s really detecting over USB, because some commands might get blocked 😬