Linkex

Done, and it looks like my array is doing a data rebuild, so I do believe I'm now sorted. Thank you very much for that Would I be right in thinking that this happened because I added disks with existing partition tables to the array? Is there something I could/should have done with the disks before adding them to the array that would prevent this?

I've just spotted, next to the start button it does say 'Start will start Parity-Sync and/or Data-Rebuild', so I'm quietly hoping that means it will rebuild disk 4 if I start the array. However, I will indeed wait for JorgeB to update before I touch anything, just in case there is a better/safer option

Thanks both for taking the time. I ran 'sgdisk -o -n 1:1M:0 /dev/sdX' on the disks, one is now showing green, but the other is still showing 'wrong'. It does now give me the option to start the array, but seems to suggest the disk will be overwritten if I do. Is there any way I can proceed without data loss? unraid-diagnostics-20240105-1323.zip

I did reassign the old parity disk as a data disk, although I couldn't say for sure which slot it ended up in - I didn't realise it was something that should be tracked Is there any way I can manually check which disk has parity data on it, as that would confirm if the disk currently in the parity slot is the actual parity disk? 'ls boot' gave an error, did you mean /boot? root@Unraid:~# ls boot /bin/ls: cannot access 'boot': No such file or directory root@Unraid:~# ls /boot EFI/ bzimage bzroot changes.txt license.txt make_bootable_mac syslinux.cfg- System\ Volume\ Information/ bzimage.sha256 bzroot-gui config/ logs/ memtest bzfirmware bzmodules bzroot-gui.sha256 ldlinux.c32 make_bootable.bat previous/ bzfirmware.sha256 bzmodules.sha256 bzroot.sha256 ldlinux.sys make_bootable_linux syslinux/

Array has recently had new (re-used) disks installed, these had been built into the array and working for at least a couple of weeks. I do think this was the first reboot since then however. In any case, rebooted the device and array won't start with error 'Too many wrong and/or missing disks!'. 2 disks are showing as wrong, however one of the 'new' discs replaced the parity device as it was larger, and that is showing green, so I don't THINK its just the new discs. showing as down From what I've read, it looks like the best option is to create a new config, but I'm not clear on if that will impact existing data or not? Are there any other options I should be looking at? unraid-diagnostics-20240104-2108.zip