Hi all, I tried following what that post solved but it was unsuccessful, it still show as unmountable. I'm lost here, I don't know what to do.

Edited December 24, 20241 yr by dunnno
probleme solved :)

here is the diag, I've an emulated device as well, dunno why.

tower-diagnostics-20241223-2245.zip

Which filesystem was the pool using? Also post the output from

 

blkid

 

Hi, it's using XFS, I chose it for it to be the same as every other disks.

 

blkid:

/dev/sdb1: UUID="d750a070-5ce9-4bb0-b24e-053dbe713ac7" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="a512dafd-ed4b-48d8-aebd-f390245eec53"
/dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="310F-19E0" BLOCK_SIZE="512" TYPE="vfat"
/dev/loop1: TYPE="squashfs"
/dev/sdf1: UUID="fb012c0b-202a-489a-b5b0-c452bbcb76e3" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="59b3f132-5f43-4eb5-9369-c89877bc243b"
/dev/sdd1: UUID="57f793ec-c3d9-4c87-8c6a-3e56c7119913" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="6010d587-c548-47e6-8db1-9407a8c5035f"
/dev/sdg1: PARTUUID="eb5247a1-ecbe-4d5b-a2a5-c45ff8f8a533"
/dev/loop0: TYPE="squashfs"
/dev/sde1: UUID="e095ab19-780e-46b0-9e6b-e68c526f6fe2" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="dabef6fe-6fe9-4314-bc1b-d46d203023d7"
/dev/sdc1: UUID="a79678e3-18be-4874-be36-22dc2ef19e46" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="3a7ca85f-1a5a-4b81-90d3-d0533ff17cf1"
/dev/nvme1n1p1: UUID="de8d3c83-75e7-47a0-91c2-8f749577fd42" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="94f82380-01"
/dev/sdh1: UUID="ef88f827-4745-4fb7-9582-53e66ef18aac" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="baaccf17-fefd-4e2a-8340-3497468dcd04"

 

XFS doesn't support multiple devices, set the pool to one slot.

Ok then, I bought a second ssd to get 2 for the cache. I was at a thousand kms to know that XFS does not support multiple devices, only a pro like you can tell me, and really, really thank you for that. I was painfully, excruciatingly ready to press the format button in order to make it work again  . I have all my appdata and cached files which hadn't moved yet and docker.img on that drive. The appdata backup and the mover were due to run the day after, so I was about to lose a week of data (·•᷄‎ࡇ•᷅ )

 

So, what do you advise, set everything that is "Cache-ssd ==> Array" to "Array" and when it's done, add the second SSD cache drive and format them all ?

 

 

EDIT: Ok sorry for the bother with what follows, saw ppl had the same problem, made a dummy change on each guilty shares, and the warnings are gone.

 

Also, now the SSD is back online, some shares (many) that were Storage : "Array" now show : 

This share is invalid; It references storage that does not exist

 

How to get them back correctly ? is it because of the emulated disk ?

Edited December 24, 20241 yr by dunnno
typo

You can use this procedure:

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/#findComment-511923