May 10, 20242 yr Hello, I had a drive that looking like it was failing so shut down my server and replaced it. When I booted back up, I started a pre-clear on the new disk, but needed access to the array for a small amount of time so started the array with the replaced disk missing and emulated. While the array was starting I started to see errors like the followng in my system log "kernel: ata5: COMRESET failed (errno=-16) unraid" when the array started none of the shares were listed so I stopped the array and rebooted. When the system came back up the array started automativally with the missing disk still missing but it was not being emulated. I did not see any errors in the log upon reboot, but I immediately shut down the array since not all looked right. Have I now lost everything that was on the original disk, or when I add the new pre-cleared disk to the array will it be recovered from parity? Is there any steps I should take to make the data from the failing disk recoverable from parity? citizenur-diagnostics-20240509-2117.zip Edited May 17, 20242 yr by citizen_y
May 10, 20242 yr Author Of note - I did just find a diagnostic I pulled about a week ago which should have the full config in it. Prior to today, none of my disk assignments have changed for months. Is it possible for me to use the config backup from the diagnostic a week ago, to restore my array configuration information and rebuild from parity? If so, what steps would I follow to do so?
May 10, 20242 yr Author 3 hours ago, JorgeB said: Check filesystem on disk1, run without -n. Hey, thanks for replying. Right now I don't have any disk assigned as disk 1 (that was the disk that was failing). I have a disk currently in preclear that I intend to assign as disk 1 and rebuild from parity once preclear is completed. The array is currently stopped. Given that current situation, is it viable for me to run a check file system on disk 1? If so, is it the right step for me to bring the array online in maintenance mode with the disk 1 assignment empty and attempt to run a check filesystem on an emulated disk 1? I just want to make sure I'm clear on the steps to take so I can avoid losing the data if possible.
May 10, 20242 yr Community Expert 11 minutes ago, citizen_y said: Right now I don't have any disk assigned as disk 1 You run it on the emulated disk.
May 11, 20242 yr Author 13 hours ago, JorgeB said: You run it on the emulated disk. Thanks for this - when I went to run without the "-n" option I got the following error. Recommendations on how to proceed? Quote Phase 1 - find and verify 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.
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.