July 2, 201610 yr All, I recently upgraded to Unraid V6. After that I decided to change the file systems on my disks to XFS. It has not gone as smoothly as I'd hoped. During that process, I've had a few data disks fail and they have been replaced. All of my disks and, thankfully all of my data seems intact. However, at one point, I could not access my user shares. They were not visible on the unRaid GUI and I could not access them via windows. I looked at my log and it suggested that I run XFS_Repiar on one of my new disks. I did so and the shares became both visible and accessible again. However, when I access my user shares, only some of the files that should be there are there. For example, some of the folders in "video" are there but not all of the folders and none of the individual files that are not in folders. I can access individual disks that have a "video" folder and all of the files & folders are there, but they are not accesible through my mapped drives. Several of my shares indicate that "some or all of the files are not protected". My scheduled monthly parity check is currently running, but it usually takes about two days. My last log can be found here: https://dl.dropboxusercontent.com/u/5155002/tower-diagnostics-20160701-1949.zip Thanks all John
July 2, 201610 yr Community Expert You have file system corruption on disk8, run xfs_repair. Edit: There's also corruption on your docker image, you should delete and re-create it.
July 2, 201610 yr Author I ran xfs_repair on disk 8 and got the following result: ERROR: The filesystem has valuable metadata changes in the 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 a mount of the filesystem before doing this. I now cannot mount disk 8. I am unfamiliar with any of this and I'm hesitant to proceed without some extra advice. Would the command with the -L option be: xfs_repair -L /dev/md8? What can I expect from here? https://dl.dropboxusercontent.com/u/5155002/tower-diagnostics-20160702-0938.zip Many thanks John
July 2, 201610 yr Community Expert If it can't be mounted I think it's your only option, but you may wait a while to see if someone else has another idea. You can include -v for verbose output: xfs_repair -v -L /dev/md8
July 2, 201610 yr Author Thanks, It's my only problematic disk right now and my parity is valid (although it just finished the check yesterday, when this disk was presumably already having errors). Would it be advisable to just re-create the file system on the bad disk and attempt a data rebuild? Or should I save that as a last resort?
July 2, 201610 yr Community Expert Parity can't fix file system errors, a rebuild will recreate the disk as it is now, file system corruption included.
July 2, 201610 yr Community Expert During that process, I've had a few data disks fail and they have been replaced. All of my disks and, thankfully all of my data seems intact. File system corruption probably comes from errors during the previous rebuilds, e.g., if during the rebuild of one disk there were errors on another one.
July 2, 201610 yr Would it be advisable to just re-create the file system on the bad disk and attempt a data rebuild? Or should I save that as a last resort? No! If you re-create the file system, a data rebuild will rebuild the new empty file system.
July 2, 201610 yr Author Great success! xfs_repair -v -L /dev/md8 Seems to have fixed the majority of my problems. I can now access all the files that were in my shares. Many thanks gentlemen, John
Archived
This topic is now archived and is closed to further replies.