October 7, 20169 yr Hello all! My system has been very smoothly running 6.19 and made the plunge some weeks ago to 6.20. All went well but after a few hours I noticed the system was down and XFS was noting errors on one of the drives repeatedly. Rebooted and tried again. Same thing later. On the third reboot, the drive was no longer mountable... Did a xfs_repair, clearing the log and thankfully the drive was back and the files all seemed to be there. This drive is especially important as it houses all my Plex metadata, among other goods. Back to 6.19 and all well again. Got the idea that perhaps a fix in 6.21 was implemented (I did not see one via the changelog...) so did the upgrade again. Same thing...XFS complaining. This time I have a screenshot. I just want to confirm that this is XFS having a physical issue with one of the drives. If so, why does this not appear under 6.19? I also need to know which drive this actually is (md1). I did not capture a syslog or dump from the system as I did not want any further corruption like the last time. Has something been tweaked that a marginal drive is now getting flagged? Kev.
October 7, 20169 yr Community Expert Chances are simply that 6.1.9 is not detecting the corruption. The 6.2 release has more recent versions of the XFS driver and xfs_repair tool. For reference /dev/md1 is disk1 in the unRAID GUI.
October 7, 20169 yr Author This is what I have been thinking. So...the fix is to run xfs_check and attempt a repair under 6.21? Odd that when I run it under 6.19 it is fine so things obviously have changed. Is there a way to boot UnRAID into maintenance mode so I can check the disks rather than via the GUI? I guess if I am quick I can stop the array and bring it back up via maintenance and let the check go. The safest plan is to have a backup of all the files I imagine prior to the upgrade and attempted repair I am thinking. Kev.
Archived
This topic is now archived and is closed to further replies.