February 11, 201610 yr I ran an update from 6.1.6 to 6.1.7 from the web interface. Everything seemed to go fine, when I rebooted the server, it went through it's normal boot process. But at some point along the way, the text starts to glitch out. I attached a screenshot. Furthermore, the web interface doesn't look right either. I've rebooted the server and the same thing happens. The data appears to be fine. Any ideas? Do I dare manually upgrade to 6.1.8 (if I can remember how)?
February 11, 201610 yr Sounds like bad RAM to me. I think the update was coincidental. Could it also be corruption of the Flash drive file system?
February 11, 201610 yr Sounds like bad RAM to me. I think the update was coincidental. Could it also be corruption of the Flash drive file system? Console corruption makes me think RAM. I guess maybe if the console fonts are reloaded from the flash at some point in the boot process? Temporarily booting just the USB stick in another box and looking for console corruption would be a good test.
February 11, 201610 yr Author Sounds like bad RAM to me. I think the update was coincidental. Could it also be corruption of the Flash drive file system? Console corruption makes me think RAM. I guess maybe if the console fonts are reloaded from the flash at some point in the boot process? Temporarily booting just the USB stick in another box and looking for console corruption would be a good test. Here's a dumb question, should I have a plugin for dynamix in my Plugins folder? Not sure if that was brought over from my 5.0.x upgrade, but from what I've read Dynamix webGUI is now built into 6.0. The errors shown on the web interface point to "/boot/config/plugins/dynamix/dynamix.cfg" and other Dynamix issues. Maybe it's just a display issue from that? Not sure what the file is suppose to look like, but I attached the corrupt text looking .cfg file. Or do you think it's still a possible RAM issue? dynamix.cfg
February 12, 201610 yr * I agree with jonathanm, bad RAM is a strong suspect, and when RAM is even remotely suspect, then you don't want to do *anything* else with the machine, until it can be fully trusted. Using the machine in any way could be causing more stuff to be corrupted, if there's bad RAM. MemTest is imperative, before anything else. * That dynamix.cfg has been overwritten with binary garbage, so you don't want it, needs to be deleted. It will be recreated on the next boot. * The OS after attempting to load looks severely corrupted, possibly because of the RAM, and possibly because files on the flash drive have been corrupted. It would be a good idea to manually reinstall unRAID on it, and might as well use the latest - v6.1.8. - I would first run a check disk on it on a Windows or Mac station - Make a backup copy of the config folder from the flash drive, and add any other files from the flash you want to save (or just backup the whole flash) - Download the 6.1.8 zipped distro from the LimeTech Download page (from the first post of the Announcement) - In the root of the zip is install.txt, containing instructions for preparing a new flash, including formatting it, running make_bootable, and extracting the whole distro to it - Now you can carefully and selectively copy back files and folders from your saved config folder, but you should carefully examine them first. Practically everything in the config folders is an ordinary text file, except for super.dat, your .key file(s), image files, and .txz files. Use your common sense. If you open and view them, there should be nothing but plain text. If not, I'd delete it, and let the system recreate it, or reenter its settings yourself, once back in operation. In some cases, it may be simpler to drop whole plugin folders, and reinstall them later. The only file that concerns me is super.dat, because it's a binary file already, and the system writes to it, so you may not be able to detect corruption in it. A recent backup may be useful, if no major array layout changes, or you may have to run New Config and reassign everything. - If you haven't already, after reinserting the cleaned-up flash drive, run MemTest first, and replace memory as needed. - Boot and check EVERYTHING! Reenter whatever is needed. Hopefully, that should get you back up. I'd wait a half day at least, so others can check my steps - I occasionally forget important parts! Edit: There's one other remote possibility, the video card is going bad or is too hot, a failed fan. Looks much more like RAM corruption though.
February 13, 201610 yr Author Thanks for the tips guys. Here's what I did. I deleted the folders /config/plugins/dynamix and /config/plugins/dynamix.kvm.manger and the web interface immediately turned back to normal. Then I did a reboot on the server, and everything looked correct again (no jumbled up/corrupt looking text). I'm going to run a parity check (it did say the last check found 42 errors!) and continue to monitor things a little closer to make sure it isn't bad RAM. Since my issue only started right after I did the update, I'm wondering if something got corrupt during the update on the Dynamix side of things. For now, I'm going to mark this as resolved and cross my fingers it's nothing major.
February 13, 201610 yr I can't stress enough that you need to do a Memtest before *anything* else! Memory corruption is not always immediately visible. It's a great thing when it's as visible as you saw, because you stop immediately, before more damage is done. Now it could be silently corrupting parity, or something else.
February 14, 201610 yr Author Okay, I ran 10 passes of the Memtest86+ and it found 0 errors. So maybe it's not the RAM. Any other suggestions to try? It does appear to be running smooth now. A parity check found 0 errors.
Archived
This topic is now archived and is closed to further replies.