madejackson

I have an issue with radarr/sonarr/bazarr randomly accessing my files and thus unnecessary spinning up drives. The Access happens randomly, averaging about 1 access per hour. Is there any way to prevent that? f.e. Today from 09:00 to 10:00 my drives were accessed 2 times, once from radarr, once from sonarr: I do not see any pattern in these accesses hence I cannot seem to find the culprit. I have automatic rescan disabled in the settings, so this is definitely not the culprit: My Drives should idle 12-16h per day, but because of this behaviour they randomly spin up and down several times a day. This leads to unnececary power usage and wear on the hdd's. My Plex-Library has >5000 files and >10tb accross 12 HDD's.

Seriously, What good is a raid-protected filesystem if it fails to protect your data. Most important infos at first, my Questions: Why does unraid/btrfs not detect and notify me that my ssd's going havoc? Why does unraid/btrfs allow writing to a bad pool, rendering the data inaccessible? Why is btrfs not able to restore my data after a drive failure? (raid 6, 1 drive detached) Why is btrfs not able to correct Errors, even in RAID 6, which should survive 2x drive failures? (raid 6, all drives accessible) In my understanding, uncorrectable error would mean, I have lost at least 3 of my 6 drives at once. It's impossible that this is a purely hardware based failure. Writeup: In recent months I got very frustrated with my BTRFS-Cache pool and I think it is not ready for Primetime at all. Unfortunately, there is no alternative, as ZFS does not allow a protectet cache. Maybe I am doing something wrong but I frequently get uncorrectable I/O-Error's and suddenly disappearing drives. in the past 5 Years I had 2x240gb in RAID 1 which I upgraded 1 Year ago to 3x240GB in RAID5. I also added another pool with 2x120GB in raid 0 (metadata raid1). It started with getting corrupted files in the raid0-Pool. The bad files were logged and I was able to delete them. As this issue started to re-appear I recreated the complete pool but: no avail. Suddenly, one day my server froze and I had to kill it via Powerswitch. After Reboot I saw a lot of I/O-Errors on the raid 5 pool and 1x Drive was not recognized by unraid anymore. After a reboot, the drive was appearing but suddenly disappeared when trying to add it to the pool. After Clearing the disk via an USB-SATA-Adapter on another machine and then preclearing it via unraid, I was able to add the drive to the pool again and it suddenly worked flawlessly again. Tons of my photos were corrupted and I tried every fucking btrfs-tutorial and command out there on the internet to save them but it didn't work. The data is gone despite using a RAID 5. After this devastating dataloss-fiasco, I removed the raid0 pool and created one huge pool with raid 6, 3x240gb + 3x120gb. Working flawlessly for 2 Months. Today, i suddenly noticed one of the drive had no access anymore and the logs showed ton's of btrfs errors. I stopped everything and Rebooted, drive not showing up anymore. Btrfs showed a ton of Errors. AGAIN: Every fucking tutorial to save the data didn't work. I always have some unsolvable error and the command get's abortet. reattached the drive via an USB-SATA adapter and wow: Drive is suddenly back and can be accessed. Well I am not gonna use this Drive anymore: btrfs device remove... Result: aborted IO-ERROR: ARE YOU FUCKING KIDDING ME I even cannot remove a bad drive what should i do? btw: My System has ECC-RAM installed, so definitely no issues there. tower-diagnostics-20211213-2249.zip

In July 21, I installed 3x 600GB SAS drives in my unraid system and installed this plugin. Unfortunately, it does not work for me. I get random read/write errors on 2x drives. One of the drives just went offline while shutting down all drives while writing to the drive simultaniously. I am using an LSI3008 card and 2x Toshiba AL14SEB060N 600GB drives (Unraid 6.9.2). Interestingly, I have also 1x HGST HUC101860CSS204, which is working fine so far. It seems like Unraid does not realize the drive is spun down and tries to access it regardlessly, resulting in read/write errors: ... Nov 1 15:13:50 Tower emhttpd: spinning down /dev/sdp Nov 1 15:13:50 Tower SAS Assist v0.86: Spinning down device /dev/sdp Nov 1 15:13:59 Tower kernel: sd 15:0:7:0: [sdp] tag#4350 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=8s Nov 1 15:13:59 Tower kernel: sd 15:0:7:0: [sdp] tag#4350 Sense Key : 0x2 [current] Nov 1 15:13:59 Tower kernel: sd 15:0:7:0: [sdp] tag#4350 ASC=0x4 ASCQ=0x11 Nov 1 15:13:59 Tower kernel: sd 15:0:7:0: [sdp] tag#4350 CDB: opcode=0x2a 2a 00 28 25 b9 18 00 04 00 00 Nov 1 15:13:59 Tower kernel: blk_update_request: I/O error, dev sdp, sector 673560856 op 0x1:(WRITE) flags 0x0 phys_seg 128 prio class 0 Nov 1 15:13:59 Tower kernel: md: disk10 write error, sector=673560792 Nov 1 15:13:59 Tower kernel: md: disk10 write error, sector=673560800 ... ... Nov 1 15:13:59 Tower emhttpd: spinning down /dev/sdo Nov 1 15:13:59 Tower SAS Assist v0.86: Spinning down device /dev/sdo Nov 1 15:14:08 Tower kernel: sd 15:0:6:0: [sdo] tag#4276 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 cmd_age=8s Nov 1 15:14:08 Tower kernel: sd 15:0:6:0: [sdo] tag#4276 Sense Key : 0x2 [current] Nov 1 15:14:08 Tower kernel: sd 15:0:6:0: [sdo] tag#4276 ASC=0x4 ASCQ=0x11 Nov 1 15:14:08 Tower kernel: sd 15:0:6:0: [sdo] tag#4276 CDB: opcode=0x28 28 00 19 ce 1b 40 00 00 20 00 Nov 1 15:14:08 Tower kernel: blk_update_request: I/O error, dev sdo, sector 432937792 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0 Nov 1 15:14:08 Tower kernel: md: disk11 read error, sector=432937728 Nov 1 15:14:08 Tower kernel: md: disk11 read error, sector=432937736 ... (Edit: added Info about the HGST-Drive)

Suddenly, I was having issues accessing my Dockers on custom VLAN's. It was working fine last year and it stopped working around starting this year, doesn't know exactly when (Dockers on Bridge/Host and pfsense in a VM were still working fine.) I now found a solution: "Host access to custom networks" = disabled This fixed the issue for me completely. In the network tabs, all routes for "shim-br0.xx" disappeared. But it's working now, so I am happy

Unfortunately, this Guide does not work for me, either. I'm stuck at entering the Domain of Collabora in Nextcloud Settings, I always get a big red Cross, even if I am trying to use the built in collabora App. It seems like an issue with the nextcloud-Docker image, Probably in combination with SWAG. If I try to open a word via Dashboard I get either a Self-Signed-Certificate or a 404 error.

Thank You very much, this works for me, too.