vtdweller

I got frustrated and replaced all cables in the box, and that seems to have stopped the error. So frustrating 😖

After years of minimal issues, it looked like a drive was failing so I replaced it. Now, I can't seem to keep anything up and running. Tried new drives, swapping cables, everything. Do I need a new power supply? A new mobo? Is it a SATA controller? This is my log, and it repeats this way every 6 seconds forever: Jan 5 18:53:19 tower kernel: ata2.00: exception Emask 0x50 SAct 0x0 SErr 0x4890800 action 0xe frozen Jan 5 18:53:19 tower kernel: ata2.00: irq_stat 0x0c400040, interface fatal error, connection status changed Jan 5 18:53:19 tower kernel: ata2: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } Jan 5 18:53:19 tower kernel: ata2.00: failed command: READ DMA EXT Jan 5 18:53:19 tower kernel: ata2.00: cmd 25/00:40:c0:ae:11/00:05:2f:00:00/e0 tag 5 dma 688128 in Jan 5 18:53:19 tower kernel: res 50/00:00:bf:ae:11/00:00:2f:00:00/e0 Emask 0x50 (ATA bus error) Jan 5 18:53:19 tower kernel: ata2.00: status: { DRDY } Jan 5 18:53:19 tower kernel: ata2: hard resetting link Jan 5 18:53:24 tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 5 18:53:24 tower kernel: ata2.00: configured for UDMA/33 Jan 5 18:53:24 tower kernel: ata2: EH complete Jan 5 18:53:24 tower kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen Jan 5 18:53:24 tower kernel: ata2.00: irq_stat 0x0c400040, interface fatal error, connection status changed Jan 5 18:53:24 tower kernel: ata2: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Jan 5 18:53:24 tower kernel: ata2.00: failed command: READ DMA EXT Jan 5 18:53:24 tower kernel: ata2.00: cmd 25/00:40:40:d1:11/00:05:2f:00:00/e0 tag 29 dma 688128 in Jan 5 18:53:24 tower kernel: res 50/00:00:3f:d1:11/00:00:2f:00:00/e0 Emask 0x10 (ATA bus error) Jan 5 18:53:24 tower kernel: ata2.00: status: { DRDY } Jan 5 18:53:24 tower kernel: ata2: hard resetting link Jan 5 18:53:30 tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 5 18:53:30 tower kernel: ata2.00: configured for UDMA/33 Jan 5 18:53:30 tower kernel: ata2: EH complete Jan 5 18:53:30 tower kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x4890000 action 0xe frozen Jan 5 18:53:30 tower kernel: ata2.00: irq_stat 0x0c400040, interface fatal error, connection status changed Jan 5 18:53:30 tower kernel: ata2: SError: { PHYRdyChg 10B8B LinkSeq DevExch } Jan 5 18:53:30 tower kernel: ata2.00: failed command: READ DMA EXT Jan 5 18:53:30 tower kernel: ata2.00: cmd 25/00:80:40:0a:12/00:01:2f:00:00/e0 tag 27 dma 196608 in Jan 5 18:53:30 tower kernel: res 50/00:00:3f:0a:12/00:00:2f:00:00/e0 Emask 0x10 (ATA bus error) Jan 5 18:53:30 tower kernel: ata2.00: status: { DRDY } Jan 5 18:53:30 tower kernel: ata2: hard resetting link Jan 5 18:53:36 tower kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 5 18:53:36 tower kernel: ata2.00: configured for UDMA/33 Jan 5 18:53:36 tower kernel: ata2: EH complete Jan 5 18:53:36 tower kernel: ata2.00: exception Emask 0x50 SAct 0x0 SErr 0x4890800 action 0xe frozen Jan 5 18:53:36 tower kernel: ata2.00: irq_stat 0x0c400040, interface fatal error, connection status changed Jan 5 18:53:36 tower kernel: ata2: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } Jan 5 18:53:36 tower kernel: ata2.00: failed command: READ DMA EXT Jan 5 18:53:36 tower kernel: ata2.00: cmd 25/00:40:c0:68:12/00:05:2f:00:00/e0 tag 4 dma 688128 in Jan 5 18:53:36 tower kernel: res 50/00:00:bf:68:12/00:00:2f:00:00/e0 Emask 0x50 (ATA bus error) Jan 5 18:53:36 tower kernel: ata2.00: status: { DRDY } Jan 5 18:53:36 tower kernel: ata2: hard resetting link

Ok, this can now be closed. I removed the docker and reinstalled. I then moved the Plex database backup file from the old location to the new one, mapped the correct paths in the docker settings, and now I'm refreshing metadata, but by golly, I think I'm in the clear. Thank you!

At this point I'm willing to blow up my library and build it again, but I can't figure out why my Server isn't working. I can't access it from the web gui. The docker says it's running, but how do I confirm that? It seems like such a simple thing but for some reason it's holding up the whole operation. unRAID server: working docker: working http://192.168.0.102:32400/web/index.html: nothing Where do I even begin?

Perhaps a stupid question, but I see two folder structures that seem almost identical. Which is the proper set of data that needs to be backed up? /mnt/cache/apps/Plex/Application Support/Plex Media Server or /mnt/cache/apps/Plex/Library/Application Support/Plex Media Server

Not to my knowledge. The log shows something about permissions, but I'm not sure what it's doing or why. I made no changes to the system until I noticed that my server wasn't running. Then I merely updated and restarted the docker.

I don't know what changed, but I can no longer access my Plex Media Server. Stats: unRAID 6.2.4 PlexMediaServer Container ID: 233d1183e9b5 By: limetech/plex:latest What works: - I can access my shares from my other desktop - I can access the unRAID UI from my other desktop What doesn't work: - I can't access the Plex WebUI from the docker - I can't see the server from my Plex account The docker log repeats this over and over: 10000 chown: changing ownership of '/config/tmp': Read-only file system chown: changing ownership of '/config/Library': Read-only file system chown: changing ownership of '/config/Library/Application Support': Read-only file system chmod: changing permissions of '/config/tmp': Read-only file system chmod: changing permissions of '/config/Library': Read-only file system chmod: changing permissions of '/config/Library/Application Support': Read-only file system 6 10000 /config/Library/Application Support 10000 chown: changing ownership of '/config/tmp': Read-only file system chown: changing ownership of '/config/Library': Read-only file system chown: changing ownership of '/config/Library/Application Support': Read-only file system chmod: changing permissions of '/config/tmp': Read-only file system chmod: changing permissions of '/config/Library': Read-only file system chmod: changing permissions of '/config/Library/Application Support': Read-only file system 6 10000 /config/Library/Application Support 10000 chown: changing ownership of '/config/tmp': Read-only file system chown: changing ownership of '/config/Library': Read-only file system chown: changing ownership of '/config/Library/Application Support': Read-only file system chmod: changing permissions of '/config/tmp': Read-only file system chmod: changing permissions of '/config/Library': Read-only file system chmod: changing permissions of '/config/Library/Application Support': Read-only file system 6 10000 /config/Library/Application Support

If it helps... This error occurs at random times - sometimes right at the beginning of a copy, sometimes four files in. When it occurs, I can't delete the partially created file as it registers as in use. I must stop the array, restart it, and then I can delete the file. I tried cutting the jumbo packet size back to 6000, but it's still occurring.

I'm having the same problem. I just set up my server, both disks are new. In order to get my transfer speeds up, I added a gigabit switch and had to change the jumbo frame sizes (on both my home PC and my unRAID box) to 9000 mtu. This increased my throughput to ~100MB/s, but then I have the same connectivity issues as OP. If I transfer at 11MB/s, I can transfer without losing connection (14 hours now and running). Is it possible that the data is moving TOO fast? Should I throttle the jumbo frame sizes a bit? NOTE: For the initial load, I've deactivated the parity drive - this is just a straight copy across the network.