June 13, 20242 yr Hello everyone. I restarted my server and noticed DISK 2 was unmountable. I followed THIS guide and got to the point of running the test. I got the below 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 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 181403022, counted 182383607 - 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 = 3 - agno = 2 - agno = 1 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. I am a little worried that something bad has happened to the disk, but I have two parity drives so my data should be safe. Should I follow the guide and conduct a repair? Edited June 13, 20242 yr by PrisonMike
June 13, 20242 yr Community Expert That error is not usually a filesystem problem, post the diagnostics.
June 19, 20242 yr Author JorgeB, hello and thanks for your assistance. I have attached my diagnostic zip file to this post. tower-diagnostics-20240619-1116.zip
July 11, 20241 yr Author On 6/19/2024 at 12:02 PM, JorgeB said: Diags after array start please, or it won't show the error. My apologies, I didn't realize that I had to do them after the array started. I have attached the new diagnostics for your review. Thanks again in advance. tower-diagnostics-20240711-0757.zip Edited July 11, 20241 yr by PrisonMike sp
July 11, 20241 yr Community Expert Assuming disk2 is still sdb, post the output of: blkid /dev/sdb and fdisk -l /dev/sdb
July 11, 20241 yr Author 1 hour ago, JorgeB said: Assuming disk2 is still sdb, post the output of: blkid /dev/sdb and fdisk -l /dev/sdb Hello, it is still sdb. Please see the outputs below /dev/sdb: PTUUID="1616b127-e5f5-4f58-a5ac-0ee54460088b" PTTYPE="gpt" and The primary GPT table is corrupt, but the backup appears OK, so that will be used. Disk /dev/sdb: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors Disk model: WDC WD40EFRX-68N Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 1616B127-E5F5-4F58-A5AC-0EE54460088B Device Start End Sectors Size Type /dev/sdb1 64 7814037134 7814037071 3.6T Linux filesystem Thanks again
July 11, 20241 yr Community Expert 24 minutes ago, PrisonMike said: The primary GPT table is corrupt This is likely the problem, with the array stopped type gdisk /dev/sdb And post the results
July 12, 20241 yr Author 19 hours ago, JorgeB said: This is likely the problem, with the array stopped type gdisk /dev/sdb And post the results Hello, here is the result: root@Tower:~# gdisk /dev/sdb GPT fdisk (gdisk) version 1.0.9.1 Caution: invalid main GPT header, but valid backup; regenerating main header from backup! Warning: Invalid CRC on main header data; loaded backup partition table. Warning! One or more CRCs don't match. You should repair the disk! Main header: ERROR Backup header: OK Main partition table: OK Backup partition table: OK Partition table scan: MBR: protective BSD: not present APM: not present GPT: damaged **************************************************************************** Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk verification and recovery are STRONGLY recommended. **************************************************************************** Command (? for help): Should I repair the GPT table? How is this conducted. Thanks!
July 13, 20241 yr Author On 7/12/2024 at 6:32 AM, JorgeB said: Try repairing it, type w then Y Thanks so much for your assistance! This worked after I restarted, everything appears to be working normal now!
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.