M0CRT

Jorge...Working. Note to self, do not expect the disk to be presented in exactly the same way via a cra*py USB3 dock > SATA interface. As soon as I returned the disk to a direct SATA3 interface on the M/B...it returned as a 'ZFS' partition rather than a 'member ZFS' partition and it imported / mounted with a blink of an eye. Sure useful to note for all. Get the basics right. Thanks again and apologies. Mo

Fair enough. I wonder also if attempting to access the drive via a USB dock when I created it on an internal SATA port is going to cause issues. Thanks for your response and all your amazing support you provide for everyone. Mo

Hi Jorge. I think I may have created on command line.. Apologies for not replying sooner...How strange. Would I be able to recover files with a recovery tool?

Hi Jorge...Sorry for the delay in responding. root@server:~# fdisk -l /dev/sdi Disk /dev/sdi: 2.73 TiB, 3000592982016 bytes, 732566646 sectors Disk model: 001-1ER166 Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 33550336 bytes Disklabel type: dos Disk identifier: 0x4226f2f1 Device Boot Start End Sectors Size Id Type /dev/sdi1 1 4294967295 4294967295 16T ee GPT

'No available pools to import' when attempted. It was created on the Unraid array around 3 months ago...prior to 7 upgrade.

/dev/sdi: TYPE="zfs_member" PTTYPE="PMBR". is the disk...obviously. :-)

JorgeB...you are a star. root@server:~# blkid /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="2732-64F5" BLOCK_SIZE="512" TYPE="vfat" /dev/md1p1: UUID="51354d8b-de02-4b42-affd-6135b2c3c012" BLOCK_SIZE="512" TYPE="xfs" /dev/md2p1: UUID="d780ea51-40b4-4fb8-8f8d-d43e75e8b8be" BLOCK_SIZE="512" TYPE="xfs" /dev/md3p1: UUID="6ff58b58-4324-4f1f-9b39-36c69ca5498f" BLOCK_SIZE="512" TYPE="xfs" /dev/md4p1: UUID="79f41d3e-1b61-4c6c-a4c5-44f58b7c9f8f" BLOCK_SIZE="512" TYPE="xfs" /dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs" /dev/nvme0n1p1: LABEL="SSD2" BLOCK_SIZE="512" UUID="129E4F7A9E4F557F" TYPE="ntfs" PARTUUID="e5c144bb-01" /dev/sdi: TYPE="zfs_member" PTTYPE="PMBR" /dev/nvme2n1p3: BLOCK_SIZE="512" UUID="9E16D8BC16D8969D" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="a61fa55f-f6ae-47c1-bab6-0205eca42e87" /dev/nvme2n1p1: UUID="34CC-A658" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="3215fab5-ac51-4177-ab85-ae023dec5eca" /dev/loop2: UUID="06090d70-8413-416b-a356-b1de5400af34" UUID_SUB="0ce29b88-ec2c-4181-a625-22bef20a7291" BLOCK_SIZE="4096" TYPE="btrfs" /dev/sdg1: LABEL="cache" UUID="11731246308525138860" UUID_SUB="5631085809690507914" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="5cecabc3-01" /dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs" /dev/nvme1n1p2: LABEL="SSD2" BLOCK_SIZE="512" UUID="9EFAE9F3FAE9C81B" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="4be98a8a-fd5e-4270-bbb8-a8daaf16d183" /dev/loop3: UUID="000ee9d6-418c-4ffb-a250-19b192adfb04" UUID_SUB="f3543e23-3229-4f00-98e2-a64649b9d2c4" BLOCK_SIZE="4096" TYPE="btrfs" /dev/sdh1: LABEL="cache" UUID="11731246308525138860" UUID_SUB="15774442455614836752" BLOCK_SIZE="4096" TYPE="zfs_member" PARTUUID="5cecabc1-01" /dev/nvme2n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="d6062404-96f5-417f-a41c-c9c3b46bc4d7" /dev/nvme1n1p1: PARTLABEL="Microsoft reserved partition" PARTUUID="226bc947-3397-452d-83e3-8ba10168d07c" root@server:~# zpool import no pools available to import root@server:~# zpool status pool: cache state: ONLINE status: Some supported and requested features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(7) for details. scan: scrub repaired 0B in 00:03:58 with 0 errors on Sun Sep 29 01:03:59 2024 config: NAME STATE READ WRITE CKSUM cache ONLINE 0 0 0 mirror-0 ONLINE 0 0 0 sdg1 ONLINE 0 0 0 sdh1 ONLINE 0 0 0 errors: No known data errors

Hi all Version 7. B2.. Looking to import a ZFS Pool that was created only on a single disk...and is separate from my main array (XFS) / cache (ZFS) Unassigned Devices shows FS as 'ZFS Member' and 'Partition'. I was expecting to be able to 'ZFS Import' but no pools are found. Do I need to off-line my array in some way? ZFS Master and Unassigned Devices + Unassigned Devices + installed. Thank you so much. Mo

Perfect Jorge. Worked like a charm! :-). Thanks

I have checked the 'cctv big disk' and it looks like it may be fully allocated: image: vdisk4.img file format: raw virtual size: 500 GiB (536870912000 bytes) disk size: 500 GiB Will the resparse still help here? i.e. am I not already allocating all the disk? XML of VM...noting the VM is a 'Synology'... <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/cctv-vm/Synology/vdisk4.img'/> <target dev='hde' bus='sata'/> <address type='drive' controller='1' bus='0' target='0' unit='4'/> </disk>

That's a great idea Jorge. Thanks. Think that's what the issue may be...I've run the balance on the BTRFS and i'm in a good place there. You are right, it's likely to be the 'allocation' of the images associated with my VM. I'll cp them back with 'resparsify'

I'll take a look :-). Thanks! UPDATE: Great article...thanks Kilrah! Yes...it's not as 'simple' as it may initially seem! :-)

As a follow up. Calc in Unraid shows 708Gb 'occupied' but on summary page, only 70/80Gb Free...Is the BTRS volume potentially reserving some space? Surely this should be reported as approx. 290Gb free?

Thanks for your feedback Jorge. Any reason why the difference in reported free space compared to usage?

Hi All I've pondered on this for the last 24 hours and am still scratching my head. Cache pool with x2 identical SSDs. Reported available disk space of 1Tb I've several shares set to cache only: System (87.0Gb) Appdata (35.3Gb) cctv-vm (running my CCTV VM) (554Gb) nzbdownload (Deluge downloads et al) (31.8Gb) The rest of my shares do not use cache at all. When I run a calc on space used for these shares and a DU, the space used and remaining does not calculate up. For example, if I calc my cache only shares (using the Unraid GUI on the shares page), the utilise space comes to a total of 708.1Gb. However, my 'free space' on the cache shows 73.0Gb... With my rough math, I feel like I'm missing around 240Gb...Could someone explain what I may be missing here? I've run a balance and scrub on the cache pool (not expecting that this would 'fix' anything) This a block size issue? Any reason why I may be 'loosing' disk space? I've triple checked and don't have something else on the cache beyond the shares / files above. Maybe file permissions in order to 'calc' the disk space? Yours, awaiting enlightenment and putting straight! :-) Thanks