[Downgrade from DSM 6.0]

On 5/19/2017 at 6:27 AM, A.S._id said:

If you can't even access to NAS, you can extract HDDs from device, connect to BB (any os, the same download NAS via boot flash with ubuntu installer), open HDDs any disk editor and format the first partition from start of disk on every HDD. Then assistant to show "not installed" and you can install DSM at zero.

 

Remove all but 1 drive incase you screw something up, boot into Ubuntu live USB - mount the system partition and edit the /etc.defaults/version file - save your changes and reboot.

 

Synology assistant or find.synology.com should detect the NAS as migrateable and you can then select the PAT file to install.

 

I was stupid and upgraded to 6.0.3 on my N54L and had to use this to recover.

 

Once the system has started, it will detect the system partitions are damaged on the other drives - so you need to click the Repair option but thats about it - no data loss.

[DSM 6.1.x Loader]

2 hours ago, jun said:

Sorry, fixed

 

Would you be able to produce a build for AMD N54L please - the experimental version you did for 1.01 worked so would it be possible to apply them to your new loader?

 

If not could you provide more information on what you did to produce that loader so we can look at spinning our own release?

[DSM 6.1.x Loader]

hi all,

I am currently running 5.2 on my hp n54l baremetal. May i ask does this loader support my n54l? becoz when i try to upgrade to 6.0 with this loader. I couldnt find my server through synology assistant, neither on the web or the software. i followed the instructions, changed my usb PID. I saw the lan socket is blinking on both sides, but it seems there is no IP given to my server.is it the lan driver problem?

Thanks in advance.

 

Stay where you are, i had DSM 6 when it was supported on N54L, had some issues with it.

 

If you want to try nevertheless, try with some other hard disk and usb boot drive and always have a backup!

 

Now i'm back at DSM 5, perfectly happy with it because everything works as it should be

 

DSM 6.0 works fine here on N54L - been running the original loader since Jun released the loader.

 

Haven't had any issues although I am hoping for a 6.1 build compat with it

[DSM 6.1.x Loader]

Any experience with 6.1.1 u2 on AMD E350-M1 ? I have DSM5 running on that system. I would like to reinstall to the latest DSM6.

 

Mine is working smooth for a week on AMD E350-M1-I: bare metal installation with 6.1.1 (downloaded directly from synology) + juno's 1.02a DS3615xs.

Had some troubles with ethernet after the update done keeping DSM settings.

Solved selecting the force install option and doing a clean install (you will lose settings of DMS but not data).

Update 2 installed by DSM web interface.

 

Any experience with HP N54L?

Does it work since the beginning of 6.1, or is recent?

 

thanks

 

6.1 isn't working on N54L using 1.02a2 loader I'm afraid at this time

[@eaDir in DSM 6.0]

Because having it plays havoc with some web apps that auto load includes?

[DSM 6.1.x Loader]

I'm using Juns AMD image on a N54L with no issue.

 

My Mellanox card also works great - thanks for your hard work

[DSM 6.1.x Loader]

I can't post a log as there is no SSH access however the N54L appears to freeze during/after PCI enumeration which would explain why nobody can find the device on Synology Assistant or on their network.

 

I was looking for a core dump or something to pinpoint where it was failing but nothing obvious stood out, the below is all I found out.

 

Last messages in the boot process are similar to the below:

 

[ 0.193677] NET: Registered protocol family 2

[ 0.194016] TCP established hash table entries: 65536 (order: 7, 524288 bytes)

[ 0.194303] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)

[ 0.194726] TCP: Hash tables configured (established 65536 bind 65536)

[ 0.194791] TCP: reno registered

[ 0.194799] UDP hash table entries: 4096 (order: 5, 131072 bytes)

[ 0.194869] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)

[ 0.194985] NET: Registered protocol family 1

 

Prints a couple lines like:

 

[ 0.193611] pci_bus 0000:02: resource 0 [io 0xc000-0xcfff]

[ 0.193612] pci_bus 0000:02: resource 1 [mem 0xfe600000-0xfe7fffff]

[ 0.193613] pci_bus 0000:02: resource 2 [mem 0xfe000000-0xfe1fffff 64bit pref]

 

then freezes

The synology kernel do not have AMD CPU support compiled in, so it is expected that AMD box can not run properly.

Adding support requires a full recompilation from source or some non-trivial patch to the synology kernel, both solution has its own difficulties.

I personally does not have the hardware, so It may be a long wait before something positive happens.

 

Might be worth putting a big notice in the original thread so N54L/AMD users know this as originally people suspected that it was just due to missing network card drivers as opposed to the system not booting,

[DSM 6.1.x Loader]

I can't post a log as there is no SSH access however the N54L appears to freeze during/after PCI enumeration which would explain why nobody can find the device on Synology Assistant or on their network.

 

I was looking for a core dump or something to pinpoint where it was failing but nothing obvious stood out, the below is all I found out.

 

Last messages in the boot process are similar to the below:

 

[ 0.193677] NET: Registered protocol family 2

[ 0.194016] TCP established hash table entries: 65536 (order: 7, 524288 bytes)

[ 0.194303] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)

[ 0.194726] TCP: Hash tables configured (established 65536 bind 65536)

[ 0.194791] TCP: reno registered

[ 0.194799] UDP hash table entries: 4096 (order: 5, 131072 bytes)

[ 0.194869] UDP-Lite hash table entries: 4096 (order: 5, 131072 bytes)

[ 0.194985] NET: Registered protocol family 1

 

Prints a couple lines like:

 

[ 0.193611] pci_bus 0000:02: resource 0 [io 0xc000-0xcfff]

[ 0.193612] pci_bus 0000:02: resource 1 [mem 0xfe600000-0xfe7fffff]

[ 0.193613] pci_bus 0000:02: resource 2 [mem 0xfe000000-0xfe1fffff 64bit pref]

 

then freezes

[DSM 6.1.x Loader]

Could you also include the following for Mellanox cards?

 

[ 4.126061] mlx4_core: Mellanox ConnectX core driver v1.1 (Dec, 2011)

[ 6.564021] mlx4_en: Mellanox ConnectX HCA Ethernet driver v2.0 (Dec 2011)

 

Would make me super happy

[XPEnology Developers contact me for 7393 kernel src code]

Is it the kernel source or just the toolchain?

[Just for info on QNAP firmware]

Extracting/Mounting the root FS appears to be handled by /etc/rcS.d/S30mountall

 

You can see where they have coded the expected device names

 

Upon correcting this, the libc errors will disappear and the system will bring up services when you run the init, however my network devices aren't present which is an issue

Hi, thanks for hint, but as you saw there are two file that seems to be rootfs

 

I'm not sure what you are asking here? If you look at the mount script, it shows the extraction of both rootfs files and their location.

[Just for info on QNAP firmware]

Extracting/Mounting the root FS appears to be handled by /etc/rcS.d/S30mountall

 

You can see where they have coded the expected device names

 

Upon correcting this, the libc errors will disappear and the system will bring up services when you run the init, however my network devices aren't present which is an issue