Jeff Amacher

Got it. That fixed the issue and its running BTFRS operation to sync the data. Thanks Again.

I plug into another PC and it reads the drive was able to open and format the drive fine. I'm going to shutdown and restart see if that makes any difference.

Added the new drive and now its not showing up in the drop down list. This was the one I originally tried to add. You think this is causing an issue?

Thanks for the help. Saved me hours of work. Going to make a back up this time first and then swap the drive.

FYI - Beer money sent.

Thanks. Here is the latest Diag. amacher-diagnostics-20250206-1001.zip

So run a balance and select convert to raid1 mode or leave as perform full balance?

Okay thanks. Here are the diags amacher-diagnostics-20250206-0933.zip

I stopped and restarted the Array and now see my cache drive!! Thanks! I'll send beer money! How can I replace 1 of the drives and not have this happen again?

Here is the output root@amacher:~# btrfs fi show Label: none uuid: f79cb3e6-b693-4a91-8cd9-4fc819da001e Total devices 2 FS bytes used 150.59GiB devid 1 size 931.51GiB used 151.06GiB path /dev/sdi1 devid 3 size 931.51GiB used 153.00GiB path /dev/sdb1

Yes it was. Here is the output root@amacher:~# sfdisk /dev/sdi Welcome to sfdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Checking that no-one is using this disk right now ... OK 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 sfdisk is going to create a new 'dos' disk label. Use 'label: <name>' before you define a first partition to override the default. Type 'help' to get more information. >>> 64 Created a new DOS disklabel with disk identifier 0xcc430fa1. Created a new partition 1 of type 'Linux' and of size 931.5 GiB. Partition #1 contains a btrfs signature. Do you want to remove the signature? [Y]es/[N]o:

@trurl

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

I get this in the array operations Unmountable disk present: Cache • WDC_WDS100T1R0A-68A4W0_24506J804746 (sdb) Cache 2 • WDC_WD10EADX-22TDHB0_WD-WCAV5V485415 (sdi)

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

Here you go

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

Here are the screenshots

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!

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?

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

Went to replace a cache drive and then got this message above. I have placed back the original drive and still getting this error anyway to resolve or at least copy the cache drive data off? amach-diagnostics-20250205-1400.zip

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