August 20, 2025Aug 20 Hi all,I was trying to remove one drive from a mirrrored cache pool that stored my app data and VMs. I stopped my array, unassigned the disk, then started my array again. I got an error: unmountable: wrong or no file system. I tried re-adding the drive to the cache pool, formatting the drive, etc. I can't fix the error to start my array with docker containers again. Please help! attaching diagnosticsEDIT: Reattaching diagnostics zip filetower-diagnostics-20250820-1121.zip Edited August 20, 2025Aug 20 by slam23
August 20, 2025Aug 20 Author Hello,I'm copying the output here:root@tower:~# btrfs fi showLabel: none uuid: ee35825c-5743-4d4c-96da-f8cf30cec007 Total devices 2 FS bytes used 137.65GiB devid 1 size 931.51GiB used 145.03GiB path /dev/nvme1n1p1 devid 2 size 953.87GiB used 145.03GiB path /dev/nvme0n1p1Label: none uuid: 29f54f96-23b1-4f36-b5bd-f37f070ecb95 Total devices 1 FS bytes used 41.69GiB devid 1 size 1.86TiB used 46.02GiB path /dev/nvme2n1p1Label: none uuid: 6f3ca181-9210-4942-aaad-eef8487ae2ea Total devices 1 FS bytes used 372.00KiB devid 1 size 40.00GiB used 536.00MiB path /dev/loop2Label: none uuid: dfc5688a-f673-4b69-90b7-b982c1059842 Total devices 1 FS bytes used 416.00KiB devid 1 size 1.00GiB used 126.38MiB path /dev/loop3
August 20, 2025Aug 20 Community Expert 18 minutes ago, slam23 said:Label: none uuid: ee35825c-5743-4d4c-96da-f8cf30cec007Total devices 2 FS bytes used 137.65GiBdevid 1 size 931.51GiB used 145.03GiB path /dev/nvme1n1p1devid 2 size 953.87GiB used 145.03GiB path /dev/nvme0n1p1This the pool you want correct? If yes, reimport it:on main click on the first device for that pool and then "remove pool"back on main, create a new pool with the same name and number of slotsassign the pool device(s), leave the filesystem set to autostart the array to import the pool and post new diags
August 20, 2025Aug 20 Author Thank you for the response. I followed the instructions in your post. Once I started the array, I see that the file system is "auto" and I am still presented with the message " unmountable: unsupported or no file system." Attaching the diagnostics:tower-diagnostics-20250820-1243.zip
August 20, 2025Aug 20 Community Expert The pool device is not showing the correct signature; post the output fromblkid /dev/nvme1n1p1blkid /dev/nvme0n1p1
August 20, 2025Aug 20 Community Expert After that, see if it mounts manually:mkdir /xmount -t btrfs /dev/nvme1n1p1 /x
August 20, 2025Aug 20 Author Output from first step:root@tower:~# blkid /dev/nvme0n1p1root@tower:~# blkid /dev/nvme1n1p1blkid /dev/nvme0n1p1/dev/nvme1n1p1: PARTUUID="39f940ee-01"root@tower:~# Output from second step:root@tower:~# mkdir /xmount -t btrfs /dev/nvme1n1p1 /xmount: /x: wrong fs type, bad option, bad superblock on /dev/nvme1n1p1, missing codepage or helper program, or other error. dmesg(1) may have more information after failed mount system call.root@tower:~#
August 20, 2025Aug 20 Community Expert And btrfs fi show still shows a filesystem for those two devices?If yes, type:btrfs-select-super -s 1 /dev/nvme0n1p1btrfs-select-super -s 1 /dev/nvme1n1p1If that succeeds, then once more:blkid /dev/nvme1n1p1blkid /dev/nvme0n1p1
August 20, 2025Aug 20 Author Output from btrfs fi showroot@tower:~# btrfs fi showLabel: none uuid: ee35825c-5743-4d4c-96da-f8cf30cec007 Total devices 2 FS bytes used 137.65GiB devid 1 size 931.51GiB used 145.03GiB path /dev/nvme1n1p1 devid 2 size 953.87GiB used 145.03GiB path /dev/nvme0n1p1Label: none uuid: 29f54f96-23b1-4f36-b5bd-f37f070ecb95 Total devices 1 FS bytes used 41.69GiB devid 1 size 1.86TiB used 46.02GiB path /dev/nvme2n1p1Label: none uuid: 6f3ca181-9210-4942-aaad-eef8487ae2ea Total devices 1 FS bytes used 372.00KiB devid 1 size 40.00GiB used 536.00MiB path /dev/loop2Label: none uuid: dfc5688a-f673-4b69-90b7-b982c1059842 Total devices 1 FS bytes used 416.00KiB devid 1 size 1.00GiB used 126.38MiB path /dev/loop3So I typed the first part:root@tower:~# btrfs-select-super -s 1 /dev/nvme0n1p1btrfs-select-super -s 1 /dev/nvme1n1p1warning, device 1 is missingusing SB copy 1, bytenr 67108864ERROR: /dev/nvme1n1p1 is currently mounted, abortingroot@tower:~#
August 20, 2025Aug 20 Community Expert Solution You have that device mounted with UD:/dev/nvme1n1p1 943G 138G 793G 15% /mnt/disks/20BA079912DE00043471You need to unmount if first, then try mounting the pool again.
August 20, 2025Aug 20 Author Hi, after I unmounted the disk and remounted the pool again, the drive copied data to the other drive. It seems to be operational now?I noticed that under the Dockers tab, I have no more docker containers intstalled (edit: and VMs are gone as well). At this point, is it possible to restore the containers from the pool somehow? I do have the Appdata Backup plugin setup so I can potentially restore from a previous backup but it is slightly less ideal because it's one week old.Thank you for the help so far. attaching diagnosticstower-diagnostics-20250820-1407.zipedit: I quickly installed all dockers again and the templates were saved. Although after some time, I got a notification that the docker image returned to normal so maybe I could have just waited? Anyways I consider this solved! Thanks so much Edited August 20, 2025Aug 20 by slam23
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.