Recommended Posts

Hey just want to know how to update

 

Do i put the new bootloader 5.2 and migration my data to the new system

or do i update in the 5.1 boot loader then once updated remove usb and put 5.2 boot loader?

 

i'm not clear on what to do to update to 5.2

 

i'm running DSM 5.1-5055

Share this post


Link to post
Share on other sites

me the way i did it

 

toke a spare usb key

load on it XPEnoboot_DS3615xs_5.2-5565.2

stop my nas

reboot with the new usb key

go in dms

go to update and manually update the pat DSM_DS3615xs_5565

reboot after.

install update

and all should be good

 

my setup is bare metal pc

Share this post


Link to post
Share on other sites

I took a slightly different approach.

 

1. Removed USB stick with 5.1 image - server still running!

2. Wrote new 5.2 image to USB stick

3. Put the USB stick back in the server - server still running

4. Updated manually in DSM with downloaded pat file

5. Server rebooted - the USB stick with the new image did it's job patching files

6. Updated to update 2 through DSM

 

And voila - running 5.2-5565.2 without problems.

Did this procedure on 3 different N54L servers.

Share this post


Link to post
Share on other sites

Hi!

 

I tried the approach from Zarocq, but it stops at 65% and gives me an "error 21" is there any solution to this?

 

I am currently on 5022.5 on a N36L barebone.

Share this post


Link to post
Share on other sites

is it possible to update 5.1 to 5.2 if you have forgotten the admin password ?

I have seen that on 5.2 there is a way to rest the admin password but not on 5.1.

 

If I create a new "new bootloader 5.2" and then press tab and select upgrade will it kill my data on my NAS ?

Share this post


Link to post
Share on other sites

admin user is disabled in later dsm, you create a new account with admin rights and use that

Share this post


Link to post
Share on other sites

if your data is important then you should back it up before any upgrades.

However, I have updated several bare metal setups from 5.1 to 5.2 (using a method similar to @thecapri) and things were fine.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now