inkindar

I have dual parity. Your question made me poke around & find auto-start got disabled at some point. Things are fine now & the empty slots are now easily ignored.

My BIOS & clock battery died. Unraid booted to the default name "Tower" after I replaced it. Why is this? My understanding is this is on the boot USB, unaffected. ChatGPT says this isn't the case & hostname lives in the BIOS?

After consolidating disks while preserving parity, my array has 2 empty slots. This necessitates manual array starts, which I don't like. Can I remove these slots w/o parity changes?

Thanks for the assurances. The warnings indeed didn't apply. For the record, I indeed have 2 parity disks. I'm also locked in to one iteration per disk by my experimentation, so I can't comment on the outcome of zeroing all disks before a config, but I imagine it would have worked out.

On reflection, I suspect I did not toggle on retaining the array configuration. Does this change things? I do have a spreadsheet of my assignments.

I am in the middle of shrinking my array while preserving parity according to these instructions. I have zeroed the 1st data disk. I have 2 questions about next steps. [1] I presume I could zero the 2nd data disk & then do a new config, or must I go through the whole process once per disk? [2] If I were to start the array sans zeroed disk, with parity preserved checked, I'm still warned about writes to parity. Is this expected behavior on v6.12.13?

I should've clarified: quickest way with parity preserved? As I understand, the above wouldn't.

So it would seem the quickest way is to format these disks to be removed & then reconfig the array with valid parity?

I'm trying to shrink my array while preserving parity on v6.12.13. Per the wiki, I need to rm -rf /mnt/disk1/ mkdir /mnt/disk1/clear-me but I experience root@Tower:~# du -h /mnt/disk1/ 1.0K /mnt/disk1/root 1.0K /mnt/disk1/.Trash-99 2.5K /mnt/disk1/ root@Tower:~# du -h /mnt/disk2/ 1.0K /mnt/disk2/root 1.5K /mnt/disk2/ root@Tower:/# rm -rf /mnt/disk1/ rm: cannot remove '/mnt/disk1/root': Device or resource busy rm: cannot remove '/mnt/disk1/.Trash-99': Device or resource busy root@Tower:/# rm -rf /mnt/disk2/ rm: cannot remove '/mnt/disk2/root': Device or resource busy despite no processes root@Tower:~# lsof | grep /mnt/disk1 root@Tower:~# lsof | grep /mnt/disk2 root@Tower:~# pwd /root root is my share, which only inlcudes a different disk I copied to. I don't exlcude these disks, per the guide. Nonetheless, this is because the array is not stopped. root@Tower:/# fuser -mv /mnt/disk1 USER PID ACCESS COMMAND /mnt/disk1: root kernel mount /mnt/disk1 root@Tower:/# fuser -mv /mnt/disk2 USER PID ACCESS COMMAND /mnt/disk2: root kernel mount /mnt/disk2 So, I need to unmount the disks to fully clear them. Would this invalidate parity? I'm also trying to avoid the tedium of formatting disks.