January 13, 20179 yr I'm hoping someone can help because I am at a loss. I woke up to plex client not seeing the server. Everything looked ok. I thought the docker was corrupt and so I deleted it and recreated it and reinstalled the apps. Still no good. I then rebooted the server and disk 7 was unmountable. I took it out of the array and brought it back up because my thought was to replace the unmountable drive but the apps still aren't able to access the data and couchpotato won't start at all. I know the data is there because I can play it directly from the share. Also, it still stays parity is valid too. I am attaching a diagnostic report. Not sure what to do. Thanks for your help. tower-diagnostics-20170113-1654.zip
January 13, 20179 yr Author as an update, it looks like i lost some data. I got plex to load soem content but couchpotato still won't start. Some of the movies are showing up as unavailable because they aren't there. They might all be on drive 7. I haven't formatted the drive and there aren't any smart errors on it so I guess I could use it if I could somehow clear the errors but I am not sure how to proceed.
January 13, 20179 yr Community Expert First, most of your disks show an abnormal number of CRC errors, you have a lot of bad sata cables or some other issue causing them, start by replacing those cables and monitoring those attributes, any increase of 2 or more means there's still a problem. This is the attribute to monitor: 199 UDMA_CRC_Error_Count 0x003e 200 197 000 Old_age Always - 119 Emulated disk7 (md7) needs a file system check: https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_XFS If after the check everything looks good you can then rebuild it to the old or new disk.
January 13, 20179 yr Author I will look in to the cables. Never had a problem and it's been running fro awhile. This is what I see with a check on /dev/md7 Phase 1 - find and verify superblock... - block cache size set to 512616 entries Phase 2 - using internal log - zero log... zero_log: head block 571635 tail block 565904 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. the weird this is that the filesystem still shows as parity is valid and not being emulated.
January 13, 20179 yr Author Ok. Ran it with -L . And it found a bunch of errors. Can I just add it back to array now?
January 13, 20179 yr Community Expert Start the array like it is, without assigning the old disk, and check that the emulated disk now mounts and all data appears intact.
January 13, 20179 yr Community Expert If data looks OK you can stop the array, reassign disk7 and start the array to begin the rebuild. If you're not going to replace the sata cables before the rebuild post new diagnostics after it finishes and before rebooting.
January 13, 20179 yr Author Ok. Rebuilding now. I will post diags when finished. Weird thing is that couchpotato still won't start but I'll deal with that after the rebuild. Thanks so much for your help.
January 14, 20179 yr Author Here are the diags after rebuild before reboot. tower-diagnostics-20170114-1719.zip
January 14, 20179 yr Community Expert Most disks held their values, but these three didn't, attributes before and after the rebuild: Device Model: ST3000DM001-9YN166 Serial Number: W1F07LAX 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 35 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 56 Device Model: ST31000524AS Serial Number: 5VP9LX31 199 UDMA_CRC_Error_Count 0x003e 200 198 000 Old_age Always - 98 199 UDMA_CRC_Error_Count 0x003e 200 198 000 Old_age Always - 102 Device Model: ST31000524AS Serial Number: 5VP9SA85 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 86 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 89 So there's still an issue, start by replacing these SATA cables and keep monitoring the other disks for a few weeks.
January 18, 20179 yr Author OK. I'll replace the cables as soon as I can and take a look. Thanks again!!
Archived
This topic is now archived and is closed to further replies.