Luke787

Awesome. Appreciate the quick response. I'll try these out over the weekend and respond with the results. I appreciate the input!

Unraid 6.8.3 Hardware: Dell R710 + Lenovo SA120 I recently installed PiHole in a docker which lead to a kernel panic that caused an unclean shutdown. After starting UnRaid back up, I had the Fix Common Problems plugin showing the error: Unable to write to cache Drive mounted read-only or completely full. I've had multiple issues with multiple containers having Sql issues, likely due to something wrong with the cache. If I perform an 'ls' on the cache drive, I get: root@R710:/mnt/cache# ls /bin/ls: reading directory '.': Input/output error The disk log info shows a lot of this and more: Oct 16 04:40:06 R710 kernel: verify_parent_transid: 8 callbacks suppressed Oct 16 04:40:06 R710 kernel: BTRFS error (device sdg1): parent transid verify failed on 114130944 wanted 1964701 found 1964700 ### [PREVIOUS LINE REPEATED 5 TIMES] ### Oct 16 04:40:08 R710 kernel: BTRFS error (device sdg1): parent transid verify failed on 113278976 wanted 1964701 found 1964700 Oct 16 04:40:08 R710 kernel: BTRFS error (device sdg1): parent transid verify failed on 114130944 wanted 1964701 found 1964700 ### [PREVIOUS LINE REPEATED 2 TIMES] ### Oct 16 04:40:09 R710 kernel: BTRFS info (device sdg1): no csum found for inode 30816523 start 0 Oct 16 04:40:09 R710 kernel: BTRFS warning (device sdg1): csum failed root 5 ino 30816523 off 0 csum 0x39ffcf77 expected csum 0x00000000 mirror 1 Oct 16 04:40:09 R710 kernel: BTRFS info (device sdg1): no csum found for inode 30816523 start 0 I'm not terribly familiar with Btrfs, and I assume there is corruption somewhere due to the unclean shutdown. Wondering what the best next steps are to get my cache disk working again and hopefully not lose the data on it. Any help or insight would be appreciated. r710-diagnostics-20201016-0106.zip

This is likely a silly question but I'm new to Minecraft and obviously this container. Is there anyway to upgrade to the latest snapshot, 20w10a in this docker container?

I have since tried switching the cables, and the Firecuda drive with another Firecuda drive. Same issue persisted. I switched to a different hard drive and absolutely no issues. I'm not sure if it's a firmware or driver issue or what at this point...

The cables and backplane are shared with the other drives that work fine. If the disk was bad, wouldn't it have similar issues with other OS's?

I am currently running the trial version of UnRaid on my R710 for a few weeks, and have been pretty happy so far. However, I bought a brand new 2 TB drive on prime day (Seagate ST2000LX001). I was going to add it to my array of two 4 TB disks but things aren't working out as smoothly as the previous drives. At first when I went to perform anything on the drive, it disappeared from unassigned devices. I switched the slot it was in just in case that was an issue and it appeared. I ran a preclear then afterwards was unable to use it. Unraid wouldn't let me run a smart test as it had to be spun up. However it wouldn't spin up. Everything was greyed out. After reset, it wouldn't even show up. I ended up removing the drive and formatting it outside of the unraid box and reinserting it before it would pop up. I then formatted it in Unraid and added it to the array. I thought everything was fine, then after a couple hours the drive becomes missing. It won't recognize it again. I have tried drive slots from both SAS bays. I have been having this battle for days. After a format it shows up almost every time only to disappear when I try to perform any actions such as adding it to the array and starting a rebuild. The drive is recognized in the BIOS and shows up in UnRaid system devices. The SMART results seem fine with no pending or reallocated sectors and passes every test I have thrown at it when unraid would let me. I have also tested the drive multiple times on other computers without issue. I looked at the system log and found this around the time that it disappeared after trying to do a rebuild on it: Jul 23 13:52:22 R710 emhttp: err: ckmbr: read: Input/output error Jul 23 13:52:22 R710 emhttp: ckmbr error: -1 Jul 23 13:52:22 R710 kernel: sd 2:0:5:0: Device offlined - not ready after error recovery Jul 23 13:52:22 R710 kernel: blk_update_request: I/O error, dev sde, sector 0 Any help would be greatly appreciated. r710-diagnostics-20170723-1432.zip r710-syslog-20170723-1434.zip