manples

N54L - upgrade from DSM 6.1.7 to 6.2.1?

Recommended Posts

Hi all.
I have the same problem as @sebelec
I recive IP by DHCP, but I can not visualize the interface and therefore I can not make any changes in the configuration of the network card.
Can someone help?
Thank you!

Share this post


Link to post
Share on other sites

@XbladeX 

1 - What hardware are you currently using? 

2 - What bootloader are you using? 

3 - What is your Synology "base" (3615/3617/...)?

4 - Has it been working before?

5 - Did it stop working after an update from 6.1.7 to 6.2.1?

6 - Are you using any "extra.lzma"?

7 - Have you at any time been using any other types of bootloaders? (nanoboot/xpenoboot/...)

 

@sebelec nr. 7 applies to you as well.

Share this post


Link to post
Share on other sites
6 minutes ago, bearcat said:

@XbladeX 

1 - What hardware are you currently using? 

2 - What bootloader are you using? 

3 - What is your Synology "base" (3615/3617/...)?

4 - Has it been working before?

5 - Did it stop working after an update from 6.1.7 to 6.2.1?

6 - Are you using any "extra.lzma"?

7 - Have you at any time been using any other types of bootloaders? (nanoboot/xpenoboot/…)

 

@sebelec nr. 7 applies to you as well.

Hi @bearcat

 

1 - What hardware are you currently using? Hp NL54 Micreoserver

2 - What bootloader are you using? Baremetal Boot 1.3b

3 - What is your Synology "base" (3615/3617/...)? DS3615xs  -Versión -   6.2- 23739

4 - Has it been working before? - Yes, Works fine before, with boot 1.02b-red And 6.1.7 - 15284

5 - Did it stop working after an update from 6.1.7 to 6.2.1? I have Internal NIC and at the momnet I can´t update up to 6.2   -  23739 ( Need Intel NIC for Update 6.2.1)

6 - Are you using any "extra.lzma"? No, Dot use Extra.Izma

7 - Have you at any time been using any other types of bootloaders? (nanoboot/xpenoboot/…) Yes the first Boot used was "XPEnoboot_DS3615xs_5.2-5644.5" in year 2016, in 2017 UPDATE to  synoboot-1.02b and All Works fine, NOW in 2019 i try Update and i have this problem

 

Thank for all!

 

 

Share this post


Link to post
Share on other sites

@XbladeX From earlier experience with a problem like that:

try these steps:

Activate the SSH service in DSM (if not active)
Connect to your NAS with an SSH client (e.g. putty) (or from Win 10, open a cmd window, run : ssh admin@my.nas.ip (replace with the actual IP)
Enter your credentials (user: admin)
Change folder to root (cd /)
Delete the xpenoboot folder (sudo rm -r .xpenoboot)
If the SSH service keeps stopping, you have to be quick.

  • Like 1

Share this post


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

@XbladeX From earlier experience with a problem like that:

try these steps:

Activate the SSH service in DSM (if not active)
Connect to your NAS with an SSH client (e.g. putty) (or from Win 10, open a cmd window, run : ssh admin@my.nas.ip (replace with the actual IP)
Enter your credentials (user: admin)
Change folder to root (cd /)
Delete the xpenoboot folder (sudo rm -r .xpenoboot)
If the SSH service keeps stopping, you have to be quick.

you are the master, many thanks!  Yeahhhhh

I'm really very grateful to you.

Share this post


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

@XbladeX From earlier experience with a problem like that:

try these steps:

Activate the SSH service in DSM (if not active)
Connect to your NAS with an SSH client (e.g. putty) (or from Win 10, open a cmd window, run : ssh admin@my.nas.ip (replace with the actual IP)
Enter your credentials (user: admin)
Change folder to root (cd /)
Delete the xpenoboot folder (sudo rm -r .xpenoboot)
If the SSH service keeps stopping, you have to be quick.

 OMG @bearcat you are amazing !!! it works !!!!!

 

Thank you so much !!! 

Share this post


Link to post
Share on other sites

Hey everybody,

i have an N54L with Boardcom NIC and working DMS 6.2 U2. Now I want to upgrade to 6.2.1. When I am installing the HP NC360T an disable internal NIC do I have to change the (working) grub.cfg? At the moment I am using a fake NIC.

 

Thank you!

Share this post


Link to post
Share on other sites

@thearc Actually, you don't have to change it, the current "MAC1=aabb..." setting will be used for eth0 on your new nic.

Unless your "face" MAC conflicts with your eth1 on the new nic, you should be ok.

  • Thanks 1

Share this post


Link to post
Share on other sites
On 1/14/2019 at 1:40 PM, bearcat said:

@thearc Actually, you don't have to change it, the current "MAC1=aabb..." setting will be used for eth0 on your new nic.

Unless your "face" MAC conflicts with your eth1 on the new nic, you should be ok.

 

Just a quick update. It was very easy, throw in the HP NC360T an disable internal NIC. I did an update with the Webinterface. It works like charm with 6.2.1 U4 :96_ok_hand:

Edited by bab86

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