Kuchar09

Thanks for the quick reply! So I ran "btrfs rescue zero-log /dev/nvme0n1p1" and "btrfs rescue zero-log /dev/nvme1n1p1" and that appears to have let my cache mount without any issues. I then upgraded to v6.11.5 Interesting enough I'm still having issues with Dockers randomly not responding. Then once I stop them and restart them I recieve an error "Execution error Error code 403" then eventually the server just locks up. This was my original issue that forced me to hard reboot yesterday making me thing my flash drive was dying. I took a diagnostic report (server-diagnostics-20230104-1501.zip) right after the 403 error before the lockup and another after a hard reboot (server-diagnostics-20230104-1512.zip). I'm currently going to just let it sit without my 2 main VMs running and see if it survives the night. I have a feeling something got corrupt or some hardware is dying. EDIT: And my server just went unresponsive again within minutes without even doing anything. Can't ping it or anything.... Would it be worth trying to move everything off the cache drive, reformating it, then try putting the appdata back on it? server-diagnostics-20230104-1501.zip server-diagnostics-20230104-1512.zip

I had issues this afternoon where my docker were going unresponsive. So I shutdown all VMs and dockers and tried to restart my server but it hung up on shutdown so I had to force it off. I then tried restarting my server just for the IP/ GUI to never appear. So I connected a basic video card I use for troubleshooting and saw I had a panic kernal which typically means flash drive failed. So I downloaded my backup and restored to a new flash drive but couldn't get my mobo to boot the flashdrive automatically. So I upgraded the bios since it seemed like a bug and I was able to get everything to work as expected until I started the array. My cache now reads "Unmountable: No file system". I tried following these steps "Link" but am afraid of breaking something and losing a lot of photos I forgot I stored on my cache (NextCloud sync). I assume something is corrupt according to these disk logs. Jan 3 21:58:30 Server kernel: BTRFS info (device nvme0n1p1): bdev /dev/nvme0n1p1 errs: wr 0, rd 0, flush 0, corrupt 1, gen 0 Jan 3 21:58:30 Server kernel: BTRFS info (device nvme0n1p1): bdev /dev/nvme1n1p1 errs: wr 0, rd 0, flush 0, corrupt 2, gen 0 Attached is my diagnostic report. Any help to try and save some data would be greatly appreciated!!! server-diagnostics-20230103-2200.zip

I finally got it to work! Not sure why but I had to add a VNC as my first graphics card and my RTX 3090 as my second graphics card to the VM template. Not exactly sure how that stopped both my Windows 10 and 11 VM from crashing on login but it did. Maybe it's because I'm on UnRAID 6.10.0-rc2?

I feel like I must be doing something wrong. I tried this on both my Windows 10 and Windows 11 VM and they both give me a BSOD when I log into windows. "Stop code: CLOCK_WATCHDOG_TIMEOUT" Server is running a Intel i7-11700K and RTX 3090 My XML is identical to your example so I'm not sure what I'm missing. Is there something obvious I'm missing? <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> <kvm> <hidden state='on'/> </kvm> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='8' threads='2'/> <cache mode='passthrough'/> <feature policy='disable' name='hypervisor'/> </cpu>

Thanks for the reply! I read that about reboots so I will have to remember that for future reference. My rebuild was successful! I'm currently running a parity check and will also run an extended SMART test when finished to verify I'm in the clear.

I randomly received 24 errors on all 3 of my disk this morning after I notice my VM wasn't responding and attempted to restart it via the VM Manager in the web GUI which failed, the VM would not restart or shutdown. Not sure if it was a coincidence or what. Honestly it doesn't make any sense considering the vdisk for my VM is on a 1TB unassigned device and is completely separate of my array. I have a 3 disk array (1 parity + 2 disk all 10TB) and this is my first time dealing with a possible hard drive failure. The disk is almost 1 yr old so it shouldn't be dying just yet I hope. I did disconnect 2 sata cables to the drives yesterday to put labels on the drives while adding a fan to my system so I thought it could possibly be a loose connection. After I saw the errors I shutdown the system and went to check my cables and all looked fine. I rebooted the system and noticed the errors are gone but my disk 1 (ZA27GL6X) is now disabled. I ran a short SMART self- test and everything looks good. I also took a diagnostic but honestly have no clue what I'm looking for. I probably should have went and bought a replacement drive and pre-cleared this one before attempting to re-use it but decided to just rebuild the the drive since I feel it is a fluke. Could someone please take a look at my diagnostic file and see if something stands out? Thanks in advance for any help or guidance!!! server-diagnostics-20191006-1541.zip server-smart-20191006-1040.zip