Issues running SpinRite 6.1 Rel 2 on Zimaboard
- Thread starter the_physio
- Start date
- Watchers 9
-
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.)
I think Steve is writing a good utility to find flaky memory, which Memtest does not find.........
Might find a place in the free software library as a memory test utility, and could even be integrated into the ISO Steve is offering as well, as part of the Freedos suite, and included in the menu.
Might find a place in the free software library as a memory test utility, and could even be integrated into the ISO Steve is offering as well, as part of the Freedos suite, and included in the menu.
@the_physio: Just a note that with SR61-RT5 it's no longer necessary to stop and restart it since RT5 now has an error counter (like MemTest86) which will allow you to just let it keep going. 
New functionality of -RT5 now noted.
The third test results was left running overnight & produced 2 errors (refer to SR61-RT5c.jpg) after running for a period of between 10:30:00 & 12:58:02.
I have restarted a fourth test (sorry I didn’t read the above post before doing so) & as a new testing strategy I was intending to restart it every hour. @Steve do you think there is value in that or would you rather I just leave it running uninterrupted?
The third test results was left running overnight & produced 2 errors (refer to SR61-RT5c.jpg) after running for a period of between 10:30:00 & 12:58:02.
I have restarted a fourth test (sorry I didn’t read the above post before doing so) & as a new testing strategy I was intending to restart it every hour. @Steve do you think there is value in that or would you rather I just leave it running uninterrupted?
Attachments
Its definitely "odd" that one time MemTest86 showed 6 errors and the next time 101. But "in theory" there should be no reason to stop and restart. Nothing should be different.
Okay, I'll leave the Zimaboard running -RT5 & do an hourly check to see how many errors have acculated - after 4 hours there are currently 2.
Is there any value in photographing the errors (eg showing which "Erroneous bits found")?
Is there any value in photographing the errors (eg showing which "Erroneous bits found")?
@the_physio conscious that you may be running out of a return window depending on how recently you got the Zimaboard. You may have to jump through a few more hoops. Might be worth at least emailing their support and kicking off an RMA case which might buy you some time.
Agreed. We've learned what we need to from that board. THANK YOU for all the terrific testing. But if you can get it replaced, there's no reason to wait any longer!
@the_physio: If you have the time and inclination, I've created another test to see whether this one might be more adept at inducing and detecting RAM errors on your ZimaBoard. Since we don't have any theoretical model for what's going on, we're reduced to trial and error. But before you lose access to your ZimaBoard, if you are planning to return and replace it, I'd love to know whether this -RT6 might be a superior problem detector. Thanks!
Thanks for the advice about returning the Zimaboard, but I did purchase it back in 2022 as I wanted to have it so I could hit the ground running when 6.1 was released. So I think the ship SS Warranty has well & truly sailed – correction – it’s sailed, arrived, disembarked, been towed out to sea, & skuttled to become an artificial reef for the sea life.
Let me know if you’re still interested in doing a swap with it otherwise, I’ll try & think of some use that isn’t “mission critical”.
I’ve aborted the -RT5 test – after 9 hours it still hadn’t come up with more than the 2 errors it had after 3 hours.
-RT6 is now running & I’ll keep an eye on it every 15 minutes or so & let you know how it goes.
Let me know if you’re still interested in doing a swap with it otherwise, I’ll try & think of some use that isn’t “mission critical”.
I’ve aborted the -RT5 test – after 9 hours it still hadn’t come up with more than the 2 errors it had after 3 hours.
-RT6 is now running & I’ll keep an eye on it every 15 minutes or so & let you know how it goes.
I have a feeling that as a first thing, you might want to use a different PSU on that board, before doing the sailing off via post. Use a new 12V 5A power supply, probably best to buy Meanwell, as they are cheap, quite good units, and 12V 5A is a very common one. you will need to sacrifice the existing cable to connect it, and also an IEC lead, plus look into a box to enclose it, as it is not exactly meant to be used open, but it does often get specced in industrial use. Then run the test again, and see if there is a difference, plus a 5A unit will work well for doing 2 spinners at once, and you do get dual output ones that provide a 5V supply and a 12V supply, so the drives can have their own 5V supply as well.
is an example, and there is US stock of it.
Otherwise
12V 6A, well capable of powering a few HDD units, though only a single 12V output, but most of the draw of a hard drive comes off the 12V rail.
is an example, and there is US stock of it.
Otherwise
12V 6A, well capable of powering a few HDD units, though only a single 12V output, but most of the draw of a hard drive comes off the 12V rail.
Okay -RT6 has been running for 3 hours now. It picked up 1 error in the first 15 minutes & then no more thereafter.
I feel like making an executive decision & starting another test to see if it picks up something early in the cycle - I know it shouldn't but there is almost a pattern of this happening. If it's zero after an hour or two then I'll turn it off & let it cool down before doing a rinse & repeat to see if it picks up something early from a cold start. Again, let me know if there is value in posting images of the error screen otherwise I'll just update with text.
I feel like making an executive decision & starting another test to see if it picks up something early in the cycle - I know it shouldn't but there is almost a pattern of this happening. If it's zero after an hour or two then I'll turn it off & let it cool down before doing a rinse & repeat to see if it picks up something early from a cold start. Again, let me know if there is value in posting images of the error screen otherwise I'll just update with text.
@the_physio: Text only is fine. Just the number of errors found. And anything you feel like doing along the lines of “executive decisions” will be terrific. We're all just feeling our way along here. If RT6 doesn't perform obviously better than RT5, and certainly if RT5 seems to do better, which it might, I'll stick with RT5 for SpinRite's final use. Thanks!
An interesting update on the SR61-RT6.EXE to share.
Executed a new “warm” run (ie the Zimaboard had been running for the better part of the day & was warm to touch) of -RT6 & produced 1 error around the 2:20 (2 hour 20 minutes) mark. I left it running until 3:00 without any new errors.
As promised, I turned off the Zimaboard for an hour & executed a “cold” run (ie the Zimaboard was now cold to touch) of -RT6. 4 errors were reported within 10 seconds. I left it running for until 3:00 (3 hours) without any new errors.
Repeated the turn off, cool down, & execute -RT6 cycle. 3 errors reported within 15 seconds. Left it running for another hour but no new errors.
Repeated the turn off, cool down, & execute -RT6 cycle for the third time. 3 errors reported within 2 minutes. Left it running for another hour but no new errors.
It’s a small sample set, but anecdotally for THIS Zimaboard at least the -RT6 appears to be much more sensitive when it’s cold. Indeed the “return on investment” of running -RT6 on THIS Zimaboard for longer periods once it’s “warm” is questionable.
Whether this is indicative of all memory issues I have no idea but I’d certainly recommend running -RT6 from a cold state. I’m wondering if the large variations in MemTest86 results were affected by the temperature of the Zimaboard – to be honest I can’t remember if the board was warm or cold when I ran those tests.
I'll repeat the cold test with -RT5 a couple of times to see how it goes & then I’m inclined to run the MemTest86 again from cold & warm to see how they compare too.
Executed a new “warm” run (ie the Zimaboard had been running for the better part of the day & was warm to touch) of -RT6 & produced 1 error around the 2:20 (2 hour 20 minutes) mark. I left it running until 3:00 without any new errors.
As promised, I turned off the Zimaboard for an hour & executed a “cold” run (ie the Zimaboard was now cold to touch) of -RT6. 4 errors were reported within 10 seconds. I left it running for until 3:00 (3 hours) without any new errors.
Repeated the turn off, cool down, & execute -RT6 cycle. 3 errors reported within 15 seconds. Left it running for another hour but no new errors.
Repeated the turn off, cool down, & execute -RT6 cycle for the third time. 3 errors reported within 2 minutes. Left it running for another hour but no new errors.
It’s a small sample set, but anecdotally for THIS Zimaboard at least the -RT6 appears to be much more sensitive when it’s cold. Indeed the “return on investment” of running -RT6 on THIS Zimaboard for longer periods once it’s “warm” is questionable.
Whether this is indicative of all memory issues I have no idea but I’d certainly recommend running -RT6 from a cold state. I’m wondering if the large variations in MemTest86 results were affected by the temperature of the Zimaboard – to be honest I can’t remember if the board was warm or cold when I ran those tests.
I'll repeat the cold test with -RT5 a couple of times to see how it goes & then I’m inclined to run the MemTest86 again from cold & warm to see how they compare too.
Here are the results from running three cold tests of SP61-RT5.EXE:
- Test#1: within 60 seconds – 6 errors; no further errors for next 30 minutes (when test was stopped).
- Test#2: within 20 seconds – 1 error; within 3 minutes – 12 errors (in total); no further errors for next 30 minutes.
- Test#3: within 5 seconds – 1 error; within 3 minutes – 2 errors; within 7 minutes – 3 errors; within 13 minutes – 4 errors; no further errors for next 30 minutes.
This is perfect, @the_physio! It appears that what we had with RT5 is catching plenty of problems, at least as well as RT6. And RT5 is much cleaner and simpler.
You’ve also clearly shown that on your machine this is a cold machine issue.
You’ve also clearly shown that on your machine this is a cold machine issue.
I'd agree that RE-testing with an alternative power-supply would be wise before counting our metaphorical RAM error chickens.
Even with the now evident temperature sensitivity that you've discovered in your excellent tests @the-physio, it's equally probable IMO that if the power-supply block (the 'power puck' etc.) is somehow below par, its voltage stability or current capacity could vary with changes in temperature ... given that it too would cool down and warm up in tandem with the ZimaBoard itself.
Colin P.
Hey Colin (@CSPea):
I'm pretty certain that this was one of the first things that was suggested and that @the_physio did try using a beefier power supply. But otherwise, definitely a good thing to rule out!
I'm pretty certain that this was one of the first things that was suggested and that @the_physio did try using a beefier power supply.
But otherwise, definitely a good thing to rule out!Similar threads
- Contains 1 staff post(s)
