I apologize first and foremost, I'm a noob.

My cache pool  showed unmountable on a reboot. As I was trying to fix this, I read that doing a "new config" I might be able to correct my issue. My mistake was I selected the wrong assignments and did the reverse. I did a "new config" on my array slots instead of my pool slots. I have no idea what to do other than pounding my head on the wall for my stupidity. Is there anyway I can find my old config or am I SOL? Any help is appreciated, I have no idea what to do other than just starting from scratch. 35tb of data loss.... 

Hello @minhquan07, first, if you do not do inconsiderate actions, your data should be safe.  

 

Do you have a recent array health report ?

Your disk assignement is included :

 

In any case, I would wait for a more experienced user to give your proper advice for the next steps.

 

Considering that you had disabled drives, your diagnostics might help to guide you from there, please attach the zip to your next post. (Tools / Diagnostics)

Thank goodness, How do I access the health report? I run the parity checks monthly. The only inconsiderate action I might have done since freaking out was start the array with the new config (disks in new placement). I noticed that the data is still there and my cache pool still showing unmountable, but now with "no pool uuid". The system is currently running a parity-sync/data-rebuild.

The attached diagnostic is with the new array arrangement.  

tower-diagnostics-20210430-0843.zip

Edited April 30, 20215 yr by minhquan07
spelling

1 hour ago, minhquan07 said:

I noticed that the data is still there and my cache pool still showing unmountable, but now with "no pool uuid".

 

According to the log these are the only two devices with a valid btrfs filesystem, and a different one, so they weren't from a pool:

 

Apr 29 21:00:11 Tower kernel: BTRFS: device fsid bc84f358-49ca-4bfe-abf3-eaed0c9d7c53 devid 1 transid 298261 /dev/sdn1 scanned by udevd (1843)
Apr 29 21:00:11 Tower kernel: BTRFS: device fsid 402fa753-15e2-450f-a062-090043d62a5c devid 1 transid 142621 /dev/sdh1 scanned by udevd (1843)

 

You assigned these 3:

 

Apr 29 23:43:10 Tower emhttpd: import 30 cache device: (sdn) PERC_H800_00fed4e00dcc545625005f1746b0ad4b_36a4badb046175f00255654cc0de0d4fe
Apr 29 23:43:10 Tower emhttpd: import 31 cache device: (sdu) PERC_H800_00f516110cc70000ff005f1746b0ad4b_36a4badb046175f00ff0000c70c1116f5
Apr 29 23:43:10 Tower emhttpd: import 32 cache device: (sdk) PERC_H800_001dff5c100b8d1d28005f1746b0ad4b_36a4badb046175f00281d8d0b105cff1d

 

So the other two don't have a valid btrfs filesystem, you can try to mount sdn its own with UD, then post new diags if it fails.

I see, should I wait for the parity-sync/data-rebuild to finish first? 

I would wait so you can get the array to a protected state.

3 hours ago, minhquan07 said:

Thank goodness, How do I access the health report?

It is a notification (Settings / Notification Settings) that informs you on a schedule of the status of the Array and the Pools.

I am not sure what is the default setting for that, if you don't know what it is, I suppose you don't have it activated.

On 4/30/2021 at 10:15 AM, JorgeB said:

So the other two don't have a valid btrfs filesystem, you can try to mount sdn its own with UD, then post new diags if it fails.

 

Sorry for the delay, the parity-sync/rebuild just finished. I tried to mounting sdn but still getting the unmountable error. I'm not sure what "UD" means, I'm sorry

10 minutes ago, minhquan07 said:

I'm not sure what "UD" means

 

The Unassigned Devices plugin.