ThWiecz

> all of your configuration is in config on flash so make sure you always have a current backup Thanks. I know that. Taking a backup daily. > Is disk1 connected USB? USB not recommended for array or pools for many reasons, but shouldn't be the cause of this problem. Also do know that Besides the disk size, the USB connection was another reason to replace the disks. I just started testing with Unraid using available USB disks. When I started loving Unraid, I bought 3 SATA disk and started migrating. Not, because I don't have the data elsewhere. But to learn, how that works. Being prepared for the desaster. The Migration of the parity disk worked like a charm. > Did you make any change to the way disk2 was connected? Not at all. As described: I removed the other USB data disk. Then I started the array in maintenance to make Unraid recognizing it. As the next step, I connected the SATA disk. Unraid accepted the new disk and recogized the bigger size. I confirmed the rebuild and let it run. After it finished successful, I stopped the array to remove the remaining USB disk and finally add the 3rd SATA, then do the last rebuild. But when I stopped the array after the successful rebuild, the disk 2 slot suddenly showed as unassigned. And assigning the disk that just was rebuilt ended in "wrong disk". As a list, so it is more visible: shut down array remove 2TB USB disk start array in maintenance stop array add SATA disk start array for rebuilding rebuild successful stop array for another disk switch surprise: newly rebuild disk got unassigned and wasn't accepted when assigning rebooted to see, if it's kind of a cache issue... problem stayed started rebuilding again PS: now made my Raspberry the syslog-server for the Unraid. If it happens again, I hopefully have the sequence in the logs

Thanks a lot... that was, what I was searching for while you replied It's part of my job to open a lot of tickets each day and I know: the more info, the better Diagnostics attached. diagnostics-20231216-2355.zip

Hey guys, I just replaced a data disk in my array (4GB parity, 2 x 2GB data) by a bigger one (4GB). Everything seemed fine, Unraid detected a new, bigger disk (told me something that it'll resize) and did the rebuild. After 12h it was done. Also confirmed via email: Event: Unraid Disk 2 message Subject: Notice [MINIS] - Disk 2 returned to normal operation Description: ST4000VN006-3CW104_ZW61HYCG (sde) Importance: normal Event: Unraid Data-Rebuild Subject: Notice [MINIS] - Data-Rebuild finished (0 errors) Description: Duration: 11 hours, 8 minutes, 27 seconds. Average speed: 99.8 MB/s Importance: normal As the next step, I shut down the array to replace the Disk 1 as well by a new 4GB Disk. After the array shutdown was done, I was quite surprised, when the webGUI refreshed: Slot Disk 2 showed up as unassigned. I thought "well, just open the drop-down, add the newly rebuilt disk". But: When I chose it, Unraid told me: "Wrong Disk" and warned me, that the disk will be emptied, when I start the array. For now, I just did it and Unraid is doing the same rebuild again. But this is annoying, as now, I do not trust that the system is in a good shape in 12h. At the end, I am doing the same that I did 12h ago: letting Unraid rebuild the removed disk to the new one using the (healthy) parity. So... does anybody have an idea, what went wrong here? Thanks in advance! P.S.: Log is attached P.S.2: pls ignore the syslog errors... I had the goofy idea to use a docker within Unraid as syslog server for Unraid itself... cannot work for sure Sorry, it was late, when I had this idea... syslog-20231216-2226.zip