Ribby

Hi all, I've tried looking around for this online but haven't cracked why this is happening yet. I have my old RTX 2080 in my server machine, it's bound to an IOMMU group (no Nvidia driver installed in Unraid). I can confirm it can be picked up in Linux VM but only as a secondary GPU, the Linux drivers work and I can confirm Nvidia X Server sees the GPU and can control it with no issue. if I switch the 2080 to primary GPU the machine(s) shows no sign of posting. No error(s). I've installed both AnyDesk and Parsec to detect and access the VM after posting, both are set to autostart with the VM and I have confirmed they both start without any input from the user after booting. I can only assume the machine(s) aren't posting since neither apps can see the VM(s) anymore. So I've only tried 2 distros, Pop! OS and Manjaro, but it's strange it happened the same exact way for both. I'm sure there's a more elegant way to test this and see what the issue is, but this was my (admittedly) beginner level troubleshooting so far.

Yeah, looks like it's gone. No activity at all anywhere. How do I go about reformatting the disk?

I let it sit for a few hours and after not seeing anything (although there was read activity) I thought I did something wrong so I rebooted the server so I could try again with a blank slate, now the server is stuck in limbo trying to mount disk2 and never continues. I can't collect diagnostics, that too also hangs and never finishes. The last log I can see is "PANIC at dmu.c:1123:dmu_write()"

Hm. zpool import -F doesn't seem to do anything or is taking forever, there's no response in terminal and it just hangs. How long should it take before I see a response?

ah, thank you for the heads up on the Ryzen stuff. I have done a memtest when I first built my server earlier in the year with 0 errors but I'll try it again, might find something. I'll fix that right away and try those commands since I'm facing either that or rebuilding the whole disk.

Hi all, I'll keep this brief and share what I know but I'm at a loss for next steps. I tried googling this error for my ZFS drives but couldn't find a thread that didn't end with the drive being corrupted and needed rebuilding Long story short, Disk2 in my array is now reporting "Unmountable: Unsupported or no file system", all other disks mount correctly. This was after a hard shutdown after my server became unresponsive and crashed. I attached my diagnostics, would appreciate any help on next steps. Totally prepared to rebuild array as of right now if needed. milkmaid-diagnostics-20231111-1630.zip

Sorry for the long delay in replying, I did replace the SATA cable and connected a different power connector and that seemed to do the trick. I ran a correcting parity with around a hundred errors then one non-correcting sync which showed 0 errors. This took a few days but it was worth it, thanks!

I'll try swapping those out, I've already tried replugging in those cables in but it could be a dying cable, I'll report back.

Hi all, I've started running into a unfortunate set of circumstances and I'll try my best to convey what I have/know As of a couple days ago my parity disk drive started to put out "high heat" warnings (>45 degrees) periodically, not all the time and they blended in with my unused ssd disk high heat warnings, everything seemed to be running fine but today I might be paying for my lack of attention. I've noticed my server taking much longer than usual to start up and mount drives after reboot. My scheduled parity check started and I noticed the array couldn't sustain good read/write speeds and would drop to 0 every few seconds (with an audible sound from the disk), estimated parity check speed was well under normal and the estimated time ballooned to hundreds of days. Parity errors were being corrected but errors were also appearing on the disk itself in my array. I'm no longer getting heat warnings so that's a small win at least. I'm almost certain I'm running into another dying/ disk after my last one failed just one week ago (unrelated to heat), guess I'm wondering if anyone can confirm I killed my parity disk and should start looking for a replacement? milkmaid-diagnostics-20230711-1359.zip

Just coming back to confirm I got a replacement disk, built the array with 0 errors, and recreated the image. After re-installing my apps their settings were saved and run again! Thank you!

I had a scare while rebuilding where the new disk I got failed to rebuild due to read errors but after replacing the SATA cable it seemed to fix that so I chalked it up to the SATA cable being faulty. I'm now wondering if my new HDD is a dud...

Unraid Version: 6.12.0-rc2 So this is my first forum post and will try my best to provide what is needed! So i recently had a disk failure, everything after that went as expected, replaced the disk, rebuilt the array, and everything seemed to be okay until I realized none of my docker apps started nor could be started. I only have 2 apps but both cannot be started anymore. Trying to start an app results in an error: When I try to delete the app to try and reinstall them (not ideal) I get "server error". So I'm just officially stuck right now. I've Googled around a bit and someone suggested emptying/resetting cache, I tried that and made no progress. All other shares/functions of the server seem to be working fine though... If I can get my docker apps back as they were before that'd be perfect but understand if I have to reinstall them as much as I'd like to avoid that. Any help greatly appreciated! milkmaid-diagnostics-20230626-1235.zip