horsekeeper

Some other small things I have noticed when upgrading to DSM 7.1.1 I had to create a new Hyper Backup as the existing one didn't recognise all the applications. The Hyper Backup created a .hbk folder keeping a copy of what it backed up. Took me a bit by surprise when I realised I had 3.7TB less space than before running the backup. I have a scheduled task that checks my external IP and e-mails me when it changes. WHen the scheduled task failed, it didn't e-mail me, so had to set that up again I had changed the default port on Photo Station on DSM 6 and had to do it again on DSM 7 Just minor things and I am sure I will find more over the next few weeks. Now, just need to find a decent encrypted Cloud Backup solution in case the house burns down. I was thinking iDrive as it seems value for money, but do I want my data stored in the USA?

Hi, It wasn't just watched and unwatched. I had to create new libraries and Plex had to download all the Metadata again. Even the sort titles for the movies disappeared. More annoying than actually causing an issue. I did play with changing the settings on the loader when I was on 6.1.7 and managed to get a USB key to appear as an extra HDD slot, but couldn't get it to create a btrfs volume. I have 4 x 8TB WD Red Plus in Raid 5, so might change that to 3 x 12TB in Raid 5 and change the 4th slot to be a btrfs.

I created the USB loader, stuck it into the HP Microserver, booted and then followed the on-screen menu to finish the install. I didn't have the TinyCore symbol like it has in the screenshots but the menus seemed to work fine for me. I downloaded the arpl-1.0-beta3.img.zip, possibly from this forum and it worked a treat. Much easier than Jun's loader. Python isn't supported in DSM7 (I had to uninstall the package along with some others) but I had my Sonarr, Radarr, Sabnzbd, Lidarr and Bazarr running in Docker anyway, so wasn't an issue for me. They all started fine. It did mess up my Plex Server though and I had to create new libraries. Not looked into where the plex files are and if I can manually update them to the correct path as it thinks a lot of stuff is "unwatched". I am not running Plex inside docker as it works fine as a normal Synology application package. I did try to install a Virtual Machine but my storage is set up as Ext4 and VMM wants a Brfs storage. What type of storage are you using? Next weekend I was planning researching this: https://kb.synology.com/en-id/DSM/tutorial/How_to_change_from_ext4_volume_to_btrfs_volume But wasn't sure whether that is asking for more trouble. I was bricking myself that I wouldn't get the NAS back after the migration to 6.2.4 failed Even though I consider myself IT savy, I don't like tinkering with systems that work, especially since I don't do this on a day to day basis. Good Luck!

When in doubt, fix forward and do not roll back. Not sure how exactly, but I followed this guide more or less https://xpenology.club/install-dsm-7-on-baremetal-or-vm/ and am now on DSM 7.1.1-42962 Update 4 Just waiting for Photostation to do its thing and do some testing. I see Plex needs a repair too, but at least it is sort of back.

Thanks, I tried doing that. I shut down my NAS, took out all my HDD, took out the working USB. Created a new USB using the 1.03 loader (that took ages as win32 DIskImager kept giving me an Error 5) and then all of a sudden it worked. Stuck in 4 old HDD, booted, used find.synology.com to find the NAS, then tried to update to 6.2.3-25426, which said, it worked, then the NAS rebooted but I couldn't get synology to work. I then shut down, took out the USB stick, put the old one in, booted and it told me it recognised new HDD and if I wanted to recover, stupidly, I said yes, it rebooted but now even though find.synology.com can find the NAS, it won't connect. I then shut down, took out the old HDD, put the working ones in and now when I boot and find.synology.com, although it finds the NAS, it finds 4 of them, on the correct IP addressed but two of them have DSM version 6.2-23739 and two of them have DSM version 6.1-15284 (see screenshots below) No matter which one I try to connect to, I get a timeout. I'm unsure as to what to do next...any ideas? I took a full back-up before starting, so if I can get a working 6.1.7 again, I suppose I can restore from the backup? Thanks

Hello, @Turbine-7WHat did you end up doing? I am currently running a DS3615xs on a HP Gen 8 running DSM 6.1.7-15284 and was thinking of upgrading to DSM7. I only use my NAS for backups of other devices, Plex, Photo Station and used to use Surveillance Station when I only had 2 cameras, biut since I now have 3, I have tried ZoneMinder, iSpy and Shinobi but still prefer SS over all of these. I was thinking of moving to the DVA1622 loader but wasn't sure if I really needed to do the interim updates from 6.1.7 to 6.2.4-25556 to 7.0.1-42218 to 7.1-42661 or if I could go straight from 6.1.7 to the latest working 7.1-x version. Thanks.

Hi, I was curious as to how you got on? I have an HP ProLiant Gen8 G1610T MicroServer running on 6.0.2 and want to upgrade to 6.2.2 so followed the same steps you had above but in step 3e it didn't let me choose "migrate". It told me "We've detected that the hard drives of your current DS3615xs have been moved" and told me I needed to do an install. I'm worried that with an install I will lose all my settings and setup, so I aborted. Do I need to go to 6.1.x first and from there go to 6.2.2? Thanks.