karlpox Posted April 17, 2017 Share Posted April 17, 2017 Hi, Â Need help getting access to web gui again. All I did was transfer 500gb of data to the unraid server, after maybe 20seconds of doing this the file transfer freezes and I rebooted both server ang source of data PC. I rebooted about 5 times each trying to figure things out and now I no longer have access to my web gui. Â I got the syslog from my USB. I did a diagnostic on the server by plugging it to a monitor. syslog.txt syslog.txt Link to comment
JorgeB Posted April 17, 2017 Share Posted April 17, 2017 Disable array auto-start by editing disk.cfg on your flash drive (config/disk.cfg) and changing startArray="yes" to "no". Â Then start the array in maintenance mode and check filesystem on disk4 (md4): Â https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_XFS Link to comment
karlpox Posted April 18, 2017 Author Share Posted April 18, 2017 Hi Johnnie.black,  I did what you said. and heres what I got.  Phase 1 - find and verify superblock... - block cache size set to 324824 entries Phase 2 - using internal log - zero log... zero_log: head block 1544354 tail block 1520767 - scan filesystem freespace and inode maps... Metadata corruption detected at xfs_agf block 0xaea851b1/0x200 flfirst 118 in agf 2 too large (max = 118) agf 118 freelist blocks bad, skipping freelist scan sb_icount 905152, counted 905600 sb_ifree 155, counted 95 sb_fdblocks 254455625, counted 238421612 - found root inode chunk Phase 3 - for each AG... - scan (but don't clear) agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 1 - agno = 3 - agno = 2 - agno = 0 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting. XFS_REPAIR Summary Tue Apr 18 12:14:25 2017 Phase Start End Duration Phase 1: 04/18 12:10:24 04/18 12:10:24 Phase 2: 04/18 12:10:24 04/18 12:10:32 8 seconds Phase 3: 04/18 12:10:32 04/18 12:12:53 2 minutes, 21 seconds Phase 4: 04/18 12:12:53 04/18 12:12:54 1 second Phase 5: Skipped Phase 6: 04/18 12:12:54 04/18 12:14:25 1 minute, 31 seconds Phase 7: 04/18 12:14:25 04/18 12:14:25 Total run time: 4 minutes, 1 second I then logged into SSH and did a  xfs_repair -v /dev/md4 and got this error.  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. What do I do next?   Link to comment
JorgeB Posted April 18, 2017 Share Posted April 18, 2017 Use -L, usually there's no data loss. Link to comment
karlpox Posted April 18, 2017 Author Share Posted April 18, 2017 Im doing a parity check now. Ill try the -L afterwards. Is that ok? Link to comment
karlpox Posted April 18, 2017 Author Share Posted April 18, 2017 OK, ill update this thread later. It needs 4 hrs to finish the parity check. Link to comment
karlpox Posted April 18, 2017 Author Share Posted April 18, 2017 I got an error on parity check  unRAID Disk 2 error: 18-04-2017 15:28 Alert [SOBNOLOGY] - Disk 2 in error state (disk dsbl) WDC_WD30EFRX-68EUZN0_WD-WMC4N0K74C71 (sdh) Link to comment
JorgeB Posted April 18, 2017 Share Posted April 18, 2017 That's a different problem, post the diagnostics. Link to comment
karlpox Posted April 18, 2017 Author Share Posted April 18, 2017 I also got this error from check filesystem Phase 1 - find and verify superblock... superblock read failed, offset 0, size 524288, ag 0, rval -1 fatal error -- Input/output error  sobnology-diagnostics-20170418-1551.zip Link to comment
JorgeB Posted April 18, 2017 Share Posted April 18, 2017 You're are having issues on multiple disks, first thing to do is to power down and remove all disks from the Marvell controller (first 4 white ports), these are know to be problematic on those boards, use the Intel PCH ports only. Â After doing that power back on then grab and post new diags. Link to comment
karlpox Posted April 18, 2017 Author Share Posted April 18, 2017 Here's a fresh diags. I moved the 1st 4 white ports to the other intel ports. I checked the manual but cant check if the 1st 4 ports are the marvel ones. sobnology-diagnostics-20170418-1851.zip Link to comment
JorgeB Posted April 18, 2017 Share Posted April 18, 2017 OK, all disks are off the Marvell, never use those ports again.  Best now would be to do a new config and resync parity:  -tools -> new config -> on "retain current configuration" select "all" then click apply  Start array to begin parity sync. Link to comment
JorgeB Posted April 18, 2017 Share Posted April 18, 2017 You'll still need to run xfs_repair on disk4, before or after the parity sync. Link to comment
karlpox Posted April 18, 2017 Author Share Posted April 18, 2017 I already started the array. Cant access anything on the web gui, it just says mounting disks with a loading icon on the browser tab. Is this normal? Link to comment
JorgeB Posted April 18, 2017 Share Posted April 18, 2017 It's probably the file system issue on disk4, or on another disk, you should still be able to grab the diags in the console by typing diagnostics, upload those, if you can't, then reboot, start in maintenance mode and run xfs_repair on all disks. Link to comment
karlpox Posted April 18, 2017 Author Share Posted April 18, 2017 im on this page for 3 hours. is this normal? Link to comment
karlpox Posted April 18, 2017 Author Share Posted April 18, 2017 should i force reboot? Link to comment
JorgeB Posted April 18, 2017 Share Posted April 18, 2017 Get the diagnostics on the console, it should still work, and then, either way you'll need to reboot, first try on the console:  powerdown -r  If it doesn't reboot after a couple of minutes you need to press reset. Link to comment
karlpox Posted April 18, 2017 Author Share Posted April 18, 2017 Did a hard shutdown. I got into web gui again. sobnology-diagnostics-20170418-2233.zip Link to comment
JorgeB Posted April 18, 2017 Share Posted April 18, 2017 Those diags don't help, it would only help the ones from the console after starting the array, do that or start in maintenance mode and run xfs_repair on all disks. Â Â Link to comment
karlpox Posted April 18, 2017 Author Share Posted April 18, 2017 went to maintenance mode and then resync.. 5h 30m to finish. Hope this will be successful. Link to comment
JorgeB Posted April 18, 2017 Share Posted April 18, 2017 Just now, karlpox said: went to maintenance mode and then resync.. 5h 30m to finish. Hope this will be successful.  You still need to fix the file system on the problem disk(s) or it will crash again at array start. Link to comment
karlpox Posted April 18, 2017 Author Share Posted April 18, 2017 on which drives do i need to do this besides disk4? Im already running xfs_repair -L on disk4. Link to comment
karlpox Posted April 18, 2017 Author Share Posted April 18, 2017 root@sobnology:~# xfs_repair -L /dev/md4 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... Metadata corruption detected at xfs_agf block 0xaea851b1/0x200 flfirst 118 in agf 2 too large (max = 118) sb_icount 905152, counted 905600 sb_ifree 155, counted 95 sb_fdblocks 254455625, counted 238421619 - found root inode chunk Phase 3 - for each AG... - scan and clear agi unlinked lists... - process known inodes and perform inode discovery... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 3 - agno = 2 Phase 5 - rebuild AG headers and trees... - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify and correct link counts... Maximum metadata LSN (1:1544351) is ahead of log (1:2). Format log to cycle 4. done  Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.