SnarfsMojo

Should the shares be Primary = Cache, Secondary = Array or Primary = Array, Secondary = Cache Thanks much!

I have a ZFS Cache Pool that is acting up. qty 4 1tb SSDs, all SSDs are throwing read and write errors (they ran fine for a little over a year before the errors started). I did a zpool clear but the errors came back. This has me feeling all sorts of squidgy. I would like to get rid of the cache pool entirely at this point. All of my shares that utilize the cache pool have the same share settings, I have attached screenshots of the settings here. I would like to do the following - Ensure all data which was stored on cache is moved to the array Remove logical cache pool Physically remove cache drives If any of you lovely people could lend me a hand with what i need to change in my settings to make this happen, I would be eternally grateful. When I set this system up I had SO much more free time. 4 kids vs 2 kids = no more time for me to play with my toys... HA!

Diagnostics attached. :) Thanks! unraid-diagnostics-20250919-2121.zip

I have a zfs pool made of 4 1tb SSDs. Qty1 Crucial MX500 1TB 3D NAND SATA 2.5-inch and Qty3 Samsung SSD 870 EVO 1TB. I received notification that the life expectancy of the Crucial SSD was at 00% a few weeks ago. I have been super busy, and i didn't get around to checking on the pool until tonight. Below is what I see when I check the pool's status. I'm kinda freaked out. We use ZFS at work, but it is REALLY rare for us to see any errors. And when we do get errors, we clear them once. when they come back the drive gets replaced. This cache has only been in the server for about 18 months. Any thoughts / suggestions re: what I should do would be greatly appreciated. I added cache because my VMs seemed really slow, but frankly the cache hasn't seemed to have helped that at all. Might it be possible / reasonable to just migrate everything off the cache to spinny disks and chuck the cache entirely? :( root@unraid:/dev# zpool status pool: cache state: ONLINE status: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected. action: Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'. see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-9P config: NAME STATE READ WRITE CKSUM cache ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 sdaf1 ONLINE 0 38 0 sdz1 ONLINE 10 61 0 sdn1 ONLINE 13 121 0 sdt1 ONLINE 0 76 0 errors: No known data errors

just to follow up on this, I have been super busy as of late. last night I finally set aside time to dig in and try to fix the issue. and lo and behold, the issue has resolved itself *shrug*. not great, but not the end of the world let's just hope it stays fixed!

updated the drivers to the latest version, same results. Also, it should probably be mentioned that I can't manually start the VirtIO FS service either. When I try to it throws the error "Windows could not start the Virt-IO FS Service service on Local Computer. Error 1117: The request could not be performed because of an I/O device error."

Running with admin privileges OK

I am having an issue I hope ya'll can help with. I used the scripts provided by @mackid1993 to get a folder from my unraid box mounted and stable on a windows VM. It worked great for almost 2 months! Thanks for providing it, great work! I had backed up 59 of 60.5tb of data to backblaze. Unfortunately, the drive stopped working on 9/11/24. Now when the script runs to mount the drive, I see three events in my windows event viewer. Information: "launcher-x64: create virtiofs\viofsZ = 0" Error: "virtiofs: the service VirtIO-FS has failed to start (Status=c0000185)." Information: "launcher-x64: terminated virtiofs\viofsZ" I have reinstalled WinFSP and the virtio-win-0.1.248 drivers (my VirtIO FS driver version is 100.94.104.24800) Here is the virtiofs section of my vm config - <filesystem type='mount' accessmode='passthrough'> <driver type='virtiofs' queue='1024'/> <binary path='/usr/libexec/backup.sh' xattr='on'> <cache mode='always'/> <sandbox mode='chroot'/> </binary> <source dir='/mnt/user/backup'/> <target dir='backup'/> <alias name='fs0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </filesystem> Here is the script at /usr/libexec/backup.sh #!/bin/bash # process -o option but ignore it because unraid generates the command for us VALID_ARGS=$(getopt -o o -l fd: -- "$@")i if [[ $? -ne 0 ]]; then exit 1; fi eval set -- "$VALID_ARGS" while [ : ]; do case "$1" in --fd ) FD="$2" shift 2 ;; -o ) shift 1 ;; -- ) shift; break ;; * ) shift; ;; esac done # https://gitlab.com/virtio-fs/virtiofsd /usr/libexec/virtiofsd \ --fd="$FD" \ --shared-dir="/mnt/user/backup" \ --xattr \ --cache="never" \ --sandbox="chroot" \ --inode-file-handles="mandatory" \ --announce-submounts \ --syslog and here is the mount script I'm using on my windows vm @echo off :: Check for admin privileges net session >nul 2>&1 if %errorlevel% == 0 ( echo Running with admin privileges ) else ( echo Running without admin privileges echo Attempting to elevate process... PowerShell -Command "Start-Process -Verb RunAs -FilePath '%comspec%' -ArgumentList '/c %~f0'" exit /b ) :: Rest of your batch file starts here REM Modify the Drive Letters such as viofsJ J: as well as the tag (tag1) to match the tags (case senstive) set in Unraid. "C:\Program Files (x86)\WinFsp\bin\launchctl-x64.exe" start virtiofs viofsZ backup Z: TIA for any assistance / guidance you can provide

Thanks for the prompt replies! Is there a need to check parity after every rebuild (pulling a 4tb drive, replacing it with an 8tb drive, letting the 8tb drive rebuild based on parity settings)?

Good evening, i'm hoping someone can help me out - I am replacing qty8 4tb drives with qty 8 8tb drives. I have enough room in my array to add the 8tb drives in alongside the existing 4tb drives. I would like to use unbalance to move the data off of the 4tb drives and onto the 8tb drives. Once the 4tb drives have been emptied, could I just remove them from the array (stop array, physically remove the drives, start the array). My main concern is how much trashing removing the 4tb drives using the standard procedure (rebuilding the drive from parity plus the data on the existing drives) will cause. I have already migrated about 50% of one of the 4tb drives to an 8tb drive, then started doing some digging and realizing it may not be the best approach. TIA for anyone who can help Snarfy