December 15, 20169 yr My Unraid array crashed, and when I rebooted it (it was totally non-responsive), it didn't come up. I've done Memtest and it passed without errors... System halts as array tries to come online, or, if not trying to come online, unraid will stop responding within a couple of minutes of reboot while I'm trying to get in and do stuff... I can reboot the unit locally, and have done that a few times.. If I hard reboot, the array will come back up, but I'm not able to get to the GUI, although I did one time... Very odd. Attached is a syslog and diag pack, as well as some screenshots from the crash window from different crashes. tower-diagnostics-20161214-1834.zip
December 15, 20169 yr Author One other thing I noticed is that while crashed it seemed to be spamming the hell out of my LAN. My guess is lots of broadcast traffic, but didn't fireup wireshark to confirm. Follow on NOte, System does boot up in Safe Mode, and array will start in maintenance Mode... I saw an error message related to /dev/sdo, and removed it, rebooted, and still have the same problem.
December 15, 20169 yr Author One last log to post... This was a tail -f of /var/log/syslog while I started the array. Dec 14 21:04:30 Tower emhttp: shcmd (341): set -o pipefail ; mount -t xfs -o noatime,nodiratime /dev/md2 /mnt/disk2 |& logger Dec 14 21:04:30 Tower kernel: XFS (md2): Mounting V5 Filesystem Dec 14 21:04:30 Tower kernel: XFS (md2): Starting recovery (logdev: internal) Dec 14 21:04:32 Tower kernel: XFS (md2): Internal error XFS_WANT_CORRUPTED_GOTO at line 3156 of file fs/xfs/libxfs/xfs_btree.c. Caller xfs_free_ag_extent+0x419/0x558 Dec 14 21:04:32 Tower kernel: CPU: 5 PID: 7487 Comm: mount Not tainted 4.4.30-unRAID #2 Dec 14 21:04:32 Tower kernel: Hardware name: Gigabyte Technology Co., Ltd. Z97X-UD7 TH/Z97X-UD7 TH-CF, BIOS F4 05/30/2014 Dec 14 21:04:32 Tower kernel: 0000000000000000 ffff88045ecdba38 ffffffff8136f79f ffff88047b14c820 Dec 14 21:04:32 Tower kernel: 0000000000000000 ffff88045ecdba50 ffffffff81275fd0 ffffffff812465ad Dec 14 21:04:32 Tower kernel: ffff88045ecdbac0 ffffffff8125a774 ffffffff8125998e 000000005ec1c1d0 Dec 14 21:04:32 Tower kernel: Call Trace: Full file is attached... BringUpArrayCrash.txt
December 15, 20169 yr Community Expert You need to check filesystem on disk2. https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_XFS
December 15, 20169 yr Author You need to check filesystem on disk2. https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_XFS That resolved it. With -L. Sent from my iPhone using Tapatalk
Archived
This topic is now archived and is closed to further replies.