From DSM_DS3615xs_15284 (6.1.7) Jun's Mod V1.02b to DSM_DS3615xs_25426 (6.2.3)

[Egnos]

Hi all,

a few years ago, to perform some tests, I had installed a "DSM_DS3615xs_15284" (6.1.7) with "Jun's Mod V1.02b" on a Lenovo PC.

In these years of testing it has always worked well and therefore I decided to make it definitive and I would like to update the S.O.

Unfortunately I find it hard to remember all the steps and I would like your advice and help.

 

I saw that a stable DSM is the "DSM_DS3615xs_25426" (6.2.3) version and I believe that correct Loaders is this "Jun's Loader v1.03b DS3615xs"...can you confirm?

On the control panel I am asked to update the DSM to the latest version, I think I understand that I don't have to update it like this...correct?

I think we need to update the S.O. in manual...is there a guide for updating?

 

In this post I saw that updating is not impossible...

 

Can you help me please.

Thanks.

[billat29]

An update to 6.2.3 should be possible with the 1.03b DS3615xs loader. You need to prepare a new USB stick and download 6.2.3 .pat file to your PC and run a manual upgrade.

There isn't a current tutorial, but this method is still valid.

 

There is a tool to help create the USB stick which can be found here:

 

[Egnos]

Thanks @billat29 for the guides.

In the first guide I read:

Quote

Change mac1=0011322CA785 to mac1=[your NIC MAC address #1]. You can also add set mac2=[your NIC MAC address #2] and so on until mac4 if you have multiple NICs. However, this is not necessary.

Which MAC are talking about? To that of the PC with Windows or the one where I will install the DSM?

[billat29]

The MAC of the target machine - i.e. the one you will install DSM on

[Egnos]

How can i find the MAC address of the NAS?

 

Thanks

[billat29]

If its running DSM then info center>network  or if  windows in settings>network

Or you could look at your router's list of devices

or it should be listed in the BIOS of the machine

 

[Egnos]

Hello,

this morning I perform some test connecting only 1 HD with DSM 6.1.7 installed (HD in RAID 1 ...), but unfortunately I was unable to connect to the NAS!

I arrive at the usual intro screen where it invites you to search for the NAS but both using "http://find.synology.com./" or the "Synology Assistant" application cannot find the NAS on the network!

I've tried all sorts of ways:

• change pid and vid
• change BIOS settings (settings that work fine with 1.02b ...)
• changed USB stick
• changed usb port

Nothing to do!

 

 

These are the technical features of my PC

 

I don't understand why everything works perfectly with loader 1.02b and instead with 1.03b no ... !!😭
Some advice?

 

Thanks

Edited December 10, 2021 by Egnos

[billat29]

What I can say is that 6.1.7 is the version that supports the widest range of hardware and that there isn't anything magical in 6.2.3.

It could be that the 1.03b loader doesn't have the driver for the nic on your PC. I did a search on the forum and found these. I don't know whether it is worth reviewing the second link as I think he says that he got it to work.

 

 

[Egnos]

What really changes from 6.1.7 to 6.2.3?

In any case, before filling the NAS I would like to try an update.

I ran a linux live to see what kind of network card is installed.

Command “lspci -k”:

knoppix@Microknoppix:~$ sudo lspci -k
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09)
	Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller
	Kernel driver in use: ivb_uncore
	Kernel modules: ie31200_edac
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port (rev 09)
	Kernel driver in use: pcieport
00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)
	Subsystem: Lenovo Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller
	Kernel driver in use: i915
	Kernel modules: i915
00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller (rev 04)
	Subsystem: Lenovo 7 Series/C210 Series Chipset Family USB xHCI Host Controller
	Kernel driver in use: xhci_hcd
00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset Family MEI Controller #1 (rev 04)
	Subsystem: Lenovo 7 Series/C216 Chipset Family MEI Controller
	Kernel driver in use: mei_me
	Kernel modules: mei_me
00:16.3 Serial controller: Intel Corporation 7 Series/C210 Series Chipset Family KT Controller (rev 04)
	Subsystem: Lenovo 7 Series/C210 Series Chipset Family KT Controller
	Kernel driver in use: serial
	Kernel modules: 8250_pci
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (rev 04)
	Subsystem: Lenovo 82579LM Gigabit Network Connection (Lewisville)
	Kernel driver in use: e1000e
	Kernel modules: e1000e
00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #2 (rev 04)
	Subsystem: Lenovo 7 Series/C216 Chipset Family USB Enhanced Host Controller
	Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04)
	Subsystem: Lenovo 7 Series/C216 Chipset Family High Definition Audio Controller
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel
00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB Enhanced Host Controller #1 (rev 04)
	Subsystem: Lenovo 7 Series/C216 Chipset Family USB Enhanced Host Controller
	Kernel driver in use: ehci-pci
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a4)
00:1f.0 ISA bridge: Intel Corporation Q77 Express Chipset LPC Controller (rev 04)
	Subsystem: Lenovo Q77 Express Chipset LPC Controller
	Kernel driver in use: lpc_ich
	Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] (rev 04)
	Subsystem: Lenovo 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode]
	Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus Controller (rev 04)
	Subsystem: Lenovo 7 Series/C216 Chipset Family SMBus Controller
	Kernel driver in use: i801_smbus
	Kernel modules: i2c_i801
01:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
	Subsystem: Intel Corporation PRO/1000 PT Dual Port Server Adapter
	Kernel driver in use: e1000e
	Kernel modules: e1000e
01:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06)
	Subsystem: Intel Corporation PRO/1000 PT Dual Port Server Adapter
	Kernel driver in use: e1000e
	Kernel modules: e1000e

 

Command “sudo lspci -k | grep 'Kernel driver'”:

knoppix@Microknoppix:~$ sudo lspci -k | grep 'Kernel driver'
	Kernel driver in use: ivb_uncore
	Kernel driver in use: pcieport
	Kernel driver in use: i915
	Kernel driver in use: xhci_hcd
	Kernel driver in use: mei_me
	Kernel driver in use: serial
	Kernel driver in use: e1000e
	Kernel driver in use: ehci-pci
	Kernel driver in use: snd_hda_intel
	Kernel driver in use: ehci-pci
	Kernel driver in use: lpc_ich
	Kernel driver in use: ahci
	Kernel driver in use: i801_smbus
	Kernel driver in use: e1000e
	Kernel driver in use: e1000e

 

 

Is it supported by loader 1.03b?

 

Thanks.

[flyride]

5 hours ago, Egnos said:

Hello,

this morning I perform some test connecting only 1 HD with DSM 6.1.7 installed (HD in RAID 1 ...), but unfortunately I was unable to connect to the NAS!

I arrive at the usual intro screen where it invites you to search for the NAS but both using "http://find.synology.com./" or the "Synology Assistant" application cannot find the NAS on the network!

I've tried all sorts of ways:

• change pid and vid
• change BIOS settings (settings that work fine with 1.02b ...)
• changed USB stick
• changed usb port

 

Did you set CSM (Legacy Boot) mode?  That is a difference with 3615xs/3617xs on 1.03b versus 1.02b and is required with the 36xx/1.03b combination.

[Egnos]

17 hours ago, flyride said:

 

Did you set CSM (Legacy Boot) mode?  That is a difference with 3615xs/3617xs on 1.03b versus 1.02b and is required with the 36xx/1.03b combination.

 

When I select LEGACY/CSM in the BIOS,  the pc is unable to boot from the key, it does so only in UEFI mode.
In Legacy mode it seems not to find an S.O.
To write the key I use the SW provided "XPENOLOGY TOOL V1.4.2":
- Win32DiskImager but it gives me an error while writing
- RUFUS is able to write in "destination system" there is an immutable field "UEFI (not CSM)".
- USB IMAGE TOOL manages to write but can't find settings on LEGACY, UEFI, CSM...

 

Below are some photos of when selecting LEGACY in the BIOS:

 

 

 

The "Intro" screen appears only if I select UEFI mode in the BIOS, but I still can't find the NAS on the network ...

 

Any other suggestions?

 

Thank you all.

Edited December 11, 2021 by Egnos

[IG-88]

3 hours ago, Egnos said:

Below are some photos of when selecting LEGACY in the BIOS:

 

cant see any but beside booting up with active csm you also need to use the "non uefi" boot device from the list, there are usually 2 uefi for every partition of the usb and the 3rd usb entry looking different will be the one for csm

csm is only a option and when choosing a uefi boot device then the option is not used

also keep in mind that usually you need to boot up with csm already active, so look for the device in question on 2nd boot in bios

Edited December 11, 2021 by IG-88

[Egnos]

3 hours ago, IG-88 said:

 

cant see any but beside booting up with active csm you also need to use the "non uefi" boot device from the list, there are usually 2 uefi for every partition of the usb and the 3rd usb entry looking different will be the one for csm

csm is only a option and when choosing a uefi boot device then the option is not used

also keep in mind that usually you need to boot up with csm already active, so look for the device in question on 2nd boot in bios

Sorry i didn't understand where i should find "NON UEFI" boot device. In the BIOS or when I write the USB stick?

[Egnos]

Can someone help me?

I am attaching the screenshots of the BIOS:

 

@IG-88Looking at the screenshots, what should I still change in the BIOS?

 

 

 

Edited December 12, 2021 by Egnos

[flyride]

What you have shown looks correct to me.  You should not have or need the SATA disk in the boot sequence though.

 

The one thing that catches my eye, is that your system continues to try a network boot.  I would attempt to disable that.  Often in PCI settings or hardware device options.

 

Also, you might try a different USB key, or create the key from scratch if BIOS changes have occurred.  

[Egnos]

@flyridemany thanks for your answer.

I ask you the courtesy to check my Hw configuration above in the discussion because, in addition to the ethernet port on the motherboard, I also have a PCI card with two Ethernet ports (I don't understand the model...).  

Which one do you think is better to use?

Edited December 13, 2021 by Egnos

[flyride]

8 minutes ago, Egnos said:

in addition to the ethernet port on the motherboard, I also have a PCI card with two Ethernet ports (I don't understand the model...).  

Which one do you think is better to use?

 

There isn't enough information to make a decision about this.  You will need to provide information about the add-in PCI card in order for someone to offer an opinion about it.

 

Based on the M92p specs I can't see a reason that the onboard NIC is not suitable for DSM however. In general if you are troubleshooting hardware, it is best to simplify the environment and get things working first, which might encourage me to remove the PCI card, at least for now.

[Egnos]

20 hours ago, flyride said:

What you have shown looks correct to me.  You should not have or need the SATA disk in the boot sequence though.

 

The one thing that catches my eye, is that your system continues to try a network boot.  I would attempt to disable that.  Often in PCI settings or hardware device options.

 

Also, you might try a different USB key, or create the key from scratch if BIOS changes have occurred.  

I'll do some more tests tonight. I keep you updated.

Which tool to write the USB stick do you recommend (Win32DiskManager does't work...)?

Might the BIOS need to be updated?

 

Thank you

Edited December 14, 2021 by Egnos

[Kamele0N]

Reinstall it (win32diskmannager)....sometimes just quits working! 

[Egnos]

I have finally taken a step forward!
I updated the BIOS and finally the USB key started in Legacy / CSM!
I can find the NAS on the network.

 

But unfortunately I have another problem🤬
At this point I am offered two options:

• Migration
• Re-installation

I select migration, manual installation and on browse I select locally the downloaded .pat "DSM_DS3615xs_25426.pat".

Arrived at 56% of the installation I get this error: ”Failed to install the file. The file is probably corrupted. (13) ".

 

 

I have already tried to re-download .pat and change the update version. 
VID and PID seem correct to me, what should I do now?

 

21 hours ago, Kamele0N said:

Reinstall it (win32diskmannager)....sometimes just quits working! 

I found that the "Win32DiskImager-0.9.5" version runs in Win10 but version 1.0.0 not.... 

[Kamele0N]

Its usually because your USBs VID/PID numbers dont match those in grub.cfg. You would find that answer if you  entered Failed to install the file. The file is probably corrupted. (13) into forums searchbar!!!!!

 

 

 

Edited December 15, 2021 by Kamele0N

[Egnos]

@Kamele0N thank you very much!!

But I have already explored the forum for a long time before posting the problem!

I have checked VID / PID many times and they seem correct to me.

 

Is there anything else that can generate this error?

 

Thanks

[IG-88]

maybe try to boot a live/rescue linux and post what "lsusb" shows up and also your grub.cfg

 

also the uefi and non-uefi usb boot option (of the same usb device) might look like this

the 2nd marked is the non-uefi and would result in csm mode when used for booting

[Egnos]

I am trying to use the card reader (Realtek Semiconductor Corp. RTS5182 Card Reader) placed on the front of the PC.

With 1.02b works perfectly, with 1.03b it gives me error 13 during installation

knoppix@Microknoppix:~$ lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 0bda:0184 Realtek Semiconductor Corp. RTS5182 Card Reader
Bus 001 Device 004: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 Optical USB Mouse]
Bus 001 Device 003: ID 0951:1666 Kingston Technology DataTraveler G4
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 03f0:0324 Hewlett-Packard SK-2885 keyboard
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
knoppix@Microknoppix:~$ 

 

grub.cfg

if serial --port=0x3F8 --speed=115200;then
        set has_serial=true
        terminal_input --append serial
        terminal_output --append serial
else
        clear
fi

terminal_input --append console
terminal_output --append console

if [ x"${grub_platform}" = xefi ]; then
        insmod efi_gop
        insmod efi_uga
else
        insmod vbe
fi

set extra_initrd="extra.lzma"
set info="info.txt"

set vid=0x0bda
set pid=0x0184
set sn=1230LWN018548
set mac1=0011322CA785
set rootdev=/dev/md0
set netif_num=1
set extra_args_3615=''
#set extra_args_3615='earlycon=uart8250,io,0x3f8,115200n8 earlyprintk loglevel=15'

set common_args_3615='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet syno_port_thaw=1'

set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0'

set default='0'
set timeout='4'
set fallback='1'

if [ -s $prefix/grubenv ]; then
        load_env
        if [ -n "$saved_entry" ]; then
                set default="${saved_entry}"
        fi
fi

VERSION="with Jun's Mod v1.03b"

search --file -s /bzImage

function savedefault {
        if [ -s $prefix/grubenv  ]; then
                saved_entry="${chosen}"
                save_env saved_entry
        fi
}

function do_option {
        if [ $# -lt 2 ]; then
                eval "set value=\"\$$1\""
                echo "current $1: $value"; return;
        fi
        set key=$1
        shift
        set $key="$*"
        if [ -s $prefix/grubenv  ]; then
                save_env $key
        fi
}

function vid { do_option vid $@; }
function pid { do_option pid $@; }
function sn { do_option sn $@; }
function mac1 { do_option mac1 $@; }
function mac2 { do_option mac2 $@; }
function mac3 { do_option mac3 $@; }
function mac4 { do_option mac4 $@; }
function rootdev { do_option rootdev $@; }
function append { do_option extra_args_3615 $@; }

function vidpid {
        if [ $# -lt 2 ]; then
                echo "usage: vidpid 0xVVVV 0xPPPP"; return;
        fi
        set usb_args="vid=$1 pid=$2"
        if [ -s $prefix/grubenv  ]; then
                save_env usb_args
        fi
}

function showtips {
        if [ -n "$has_serial" ]; then
                terminal_output --remove serial
        fi
        echo "Screen will stop updating shortly, please open http://find.synology.com to continue."
        echo
        echo
        if [ -n "$has_serial" ]; then
                terminal_output --append serial
        fi
}

function loadinitrd {
        if [ -s $img/$info ]; then
                if [ -n "$has_serial" ]; then
                        terminal_output --remove serial
                fi
                cat $img/$info
                if [ -n "$has_serial" ]; then
                        terminal_output --append serial
                fi
        fi
#        if [ -s $img/$extra_initrd ]; then
#                initrd $img/rd.gz $img/$extra_initrd
#        else
#                initrd $img/rd.gz
#        fi
}

function common_add_option {
        eval "set value=\"\$$1\""
        if [ -z $value ]; then return 1; fi
        set common_args="$common_args $1=$value"
}

function common_add_option_ex {
        eval "set value=\"\$$1\""
        if [ -z $value ]; then return 1; fi
        set common_args="$common_args $2=$value"
}

function loadlinux {
        set model=$1
        set bootdev=$2
        shift 2
        if [ -n $vid -a -n $pid ]; then
                set usb_args="vid=$vid pid=$pid"
        fi
        eval "set common_args=\"\$common_args_$model\""
        eval "set extra_args=\"\$extra_args_$model\""
        eval "set bootdev_args=\"\$${bootdev}_args\""
        common_add_option_ex rootdev root
        common_add_option sn
        if common_add_option mac1; then set netif_num=1; fi
        if common_add_option mac2; then set netif_num=2; fi
        if common_add_option mac3; then set netif_num=3; fi
        if common_add_option mac4; then set netif_num=4; fi
        common_add_option netif_num
	if [ -z $zImage ]; then
		set zImage=bzImage
	fi
        linux $img/$zImage $common_args $bootdev_args $extra_args $@
}

menuentry "DS3615xs 6.2 Baremetal $VERSION" --class os {
        set img=
        savedefault
        loadlinux 3615 usb
        loadinitrd
        showtips
}

menuentry "DS3615xs 6.2 Baremetal $VERSION Reinstall" --class os {
        set img=
        loadlinux 3615 usb mfg
        loadinitrd
        showtips
}

#menuentry "DS3615xs 6.2 Baremetal AMD $VERSION" --class os {
#        set img=
#        set zImage=bzImage
#        savedefault
#        loadlinux 3615 usb
#        loadinitrd
#        showtips
#}

menuentry "DS3615xs 6.2 VMWare/ESXI $VERSION" --class os {
        set img=
        savedefault
        loadlinux 3615 sata
        loadinitrd
        showtips
}

 

 

 

Edited December 16, 2021 by Egnos

[IG-88]

yes you are right, looks ok for the usb vid/pid of the card reader

as you already have a "Kingston Technology DataTraveler G4", maybe try this one instead of the card reader

i know the hpe microserver have a reader too and they work with dsm so its not a general problem,