03-17-2022, 02:46 PM
(This post was last modified: 03-17-2022, 03:04 PM by UpsiUps.
Edit Reason: Additional information from source
)
(03-17-2022, 11:53 AM)Tim Curtis Wrote:(03-17-2022, 11:22 AM)UpsiUps Wrote: I hate the Major version upgrades as I have to walk and find all my RPis in the house, plug th eSD card , burn a new one , plug the new one in and restart configuration ... Oh, last point has a significant improvement : backup and restore !
Excellent! and even a possibility to run my own restore script - more excellent !
I all mention that as there seems a small bug, that I have been faced during my upgrade procedure: I unwraped all backup-zips to grab the unique moodecfg.ini and throw them on the /boot partition. That worked very well and the players came up even with the NAS connected per NFS. I then restored using the zip file the rest.
... and then I had a duplication of my NAS Library as Library source. So it seems that restore adds the library regardless if this is already connected.
Workaround ist fast: just deleted the latest entry of the list. But maybe you want to proof, why the duplication is happening.
The Restore handles copying moodecfg.ini to /boot. You don't have to do it manually.
Not really: If you don't change the moodecfg.ini the system might get no IP and the hostname will be wrong. if you boot up multiple RPis you have the fun to find them on your local network.Only after that you could start the restore to fix things. So -IMHO- I think the sequence is better it is better to copy the moodecfg.ini before you boot up the first time. After that you start the restore to re-create your local radiostation etc.
The restore will also find the configuration moodecfg.ini and will restore it a second time. That should not be a problem. The only observation is, that the source entry was now duplicated.
Maybe I missunderstood the restore process: is there a way to start the restore on a fresh image ? E.g. by store the backup...zip on the /boot partition ? I am currently only aware to start the restore after mood has started and you could use the browser UI to upload the backup.zip file.
In generic it is not a big issue. I would like to thank you that the major upgrade process is nowadays much easier than in the 5.x and less releases.
- Update -
I reviewed the source and found the challenge :
Code:
.... line 188 of backupmanager.py ...
if configPresent:
print('config')
content.append('config')That's the reason, why the Source/Library entry is duplicated. Now, if I want to "restore" , why would i like to append it to the current moodecfg.ini ? I would rather think I would like to overwrite the moodecfg.ini even if it is in place, nor ?
