January 30, 201610 yr I was happily accessing my shares last night through Windows when suddenly they all disconnected. I logged into the webGUI to find the array stopped. When I attempt to restart the array, the system hangs and the entire GUI is unresponsive. The only way to remedy it is to hard shutdown the machine and power it back on. When I do this, I'm able to get back to the GUI, and access anything, but am never able to successfully start the array. I've tried a clean reboot after a hard shutdown, I've looked at my log and don't see any errors. I pulled the thumb drive over to Windows and did a chkdsk. Any idea what the culprit it? I did have a power loss in the house a few days ago, but was able to restart and parity check fine. This is now just a sudden problem.
January 30, 201610 yr post your diagnostics (tools - diagnostics). Ideally, I guess you should try and start the array normally, then telnet / putty in and grab the diagnostics by entering "diagnostics" at the command line (the file will be saved onto your flash drive) and post that.
January 31, 201610 yr Community Expert Possible file system corruption, start by https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_XFS Crash happens when trying to mount disk1, so start with it.
January 31, 201610 yr Author Here's what I get when I try to repair: xfs_repair -v /dev/md1 Phase 1 - find and verify superblock... - block cache size set to 652392 entries Phase 2 - using internal log - zero log... zero_log: head block 3418010 tail block 3418006 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. Do you know the syntax for clearing the log? I tried xfs_repair -l /dev/md1 but it didn't work.
January 31, 201610 yr Community Expert Here's what I get when I try to repair: xfs_repair -v /dev/md1 Phase 1 - find and verify superblock... - block cache size set to 652392 entries Phase 2 - using internal log - zero log... zero_log: head block 3418010 tail block 3418006 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. Do you know the syntax for clearing the log? I tried xfs_repair -l /dev/md1 but it didn't work. You need to use -L and not -l (Linux is case sensitive).
January 31, 201610 yr Author Just came back to note that I had figured that out with some google-fu. Destroyed the log and re-ran -v. It worked! I'm back up and running with all of my files intact. Thank you all for the assistance!
Archived
This topic is now archived and is closed to further replies.