Just wanting to post about how I went with the update from 3.9 to the new stable 4.1 to identify a few possible issues in case the information is of any use.
- Created backup from web-UI of 3.9
- Disconnected data drives
- Fresh install of 4.1 (text installer, all automated/defaults) onto new drive as I was moving from USB drive to SATA SSD at anyway (at last)
- Reconnected data drives
- Import pools
- Restore config from backup and wait until system settled (as per watching “top” from a shell)
- Data import/pools/shares all intact (important parts a duplicated to a backup service)
- NFS share configuration kept - just had to re-enable the service
- Extra users I had added were kept as expected. Needed to re-add my ssh public key and enable that user via sshd_config
- Rockons worked once I enabled the service, however some did not show up as installed in the web-UI. A
docker psshowed them running, eg. nzbget, and I could access its web interface, but it allowed me to re-install and now shows up. Same happened for Emby, Unifi and Transmission if I recall correctly
Not so much
- Samba share configurations weren’t restored and needed re-entering. Could this be because I had manually edited some parts of the config file previously? I changed the min protocol to get around older Sonos issues. Works after setting up the shares again.
- Scheduled tasks - They are restored, but point to the wrong shares and I don’t seem to be able to edit this. One example attached as a screenshot.
I believe this is because shares are referenced by a number in the backup file, eg. share 18, but these numbers must have changed on import?
One more suggestion. It would be great if we could export a backup that is not gzipped. I tried to reference the json file when manually restoring some settings but found it rather difficult to read after decompressing. A more human readable version might help.
Overall, glad to be on a much more up to date platform now after previously only having time to do a tiny bit of testing on another system back when we had to install OpenSUSE and rockstor manually on top.