I shut down my server abd added an SSD. I started the server and created a second pool (cache_ssd) and assigned the ssd to it. I started the array and the original cache pool (dual nvme 1Gb drives in a raid 1 btrfs config) now show "Unmountable: Unsupported or no file system". I stopped the array and removed the cache_ssd pool, then restarted the array. The original cache pool still shows the same Unmountable error.

 

I have attached diagnostics before array restart (1430) and after (1439).

mongo-diagnostics-20240415-1430.zip mongo-diagnostics-20240415-1439.zip

I ran short SMART diagnostics on both drives from the cache pool and have attached them here.

mongo-smart-20240415-1527.zip mongo-smart-20240415-1522.zip

Post the output of

btrfs fi show

 

root@Mongo:~# btrfs fi show
warning, device 1 is missing
Label: none  uuid: d0989cc1-462a-4a25-ac4c-b3fbb1d27a4c
        Total devices 2 FS bytes used 95.33GiB
        devid    3 size 931.51GiB used 100.03GiB path /dev/nvme0n1p1
        *** Some devices missing

 

BTW- the array is still stopped.

Edited April 16, 20242 yr by hfuhruhurr

Looks like all 3 devices have the same btrfs UUID, that should never happen unless they were used together in the past:

 

Apr 15 14:33:08 Mongo emhttpd: Label: none  uuid: d0989cc1-462a-4a25-ac4c-b3fbb1d27a4c
Apr 15 14:33:08 Mongo emhttpd: #011Total devices 2 FS bytes used 95.33GiB
Apr 15 14:33:08 Mongo emhttpd: #011devid    1 size 931.51GiB used 100.03GiB path /dev/nvme1n1p1
Apr 15 14:33:08 Mongo emhttpd: #011devid    2 size 931.51GiB used 82.03GiB path /dev/sdi1
Apr 15 14:33:08 Mongo emhttpd: #011devid    3 size 931.51GiB used 100.03GiB path /dev/nvme0n1p1

 

Physically disconnect /dev/sdi and post new output of

btrfs fi show

 

Shutdown server and disconnected /dev/sdi. Restarted server and ran below command with array stopped.

 

root@Mongo:~# btrfs fi show
warning, device 1 is missing
Label: none  uuid: d0989cc1-462a-4a25-ac4c-b3fbb1d27a4c
        Total devices 2 FS bytes used 95.33GiB
        devid    3 size 931.51GiB used 100.03GiB path /dev/nvme0n1p1
        *** Some devices missing

That device it from the old pool correct? If yes, the other one was wiped, was the pool redundant?

The /dev/sdi device was just added as a separate pool named cache_ssd. It was never part of the main cache pool. Originally only had one pool with 2 devices in raid 1.

Edited April 16, 20242 yr by hfuhruhurr

There's still something strange going on there, leave sdi disconnect for now, unassign both nvme devices, start array, stop array, re-assign only /dev/nvme0n1p1 to the old pool, start array, post new diags

Ok, sdi is still disconnected. I unassign both nvme devices, started array, stopped array, then re-assigned only /dev/nvme0n1p1 to the old pool (in it's original slot 2 of the pool), started array, and it started with no errors. New diags attached.

mongo-diagnostics-20240416-0835.zip

Edited April 16, 20242 yr by hfuhruhurr

OK, you can now add the other NVMe device, if you want to make the pool redundant again.

After that you can also create a new pool with sdi, but make sure it's wiped first, just in case there's some old filesystem there causing issues, so before adding it to a new pool run:

 

wipefs -a /dev/sdX

 

 

Ok, sounds good. One question, when I add the other nvme device back to the pool, do I need to do anything in pool setup? Right now the pool setup (in slot 1) shows File system type: btrfs single. Would I need to change it to Raid 1? Or will Unraid just handle to change? Also, is there any reason to move /dev/nvme0n1p1 to slot 1 in the pool before adding the second nvme drive?

Just added and start the array, it should automatically create a mirrored pool (raid1).

One more issue. When I add second nvme drive and try to start the array, I get an error:

Wrong Pool State

cache - too many missing/wrong devices

That should not happen when adding a new device, something weird still going on there, try this:

 

Unassign the second nvme device, also wipe it with wipefs -a, set pool slots to one, start array with just the 1st device, stop array, set pool slots back to 2, re-assign 2nd device, start array, if it doesn't work post new diags.

I don’t have the option to set slots to 1, the lowest number is 2.

Unassign all devices, start array, stop array, now set slots to 1 and re-assign the 1st device, then continue with

58 minutes ago, JorgeB said:

start array with just the 1st device, stop array, set pool slots back to 2, re-assign 2nd device, start array, if it doesn't work post new diags.

 

That worked perfectly! The pool is balancing now. When it is complete, I will add the new cache_ssd pool.

Thank you so much for your kind assistance and patience!