Spinrite on Virtualisation Station

  • SpinRite v6.1 Release #3
    Guest:
    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.
    /Steve.
  • 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.)

ade_m

New member
Jan 29, 2021
2
0
Hi,

I've a USB backup drive that's connected to a remote QNAP NAS, that I think has some faults on it. The drive is configured with an NTFS filesystem.

The QNAP OS software doesn't have any tool or command I can find to scan the NTFS filesystem for erors.

But - it does have Virtualisation Station, a QNAP implementation. And I'm able to virtually connect the USB drive through to it.

I'm a long time user of Spinrite so thought I'd try booting a VM in that configuration.

But Spinrite tells me that the partition size doesn't match what the bios is telling it. Its an error I've seen many times on my laptop internal drive, and I've no idea why its telling me that. The BIOS is running in Legacy BIOS rather than UEFI.

If I boot a Gandalf ISO up, Windows within the VM is able to "see" the disk without any problem. I'm current scanning the sectors with another tool but I don't think it'll try any repairs.

If anyone has any idea as to why spinrite can't see the drive/partition in the same way as Gandalf, please let me know.

Thankyou!

(note: at the speed the 8TB drive is disk checking (5Mb/s), it'll probably be a few weeks before it completes, so no rush on any reply!
 
SpinRite 6 is limited to 2.2Tb - you'll be awaiting 6.1 eagerly (that may solve the issue, @Steve will know better, the method of connecting the drive might not work well but I do test most of my drives in a USB dock successfully (and slowly)).

https://www.grc.com/sn/sn-801.txt (search 2.2, it's the limitation of the addressing)
 
haha... my current scan says it'll take 406 hrs.. so maybe sprinrite 6.1 will be out before it actually finishes!

But yeah that makes sense then, its an 8Tb drive and will look forward to 6.1 (and 7!) Thanks for the replies folks.