RAID Use Case

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

lamwilli

New member
Feb 7, 2024
4
1
I am building a new workstation with TPM so I can run Windows 11. The motherboard features RAID. In my simple mind, I could set up a stripped RAID 1 SSD boot partition and a RAID 0 HDD data partition. My boot partition would be redundant and fast while the data partition would present a single huge logical volume.

Knowing that SSDs degrade over time, I plan to use Spinrite to periodically "refresh" the drives.

I don't want to break the RAID configuration on the workstation, so I expect to remove drives and attach them to an old system where I can run Spinrite.

Question: Can I use my m.2 and SATA to USB adapters to connect the drives from the RAID arrays in the workstation to the computer running Spinrite? If so, what are the caveats?

Many thanks.
 
SpinRite 6.1 is slower when testing a USB drive than when
testing a SATA drive.

SpinRite 6.1 may be compromised by BIOS access to less
than a full USB drive.

Some folks suggest doing a secure erase on a drive pulled
from a RAID so that any 'repairs' done to that drive do not
confuse the RAID when the drive is reinserted, instead, the
RAID reconstructs the missing data onto the blanked drive
when it is inserted, so secure erase may accomplish your
goals without needing to run SpinRite 6.1 to 'refresh' a
drive - your mileage may vary, a SpinRite 6.1 Level 3 that
does not engage DynaStat may allow reinsertion of RAID
drive without needing reconstruction, so try:

SPINRITE NORAMTEST LEVEL 3 DYNASTAT 1 NOREWRITE

The 'no rewrite' command line option tells SpinRite to
leave any impartially / unsuccessfully read sector 'as is',
letting the RAID decide what to do; if we get no such
sectors, we're good to go.

Personally, any SSD with failure to read successfully is
toast, and I'd move on from it.
 
Question: Can I use my m.2 and SATA to USB adapters to connect the drives from the RAID arrays in the workstation to the computer running Spinrite? If so, what are the caveats?
Possibly, but likely not. SpinRite 6.1, like its venerable predecessor SpinRite 6.0, is limited to accessing USB drives via the BIOS. Therefore, SpinRite will only be able to see what the BIOS can see, and access what the BIOS can access. In most cases that will be limited, problematic, and confusing.

See this thread for more info: https://forums.grc.com/threads/usb-support-in-spinrite-6-1.1479/