Working DSM 6


Recommended Posts

Hi All,

fyi I have installed on a Bare metal N40L. On this machine I have disabled the on-board nic and replaced it with a natively supported Intel nic.

Changed the boot config to ignore my boot usb stick, I also added / changed the script to allow usb devices to be recognised when plugging them into the box

(this has been documented further back in the thread)

 

Issues:

1. I cannot change the boot order that was originally suggested in the first post, I have to keep it on "install'

2. Obviously the btrfs issues

3. Shutdown via the web-gui does not work

4. WOL does not work after manually entering poweroff via the console

 

As my machine usually runs 24/7 this is not really a problem...

 

I have managed to get the shutdown correctly working by implementing the process http://xpenology.me/how-to-activate-wol/. However the path seems to have changed and is no longer /USR/SYNO/etc/rc.d/ but is /usr/syno/etc/rc.sysv

 

The shutdown via the web-gui works, but WOL does not. As I'm not a linux expert this is probably the end of the line here, but I will have a look further. I think it might have to do with the fact that I'm not using the onboard nic of my box (N40L) but a extra pce-i intel nic.

 

 

Ok, have now managed to activate WOL. For some reason setting WOL in the UI and directly in the file responsible does not work. I have created a little script that is run on startup that does nothing else than set the wol settings... ethtool eth0 -s wol g

After doing this WOL works...

 

 

Cheers

pak

Edited by Guest
Link to post
Share on other sites

Hello,

 

is it possible to get DSM6 working on "Vmware Workstation 11 Linux"?

I tested it under "Vmware Workstation 11 Windows" and it is working.

But on "Vmware Workstation 11 Linux" the e1000e driver is not working.

 

I found this:

For Linux guests, e1000e is not available from the UI (e1000, flexible vmxnet, enhanced vmxnet, and vmxnet3 are available for Linux).

 

 

 

What you wrote is for "Linux guests" but you should look for "Linux hosts".

Linux guest is the VM.

 

And what can i do?

DSM 5.2 is working, but with Intel e1000.

Is it possible to make a DSM_DS3615xs_7393.iso with e1000 or vmxnet3 driver?

 

 

Why is the e1000e not working? Can someone help? I have this log:

 

==================== start udevd ====================

[ 8.327921] NET: Registered protocol family 10

[ 8.336669] sit: IPv6 over IPv4 tunneling driver

[ 8.422463] init: syno-auth-check main process (5285) killed by TERM signal

[ 9.076017] fuse init (API version 7.22)

[ 9.079272] dca service started, version 1.12.1

[ 9.081808] e1000e: Intel® PRO/1000 Network Driver - 3.1.0.2-NAPI

[ 9.082497] e1000e: Copyright© 1999 - 2014 Intel Corporation.

[ 9.083538] e1000e 0000:03:00.0: Disabling ASPM L0s L1

[ 9.084572] e1000e 0000:03:00.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode

[ 9.189480] divide error: 0000 [#1] SMP

[ 9.190447] Modules linked in: e1000e(O+) dca fuse vfat fat crc32c_intel aesni_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha512_generic sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand mperf processor thermal_sys cpufreq_stats freq_table dm_snapshot crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram© sg etxhci_hcd xhci_hcd uhci_hcd ehci_pci ehci_hcd usbcore usb_common [last unloaded: bromolow_synobios]

[ 9.190492] CPU: 0 PID: 5673 Comm: insmod Tainted: P C O 3.10.77 #7393

[ 9.190537] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 05/20/2014

[ 9.190582] task: ffff88005cbad550 ti: ffff88005c1ac000 task.ti: ffff88005c1ac000

[ 9.190627] RIP: 0010:[] [] e1000e_cyclecounter_read+0x9f/0xb0 [e1000e]

[ 9.190672] RSP: 0018:ffff88005c1afbc8 EFLAGS: 00010246

[ 9.190717] RAX: 0000000000000000 RBX: ffff88005c1ff5f8 RCX: 0000000000000000

[ 9.190762] RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff88005c1ff5e0

[ 9.190806] RBP: 146cae21484b9e99 R08: 0000000000000032 R09: 0000000000000000

[ 9.190851] R10: 00000007ffffffff R11: 000000000000000e R12: 0000000001a00000

[ 9.190896] R13: 0000000000000000 R14: ffff88005c1fc700 R15: 0000000000000000

[ 9.190941] FS: 00007fb897445700(0000) GS:ffff88005f600000(0000) knlGS:0000000000000000

[ 9.190986] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b

[ 9.191031] CR2: 00000000004192d0 CR3: 000000005a39e000 CR4: 00000000000007f0

[ 9.191076] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000

[ 9.191121] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400

[ 9.191166] Stack:

[ 9.191211] ffffffff81076c80 0000000000000000 0000000000000000 ffffffffa024ca2c

[ 9.191255] 00ffc90000000000 01a000005c1afb8c ffff88005c1fc700 ffff88005c1fcbd0

[ 9.191300] ffff88005c1fcbd0 0000000000008000 ffff88005c1fc700 ffff88005c1fc000

[ 9.191345] Call Trace:

[ 9.191405] [] ? timecounter_init+0x10/0x20

[ 9.191465] [] ? e1000e_config_hwtstamp+0x22c/0x530 [e1000e]

[ 9.191524] [] ? e1000e_reset+0x29d/0x7a0 [e1000e]

[ 9.191584] [] ? e1000_probe+0xb07/0xdb0 [e1000e]

[ 9.191642] [] ? pci_device_probe+0x60/0xa0

[ 9.191700] [] ? really_probe+0x5a/0x220

[ 9.191757] [] ? __driver_attach+0x81/0x90

[ 9.191813] [] ? __device_attach+0x40/0x40

[ 9.191871] [] ? bus_for_each_dev+0x53/0x90

[ 9.191927] [] ? bus_add_driver+0x158/0x250

[ 9.191988] [] ? 0xffffffffa0272fff

[ 9.192044] [] ? driver_register+0x68/0x150

[ 9.192102] [] ? 0xffffffffa0272fff

[ 9.192159] [] ? do_one_initcall+0xea/0x140

[ 9.192217] [] ? load_module+0x1ae8/0x2050

[ 9.192273] [] ? store_uevent+0x40/0x40

[ 9.192332] [] ? vfs_read+0xf3/0x160

[ 9.192389] [] ? SyS_finit_module+0x6d/0x70

[ 9.192448] [] ? system_call_fastpath+0x16/0x1b

[ 9.192493] Code: f8 d5 ff ff 8b 80 00 b6 00 00 48 8b 8f f8 d5 ff ff 8b 89 04 b6 00 00 48 c1 e1 20 89 c0 48 09 c1 48 89 ce 48 29 d6 31 d2 48 89 f0 <49> f7 f1 48 85 d2 75 c1 4c 39 d6 77 bc 48 89 c8 c3 55 53 48 89

[ 9.192538] RIP [] e1000e_cyclecounter_read+0x9f/0xb0 [e1000e]

[ 9.192582] RSP

[ 9.192680] ---[ end trace 5811a38d5625a212 ]---

[ 9.198894] Intel® Gigabit Ethernet Network Driver - version 5.2.17

[ 9.200501] Copyright © 2007-2015 Intel Corporation.

[ 9.207395] Intel® 10 Gigabit PCI Express Network Driver - version 4.3.13

[ 9.207496] Copyright © 1999-2015 Intel Corporation.

[ 9.208633] ixgbe unsupported_sfp_notify proc entry initialized

[ 9.212577] i40e: Intel® Ethernet Connection XL710 Network Driver - version 1.3.47

[ 9.213503] i40e: Copyright © 2013 - 2015 Intel Corporation.

[ 9.217677] tn40xx: Tehuti Network Driver, 0.3.6.11.2

[ 9.221209] Loading modules backported from Linux version v3.18.1-0-g39ca484

[ 9.221472] Backport generated by backports.git v3.18.1-1-0-g5e9ec4c

[ 9.227973] Compat-mlnx-ofed backport release: b558788

[ 9.228473] Backport based on mlnx_ofed/mlnx_rdma.git b558788

[ 9.229474] compat.git: mlnx_ofed/mlnx_rdma.git

[ 9.257770] bnx2x: QLogic 5771x/578xx 10/20-Gigabit Ethernet Driver bnx2x 1.713.00 ($DateTime: 2015/07/28 00:13:30 $)

[ 9.280877] bio: create slab at 1

[ 9.281628] Btrfs loaded

[ 10.339967] systemd-udevd[5825]: starting version 204

Link to post
Share on other sites

Hello, which files have you used to get this working on ESXi 6? I'm sure I've tried everything in this thread numerous times but cannot get it to work. :shock:

 

DSM 6 running fine on esxi, used okitsme's hw10 workstation vmdks converted.

Tested with sata virtual disks, btrfs raid 6, everything seems to work.

Thank you so much for sharing this, I would have never been able do pull something like this off!

 

I have two issues. One is the lack of shr support which I attribute to the DS3615xs pat. Anyone have a workaround?

The bigger problem for me however is that the perc H310 card finally arrived, flashed it to LSI it firmware (following techmattr's guide) but it does not work with dsm. Have two disks connected for testing, passed the card to DSM but disks dont show. If I pass it to a Windows vm drives show and operate as expected.

Do I have to take any additional steps to enable the card? One weird thing is that even though the flashing worked (confirmed multiple times to test my sanity) the card shows as a Dell in esxi.

Link to post
Share on other sites

Hello, which files have you used to get this working on ESXi 6? I'm sure I've tried everything in this thread numerous times but cannot get it to work.

 

DSM 6 running fine on esxi, used okitsme's hw10 workstation vmdks converted.

Tested with sata virtual disks, btrfs raid 6, everything seems to work.

Thank you so much for sharing this, I would have never been able do pull something like this off!

 

I have two issues. One is the lack of shr support which I attribute to the DS3615xs pat. Anyone have a workaround?

The bigger problem for me however is that the perc H310 card finally arrived, flashed it to LSI it firmware (following techmattr's guide) but it does not work with dsm. Have two disks connected for testing, passed the card to DSM but disks dont show. If I pass it to a Windows vm drives show and operate as expected.

Do I have to take any additional steps to enable the card? One weird thing is that even though the flashing worked (confirmed multiple times to test my sanity) the card shows as a Dell in esxi.

Link to post
Share on other sites
Hello, which files have you used to get this working on ESXi 6? I'm sure I've tried everything in this thread numerous times but cannot get it to work.

 

Hi, I used okitsme's Workstation files on page 7 (oktisme » 16 Jun 2016 11:33). Converted the vm with VMware standalone converter. I used hardware version 10 and changed the nic to 1000e before converting.

No install, booted straight away with the run option, has been working since.

 

There's a ready made one from haydibe I didn't notice until now, might be a more straightforward way, also on page 7.

Link to post
Share on other sites
Hello, which files have you used to get this working on ESXi 6? I'm sure I've tried everything in this thread numerous times but cannot get it to work.

 

Hi, I used okitsme's Workstation files on page 7 (oktisme » 16 Jun 2016 11:33). Converted the vm with VMware standalone converter. I used hardware version 10 and changed the nic to 1000e before converting.

No install, booted straight away with the run option, has been working since.

 

There's a ready made one from haydibe I didn't notice until now, might be a more straightforward way, also on page 7.

I'm using that on my ESXi and it's working OK.

Link to post
Share on other sites
your controller should be a rebranded LSI9211-8i, which should be supprted by the included mpt2sas.ko driver.

 

Something is strange with the driver. It exists in /lib/modules and can be loades from the cli 'insmod /lib/modules/mpt2sas.ko'. After insmod, mpt2sas is listed in lsmod. But i couldn't load it using modprobe...

 

Though, i never tried to actualy use my lsi contollers in pass thru mode with DSM6. My main storages are still using XPE and I mounted shares from it to my DSM6 vm. Since i am using DSM6 only for it's docker capabilites, it's workng fine for me :smile:

 

Thanks for looking into it. This is my first foray into xpenology, plus I'm not too familiar with linux, don't know how the drivers are loaded.

I also don't understand the difference between the "Install" and run options.

After a lot of trial and error I found out the controller does work if booted to "install". If I then restart to "run" the first time setup screen comes up, my previously created account seems to be gone, but then I reboot to install and everything is there as before.

I can create volumes, but not btrfs (immediete crash), and I'm a little uncomfortable running it with install as I don't see that being the intended way and do not understand the implications.

Link to post
Share on other sites

One way to look at it is that "install" is basically Xpenoboot for 5.2 and has support for non-synology hardware but not all the new stuff in V6 (eg btrfs). "run" is the V6 synology bootloader with a mod to disable the security check. If you have compatible hardware, you can load the "synology bootloader" and get access to the features of V6.

If you run with "install", then you are trying to run V6 on the V5.2 bootloader and that's not really a good idea as oktisme said somewhere near the beginning when I said I was doing it.

Link to post
Share on other sites
Hello, which files have you used to get this working on ESXi 6? I'm sure I've tried everything in this thread numerous times but cannot get it to work.
:shock:

 

Describe where or what you are doing at the point of "not working"

The VM boot process takes a few seconds are you are left with a screen with blue box and 5 lines of output, last line should say "Booting the kernel"

Link to post
Share on other sites
Anyone tried and succeed installing 6.0.2-8451 update?

Failed for me with "unknown error"

 

Came here to ask the same. It fails for me too at 20% with unknown error. I updated to 6.0.1 update 2 without issue. I guess we will have to wait for someone with expertise to make a new image.

Link to post
Share on other sites
One way to look at it is that "install" is basically Xpenoboot for 5.2 and has support for non-synology hardware but not all the new stuff in V6 (eg btrfs). "run" is the V6 synology bootloader with a mod to disable the security check. If you have compatible hardware, you can load the "synology bootloader" and get access to the features of V6.

If you run with "install", then you are trying to run V6 on the V5.2 bootloader and that's not really a good idea as oktisme said somewhere near the beginning when I said I was doing it.

 

Thanks, this explains a lot! I was under the impression that the LSI cards are natively supported. I'm using a Dell H310 flashed to LSI-9211i8i firmware. Is the LSI-9211i8i not supported, or did I wonk something with the flash? The card still does show up as a Dell HBA in esxi.

 

Anyways, think I'll try running whatever the last "supported" Xpenology build if all else fails.

 

BTW update 6.0.2-8451 gave me "Unknown error occurs (21)." as others already posted above.

Link to post
Share on other sites
Hi!

 

Iv*e got everything work yesterday but i dont know what happend today :/

 

maybe is it bevause in installed SurveillanceStation-x86_64-7.2.2-4649.spk

 

i patched it with sspatcher-v061

 

chek around littlebit in menus etc... after some time but now i have

 

extreamly slowly xpenology and i get errors like:

 

synology connection failed please check your network settings

 

and i cant check updates.. says no connection etc... and i cant see almost nothing in menus...

 

every boxes looks emty and so on :sad:

 

haha... and now i get blank (white) login page :sad:

 

maybe someone can help me?

 

Only i can log in with telnet. SSH not also working to :/

 

Same problem here!

 

Any news about that?

Link to post
Share on other sites
Hi!

 

Iv*e got everything work yesterday but i dont know what happend today :/

 

maybe is it bevause in installed SurveillanceStation-x86_64-7.2.2-4649.spk

 

i patched it with sspatcher-v061

 

chek around littlebit in menus etc... after some time but now i have

 

extreamly slowly xpenology and i get errors like:

 

synology connection failed please check your network settings

 

and i cant check updates.. says no connection etc... and i cant see almost nothing in menus...

 

every boxes looks emty and so on :sad:

 

haha... and now i get blank (white) login page :sad:

 

maybe someone can help me?

 

Only i can log in with telnet. SSH not also working to :/

 

Same problem here!

 

Any news abou that?

Link to post
Share on other sites
Do I understand correctly: the project XPEnology stopped safely with the latest bootloader version 5.2 and further development is not supposed to?

XPEnology supports DSM 5.2. If Synology release more builds for this version, then I expect that the devs will update the XPEnology bootloader if needed.

 

XPEnology does not support DSM 6. The devs are waiting for Synology to release the source code as they are obligated to (there's another thread on that) and then they can start to work on that version. I expect that Synology will delay release as long as they can.

 

oktisme patched the Synology bootloader to work around Synology's security check. The check was basic and it is quite probable that they have changed it to something more advanced and this might be the reason why the latest DSM won't install.

Link to post
Share on other sites
Finally got around to installing DSM 6.0.1-7393 on ESXi 6.0 (via the posted DSM6_esxi_hw10.ova here). Works like a charm. :smile: It won't let me upgrade to 6.0.2-8451, though. Is there a way around that?

 

Thanks.

 

Here, where? There is no link to your post!

Link to post
Share on other sites
Finally got around to installing DSM 6.0.1-7393 on ESXi 6.0 (via the posted DSM6_esxi_hw10.ova here). Works like a charm. :smile: It won't let me upgrade to 6.0.2-8451, though. Is there a way around that?

 

Thanks.

 

Here, where? There is no link to your post!

 

This is the package I used:

 

http://xpenology.com/forum/viewtopic.php?f=2&t=16114&start=60#p65490

Link to post
Share on other sites
I tested your vmdk in vmware and works pretty fine, thank guys!

 

but i would like to use it on KVM (because I use unraid as a backend I prefer this storage system more than typical mdadm raid) and share volumes over NFS

 

Anyone know how can I install it on KVM?

 

I didn't see any other responses in regards to Unraid. I got it working in unraid, here's how.

 

I used these files mentioned previously in the thread ...

 

IMG file from @dynax

https://mega.nz/#!w9RkULAR!3_Hhvp7yX3kc ... kRBzxw1ONY

 

PAT file from @oktisme

https://mega.nz/#!sQlWSC5C!tgGduyY5bze3 ... 87PrPkx4fc

 

To note, I'm on Unraid 6.2.0 - RC4 (They've made major updates to the VM stuff in the beta, I'd reccomend updating if you havent)

 

Use the img file as the primary hard drive and use driver 'VirtI0' - If you use SATA then when you try to install the PAT DSM thinks the boot disk should be formatted, VirtI0 makes it so DSM can't see the drive.

 

Create a data drive and use SATA driver in the drop down. (If not on beta you have to manually change the driver in the xml file. See below.)

 

(only if you're not on beta)

 

<------------- Change this from bus='virtio'/> to bus='sata'/>

 

 

 

After you've created your VM be sure to edit the XML and change the NIC driver - See below.

 

(Whether you're on beta or not you have to make this change every time you edit via web gui.)

 

<------ Change this from to type='e1000'/>

 

 

Now Boot, find syno, install pat, reboot. - Use EXT4 not BTRFS.

 

That's as far as I've gotten at this point. Working on backing up my DSM5 files and apps, planning on restoring to DSM6.

 

Hopes this helps a fellow Unraid user.

 

-NeoenY152

Link to post
Share on other sites

So I'm trying to test out injecting proper serial number and mac address but cannot successfully edit the syslinux.cfg file.

 

Can someone point me in the right direction how to edit the cfg file inside the vmdk? I have tried using VMware workstation on windows, but it crashes when trying to save the file. Now i'm trying to mount it in Ubuntu with little success. I don't have much experience with vmdk files so I'm hoping i'm missing something easy.

Link to post
Share on other sites

I am sorry if this is already addressed. Went through all the pages and couldn't find the answer :sad:

 

I have 5.x running in VMWare Workstation (phyiscal drive added) and is it possible to upgrade to 6.x DSM using this method? I could run new DSM setup using the first page downloads.

 

- Sriman

Link to post
Share on other sites
Guest
This topic is now closed to further replies.