Unable to boot into newly created USB thumbdrive

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

omry

New member
Apr 3, 2024
3
0
Hi,
I am trying to boot into SpinRite 6.1 (release 4) and I can't get my system to boot into the newly created bootable thumb drive:
This is what I did:
1. Installed on a as a bootable thumb drive ("Install SpinRite on USB") and tried to boot into it by changing the BIOS boot order. The system refused to boot from it.
2. inspected thumb drive content. seems ok.
3. tried a second USB thumb drive. still couldn't boot into it.
4. created a new Ubuntu bootable disk with Rufus (ISO mode) on the first thumb drive and booted into it successfully.

It looks like something is wrong with the created bootable thumb drive.
Any advice on how to proceed?
 
Welcome to the forums!

It appears that your computer is UEFI booting. That is NOT compatible with SpinRite 6.1 booting and running. A BIOS-DOS boot is required for that. I expect there is nothing wrong with your bootable thumb drive,

You need to go into the BIOS setup and look for a CSM setting. That would need to be enabled (and UEFI boot and Secure boot both disabled). Please see this article for more information:

 
Thanks, activating CSM solved it for me.
Unfortunately, SR 6.1 can't see my NVME drive, which was what I was hoping to scan.
I'll dig in the forums to see if there is a solution for that.
 
Unfortunately, the only thing you can do is try a different computer. SpinRite 6.1 relies on the BIOS for access to NVMe drives. SpinRite 7 will support NVMe natively.
 
The NVME is my boot disk so I will need to do this from a live CD. Not sure it's worth the headache for me.(I just want to see if It can improve the disk performance).
Do you do image backups?

If so, just do a new image backup and then immediately restore it. That would re-write (refresh) all data on the drive, effectively accomplishing what a SpinRite level 3 scan would do. Drive performance ought to improve noticeably. :)

Yes, a SpinRite level 3 scan would be much more comprehensive and thus desirable. But as been already noted in this thread, that will have to wait for SpinRite 7.

Note: Some systems BIOS are capable of seeing an internal NVMe drive as a BIOS drive. This would allow the drive to be SpinRite scanned albeit at very s-l-o-w BIOS I/O speed. You might take another look in the BIOS settings for something that would allow this (there may not be anything).
 
Welcome to the forums!

It appears that your computer is UEFI booting. That is NOT compatible with SpinRite 6.1 booting and running. A BIOS-DOS boot is required for that. I expect there is nothing wrong with your bootable thumb drive,

You need to go into the BIOS setup and look for a CSM setting. That would need to be enabled (and UEFI boot and Secure boot both disabled). Please see this article for more information:

That's so unfortunate.