synogeek

HP N54L - DSM 6.1 onwards

Recommended Posts

Problem Solved.

I started a fresh installed XPEnology and attached the hard disk from my old.

The Synology recognized the RAID/Volume and repaired it.

 

But I have still another problem.

I can't install updates.

I get the error: connection failed. Check your Internet connection.

The Internet is working on the system. I can install Pakeges.

If I try to ping update.synology.com or www.google.de from the consol i get "ping: www.google.de: Temporary failure in name resolution"

 

Can some one help me?

 

 

Share this post


Link to post
Share on other sites
Hi,
I have a N54L with DSM 6.1.3, but WOL doesn't work anymore.
 I have problems with the Mac and Serial.
 
Schould I use the Mac from my N54L networkcard?
But how can I generate a serial, which fits?
 
Or can I choose any Mac an Serial by the generator?
Schould i flash my Networkcard after that ?
 
I only want to start the NAS by Magic Packet, over the fritzbox.

Did you upgrade or clean install?

Share this post


Link to post
Share on other sites

Upgrade from 6.0.2 to new Version worked like a charme after reading a bit here.

 

Thank you very much! :smile:

  • Like 1

Share this post


Link to post
Share on other sites
On 10/08/2017 at 7:48 PM, mape said:

Hi,

 

Schould I use the Mac from my N54L networkcard?

But how can I generate a serial, which fits?

 

No. I used a MAC address from a vaild synology system and generated a new mac/sn pair:

google if you want know how this is done.

 

 

Quote

Or can I choose any Mac an Serial by the generator?

Schould i flash my Networkcard after that ?

 

I just edited the grub.conf to hold the new information. So no flashing the networkcard on my side.

 

Quote

I only want to start the NAS by Magic Packet, over the fritzbox.

 

Since my nas is always on, I've never used WOL. Hope it will for you.

Edited by martva

Share this post


Link to post
Share on other sites

Migration done with jun's standard loader, C1E desactivated, grub file modified with pid/vid/sn/mac, not the sataport... it works the first time with 5 disks on a n54L!

Thanks for all the tips!

:smile:

 

  • Like 1

Share this post


Link to post
Share on other sites

Ran a test today on N54L with NC360T, 

 

Installed using Broadcom On-Board Nic

DSM 6.1-15047

Setup JBOD Btrfs

Works fine, I can see 3 Network Connections

 

Now the big mystery

In the control Panel it showed DSM 6.1.3-15152  is available

So I ran the update. It goes thru the ten minute thing and then says use Synology Assistant to find the box.

 

Now I can only see two ip's from the NC360T. I connect to one of those and access the N54L

It now has DSM 6.1.3-15152 but only 2 Network Connections.   The On-board Broadcom Network Connection is gone......

Share this post


Link to post
Share on other sites

I tried to install latest Jun build on my N54L under spare boot drive. Everything works well except my raid unit attached to 3ware 9xxx raid card is not available under DSM. Do I need to replace the extra.lzma in order to get it recognized?

Edited by Walechan

Share this post


Link to post
Share on other sites

There is no problem with WOL, I had to copy the attached script to "/usr/local/etc/rc.d" same I did in DSM 5.2 and versions before and enable WOL in control panel "hardware and power" section, it works fine.

S99ZZZ_Shutdown.sh

Edited by synook
  • Like 1

Share this post


Link to post
Share on other sites
1 hour ago, Messenger said:

  rc.d not existing is it the same like rc.sysv?

found it my fault thx will test it later

 

Share this post


Link to post
Share on other sites
On 05/07/2017 at 0:40 AM, Toetje583 said:

Guys with memory problems add this to the grub.cfg

disable_mtrr_trim

Example: 
 


set common_args_3617='disable_mtrr_trim syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3617xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_port_thaw=1'

Now I got:

                   total        used        free
Mem:          16034         260       15458           3         315       15560
Swap:         11665           0       11665


/proc/mtrr is editable even from a command shell: you can disable register records and/or write new values there this seems to be a Bios bug.
Adding disable_mtrr_trim disables it without losing any performance as far as I know.

 

Thank you for this great tip ! It's now working fine on my baremetal N54L !

 

However I suspect that DSM would be able to use the amount of RAM reserved for graphic card purposes (specified in the BIOS) which could lead to some issues ?

It may be safer to buy a dedicated graphic card ? :(

Edited by moimoimoi

Share this post


Link to post
Share on other sites
20 hours ago, synook said:

There is no problem with WOL, I had to copy the attached script to "/usr/local/etc/rc.d" same I did in DSM 5.2 and versions before and enable WOL in control panel "hardware and power" section, it works fine.

S99ZZZ_Shutdown.sh

 

can u explain how u exactly did it?

 

with winscp i cannot verify with root and with admin i ve got permission denied to copy in this share.

with putty i can login with admin and switch to root with "sudo -i" but i don´t know how to copy.

Edited by Messenger

Share this post


Link to post
Share on other sites

Jun 1.02b (native) does not work with my N54L. Khiles JunsMod102a-test-NICadd works flawless. But when booting from an usb stick with native Jun 1.02b my N54L is in a boot loop (cryptic screen). Server-Hardware not changed; C1E disabled.

¯\_(ツ)_/¯

 

 

Gesendet von iPad mit Tapatalk Pro

 

Share this post


Link to post
Share on other sites

ok i´ve got wol working:

 

start putty

login as admin

sudo -i
cd /usr/local/etc/rc.d
vi S99ZZZ_Shutdown.sh

paste the commands from the scipt with copy and paste:

#!/bin/sh
case $1 in
start)
 if [ -f /var/packages/shutdown_script/DSShutdown.sh ]; then
  /var/packages/shutdown_script/DSShutdown.sh &
 fi
    ;;
stop)
 if [ -f /var/tmp/shut.down ]; then
  rm /var/tmp/shut.down
 fi
 ifconfig eth0 down
    ;;
*)
    echo "Usage: $0 [start|stop]"
    ;;
esac

then save with: wq!

chmod 755 S99ZZZ_Shutdown.sh

the wol is working again

  • Like 1

Share this post


Link to post
Share on other sites
On 8/25/2017 at 6:36 PM, Messenger said:

ok i´ve got wol working:

 

start putty

login as admin


sudo -i
cd /usr/local/etc/rc.d
vi S99ZZZ_Shutdown.sh

paste the commands from the scipt with copy and paste:


#!/bin/sh
case $1 in
start)
 if [ -f /var/packages/shutdown_script/DSShutdown.sh ]; then
  /var/packages/shutdown_script/DSShutdown.sh &
 fi
    ;;
stop)
 if [ -f /var/tmp/shut.down ]; then
  rm /var/tmp/shut.down
 fi
 ifconfig eth0 down
    ;;
*)
    echo "Usage: $0 [start|stop]"
    ;;
esac

then save with: wq!


chmod 755 S99ZZZ_Shutdown.sh

the wol is working again

Working for me now again, but I don´t understand why.. The file /var/packages/shutdown_script/DSShutdown.sh which the script is looking for to execute doesn´t exist in my system but still it works now like charm.. Anyone know why this script is working?! :grin:

Share this post


Link to post
Share on other sites
On 19.7.2017 at 4: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.

Unfortunately I can't find such thing as triggered task in DSM 5.2. Is it a new feature in DMS 6.x?

Any ideas how to deal with the update_patch.sh script in DSM 5.2?

Share this post


Link to post
Share on other sites

The link of the loader in the first page seems off.

 

Anyone can help to re-upload it?

Share this post


Link to post
Share on other sites
On 8/25/2017 at 6:36 PM, Messenger said:

ok i´ve got wol working:

 

...


chmod 755 S99ZZZ_Shutdown.sh

the wol is working again

 

or just copy somewhere the file I attached let say to

/volume1/private/S99ZZZ_Shutdown.sh

login via SSH putty

sudo su -i
cp /volume1/private/S99ZZZ_Shutdown.sh /usr/local/etc/rc.d/
chmod 755 /usr/local/etc/rc.d/S99ZZZ_Shutdown.sh

Don't ask me why it works, I found it here in forum years ago and just reused again ;-)

Share this post


Link to post
Share on other sites

Hello, regarding WOL, did you also have to modify the synoinfo.conf file, as explained in this S99ZZZ_Shutdown.sh how-to?

I'm not using the same hardware (asrock Q1900-itx) but my WOL isn't working and I'm trying to understand why. Thank you for your help!

Share this post


Link to post
Share on other sites
20 minutes ago, pmchan said:

Hello, regarding WOL, did you also have to modify the synoinfo.conf file, as explained in this S99ZZZ_Shutdown.sh how-to?

I'm not using the same hardware (asrock Q1900-itx) but my WOL isn't working and I'm trying to understand why. Thank you for your help!

on n54l you didn´t have to modify.

  • Like 1

Share this post


Link to post
Share on other sites

Hello,

Just have a few questions regarding DSM 6.1:

Is the "power schedule" working which can be found in "hardware & power"?
In DSM 5.2 you can only make a scheduled power off cause it always writes to the bios!

When I migrate from 5.2 to 6.1 will it still be possible to attach more than 4 HDDs?

Do I need the Loader from the first page in this thread or did you just go through the "Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)"  and just used the 1.02b Loader and DSM 6.1??

 

Thanks for helping!

Share this post


Link to post
Share on other sites
54 minutes ago, aundroid said:

Hello,

Just have a few questions regarding DSM 6.1:

Is the "power schedule" working which can be found in "hardware & power"?
In DSM 5.2 you can only make a scheduled power off cause it always writes to the bios!

When I migrate from 5.2 to 6.1 will it still be possible to attach more than 4 HDDs?

Do I need the Loader from the first page in this thread or did you just go through the "Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)"  and just used the 1.02b Loader and DSM 6.1??

 

Thanks for helping!

i´ve got 5 hdd´s in a raid and one single hdd. Just jun´s loader (modified with my mac, sn, vid, pid) with custom bios. no problems ´till now.

Share this post


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