#PIC Restore Directory - Unraid

1 messages · Page 1 of 1 (latest)

split egret
#

Have used some previous posts from bullmoose (Thanks <3) and have gotten PIC up and running on my Unraid server. First ran in report mode just to make sure it was running and it identified over 2000 images to clean. I then chnaged to move mode, but get a no such file or directory error when it attempts to move. I go to my plex path directory and there is no PIC RESTORE directory so thought maybe I need to create it so I did, but no luck same error on another run.

Most likely something stupid on my part, but I couldn't find any help searching this discord so here i am asking 🙂

Thanks! ❤️

proven leafBOT
#

Welcome @split egret!

Someone from <@&938443185347244033> will assist when they're available.

Including the meta.log from the beginning is a huge help, type !logs for more information.

#

You can press the "Close Post" button above or type /close at any time to close this post.

proven leafBOT
ruby burrowBOT
#
Providing Log Files

1: Go to your config folder

2: Go into the logs folder

3: Look for meta.log (not meta.1.log etc)

4: Drag it in the Discord thread - the whole thing, DO NOT EDIT IT

5: Still confused? ¯\(ツ)/¯

Log file too big? USE PASTEBIN or ZIP THE FILE

Thanks for using Plex Meta Manager!
split egret
quartz ginkgo
#

I don't think this is an error on your end, I think something changed or broke in the latest update because I ran PIC on 1/2 and it was fine but tried it today and got the same error you did

split egret
#

Oh, interesting.....good to know Thanks!
Do you happen to know if "latest" is the only version available to pull or if we can pull the last version that worked from Docker?

soft tulip
split egret
#

Thanks!!

#

Ok, based on @quartz ginkgo comment above, 1/2 would have been version v1.0.0 or maybe v1.0.1, will try those two and see what happens

ivory swallow
#

on 1/11, PIC was updated

quartz ginkgo
#

Yeah, I ran v1 for a while with no issues so you should be fine with that

ivory swallow
#

version 1.0.2 came out, which was a revert back to 1.0.0

#

so 1.0.2 should be good

split egret
#

Ok, so can go with v1.0.0 and v1.0.2

split egret
quartz ginkgo
#

I think 1.0.2 is what caused the issue actually

#

if you look at @split egret log file, it stats they're already running 1.0.2

split egret
#

I kicked off v1.0.1 before we finished this conversation
It seems to be running well so far.

quartz ginkgo
#

yeah I checked my old logs and it ran fine on 1.0.0 and 1.0.1

#

so something wonky with 1.0.2

split egret
#

Nice, thanks again!

#

Should I close this or keep it open as it is an issue with latest version?

quartz ginkgo
#

I'd recommend opening a github issue with your logs

split egret
#

ok, will close this up then to keep the discord clean, thanks