foo_fighter

No, unfortunately rebuilding the drive will restore everything including the filesystem. If you're risk tolerant, you could convert one of the parity drives to a data drive and transfer data to it and then rinse and repeat then move it back to dual parity when you're done.

photo prism, photo structure(heif-convert) or icloudpd can do the conversion.

Do you have snapshots for that data? Disk space won't be freed until all snapshots are deleted as well.

Immich is probably another one you should try. Even NextCloud has a photos app.

You could use a SAS expander JBOD with another 8i HBA. https://www.pc-pitstop.com/8-bay-expander-tower-trayless Or possibly a USB/C JBOD. https://www.amazon.com/QNAP-TL-D800C-Desktop-Enclosure-Connectivity/dp/B086WCRFQ3?ref_=ast_sto_dp&th=1 https://www.amazon.com/Syba-Swappable-Drive-External-Enclosure/dp/B07MD2LNYX/ref=sr_1_5?crid=1R2191VVMMSCR&keywords=8%2Bdrive%2Bjbod&qid=1702435563&s=electronics&sprefix=8%2Bdrive%2Bjbod%2Celectronics%2C109&sr=1-5&th=1

Are you going from PC -> Unraid? FreeFileSync(or the many gui sync applications or Rsync(command line) on unraid would work.

I have a similar setup. I don't think it matters but I'd also like to know if anyone's tried to optimize their setup. 300MB/s for Sata gen2 is more than the sustained read/write of your spinning disks.

You would use a JBOD or a picopsu with a couple of 5in3 SATA hot swap backplanes. Here is a similar setup:

It's pretty transparent. If you have an older drive or ssd and a spare port you might as well try it. In the shares setting, you can set the preferences for "Movies." It will first copy it to the cache and then later, the mover will move it from cache to the array. The entire time, it will appear is if it is under the "Movies" share. You'll speed up transfers to the limit of your network connection instead of your array write speeds. In your case, it might not have any benefits.

Unraid can run on Terramaster and Asustor(x64) without too much hackery. It comes by default on the lincstation. For the Lincstation I was going to add 3.5" drives via a USB 10gbs JBOD, 10gbs should be enough for 4 drives, either that or use SATA extension cables to a 4 or 5 bay sata hot swap backplane(That's admittedly a bit of a hack). Speaking of AOOSTAR, they announced 2 new NAS devices, available soon: https://aoostar.com/blogs/news/aoostar-pro-4-bay-nas-with-n100-n305-5700u-cpu The TPU can be installed in a E.key right? some of these systems come with wifi-bt in as an E.key module.

If you have mover tuning. I had to set it from 0% to 5% to get it to work. I'm not sure if it was the act of saving settings or the change from 0 to 5.

You could run file integrity / bunker on top of that and check the Xattr or something like snap raid. Rsync has its own -checksum switch but it slows down the process dramatically. If backing up ZFS to ZFS, you should investigate syncoid(part of sanoid) or Znapzend. Here is a similar thread:

Both photoprism and photo structure have options leave the photos inplace. I tried both and stuck with photoprism. I still have photostructure but just disabled the docker.

The Linkstation N1 is currently €256 EUR On Indiegogo €322 EUR if you wait for the release. I'm very tempted to get one and do some mods/hacks, like run 3.5" drives from the 2 Sata ports possibly more with a M.2 to Sata converter. I know this defeats the purpose of a "silent" NAS but I'd rather have more storage. Cool 3d Print BTW.

OP: have you looked at any of the pre-build N5105 systems? Asustor, Terramaster, or even the Lincstation N1 with the included Unraid License?

Let's say I only have 2 identical disks. Both Unraid Parity with 1 ZFS Disk and A Zpool would be considered "Mirrors" with the same information identically stored on both drives. But it seems like there are some subtle differences: A Zpool would have bitrot protection(A Scrub would auto fix it) but Unraid parity would not(Need to restore from Backup if Integrity plugin indicates mismatches)? Both can provide ZFS snapshots. Unraid Parity: Reads only would only require 1 drive to spin up, Would a Zpool require both drives to spin up? Expanding: Unraid Parity is easier to expand with extra drives without touching existing data. I'm not an expert but it seems like you cannot change a ZMirror to a RaidZ1(Parity) easily? You have to destroy/rebuild the pool? A build with Zpools only needs a dummy parity assigned(could be USB)? Mover can move from Cache Pool to Array. Can it also now be configured to Move from 1 Pool to another Pool? Any other pros/cons/differences between the 2?

I've had this same issue and it turned out to be bad memory. Running memtest found it and after replacing the RAM, the corrupted USB drive went away as well as other issues.

@bonienl This is the same issue that happened with the 6.10 -> 6.11 Transition. the s3_script command to find the array disks doesn't match the disks.ini file. Could you make the -PB cmd line argument more future proof as more lines are added to disks.ini? From my previous post about the fix for 6.11 (modified to add more before lines in the grep command)

This plugin was updated on 2/5/2023 but still doesn't seem to fix the s3_sleep issue: Mine still shows 3.0.8 and I still had to manually change PB12 to PB13 for 6.11.5 to recognize the array disks properly. # Version 3.0.8 Support for Unraid 6.9 # s/PB12/PB13/ for new .ini format # # Bergware International #################################################################################### version=3.0.8 program=$(basename $0) ini=/var/local/emhttp/disks.ini # Get flash device getFlash() { flash=($(grep -PB13 '^type="Flash' $ini|grep -Po '^device="\K[^"]+')) } # Get list of cache devices (if present) getCache() { cache=($(grep -PB13 '^type="Cache' $ini|grep -Po '^device="\K[^"]+')) } # Get list of array devices getArray() { array=($(grep -PB13 '^type="(Parity|Data)' $ini|grep -Po '^device="\K[^"]+')) }

In my case, silent file corruptions and corrupted USB stick on reboots or shutdowns. Please don't use a faulty memory module.

disks.ini seems to have changed after 6.9X which causes the dynamic s3_sleep plugin to not be able to detect array disks. Not sure if this plugin is actively updated. Fix is here:

Found this after I made the same fix: root@Tower:/usr/local/emhttp/plugins/dynamix.s3.sleep/scripts# diff s3_sleep s3_sleep.orig 41d40 < # Change -PB12 to -PB13 for new .ini file format 51c50 < flash=($(grep -PB13 '^type="Flash' $ini|grep -Po '^device="\K[^"]+')) --- > flash=($(grep -PB12 '^type="Flash' $ini|grep -Po '^device="\K[^"]+')) 56c55 < cache=($(grep -PB13 '^type="Cache' $ini|grep -Po '^device="\K[^"]+')) --- > cache=($(grep -PB12 '^type="Cache' $ini|grep -Po '^device="\K[^"]+')) 61c60 < array=($(grep -PB13 '^type="(Parity|Data)' $ini|grep -Po '^device="\K[^"]+')) --- > array=($(grep -PB12 '^type="(Parity|Data)' $ini|grep -Po '^device="\K[^"]+')) To make it persistent, you'd have to patch the file here I believe or better yet ask the Author to update: /boot/config/plugins/dynamix.s3.sleep I'm not sure if this patch is stable, there's gotta be a more robust way to get the array devices, otherwise next time we'll be hacking it to -PB14.

The repos have been updated to patch the log4j exploit. Everyone should pull the update.

You can try adding this to your preferences.xml: disableRemoteSecurity="1"