June 3, 20242 yr hello, i randomly got this message "disk in error state" and now unraid is not letting me select the drive for my array even tho the drive seems to be working fine; i even did a SMART test on unraid itself and nothing bad was reported, so what could be the issue? i even rechecked all my drive sata connections and they seem fine. in this diagnostic i restarted pc and booted without selecting the hard drive unraid-diagnostics-20240603-2304.zip Edited June 3, 20242 yr by giovacca
June 3, 20242 yr Author what i did for now that seemed to work: start unraid without selecting the disk stop unraid start unraid with selecting the disk and now a data rebuild is started, but what can i do to avoid this in the future? because data rebuilding is gonna take a whole day. do the diagnostic say something about this issue? thanks Edited June 3, 20242 yr by giovacca
June 4, 20242 yr 10 hours ago, giovacca said: but what can i do to avoid this in the future? The way to avoid is trying to figure out why the disk got disabled in the first place, because after that, rebuild is the best option. Diags you posted are after a reboot, so we cant see what happened, post new ones if it happens again, before rebooting.
June 5, 20242 yr Author Solution On 6/4/2024 at 9:28 AM, JorgeB said: The way to avoid is trying to figure out why the disk got disabled in the first place, because after that, rebuild is the best option. Diags you posted are after a reboot, so we cant see what happened, post new ones if it happens again, before rebooting. hi, i need help. the data rebuilding just finished but the disk is showing "Unmountable: Unsupported or no file system" what could be the issue? it seems like it's forcing me to do a format, but i have some data on it which i dont want to lose tried doing a xfs_repair but the status says: Quote Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now. after removing -n now it says Quote Phase 1 - find and verify superblock... 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... 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. added -L and now my disk back to normal operations! thanks for the help diagnostics-20240605-2055.zip Edited June 5, 20242 yr by giovacca
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.