December 23, 20232 yr 1 of 2 parity disks is disabled as is one of the data array disks. happened all of a sudden, not sure why. last action was to rebuild a bad disk just a few days prior. htpc-vault-diagnostics-20231223-1713.zip
December 23, 20232 yr Community Expert Disks were already disabled at array start so we can't see what happened, there's a 1TB disk causing constant errors, I assume that is the missing disabled disk15? Check/replace cables for that disk and post new diags after array start.
December 27, 20232 yr Author Hi JorgeB, Happy Holidays and new year is just around the corner, appreciate the help so far. I've attached the new diagnostics data. The machine was restarted a few times and managed to get a rebuild going but then the server becomes unresponsive after a few hours. Now the array is seeing lots of errors on the disks. Not sure what the cause is, help will be appreciated. htpc-vault-diagnostics-20231227-1534.zip
December 27, 20232 yr Community Expert So far only see this: Dec 27 07:27:24 HTPC-Vault kernel: XFS (md15p1): Unmount and run xfs_repair Check filesystem on disk15, also enable the mirror to flash drive option in the syslog server, and post that if it crashes again.
December 27, 20232 yr Author The file check on disk 15 was this output: Quote 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 ignored because the -n option was used. Expect spurious inconsistencies which may be resolved by first mounting the filesystem to replay the log. - scan filesystem freespace and inode maps... sb_fdblocks 33536868, counted 35246757 - 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 bad CRC for inode 536871079 bad CRC for inode 536871079, would rewrite would have cleared inode 536871079 - 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 bad CRC for inode 536871079, would rewrite would have cleared inode 536871079 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. Not sure what the above means. The drive is powered up and the cage it's in is powered on. syslogs are attached. syslog syslog-previous
December 28, 20232 yr Author disk check done again without the -n, see bwlo: Quote 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 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... done
January 3, 20242 yr Author All fine now, thank you for the help. I'll have to read up more on this and it's the first time using this command. Appreciate the learning experience. Thanks!
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.