October 24, 20169 yr Hi, So here is what happened - stopped array via stop array now button ( first mistake ) - server sat there the webgui was frozen ... I would assume attempting to unmount in use disks - I attempted to power down my server via the power button ( no luck ) ( second mistake ) - pulled the power on my server ( third mistake ) - booted it back up - now I have no webgui and its failing to mount the array - and i'm pretty much lost on where to go from here - I have ssh access to the server and I have attached a copy of the syslog ( its not the pre shutdown one but still shown errors) and a diagnostics report - Everything seems to be ok in the log till "Oct 23 20:24:55 Tower kernel: XFS (md2): Internal error XFS_WANT_CORRUPTED_GOTO at line 1627 of file fs/xfs/libxfs/xfs_alloc.c." - And Oct 23 20:24:55 Tower kernel: XFS (md2): Failed to recover EFIs Any help would be greatly appreciated. I'm not sure if this is recoverable or not, if even partially Thank You ! Ryan syslog.txt tower-diagnostics-20161023-2117.zip
October 24, 20169 yr Community Expert If enable disable array autostart by editing disk.cfg on your flash drive (in the config folder): change startArray="yes" to "no" Then start in maintenance mode and run xfs_repair on disk2. https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_XFS
October 24, 20169 yr Author Here is the output of xfs_repair, also disabling autostart brought my webgui back. Should I proceed with the -L option ? or attempt to mount the file system ? xfs_repair -v /dev/md2 Phase 1 - find and verify superblock... - block cache size set to 483192 entries Phase 2 - using internal log - zero log... zero_log: head block 1823858 tail block 1823803 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.
October 24, 20169 yr Community Expert Because unRAID crashes attempting to mount the disk you have to use -L, usually there's no data loss.
October 24, 20169 yr Author here is the output of xfs_repair, I would assume the next step to to mount everything? xfs_repair -v -L /dev/md2 Phase 1 - find and verify superblock... - block cache size set to 483192 entries Phase 2 - using internal log - zero log... zero_log: head block 1823858 tail block 1823803 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... sb_fdblocks 481149648, counted 481157840 - 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 Metadata CRC error detected at block 0xb94ea468/0x1000 bad directory block magic # 0x454e7064 in block 0 for directory inode 3302913292 corrupt block 0 in directory inode 3302913292 will junk block no . entry for directory 3302913292 no .. entry for directory 3302913292 problem with directory contents in inode 3302913292 cleared inode 3302913292 - agno = 2 imap claims a free inode 5011562904 is in use, correcting imap and clearing inode cleared inode 5011562904 imap claims a free inode 5011562905 is in use, correcting imap and clearing inode cleared inode 5011562905 imap claims a free inode 5011562906 is in use, correcting imap and clearing inode cleared inode 5011562906 imap claims a free inode 5011562907 is in use, correcting imap and clearing inode cleared inode 5011562907 data fork in ino 5011562909 claims free block 629109648 data fork in ino 5011562909 claims free block 629109649 data fork in regular inode 5011562910 claims used block 626441194 correcting nextents for inode 5011562910 bad data fork in inode 5011562910 cleared inode 5011562910 imap claims a free inode 5011579177 is in use, correcting imap and clearing inode cleared inode 5011579177 imap claims a free inode 5032894255 is in use, correcting imap and clearing inode cleared inode 5032894255 imap claims a free inode 5074494967 is in use, correcting imap and clearing inode cleared inode 5074494967 imap claims a free inode 5091219074 is in use, correcting imap and clearing inode cleared inode 5091219074 - agno = 3 data fork in regular inode 7182664326 claims used block 897833045 correcting nextents for inode 7182664326 bad data fork in inode 7182664326 cleared inode 7182664326 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 3 - agno = 1 entry "chapter7.jpg" at block 0 offset 240 in directory inode 7182461141 references free inode 7182464106 clearing inode number in entry at offset 240... entry "chapter8.jpg" at block 0 offset 264 in directory inode 7182461141 references free inode 7182464108 clearing inode number in entry at offset 264... data fork in ino 5011532016 claims dup extent, off - 0, start - 626441194, cnt 1 correcting nextents for inode 5011532016 bad data fork in inode 5011532016 cleared inode 5011532016 entry "posters" in shortform directory 5011562908 references free inode 2778437697 junking entry "posters" in directory inode 5011562908 entry "Info.xml" in shortform directory 5011562908 references free inode 5011562910 junking entry "Info.xml" in directory inode 5011562908 corrected i8 count in directory 5011562908, was 3, now 2 entry "1.xml" in shortform directory 5011563074 references free inode 5012312156 junking entry "1.xml" in directory inode 5011563074 corrected i8 count in directory 5011563074, was 1, now 0 corrected directory 5011563074 size, was 10, now 6 bogus .. inode number (0) in directory inode 5011563074, clearing inode number entry "art" in shortform directory 773216172 references free inode 3302913292 junking entry "art" in directory inode 773216172 entry "posters" in shortform directory 7182613998 references free inode 5011562904 junking entry "posters" in directory inode 7182613998 corrected i8 count in directory 7182613998, was 3, now 2 entry "Info.xml" in shortform directory 7182627573 references free inode 7182614087 junking entry "Info.xml" in directory inode 7182627573 corrected i8 count in directory 7182627573, was 3, now 2 entry "seasons" in shortform directory 5011582008 references free inode 5011583821 junking entry "seasons" in directory inode 5011582008 corrected i8 count in directory 5011582008, was 3, now 2 data fork in ino 7182662930 claims dup extent, off - 0, start - 897833045, cnt 1 correcting nextents for inode 7182662930 bad data fork in inode 7182662930 cleared inode 7182662930 entry "80b5509665f47628169c3e97ff26aa1a413b7a.content" at block 0 offset 2464 in directory inode 7182725133 references free inode 7182662930 clearing inode number in entry at offset 2464... entry "ac7871a9d1c653134b8794e63b7421096f3c56a2" at block 0 offset 824 in directory inode 5143378875 references free inode 5101416651 clearing inode number in entry at offset 824... entry "Media_db.db" in shortform directory 7227483153 references free inode 7227302023 junking entry "Media_db.db" in directory inode 7227483153 corrected i8 count in directory 7227483153, was 9, now 8 Phase 5 - rebuild AG headers and trees... - agno = 0 - agno = 1 - agno = 2 - agno = 3 - reset superblock... Phase 6 - check inode connectivity... - resetting contents of realtime bitmap and summary inodes - traversing filesystem ... - agno = 0 entry "Subtitle Contributions" in directory inode 773062430 not consistent with .. value (5011525433) in inode 7182564656, junking entry fixing i8count in inode 773062430 - agno = 1 entry "episodes" in dir ino 2778301150 doesn't have a .. entry, will set it in ino 5011563074. entry "seasons" in directory inode 2778320247 not consistent with .. value (2778324746) in inode 5011382467, junking entry fixing i8count in inode 2778320247 - agno = 2 entry "Subtitles.xml" in shortform directory inode 5011356278 points to free inode 5011532016 junking entry fixing i8count in inode 5011356278 entry "6" in directory inode 5011389294 references already connected inode 7182464113. junking entry fixing i8count in inode 5011389294 entry "art" in directory inode 5011562908 references already connected inode 7182614014. junking entry entry "extras" in directory inode 5011562908 not consistent with .. value (7182624731) in inode 773244327, junking entry fixing i8count in inode 5011562908 bad hash table for directory inode 5143378875 (no data entry): rebuilding rebuilding directory inode 5143378875 - agno = 3 bad hash table for directory inode 7182461141 (no data entry): rebuilding rebuilding directory inode 7182461141 bad hash table for directory inode 7182480395 (no data entry): rebuilding rebuilding directory inode 7182480395 bad hash table for directory inode 7182494609 (no data entry): rebuilding rebuilding directory inode 7182494609 fixing ftype mismatch (2/1) in directory/child inode 7182627573/7182629978 bad hash table for directory inode 7182725133 (no data entry): rebuilding rebuilding directory inode 7182725133 setting .. in sf dir inode 5011563074 to 2778301150 - traversal finished ... - moving disconnected inodes to lost+found ... disconnected dir inode 773090530, moving to lost+found disconnected dir inode 773090531, moving to lost+found disconnected dir inode 773090532, moving to lost+found disconnected dir inode 773090533, moving to lost+found disconnected dir inode 773179831, moving to lost+found disconnected inode 3302913293, moving to lost+found disconnected inode 3302913294, moving to lost+found disconnected inode 3302913295, moving to lost+found disconnected inode 3302913296, moving to lost+found disconnected inode 3302913297, moving to lost+found disconnected inode 3302913298, moving to lost+found disconnected inode 3302913299, moving to lost+found disconnected inode 3302913300, moving to lost+found disconnected inode 3302913301, moving to lost+found disconnected inode 3302913302, moving to lost+found disconnected inode 3302913303, moving to lost+found disconnected dir inode 5011562908, moving to lost+found disconnected inode 5011583819, moving to lost+found disconnected inode 5011699580, moving to lost+found disconnected inode 5101416660, moving to lost+found disconnected inode 5101416661, moving to lost+found disconnected inode 5101416662, moving to lost+found disconnected inode 5101416663, moving to lost+found disconnected inode 5101416666, moving to lost+found disconnected inode 5101416677, moving to lost+found disconnected inode 5101416678, moving to lost+found disconnected inode 5101416679, moving to lost+found disconnected inode 5101416687, moving to lost+found disconnected inode 5101416688, moving to lost+found disconnected inode 7225789829, moving to lost+found Phase 7 - verify and correct link counts... resetting inode 772909583 nlinks from 2 to 8 resetting inode 773062430 nlinks from 6 to 5 resetting inode 773216172 nlinks from 4 to 3 resetting inode 773264726 nlinks from 3 to 2 resetting inode 773265087 nlinks from 3 to 2 resetting inode 2778320247 nlinks from 3 to 2 resetting inode 5011389294 nlinks from 3 to 2 resetting inode 5011401562 nlinks from 1 to 2 resetting inode 5011562908 nlinks from 5 to 2 resetting inode 5011582008 nlinks from 4 to 3 resetting inode 5011583820 nlinks from 1 to 2 resetting inode 7182613998 nlinks from 5 to 4 resetting inode 7182627573 nlinks from 3 to 2 Metadata corruption detected at block 0x11b722b28/0x1000 libxfs_writebufr: write verifer failed on bno 0x11b722b28/0x1000 Metadata corruption detected at block 0x11b722b28/0x1000 libxfs_writebufr: write verifer failed on bno 0x11b722b28/0x1000 XFS_REPAIR Summary Mon Oct 24 06:53:18 2016 Phase Start End Duration Phase 1: 10/24 06:48:44 10/24 06:48:44 Phase 2: 10/24 06:48:44 10/24 06:51:33 2 minutes, 49 seconds Phase 3: 10/24 06:51:33 10/24 06:52:58 1 minute, 25 seconds Phase 4: 10/24 06:52:58 10/24 06:52:58 Phase 5: 10/24 06:52:58 10/24 06:52:58 Phase 6: 10/24 06:52:58 10/24 06:52:59 1 second Phase 7: 10/24 06:52:59 10/24 06:52:59 Total run time: 4 minutes, 15 seconds done root@Tower:~#
October 24, 20169 yr Author There are some files and folders in there, but it would appear to be plex metadata files nothing over 40KB . It looks like its back up and running do I just delete everything in there ? Thank you very much !
October 24, 20169 yr Community Expert do I just delete everything in there ? If there's nothing of interest you can deleted them.
October 24, 20169 yr Community Expert Glad you got it solved. For future reference, it isn't necessary to post a syslog and diagnostics, because diagnostics already includes the syslog. Just post diagnostics.
October 24, 20169 yr Author Thank You johnnie.black for all your help ! I noticed that syslog was in there after posting it thank you trurl
Archived
This topic is now archived and is closed to further replies.