TedatTNT

I'll be following this thread with interest!

I've updated to 6.2.0 beta 18 and tested. So far, I have not had this problem. I'll continue to monitor and report back.

When it fails to load with a kernel error, it says: Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) Does anyone know what this means?

*Bump.

Okay, I've tried these steps - twice. Copying the bzroot-gui file was the easiest, so I started with that, even re-downloading the zip and copying it over. And, in addition to reformatting, I tried a different flash drive -- still no help. It doesn't load enough to have anything logged that I can post. The best I can offer is a video of it failing to fully load: https://www.dropbox.com/s/oh139mvkzu4xhef/Unraid.mp4?dl=0 Thanks, Ted

Yeah, that was issue #1. But, after manually copying it, I ran into the other issue, and had to hard-power-down the server as it was locked. Even after copying it over, I cannot successfully boot into the GUI mode.

I'm having issues with the Unraid GUI. First, I was running 6.x (not sure which version). I then initiated the installation using these instructions from the 6.2 post: ...and then I went to the Flash syslink config and moved the "default" line to the GUI mode section. After rebooting, I was stuck in a boot loop, trying to launch bzroot-gui, but never getting the OK -- just back to the options page with a timer before launching the default. I intervened by selecting the non-GUI version. I checked the flash drive, and found that bzroot-gui was missing from the flash drive. I downloaded the zip file and manually copied it over. I rebooted again. This time, there was no boot loop. Things began loading and then the last lines were: Kernel Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) I am still able to reboot in the non-GUI mode, but but GUI mode does this every time. Ideas?

Send us an e-mail on it. I'll need to have Tom look at it. I've not heard anything back -- should I be expecting an email?

Okay, I was finally able to copy the syslog from the console. It is attached. syslog-2016-03-09-003.txt

Send us an e-mail on it. I'll need to have Tom look at it. I sent an email with a link to this thread.

Drives are 34 - 39 degrees Not sure how to find the CPU temp. There is an addon for it, but you aslo need to install nerd pack and perl from the nerd pack. I just got a heat warning for one drive - 46 degrees.

Silly question... How do I send a message to support? Is there a forum username that I use?

Yes, the dual NIC's are the Marvell Yukon 88E8053's. I have the some issues no matter which is being used. Is there a HIGHLY recommended GB LAN card that I could purchase and test with? I'm asking because the Marvell Yukon's are on the hardware compatibility list.

Okay, I've collected some video -- I'm hoping that this helps. I've edited it down to a 4-minute file and added a few notes and I'm hoping that for somebody, it will be clear what is going on. I can't attach a video here, so this is a link to the video on Dropbox... https://dl.dropboxusercontent.com/u/53914472/UNRAID-001.mp4 Thanks in advance... Ted

When I went to take a photo, the lines were changing pretty quick, so I missed a bunch of them -- should I do it again -- maybe shoot video? Ted So, very strange... It only took a moment to make it freeze before -- just accessed a few files and hadn't even begun the Parity Check. This time, with a video camera recording the screen, I have transferred dozens of GB's of data and been running a Parity Check concurrently and it hasn't failed. I even tried accessing identical files. It seems that the fix is to keep a video camera recording the screen -- that was easier than I thought.