asilva54

Getting this error on starting array. 2 VMs, one for hassio (no passthrus) and one win11 w/ SR-IOV igpu passthru Event: VM Autostart disabled Subject: vfio-pci-errors Description: VM Autostart disabled due to vfio-bind error Please review /var/log/vfio-pci-errors After I get the error when starting the array, I can manually start each VM successfully. silva-nas-diagnostics-20240129-2237.zip

Thanks. Yes for sure it was emulating the drive when it was disabled. I looked at the folders and they seemed directionally correct

what i did so far: reboot: device name completely gone, as if the drive wasnt there anymore. shutdown: made sure all connections are tight boot without starting array. Device shows up and now can get SMART for the drive that was having issues. going to try rebuild. silva-nas-diagnostics-20210816-2341.zip

hello, not sure whats going on - got 2 notifications: Event: Unraid array errors Subject: Warning [SILVA-NAS] - array has errors Description: Array has 1 disk with read errors Importance: warning Disk 7 - WDC_WD80EFAX-68LHPN0_7SHJTD5W (sdh) (errors 2) ------------------------------- Event: Unraid Disk 7 error Subject: Alert [SILVA-NAS] - Disk 7 in error state (disk dsbl) Description: WDC_WD80EFAX-68LHPN0_7SHJTD5W (sdh) Importance: alert silva-nas-diagnostics-20210816-2253.zip

Sure enough, parity check finished. 0 errors. And that's after I put in 2 Evo 860 1TBs in a cache pool. So I don't have any real root cause, other than my Asus x470 ROG Strix didn't like the HP NVMe 1TB.

good point, by the time it crashed yesterday, I had no way to get in to retrieve them. parity almost done. my next steps are: finish parity put in traditional sata ssd for cache (none atm, the NVMe was my cache)...hurry up amazon move domains/appdata/system to cache run new parity, pray for 0 errors i think if i get thru all that then can safely say it was the NVMe...no crashes since taking out the NVMe.

I am hoping that is the case. I am doing parity check now and it has sync errors, but had so many crashed that I think that is expected. I'll run a 2nd one after and if it's 0 and no crashed as I let Plex do a brand new scan, then it was the nvme My logs look clean right?

i remember seeing lots of BTRFS messages when unraid would crash on the screen i have on the side plugged into my unraid box. the HP NVME is the only new drive from a recent hardware (mobo/cpu/ram) upgrade. Taking it out now.

no, but reducing it now since i killed the docker.img anyways to turn off auto-start on containers.

server has been crashing non stop - at one point, accessing the plex cache folders and others in that appdata/plex/config was hanging up the system. I couldnt kill that folder (was on cache drive, the nvme), but MC moved everything but those and recreated docker pulls and stood the VMs back up (moved those too). formatted the drive (set to xfs then back to brtfs) and started loading everything up again. I could swear it was just those folders in plex cache that was hanging it all up, since the other files moved fine. was going well until this morning (plex was doing its mass cataloging) and it died in similar fashion flash drive was recreated just in case, so fresh install. took out 2nd video card too. attached diagnostic, not really sure what I am looking for. silva-nas-diagnostics-20190318-1044.zip