August 17, 20241 yr Community Expert 8 hours ago, Scuba_Steve said: and still It is not mounting when I start the array. That's expected, if the actual disk is mounting with UD you can do a new config to re-enable it, you can also check parity is valid before array start, but then run a correcting parity check right after array start.
August 17, 20241 yr Author When I try to mount, I get this pop error and I am not able to proceed. Do I need to proceed with creating a new config?
August 20, 20241 yr Community Expert That disk was unassigned, how are you checking the fs using the GUI? You can check with UD
August 20, 20241 yr Author I just ran UD for FS check. Here is the results. FS: xfs Executing file system check: /sbin/xfs_repair -n '/dev/sdg1' 2>&1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... Log inconsistent (didn't find previous header) failed to find log head zero_log: cannot find log head/tail (xlog_find_tail=5) - scan filesystem freespace and inode maps... sb_fdblocks 958435423, counted 989079561 - 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 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 6 - agno = 2 - agno = 4 - agno = 5 - agno = 8 - agno = 12 - agno = 7 - agno = 15 - agno = 11 - agno = 13 - agno = 14 - agno = 10 - agno = 1 - agno = 9 - agno = 16 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... Maximum metadata LSN (5:1925555) is ahead of log (0:0). Would format log to cycle 8. No modify flag set, skipping filesystem flush and exiting. File system corruption detected!
August 20, 20241 yr Author This is the results when I select Run with Corrected Flag. FS: xfs Executing file system check: /sbin/xfs_repair -e '/dev/sdg1' 2>&1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... Log inconsistent (didn't find previous header) failed to find log head zero_log: cannot find log head/tail (xlog_find_tail=5) ERROR: The log head and/or tail cannot be discovered. Attempt to mount the filesystem to replay the log or use the -L option to destroy the log and attempt a repair. Dirty log detected! Do I want to proceed with Force Log Zeroing?
August 21, 20241 yr Author Here is the output from Force Log Zeroing. FS: xfs Executing file system check: /sbin/xfs_repair -e -L '/dev/sdh1' 2>&1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... Log inconsistent (didn't find previous header) failed to find log head zero_log: cannot find log head/tail (xlog_find_tail=5) - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata sb_fdblocks 958435423, counted 989079561 - 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 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 17291286848 no . entry for directory 17291286848 no .. entry for directory 17291286848 problem with directory contents in inode 17291286848 cleared inode 17291286848 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 17291286878 no . entry for directory 17291286878 no .. entry for directory 17291286878 problem with directory contents in inode 17291286878 cleared inode 17291286878 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 17302820448 no . entry for directory 17302820448 no .. entry for directory 17302820448 problem with directory contents in inode 17302820448 cleared inode 17302820448 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 17348127099 no . entry for directory 17348127099 no .. entry for directory 17348127099 problem with directory contents in inode 17348127099 cleared inode 17348127099 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 17348127590 no . entry for directory 17348127590 no .. entry for directory 17348127590 problem with directory contents in inode 17348127590 cleared inode 17348127590 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 18215397267 no . entry for directory 18215397267 no .. entry for directory 18215397267 problem with directory contents in inode 18215397267 cleared inode 18215397267 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 18215397289 no . entry for directory 18215397289 no .. entry for directory 18215397289 problem with directory contents in inode 18215397289 cleared inode 18215397289 xfs_repair: read failed: Input/output error can't read block 0 for directory inode 18215572818 xfs_repair: read failed: Input/output error can't read block 1 for directory inode 18215572818 no . entry for directory 18215572818 no .. entry for directory 18215572818 problem with directory contents in inode 18215572818 cleared inode 18215572818 xfs_repair: read failed: Input/output error cannot read inode 18219945536, disk block 18219945472, cnt 32 Disk 1 still does not mount. I am not sure how or why this happened. It all started when I swapped out my parity drive and the parity drive never rebuilt properly. Why can't I just put the original parity drive back?
August 21, 20241 yr Community Expert 1 hour ago, Scuba_Steve said: xfs_repair: read failed: Input/output error xfs_repair is failing, post new diags.
August 21, 20241 yr Author It looked like it was going to work, then still will not mount. uss-enterprise-diagnostics-20240821-1845.zip
August 22, 20241 yr Community Expert Aug 21 18:45:19 USS-ENTERPRISE kernel: mpt2sas_cm0: log_info(0x31110d00): originator(PL), code(0x11), sub_code(0x0d00) Aug 21 18:45:19 USS-ENTERPRISE kernel: scsi_io_completion_action: 50 callbacks suppressed Aug 21 18:45:19 USS-ENTERPRISE kernel: sd 1:0:6:0: [sdh] tag#3067 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=3s Aug 21 18:45:19 USS-ENTERPRISE kernel: sd 1:0:6:0: [sdh] tag#3067 Sense Key : 0x2 [current] Aug 21 18:45:19 USS-ENTERPRISE kernel: sd 1:0:6:0: [sdh] tag#3067 ASC=0x4 ASCQ=0x0 Aug 21 18:45:19 USS-ENTERPRISE kernel: sd 1:0:6:0: [sdh] tag#3067 CDB: opcode=0x88 88 00 00 00 00 05 80 00 00 98 00 00 00 10 00 00 Aug 21 18:45:19 USS-ENTERPRISE kernel: blk_print_req_error: 50 callbacks suppressed Aug 21 18:45:19 USS-ENTERPRISE kernel: I/O error, dev sdh, sector 23622320280 op 0x0:(READ) flags 0x800 phys_seg 2 prio class 2 Aug 21 18:45:19 USS-ENTERPRISE kernel: sd 1:0:6:0: [sdh] tag#3071 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Aug 21 18:45:19 USS-ENTERPRISE kernel: sd 1:0:6:0: [sdh] tag#3071 Sense Key : 0x2 [current] Aug 21 18:45:19 USS-ENTERPRISE kernel: sd 1:0:6:0: [sdh] tag#3071 ASC=0x4 ASCQ=0x0 Aug 21 18:45:19 USS-ENTERPRISE kernel: sd 1:0:6:0: [sdh] tag#3071 CDB: opcode=0x88 88 00 00 00 00 05 80 00 00 a0 00 00 00 08 00 00 Problems with that disk, SMART looks fine, so try replacing the cables, run xfs_repair again and post new diags if it still fails to repair.
August 22, 20241 yr Author How can I have so many issues just from changing my parity drive. How can I replace my original parity drive?
August 22, 20241 yr Author Thank you for your help. I am just getting a bit frustrated. I have had zero issues for such a long time and now I am worried about losing data.
August 23, 20241 yr Author This is the output from XFS repair using UD. FS: xfs Executing file system check: /sbin/xfs_repair -n '/dev/sdg1' 2>&1 Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... - scan filesystem freespace and inode maps... - 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 - agno = 4 - agno = 5 - agno = 6 - agno = 7 - agno = 8 - agno = 9 - agno = 10 - agno = 11 - agno = 12 - agno = 13 - agno = 14 - agno = 15 - agno = 16 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 3 - agno = 6 - agno = 8 - agno = 2 - agno = 5 - agno = 7 - agno = 10 - agno = 9 - agno = 11 - agno = 12 - agno = 15 - agno = 4 - agno = 14 - agno = 1 - agno = 13 - agno = 16 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. No file system corruption detected! Disk 1 is still showing Unmountable. uss-enterprise-diagnostics-20240822-1901.zip
August 23, 20241 yr Community Expert 1 hour ago, Scuba_Steve said: No file system corruption detected! Disk 1 is still showing Unmountable. You weren't repairing disk1. But can you mount the unassigned sdg and see its contents?
August 23, 20241 yr Author Here is the output with -n Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock... ..........found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... ...........found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .......Sorry, could not find valid secondary superblock I am not able to see the contents due to the drive is unmountable. uss-enterprise-diagnostics-20240822-2105.zip
August 23, 20241 yr Community Expert 6 hours ago, Scuba_Steve said: Here is the output with -n From which disk is this?
August 23, 20241 yr Community Expert … and if not done using the GUI exactly what command did you use (it is easy to get it wrong)?
August 23, 20241 yr Author The XFS repair is on disk 1. The disk still does not mount. I used the GUI for the repair. Edited August 23, 20241 yr by Scuba_Steve
August 23, 20241 yr Community Expert 10 hours ago, trurl said: can you mount the unassigned sdg and see its contents?
August 23, 20241 yr Author When I try mounting the drive it will not mount and I am not able to view the contents of the drive.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.