Just got a new motheroboard/cpu in today and it booted up fine. (had a little trial and error, here and there, but it was working)

 

I shut down to do a Bios upgrade and tweak a few settings before calling it good. In doing so I cancelled a parity check and  stopped the array (or tried to). It seemed to freeze up while shutting down the docker, so I just hit the power button.  I did the bios update and when I restarted it froze just after "loading bizroot... ok"

 

I tried rebooting... same effect.

 

I took the drive and tried copying bzroot and bzimage files over the top of the existing ones (though I screwed up and pulled them from my unRAID 5 backup). Either way, it booted, though to my old unRAID version 5 webui.

 

So I took the drive back, and transferred the bzroot and bzimage file off from the latest 6.1.8 download (that's what I was running pre hardware upgrade.) Booted it up and it froze at the same spot again.

 

I tried a bunch of different methods, even a full Clean install of 6.1.8, and all of them freeze at the same spot during boot. (even the clean install!  wut???)

 

What's really wierd, I copied back the backup I made before I started formatting the drive and copied the bzroot bzimage from the old version 5 backup back onto the drive, and it boots up just fine again. WTH?

 

I'm starting to think the I missed a BIOS setting or the new BIOS isn't playing nice with version 6.  Any other thoughts?

 

I'm running the ASRock Z170 Extreme 7 +

 

Luckily it has 2 BIOS chips (one of which I didn't upgrade)!  I'm going to load my ver 6 update back onto the drive, switch to the second chip and see if it works. I'll report back my findings. In the meantime, I'm open to any other suggestions.

have you tried to repair the usb drive on a windows machine??

Yep... Ran the error checking tool several times.

 

After some experimenting, turns out it's a little bit of both!  I loaded the drive up with a completely clean install of ver. 6.1.8 and tried it on the secondary BIOS (with the original BIOS version that shipped with the board) with all of the same settings and it booted completely fine. I then tried loading in the Backup I did early (after I started having trouble) and no dice. I went back to the clean install and added the ident.cfg, network.cfg, shares.cfg, and shares folder (from the corrupted backup) to the config folder on the drive and it booted completely fine again!

 

I then switched back to the primary BIOS and no go...  Only seems to want to work with the default BIOS.  Oh well.

 

Either way, I'm just going to go ahead and start from scratch (sorta) since it seems to be working now. I went ahead and reassigned the drives to their correct orders (whoever said to take a screen capture of the various settings screens was a genius! lol) and have it running a Parity Check right now. When it finishes I'll go ahead and reverify all of the other pages and then try to get my docker and plugins back to working... which will bring up my next issue:

 

All I was running via the docker was an Emby Server and a Plex Server. All of the data they downloaded and used is still on the drives, as well as the docker.img file. Do I have to just scrub all of that and start from scratch again with both or do I just set it up with the same media locations and it should work again?  If I just need the same media locations I used when I initially set up the Emby and Plex dockers, Is there anyway to get that info from my old backup (since I'm not entirely sure I have a screen cap of either of those pages)?

Once you re enable docker and point the system to the image, everything will be back the way it was

 

Brilliant! That worked perfectly! 

 

I had to find the github repository links again, but they seem to both be working as before, now.  Thanks for the help.

Brilliant! That worked perfectly! 

 

I had to find the github repository links again, but they seem to both be working as before, now.  Thanks for the help.

 

Install the Community Applications plugin and you won't need to worry about github repos...

Hahaha... I guess not.  I've been running unRAID for over 6 years now and it's only been during the last month or so that I'm really starting to learn some of the cool tricks! 

 

My next project is going to be to setup a virtual machine I can run via remote access.  I think it would be extremely handy for network Based Graphics rendering, processing, and the like.

 

I just threw a 240GB SSD in as a cache drive. Should I transfer the location of my docker.img and emby/plex configs to that to increase performance of those two apps?

Seems a logical thing to do to me mate... 

 

Run docker.img and your appdata share off the SSD cache.

 

Don't forget when setting it up to make sure that the appdata share is set to Use cache only...

lol... what did you get me into?  Started the move of my Appdata folder too the cache drive.  366,376 scanned files later it's finally started moving the stuff! The one thing I absolutely hate about plex is the fact that it stores all it's metadata in the install/config directory instead of in the individual media locations like Emby does... In fact, why doesn't it just use that meta data!  hahaha

 

Other than that, this should (hopefully) really speed up Emby/Plex Server loading and browsing! 

 

 

edit:  So It took two and half hours to transfer 19GB via Midnight Commander... granted that was broken up into some half a million+ files. I moved the docker.img (10GB) and it took all of 30 seconds. hahaha 

 

On the upside, both apps are now lightning fast! It used to take the movie pages awhile to populate the posters and details, etc...  Now it's instantly there. No Lag! Gotta love it. Thanks a ton everybody. this is so much better than it ever was before. 

I don't suppose you have a ASRock Z-170 Motherboard do you? I encountered the same sort of bios issue as you with my recent upgrade.

I don't suppose you have a ASRock Z-170 Motherboard do you? I encountered the same sort of bios issue as you with my recent upgrade.

 

Yep, Z170 Extreme 7+.

 

Gotta love the dual BIOS chips. Flip a switch and problem solved. The default p1.70 has been working perfect with all my components so far. The latest, 2.6, only seems to have an issue with unRaid 6. I haven't tried any BIOS versions in between, but might give it a shot this weekend if I get bored. Of course this time I'll make a proper backup before I start goofing around with things! Haha

I sent ASRock a support email through their website about this, along with asking for clarification about whether PCIe Gen3 and NVME being the same thing. I never heard back.

 

I own the Extreme4 btw.

Weird... Then it's obviously an ASRock issue since it's doing it on two (while similar) separate boards.  Wonder what the cause could be?

Unraid doesn't support UEFI afaik only legacy...

Even so, the factory installed BIOS is UEFI and it works. I also can't find a single different setting I could make between the old and the new version that would make a difference. Configured every setting exactly the same for both versions. And it doesn't lock up till after it's loaded bzroot. Oh well... as long as it IS working now, and I don't have any real need to upgrade to the newest BIOS, then I guess it doesn't matter.