July 16, 20241 yr Good evening, I caused some damage while changing a disk. Today, since I was running out of space in my array, I removed disk 2 (HGST_HUH721010ALE600_1DGJ8K7Z) which was 10TB and replaced it with a new disk (ST20000NM007D-3DJ103_ZVT9W704) which is 20TB. To do this, I stopped the array, physically removed the 10TB disk, and inserted the 20TB disk. Once Unraid detected it, I selected the new 20TB disk in the dropdown menu to replace disk 2 and started the array. The data reconstruction began immediately, but after a few hours, I noticed that no shares were available anymore. If I check /mnt/disk1 and /mnt/disk2, they don't exist and it only shows the parent directory and it seems to be read only. I stopped everything, and if I try to restart it, I get errors on disk 1 (a disk that shouldn't have any errors since it passed the parity check a few days ago). I still have the original 10TB disk 2 with all the data but now it want the 20tb. What can I do? w/o the disk seems to be all working and all data there, but I'm afraid that when it found errors on disk 1, it might have corrected and corrupted the files. Disk 1 and Disk 2 when the Data-Rebuild is in progress. Disk 3 seems to be intact. help <3 quiethub-diagnostics-20240716-1727.zip
July 16, 20241 yr Author 1 minute ago, JorgeB said: Check filesystem for the emulated disk2, run it without -n 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.
July 16, 20241 yr Community Expert Restart the array to see if it mounts, since it did before, if now it doesn't, use -L
July 16, 20241 yr Author 3 minutes ago, JorgeB said: Restart the array to see if it mounts, since it did before, if now it doesn't, use -L I need to start the array with the new 20TB disk or with the emulated? Edited July 16, 20241 yr by Vash
July 16, 20241 yr Author Ok, the array mounts, also the shares are there and if i explore the disk are all ok
July 16, 20241 yr Community Expert Post new diags, 1st screenshot shows no writes going on for disk2, suggesting something is wrong.
July 16, 20241 yr Community Expert Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1051944 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1051952 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1051960 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1051968 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1051976 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1051984 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1051992 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1052000 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1052008 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1052016 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1052024 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1052032 It's not logged as a disk problem, so replace cables, both power and SATA and try again.
July 16, 20241 yr Author 15 minutes ago, JorgeB said: Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1051944 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1051952 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1051960 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1051968 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1051976 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1051984 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1051992 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1052000 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1052008 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1052016 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1052024 Jul 16 17:32:47 QuietHub kernel: md: disk1 read error, sector=1052032 It's not logged as a disk problem, so replace cables, both power and SATA and try again. Tried, swap all cables. Same problem, But only when rebuild, If the disk is emulated there seems to be no problem (I see all data in disk1 and 2. I don't know if the data is intact in disk 1 at this point because when the rebuild finds errors does it correct them immediately?
July 17, 20241 yr Community Expert 13 hours ago, Vash said: But only when rebuild, If the disk is emulated there seems to be no problem The problem happens when disk1 drops, since single parity cannot emulate two disks, so both will become inaccessible, if swapping cables didn't help, and make sure you swapped both cables, disk1 may be failing, and in that case not many options.
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.