Bought new drive, WD red plus 10tb.
Added to server, pre-cleared with unassigned devices.
Stop array, (tried to at least)
restart server, new disk added to array. Tick the box to format unmountable disk - click format,, status showing Formating device(s) for a few seconds, and then the Array is back to showing a disk that is not formated



PS: Was not able to stop array when going to shut down to install new nvme,, can the pause of parity-check after restart be the issue?
Know I did not have to restart,,, but wanting to ad an extra nvme and a m2-coral and adjust some fan-settings in bios,, so wanted to get that done when i had the oportunity
Awaiting some qualified advice before starting parity-check,, in case there is somehting else I should rather do before that,,,

unraid1-diagnostics-20230726-1847.zip

I did not follow this to the letter,,  https://docs.unraid.net/unraid-os/manual/storage-management#data-disks
given that I added the drive and did a preclear first,, but should it not be OK to do 1 - 5 - 6 - 8 - 9 - 10 ?
I am able to click format, and the disk shows for a few seconds as "Formating"
 

 

then it is back to the status of "unmontable,,,, " after a few seconds,,

Your system's diagnostics zip file taken after a failed format attempt might give a clue.

55 minutes ago, itimpi said:

Your system's diagnostics zip file taken after a failed format attempt might give a clue.

just tried once more,, was a bit longer standing with "formating" - but got back to the "unmountable"
 

unraid1-diagnostics-20230726-2018.zip

How is the disk in question connected?   In the diagnostics I see:

Jul 26 19:03:07 unraid1 kernel: sd 2:0:3:0: attempting task abort!scmd(0x000000002f39e8d5), outstanding for 7339 ms & timeout 7000 ms
Jul 26 19:03:07 unraid1 kernel: sd 2:0:3:0: [sdh] tag#1801 CDB: opcode=0x85 85 06 20 00 d8 00 00 00 00 00 4f 00 c2 00 b0 00
Jul 26 19:03:07 unraid1 kernel: scsi target2:0:3: handle(0x000c), sas_address(0x4433221105000000), phy(5)
Jul 26 19:03:07 unraid1 kernel: scsi target2:0:3: enclosure logical id(0x500605b004e9ec1f), slot(6) 
Jul 26 19:03:07 unraid1 kernel: sd 2:0:3:0: task abort: SUCCESS scmd(0x000000002f39e8d5)

which suggests some sort of connection issue.

5 minutes ago, itimpi said:

How is the disk in question connected?

It's connected through the LSI-HBA.
The HBA has two cables to two four-bay hotswap in the 4408-case,,, and the new drive is the first one on the upper bay,, 
- but it has run just fine for two days for the pre-clear??  
Anyway,, will shut down and try re-attach the cables,,  - will report back when done

Thanks for the assistance so far 

That made the trick,,  Shut-down, re-attached cables, even moved the disk new to second row (mostly for improved airflow), startup and format is completed on first try !
- thanks a lot for the assistance and guidance !

Now I see a second issue,, my old crappy spin-drive for Frigate-recording is having a hickup again.  

it seems to be mounted,, but there are no indication of size (last time I checked there was about 12gb of snapshot/video on it)

 

I've previously seen issues where the dropping of of the usb-attached Local_dr messes with the (sdi)-references,, so I've found them in console using 

 

 

then I've unmounted and was able to mount again,,,

But now it seems like it is not mounted and just not available to mount?

 

 

unraid1-diagnostics-20230727-0000.zip

first issue solved by de-attaching and re-attaching cables,,

Second issue fixed by assigning drive to a dedicated pool for Frigate,,