mycarrysun

Ok sounds good. If it needs rebuilt anyways I may just start now since yea it will probly take 3 days or so... Thanks for looking into this with me!

Ok here you go tower-diagnostics-20250416-1446.zip

Sounds good - the extended smart test is also taking a while. It's saying it's 15% complete.

Ok it is saying the disk is still disabled after a clean reboot and starting the array. I started an extended smart test. Will get the new diagnostics once that's done. Should I also perform a read check? I started one but it looks like it'll take a day or two.

Worried that my disk less than a year old is already toast. Can someone help me figure out if I need to just reset something? Or maybe I should warranty the disk. tower-diagnostics-20250416-1125.zip

Seems like the only way to find out what's going on is to post on the forums based on the help article here tower-diagnostics-20250326-0901.zip

Oof that is a lot of work...but I can do that - do you know the reason that this happens? What does transparent mean exactly? If I can see the data on them after shucking wouldn't that mean they are somewhat transparent?

I've probably gone about this the wrong way it seems. But I can't get my disks to be recognized correctly after shucking them out of the enclosure. I had precleared and did data rebuilds on them after swapping out the old disks, but I did this all via USB. Unfortunately that seems like the wrong move, cause the serial number changes and the drive is not recognized when you connect it via the SATA ports... Anyways, I've not done anything up to this point except for `Tools > New Config` a few times to try different orders of drives. This is what it looks like before starting up (sdf, sdb, sdc, and sdd are the new drives - I verified via the Power On Hours that sdd is indeed the parity drive, but all the other drives sdb/sdc/sdf are data drives and not sure which order they go in, if that matters). After starting up it looks like this: Also I've looked in the terminal and can see that the data is intact on the drives, they each have data, and the folders are identical to my shares. So i'm confused why the partition would not be valid (at least according to unraid). Any help would be appreciated! I am at the limit of my knowledge here... tower-diagnostics-20241101-2144.zip

Welp...I lost all my docker networks when I tried deleting the docker img file and then recreating...hope no one else had to go through and manually setup all their docker containers again like me. I'd rather just do the original shrink method. Wish it was done in the Web GUI when you change the docker vdisk size option.