February 10, 20242 yr Hi, After a reboot this morning I get this error on one of my drives in the array. is it dead or is there something I can do to get it back before I swap it out? I've attached a diagnostics dump in case it s needed. thanks for any help offered. Edd sag-a-star-diagnostics-20240210-1202.zip Edited February 10, 20242 yr by ApriliaEdd Solved
February 10, 20242 yr Community Expert Which disk is it? Most of the time it is not the drive that is the issue.
February 10, 20242 yr Author running check on disk 13 without -n results in Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... 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.
February 10, 20242 yr Author results 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... clearing needsrepair flag and regenerating metadata - 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:259292) is ahead of log (1:2). Format log to cycle 4. done should i try to restart the array now?
February 10, 20242 yr Community Expert 22 minutes ago, ApriliaEdd said: should i try to restart the array now? You need to restart the array in normal mode to see if the disk now mounts OK and looks like it has all its data intact.
February 10, 20242 yr Author it appears to be back online. data seems to be there. was there any indication in the diag file as to what could have caused it? I've been having issues recently with Pbs_storage pool showing as empty and a reboot is required to have it show data again which was why I rebooted this morning. i suspect that this might be to do with my disk shelf but have not confirmed this yet. marking as solved many thanks fellas 👍 you guys rock
February 10, 20242 yr Community Expert Do you have lost+found share now? Repair puts anything it can't figure out in lost+found. Post new diagnostics.
February 10, 20242 yr Author no, there is no Lost + Found share that I can see. new diagnostics attached sag-a-star-diagnostics-20240210-1432.zip
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.