theredviper

Thanks all, parity was rebuilt successfully, so far so good.

Thanks I replaced the cable and restarted, for the record I had to: 1. stop array, remove parity disk, restart array 2. stop again, add parity disk back, restart array It is currently rebuilding. The disk has flagged 1 UDMA CRC error. Is this due to the cable, can it (should it) be cleared? Thanks again.

Hi folks, I'm hoping to get some help with this error, I just noticed it but it appears my parity disk went offline a few days ago. I tried stopping the array, unassigning the device, then reassigning (it errored out and disappeared at that stage). I rebooted and the drive was visible again but still disabled when I tried to restart the array. The disk is the newest in the box, around 6 months old. I'm wondering if it's the disk or the controller that might be the issue. I haven't opened it up to reseat everything yet. Diagnostics attached, disk in question is sdf. tower-diagnostics-20230708-1902.zip

After having issues with the official Plex docker image I've tried installing this one as it seems to have far more support. It is using separate appdata paths as I'm ok starting over in terms of my Plex DB but I'm getting the same error and struggling to find out more from the logs. Plex Docker/UI Log: **** Server already claimed **** Docker is used for versioning skip update check [custom-init] No custom files found, skipping... Starting Plex Media Server. . . (you can ignore the libusb_init error) [ls.io-init] done. Jobs: Exec of ./CrashUploader failed. (2) Critical: libusb_init failed Plex Crash Uploader log (this is the whole file): Nov 20, 2022 12:52:58.105 [0x14a1720c6b38] INFO - Crash Uploader - Platform: Linux ServerUUID: df6604e58b6e1133f4bc414b0e2d34e966d6232a UserId: NOUSERID Version: 1.29.2.6364-6d72b0cf6 Nov 20, 2022 12:52:58.105 [0x14a1720c6b38] DEBUG - Pre-processed minidump directory: /config/Library/Application Support/Plex Media Server/Crash Reports/1.29.2.6364-6d72b0cf6 Nov 20, 2022 12:52:58.105 [0x14a1720c6b38] DEBUG - Post-processed minidump directory: /tmp Nov 20, 2022 12:52:58.101 [0x14a172bc2808] ERROR - Too many crashdumps detected / retries disallowed! Crash Reports folder is there and has a Plex Media Server folder but it's empty. I've attached the Plex Media Server.log and here's my docker run: The server is "running" and under My Authorized Devices on Plex I can see the claim ID seems to be recognized, but everything is inaccessible. I was running fine this week on unRAID 6.11.2. I woke up to an issue this morning, and among other things I upgraded to 6.11.4 with no change. Edited to include diagnostics too. Plex Media Server.log tower-diagnostics-20221120-1305.zip

Having an issue with Plex v1.29.2.6364-6d72b0cf6 on unRAID 6.11.4 (was on 6.11.2 and same problem, upgrade didn't change it). Log in unRAID as follows: I understand that is a USB tuner lib which isn't relevant for me, don't have or use one. What other logs are helpful here?

Hi guys, I use Sonarr/Plex with Sabnzbd and Qbittorrent to download. Everything works except I'm having a problem with Sonarr and qbittorrent. Sonarr will send the torrent and QBT will download. When the download ends, the file will sit in "complete" and not get copied to the media folder I want. The only line in Sonarr trace logs is as follows: 2022-09-18 18:55:38.7|Trace|DiskProvider|Hardlink '/data/complete/path/MEDIA.mkv' to '/media/plex path/MEDIA.mkv' failed due to cross-device access. I can't find anything on "cross-device access". I feel like it's a read/write issue between QBT and Sonarr's file handling. Any advice where else to look? I have seen ratio/seed time settings in QBT and blank in Sonarr. Should it be the other way around? Thanks.