darber

disk 1 shows up as a new device now is that ok?

The disk seems to be making a "dink" noise which doesnt sound good. I currently have disk one set as not installed as I was going to RMA that drive (it is the newest one I have bought) but usually when doing this my array just uses the parity disk and continues but I currently have a lot of data missing this time.

I had a drive fail recently and I seem to have lost data even though my parity disk is ok? I hope someone can help. Thanks, tower-diagnostics-20231204-1546.zip

I have disabled Docker and VMs, set all shares to cache:yes and then run data mover but still have app data and system folders on cache? tower-diagnostics-20230309-1758.zip

Array is rebuilt and I have restarted the server but still the same issue with Docker. tower-diagnostics-20230228-1857.zip

Hi JorgeB, You helped me earlier with my array. Its still rebuilding, ill let it finish and then reboot. It has an estimated 1 hour left. Thanks,

Im seeing the error when selecting the docker tab. I have seen you can delete the docker.img file and reinstall the containers but I just wanted to check here before I did that. I have looked and the image doesnt appear to be full, not sure what else to look at. Thanks for your help. tower-diagnostics-20230228-1723.zip

Thanks for all your help, disk1 is mounted and rebuild is running at a good speed now. Shares and data are back, docker tab says Docker Service failed to start but it was sying that before this, ill sort that issue next! Thanks again.

ok done disk1xfsrepair.txt

It says this, does this mean I should run again with -L ? Phase 1 - find and verify superblock... - block cache size set to 744800 entries Phase 2 - using internal log - zero log... zero_log: head block 1001598 tail block 1001594 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.

Here is the filesystem check result disk1fscheck.txt

Here are new diagnostics, im not sure if im in a better or worse position now. No errors on parity but disk 1 Unmountable and all my shares containers and data seem to be missing. The data rebuild still wants to start should I let it finish? tower-diagnostics-20230228-0920.zip

No I didnt

I shut down the server and checked all the connections to the drives. Booted the server and started the array. The parity disk isnt logging errors any more but disk 1 is showing Unmountable: Wrong or no file system. The rebuild starts and seems to be rebuilding back to disk 1 even though it is unmountable? also I have no shares and no docker containers, am I screwed? Ill download and attach more diagnostics.

Version 6.11.5 2022-11-20 Im quite new to unraid. I had a disk fail in my array, bought another one and replaced it but its rebuiling the array at 1MB/sec. Ive also noticed the number of errors on the parity disk increasing although SMART error log shows no errors. Im not sure what to do. tower-diagnostics-20230227-1151.zip