SpinRite FAQ ‑ Frequently Asked Questions
This page will be created shortly. Suggestions for its contents may be posted in the thread below and as they are considered they will be moved into this main body of the FAQ.
-
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.)
I would like a very clear description of how DynaStat interacts with levels that request a write/refresh. If the sector is unrecoverable via DynaStat, does it get written with recovered data if any, or zeroes if none was recoverable, or does it get left alone for future recovery attempts? I assume the answer is: the user chose a level that requires a rewrite so therefore bad sectors do get rewritten, no matter what, which probably forces the drive to relocate the sector if possible.
This does pose an issue for someone who doesn't know they have an unrecoverable sector and thought they were just doing maintenance and refreshing the drive in advance of any problems. In this case, SpinRite is running unattended and will "paper over" a problem the user didn't know they had.
This does pose an issue for someone who doesn't know they have an unrecoverable sector and thought they were just doing maintenance and refreshing the drive in advance of any problems. In this case, SpinRite is running unattended and will "paper over" a problem the user didn't know they had.
My drive is not showing up in the BIOS, can I still use SpinRite to get my data back?
My drive is showing zero capacity, can I still use SpinRite to get my data back?
My drive is making click click click sounds, can I still use SpinRite to get my data back?
My drive is making grinding/scraping sounds, can I still use SpinRite to get my data back?
Why do hard drives fail?
What are good sectors?
What are slow sectors?
What are bad sectors?
Can SpinRite detect drive firmware problems?
My drive is showing zero capacity, can I still use SpinRite to get my data back?
My drive is making click click click sounds, can I still use SpinRite to get my data back?
My drive is making grinding/scraping sounds, can I still use SpinRite to get my data back?
Why do hard drives fail?
What are good sectors?
What are slow sectors?
What are bad sectors?
Can SpinRite detect drive firmware problems?
Last edited:
Original post 2023: Development background: That's a limit for BIOS-presented USB-connected drives, where SpinRite 6.1 under development would test only the first 128GiB/137GB of a USB drive, that's not all drives, just USB, and @Paul_F developed a TSR-suite of programs that may test and present USB-connected drives via SCSI, and then SpinRite 6.1 would test the entire drive up to 2.2TB.
Update 2024-03: Steve Gibson has evolved SpinRite 6.1 during development to self-address the issue, and will do one of 3 things if the BIOS permits:
- self-limit USB drives to 128GiB/137GB if SpinRite cannot 'patch' the BIOS dynamically in RAM during SpinRite's run,
- work on the drive up to 2.2TB if the BIOS self-limits and if SpinRite can 'patch' the BIOS dynamically in RAM during SpinRite's run,
- work up to and beyond 2.2TB if the BIOS permits and if SpinRite can 'patch' the BIOS dynamically in RAM during SpinRite's run.
The key is 'if the BIOS permits'.
There's also a technical explanation as to the bit-depth of various BIOS USB controls that explains the problem, different across a variety of BIOS and years of production.
Yes, this possible limit on running SpinRite 6.1 to test USB drives most probably should be presented in the FAQ that is inside SpinRite 6.1 and here so that folks who cannot get SpinRite 6.1 to fully test a USB drive know the reasons, and are directed to a workaround:
- try a different computer,
- or if the USB drive contains an HDD or SSD, then try to 'shuck' the drive ( take it out of it's cabinet ), if possible, and attach the internal HDD or SSD directly inside the computer via the computer's own internal IDE/PATA/SATA connections.
Thanks.
.
Last edited:
Um, your display indicates that SpinRite is 100% complete... so I am unsure what specifically you're questioning?
@vmax5000 : What you're seeing is definitely weird. What's not so weird is that it's with a WD20EARS drive. During our testing, we encountered a bunch of bad behavior from that particular model of WD drive. That's not meant to excuse SpinRite for getting into the state it's in, but neither am I surprised that this happened with that drive.
I'm curious, though, why the Real-Time Activities screen shows so much data recovery activity...
Yet the map shows completely clean?? Did all of this activity appear at the very end of the drive, on that last "square" of the map? Thanks!
I'm curious, though, why the Real-Time Activities screen shows so much data recovery activity...
Yet the map shows completely clean?? Did all of this activity appear at the very end of the drive, on that last "square" of the map? Thanks!
Can I add to our list of FAQs? I may be dumb, but I really can't make any sense of the SMART values. Perhaps something that explains how someone interprets this information?
Edit: I didn't find this browsing GRCs SpinRite pages - google actually took me here. https://www.grc.com/sr/smart.htm
Edit: I didn't find this browsing GRCs SpinRite pages - google actually took me here. https://www.grc.com/sr/smart.htm
Hello Steve,
Long time listener of SN, had and loved SR6 for years... First time in the forums.
Recommendation: top 5 external drive testing "docks".
Since USB is space limited. Is external ESATA the way to go? Any better recommendations?
Maybe a Steve's approved tester base hardware kit?
Long time listener of SN, had and loved SR6 for years... First time in the forums.
Recommendation: top 5 external drive testing "docks".
Since USB is space limited. Is external ESATA the way to go? Any better recommendations?
Maybe a Steve's approved tester base hardware kit?
Until we get to SR7, USB should be avoided wherever possible. SRv6.1 is still stuck using the BIOS for USB. That will be one of the many welcome changes coming in SR7. The use of the BIOS, while not limiting the drive's size on newer BIOSes, prevents SpinRite from accessing any of the drive's quite useful "metadata". So any form of direct connect (to SATA) would be much preferred.
Yes. If eSata is available that will definitely be a plus.
There has been a lot of discussions of this since its release. It's known as the "ZimaBoard". The smallest one is likely all that's needed, for $119. I think that even Amazon offers it now. You would want the extra $4 "Y" adapter for SATA and you'll want to get a beefier 12V suppy if you want to power a pair of larger 3.5" spinning drives. MANY of SpinRite's testers have purchased these and it is my SpinRite development platform... so everything now and in the future will be guaranteed to run on it. It's a terrific little standalone solution!
Can we get a list of current options to run SR 61 under if we wanted to modify our AUTOEXEC.BAT file?
Thanks.
Thanks.
Hi,
Just got my hands on some old/used 36 x 3TB SAS drives to have a play with in the homelab, heard about SR from SN and so figured it was time for me to purchase.
I couldn't see anywhere on SR's FAQ page stating SAS as being supported and so just wanted to know before I purchased. I'll probably purchase anyway LOL.
I only saw SCSI mentioned when it comes to the low-level question in the FAQs.
I'm assuming SCSI and therefore SAS are supported, but just wanted to be sure is all.
ta
Just got my hands on some old/used 36 x 3TB SAS drives to have a play with in the homelab, heard about SR from SN and so figured it was time for me to purchase.
I couldn't see anywhere on SR's FAQ page stating SAS as being supported and so just wanted to know before I purchased. I'll probably purchase anyway LOL.
I only saw SCSI mentioned when it comes to the low-level question in the FAQs.
I'm assuming SCSI and therefore SAS are supported, but just wanted to be sure is all.
ta
That's because is isn't. Don't purchase it with the thought you can use it on this set of drives unless there is some way to proxy the SAS drives as something like IDE or SATA.
I purchased sr 6.1 but it doesn't boot from the memory I installed. I went to the memory and it has the data. I have XPS 8960 the BIOs has 3 booting 1 windows the other 2 (I forget their name) tried it/them, and booting goes to windows.
Why it does not boot from the memory?
Why it does not boot from the memory?
Similar threads
