jun

DSM 6.1.x Loader

Recommended Posts

i wanted to try 1.02b on my baremetal (hp gen8 with i3 3220t cpu), 3615xs loader tested and working, 3617xs loader tested and working, 916+ loader not working, hangs on boot:
 

[    0.192870] invalid opcode: 0000 [#1] SMP
[    0.194242] Modules linked in:
[    0.195217] CPU: 1 PID: 1 Comm: swapper/0 Not tainted 3.10.102 #15047
[    0.197217] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 07/16/2015
[    0.199283] task: ffff880200d23510 ti: ffff880200d24000 task.ti: ffff880200d24000
[    0.201473] RIP: 0010:[<ffffffff8148f33e>]  [<ffffffff8148f33e>] sha_transform+0x2e/0x12e0
[    0.203924] RSP: 0000:ffff880200d27d60  EFLAGS: 00010092
[    0.205485] RAX: ffffffff819c2a80 RBX: 0000000010325476 RCX: 00000000e8a4602c
[    0.207646] RDX: ffff880200d27db0 RSI: ffffffff819c2a80 RDI: ffff880200d27d98
[    0.209730] RBP: 00000000c3d2e1f0 R08: 00000000efcdab89 R09: 0000000010325476
[    0.211814] R10: 0000000067452301 R11: 0000000098badcfe R12: 00000000f33d5697
[    0.213886] R13: ffff880200d27e66 R14: 0000000000000286 R15: 0000000000000004
[    0.215986] FS:  0000000000000000(0000) GS:ffff88020ba40000(0000) knlGS:0000000000000000
[    0.218407] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    0.220116] CR2: 0000000000000000 CR3: 000000000180d000 CR4: 00000000001407e0
[    0.222202] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    0.224281] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    0.226362] Stack:
[    0.227048]  0000000000000010 ffffffff81842cc0 ffffffff81842ce4 ffff880200d27e66
[    0.229395]  0000000000000286 0000000000000004 ffffffff812fa652 efcdab8967452301
[    0.231747]  1032547698badcfe 00000000c3d2e1f0 ffffffff81842e10 0000000000000246
[    0.234128] Call Trace:
[    0.234853]  [<ffffffff812fa652>] ? extract_buf+0x62/0x140
[    0.236492]  [<ffffffff810579a5>] ? __wake_up+0x35/0x50
[    0.238091]  [<ffffffff812fa464>] ? account+0x104/0x290
[    0.239617]  [<ffffffff812fab9c>] ? extract_entropy+0x5c/0x170
[    0.241334]  [<ffffffff8115f047>] ? proc_register+0x67/0x140
[    0.242982]  [<ffffffff813e89fb>] ? neigh_hash_alloc+0x7b/0xb0
[    0.244657]  [<ffffffff813e8ab6>] ? neigh_table_init+0x86/0x2b
[    0.325107]  [<ffffffff818a13af>] ? arp_init+0xc/0x47
[    0.348100]  [<ffffffff818a16c0>] ? inet_init+0x18e/0x27a
[    0.349743]  [<ffffffff818a1532>] ? ipv4_offload_init+0x63/0x63
[    0.351496]  [<ffffffff810003aa>] ? do_one_initcall+0xea/0x140
[    0.353222]  [<ffffffff81876dc8>] ? kernel_init_freeable+0x13a/0x1bb
[    0.355053]  [<ffffffff814909f0>] ? rest_init+0x70/0x70
[    0.356589]  [<ffffffff814909f5>] ? kernel_init+0x5/0x180
[    0.358232]  [<ffffffff814a2548>] ? ret_from_fork+0x58/0x90
[    0.359868]  [<ffffffff814909f0>] ? rest_init+0x70/0x70
[    0.361422] Code: 8b 5f 08 44 8b 17 41 56 44 8b 47 04 44 89 d1 41 55 c1 c1 05 41 54 45 8d 23 55 8b 6f 10 41 81 c4 99 79 82 5a 53 8b 5f 0c 41 89 d9 <0f> 38 f0 06 45 31 d9 89 02 45 21 c1 41 c1 c8 02 41 31 d9 41 01
[    0.369569] RIP  [<ffffffff8148f33e>] sha_transform+0x2e/0x12e0
[    0.371349] RSP <ffff880200d27d60>
[   20.207634] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu1

 

Share this post


Link to post
Share on other sites
17 minutes ago, abced said:

Anybody successfully running the DS916 loader? I only see people pisting about DS3615 and DS3617.

i tried, i was interessed to 916 too but doesnt work for me

 

Share this post


Link to post
Share on other sites
35 minutes ago, Haris2887 said:

Do I need to change the Serial number on my fresh install on ESXi ?

 

 

Yes, it's better to keep the same serial number between bootloaders ;)

Share this post


Link to post
Share on other sites
4 hours ago, john_matrix said:

You can flash your USB key to 1.02b the same way you had done with 1.02a ;)

Don't forget to change your serial and mac address in the grub.conf

I understand that will be the way for bare metal installation. I was referring to changing to a loader if my installation was as VM in ESXI 6

I am already on the latest 6.1.1 but I wish to update to the latest 1.02b loader , to be ready for future synology updates

 

Much thanks for help on changing loader for an esxi installation. :smile:

Edited by epicurean

Share this post


Link to post
Share on other sites

For ESXi utilization, you only have to edit the VM settings for pointing the boot device to the new bootloader file (and removing the previous one)

Share this post


Link to post
Share on other sites

What to upgrade to the my version of synology without blowing my system up :).  Currently running dsm DSM 6.0.2-
8451 with Jun 1.01 bootloader.  what would be my safest upgrade path?
 
With the below hardware does it make sense to upgrade to the ds3617xs? or should i stay with ds3615xs?


Hardware
16 GB Ram
2x 3TB WD Red drives
Intel core I7
Mobo: ASRock H97M-ITX/ac
    Intel 97 Chipset
    Qualcomm Atheros AR8171 Lan

 

Thanks.
 

Share this post


Link to post
Share on other sites

I couldn't install the new bootloader. I have a small test-system (MSI Z97i and i3). Following the instructions I get this:

 

After the "Screen will stop updating shortly...." message I have this:

"Trying to terminate EFI services again" and nothing happens

 

What did I do wrong?

Edited by Technic
  • Like 1

Share this post


Link to post
Share on other sites
15 hours ago, Haris2887 said:

Hello All.

I am having trouble ISCSI drives being recognised in ESXi 6.x.

  • I am trying to do RMD mapping for 3 x 2TB Disks that I have as local Disks on an ESXI host . (I don't have a raid card so no pass-through vt-d option)

Creating an RDM Mapping for Local Disk

1.png


vmkfstools -r /vmfs/devices/disks/vml.0100000000202020202057442d574d43333030343931373636574443205744 /vmfs/volumes/datastore1/RDMRed3.vmdk 

2.png

 

Then to see what the created Vmdk looks like 

3.png

 

Nest I just add the VMDk to the esxi VM

4.png

5.png

6.png

 

power On the Vm , all Good

7.png

 

But disks do not show in DSM.

8.png

 

 

 

long story short, I am not sure what else to do , this is a fresh clean install of the latest DMS using the latest loader.

I suspect that SCSI disk are not supported and I must use SATA, can anyone confirm this form me please .

 

 

 

HUm, strange, i did that on 6.5 and no problem...
 

 

Share this post


Link to post
Share on other sites

Hello,

 

I running running dsm DSM 6.0.2-8451 Update 11 with Jun 1.01 bootloader.

Is there a way without data lost to upgrade to a higher version or to a new bootloader and than to a higher version?

 

what would be safe to upgrade?

 

Thanks.

 

Regards,

Michel 

Share this post


Link to post
Share on other sites
9 hours ago, michel30 said:

Hello,

 

I running running dsm DSM 6.0.2-8451 Update 11 with Jun 1.01 bootloader.

Is there a way without data lost to upgrade to a higher version or to a new bootloader and than to a higher version?

 

what would be safe to upgrade?

 

Thanks.

 

Regards,

Michel 

 

That´s what I did last night.

Just for your information I´m running a baremetal Intel machine.

 

My starting point was DSM 6.1.1-15101 Update 4 with Jun 1.02a2 bootloader for ds3617xs.

I placed the new bootloader 1.02b onto my current usb stick, edited the grub.cfg and plugged it back in without updating DSM.

It booted and asked my to "recover" my old installation. This step took 1 or 2 seconds, it then rebooted itself.

DSM came back up just fine. I then went on to upgrade DSM to the latest version 6.1.2-15132. Rebooted and it´s now running peacefully since then.

 

Just to give you guys some feedback.

 

Big thanks to Jun for his amazing loader :-) 

 

Greetz,

Desi

Edited by Designator
Little correction on version numbers

Share this post


Link to post
Share on other sites
On 2017-6-20 at 3:24 PM, 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!

: >

 

 

Anyone could help?

 

Share this post


Link to post
Share on other sites
4 hours ago, Designator said:

 

That´s what I did last night.

Just for your information I´m running a baremetal Intel machine.

 

My starting point was DSM 6.1.1-15101 Update 4 with Jun 1.02a2 bootloader for ds3617xs.

I placed the new bootloader 1.02b onto my current usb stick, edited the grub.cfg and plugged it back in without updating DSM.

It booted and asked my to "recover" my old installation. This step took 1 or 2 seconds, it then rebooted itself.

DSM came back up just fine. I then went on to upgrade DSM to the latest version 6.1.2-15132. Rebooted and it´s now running peacefully since then.

 

Just to give you guys some feedback.

 

Big thanks to Jun for his amazing loader :-) 

 

Greetz,

Desi

 

I just did this on my ESXi 6.0 install which previously failed and now works. Well done again Jun.

 

I simply uploaded the new loader to the datastore overwriting the existing loader, started the VM, recovered then updated.

Share this post


Link to post
Share on other sites
23 hours ago, john_matrix said:

For ESXi utilization, you only have to edit the VM settings for pointing the boot device to the new bootloader file (and removing the previous one)

Sorry for my noobieness, but how exactly do you do that?

Share this post


Link to post
Share on other sites

Used the 1.02b to flash installing DSM in ESXI,

 

I have edit the grub.cfg to add "rmmod=ata_piix",

 

But DSM also can recognize the booting vmdk.

 

Has anyone met and solved this problem?

Share this post


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

Sorry for my noobieness, but how exactly do you do that?

upload the new loader with the same filename to the datastore overwriting the existing loader.

If you want to use a different filename you can download the boot vmdk and edit it e.g. in Notepad++/vim/nano

Share this post


Link to post
Share on other sites

Any body can tell me Jun's v1.02b folder only contain "synoboot.img", how i can create in ESXi??

 

If upgrade using the old verion 6.0.2 vmdk?

Share this post


Link to post
Share on other sites

I'm on 5.2 right now. Can i upgrade to DSM 6.1.2-15132 with v1.02b loader without any intermediate version upgrades?

Share this post


Link to post
Share on other sites

Just reporting that jun's 1.02b loader and the latest 3617xs pat works fine for me on bare metal, a GA X58A-UD3R mobo with 6GB RAM and an i7-930 CPU. 

 

Wrote the image to the stick, changed the vid/pid/sn/MAC (sn using sn generator, MAC using standard Syno first 8 and random last 4) and changed sataportmap to 6, booted, find.synology.com, profit. Thanks for the hard work!

Share this post


Link to post
Share on other sites

anyone know why system not loading when i'm adding new disk in esxi? I see standard boot message from 1.02b loader but syno assistant can't find my box. When i remove that new disk system loading fine. Is there a way to see some debug logging when loading?

Share this post


Link to post
Share on other sites
18 hours ago, Designator said:

 

That´s what I did last night.

Just for your information I´m running a baremetal Intel machine.

 

My starting point was DSM 6.1.1-15101 Update 4 with Jun 1.02a2 bootloader for ds3617xs.

I placed the new bootloader 1.02b onto my current usb stick, edited the grub.cfg and plugged it back in without updating DSM.

It booted and asked my to "recover" my old installation. This step took 1 or 2 seconds, it then rebooted itself.

DSM came back up just fine. I then went on to upgrade DSM to the latest version 6.1.2-15132. Rebooted and it´s now running peacefully since then.

 

Just to give you guys some feedback.

 

Big thanks to Jun for his amazing loader :-) 

 

Greetz,

Desi

Is it worth upgrading to the ds3617xs?

 

I got the folloeing hardware

Hardware
16 GB Ram
2x 3TB WD Red drives
Intel core I7
Mobo: ASRock H97M-ITX/ac
    Intel 97 Chipset
    Qualcomm Atheros AR8171 Lan

 

currently running dsm 6.02-8451

Share this post


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

answeting myself: upgraded without problems

Can you explain how to ? how can i get the new vmdk ?

Share this post


Link to post
Share on other sites
19 hours ago, Designator said:

 

That´s what I did last night.

Just for your information I´m running a baremetal Intel machine.

 

My starting point was DSM 6.1.1-15101 Update 4 with Jun 1.02a2 bootloader for ds3617xs.

I placed the new bootloader 1.02b onto my current usb stick, edited the grub.cfg and plugged it back in without updating DSM.

It booted and asked my to "recover" my old installation. This step took 1 or 2 seconds, it then rebooted itself.

DSM came back up just fine. I then went on to upgrade DSM to the latest version 6.1.2-15132. Rebooted and it´s now running peacefully since then.

 

Just to give you guys some feedback.

 

Big thanks to Jun for his amazing loader :-) 

 

Greetz,

Desi

 

But he asked for an update to the latest, from DSM 6.0.2-8451 Update 11, without data loss. That's not going to happen, as they changed the file system.

Share this post


Link to post
Share on other sites
6 hours ago, hacken said:

Can you explain how to ? how can i get the new vmdk ?

I used starwind v2v converter to convert img file (after i edit grub.cfg and put new sn, mac there) to vmdk disk.

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.