Export thread

  • SpinRite v6.1 Release #3
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • 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!

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

HDD problem?




Greetings all!

Sorry for the lame title, but for the life of me I can't remember what the problem was called.

It was on a podcast episode some time back. HDD manufacturers were using some kind of lame tech that made their allegedly high-performance HDDs suck. Western Digital was doing it along with some others, and apparently even some of their Black line of HDDs had the problem.

I need to buy a new HDD, and I've been buying WD Black HDDs for many, many years, so I want to get a new one... but I want to make sure that I get a good one.

Does anyone remember what the issue was actually called? If I could figure that out, I could search around a bit more and make sure that I get a drive without it...





SMR - Shingled Magnetic Recording
There was some discussion on SMR on Episode #800, Jan 05, 2021.







Ahh, yeah, that was it.


Now, to find out if the drive I was looking at has it or not... thinking about that Black 10tb HDD...




Looks like it's CMR...





Also, don't go with a hybrid drive - part SSD and part HDD. I think those were a boondoggle and often the SSD part would be too small and would bottleneck large transfer performance. And the SSD piece wears out fast.

May your bits be stable and your interfaces be fast. :cool: Ron




When I try to boot my acer laptop with an older HGST 55Gb drive (spare) installed (which I hope to re use) I get a message indicating the hdd is password locked... I have no idea what the pw may be and cannot get a into bios or boot menu. Tried to initialize the drive with Windows 10 disk management and tried formatting with mini-tool partition wizard, with diskpart which reported an error finding the volume... Any advice will be much appreciated! ;-)




hdd is password locked
Sounds like a previous computer's BIOS applied some sort of a lock to the HDD. I believe there is an ATA command which can override the drive lockout by wiping it clean, but I don't know which, if any tools, support invoking it. Hopefully someone who has some actual experience with this type of problem will post something helpful.




There may actually be a password set by the drive firmware, not by the prior system’s BIOS/firmware. Maybe the “sanitize block erase” command will work




Try wiping the drive with Darik's Boot and Nuke (DBAN).




I haven't had occasion to use it, but Verawipe ( https://sourceforge.net/projects/verawipe/ ) might be another good option for a disk wipe.