JackTovey

You're a scholar and a gent/lady, switched to Rsync and it appears to be working.

I keep seeing errors about unresolved hardlinks, unsure how to fix these, does anybody have any advice.

I recently moved my machine around and I have since started to get errors thrown in syslog for the two SSDs which I have hosting the files for my docker containers and such, and it appears to have been causing some issues since the move. Nothing before the move afaik, so I am really confused. I have tried them on two different cables on the HBA, no joy, so either the HBA is borked (which I doubt as the other drives appear fine), the drives themselves are bad, or I have another issue that is masquerading as an issue with the SSDs. Hardware in question: HBA - LSI 9400-16i (running in a 4x wired 16x slot, appears the be running the latest firmware as far as I can tell) SSDs - Samsung 860 Evo 500GB Error (this shows one drive but I have also seen a similar error on another drive): Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: attempting task abort!scmd(0x000000000f47542d), outstanding for 30212 ms & timeout 30000 ms Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: [sdf] tag#299 CDB: opcode=0x42 42 00 00 00 00 00 00 00 18 00 Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: handle(0x002f), sas_address(0x300605b010b23967), phy(7) Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: enclosure logical id(0x300605b010113960), slot(11) Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: enclosure level(0x0000), connector name( C2 ) Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: task abort: SUCCESS scmd(0x000000000f47542d) Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: attempting task abort!scmd(0x000000002ece6e8d), outstanding for 30242 ms & timeout 30000 ms Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: [sdf] tag#297 CDB: opcode=0x2a 2a 08 00 00 08 80 00 00 08 00 Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: handle(0x002f), sas_address(0x300605b010b23967), phy(7) Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: enclosure logical id(0x300605b010113960), slot(11) Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: enclosure level(0x0000), connector name( C2 ) Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: No reference found at driver, assuming scmd(0x000000002ece6e8d) might have completed Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: task abort: SUCCESS scmd(0x000000002ece6e8d) Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: attempting task abort!scmd(0x00000000fbaff48a), outstanding for 30186 ms & timeout 30000 ms Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: [sdf] tag#292 CDB: opcode=0x2a 2a 00 09 14 d7 40 00 00 b8 00 Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: handle(0x002f), sas_address(0x300605b010b23967), phy(7) Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: enclosure logical id(0x300605b010113960), slot(11) Dec 13 20:32:50 lil-NAS-x kernel: scsi target9:0:5: enclosure level(0x0000), connector name( C2 ) Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: No reference found at driver, assuming scmd(0x00000000fbaff48a) might have completed Dec 13 20:32:50 lil-NAS-x kernel: sd 9:0:5:0: task abort: SUCCESS scmd(0x00000000fbaff48a) Dec 13 20:32:51 lil-NAS-x kernel: sd 9:0:5:0: Power-on or device reset occurred Really appreciate anybodies suggestions regarding this.

Out of interest, does anybody have advice on using this alongside immich? I get alerts for the .immich files which I believe are updated every time I add a file, which generate a lot of noise in the output.

One feature request: Can you make it so that synchronising is a "per share" option, as depending on the type of data, I might not want to synchronise every share.

hey @Khaosstormer you need to upload the .txz file BEFORE you install the .plg file, then it does the extraction of the .txz file. Then you use the plugin UI to import the JSON file, similar to how you exported it.

Hey folks, not urgent, thought it was worth putting it in as a feature request, but now that Unraid doesn't show upgrade status for 3rd party containers in 7.0.1 (like those created with docker compose) any chance the new version you are working on could also check that somehow? Would be nice to not see "update ready" when everything is up to date

Seeing this error when I try to run the mover, any ideas: Jan 13 13:47:31 <redacted> emhttpd: shcmd (635638): /usr/local/sbin/mover start |& logger -t move & Jan 13 13:47:31 <redacted> move: Log Level: 1 Jan 13 13:47:31 <redacted> move: /usr/local/sbin/move does not exists, creating soft link Jan 13 13:47:31 <redacted> move: ln: failed to create symbolic link '/usr/local/sbin/move': File exists Jan 13 13:47:31 <redacted> move: mover: started Jan 13 13:47:31 <redacted> move: /usr/local/emhttp/plugins/ca.mover.tuning/age_mover: line 206: /usr/local/sbin/move: No such file or directory Jan 13 13:47:31 <redacted> move: cat: write error: Broken pipe Jan 13 13:47:31 <redacted> move: mover: finished

Howdy there folks, I was wondering if you can add in support for use alongside the docker-compose plugin? I have setup health checks and proper dependencies between services in my stack and sadly your plugin does not support this behaviour.