Spinrite Aberrant Error?

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

Confusered

Member
Oct 21, 2023
7
1
Was able to get spinrite 6.1 booted up fine following the "make a ReadSpeed bootable USB, copy the new Spinrite onto drive, escape at the ReadSpeed boot and just run Spinrite from the DOS menu" method, thanks to whomever suggested that. The new bootup for Spinrite is a little weird being so used to how instant 6.0 usually is.

Started scanning a known bad 4 terabyte disk, finally (damn it Steve ;)), and I guess it found the bad spot. Never seen this error before though, didn't see a mention of aberrant in the forums search.

PS...if you're going to have a picture size limit and put in a message that it's too large, you can at least comment what the size limit is in the message...which now isn't showing me an error for why it isn't uploading.
 
Was able to get spinrite 6.1 booted up fine following the "make a ReadSpeed bootable USB, copy the new Spinrite onto drive, escape at the ReadSpeed boot and just run Spinrite from the DOS menu" method, thanks to whomever suggested that. The new bootup for Spinrite is a little weird being so used to how instant 6.0 usually is.
Right... Though the user is rewarded with a LOT more information than they used to have. :)

Started scanning a known bad 4 terabyte disk, finally (damn it Steve ;)), and I guess it found the bad spot. Never seen this error before though, didn't see a mention of aberrant in the forums search.
I can see the need for a picture since I don't know what you're referring to!

PS...if you're going to have a picture size limit and put in a message that it's too large, you can at least comment what the size limit is in the message...which now isn't showing me an error for why it isn't uploading.
The problem is that today's smartphone cameras have so much resolution that 25 megabyte 4K resolution JPGs are often generated and people will just upload such images without taking the time to reduce the resolution to a useful size. It's massive storage that's being wasted and it then slows everything down. (Sort of like people throwing away large empty boxes in communal shared trash bins without taking the time to collapse the box. :( )

But I agree that any error message ought to tell you what the limit is! (These forums are still maturing since I created them in order to move SpinRite's technical support online and into a community.) I'll see about that! Thanks!!
 
  • Like
Reactions: Confusered
Right... Though the user is rewarded with a LOT more information than they used to have. :)


I can see the need for a picture since I don't know what you're referring to!


The problem is that today's smartphone cameras have so much resolution that 25 megabyte 4K resolution JPGs are often generated and people will just upload such images without taking the time to reduce the resolution to a useful size. It's massive storage that's being wasted and it then slows everything down. (Sort of like people throwing away large empty boxes in communal shared trash bins without taking the time to collapse the box. :( )

But I agree that any error message ought to tell you what the limit is! (These forums are still maturing since I created them in order to move SpinRite's technical support online and into a community.) I'll see about that! Thanks!!
The size of the picture started at just over 3 MB, I've now shrunk it twice and it says it's at 546 KB, it looks like it has uploaded, there's the icon to delete the upload, but the thumbnail is simply blank. Going to try to save as a copy, I'm on an android phone using Brave, if that helps anyone.
 
The size of the picture started at just over 3 MB, I've now shrunk it twice and it says it's at 546 KB, it looks like it has uploaded, there's the icon to delete the upload, but the thumbnail is simply blank. Going to try to save as a copy, I'm on an android phone using Brave, if that helps anyone.
Heyyyy...making it down to a tiny 132 KB seems to have worked, save as copy didn't help.
 

Attachments

  • 20231021_144244.jpg
    20231021_144244.jpg
    132.8 KB · Views: 171
Heyyyy...making it down to a tiny 132 KB seems to have worked, save as copy didn't help.
Looking at the Status Display, this didn't error on the bad spot, and the B is about where I expected it, and where MacrorITScanner consistently showed it over the years. I think their scanner is equivalent to Spinrite level 2, but nothing beats your level 4.
 
Yup. Those of us who have been testing SpinRite v6.1 have grown familiar with that error message. And as SpinRite suggests... it's not supposed to happen. :-/

It looks like it got 73.7594% into that 4TB drive. So you could exit SpinRite (no need to power-cycle or reboot) then restart the work on that drive at 73.74% of the drive to see whether it occurs again. If so... there really IS a problem there. Running a level 5 over that spot might resolve it. That's what I'd try.

For today's massive drives, SpinRite's percentage and sector range operations become much more important! (y)
 
  • Like
Reactions: Confusered
Yup. Those of us who have been testing SpinRite v6.1 have grown familiar with that error message. And as SpinRite suggests... it's not supposed to happen. :-/

It looks like it got 73.7594% into that 4TB drive. So you could exit SpinRite (no need to power-cycle or reboot) then restart the work on that drive at 73.74% of the drive to see whether it occurs again. If so... there really IS a problem there. Running a level 5 over that spot might resolve it. That's what I'd try.

For today's massive drives, SpinRite's percentage and sector range operations become much more important! (y)
I swear I googled and searched and saw nothing for Aberrant before hopping on here.

I wish I saw that it was plugged into a SATA 2 port 73 hours ago...could you pop up a warning for that? Because 11 hours estimated time in the speed test benchmark after the fact feels a little, you know...late. Thanks for the quick reply and assistance sir.
 
The size of the picture started at just over 3 MB, I've now shrunk it twice and it says it's at 546 KB, it looks like it has uploaded, there's the icon to delete the upload, but the thumbnail is simply blank. Going to try to save as a copy, I'm on an android phone using Brave, if that helps anyone.
Just an FYI... The forums will shortly have full "auto image resizing" in place so that images of any practical size can be uploaded and they will be auto-resized for the storage and display from then on. (y) Thanks for bringing this up. As I said... The forums are still maturing based upon our users' feedback. So thanks for it!
 
I swear I googled and searched and saw nothing for Aberrant before hopping on here.

I wish I saw that it was plugged into a SATA 2 port 73 hours ago...could you pop up a warning for that? Because 11 hours estimated time in the speed test benchmark after the fact feels a little, you know...late. Thanks for the quick reply and assistance sir.
There actually is a warning for that. If you peruse the selected drive's properties, if a SATA 3 capable drive is attached to a SATA 2 port, SpinRite will highlight that in RED in the UI. (y)
 
I swear I googled and searched and saw nothing for Aberrant before hopping on here.

I wish I saw that it was plugged into a SATA 2 port 73 hours ago...could you pop up a warning for that? Because 11 hours estimated time in the speed test benchmark after the fact feels a little, you know...late. Thanks for the quick reply and assistance sir.
There actually is a warning for that. If you peruse the selected drive's properties, if a SATA 3 capable drive is attached to a SATA 2 port, SpinRite will highlight that in RED in the UI. (y)
After I rebooted and restarting the scan for the 4th time trying all of the ports, I finally noticed the bit of red on the side, go figure. I apparently I wear glasses just for the style. I was expecting a popup of sorts like with your old gpt warnings and the such. Very nice, cheers. 😁
 
  • Like
Reactions: GBark
After I rebooted and restarting the scan for the 4th time trying all of the ports, I finally noticed the bit of red on the side, go figure. I apparently I wear glasses just for the style. I was expecting a popup of sorts like with your old gpt warnings and the such. Very nice, cheers. 😁
Right. I agree that it's not "in your face" — but it's meant to be more informational since it's not a critical error. And also since most “Spinners” will do as well with SATA2 as with SATA3. (y)
 
Right. I agree that it's not "in your face" — but it's meant to be more informational since it's not a critical error. And also since most “Spinners” will do as well with SATA2 as with SATA3. (y)
Can confirm, after trying it on 2 other Desktops laying around, one didn't even show what speed the port was running at, but looked just as slow. But I found one that didn't give an error, showed it was SATA 3, and it's still just as slow. 5400 RPM isn't doing it any favors. I'm still amazed that after the dozen times I ran it through MacrorIT and it showed the sector as bad, once Spinrite slated it as bad, the drive finally knew it was bad. Couldn't find that location as bad again on the other three level 4 passes I ran over it. Spinrite is ridiculous, amazing, and HDD will forever be a pain.
 
I'm still amazed that after the dozen times I ran it through MacrorIT and it showed the sector as bad, once SpinRite slated it as bad, the drive finally knew it was bad. Couldn't find that location as bad again on the other three level 4 passes I ran over it. SpinRite is ridiculous, amazing, and HDD will forever be a pain.
Nice! Just what we want — SpinRite magic sauce! (And just WAIT 'till you see what SpinRite 7 will show you about SSDs! (y)
 
  • Like
Reactions: Confusered
Yes, you will have power cycle the drive some how, or at least I had to when I was experiencing this problem,
There are two very similar ”Big Red Boxes”. The Drive Fault screen definitely requires a power cycle of the drive itself. But the “Drive has stopped responding“ box generally does not.
 
Drive has stopped responding
Hmm, maybe it changed during development, but that box looks like the one I remember, and I could never get the drive to recover. I also assumed you (as SpinRite) couldn't either, or else you would have done whatever it took to recover the drive... ? In any case, we need pictures of all the various screens in some sort of a database, with a description of each, so people can find the screen that matches and maybe learn from the associated notes/help.
 
  • Like
Reactions: Steve