April 3, 20251 yr been struggling the last few days troubleshooting random crashes. with all the power cycles and troubleshooting i guess at some point i started the array without disk4 in it. so the next time i included it in the array and started it would try to rebuild the disk, but before that could happen the server would crash. i eventually moved the disks and flash over to other set of hardware and was able to complete the rebuild there, but now showing the disk as Unmountable: wrong or no file system. if i do format this disk will it rebuild from parity still after, or is the data on it lost now?
April 3, 20251 yr Community Expert Solution DO NOT FORMAT any disk that has data on it you want to keep. Format is a write operation. It writes an empty filesystem to the disk. This is basically the definition of "format" in any OS. All write operations in the array updates parity at the same time so parity will be in sync. So, after formatting a drive in the array, parity agrees it has an empty filesytem on it, and trying to rebuild at that point can only result in an empty filesytem. Typically, we try to repair unmountable before rebuilding on top of the same disk.That gives more options for recovering data. We will have to check filesystem on the unmountable disk. Attach Diagnostics ZIP to your NEXT post in this thread.
April 3, 20251 yr Author Thank you. Here's the output from that. the result states "File system corruption detected." with the button reading "Fix" now. i want to click it but going to make sure i ask so i dont lose anything. diagnostics below. 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 251623534, counted 239557133 - 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 Bad mtime nsec 2111207260 on inode 128, would reset to zero - 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 Bad mtime nsec 2111207260 on inode 128, would reset to zero - 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. server-diagnostics-20250403-1817.zip
April 3, 20251 yr Community Expert Yes, fix Then start the array in normal (not maintenance) mode and post new diagnostics.
April 3, 20251 yr Author back in business, baby! thanks you guys are great. disk mounts and im able to browse content. server-diagnostics-20250403-1828.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.