October 23, 20241 yr I have an older unraid box that's been used only as cold storage (with regular parity checks and drive replacements) and almost never connects to the internet (can't think of any times this decade outside of unraid upgrades in recent years). As a result, it rarely gets updated. I wanted to add the Parity Tuning Plug-In to this box so I could pause and resume with shutdown during extremely long parity checks (dual parity, larger drives). I checked the forum announcements in the 6.9s and 6.12s and didn't see any obvious warning flags about upgrading directly from 6.8.3 to the newest release through the unraid GUI, so I backed up my flash drive, pulled diagnostics, and gave it a shot. Upon installation, the unraid GUI prompted me to reboot my system. I did that, and the screen's hanging at a blinking cursor. I'm thinking the boot order may have been changed by my BIOS automatically, but I'm hesitant to just shut it down at this point without checking in here first. Is there some massive mistake I could have made in upgrading directly from 6.8.3 to 6.12.13, (that I should try and fix now before shutting down or rebooting to try and change my boot order in the BIOS)? Thanks so much in advance for any guidance anyone can provide! Edited October 26, 20241 yr by wheel
October 23, 20241 yr Take my advice with a grain of salt... my first thought goes to a bad USB... I have had a number of them go bad recently(rarely used USB) I dont think you are at any risk if/when powering it off... To be clear, you are able to access the unraid webpage on the box? That's how you were able to pull diags, right? IMO, take a screenshot of the array(recording the drive order), power down the system, backup the USB, format the USB, reimage the USB, and start the array again with the drives where they should be... perhaps also validating the USB is healthy before reimaging... Though this is the nukelier option... Please wait for others to post what they would do, but my mind goes straight to the USB as being at fault
October 23, 20241 yr Author I *was* able to access the unraid webpage when upgrading to 6.12.13, and I pulled diagnostics as a safety measure then. The boot process is hanging at some point (I didn't see how far it got on screen before hanging at the flashing cursor). I can't really pull any new information without a reboot or power down (and maybe not even then). Thanks for the response!
October 23, 20241 yr Community Expert Shut down the server. Then pull the USB drive and plug into a PC. Make a backup of the disk/drive. Then run chkdsk on it even if you can't copy all the files off of it. Report back on the results. Edited October 23, 20241 yr by Frank1940
October 23, 20241 yr Author Volume UNRAID created 6/30/2012 1:40pm Volume Serial Number is *** Windows is verifying files and folders... File and folder verification is complete. Windows has scanned the file system and found no problems. No further action is required. (Disk space allocation numbers)
October 23, 20241 yr Solution Simply put... If it doesnt boot... you cant access the OS to make any changes... You could try to build a separate USB to boot to, validating that the mobo/cpu/ram is good. If it does boot then it's simply the old USB that needs to be reimaged and or replaced
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.