Jump to content
XPEnology Community

DSM 6.0.2 Upgrade path to DSM 7


Recommended Posts

Sorry if this has been asked before, but couldn't find by searching or in the tutorials. 

 

I'm on DSM 6.0.2-6451 Update 8 (baremetal HP Gen8) and would like to upgrade to 6.2 to try Synology VMM and then DSM 7.x. Do I need to install 6.1.7 first, or can I go straight to 6.2.3?

 

The reason I've held back over the years is because I'm on an old 8.0.0 version of Surveillance Station and can't update it. Looks like VMM offers me a workaround, but another question - does anyone know if SS 8.0 runs on DSM 7?

Link to comment
Share on other sites

https://www.synology.com/en-global/support/download/DS3615xs?version=7.1#system

 

image.thumb.png.5dcccbe3f8a2d335e5900c3a256d0bed.png

 

This is the official Synology's recommandation to update from 6.0.2 to latest version.

 

In your case :

 

image.thumb.png.4a495aa62caf2580422f983bed47e44f.png

 

image.thumb.png.a42d2644bd9e6476bf5dcfd5b9b5024b.png

 

Edit : You can forget SS 8 on DSM7, you should also forget about VMM.

 

You probably should look to DVA1622 loader wich offers 8 camera licence once you go to DSM 7.

Edited by Orphée
  • Like 1
Link to comment
Share on other sites

Thank you.

 

What's wrong with VMM on DSM 7? The workaround is to load DVA1622 on a VM to import the extra licenses. I'd like to try this on 6.2 if possible, before updating to DSM 7. I only have 4 camera's, but want to make sure everything works first as that's one of the main uses for the server.

Edited by Turbine-7
Link to comment
Share on other sites

I don't think you can have camera licences with Synology VMM. Dev are not that dumb. Virtualized DSM "knows" it is not a real one and does not give an extra licence.

 

You are currently running 6.0.2, probably DS3615xs or DS3617xs. You best option if you want to go to DSM7 is to migrate from your current loader to DSM7 DVA1622 loader.

 

I did not try DVA1622 as baremetal on the Gen8 but I made it run under Proxmox so it should work as baremetal too.

 

Link to comment
Share on other sites

Well you really should consider DVA1622 as it use the intel HD iGPU to make its AI advanced features working.

 

So if you know how to make transcoding work on DS918+, I think it should be the same with DVA1622.

 

So I think you should be able to have transcoding AND SS AI advanced features...

 

But as I don't have compatible CPU to test transcoding, I can't confirm.

 

Try with a spare disk/usb key.

  • Like 1
Link to comment
Share on other sites

  • 3 months later...

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.

 

Link to comment
Share on other sites

I did the interim updates up to 6.2.3-25426 update 3. The next update is 7, but I stopped at this point as it gave me a chance to play with VMM to see if I could get all 4 cameras running.

 

I installed 6.2 on a VMM and installed SS. I've got both versions on 8.2.8-6335 (which is the last version you can do without DSM 7) and all 4 cameras are working.

 

I've also installed DSM 7 using VMM, which gave me a chance to try the loader. There are a lot more options (meaning more to go wrong), so I've been a bit nervous about updating. I could just run SS on a DVA1622 VM if I want the latest version.

 

 

Link to comment
Share on other sites

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?

 

image.thumb.png.78bf19bffdd2204068d6ed8a857d5846.png

 

image.thumb.png.9fd31ccbca69f61be178c5a20fa4f59d.png

image.thumb.png.51b50c10dbba768129bf4387aa874cae.png

 

 

 

image.thumb.png.544d75bad3abbd381dacb4254923a242.png

 

 

image.thumb.png.1e013f8c784f194f5ca06d082fb2a231.png

 

Thanks

 

 

Link to comment
Share on other sites

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.

 

 

 

 

 

Link to comment
Share on other sites

Glad you got it working!

 

Thanks for the link, I'll have a read. I think it was getting the right disk order that put me off before and not knowing which loader to choose.

 

Just read that there are issues with python 2 apps (couch potato, sickbeard etc) and Plex. Did you get yours working without using docker?

Edited by Turbine-7
Link to comment
Share on other sites

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!

Link to comment
Share on other sites

Thanks for the info!

 

I use sickbeard, sabnzbd and couchpotato, so I'll look at moving those to docker first. Plex Server might be an issue, but if it's just the watched/unwatched status, I can live with that.

 

I'm using Ext4 on all disks except the SSD. Had to change that to have some storage for VMM.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

Some other small things I have noticed when upgrading to DSM 7.1.1

 

  1. I had to create a new Hyper Backup as the existing one didn't recognise all the applications. 
  2. 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.
  3. 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
  4. 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?

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...