SpinRite Best Config for All Drivers

[Info]

Hi,

Running Spinrite on the first drive, I chose level 5. Would this be the best level to confirm that a drive is 100% defect-free? All data will be erased, right? Can we say that before selling a used drive, we can use level 5 for a complete rewrite and a log confirming that the unit is 100% functional?

I selected the drive and level 5, benchmark before and after, log enabled.

One question: will the log be saved on the USB drive or on the hard drive?

Any other thoughts or tips would be greatly appreciated.

The estimated time is approximately 48 hours for a 6TB drive. Can we say that for 18TB drives it will take 6 days? And for 22TB it will take 1 week, right?

The biggest problem would be a power outage when it's almost finished; would the test have to be restarted from the beginning?

Best Regards,

 

[Info]

 

[ColbyBouma]

Running Spinrite on the first drive, I chose level 5. Would this be the best level to confirm that a drive is 100% defect-free?

Yes, it is the most thorough level, if you're willing to take the time to let it run. Level 3 should catch almost everything though, if you want a faster scan.

All data will be erased, right?

No. SpinRite tries VERY hard to NOT erase data

Can we say that before selling a used drive, we can use level 5 for a complete rewrite and a log confirming that the unit is 100% functional?

SpinRite writes logs to the boot drive (usually a USB stick) by default. If you want to give the log file to the buyer, you can.

The estimated time is approximately 48 hours for a 6TB drive. Can we say that for 18TB drives it will take 6 days? And for 22TB it will take 1 week, right?

I don't have any logs for a Level 5 scan of drives that large, but those estimates sound reasonable to me.

The biggest problem would be a power outage when it's almost finished; would the test have to be restarted from the beginning?

No. You can start a scan at any point. If you lose power, the log may not be written, so you may have to guess where it was. I highly recommend buying a UPS. They cost less than the hard drives you're testing

 

[Info]

Complete the first disc with Spinrite level 5.

SpinRite v6.1 - Release 4

Type|Port|BIOS|Runtime|Size| Model | Serial

ATA | SS | 81 | 58,867|6.0T|HGST HDN726060ALE610 |NAG0MNPP
BIOS| 80 | 80 | ... | 31G|This is the system boot drive |



| SpinRite 6.1, beginning level 5 operation at 12:33 am on Jan 1st, 2002. |
|--------------------------------------------------------------------------|
| From 0.0000% sect: 0 To 100.0000% sect: 11,721,045,167 |

| HGST HDN726060ALE610 |
|--------------------------------------------------------------------------|
| access mode: direct bus master serial number: NAG0MNPP |
| pci bus addr: 0:31:2 firmware rev: APGNT517 |
| adapter vendor: Intel Corporation rotation rate: 7200 |
| vendor-device: 8086-27C0 ata/atapi spec: ATA-8 |
| bios drive: 81h drv technology: generic |
| controller reg: 0170-0177h, 0376h lba in use: yes, 48-bit LBA |
| bus master reg: FFA8h |
| max transfer: serial 6.0 Gb/sec multi-word dma: -/2 (unknown md) |
| ultradma modes: 5/6 (100.0 MB/s) |
| sector count: 11,721,045,168 available pio: 4/4 (16.67 MB/s) |
| byte count: 6,001,175,126,016 |
| 4Ksec features: SMART SECURE POWR |
| transfers: 32,768 sector long ops: no : WCACH LOOKAHD HPA |
| ATA speed: 192,460,678 byte/s feature detail: 746B7D69 7469BC41 |

| Drive's measured performance before running SpinRite |
|--------------------------------------------------------------------------|
| smart polling delay: 39.304 msec |
| random sectors time: 11.841 msec |
| front of drive rate: 227.683 MB/s |
| midpoint drive rate: 188.535 MB/s |
| end of drive rate: 96.807 MB/s |

| Events |
|--------------------------------------------------------------------------|
| Sector 1,055,137,905 (9.0020%) SpinRite's rewritten data verification |
| failed. The drive did not report any trouble, but the reread data did |
| not match what was written! |
|--------------------------------------------------------------------------|
| Sector 1,055,137,919 (9.0020%) Despite many attempts, this sector of |
| the media refused to be written and re-read. |
|--------------------------------------------------------------------------|
| Sector 5,523,046,400 (47.1207%) The drive has refused to accept |
| original data after inverted data was written. Attempting rewrite to |
| restore original data. |
|--------------------------------------------------------------------------|
| Sector 6,523,286,560 (55.6544%) SpinRite's rewritten data verification |
| failed. The drive did not report any trouble, but the reread data did |
| not match what was written! |
|--------------------------------------------------------------------------|
| Sector 6,523,286,575 (55.6544%) Despite many attempts, this sector of |
| the media refused to be written and re-read. |
|--------------------------------------------------------------------------|
| Sector 6,933,741,568 (59.1563%) The drive has refused to accept |
| original data after inverted data was written. Attempting rewrite to |
| restore original data. |
|--------------------------------------------------------------------------|
| Sector 6,990,004,224 (59.6363%) The attempt to write a block with |
| inverted data failed and the trouble sector could not be identified. |
|--------------------------------------------------------------------------|
| Sector 10,049,486,848 (85.7388%) The attempt to write a block with |
| inverted data failed and the trouble sector could not be identified. |
|--------------------------------------------------------------------------|
| Sector 10,362,093,568 (88.4058%) The drive has refused to accept |
| original data after inverted data was written. Attempting rewrite to |
| restore original data. |

| Drive's measured performance after running SpinRite |
|--------------------------------------------------------------------------|
| smart polling delay: 37.925 msec |
| random sectors time: 11.978 msec |
| front of drive rate: 228.650 MB/s |
| midpoint drive rate: 190.738 MB/s |
| end of drive rate: 97.767 MB/s |

| Level: 5 Graphic Status Display |

| :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: |
| ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: |
| :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: |
| :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: |
| :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: |
| :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: |
| :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: |
| ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: |
| :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: |
| :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: |
| :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: |
| :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: |
| :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: |
| :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: |
|--- work ---- remaining --- completed +------- sector status key ---------|
| megabytes: 0.000 6,001,175 | .oO analyzing | R recovered |
| %: 0.000% 100.000%| . unprocessed | B defective |
| time: 0:00:00 60:45:42 | : processed | U unrecovered |

| Final Sector Event Counts |

| command timeout: 0 command aborted: 7 |
| comm/cable errs: 0 not recoverable: 2 |
| minor troubles: 0 sect neverfound: 0 |
| dynastat recovr: 0 defective sectr: 2 |

| End-of-Run SMART System Status |
|--------------------------------------------------------------------------|
| monitored param margin current/max raw data |
| ECC corrected 0 :::::::::::::::::::::::::::::: 84/84 00000000000000 |
| rd chan margin - |
| relocated sect 0 :::::::::::::::::::::::::::::: 95/95 00000000000001 |
| realloc events 0 :::::::::::::::::::::::::::::: 100/100 00000000000001 |
| seek errors 0 :::::::::::::::::::::::::::::: 33/33 00000000000000 |
| recal retries - |
| cabling errors 0 :::::::::::::::::::::::::::::: 200/200 00000000000007 |
| uncorrectable 0 :::::::::::::::::::::::::::::: 100/100 00000000000000 |
| write errors - |
| command timeout - |
| pending sectors 0 :::::::::::::::::::::::::::::: 100/100 00000000000000 |
| read retries - |
| total writes - |
| write failures - |
| wear leveling - |
| remaining life - |
| realloc space - |
|--------------------------------------------------------------------------|
| drive temperature: 51'C/124'F |

| SpinRite 6.1, level 5 operation completed at 1:20 pm on Jan 3rd, 2002. |

How can we interpret this? What is the condition of this HDD?

 

[peterblaise]

"... command aborted: 7 ... not recoverable: 2 ... defective sectr: 2 ...
How can we interpret this? What is the condition of this HDD? ..."

SpinRite has 2 assignments:

data recovery in place​

​

drive maintenance​

This drive may have failed both.

2 sectors may have lost data​

​

the drive refuses to accept or report accurate data on some sectors​

With the sector numbers, we can see what files they are used by, if
any, using the NTFS command line utiilty NFI.EXE. *

If not an NTFS partition, then ChkDSk /R is all we can do.

Run Level 5 again and confirm.

If the [ B ] are gone on a second pass, then the drive is fixed.

If the [ B ] bad blocks stay, then the drive may be suitable for use
with a high-level ChkDsk /R to mark wonky sectors bad.

If the [ B ] expand on a second pass, then the drive is decaying, to
be retired as a test drive only.

Right?

- - - - -

* Google, how do we get and use the NTFS NFI.EXE command line utility?

The NFI.EXE (NTFS File Sector Information) utility is an older Microsoft Sysinternals tool for inspecting NTFS volume and file data, often used to find which file occupies a specific sector, requiring admin rights and run from Command Prompt, though it's now largely superseded by modern tools like NTFSInfo from Sysinternals or forensic suites, as finding the original NFI download can be tricky.
To use it (if you find it), you'd run it like for volume info or for a file, or to map a physical sector, but you must run it as an Administrator for detailed analysis. [1, 2, 3, 4]

How to Get NFI.EXE (If You Can Find It)

1. Search for Sysinternals Suite: NFI was part of older Sysinternals tools. Search for the "Sysinternals Suite" or "NTFS Utilities" on Microsoft Learn or archive sites, as it's less common now.
2. Use Alternatives: For modern tasks, Microsoft now offers NTFSInfo, a more user-friendly tool with similar functions, available from Microsoft Learn. [1, 3, 5]

How to Use NFI.EXE (General Syntax)
You'll need to run it from an elevated Command Prompt (Run as Administrator).

• : Shows information for the entire volume (e.g., or ).
• : Dumps info for a specific file (e.g., ).
• : Finds which file a physical sector belongs to (e.g., ). [2]

What It Does

• Displays detailed NTFS metadata.
• Maps physical sectors to files, useful for forensics or data recovery on failing drives. [2, 7, 8]

Modern Alternatives & Considerations

• NTFSInfo: A modern Sysinternals tool that's better for general NTFS volume inspection.
• 7-Zip: Can open physical drives (PhysicalDrive0, etc.) as an administrator to view NTFS metadata files like .
• Advanced Tools: For deep forensic work on bad sectors, tools like ddrescue with ddru_ntfsfindbad (Linux-based) are more specialized. [1, 7, 9, 10]

[1] https://learn.microsoft.com/en-us/sysinternals/downloads/ntfsinfo
[2] https://superuser.com/questions/97823/how-do-i-determine-what-file-occupies-a-given-sector
[3] https://serverfault.com/questions/304586/how-do-i-view-ntfs-metadata
[4] https://en.wikipedia.org/wiki/NTFS
[5] https://community.spiceworks.com/t/top-5-free-tools-for-ntfs-permissions-reporting/616942
[6]

[7] https://superuser.com/questions/1266135/how-do-i-find-if-there-are-files-at-a-specific-bad-sector
[8] https://jotelulu.com/en-gb/blog/what-is-ntfs-and-what-does-it-do/
[9] https://thestarman.pcministry.com/asm/mbr/IntNTFSfs.htm
[10] https://superuser.com/questions/1615910/unable-to-locate-the-physical-disk-sectors-a-file-occupies

 

[AlanD]

SpinRite writes logs to the boot drive (usually a USB stick) by default. If you want to give the log file to the buyer, you can.

Check that your SR serial number is not visible in the log before handing it over to anyone else.

 

[ColbyBouma]

Check that your SR serial number is not visible in the log before handing it over to anyone else.

SpinRite 6.1 does not put the serial number in the log. Previous versions did.

 

[Info]

"... command aborted: 7 ... not recoverable: 2 ... defective sectr: 2 ...
How can we interpret this? What is the condition of this HDD? ..."

SpinRite has 2 assignments:

data recovery in place​

​

drive maintenance​

This drive may have failed both.

2 sectors may have lost data​

​

the drive refuses to accept or report accurate data on some sectors​

With the sector numbers, we can see what files they are used by, if
any, using the NTFS command line utiilty NFI.EXE. *

If not an NTFS partition, then ChkDSk /R is all we can do.

Run Level 5 again and confirm.

If the [ B ] are gone on a second pass, then the drive is fixed.

If the [ B ] bad blocks stay, then the drive may be suitable for use
with a high-level ChkDsk /R to mark wonky sectors bad.

If the [ B ] expand on a second pass, then the drive is decaying, to
be retired as a test drive only.

Right?

- - - - -

* Google, how do we get and use the NTFS NFI.EXE command line utility?

The NFI.EXE (NTFS File Sector Information) utility is an older Microsoft Sysinternals tool for inspecting NTFS volume and file data, often used to find which file occupies a specific sector, requiring admin rights and run from Command Prompt, though it's now largely superseded by modern tools like NTFSInfo from Sysinternals or forensic suites, as finding the original NFI download can be tricky.
To use it (if you find it), you'd run it like for volume info or for a file, or to map a physical sector, but you must run it as an Administrator for detailed analysis. [1, 2, 3, 4]

How to Get NFI.EXE (If You Can Find It)

1. Search for Sysinternals Suite: NFI was part of older Sysinternals tools. Search for the "Sysinternals Suite" or "NTFS Utilities" on Microsoft Learn or archive sites, as it's less common now.
2. Use Alternatives: For modern tasks, Microsoft now offers NTFSInfo, a more user-friendly tool with similar functions, available from Microsoft Learn. [1, 3, 5]

How to Use NFI.EXE (General Syntax)
You'll need to run it from an elevated Command Prompt (Run as Administrator).

• : Shows information for the entire volume (e.g., or ).
• : Dumps info for a specific file (e.g., ).
• : Finds which file a physical sector belongs to (e.g., ). [2]

What It Does

• Displays detailed NTFS metadata.
• Maps physical sectors to files, useful for forensics or data recovery on failing drives. [2, 7, 8]

Modern Alternatives & Considerations

• NTFSInfo: A modern Sysinternals tool that's better for general NTFS volume inspection.
• 7-Zip: Can open physical drives (PhysicalDrive0, etc.) as an administrator to view NTFS metadata files like .
• Advanced Tools: For deep forensic work on bad sectors, tools like ddrescue with ddru_ntfsfindbad (Linux-based) are more specialized. [1, 7, 9, 10]

[1] https://learn.microsoft.com/en-us/sysinternals/downloads/ntfsinfo
[2] https://superuser.com/questions/97823/how-do-i-determine-what-file-occupies-a-given-sector
[3] https://serverfault.com/questions/304586/how-do-i-view-ntfs-metadata
[4] https://en.wikipedia.org/wiki/NTFS
[5] https://community.spiceworks.com/t/top-5-free-tools-for-ntfs-permissions-reporting/616942
[6]

[7] https://superuser.com/questions/1266135/how-do-i-find-if-there-are-files-at-a-specific-bad-sector
[8] https://jotelulu.com/en-gb/blog/what-is-ntfs-and-what-does-it-do/
[9] https://thestarman.pcministry.com/asm/mbr/IntNTFSfs.htm
[10] https://superuser.com/questions/1615910/unable-to-locate-the-physical-disk-sectors-a-file-occupies

Thanks very much peterblaise, my main interest is not in data recovery. Currently, my backup covers most of my important files.

The main concern is to know if a unit has any defects/problems, however minor, so that the data is not at risk.

I'll run SpinRite on that HDD again and check the result; it no longer has any files on it, because when I received the first Smart HDTune alert, we had already transferred the files to another HDD.

I'll be back soon with the results of the second check.

Best Regards,

​

 

[DanR]

my main interest is not in data recovery

That is good to know.

Please note: Level 5 is a rigorous/harsh drive exercise mode that can easily push a problematic drive over the edge.

Contrary to the grossly misinformed opinions of some, level 5 is NOT a panacea for all things for all drives.

in this case, there is a better less potentially harmful option available. Level 2, DynaStat 0

c:\>spinrite level 2 dynastat 0

This will do one normal read per every sector on the drive. If the read succeeds go to the next sector.

If the read fails, write all zeros to the sector. If the write fails (hence a "B") then this typically triggers the drive firmware to reallocated the sector.

A level 2 run saves an enormous amount of time versus a level 5 run, and is much MUCH safer for a problematic drive such as this one.

Then a simple Level 3 run should be a clean error free run.

A pertinent question is: When/where will another sector go bad???

The run time of almost 59,000 hrs is another concern.

Thus, I would consider this drive’s reliability for any important/critical data storage to be very suspect and not to be considered..

But as a scratch drive for inconsequential data, it could be of some use. But with almost 59,000 hours on the drive, that use is likely limited.

Lastly, if additional bad sectors continue to appear, the drive is failing and should either be tossed or set aside as a test specimen for a future yet to be developed version of SpinRite.

 

[jlee]

The main concern is to know if a unit has any defects/problems, however minor, so that the data is not at risk.

Just run a level 1. It will find all sectors that are unreadable but won't try to fix them. It's the fastest for what you want. The logs will tell you any bad sectors it finds.

 

[peterblaise]

If we plan on using a drive for original data
storage, Level 5 is critically important, as it
tests every sector, every byte's ability to
WRITE twice, as well as READ three times.

Level 2 only tests all READ capability, and
some WRITE capability, but not all.

However, DynaStat 0 will probably throw a
bad drive off line when it hits bad sectors
outside the drive's own expected error
recovery, confirming that it is no longer to
be trusted with data, but has become a test
drive for future reference.

- - - - -

For those interested in data recovery, Level 2
DynaStat 0 NoRewrite may bypass throwing
a bad drive offline, and may facilitate
triggering the drive to recover some sectors
on it's own, and Spinrite may fix minor
problems, making the best chance to copy
out as much recoverable data as possible.

- - - - -

"... grossly misinformed opinions of some, level 5
is NOT a panacea for all things for all drives ..."

I've never read anyone who claims that.

From my own expereince, I have testified for
years that Level 5 is a critical test to confirm a
drive's capabilities, not 'fix' for a bad drive.

The the contrary, Level 5 has confirmed the
retirement of bad drives that otherwise have
passed Level 1, Level 2, Level 3, and even
Level 4.

Level 5 is an ultimate threshold over which
many drives just don't measure up.

And how would we know if we did not test
every drive with Level 5 BEFORE we added
our precious original data?

Level 5 on!

And share our logs via @ColbyBouma's
generous Gitlab repository :

https://gitlab.com/GRC-Community/SpinRite-Logs

Thanks.

 

[Info]

That is good to know.

Please note: Level 5 is a rigorous/harsh drive exercise mode that can easily push a problematic drive over the edge.

Contrary to the grossly misinformed opinions of some, level 5 is NOT a panacea for all things for all drives.

in this case, there is a better less potentially harmful option available. Level 2, DynaStat 0

c:\>spinrite level 2 dynastat 0

This will do one normal read per every sector on the drive. If the read succeeds go to the next sector.

If the read fails, write all zeros to the sector. If the write fails (hence a "B") then this typically triggers the drive firmware to reallocated the sector.

A level 2 run saves an enormous amount of time versus a level 5 run, and is much MUCH safer for a problematic drive such as this one.

Then a simple Level 3 run should be a clean error free run.

A pertinent question is: When/where will another sector go bad???

The run time of almost 59,000 hrs is another concern.

Thus, I would consider this drive’s reliability for any important/critical data storage to be very suspect and not to be considered..

But as a scratch drive for inconsequential data, it could be of some use. But with almost 59,000 hours on the drive, that use is likely limited.

Lastly, if additional bad sectors continue to appear, the drive is failing and should either be tossed or set aside as a test specimen for a future yet to be developed version of SpinRite.

Hello to all my friends.

c:\>spinrite level 2 dynastat 0 - executed successfully

Running level 3

After completion I will run level 5 again.

Thanks very much all help and support.

 

[peterblaise]

"... Level 5 is a rigorous/harsh drive exercise
mode that can easily push a problematic drive
over the edge ..."

SpinRite LEVEL 5 reads three times and writes
twice.

Nothing harsh about that.

Users do that all the time.

That's what drives do for a living.

If a drive can't do that, it's not ready for prime
time as a user storage and retrieval device.

That said, LEVEL 5 is DRIVE MAINTENANCE, not
DATA RECOVERY.

If anyone has difficulty copying out, LEVEL 2
DYNASTAT 1 NOREWRITE or LEVEL 2
DYNASTAT 0 NOREWRITE probably offer the
most direct route to hard-to-read data.

Some folks have found some drives to "self
heal" just on a LEVEL 1 read, enough to copy
out their data.

Then LEVEL 5 to help make a decision on ever
trusting that drive again.

There is nothign to fear about SpinRite LEVEL 5.

Just use it appropriately.

 

[Info]

Hi,

Level 03 all ok

I am now running level 5 again.

Can we say that the disc has been recovered? What is the opinion in this case?

Best Regards,

 

[peterblaise]

I'd draw read and write data transfer rate
response graphs with free HDDScan
https://hddscan.com/ to see if there are
unacceptably slow sectors or not.

SpinRite is for data recovery and drive
maintenance, but does not report
sector-by-sector performance, only
generaly multi-range data transfer rate.

If there are outlier slow sectors that cause
a user to reconsider employing the drive,
HDDScan will reveal them.

Sorry, that means yet another write cycle,
and yet another read cycle.

Fun, eh?

 

[Info]

I'd draw read and write data transfer rate
response graphs with free HDDScan
https://hddscan.com/ to see if there are
unacceptably slow sectors or not.

SpinRite is for data recovery and drive
maintenance, but does not report
sector-by-sector performance, only
generaly multi-range data transfer rate.

If there are outlier slow sectors that cause
a user to reconsider employing the drive,
HDDScan will reveal them.

Sorry, that means yet another write cycle,
and yet another read cycle.

Fun, eh?

Hi peterblaise, thanks very much for reply.

No problem, Could you guide me to the correct option in HDDScan? in TEST > Verify or READ or BUTTERFLY or ERASE ?

Best Regards,

 

[peterblaise]

You'da boss, ANY "TO THE HOST" option will test the drive actually
delivering the data to the host - it's not a self-test, it's a "please
actaully DELIVER the data" test. Butterfly is semi-real for dynamic
data, the others are linear front-to-back, like bulk writes. To match
SpinRite, you can change the data transfer block to 32,768,
otherwise, accept defaults. The goal is to see a smooth graph or
sudden dips <-- indicating slow sectors. Here's what a slow sector
looks like in an HDDScan graph:

That downward spike will cause the operating system to pause for up
to 5 reads per cluster, and the drive may do the same at the same
time per sector, compounding the delay.

ChkDsk /R may or may not find it and mark it bad.

We'd need to manually find the NTFS cluster and put it in a
$BADCLUS file to keep the operating systme away from it. *

I wish ChkDsk has a sensitivity setting for cluster responsiveness

But this is what it takes to have complete and total confidence in our
gear.

Good for you to hang in there.

So, in HDDScan:

#1 - ERASE graph

#2 - READ or BUTTERFLY ... to the host graph.

Then you'll know everything there is to know about the drive.

You may get a list like this suggesting the number of slow sectors,
and how slow:

THAT list of slow sectors is from is one ugly drive sample - I keep such
drives to test the tests!

- - - - -

* Manually adding bad clusters, Google AI-assisted search says:

1. Boot into a different environment: You must boot from a live
   USB or recovery environment that has NTFS manipulation tools.
2. Use specialized tools: Tools like ntfsclone (from the ntfsprogs
   package) or other forensic analysis tools can be used to modify
   the NTFS file system structure.
3. Add clusters to $BadClus: The tool will be used to add new
   clusters to the run list of the $BadClus file.
4. Modify file and MFT entry: The size of the $BadClus file and
   its MFT entry may need to be adjusted.
5. Mark clusters as bad: The status of the newly allocated
   clusters is set to "bad".

Alternatively, I run ChkDsk /R repeatedly until the number of bad
'sectors' ( actually clusters ) stabilizes, no longer grows.

Then I dedicate the drive to testing and learning from - it's hardly
trustworthy for data storage.

 

[Info]

You'da boss, ANY "TO THE HOST" option will test the drive actually
delivering the data to the host - it's not a self-test, it's a "please
actaully DELIVER the data" test. Butterfly is semi-real for dynamic
data, the others are linear front-to-back, like bulk writes. To match
SpinRite, you can change the data transfer block to 32,768,
otherwise, accept defaults. The goal is to see a smooth graph or
sudden dips <-- indicating slow sectors. Here's what a slow sector
looks like in an HDDScan graph:

View attachment 1834

That downward spike will cause the operating system to pause for up
to 5 reads per cluster, and the drive may do the same at the same
time per sector, compounding the delay.

ChkDsk /R may or may not find it and mark it bad.

We'd need to manually find the NTFS cluster and put it in a
$BADCLUS file to keep the operating systme away from it. *

I wish ChkDsk has a sensitivity setting for cluster responsiveness

But this is what it takes to have complete and total confidence in our
gear.

Good for you to hang in there.

So, in HDDScan:

#1 - ERASE graph

#2 - READ or BUTTERFLY ... to the host graph.

Then you'll know everything there is to know about the drive.

You may get a list like this suggesting the number of slow sectors,
and how slow:

View attachment 1835

THAT list of slow sectors is from is one ugly drive sample - I keep such
drives to test the tests!

- - - - -

* Manually adding bad clusters, Google AI-assisted search says:

1. Boot into a different environment: You must boot from a live
   USB or recovery environment that has NTFS manipulation tools.
2. Use specialized tools: Tools like ntfsclone (from the ntfsprogs
   package) or other forensic analysis tools can be used to modify
   the NTFS file system structure.
3. Add clusters to $BadClus: The tool will be used to add new
   clusters to the run list of the $BadClus file.
4. Modify file and MFT entry: The size of the $BadClus file and
   its MFT entry may need to be adjusted.
5. Mark clusters as bad: The status of the newly allocated
   clusters is set to "bad".

Alternatively, I run ChkDsk /R repeatedly until the number of bad
'sectors' ( actually clusters ) stabilizes, no longer grows.

Then I dedicate the drive to testing and learning from - it's hardly
trustworthy for data storage.

Hello,

Thanks very much for all the explanation.

HDDScan > TEST > BUTTERFLY

I obtained the following result (attached).

Can we say that the disc is still reliable?

Best Regards,

 

[peterblaise]

I've never seen a drive faster at the last tracks at the inner end than at
the first tracks at the outer lead-in:

SpinRite saw this, from your LOG:

front of drive rate:...227.866 MB/s
midpoint drive rate:...190.106 MB/s
end of drive rate:......96.843 MB/s

Your graph is opposite, backwards, and slower.

I'd like to see other runs on new HGST 6 TB drives.

Maybe an HDDScan > READ to host > Block size 32,768 would look
'normal', like this:

Those ms millisecond delay numbers 'feel' like the drive is ageing, but
at least there are only a relatively few - 651 sectors - that are really
slow, and there are no 'bads', so that's good.

This is why I tell folks to run a full suite of tests on a drive when it is
new to them, and keep the results for comparison later when they
wonder if the drive is ageing.

That's an apparently reliable storage drive, but the graph feels to
me like it's becoming an antique, very low performer, response-
wise, by today's standards.

If it's to be a WORM drive for you, write once, read many, then an
HDDScan > READ to host > Block size 32,768 would better
represents that use.

HDDScan > TEST > BUTTERFLY better represents a drive in
constant write and read and write and read over and over.

You decide.

But after so many read and write tests, it looks like a reliable, if
slow, storage drive nonetheless.

Google says:

The HGST HDN726060ALE610 is a 6TB, 3.5-inch internal hard drive with a 7200 RPM spindle speed and a 128MB cache.

It uses a SATA III (6Gb/s) interface and is designed for NAS (Network Attached Storage) systems, with a 1 million-hour Mean Time Between Failures (MTBF) for reliability. [1, 2, 3, 4, 5, 6, 7]


Key specifications

• Capacity: 6TB
• Form Factor: 3.5-inch
• Spindle Speed: 7200 RPM
• Cache: 128MB
• Interface: SATA III (6Gb/s)
• MTBF: 1 million hours
• Designed for: Desktop NAS systems [1, 2, 3, 4, 5, 7, 8, 9]

[1] https://www.disctech.com/HGST-0F23072-6TB-SATA-Hard-Drive-for-Desktop-NAS-Systems
[2] https://documents.westerndigital.co...ata-sheet-deskstar-nas-internal-drive-kit.pdf
[3] https://www.goharddrive.com/HGST-NAS-HDN726060ALE610-6TB-7200RPM-Hard-Drive-p/g01-0901-cr.htm
[4] https://www.newegg.com/p/1Z4-001J-003G3
[5] https://www.memory4less.com/hitachi-deskstar-6tb-sata-6-0-gbps-hard-drive-hdn726060ale610
[6] https://harddrivemart.com/hgst-hdn726060ale610.html
[7] https://www.ebay.com/itm/389034761114
[8] https://www.amazon.com/Ultrastar-7K6000-HUS726060ALE610-0F23001-Enterprise/dp/B00YA0DWS8
[9] https://www.cdw.com/product/hgst-6tb-sata-6gb-s-7.2k-rpm-128mb/8210887


The HGST HDN726060ALE610 hard drive was first available around early 2015. [1]

The broader HGST Deskstar NAS series was initially released in early 2014, with the 6TB capacity models following later.

While Newegg listed the product as "First Listed on Newegg" in August 2025 (likely a data entry error), UserBenchmark data and community forums suggest the 6TB model was available and discussed in early-to-mid 2015. [1, 2, 3, 4, 5]

AI responses may include mistakes.
[1] https://hdd.userbenchmark.com/SpeedTest/22222/HGST-HDN726060ALE610
[2] https://www.newegg.com/p/1Z4-001J-003G3
[3] https://bananahdd.nl/index.php/2023/02/13/hgst-deskstar-nas-hdn724040ale640-4tb-2016/
[4] https://www.storagereview.com/review/hgst-4tb-deskstar-nas-hdd-review
[5] https://community.netgear.com/discu...hds5c3020ala632-0f12117/825578/replies/825579

 

[Info]

I've never seen a drive faster at the last tracks at the inner end than at
the first tracks at the outer lead-in:

View attachment 1837

SpinRite saw this, from your LOG:

front of drive rate:...227.866 MB/s
midpoint drive rate:...190.106 MB/s
end of drive rate:......96.843 MB/s

Your graph is opposite, backwards, and slower.

I'd like to see other runs on new HGST 6 TB drives.

Maybe an HDDScan > READ to host > Block size 32,768 would look
'normal', like this:

Thanks very much for all help, I think I'm satisfied with the results. I also purchased an HD Sentinel license on Black Friday; I think that monitoring it still makes it a reliable drive.
I'll move on to the next disc and see if I can find any errors. Thank you again for everything.

View attachment 1839

Those ms millisecond delay numbers 'feel' like the drive is ageing, but
at least there are only a relatively few - 651 sectors - that are really
slow, and there are no 'bads', so that's good.

This is why I tell folks to run a full suite of tests on a drive when it is
new to them, and keep the results for comparison later when they
wonder if the drive is ageing.

That's an apparently reliable storage drive, but the graph feels to
me like it's becoming an antique, very low performer, response-
wise, by today's standards.

If it's to be a WORM drive for you, write once, read many, then an
HDDScan > READ to host > Block size 32,768 would better
represents that use.

HDDScan > TEST > BUTTERFLY better represents a drive in
constant write and read and write and read over and over.

You decide.

But after so many read and write tests, it looks like a reliable, if
slow, storage drive nonetheless.

Google says:

The HGST HDN726060ALE610 is a 6TB, 3.5-inch internal hard drive with a 7200 RPM spindle speed and a 128MB cache.

It uses a SATA III (6Gb/s) interface and is designed for NAS (Network Attached Storage) systems, with a 1 million-hour Mean Time Between Failures (MTBF) for reliability. [1, 2, 3, 4, 5, 6, 7]


Key specifications

• Capacity: 6TB
• Form Factor: 3.5-inch
• Spindle Speed: 7200 RPM
• Cache: 128MB
• Interface: SATA III (6Gb/s)
• MTBF: 1 million hours
• Designed for: Desktop NAS systems [1, 2, 3, 4, 5, 7, 8, 9]

[1] https://www.disctech.com/HGST-0F23072-6TB-SATA-Hard-Drive-for-Desktop-NAS-Systems
[2] https://documents.westerndigital.co...ata-sheet-deskstar-nas-internal-drive-kit.pdf
[3] https://www.goharddrive.com/HGST-NAS-HDN726060ALE610-6TB-7200RPM-Hard-Drive-p/g01-0901-cr.htm
[4] https://www.newegg.com/p/1Z4-001J-003G3
[5] https://www.memory4less.com/hitachi-deskstar-6tb-sata-6-0-gbps-hard-drive-hdn726060ale610
[6] https://harddrivemart.com/hgst-hdn726060ale610.html
[7] https://www.ebay.com/itm/389034761114
[8] https://www.amazon.com/Ultrastar-7K6000-HUS726060ALE610-0F23001-Enterprise/dp/B00YA0DWS8
[9] https://www.cdw.com/product/hgst-6tb-sata-6gb-s-7.2k-rpm-128mb/8210887


The HGST HDN726060ALE610 hard drive was first available around early 2015. [1]

The broader HGST Deskstar NAS series was initially released in early 2014, with the 6TB capacity models following later.

While Newegg listed the product as "First Listed on Newegg" in August 2025 (likely a data entry error), UserBenchmark data and community forums suggest the 6TB model was available and discussed in early-to-mid 2015. [1, 2, 3, 4, 5]

AI responses may include mistakes.
[1] https://hdd.userbenchmark.com/SpeedTest/22222/HGST-HDN726060ALE610
[2] https://www.newegg.com/p/1Z4-001J-003G3
[3] https://bananahdd.nl/index.php/2023/02/13/hgst-deskstar-nas-hdn724040ale640-4tb-2016/
[4] https://www.storagereview.com/review/hgst-4tb-deskstar-nas-hdd-review
[5] https://community.netgear.com/discu...hds5c3020ala632-0f12117/825578/replies/825579