Toshiba DT01ACA100 50% FAILURE

  • 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.)

cantsl

New member
Jan 22, 2021
3
0
I just ran ReadSpeed on a Dell Inspiron 3650 with a 1TB Toshiba DT01ACA100 HD

The results are:

Code:
Driv Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
 81  1.0TB TOSHIBA DT01ACA100              7.7     3.2  FAILURE    5.5     7.0

                  Benchmarked: Friday, 2021-01-22 at 18:59

I would like to run SpinRite 6.0 level 2 on this drive, but I see a warning regarding:

Code:
Part 1 MBR followed by EFI

Code:
Invalid partition for Drive Size

This partition exceeds the size of this drive as defined by the system's BIOS or BIOS extensions.

You should NOT PROCEED to use SpinRite on this drive until you have verified and corrected the disparity between this drive and the BIOS's or BIOS extensions's understanding of the drive size.


How would I go about doing this? Or am I just stuck waiting for SR 6.1? :-/

I am a Linux system admin by day and have several bootable "rescue" media options available.

EDIT: Sorry. I did not realize RS000.TXT would be on the USB and contain the results.
 
Last edited:
SpinRite 6 doesn't know about GPT. I presume this drive has a GPT partition on it. SpinRite 6.1 will understand GPT. If you're extra brave you can backup the partition table, then blank it, run SpinRite on what will then appear to be a "raw" drive, and then restore the partition table. This is fraught with danger of course, so not to be attempted by the faint of heart.

Additionally, for yourself, and others in the future, please do NOT edit the ReadSpeed results when posting, it's much easier to respond to questions if everyone uses the same formatting.
 
  • Like
Reactions: cantsl
Thanks for the suggestion.

Right now I have Clonezilla running to backup the data to an external USB drive. It seems to be working but is moving really slowly.

I thought I'd overwrite the disk with 0's or maybe DBaN and re-run ReadSpeed. 🤔
 
Clonezilla completed, saving each of the 5 partitions.

I used `shred -z -n0 -v` on each GPT partition (sda[1-5]), then restored the images that Clonezilla saved.

Rerunning ReadSpeed with no FAILURE this time and better numbers (attached), but I think this HD is dying.

I don't know how anyone can manage to use a Win10 system with only 4GB RAM. 😩

Code:
Driv Size  Drive Identity     Location:    0      25%     50%     75%     100
---- ----- ---------------------------- ------- ------- ------- ------- -------
 81  1.0TB TOSHIBA DT01ACA100             18.1    10.0    25.4   114.0    12.9

                  Benchmarked: Saturday, 2021-01-23 at 09:36
 
Last edited:
Suggestion: wipe the entire drive (not just the partitions), run SpinRite on it, then restore the image.
 
What the heck would that achieve?
It would achieve what is described, hopefully. Spinrite would probably be more comprehensive in fewer steps without destruction of data (and potential recovery).

Edit: Why did I answer that?