Bayank

I checked and re-seated all my cables, changed ports around too, didn't make a difference. After banging my head against a wall over this, I popped in a clone of the drive I made from before the case swap, and only change I made in the XML was the drive letter assignment, and lo and behold it boots successfully. Now the only new problem I'm facing is that the VM hangs on reboots. I have to kill the VM and restart it. I guess I can live with that since it's always running. Seems like I killed the original SSD somehow, or the data got so corrupted it's causing SATA errors.....

Hi y'all, I finally had my Unraid setup how I wanted it, and was using Win10 with ssd boot passthrough, GPU passthrough, and USB controller passthrough successfully. Noticed my array drives were getting a bit too hot for my comfort, like 45-50 C, so I decided to move everything into a new case with better airflow. Upon the first boot, I was not getting any display at all, and after removing devices to bare minimum, I reset the CMOS, eventually got it to boot ok. Everything seems to be OK except my Win10 VM. It boots to the windows logo and the display fades out to black, and then hangs, and it causes the whole server to hang as well. Looking through the VM logs I see lots of sata related errors, which I'm not sure why are happening now. I've attached my diagnostics for additional info. If anyone can help me figure out why my SSD is having issues all of a sudden I would be most grateful. My setup: Lenovo S30 mobo Intel Xeon E5-2665 32 GB ECC ram 7 Array drives 4 port Sata expansion controller Marvell 88SE9215 - The win10 boot ssd is not on this card, it's on a mobo sata port. GTX 970 - Using this for Win 10 Quadro 600 - Tied to Unraid, main boot display bayanraid-diagnostics-20170506-1536.zip

Hi, I'm having some issues using an ACD mounted by rClone as my backup location. When I try to setup a local folder backup pointed to the ACD mount, I get an error "The backup engine does not have access to the given location." I have the mappings as follows: /Amazon/ /mnt/disks/amazon/ <<-- This is the folder I'm pointing to in the crashplan gui /unassigned /mnt/disks/ /config /mnt/user/appdata/CrashPlan /mnt/user /mnt/user /backup /mnt/user/Backup/ In the docker settings, I set the Access mode to RW/slave as suggested by Fix Common Problems, and have turned on the Privileged setting as well. Seems to have no effect. The /mnt/disks/amazon/ folder is mapped and accessible by other dockers like Krusader and can write to it fine. Any ideas how to fix this? Thanks, Bayank

Thanks for the clarification. After updating the plugin the postread finished successfully.

Hi all, UnRaid newb here, I am trying to preclear 3 x 6TB HDDs at the same time on a new build and no array. I used the plugin to clear them, and they all failed around the same time during postread because of some dd exit code 1 error. The webgui in unassigned drives just showed the status as preclear paused, and no way I could see to resume it. I uninstalled the plugin, restarted the server, and installed again and then updated the plugin (3/23/17). It's currently running and will take a long time to get to the postread stage again. Assuming there were no errors up to that point, and if dd throws a exit code 1 error again, can I run the full verification only from the dropdown list in the plugin? What's the difference between the postread stage and verification option in the plugin?