October 24, 20232 yr Diagnostics included Hello, In the last 2 weeks I have had Unmountable disks present: Disk 23 • ST6000VN001-2BB186_ZR14744R (sdad) Disk 24 • ST6000VN001-2BB186_ZR144E4P (sdah) crash I was able to rebuild them and it happened again. This also happened to me about 4-6 months ago and I was unable to correct this issue and purchased 4 brand new 6tb disks and started me bunch of my collection over. is there anyway someone can look at this and maybe give me an idea of what is going on. towerofterror-diagnostics-20231023-2122.zip
October 24, 20232 yr Community Expert Disks were already disabled at boot, do you have previous diags from when they got disabled?
October 24, 20232 yr Author no I don't this is all i have. after the rebuild they are still saying unmoutable. I am guessing I have lost all 12 TB's
October 25, 20232 yr Community Expert Solution Unmountable and disabled are two different things, check filesystem on the unmountable disks, run it without -n.
October 26, 20232 yr Author The cause of the issues was a failing power supply on those six drives. I powered down the server, replaced the power supply, powered the server back up and could see all six drives, 2 were still unmoutable after starting the server. stopped the server, removed the drives from the server hoping to emulate and still said unmoutable after starting it back up. Zeroed the 2 drives, stopped the server and have added them back as new drives. they are currently rebuilding but still say unmoutable so I will try your recommendations in 24-48 hours when those drive are done rebuilding.
October 26, 20232 yr Community Expert Filesystem should be checked before rebuilding, no point in rebuilding if it can't be fixed.
October 28, 20232 yr Author hello, I ran the check in maintenance mode without -n this is what I got 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... writing modified primary superblock 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.
October 28, 20232 yr Author i fired up the server after running the check and now everything is running and there. thank you again unraid community for soling my issues.
October 28, 20232 yr Community Expert 5 hours ago, Soulflyzz said: I ran the check in maintenance mode without -n this is what I got When this happens use -L.
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.