toasti

Letztlich war's doch ziemlich einfach. Ich vergesse immer, obwohl ich das System schon 4 Jahre habe, dass man den Stick mit einem Backup ja sehr leicht auf einen alten Stand restoren kann. Hab also das Backup vor dem Upgrade auf den Stick gezogen, dann nochmal das Upgrade durchgeführt. Nun tut es! Danke für eure Hilfe, manchmal braucht es nur einen Denkanstoß.

Sprich, Stick neu machen mit der neuen 7er Version und von meinem Backup den Config Ordner auf den Stick packen. Ok. Könnte ich probieren. Ansonsten könnte ich auch ein Recovery vom letzten Backup fahren, sobald er wieder läuft einfach nochmal probieren auf Version 7 zu upgraden.

Wie meinst du das mit neu machen? Dann verliere ich doch meine Config. Das einzige wäre ein Backup auf den Stick zu spielen von der 6er Version und damit booten und Upgrade nochmal versuchen.

Hallo liebe Community, habe gestern auf V7 aktualisieren wollen und habe nun das Phänomen, dass er aus dem unraid Boot Manager nicht mehr heraus kommt. Ich kann zwar zwischen den Einträgen hin und her springen, aber er tut einfach nichts wenn ich ENTER drücke. Egal was ich wähle. Scheint also ein grundsätzliches Problem zu sein. Die 5 Sekunden laufen ab und fangen dann wieder bei 5 an. So geht das permanent. Habt ihr eine Idee was ich machen kann? 😕 Besten Dank vorab.

Oha! And I bet this will no more happen in future 😏

You have saved me from a sleepless night - many thanks!! It seems that all is ok, also no changes to my data. But will check tomorrow in detail. I was afraid to reboot and maybe no possibility anymore to get access to the system. Puh.... Thanks again!!!

Hello, accidentally I did this in the console Instead of this 😩😩😩 Just wanted to change permissions in one folder and subfolders in the current directory (nginx www) but overseen the / I have typed by mistake. I don't know what was really changed, it also says permission denied for a lot of folders. Is there any possibility to check this easily? Unraid says now "blacklisted" where I normally See "Unraid Plus". Web Terminal not working, No Log by web gui, every time I enter the URL I get a Login mask with "Set your password". I think I killed it... any Idea to fix this?! 😢 Please help!

Yes, that's the case, but what was nothing which bothered me. I just accepted it. It is more confusing and not ideal that we have to tweak the backups when upgrading to the new version. I will look now for the "fix", hope it will work. But what is about the old backup states in the chain? Will the cleanup work, I mean, the old backups before the last one are not moved to the new place. Edit: I moved the latest backup as suggested and then wanted to have a look if the script do the cleanup in the correct way, but the log is not complete. I backup 2 folders in this job, I can only see the details of the second folder backup, for example which backup states were deleted and which ones were preserved.

OK, thanks but is it not possible to change the script instead? I don't understand why it is not 100% compatible to the old version - was that not possible?

Thanks for the latest version, but in my understanding the existing "backup chain" should still be used with the new version - is that correct? So far I used version 0.6 and updated one backup job with the new script for a test and now it looks like the backup chain will be re-created (like a new initial backup) and ate a lot of additional space. If I change every job to the new script my backup disk will be full before all the jobs end. Do I something wrong? Please let me know. Many thanks!

I am in contact with the developer on a regular basis and he let me know to check all these settings and compare with the docker-compose. That's the reason why I compared it. OK, so I will stop PP, do a backup, change the config -> then update it and restart and cross my fingers. Thanks for your support - I hope it will run without any troubles...

OK, so I have to compare the complete template with the newest docker-compose from PP to edit, add and maybe delete some settings. For example "PHOTOPRISM_THUMB_FILTER" is no more part of the docker-compose - so just delete it in the template or will it corrupt anything? This setting is integrated in the gui of PP in the meantime.

No, not all, for example UID and GID. And others are no more available in the newest Docker compose. Please have a look here: https://dl.photoprism.org/docker/docker-compose.yml I am just not sure what will happen if I update the docker container with a new image.

I used your PhotoPrism App to get the PhotoPrism as Docker configured in my unRaid. Works like a charm. With the newest Release all the variables were changed in the config and have a prefix PHOTOPRISM_. Do I need to edit the complete config manually or did you already update the app that I can skip this? Until now there was no update available from your app, so I presume I have to edit the config manually - correct?

Thanks - clear now!