jun

DSM 6.1.x Loader

Recommended Posts

Hi All 

 

I am on DSM 6.1.2-15132 Update 1 is it safe to update to DSM 6.1.3-15152 that is that I get when I try to check the update status.

 

 

Regards

Igor

Share this post


Link to post
Share on other sites
This have something with nested virtualization, try find how to setup in vmware.
 
Thanks for the hint. Although it is not "nested" virtualization how vmware calls it, you can tick a CPU option in every vm to pass down the virtualization functions to the vm.


Gesendet von meinem ONE A2003 mit Tapatalk

Share this post


Link to post
Share on other sites

Hi,
I have a barebone Foxconn nt330i
CPU Intel Atom Dual Core 330, FSB 533 1.60GHZ 
Chipset nVIDIA MCP7A-ION
 
With xpenoboot 5.2-5967 ethernet lan works and I can install xpenology.
I Tried with Jun's loader 1.01/1.02b and Extra.lzma ramdisk but ethernet lan doesn't work and I can't install xpenology.
There is a way to add lan driver?

Share this post


Link to post
Share on other sites
On 3-8-2017 at 8:44 AM, waspsoton said:

check this post out. I am currently running the latest update on my amd system.

 

 

 

This version only support 6.0.1 and nog 6.1 as the latest jun loader has, that's why I want AMD support with the latest boot loader. Now I'm stuck at 6.0.1.

Share this post


Link to post
Share on other sites

Don't think, that many people come to such a weird solution.

 

Just try it out and let us know, how this scenario performs - if you get it running properly  :-)

 

 

Edited by hpk

Share this post


Link to post
Share on other sites

I'm on the 3615xs 1.02b loader on ESXi 6.5 and I'm struggling with this error. I'm not completely sure, but it seems like I can trigger this by going to the system information page in DSM. Any ideas would be deeply appreciated. I've also seen this in DSM 6.0, but ony when enabling SNMP. On 6.1 it happens even with the service disabled.

 

It does not happen on a clean virtual machine, only when passing through my LSI 9201 card... However, it looks like it's complaining about the CPU temperature reading (i7-3770).

 

[  901.244110] general protection fault: 0000 [#1] SMP
[  901.244815] Modules linked in: xfrm6_mode_transport xfrm4_mode_transport xfrm6_mode_tunnel xfrm4_mode_tunnel xfrm6_mode_beet xfrm4_mode_beet deflate authencesn ipcomp6 ipcomp xfrm6_tunnel xfrm4_tunnel tunnel6 esp6 esp4 ah6 ah4 xfrm_ipcomp af_key xfrm_user xfrm_algo l2tp_ppp l2tp_core pptp gre ppp_deflate bsd_comp ppp_mppe xt_TCPMSS iptable_mangle pppox ppp_async ppp_generic slhc bridge stp aufs macvlan veth xt_conntrack xt_addrtype nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_MASQUERADE xt_REDIRECT xt_nat iptable_nat nf_nat_ipv4 nf_nat xt_recent xt_iprange xt_limit xt_state xt_tcpudp xt_multiport xt_LOG nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack iptable_filter ip_tables x_tables iscsi_target_mod(O) target_core_ep(O) target_core_file(O) target_core_iblock(O) target_core_mod(O)
[  901.255561]  syno_extent_pool(PO) rodsp_ep(O) cifs udf isofs loop hid_generic usbhid hid usblp bromolow_synobios(PO) button ax88179_178a usbnet tg3 r8169 cnic bnx2 vmxnet3 pcnet32 e1000 sfc netxen_nic qlge qlcnic qla3xxx pch_gbe ptp_pch sky2 skge jme ipg uio alx atl1c atl1e atl1 libphy mii btrfs synoacl_vfs(PO) zlib_deflate hfsplus md4 hmac bnx2x(O) libcrc32c mdio mlx5_core(O) mlx4_en(O) mlx4_core(O) mlx_compat(O) compat(O) r8168(O) tn40xx(O) i40e(O) ixgbe(O) be2net(O) igb(O) i2c_algo_bit 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
[  901.265320]  cpufreq_stats freq_table dm_snapshot crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram(C) sg etxhci_hcd mpt3sas mpt2sas(O) megaraid_sas ata_piix mptctl mptsas mptspi mptscsih mptbase scsi_transport_spi megaraid megaraid_mbox megaraid_mm vmw_pvscsi BusLogic usb_storage xhci_hcd uhci_hcd ohci_hcd ehci_pci ehci_hcd usbcore usb_common el000(O) [last unloaded: bromolow_synobios]
[  901.270304] CPU: 0 PID: 23166 Comm: SYNO.Core.Syste Tainted: P         C O 3.10.102 #15152
[  901.271262] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.0.B64.1605280101 05/28/2016
[  901.272563] task: ffff88032fe3a800 ti: ffff8801377f0000 task.ti: ffff8801377f0000
[  901.273421] RIP: 0010:[<ffffffff814a9c84>]  [<ffffffff814a9c84>] mutex_lock+0x4/0x20
[  901.274377] RSP: 0018:ffff8801377f3d08  EFLAGS: 00010246
[  901.275011] RAX: ffff880329f97400 RBX: 0353850f002025d4 RCX: 0000000000000000
[  901.275833] RDX: 000000000000cccc RSI: 0000000000000002 RDI: 0353850f002025d4
[  901.276719] RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
[  901.277566] R10: 000000000000010b R11: 0000000000000246 R12: ffffffff8184e130
[  901.278408] R13: ffff8801377f3d80 R14: 000000000000fa80 R15: 0353850f002025d4
[  901.279243] FS:  00007f59af7db7c0(0000) GS:ffff88033fc00000(0000) knlGS:0000000000000000
[  901.280183] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[  901.280837] CR2: 00007f59a4a4dab0 CR3: 0000000135708000 CR4: 00000000001407f0
[  901.281668] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  901.282488] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  901.283296] Stack:
[  901.283537]  0353850f0020247c ffffffff813793cb 0000000000000000 ffff8801377f3d80
[  901.284452]  00007ffebaa8fe30 ffff8801377f3d80 00007ffebaa8fe30 0000000000000000
[  901.285367]  00007ffebaa94110 ffffffffa0b641ce ffffffffffffffff ffffffffa0b60e27
[  901.286282] Call Trace:
[  901.286574]  [<ffffffff813793cb>] ? syno_cpu_temperature+0xfb/0x1d0
[  901.287300]  [<ffffffffa0b641ce>] ? GetCpuTemperatureDenlowI3Transfer+0xe/0x80 [bromolow_synobios]
[  901.288312]  [<ffffffffa0b60e27>] ? synobios_ioctl+0x4f7/0x10f0 [bromolow_synobios]
[  901.289178]  [<ffffffff811111be>] ? dput+0x1e/0x2a0
[  901.289736]  [<ffffffff811193a3>] ? mntput_no_expire+0x13/0x130
[  901.290409]  [<ffffffff81109b66>] ? path_openat.isra.45+0x146/0x4f0
[  901.291120]  [<ffffffff810d23fe>] ? handle_mm_fault+0x13e/0x2a0
[  901.291798]  [<ffffffff8110ac4f>] ? do_filp_open+0x2f/0x70
[  901.292424]  [<ffffffff811111be>] ? dput+0x1e/0x2a0
[  901.293006]  [<ffffffff8110d07e>] ? do_vfs_ioctl+0x20e/0x880
[  901.293651]  [<ffffffff8110d770>] ? SyS_ioctl+0x80/0xa0
[  901.294249]  [<ffffffff814adf32>] ? system_call_fastpath+0x16/0x1b
[  901.294950] Code: 31 c0 48 8d 74 24 20 4c 89 e7 89 44 24 0c e8 94 5f ba ff 8b 44 24 0c 48 8d 65 d8 5b 41 5c 41 5d 41 5e 41 5f 5d c3 90 53 48 89 fb <f0> ff 0f 79 05 e8 b2 0c 00 00 65 48 8b 04 25 c0 a7 00 00 48 89
[  901.298337] RIP  [<ffffffff814a9c84>] mutex_lock+0x4/0x20
[  901.298972]  RSP <ffff8801377f3d08>
[  901.299484] ---[ end trace 5754f5ee152cbbf1 ]---

 

Share this post


Link to post
Share on other sites

Another thing I've just noticed.. I've just upgraded from DSM 6.0 to 6.1 and every time the VM boots it's status is set as "Recoverable". It's able to repair it every time, but I have no idea why this should happen. Never encountered this on earlier versions of XPenology. 

Share this post


Link to post
Share on other sites

Set the boot drive to dependent, start the vm and recover; after that you can get back and set it as independent.

Share this post


Link to post
Share on other sites
1 hour ago, koroziv said:

Set the boot drive to dependent, start the vm and recover; after that you can get back and set it as independent.

Strange, I've always had the drive as independent without issues. Thanks a lot for the suggestion, seems to have worked! :grin:

Share this post


Link to post
Share on other sites
On 19/08/2017 at 10:11 AM, ikia said:

Hi All 

 

I am on DSM 6.1.2-15132 Update 1 is it safe to update to DSM 6.1.3-15152 that is that I get when I try to check the update status.

 

 

Regards

Igor

I just did it without any problem till now (baremetal)

Share this post


Link to post
Share on other sites

I'm curious.. I know the latest loader isn't compatible with AMD CPU's, but has anyone tried to use a AMD CPU on ESXi and this way get around this limitation?

I wonder if that would actually work or if that also would fail. The reason I ask is because I suppose my i7-3770 to cause the "general protection fault" I've posted above.

 

You would think that ESXi completely virtualizes the CPU and by default it does. However, once you enable passthrough the situation seems to change and the CPU is limited to the instructions it actually supports. It's like enabling passthrough punches a hole in the virtualization layer.... I'll investigate/prove this right or wrong when testing this with other PCI devices in passthrough mode instead of the current LSI SATA controller. So if anyone has tried using AMD on ESXi please let me know. My assumption is that it works well, but breaks horrible once you enable passthrough.

Share this post


Link to post
Share on other sites

I have follow all the instructions with v1.02working great for DS3615xs on bare metal NAS with I3 Kabylake but didn't succes to boot with DS3617xs. If someone know why :smile: ?

 

by the way thank you for all your worker it's never too much to say thanks :smile:

Edited by Noura

Share this post


Link to post
Share on other sites

I am stuck at this level no error message the Synology just not detect with Synology Assistant.

maybe a network drivers issue with ds3637xs img ?

 

my motherboard : Gigabyte H97N-WIFI Carte mère Intel H97 Express Chipset Mini ITX Socket LGA1150

and CPU : Intel Skylake Processeur Core i3-6100 3.7 GHz 3Mo Cache Socket 1151 Boîte (BX80662I36100)

 

Regards

Fichier 23-08-17 22 03 37.jpeg

Share this post


Link to post
Share on other sites

hi dear team!

who can tell me?

why I receive error Fail to format disk (35)

 

I use Ubuntu→Qemu\KVM

mount emulation

- IDE with synoboot.img

- SATA - empty qcow2 image

Edited by boris0n

Share this post


Link to post
Share on other sites

Hello,

 

I have installed Xpenology and updated fine on my HP ML110. 

 

However it runs like like a dream for so many hours and then seems to die?

 

It looses its connection to the disks/raid group and then tells me the DSM page can't be found. 

 

Anyone know why? 

 

Ive tried to stop automatically update because it seems to run all day till the update time. 

 

Thannk

Edited by Simon

Share this post


Link to post
Share on other sites
Another thing I've just noticed.. I've just upgraded from DSM 6.0 to 6.1 and every time the VM boots it's status is set as "Recoverable". It's able to repair it every time, but I have no idea why this should happen. Never encountered this on earlier versions of XPenology. 
because the loader packs a earlier kernel & ramdisk with it, and they are expected to be upgraded to latest version during install or upgrade process. that is how the loader is able to support multiple dsm version, and allows you to apply latest security fix, if kernel version code does not change.

Share this post


Link to post
Share on other sites
19 minutes ago, jun said:
On 8/23/2017 at 0:31 AM, NeoID said:
Another thing I've just noticed.. I've just upgraded from DSM 6.0 to 6.1 and every time the VM boots it's status is set as "Recoverable". It's able to repair it every time, but I have no idea why this should happen. Never encountered this on earlier versions of XPenology. 

because the loader packs a earlier kernel & ramdisk with it, and they are expected to be upgraded to latest version during install or upgrade process. that is how the loader is able to support multiple dsm version, and allows you to apply latest security fix, if kernel version code does not change.

Thanks a lot for the clarification!

I've also managed to get around the "general protection fault: 0000 [#1] SMP" issue when enabling SNMP or visiting the system info page. Seems like disabling the LSI cards BIOS and enabling CPU hotplug in ESXi will do the trick. I can't reproduce the bug anymore and everything works a lot better now.

 

I now get a ton of these in dmesg, but it doesn't seem to do any hard (still trying to figure out how to remove them as well):

[30377.275744] do_IRQ: 0.218 No irq handler for vector (irq -1)

 

Edited by NeoID
  • Like 1

Share this post


Link to post
Share on other sites

I outsourced the info about how to connect easily a VMware ESXi VM to a serial port and how to connect it from a pc in a own thread:

 

Edited by Balrog
make an own thread for the serial port howto

Share this post


Link to post
Share on other sites

I install DS3617xs on HPE ProLiant ML10 Gen9 Server sucsessfuly update to

DSM 6.1.3-15152 Update 3.I have 4 disk 3x 4TB and 1x1TB i want 3x4TB in RAID 5 and 1TB separately.
Herexpenology2JPGpFkMxGy.jpg
 What should I choose?ext4 or btrfs?
Edited by AX4ND3R

Share this post


Link to post
Share on other sites
7 hours ago, AX4ND3R said:

 What should I choose?ext4 or btrfs?

 

So this is really the sort of thing you should educate yourself on and make the best decision for yourself on. I personally went with btrfs, and there are a number of advantages. ext4 is the "4" release superseding ext3, superseding ext2, etc. and so it has that "tried and true" quality. btrfs is the new shiny file system and has a number of technical advantages over ext4, one of the immediate ones being you can create a RAID5 volume from fewer minimum disks than ext4. Maybe read up on it. I suppose one standpoint is, Synology wouldn't release btrfs support if they didn't feel very confident in it. That's the risk, right, that the file system will somehow not protect your data, which seems to be mitigated by Synology supporting it. But that doesn't mean it's right for you. 

 

Cheers.

Share this post


Link to post
Share on other sites

Hi, I’m sorry I know this question has probably been asked a hundred times.

 

How do I upgrade my boot stick to the newest boot loader properly?

 

last time I just wrote over it directly and had to put my pid and vid back in the configuration file and also had to recover the Synology.

 

Is there a proper way to update without losing these settings?

 

cheers

Share this post


Link to post
Share on other sites
On 24/08/2017 at 1:37 AM, NeoID said:

I'm curious.. I know the latest loader isn't compatible with AMD CPU's, but has anyone tried to use a AMD CPU on ESXi and this way get around this limitation?

I wonder if that would actually work or if that also would fail. The reason I ask is because I suppose my i7-3770 to cause the "general protection fault" I've posted above.

 

I'm planning on trying this with a Ryzen 5 1600. From what I can tell the latest ESXi update  (6.5 update 1) supports the zen type cpu with all cores and threads working.

 

I was hoping to pass through the SAS/Sata controller as well - so it looks like I might be stuck using 6.0 either way.

Share this post


Link to post
Share on other sites
On 20-6-2017 at 9:24 AM, carlchan said:

Dear

 

I am using v1.02b 3615xs, in esxi 5.5, I already amend the sn and mac,

Before, it would not show the following error, and all video could view in ds video and ds photo.

"  System failed to convert video [/volume1/photo/.../2016-12-24 chung wedding/20161224 (9).MTS] to mpeg4  "

"  System failed to convert video [/volume1/photo/.../2016-12-24 chung wedding/20161224 (9).MTS] to mpeg4  "

... etc.,

After upgrade to 6.x.x, all video could not be covert, 

Is it due to sn/mac address problem?

 

Thanks!

: >

 

 

I've got the same issue! Is there any solution for this?

I'm on bare metal..

DSM.png

Edited by b0wi
Added system information

Share this post


Link to post
Share on other sites
2 hours ago, b0wi said:

 

I've got the same issue! Is there any solution for this?

I'm on bare metal..

DSM.png

 

Yes, for the moment with a real sn.

Share this post


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.