March 13, 201610 yr My system hung as I was installing a Windows 10 VM. (I didn't catch the syslog unfortunately before attempting a reboot). Rebooted, but couldn't access the WebGUI. SSH'd to the machine to try to figure out what's wrong, but also found that the hard drive that had the VM on it was not mounting. After attempting to mount, the session hangs and I have to open a new Putty session. Reboot/shutdown commands don't do anything except hang the session until Ctrl+C is pressed and then it acts like nothing's happened. I'm at a loss of what to try next and any help would be appreciated. syslog.zip
March 13, 201610 yr Author Yup I have tried clearing the cache on the machine. Have also tried on multiple devices including my phone. Another reason I know it's not running is that the dockers (Plex, PlexRequests, RuTorrent, ect) are all not running.
March 13, 201610 yr Author UPDATE: After recreating the USB drive to wipe everything. It seems to hang when trying to mount the same hard drive as the one that was installing Windows 10 on it. I am assuming that somehow during the installation it corrupted something on the drive. Any ideas on how to repair this without formatting and losing my data? Each time I try to mount, it hangs. GUI or the CLI window I am trying it on. Also can't "kill" the mount process.
March 13, 201610 yr Community Expert What format is the drive in? Is it a data disk? The chances are that you are going to need to run one of the disk recovery tools against it and the one you use varies with the format. Have you tried starting the array in Maintenance mode? That is required if you are going to want to maintain parity while repairing the a data disk's file system. It is probably worth posting the diagnostics file for your system (Tools->Diagnostics) so we can see if there is any obvious problem showing up.
March 14, 201610 yr Author It is in xfs format and is a data disk. I have tried maintenance mode, but I haven't had any luck mounting the disks manually. tower-diagnostics-20160313-2237.zip
March 14, 201610 yr Author Metadata corruption detected at xfs_agf block 0x1/0x200 flfirst 118 in agf 0 too large (max = 118) agf 118 freelist blocks bad, skipping freelist scan sb_ifree 48711, counted 48705 sb_fdblocks 484657295, counted 483211524 Found this with the scan.
March 14, 201610 yr Author @tking4808: Thank you. after starting in maintenance mode and using the built-in repair option. I got it up and running. Time to start building over now.
Archived
This topic is now archived and is closed to further replies.