synogeek

HP N54L - DSM 6.1 onwards

Recommended Posts

Hi all, 

 

Sorry that I am confused after following all of the posts in here.


For what I understand, the loader (hp server n36l-n54l.zip) on the first page provided by khile can "fresh" install the DSM 6.1 on N54L but will fail if we want to "upgrade" from DSM 6.0... am I right?

 

I saw someone said they can upgrade to DSM 6.1 with data safe, may I know is it mean upgrade from DSM 6.0 with Jun loader v1.01??If yes, would anyone with successful upgrade please ... please share it step by step? Many thanks.

Share this post


Link to post
Share on other sites

Hi @all,

this is my first comment here. I have a HP 54L since 3 years now. Everything is fine. 30 min ago i updated my Version 6.0.2 to 6.1.2 15132 (with hp server n36l-n54l.zip, baremetal)

I have done all steps explained earlier here (VID/PID, also SN and MAC, C1E, force install...)

I have 4 HDDs WD Red 3TB with a RAID 5 volume.

 

After installing the DSM (new installation, not migrate option) i was still able to access my files! They were recognized directly in the DSM and also the RAID volume was fine without problems. I was able to write and read from the volume.

 

Just for an information :smile:

Edited by suschmania
baremetal
  • Like 1

Share this post


Link to post
Share on other sites
18 hours ago, suschmania said:

Hi @all,

this is my first comment here. I have a HP 54L since 3 years now. Everything is fine. 30 min ago i updated my Version 6.0.2 to 6.1.2 15132 (with hp server n36l-n54l.zip, baremetal)

I have done all steps explained earlier here (VID/PID, also SN and MAC, C1E, force install...)

I have 4 HDDs WD Red 3TB with a RAID 5 volume.

 

After installing the DSM (new installation, not migrate option) i was still able to access my files! They were recognized directly in the DSM and also the RAID volume was fine without problems. I was able to write and read from the volume.

 

Just for an information :smile:

 

yes I also experienced same thing, however even after doing C1E and force install it would not find the DSM on the network for some weird reason.I powered on did force install without the 4 HDD plugged into the bays.

 

Then when it came to the DSM no disk found page, I inserted all 4 one by one, and it worked. I did not do migrate, just did new installation like you.

 

Thanks for posting back.

Share this post


Link to post
Share on other sites

Hi,

I have successfully migrated my HP N54L from version 6.0.2 to 6.1.3 15152 and created a step by step guide below which worked for me.

 

First Please read the upgrade tutorial by Polanskiman and this thread!

 

Use this guide at your own risk. I won’t be held responsible for any loss of data or failures that may result in the use of this step by step guide!

 

1.      Backup your data and system configs! You have the full responsibility!!!

2.      Disable C1E setting in bios!!!

3.      Start with the workaround script to copy network drivers at boot to prevent the HP micro server from not getting a network connection and become un-accessible

a.      Create a shared folder called Scripts in volume1

b.      Download the script update_patch.sh by Eduardo

c.      Enable SSH port 22 in Control Panel / Terminal & SNMP

d.      Use Putty to connect to your server log in with your admin account and password. Check that admin password is set.

e.      In Putty to become super user type Sudo –i

f.        Change permissions of your update file, type chmod 0744 /volume1/Scripts/update_patch.sh

g.      Log out, exit putty, disable SSH access

h.      Go to Control Panel / Tasks Scheduler and create a triggered task, select user root and select event boot up and then go to task settings and type in /volume1/Scripts/update_patch.sh and finally enable the task!

4.      Go to Control Panel /Update & Restore and update to DSM 6.1.3-15152

5.      When the server reboots turn it off and unplug your usb stick

6.      Make a backup of your usb stick with image writer

7.      Note VID, PID, mac address and serial of your grub config file of your usb stick

8.      Write with Image writer the loader image file JunsMod102a-test-NICadd.img by Khile to your usb stick

9.      Update the grub config file of your usb stick with VID, PID, serial number and mac address

10.   Update the GRUB_VER file of your usb stick with DSM Version to 15152

11.   Put back the updated USB stick to your server and start the server

12.   Start Synology assistant to check when the server comes online, if it does not come online wait about 15 minutes for the update_patch script to run and to copy the network files to the right folder after that is done it will reboot. Mine rebooted twice however my server always needs to be turned off at boot as it does not reboot the usb stick for some reason.

 

If your migration does not work out for some reason you can reinstall by pulling out all the hard disks from the server and select forced install, when the server appears in the Synology assistant insert the hard disks and install fresh.

Edited by ejt01
  • Like 4

Share this post


Link to post
Share on other sites
On 17/7/2017 at 3:51 PM, pehun said:

Sorry for my english faults

:smile:

Thanks for the procedure.

But at witch moment you plug a usb key with the new loader?

At the reboot?

 

Bruno

No need to change loader. You keep Khile's one as before. You simply update from DSM UI keeping all your data and configuration untouched.

Share this post


Link to post
Share on other sites
Hi,
I have successfully migrated my HP N54L from version 6.0.2 to 6.1.3 15152 and created a step by step guide below which worked for me.
 
First Please read the upgrade tutorial by Polanskiman and this thread!
 
Use this guide at your own risk. I won’t be held responsible for any loss of data or failures that may result in the use of this step by step guide!
 
1.      Backup your data and system configs! You have the full responsibility!!!
2.      Disable C1E setting in bios!!!
3.      Start with the workaround script to copy network drivers at boot to prevent the HP micro server from not getting a network connection and become un-accessible
a.      Create a shared folder called Scripts in volume1
b.      Download the script update_patch.sh by Eduardo
c.      Enable SSH port 22 in Control Panel / Terminal & SNMP
d.      Use Putty to connect to your server log in with your admin account and password. Check that admin password is set.
e.      In Putty to become super user type Sudo –i
f.        Change permissions of your update file, type chmod 0744 /volume1/Scripts/update_patch.sh
g.      Log out, exit putty, disable SSH access
h.      Go to Control Panel / Tasks Scheduler and create a triggered task, select user root and select event boot up and then go to task settings and type in /volume1/Scripts/update_patch.sh and finally enable the task!
4.      Go to Control Panel /Update & Restore and update to DSM 6.1.3-15152
5.      When the server reboots turn it off and unplug your usb stick
6.      Make a backup of your usb stick with image writer
7.      Note VID, PID, mac address and serial of your grub config file of your usb stick
8.      Write with Image writer the loader image file JunsMod102a-test-NICadd.img by Khile to your usb stick
9.      Update the grub config file of your usb stick with VID, PID, serial number and mac address
10.   Update the GRUB_VER file of your usb stick with DSM Version to 15152
11.   Put back the updated USB stick to your server and start the server
12.   Start Synology assistant to check when the server comes online, if it does not come online wait about 15 minutes for the update_patch script to run and to copy the network files to the right folder after that is done it will reboot. Mine rebooted twice however my server always needs to be turned off at boot as it does not reboot the usb stick for some reason.
 
If your migration does not work out for some reason you can reinstall by pulling out all the hard disks from the server and select forced install, when the server appears in the Synology assistant insert the hard disks and install fresh.

Thanks for the tutorial. Do we always leave the scheduled task enabled - so it runs every boot or can it be disabled once 15152 is working? Thanks.

Share this post


Link to post
Share on other sites
3 hours ago, neotronic said:


Thanks for the tutorial. Do we always leave the scheduled task enabled - so it runs every boot or can it be disabled once 15152 is working? Thanks.

According to Eduardo's post  you can have it enabled, I have disabled it, but I will enabled it again prior to the next update.

  • Like 1

Share this post


Link to post
Share on other sites

You can leave the task enabled. It will check if needs to copy and reboot. Only if needed. This way you won't forget when updating.

  • Like 1

Share this post


Link to post
Share on other sites
On 2017/7/19 at 10:33 PM, ejt01 said:

Hi,

I have successfully migrated my HP N54L from version 6.0.2 to 6.1.3 15152 and created a step by step guide below which worked for me.

 

First Please read the upgrade tutorial by Polanskiman and this thread!

 

Use this guide at your own risk. I won’t be held responsible for any loss of data or failures that may result in the use of this step by step guide!

 

1.      Backup your data and system configs! You have the full responsibility!!!

2.      Disable C1E setting in bios!!!

3.      Start with the workaround script to copy network drivers at boot to prevent the HP micro server from not getting a network connection and become un-accessible

a.      Create a shared folder called Scripts in volume1

b.      Download the script update_patch.sh by Eduardo

c.      Enable SSH port 22 in Control Panel / Terminal & SNMP

d.      Use Putty to connect to your server log in with your admin account and password. Check that admin password is set.

e.      In Putty to become super user type Sudo –i

f.        Change permissions of your update file, type chmod 0744 /volume1/Scripts/update_patch.sh

g.      Log out, exit putty, disable SSH access

h.      Go to Control Panel / Tasks Scheduler and create a triggered task, select user root and select event boot up and then go to task settings and type in /volume1/Scripts/update_patch.sh and finally enable the task!

4.      Go to Control Panel /Update & Restore and update to DSM 6.1.3-15152

5.      When the server reboots turn it off and unplug your usb stick

6.      Make a backup of your usb stick with image writer

7.      Note VID, PID, mac address and serial of your grub config file of your usb stick

8.      Write with Image writer the loader image file JunsMod102a-test-NICadd.img by Khile to your usb stick

9.      Update the grub config file of your usb stick with VID, PID, serial number and mac address

10.   Update the GRUB_VER file of your usb stick with DSM Version to 15152

11.   Put back the updated USB stick to your server and start the server

12.   Start Synology assistant to check when the server comes online, if it does not come online wait about 15 minutes for the update_patch script to run and to copy the network files to the right folder after that is done it will reboot. Mine rebooted twice however my server always needs to be turned off at boot as it does not reboot the usb stick for some reason.

 

If your migration does not work out for some reason you can reinstall by pulling out all the hard disks from the server and select forced install, when the server appears in the Synology assistant insert the hard disks and install fresh.

 

Many thanks for your step by step instruction... I think I will follow it to "upgrade/migrate" mine during the weekend (once ... i THINK im ready).

May I know after the migration, all your existing data can be retrieved, right? 

Also, on your step 4 "Go to Control Panel /Update & Restore and update to DSM 6.1.3-15152", is that mean you don't need to download the file "DSM_DS3615xs_15047.pat" from the first page???

 

Thanks again.

Share this post


Link to post
Share on other sites
2 hours ago, pehun said:

Hello,

 

Where could I get the "workaround script "?

 

Bruno

Hi Bruno, are you joking?

 

On 16/7/2017 at 9:59 PM, Eduardo said:

 

Hi Bruno, 

Sure it is.

For now, I'm using a trick to update without loosing anything. 6.1.3-15152 at the moment. Working flawlessly.

Just created a script to copy modules from /lib/modules/update to /lib/modules and reboot. It only acts when needed.

I attached the script.

I'm a linux newbie. Somebody would improve it, but it is working here.

Instructions:

 

Put it anywhere.

Set X permission to be executable (0744).

Go to scheduled tasks and program it on reboot. Root user.

Go to DSM and update from web UI normally.

 

I set a long time to reboot (720s) for safety reasons. In case of loop, I think is enough to disable the task. So, be patient.

As it only should work when needed, you can leave this task enabled.

I'm not an expert. Please, don't blame me if something fails. :smile:

update_patch.sh

 

Edited by Eduardo

Share this post


Link to post
Share on other sites
3 minutes ago, pehun said:

Sorry, 

I thought it was a different script than yours

 

;)

Share this post


Link to post
Share on other sites

Hi could You tell me how to update the Gub_ver ? i couldn't find it.

Thanks

Share this post


Link to post
Share on other sites
On 7/8/2017 at 5:39 AM, khile said:

I will update to version 1.02b over weekend 

 

Any news on the update to 1.02b?

Share this post


Link to post
Share on other sites
16 hours ago, milo said:

 

Many thanks for your step by step instruction... I think I will follow it to "upgrade/migrate" mine during the weekend (once ... i THINK im ready).

May I know after the migration, all your existing data can be retrieved, right? 

Also, on your step 4 "Go to Control Panel /Update & Restore and update to DSM 6.1.3-15152", is that mean you don't need to download the file "DSM_DS3615xs_15047.pat" from the first page???

 

Thanks again.

If you you have an unused spare harddisk, you could install a testsystem with 6.02 and then make a migration to 6.1.3 to verify / try out the process /new updates before migrating your real system. My data was intact after the migration.  You don't need to download the DSM_DS3615xs_15047.pat file

Share this post


Link to post
Share on other sites

Hi,

Someone can explain me how to modify the GRUB_VER on the USB stick? 

Thanks

Share this post


Link to post
Share on other sites

In Windows 10 use notepad and change the DSM version in the file GRUB_VER. Your USB stick will have 3 partitions and in one of them the GRUB VER file will be located in the root. You may have to turn on view system files in Windows if it is hidden. 

Share this post


Link to post
Share on other sites

Hi, I haven't no grub_ver files on the usb stick .... any idea ? thanks

Share this post


Link to post
Share on other sites

I have a new 1.02b boot image that works for bare metal fresh installs - just tested this today and now running the latest DSM with Update 1 applied. If anyone would like this please let me know. I take no credit for it - I received it from a user in another thread.

Tested on an N54L only on internal NIC.

Share this post


Link to post
Share on other sites
Hi, I haven't no grub_ver files on the usb stick .... any idea ? thanks

If you need an example file let me know.

Share this post


Link to post
Share on other sites
7 hours ago, neotronic said:

I have a new 1.02b boot image that works for bare metal fresh installs - just tested this today and now running the latest DSM with Update 1 applied. If anyone would like this please let me know. I take no credit for it - I received it from a user in another thread.

Tested on an N54L only on internal NIC.

Hi, what is the difference between 1.02b and the one provided on 1st page? Is it simplify the way of the installation? Is it suitable for the upgrade from dsm 6.0 to 6.1? 

Can I have one? Many thx.

Share this post


Link to post
Share on other sites
3 hours ago, milo said:

Hi, what is the difference between 1.02b and the one provided on 1st page? Is it simplify the way of the installation? Is it suitable for the upgrade from dsm 6.0 to 6.1? 

Can I have one? Many thx.

I'm not sure what the differences are other than this shows 1.02b on the boot menu and it seems to support the latest DSM Update 1. Hopefully you can also test and find good results. I've attached the file. I'll be doing some upgrade testing today from DSM 5 and and will feedback asap.

synoboot.img

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.