DSM 6.1.x Loader


Recommended Posts

Does anybody tested all the sata ports of hp n40L

I configured my 5ths port, just typing SataPortMap=5, but how can I do to use the esata port?

is it SataPortMap=6? or 61?

 

:smile:

 

This info was provided by Setsunakawa earlier in this thread...

SataPortMap=4 means first 4 ports of 1st controler.

SataPortMap=44 means first 4 ports of 1st controler and first 4 ports of 2nd controler.

SataPortMap=422 means first 4 ports of 1st controler, first 2 ports of 2nd controler and first 2 ports of 3rd controle

 

You could try SataPortMap=51 assuming you have the four bays and the onboard sata port populated and the esata is classed as a separate controller. I'm only using three bays so I can't test the theory.

Link to post
Share on other sites

I've managed to install original 8451 pat in Proxmox VM with Arcao uefi-boot img. (Mount qcow2 file as USB, Boot in UEFI from USB).

No error 13.

But after install I stuck on upgrade for now =))

Every time after reboot DSM shows me:

We've detected that the hard drives of your current DS3615xs had been moved from a previous DS3615xs, and installing a newer DSM is required before continuing.
Status: Upgrade required
Firmware version: 6.0.2-8451
DSM version: 6.0.2-8451

Link to post
Share on other sites
Hi guys,

 

Here is prepared image with included AMD zImage:

 

Image prepared with OSFMount.

Recreated my boot USB flash drive for my my HP N40L Gen7 Microserver with this image. Very easy and workes well.
  1. From Arcao's Mega folder linked from THIS POST, I used the dsm6.0.2-8451/v2/jun-amd-baremetal-hybrid-uefibios-arcao-v2.zip file to flash a USB flash drive with the Win32 Disk Imager tool
  2. Used Flash Drive Information Extractor to get USB flash drive's VID & PID
  3. Updated grub.cfg (updated sn, mac1, vid & pid, and added SataPortMap & mac2. Of course they aren't all x's :wink: )
    serial --port=0x3F8 --speed=115200
    terminal_input serial console
    terminal_output serial console
    set default='0'
    set timeout='1'
    set fallback='0'
    
    menuentry 'Synology DS3615xs' --class os {
    insmod	fat
    linux	/image/DS3615xs/zImage root=/dev/md0 syno_hdd_powerup_seq=0 netif_num=1 HddHotplug=0 SataPortMap=4 syno_hw_version=DS3615xs vender_format_version=2 vid=0x05DC pid=0xA761 console=ttyS0,115200n8 sn=xxxxxxxxxx mac1=xxxxxxxxxxxx mac2=xxxxxxxxxxxx withefi elevator=your_magic_elevator quiet
    initrd	/image/DS3615xs/ramdisk.lzma
    }

  4. Installed USB to internal USB port on System Board and booted server
  5. DSM already on 6.0.2-8451 Update 2
  6. Working well :ugeek:

Thanks again Arcao & jun! :grin:

 

Just one question; After rebooting the server (or powering off then powering on), I get System Event Notification stating "Diskstation experienced an improper shutdown". I'm only powering it off or rebooting from within the DSM web interface. Do we know what the cause of this is?

Link to post
Share on other sites

The improper shutdown is a known issue if your machine has no console. You need to edit /usr/share/init/syno_poweroff_task.conf and change console "output" to "none" and if you want to stop spam in some of the logs you need to do the same in a few other files. See Jun's original post #1 of this thread for more details.

 

Without the quotes. :wink:

Link to post
Share on other sites
BTW, how can i hide my IDE drive with loader from DSM?

Adding

set extra_args_3615='rmmod=ata_piix'

doesn't work for me =(

 

oops, good news is ata_piix works,

bad news is seems not everyone loves it :smile:

Link to post
Share on other sites

so here is my issue with v1 I can find my DSM and gives me the option to install however, it only sees my two SSDs attached to the onboard controller, it does not see 8 3TB attached to 9211-8i.

 

with V2 I been trying for 2 days to get it to work but I can never find DSM, doesn' get an IP. I tried many configurations without luck.

 

My mobo is an E3C224-4L, 32 GB ECC and LSI 9211-8i HBA mode, 8 3TB WD Red and 2 128gb SSD for cache

 

I tried disabling on board sata controllers, disabling on board lan and installing an intel nic know to be compatible, again with V1 i can boot find DSM and install, issue is can't see HD attached to LSI controller, with V2 can't find DSM period.

 

mobo specs

 

2 x PCIe 3.0 x16, 1 x PCIe 3.0 x4, 1 x PCIe 2.0 x1, 2 x PCI

4 x SATA3, 2 SATA2 by Intel C224 support RAID 0,1,5,10

2 x SATA3 by Marvell 9172 support RAID 0,1

4 x Intel i210, support Quad GLAN

ASPEED 2300 for BMC controller, Realtek RTL8211E for dedicated IPMI GLAN

4 x USB 3.0 ports (2 rear + 2 via header )

7 x USB 2.0 ports (2 rear + 4 via header +1 Type A)

 

any suggestions?

thanks

Link to post
Share on other sites

The governor works out of the box but it seems to be in "performance" mode. Is there a way to tell it to use "conservative" or "powersave" etc. without applying the old fix we used in DSM 5.X? I greped the usr folder but couldn't find the string with my searches. :oops:

Link to post
Share on other sites
The governor works out of the box but it seems to be in "performance" mode. Is there a way to tell it to use "conservative" or "powersave" etc. without applying the old fix we used in DSM 5.X? I greped the usr folder but couldn't find the string with my searches. :oops:

Just use the old script and problem solved?

Link to post
Share on other sites

I think after some testing, I realized my onboard Intel I211 is the one not working, which is eth1. Is the driver for I211 not supported?

DSM can detect 2 lan but the eth1 never able to get IP from DHCP. the working one is eth0.

 

2016-10-30T13:39:12+08:00 CALVIN-NAS kernel: [   12.315401] zram: module is from the staging directory, the quality is unknown, you have been warned.
2016-10-30T13:39:14+08:00 CALVIN-NAS kernel: [   13.869241] e1000e: Intel(R) PRO/1000 Network Driver - 3.3.5-NAPI
2016-10-30T13:39:14+08:00 CALVIN-NAS kernel: [   13.869242] e1000e: Copyright(c) 1999 - 2016 Intel Corporation.
2016-10-30T13:39:14+08:00 CALVIN-NAS kernel: [   13.869339] e1000e 0000:00:1f.6: setting latency timer to 64
2016-10-30T13:39:14+08:00 CALVIN-NAS kernel: [   13.869382] e1000e 0000:00:1f.6: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
2016-10-30T13:39:14+08:00 CALVIN-NAS kernel: [   13.869400] e1000e 0000:00:1f.6: irq 140 for MSI/MSI-X
2016-10-30T13:39:14+08:00 CALVIN-NAS kernel: [   14.355621] e1000e 0000:00:1f.6 eth0: registered PHC clock
2016-10-30T13:39:14+08:00 CALVIN-NAS kernel: [   14.355624] e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 1c:1b:0d:63:b9:36
2016-10-30T13:39:14+08:00 CALVIN-NAS kernel: [   14.355625] e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection
2016-10-30T13:39:14+08:00 CALVIN-NAS kernel: [   14.355694] e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: FFFFFF-0FF
2016-10-30T13:39:15+08:00 CALVIN-NAS kernel: [   14.375642] igb 0000:03:00.0: irq 141 for MSI/MSI-X
2016-10-30T13:39:15+08:00 CALVIN-NAS kernel: [   14.375646] igb 0000:03:00.0: irq 142 for MSI/MSI-X
2016-10-30T13:39:15+08:00 CALVIN-NAS kernel: [   14.416236] igb 0000:03:00.0: added PHC on eth1
2016-10-30T13:39:15+08:00 CALVIN-NAS kernel: [   14.416238] igb 0000:03:00.0: Intel(R) Gigabit Ethernet Network Connection
2016-10-30T13:39:15+08:00 CALVIN-NAS kernel: [   14.416239] igb 0000:03:00.0: eth1: (PCIe:2.5GT/s:Width x1)
2016-10-30T13:39:15+08:00 CALVIN-NAS kernel: [   14.416240] igb 0000:03:00.0 eth1: MAC: 1c:1b:0d:63:b9:38
2016-10-30T13:39:15+08:00 CALVIN-NAS kernel: [   14.416243] igb 0000:03:00.0: eth1: PBA No: Unknown
2016-10-30T13:39:15+08:00 CALVIN-NAS kernel: [   14.416253] igb 0000:03:00.0: LRO is disabled
2016-10-30T13:39:15+08:00 CALVIN-NAS kernel: [   14.416254] igb 0000:03:00.0: Using MSI-X interrupts. 1 rx queue(s), 1 tx queue(s)
2016-10-30T13:39:15+08:00 CALVIN-NAS kernel: [   14.664852] e1000: Intel(R) PRO/1000 Network Driver - version 7.3.21-k8-NAPI
2016-10-30T13:39:15+08:00 CALVIN-NAS kernel: [   14.664853] e1000: Copyright (c) 1999-2006 Intel Corporation.
2016-10-30T13:39:15+08:00 CALVIN-NAS kernel: [   14.746644] 2016-10-30 5:39:15 UTC
2016-10-30T13:39:15+08:00 CALVIN-NAS kernel: [   14.746648] Brand: Synology
2016-10-30T13:39:15+08:00 CALVIN-NAS kernel: [   14.746649] Model: DS-3615xs
2016-10-30T13:39:15+08:00 CALVIN-NAS kernel: [   14.746650] set group disks wakeup number to 4, spinup time deno 7
2016-10-30T13:39:16+08:00 CALVIN-NAS kernel: [   15.924310] e1000e 0000:00:1f.6: irq 140 for MSI/MSI-X
2016-10-30T13:39:16+08:00 CALVIN-NAS kernel: [   16.025096] e1000e 0000:00:1f.6: irq 140 for MSI/MSI-X
2016-10-30T13:39:19+08:00 CALVIN-NAS kernel: [   18.872040] e1000e: eth0 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

 

 

set vid=0x0781

set pid=0x556C

set sn=B1W4N42666

set mac1=1C1B0D63B936

set mac2=1C1B0D63B938

set rootdev=/dev/md0

set netif_num=2

set extra_args_3615=''

 

from BIOS:

Intel I211 - 1C:1B:0D:63:B9:38

Intel I219-V - 1C:1B:0D:63:B9:36

 

Motherboard: GA-H170N-WIFI

 

Using latest image v1.0 from Jun

Link to post
Share on other sites

 

10/29:

It's time to release a loader with a proper version number now.

Here is my loader v1.0

https://mega.nz/#F!18kB1BTB!1ft3N5Hnrcnqsneu0aQUkA

 

New features & fix:

 

Support bios & uefi boot & VMware & ESXI

Fix cmos reset issue( at least on bios mode VMware workstation)

most configurations can be done via grub command line now.

Remember last boot entry.

Autodetect synoboot partitions, not extensively tested. It is still recommended to set correct vid/pid.

AMD CPU support, not extensively tested, there are a few positive report on the forum.

Add grub menu for reinstallation.

Add grub menu to force installation when interrupted due to "Disks Disabled" message, not extensively tested

Automatically apply workaround for boards without serial port.

Fix SATA disk order remap, and allow to set SAS disk starting no, but disk order are still not deterministic between SAS disks.

Fix SAS disk naming, not extensively tested, only with one SAS2008 based HBA and synology provided mpt2sas driver.

Add ata_piix support, tested on VMware and it does not crash, only complain about "Read current link speed fail", so I

assume it works :smile:, this driver requires a bit of patching to the kernel, so I include it in the package.

 

Integrate up-to-date network drivers compiled by Arcao and Trantor.

 

 

Known issue:

When runing on a slow single core machine, there is a race condition causes the patcher loading too late.

the most obvious sign is console not working properly. I don't expected this to happen normally,

the only example is a VM on my laptop when running on battery. If anyone believes have this issue,

please send me a message.

 

Some ethernet drivers crash when set MTU above about 4096(Jumbo frame), I've not identified the culprit yet.

 

 

How to install:

 

find the vid/pid of your usb drive

Burn the image to the drive, optionally edit grub.cfg to set vid/pid and boot entry, OR

connect monitor/keyboard/serial console to your Box.

Press C during Grub boot menu to enter command line

vid 0xXXXX
pid 0xYYYY

to configure pid and vid ("pid" and "vid" are command, and "XXXX", "YYYY" are you usb drive's vid,pid)

(There are a few other options can be config this way, you can read grub.cfg to know more detail.)

Press Esc to go back to boot menu

Select baremeta/baremetal AMD entry, press enter to boot.

If your encounter the "disk port disabled" error during installation, try the force install menu entry.

if both option does not work, you have to fallback to SataPortMap method,

type this line in grub command line, replace XX with appropriate value.

append SataPortMap=XX

 

Jun,

 

Does configuring grub (vid/pid, SataPortMAp=) through command line apply changes to grub.cfg file permanently?

Link to post
Share on other sites

 

10/29:

It's time to release a loader with a proper version number now.

Here is my loader v1.0

https://mega.nz/#F!18kB1BTB!1ft3N5Hnrcnqsneu0aQUkA

 

New features & fix:

 

Support bios & uefi boot & VMware & ESXI

Fix cmos reset issue( at least on bios mode VMware workstation)

most configurations can be done via grub command line now.

Remember last boot entry.

Autodetect synoboot partitions, not extensively tested. It is still recommended to set correct vid/pid.

AMD CPU support, not extensively tested, there are a few positive report on the forum.

Add grub menu for reinstallation.

Add grub menu to force installation when interrupted due to "Disks Disabled" message, not extensively tested

Automatically apply workaround for boards without serial port.

Fix SATA disk order remap, and allow to set SAS disk starting no, but disk order are still not deterministic between SAS disks.

Fix SAS disk naming, not extensively tested, only with one SAS2008 based HBA and synology provided mpt2sas driver.

Add ata_piix support, tested on VMware and it does not crash, only complain about "Read current link speed fail", so I

assume it works :smile:, this driver requires a bit of patching to the kernel, so I include it in the package.

 

Integrate up-to-date network drivers compiled by Arcao and Trantor.

 

 

Known issue:

When runing on a slow single core machine, there is a race condition causes the patcher loading too late.

the most obvious sign is console not working properly. I don't expected this to happen normally,

the only example is a VM on my laptop when running on battery. If anyone believes have this issue,

please send me a message.

 

Some ethernet drivers crash when set MTU above about 4096(Jumbo frame), I've not identified the culprit yet.

 

 

How to install:

 

find the vid/pid of your usb drive

Burn the image to the drive, optionally edit grub.cfg to set vid/pid and boot entry, OR

connect monitor/keyboard/serial console to your Box.

Press C during Grub boot menu to enter command line

vid 0xXXXX
pid 0xYYYY

to configure pid and vid ("pid" and "vid" are command, and "XXXX", "YYYY" are you usb drive's vid,pid)

(There are a few other options can be config this way, you can read grub.cfg to know more detail.)

Press Esc to go back to boot menu

Select baremeta/baremetal AMD entry, press enter to boot.

If your encounter the "disk port disabled" error during installation, try the force install menu entry.

if both option does not work, you have to fallback to SataPortMap method,

type this line in grub command line, replace XX with appropriate value.

append SataPortMap=XX

 

Jun,

 

Does configuring grub (vid/pid, SataPortMAp=) through command line apply changes to grub.cfg file permanently?

It is saved in /grub/grubenv file, so it is permanent, but in a seperate file, this is the grub's way.

Link to post
Share on other sites

First of all thank you to everybody for this great work.

I would like to give some feedback on bare-metal installation (see signature).

After migrating from to old bootloader to the new one and updating the system my fixed IP was lost and I had to re-configure it.

My Thermal-status is always on 40°C.

CPU is always on 1.6 GHz.

HDD do not hybernate.

 

Looks like some sensor informations are not working...

 

 

Keep on developing this loader it's great work!

Link to post
Share on other sites

It is saved in /grub/grubenv file, so it is permanent, but in a seperate file, this is the grub's way.

 

Could there be any conflict if one would use the command line once thus editing /grub/grubenv and then edit the grub.cfg file manually with different data?

Link to post
Share on other sites

It is saved in /grub/grubenv file, so it is permanent, but in a seperate file, this is the grub's way.

 

Could there be any conflict if one would use the command line once thus editing /grub/grubenv and then edit the grub.cfg file manually with different data?

 

Normally grub.cfg stores default configurations, and customization through grub command line interface will take precedence.

Link to post
Share on other sites

I load the modules in this order: virtio virtio_ring virtio_pci virtio_net

 

[  148.627764] virtio_pci: Unknown symbol register_virtio_device (err 0)
[  156.005140] virtio-pci 0000:00:03.0: setting latency timer to 64
[  156.024991] virtio-pci 0000:00:13.0: setting latency timer to 64
[  156.044885] virtio-pci 0000:00:14.0: setting latency timer to 64
[  162.012201] virtio-pci 0000:00:13.0: irq 41 for MSI/MSI-X
[  162.012219] virtio-pci 0000:00:13.0: irq 42 for MSI/MSI-X
[  162.012233] virtio-pci 0000:00:13.0: irq 43 for MSI/MSI-X
[  162.016274] virtio_net: probe of virtio1 failed with error -12
[  162.016437] virtio-pci 0000:00:14.0: irq 41 for MSI/MSI-X
[  162.016454] virtio-pci 0000:00:14.0: irq 42 for MSI/MSI-X
[  162.016473] virtio-pci 0000:00:14.0: irq 43 for MSI/MSI-X
[  162.019253] virtio_net: probe of virtio2 failed with error -12
[  208.755483] virtio-pci 0000:00:13.0: irq 41 for MSI/MSI-X
[  208.755500] virtio-pci 0000:00:13.0: irq 42 for MSI/MSI-X
[  208.755515] virtio-pci 0000:00:13.0: irq 43 for MSI/MSI-X
[  208.758367] virtio_net: probe of virtio1 failed with error -12
[  208.758526] virtio-pci 0000:00:14.0: irq 41 for MSI/MSI-X
[  208.758542] virtio-pci 0000:00:14.0: irq 42 for MSI/MSI-X
[  208.758557] virtio-pci 0000:00:14.0: irq 43 for MSI/MSI-X
[  208.761175] virtio_net: probe of virtio2 failed with error -12

Link to post
Share on other sites

I can't import OVF to ESXI 6.0 because I'm getting this error:

Opening OVF source: d:\server\xpenology\ovf\ds3615.ovf
Enter login information for target vi://10.11.11.1/
Username: root
Password: ********
Error: Host name (root) resolve failed
Warning:
- No manifest file found.
- Wrong file size specified in OVF descriptor for 'synoboot.vmdk' (specified: 0, actual 432).
Completed with errors

I'm using ovftool - what am I doing wrong?

Link to post
Share on other sites
I can't import OVF to ESXI 6.0 because I'm getting this error:

Opening OVF source: d:\server\xpenology\ovf\ds3615.ovf
Enter login information for target vi://10.11.11.1/
Username: root
Password: ********
Error: Host name (root) resolve failed
Warning:
- No manifest file found.
- Wrong file size specified in OVF descriptor for 'synoboot.vmdk' (specified: 0, actual 432).
Completed with errors

I'm using ovftool - what am I doing wrong?

Sorry, I dont test ovf import, only try on VMware.

What I think maybe go wrong is the file name and extension, try this

first make sure you did not throw away synoboot.img, it is the real content, synoboot.vmdk is just a description file, if you did, put it back and try again.

otherwise rename synoboot.img to synoboot-flat.vmdk

open synoboot.vmdk with a text editor, make the same change to the line contains synoboot.img

then try again

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.