fespinoza831

Parity drive seems fine now but it only took 30 minutes to sync which i thought was odd. but disk 1 is not installed any time i add it its starts acting up. how would I go about using disk 1 as a 2nd parity drive and finding out what I lost on disk1. i really just want to make sure Im protected and make sure these issue were resolved. plexserver-diagnostics-20230930-1027.zip

i got more disks with errors now. What should I do?

Disk 1 is now disabled and im still trying to run the parity sync, am I going to loose what was on disk 1 and if so is there any way to find out what was on it. plexserver-diagnostics-20230930-0717.zip

Restarted, checked all cables, all drives appeared good one it was up again. Started the parity sync, but I still get errors on disk 1 once the parity starts. not sure how to proceed. plexserver-diagnostics-20230930-0645.zip

Even though the errors are on disk1 and not the parity drive?

Parity is still running but there's tons of issues There are no exportable user shares /var/log is getting full (currently 100 % used) and the paths below dont exist /mnt/user/appdata/ /mnt/user/system/docker/docker.img plexserver-diagnostics-20230929-1505.zip

Well the parity sync is at 10 % now so it seems to be moving along. But disk1 is showing tons of errors. how should I proceed once the parity sync is complete? both of my cards are the ones below. what would your recommendation be in regards to the cards. any way to determine if it is the card? can I still have docker enabled during a parity sync to watch Plex? I currently have it disabled. 9207-8i PCIE3.0 6Gbps HBA LSI FW:P20 IT Mode ZFS FreeNAS unRAID 2* SFF-8087 US

I checked all cables and reseated both of my HBA cards. Currently on a 2nd try at running a parity sync the first time it stooped but its now showing disk1 is also having errors. am I in danger of losing data? no sure how to proceed. plexserver-diagnostics-20230929-0951.zip

So I shutdown the server and swapped the cables and now I can actually rebuild the drive. Yesterday it would not rebuild it was just running a check.

Only power cable or data cable as well?

3rd time this happens to DIsk1 twice with a previous drive and now with a drive that has less than a week in the system. its rebuilding now. just wondering what's causing it plexserver-diagnostics-20230911-2127.zip

They share the same power cable but so do all of the rest of the drives. I powered off the server and made sure the power cables were firmly pressed in all the way. Powered back on and started the rebuild process and it worked. I did add a drive the other day so I guess I could have loosened up a cable maybe..

Thanks will check as soon as I get home from work.

Good morning, I found disk1 disabled with no error in smart check. So I removed then assigned again to start the rebuild but it stops and starts a read check which stays paused. plexserver-diagnostics-20230814-0637.zip

Got this error today. Diag was pulled before rebooting. plexserver-diagnostics-20230421-2119.zip

Found the fix. looks like its the firmware on the Crucial MX500 drives. There a firmware update that address the issue. Performed the update on Friday and haven't had any issues since.

ok just moved both drives to the HBA

OK will do this, but should mention that I had same issue on my previous board which was a MSI MPGZ490 now using a ASUS Prime Z590-A. Are the MX500 known to work?

brought it back up and running the scrub but it doesn't show any errors Still running Parity Check...

Also noticed that when this happens I cannot restart the server. I stop dock and VMs. check for open file then reboot but it will hang at a black screen. I have to hard reset to actually bring it back up from that. but if I do a shutdown and then start it it works fine.

Is this still my cache drive? Apr 7 05:47:52 PlexServer kernel: ata3: hard resetting link Apr 7 05:47:56 PlexServer kernel: ata5: link is slow to respond, please be patient (ready=0) Apr 7 05:47:58 PlexServer kernel: ata3: link is slow to respond, please be patient (ready=0) Apr 7 05:48:01 PlexServer kernel: ata5: COMRESET failed (errno=-16) Apr 7 05:48:01 PlexServer kernel: ata5: hard resetting link Apr 7 05:48:02 PlexServer kernel: ata3: COMRESET failed (errno=-16) Apr 7 05:48:02 PlexServer kernel: ata3: hard resetting link Apr 7 05:48:06 PlexServer kernel: ata5: link is slow to respond, please be patient (ready=0) Apr 7 05:48:08 PlexServer kernel: ata3: link is slow to respond, please be patient (ready=0) Apr 7 05:48:11 PlexServer kernel: ata5: COMRESET failed (errno=-16) Apr 7 05:48:11 PlexServer kernel: ata5: hard resetting link Apr 7 05:48:12 PlexServer kernel: ata3: COMRESET failed (errno=-16) Apr 7 05:48:12 PlexServer kernel: ata3: hard resetting link Apr 7 05:48:16 PlexServer kernel: ata5: link is slow to respond, please be patient (ready=0) Apr 7 05:48:18 PlexServer kernel: ata3: link is slow to respond, please be patient (ready=0) Apr 7 05:48:46 PlexServer kernel: ata5: COMRESET failed (errno=-16) Apr 7 05:48:46 PlexServer kernel: ata5: limiting SATA link speed to 3.0 Gbps Apr 7 05:48:46 PlexServer kernel: ata5: hard resetting link Apr 7 05:48:47 PlexServer kernel: ata3: COMRESET failed (errno=-16) Apr 7 05:48:47 PlexServer kernel: ata3: limiting SATA link speed to 3.0 Gbps Apr 7 05:48:47 PlexServer kernel: ata3: hard resetting link Apr 7 05:48:51 PlexServer kernel: ata5: COMRESET failed (errno=-16) Apr 7 05:48:51 PlexServer kernel: ata5: reset failed, giving up Apr 7 05:48:51 PlexServer kernel: ata5.00: disable device Apr 7 05:48:51 PlexServer kernel: ata5: EH complete Apr 7 05:48:51 PlexServer kernel: sd 6:0:0:0: [sdf] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=89s Apr 7 05:48:51 PlexServer kernel: sd 6:0:0:0: [sdf] tag#4 CDB: opcode=0x2a 2a 00 1c 97 0a a8 00 00 70 00 Apr 7 05:48:51 PlexServer kernel: I/O error, dev sdf, sector 479660712 op 0x1:(WRITE) flags 0x8800 phys_seg 14 prio class 0

Was good for a few day and it happened again yesterday. so I replace the power cables again last night. ran the scrub and woke up to docker being crashed and cache drives disabled again. is there anything else that could be causing this. Any of my hardware not recommended. Not sure what else to do here. plexserver-diagnostics-20230407-0706.zip

this is what I get when trying to access the web UI

Was testing this with Sonar before setting up NZBGET

# curl ifconfig.io returned the VPN ip but i cant access the web GUI of the routed container.