December 6, 20196 yr Looking for advice on cause and how to do xfs_repair without causing further damage. Oldest diagnostics syslog had bunch of errors, looks to be caused after file system was taken offline after xfs error. Powered down and checked SATA cables, brought back up and disk 2 was unmountable and left it for advice to minimize loss. Edit: Ran xfs_repair -n on disk2 and it is a mess (1900+ lines). Last parity sync was 14 days ago and was clean. Format and rebuild? Replace disk2 and rebuild? Edited December 8, 20196 yr by unevent
December 6, 20196 yr Rebuilding a disk won't fix filesystem corruption, you need to run xfs_repair without -n.
December 6, 20196 yr Author Ran xfs_repair without options and completed on disk2. Will look in lost+found later today to see what was trashed. What would be recommended path to get back online at this point? Never had corruption and been using since 4.7 days. Never even had parity sync issue.
December 6, 20196 yr 16 minutes ago, unevent said: What would be recommended path to get back online at this point? Not sure I understand the question, just start the array.
December 7, 20196 yr Author Thanks for the help. I had started array in maintenance mode and still showed unmountable. Remember stories inthe past about starting array with a troubled disk and loosing data. Started array normally and now sorting through lost+found to see what I need to replace. Thanks again.
December 7, 20196 yr 14 hours ago, unevent said: Ran xfs_repair without options and completed on disk2. When doing filesystem repair you should capture exactly your input and the resulting output so you can post them.
December 7, 20196 yr 6 hours ago, unevent said: I had started array in maintenance mode and still showed unmountable. Disks won't mount in maintenance mode.
December 7, 20196 yr Author 14 hours ago, trurl said: When doing filesystem repair you should capture exactly your input and the resulting output so you can post them. I have the logs. Just had no need to post drive contents to the world. Lost 1.25TB on this drive. Perhaps a feature request is to halt parity when xfs reports first error so instead of parity protecting the corruption it keeps the parity intact as much as possible. Seven plus years with unRaid and first case of corruption and with xfs and data loss. No power loss, no unclean shutdowns.
December 7, 20196 yr Author 9 hours ago, johnnie.black said: Disks won't mount in maintenance mode. lol...yes and second sentence further from that was I started the array normally.
Archived
This topic is now archived and is closed to further replies.