jam

Oh damn it, sorry! I was running the mover when the errors first happened so didn't think to check how full the cache was. Must've been filling up faster than it was emptying.

Well, after a couple of days without issue, I'm getting I/O errors again... this time with the cache pool 😒Is there anything else I can try? holt-diagnostics-20200408-0924.zip

Yeah, mine finished successfully with IOMMU still enabled. I’m preclearing the new drives now, also without errors.

It’s still going but it’s reached 75% without issues. I’m using an X399 TR board too (ASRock Taichi) so I’d recommend giving the beta a try.

Okay, I'm quietly confident that the 6.9 beta is working properly 🤞The parity rebuild is at 10% now without errors; it never reached 5% before. Thanks again for the fast assistance!

Thanks again, I'll update now & give it a try. If it was a kernel/compatibility issue though, wouldn't I have seen this before? I've had the system for just over 7 months now & never seen errors like this until now.

Thanks for the suggestions. I updated to the latest BIOS & tried again with IOMMU both enabled and disabled, but I'm still experiencing the problem. I'm guessing that the motherboard is screwed then?

Something terrible seems to have happened to my server while I was performing some upgrades 😨 I wanted to replace the existing 10TB parity drive with a 14TB one so that I could add larger capacity drives to the array. I ran a parity check beforehand, which reported 0 errors. After replacing the drive, Unraid began a parity rebuild, but didn't get very far before all drives in the array began spewing errors into the system log. I've tried the process a couple more times & the same thing keeps happening. After stopping the parity check & attempting a recursive ls on each disk, some files/directories can be accessed while others fail with "Input/output error". I can't view the SMART status of any of the drives either; it just says that "a mandatory command failed". What the hell has happened?? How could all 7 disks in the array simultaneously go bad, after a full parity check beforehand not report any errors? I didn't touch any of the cables to the array drives during the upgrade... the new drive is connected to a totally different SATA controller/PSU power cable. In the interest of full disclosure, I also added more RAM to the system recently, but this has been in place for a week without issues, and was there during the parity check prior to adding the new drive. holt-diagnostics-20200403-1326.zip

Thanks, I appreciate the help. I don't need it up & running again urgently, but I'm wary of stumbling around by myself & making things worse. I've been able to boot the server when the keyfile has been unavailable in the past, and been able to access the web UI.

Yes, the array is encrypted - the keyfile is located on another machine on my network. My server's boot drive contains the keys & scripts needed to fetch the keyfile & decrypt the array on startup, but you're right that this isn't happening. If this was the sole issue, though, I'd expect to still be able to access the web interface.

Hey all, I'm really hoping that someone here can help me out... I have a server running UnRAID 6.6.6 (one of the DVB edition builds). Last night, I encountered a bit of a catastrophe. While using the web GUI, I clicked on the VM tab, and the entire machine hung - no services were accessible, I couldn't SSH in, and it wasn't even responding to pings. Connecting a display at this point showed nothing. This has happened a couple of times in the past, always when selecting the VM tab in the web interface (although this is rare; it's not a consistently reproducible problem), but as I couldn't do anything other than hit the reset button with no way I could think of to get any info out of the system, it just got added to my mental "I need to look into that at some point" to-do list. This time, after rebooting, pretty much nothing seems to be working. The web interface isn't responding, and the array hasn't started (so obviously no Docker or VMs). I can SSH in (thankfully!) and the emhttpd process is running; I've been able to grab a diagnostics archive, but I'm at a bit of a loss as to what to do next. Any assistance would be appreciated! holt-diagnostics-20190319-1930.zip

Oh, okay - thanks for the info! I'll report back to TBS support.

Hi guys, I've recently picked up a TBS 6209 PCIe card & I'm having problems using it with the unRAID DVB Edition builds. I've tried both the open source and CrazyCat builds, up to the latest 6.6.0 RC. The card is detected with all tuners available, but any attempts to scan for channels fail. After contacting TBS support, they've sent me a link to a new package to try (http://www.tbsdtv.com/download/document/linux/media_build-2018-0822.tar.bz2). I'm fine with building the package myself; is it possible to install these drivers into an existing installation of unRAID so they survive a reboot? Thanks!