JorgeB

Another possibility is that some drives harvested from external enclosures can be slightly smaller.

No it shouldn't, but I also believe the script is not working correctly with latest unRAID, if you want to do that best to do it manually, see here: https://forums.lime-technology.com/topic/61614-shrink-array-question/?tab=comments#comment-606335

Preclear partitions the disk, it's part of the signature for the disk to be considered clear, maybe there's an issue with such a large disk, you can clear the disk in unRAID

You could try re-flashing the controller without a bios, bios is only needed if you need to boot from a device on the HBA.

You're right, I meant the disk status is invalid, not disabled, but without parity the disk can't be emulated, so kind of a bug, but like I said the array is in an unusual state.

OK, I think I understand now, disk3 is invalid (yellow) not emulated (red), array is in an unusual state but as long as data on disk3 looks correct if you start the array as is, without parity, you can do a new config, retain all and start the array, you can later (or now) add a new parity drive, but keep old disk3 intact in case anything goes wrong.

You can use the replace cache procedure and format xfs instead of replace: https://forums.lime-technology.com/topic/46802-faq-for-unraid-v6/?do=findComment&comment=511923

New config will lose any emulated disk, but didn't you un-assign parity? How do you have an emulated disk? You can also post current diags so I can see.

Btrfs filesystem is fully allocated and needs to be rebalanced, see here: https://forums.lime-technology.com/topic/54533-624-cache-drive-reporting-quotno-space-left-on-diskquot/#comment-532931

You can also see the difference form the previous diags:

Yeah, parity drive looks bad, no pending sectors but these are bad signs: 1 Raw_Read_Error_Rate 0x000b 053 053 --- Pre-fail Always - 922755730 22 Helium_Level 0x0023 076 076 --- Pre-fail Always - 76 Raw Read Error rate should be zero on an healthy drive, and it's leaking helium, never seen a helium drive where this value wasn't 100.

Grab and post new diags after the errors.

You should cancel and reboot in safe mode, the start another check, you have syncthing and crashplan running and crashplan is using a lot of CPU.

You could remount the array disks read-only, would still be able to wite to those shares if set to cache "yes", though you'd need to remount read/write before the mover ran.

It looks to be resolved, I've disabled my weekly balance and so far so good, but I'd like to wait a few more weeks before saying it's fixed for sure.

unRAID doens't stripe data disks, so you can never get more than a single disk read/write speed (and write with turbo write only).

Yes

Yes, but if the array is set to auto start and you're using Docker and/or VMs and depending how they are configured it may create duplicate images.

Copy the config folder, redo the flash drive and copy it back.

Redo your flasdrive or try with a new one just to see if it boots.

I never used the script, it may have issues with latest unRAID, you can still do it manually (array will be inaccessible during the clear): 1. If disable enable reconstruct write (aka turbo write): Settings -> Disk Settings -> Tunable (md_write_method) 2. Start array in Maintenance mode. (array will not be accessible during the clearing) 3. Identify which disk you're removing 4. For Unraid <6.12 type in the CLI: dd bs=1M if=/dev/zero of=/dev/mdX status=progress For Unraid 6.12+ type in the CLI: dd bs=1M if=/dev/zero of=/dev/mdXp1 status=progress replace X with the correct disk number 5. Wait, this will take a long time, about 2 to 3 hours per TB. 6. When the command completes, Stop array, go to Tools -> New Config -> Retain current configuration: All -> Apply 7. Go back to Main page, unassign the cleared device. * with dual parity disk order has to be maintained, including empty slot(s) * 8. Click checkbox "Parity is already valid.", and start the array

You should try redoing your flashdrive or use a new one and see if the boot completes.

Boot with the GUI option and check network settings, if still unable to make it work grab the diagnostics from there.

It doesn't need crossflashing, that is only when flashing LSI firmware on other brand controllers, like Dell and IBM, and although it's not very complicated it can be in some hardware, it may need flashing if it comes with IR firmware, from IR to IT mode, but that's very easy, like a bios update.