Then if it is disposable data you may destroy the “Security Tapes” dataset, create a new one (great opportunity to get rid of the space in that name…) and scrub. Hopefully, the error hasn’t crept to a higher level and will go away with the (meta)data.
Otherwise, for a transfer you would create a replication task and run it manually (no schedule).
I am struggling to destroy the data since it is in the read only state. What would the best approach be?
Just don’t copy the data off the read only pool or you destroy it where you are placing the Recovery. You can skip “Security Tapes”, if it’s not need or unrecoverable.
Anyone have any suggestions even im just replicating one data set at a time? Is there any way to ignore the corrupted data set and import the rest?
I came across a different post but I was hoping some more experience users would have posted. I don’t think you can use ZFS Replication is your case.
this shows using Core but may give a clue how to accomplish it.
Thank you i will start working on this as an option.
Things are happenings. I didn’t need to go as far as installing Truenas Core but i ran the same import read only command. Then I setup a new HDDs_Recovery pool z1. And am now running this command.
rsync -avh --progress --numeric-ids
–ignore-errors
–no-acls --no-xattrs
–inplace --whole-file
/mnt/HDDs/Applications/
/mnt/HDDs_Recovery/Applications/
It seems to be copying data to the new drive pool. Hoping once it is down i can start see my files again. Fingers crossed.
If anyone has any more insight or a better method please let me know.
Looking like im going to need to go to a more consumer friendly solution. I was able to get all of the data copied as far as i could tell but it seems none of the data is mounted properly and The gui at least cannot make sense of it. Im going to try a fresh install as it seems the HDD s pool is now stuck in a permanent read only state.
root@TitanHexNas[~]# mount | grep 'on / ' boot-pool/ROOT/24.10.2.4 on / type zfs (ro,nodev,relatime,xattr,noacl,casesensit ive)
root@TitanHexNas[~]# zpool import HDDs cannot mount '/HDDs': failed to create mountpoint: Read-only file system Import was successful, but unable to mount some datasets root@TitanHexNas[~]#
root@TitanHexNas[~]# zpool import -o mountpoint=/mnt/HDDs HDDs property 'mountpoint' is not a valid pool or vdev property
root@TitanHexNas[~]# mkdir -p /HDDs/Applications mkdir: cannot create directory ‘/HDDs’: Read-only file system
root@TitanHexNas[~]# zfs get mountpoint -r HDDs NAME PROPERTY VALUE SOURCE HDDs mountpoint /HDDs default HDDs/Applications mountpoint /HDDs/Applications default HDDs/ix-apps mountpoint /.ix-apps local HDDs/ix-apps/app_configs mountpoint /.ix-apps/app_configs inherited from HDDs/ix-apps HDDs/ix-apps/app_mounts mountpoint /.ix-apps/app_mounts inherited from HDDs/ix-apps HDDs/ix-apps/docker mountpoint /.ix-apps/docker inherited from HDDs/ix-apps HDDs/ix-apps/truenas_catalog mountpoint /.ix-apps/truenas_catalog inherited from HDDs/ix-apps
root@TitanHexNas[~]# zfs list -r HDDs NAME USED AVAIL REFER MOUNTPOINT HDDs 4.55T 9.87T 4.16T /HDDs HDDs/Applications 396G 9.87T 396G /HDDs/Applications HDDs/ix-apps 348M 9.87T 139K /.ix-apps HDDs/ix-apps/app_configs 128K 9.87T 128K /.ix-apps/app_configs HDDs/ix-apps/app_mounts 128K 9.87T 128K /.ix-apps/app_mounts HDDs/ix-apps/docker 229K 9.87T 229K /.ix-apps/docker HDDs/ix-apps/truenas_catalog 347M 9.87T 347M /.ix-apps/truenas_catalog
root@TitanHexNas[~]# ls -lah /mnt/HDDs_Recovery ls -lah /mnt/HDDs_Recovery/* total 9.0K drwxr-xr-x 2 root root 2 Feb 1 16:49 . drwxr-xr-x 7 root root 7 Feb 1 16:49 .. zsh: no matches found: /mnt/HDDs_Recovery/*