Bayank Posted May 8, 2017 Share Posted May 8, 2017 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 Quote Link to comment
1812 Posted May 9, 2017 Share Posted May 9, 2017 i didn't look at your diagnostics (no time at the moment,) but if you moved stuff and now get sata errors, first guess is you have a loose cable or two. Recheck/re-seat your connections. Quote Link to comment
JorgeB Posted May 9, 2017 Share Posted May 9, 2017 (edited) Constant ATA errors on the Crucial SSD, check cables. CRC errors on the PNY SSD, replace SATA cable. Edited May 9, 2017 by johnnie.black Quote Link to comment
Bayank Posted May 12, 2017 Author Share Posted May 12, 2017 (edited) 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..... Edited May 12, 2017 by Bayank Quote Link to comment
JorgeB Posted May 12, 2017 Share Posted May 12, 2017 or the data got so corrupted it's causing SATA errors.....Most likely the other way round, constant ATA errors corrupted the data on the SSD. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.