Hello,

 

I am wondering if someone can take a look at my diagnostics.

 

What happened is that I followed the parity swap procedure and removed an old 4TB drive, which hadn't failed but was starting to get errors. I replaced the drive with a 16TB HDD, which is bigger than my 12TB parity. So I had to do the parity swap (removed disk 3, moved parity to disk 3, and assigned the new drive to parity).

 

I then started the copy procedure and waited 22 hours. When it completed, I am not sure why, but I think the "new" parity drive had a red X next to it, and next to the "Start array" button was a checkbox to start the copy again (I rushed this part; I should have read and tried to figure out what happened).

 

I checked the syslog, which says "Disk 3 copy to disk 0 complete."

 

I have restarted the process, and it is at 32%.

 

I have attached my diagnostics; I am hoping someone can tell me if it failed due to errors on the new disk or something else (I didn't pre-clear it; not smart, I know).

tower-diagnostics-20250322-2324.zip

Quote

(removed disk 3, moved parity to disk 3, and assigned the new drive to parity).

you have confused me here...
 

 

 

Some one more experienced may need to better assist.

as it sounds like you moved a disk 1(as disk 3) into parity and may have lost data.

Mar 22 14:19:17 Tower emhttpd: copy: disk3 to disk0 completed

 

First copy completed, but then disk7 was missing:

 

Mar 22 14:27:40 Tower kernel: mdcmd (8): import 7
Mar 22 14:27:40 Tower kernel: md: import_slot: 7 missing

 

Unclear why, though, since it didn't drop offline, see some wrong csrf token errors logged due to the UD plugin, but don't think that should have interfered.