September 23, 20169 yr I upgraded to 6.2 without a hitch. installed libreelec next to my windows 7 vm. had an issue an tried to kill libreelec but web interface hung so I rebooted. now can't start array and get the attached log. syslog.txt
September 23, 20169 yr Community Expert You need to start in maintenance mode and run xfs_repair on disk1. If array is set to autostart disable it by editing disk.cfg on your flash drive (in the config folder): change startArray="yes" to "no" Then: https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_XFS
September 23, 20169 yr Author oh thanks, i see the error now in the log, i glossed right over it. I'm running the check, that drive has been good to me so far so I hope it's a simple auto fix.
September 23, 20169 yr Author got this output, should I try to start array or do i have a problem? Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... Metadata corruption detected at xfs_agf block 0xe8e05f31/0x200 flfirst 118 in agf 2 too large (max = 118) agf 118 freelist blocks bad, skipping freelist scan sb_icount 327104, counted 343808 sb_ifree 1583, counted 71 sb_fdblocks 38649300, counted 38276235 - 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 = 0 - agno = 1 - agno = 2 - agno = 3 No modify flag set, skipping phase 5 Phase 6 - check inode connectivity... - traversing filesystem ... - traversal finished ... - moving disconnected inodes to lost+found ... Phase 7 - verify link counts... No modify flag set, skipping filesystem flush and exiting.
September 23, 20169 yr Community Expert Those messages show that you DO have corruption (the messages about meta-data corruption. You will now need to run the repair in write mode (i.e. without the -n option). You may also be prompted to add the -L option, and if so you will need to do that as well.
September 23, 20169 yr Author hooray I'm back up and running. thank you so much. what a great support forum!
Archived
This topic is now archived and is closed to further replies.