Good Morning.  Long-time user, but my unRaid server has essentially been on auto-pilot for so long (that's a testimony to how well it just runs!) that I'm not sure on a few things and would like to request some help/guidance.

 

1.  Attached is a diagnostics package from a clean boot.  I just installed a Dell Perc H310 that I flashed to IT mode per the numerous guides out there.  I did this so all my drives would work with IOMMU and I could start experimenting with virtulization.  I seem to be getting a lot of INVALID ADDRESS REQUESTS during boot, and one drive keeps defaulting to SATA 3.0 even though they're all SATA 6.0 capable.  Can anyone take a quick look and see what's going on?

 

2.  I put a new SSD drive in (480 GB) to act as my new drive for the virtual systems.  The system bios recognizes it, it's the only drive attached to the motherboard (the rest are on the Perc H310) as SATA 3_1.  UnRaid however doesn't see it.  The drives all used to be attached to the motherboard before I put the Perc H310 in, so I'm perplexed why unRaid isn't seeing this drive but the bios is.

 

3.  What's the consensus on docker files?  I used to run a drive outside of the array using SNAP just for docker, but with the latest plugin "Unassigned Drives", there seems to be a timing issue that the drive isn't mounted before docker loads and the dockers don't start properly.  Should I just ditch that setup and put the docker file on the cache drive?

 

4.  I have a weird share "appdata" that got created and I can't delete it.  I've used MC to delete the directory (some remnant of a Plex install that has many, many sub-directories) and I've tried rm -r but it keeps failing saying that the directory is not empty.  When I go to the sub most folder, there are no files there.  ls -a shows the directory as empty.  How can I nuke this particular directory and get rid of this lonely share?

 

I appreciate any help that anyone can provide, thank you!

 

Updated: put some logs in the body of the text.  Appreciate any help provided!

rebel-data-diagnostics-20160518-0802.zip

4.  I have a weird share "appdata" that got created and I can't delete it.  I've used MC to delete the directory (some remnant of a Plex install that has many, many sub-directories) and I've tried rm -r but it keeps failing saying that the directory is not empty.  When I go to the sub most folder, there are no files there.  ls -a shows the directory as empty.  How can I nuke this particular directory and get rid of this lonely share?

the 'appdata' share is the default configuration folder for most docker apps (typically with a subfolder per app).  It should be set as a cache-only share so that it does not get moved to the main array.

Thanks.  I still can't delete those folders though, it's some left-over from a previous Plex install.  Weird.