DSM 6.1.x Loader


Recommended Posts

Hello,

 

I did step by step, but didn't boot from usb. Black screen.

20170421_205401_HDR.jpg

 

 

change

 

ch.jpg

 

What i did wrong?

 

Please help me install 6

You are using the wrong serial number. Don;t use the HP serialnumber but generate a synology one. I can't find the link but it has been posted many times.

You can find it!

Link to post
Share on other sites

OK, I've spent a day on this so I figure I'd share in the hopes that the issue can be fixed and/or I can help someone else with my workaround...

 

setup:

1. I am running an ASRrock C236 WSI mobo that has two builtin 1Gb intel nics (1xi210 and 1xi219) and I added in an intel x550-t1 pcie nic to run on my 10gbe network.

 

2. I wasn't using the onboard nics, but they were enabled in the bios (which saved me in the end).

 

3. I properly set up the mac1,mac2,mac3 entries in the grub.cfg with the appropriate mac addresses

 

problem:

when first booting loader to upgrade to 6.0.2 from 5.2, I could see the 10gbe nic requesting an IP through DHCP and my server sending one back... but then it kept asking over and over again, ignoring the responses. so I plugged a cable into the first onboard nic, and voila... worked like a champ.

 

using the onboard i219 nic, the upgrade ran smoothly.

 

after booting into DSM, I went to try to figure out what was going on with the network... this is when I realised the i210 and the x550t1 nics seemed to be able to send data out, but nothing would come back. DSM could see that the nics were connected to the network, but couldn't communicate... so it couldn't get an IP address via DHCP. Even when I manually assigned IP addresses, I could not ping that address from another machine.

 

I ssh'd into the NAS, and started looking at the modules.

 

I noticed that the i219 used the e1000e driver, while the i210 and x550 used the igb and ixgbe drivers, both of which depended on the dca.ko module (direct cache access) - not sure if this is relevant

 

solution:

Anyway, i found that if I removed and reloaded the ixgbe module, i could then use ifconfig to bring up the network adapter and i could appropriately communicate with the network.

 

I tried several other workarounds/attempted fixes, but nothing would work... so eventually I just made a script and would unload and reload the ixgbe module and called it from the /etc/rc file just before it configured the network.

 

that did the trick.

 

So, why is the igb and the ixgbe drivers not working properly at boot? I have no clue. If anyone has any ideas, please let me know. If you like me to try anything to troubleshoot, I'm happy to help.

 

Good luck all.

Link to post
Share on other sites
Hennie-M said:
dasis said:
Hello,

 

I did step by step, but didn't boot from usb. Black screen.

20170421_205401_HDR.jpg

 

 

change

 

ch.jpg

 

What i did wrong?

 

Please help me install 6

You are using the wrong serial number. Don;t use the HP serialnumber but generate a synology one. I can't find the link but it has been posted many times.

You can find it!

 

 

IT didn't help. Don't use the HP serial number, was generate a synology one.

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

set vid=0x090C
set pid=0x1000
set sn=1230LWN464934
set mac1=00215A752564
set rootdev=/dev/md0
set netif_num=1
set extra_args_3615=''

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'

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

set default='0'
set timeout='3'
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.02-alpha"

search --file -s /zImage

 

Link to post
Share on other sites
Was that for 3617 1.02a2 or 3615 .2a?

1.02a2 3617 the nic's are up and running. find syno worked initially. Loading DSM not so much. Looking at logs to see whats up when I have time.

 

Yes that was for v1.02a2. The model (3615 or 3617) is irrelevant.

Btw 3.10. should not be calling for b fw

Link to post
Share on other sites
DiskStation> lsmod | grep bnx2

bnx2x 1417616 0

bnx2 73633 0

libcrc32c 898 1 bnx2x

mdio 3293 3 bnx2x,sfc,alx

DiskStation> ifconfig eth0 up

[407668.962886] bnx2: Can't load firmware file "bnx2/bnx2-mips-09-6.2.1b.fw"

ifconfig: ioctl 0x8914 failed: No such file or directory

 

Was that for 3617 1.02a2 or 3615 .2a?

1.02a2 3617 the nic's are up and running. find syno worked initially. Loading DSM not so much. Looking at logs to see whats up when I have time.

 

Yes that was for v1.02a2. The model (3615 or 3617) is irrelevant.

Btw 3.10. should not be calling for b fw

 

It seems so. But since that is what your logs where showing that's what I added without looking into detail the firmware correspondance. Vanilla kernel 3.10.102 should be asking for either of the following firmwares:

bnx2/bnx2-rv2p-09ax-6.0.17.fw

bnx2/bnx2-rv2p-09-6.0.17.fw

bnx2/bnx2-mips-09-6.2.1a.fw

bnx2/bnx2-rv2p-06-6.0.15.fw

bnx2/bnx2-mips-06-6.2.1.fw

 

You could try the following: https://unix.stackexchange.com/question ... -6-2-1b-fw

Let us know how it goes.

Link to post
Share on other sites

Hi jun!

Thank you very much for your loader first!

I am using a motherboard whit an Intel N3710 and 4GB LPDDR3 RAM to run DSM6.1,and I flashed the 'synoboot.img' for DS3617XS which was uploaded on 10th Apr to my USB Disk and modified the 'grub.cfg' as manual told then successfully booted up and installed the DSM6.1 for DS3617XS.But it took a very long time to get the IP address when it restarted. So I restarted it again after initialized the DSM and nothing changed. It doesn't have a VGA or other monitor ports so I don't know what happend.

Is that a known problem? Or how to fix it?

Thanks!

Link to post
Share on other sites
I have tested last loader with ESXI 6.0, no problem.

 

I just cannot add second network card ? Someone did that ?

I add another network interface on VM on ESXI.

I restart Syno, but anything

I use grub menu and mac2 command, anything....

 

Another step missed ?

 

 

EDIT: It's a success, i changed Network interface with E1000 instead VMnet2.

 

Another question, someone installed VMware tools ?

The shutdown by DSM seems to be not working ...

Link to post
Share on other sites
Please, is there any way to make a loader that uses a version that supports SHR natively?

Maybe DS1815+ or something like that?

I am absolutely willing to test/work on to help, but I am no big linux-whiz I'm afraid...

You dont need a DS1815+ for SHR support

just edit /etc.defaults/synoinfo.conf

comment out/delete

supportraidgroup="yes"

then add

support_syno_hybrid_raid="yes"

 

press F5 on you web browser

 

How does one modify it? I opened the file with putty but I can not modify it because it is in use. I'm under ESXi.

 

Thank you

 

Sorry for my english it's traductions

Link to post
Share on other sites

How does one modify it? I opened the file with putty but I can not modify it because it is in use. I'm under ESXi.

 

maybe you forgot to be root (sudo -i), there ist no "in use" for /etc.defaults/synoinfo.conf

Link to post
Share on other sites

Another question, someone installed VMware tools ?

The shutdown by DSM seems to be not working ...

 

beside vmware tools there is the option (patch) to enable acpi power button within dsm (read other thread, mainly used on baremetal installs) that does acpi shutdown for virtualbox i'd expect it will work for vmware too

Link to post
Share on other sites

I think there's a serious problem with v1.02a.

 

During a RAID 5 initial build, data is getting randomly written over segments of the md0 and md1 arrays rendering the Synology unusable. This is using ESXi 6.5 as a backend with a PCI passthrough of an LSI 9211-8i card. It happens when the RAID 5 rebuild gets to about 25%.

 

This has happened on multiple ESXi hosts in various configurations, storage controllers, drive sizes and drives. It looks like one of the drivers injected may have a massive kernel memory corruption bug.

 

Here's the dmesg from the VM.

 

https://pastebin.com/raw/pLtNvVCb

Edited by Guest
Link to post
Share on other sites
if anyone need virtual imgs synoboot v.1.02a2

I got this error on my esxi 6.5 launching the 3617xs vmdk

Failed - Unsupported or invalid disk type 2 for 'scsi0:1'

 

I tried on virtualbox and VMware but hasn't any errors

From a old guide I've

set as IDE (0:0) and check “Independent -> non-persistent”

and I may boot, but I after I cannot find the box in any way :sad:

Link to post
Share on other sites

set as IDE (0:0) and check “Independent -> non-persistent”

and I may boot, but I after I cannot find the box in any way :sad:

 

Check network card settings, should be E1000. Do you have any other DSM running on the same network?

Link to post
Share on other sites
i have 1.02a running 3617xs in virtual box,using the intel pro 1000/mt desktop (bridge mode with the hardware nic) and i gave the nic the mac that was used inside the synoboot.vmdk image (on IDE controller) - try to set the mac propperly so synoimage and vm nic using the same mac?

for the disks used in dsm6.1 the vm has to use scsi controller/disks

 

Thanks for the feedback! yeah I had set the MAC the same as the one in the VM nic, will give it another try this week.

Link to post
Share on other sites
I think there's a serious problem with v1.02a.

 

During a RAID 5 initial build, data is getting randomly written over segments of the md0 and md1 arrays rendering the Synology unusable. This is using ESXi 6.5 as a backend with a PCI passthrough of an LSI 9211-8i card. It happens when the RAID 5 rebuild gets to about 25%.

 

This has happened on multiple ESXi hosts in various configurations, storage controllers, drive sizes and drives. It looks like one of the drivers injected may have a massive kernel memory corruption bug.

 

Here's the dmesg from the VM.

 

https://pastebin.com/raw/pLtNvVCb

 

Confirmed this only happens on the 3617xs image. I reverted to a 3615xs Image and it doesn't have this same issue.

Link to post
Share on other sites

Hi do I create an HA Cluster ?

Can't get this to work..

 

Running ESXI with Loader 6.0.2 DS3615XS.

Created differtened SN's and mac adresses for both VM's.

Altough have not added a Serial connection..

 

Both are running fine, but when creating the cluster, it fails..

 

NIC1 and NIC2 are used..

Is a serial connection needed for this, if yes how to configure ?

 

Hope to hear from somebody uphere, thx :wink:

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.