17 hours ago, Roam1988 said:

Do you probably know if the btrfs mailing List ist still working?

It is.

I have the same thing trying to replace a cache drive now says unmountable unsupported.  Can I run something similar or maybe find away to backup the cache if the data is still there?

amacher-diagnostics-20250205-1400.zip

1 hour ago, Jeff Amacher said:

trying to replace a cache drive

First thing, disable Docker and VM Manager in Settings until cache is working again.

Just now, trurl said:

First thing, disable Docker and VM Manager in Settings until cache is working again.

 

Unfortunately my entire cache drive is no longer showing or working so no docker or VM available now. 

Just now, trurl said:

First thing, disable Docker and VM Manager in Settings until cache is working again.

Since they were enabled, it already recreated those from scratch on the array. We will have some cleanup to do.

2 minutes ago, trurl said:

disable Docker and VM Manager in Settings until cache is working again.

 

1 minute ago, trurl said:

Since they were enabled, it already recreated those from scratch on the array. We will have some cleanup to do.

Is there anyway to get my data from the cache or make these usage able again with the data that's hopefully still on them? 

Looks like this was a 2 disk pool. Tell us more about what you did.

 

Also, have you followed this instruction yet?

6 minutes ago, trurl said:

disable Docker and VM Manager in Settings until cache is working again.

 

1 minute ago, trurl said:

Looks like this was a 2 disk pool. Tell us more about what you did.

 

Also, have you followed this instruction yet?

 

 

I cannot stop docker as they are all gone now and my VMS are stopped.   So stopped the array disabled the one disk and then started the array again.  I then shutdown and placed the new disk in the location.  Once started up I got the Unsupported message.  So I stopped the array replaced the existing cache drive back and started the array.  It still showing unsupported at this time.  Hope that helps?

 

Thanks for the support!

Go to Settings - Docker and post a screenshot.

 

Go to Settings - VM Manager and post a screenshot.

Just now, trurl said:

Go to Settings - Docker and post a screenshot.

 

Go to Settings - VM Manager and post a screenshot.

 

Here are the screenshots

 

 

So as you can see there in your screenshots, you have not yet followed my first instruction.

 

22 minutes ago, trurl said:

disable Docker and VM Manager in Settings until cache is working again.

 

1 minute ago, trurl said:

So as you can see there in your screenshots, you have not yet followed my first instruction.

 

 

Oh okay.  I got what you mean now.  Okay I disabled both now.  Sorry about that.

 

Post a screenshot of Main - Pool Devices

8 minutes ago, trurl said:

Post a screenshot of Main - Pool Devices

Here you go

Are those the original 2 disks that were in cache pool?

 

Was that pool btrfs or zfs?

Just now, trurl said:

Are those the original 2 disks that were in cache pool?

 

Was that pool btrfs or zfs?

Yes I placed the original two back in they were btrfs I believe. 

Let's see if @JorgeB can make sense of this.

28 minutes ago, trurl said:

Let's see if @JorgeB can make sense of this.

I get this in the array operations

 

Unmountable disk present:
Cache • WDC_WDS100T1R0A-68A4W0_24506J804746 (sdb)
Cache 2 • WDC_WD10EADX-22TDHB0_WD-WCAV5V485415 (sdi)

45 minutes ago, Jeff Amacher said:

I get this in the array operations

 

Unmountable disk present:
Cache • WDC_WDS100T1R0A-68A4W0_24506J804746 (sdb)
Cache 2 • WDC_WD10EADX-22TDHB0_WD-WCAV5V485415 (sdi)

Here is the fdisk command is this recoverable?

 

root@amacher:~# btrfs fi show
warning, device 1 is missing
warning, device 1 is missing
ERROR: cannot read chunk root
Label: none  uuid: f79cb3e6-b693-4a91-8cd9-4fc819da001e
        Total devices 2 FS bytes used 150.59GiB
        devid    3 size 931.51GiB used 153.00GiB path /dev/sdb1
        *** Some devices missing

 

 

root@amacher:~# fdisk -l /dev/sdb
Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC  WDS100T1R0A
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start        End    Sectors   Size Id Type
/dev/sdb1        2048 1953525167 1953523120 931.5G 83 Linux

 

root@amacher:~# fdisk -l /dev/sdi
Disk /dev/sdi: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EADX-22T
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

 

 

 

21 minutes ago, Jeff Amacher said:

Here is the fdisk command is this recoverable?

 

root@amacher:~# btrfs fi show
warning, device 1 is missing
warning, device 1 is missing
ERROR: cannot read chunk root
Label: none  uuid: f79cb3e6-b693-4a91-8cd9-4fc819da001e
        Total devices 2 FS bytes used 150.59GiB
        devid    3 size 931.51GiB used 153.00GiB path /dev/sdb1
        *** Some devices missing

 

 

root@amacher:~# fdisk -l /dev/sdb
Disk /dev/sdb: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC  WDS100T1R0A
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000

Device     Boot Start        End    Sectors   Size Id Type
/dev/sdb1        2048 1953525167 1953523120 931.5G 83 Linux

 

root@amacher:~# fdisk -l /dev/sdi
Disk /dev/sdi: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10EADX-22T
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

 

 

 

@trurl

Let's see if @JorgeB can make sense of this.

 

It may be several hours, it's way past bedtime in his timezone.

I already replied to user's other thread, and since you also started a new one, let's please continue there.

I am locking this thread since it was already marked solved for OP.

@Jeff Amacher

Resume discussion here: