I just noticed that all the files on my unassigned drive are missing, the drive is totally empty, according to the unassigned drives tab in unRAID.  I opened a console via putty, opened Midnight Commander and navigated to the shares and the cache, user and my unassigned drive all show in red with a question mark to the left of them.

 

I assume this is a bad thing, but what exactly does it mean?

 

I had a drive fail to write yesterday, so it's been using an emulated drive, and I just recently removed it, started the array, stopped the array, added the same drive back to the missing slot and restarted the array, causing it to rebuild the drive.  While it was doing this, I tried to start a VM and it couldn't (which is how I discovered the unassigned drive issue).

 

Are these drives just going to be unavailable while the drive rebuilds, or are they jacked up for good now?

 

**I suspect this all has to do with my enabling the ACS override to allow my second video card to be used in a second VM.  I really, REALLY regret buying a second video card, larger SSD and more memory only to find out I can't use them for the VM I intended without compromising my server integrity. so sad.

I just noticed that all the files on my unassigned drive are missing, the drive is totally empty, according to the unassigned drives tab in unRAID.  I opened a console via putty, opened Midnight Commander and navigated to the shares and the cache, user and my unassigned drive all show in red with a question mark to the left of them.

 

I assume this is a bad thing, but what exactly does it mean?

 

I had a drive fail to write yesterday, so it's been using an emulated drive, and I just recently removed it, started the array, stopped the array, added the same drive back to the missing slot and restarted the array, causing it to rebuild the drive.  While it was doing this, I tried to start a VM and it couldn't (which is how I discovered the unassigned drive issue).

 

Are these drives just going to be unavailable while the drive rebuilds, or are they jacked up for good now?

 

**I suspect this all has to do with my enabling the ACS override to allow my second video card to be used in a second VM.  I really, REALLY regret buying a second video card, larger SSD and more memory only to find out I can't use them for the VM I intended without compromising my server integrity. so sad.

ACS wouldn't have anything to do with this.  You should be posting this probably in the unassigned devices plugin thread as it sounds like this isn't happening to any of the devices managed by the OS itself.

It seems to have been related to unRAID rebuilding the missing/emulated drive.  Once that process finished and I rebooted the server, all the drives were back to normal again.

 

FWIW, it was also affecting unRAID managed drives, it affected the cache drive and the users share listing in Midnight Commander.

 

Either way, it's back to normal now.  (I did turn off the override setting, so I'll have to find another way to run my second VM)

Did you capture system diagnostics during this issue?  Gotta post those or we got nothing to go on for diagnosing.

Sadly, no.  I thought about it about 15 seconds after hitting reboot :(

 

The server was acting much like it does when I do a parity check (slowly losing access to the shares and the GUI), so maybe I'll start a parity check later today and see if the issue recurs, and if so, I'll grab the diagnostics and update the parity check problem report thread I started previously.

 

thanks again for all your help jonp, I do appreciate it.