July 6, 20241 yr i recently had an emulated failing drive error. swapped out the drive (disk 9) with a larger new hdd. when adding disk9 back in the ID had changed on disk8. the system wanted me to do a rebuild on both drives, which i did. now all my drive IDs have changed including both my parity drives. in addition, both disk8 and disk9 keep saying unmountable or unsupported file system. i havent formatted anything, etc. so i'm hoping all my data is still intact and just need to re-arrange things back. before swapping the the bad drive out i had added two new controllers to an empty riser card i had in my pci express slot for my array, but the IDs were fine at this point so i proceeded to swap the bad drive out. in addition, i noticed one of my 400w psu had failed on the disc array, i'm currently waiting for a replacement as i'm not sure if this is the real issue or caused the issue or both. i have attached a before ID screenshot along with an after ID screenshot of the hdds in the array. is there a way to put the array back to the old ID system. i'm afraid to do anything because i dont want to lose data. i have also attached current diagnostics.blacksheep2-diagnostics-20240705-2035.zip
July 6, 20241 yr Author was checking out the wiki and ran the following command with following output if this helps. xfs_repair -v /dev/sdn1 Phase 1 - find and verify superblock... - block cache size set to 6080528 entries sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 Phase 2 - using internal log - zero log... zero_log: head block 553400 tail block 553396 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.
July 6, 20241 yr Author Solution in case anyone else has similar situations. i used the wiki. https://docs.unraid.net/unraid-os/manual/storage-management/#drive-shows-as-unmountable i decided to use the command line to check the drives. it spit the above post error out. i stopped the array in the maintenance mode and then started the array up normally and noth disk8 and disk9 are now mounted and showing all the data.
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.