jun

DSM 6.1.x Loader

Recommended Posts

OK, got it working in ESXI 6.0. I've simply uploaded synoboot.vmdk and synoboot.img files to ESXI datastore and attached synoboot.vmdk as SATA hard disk. I had to add serial port to virtual machine.

 

 

Was this on an already existing (5,2) xpenology VM, or did you create a new VM?

 

:cool:

Share this post


Link to post
Share on other sites

This was on existing xpenology VM, but I've created this VM manually a month ago. I think that it is possible to create a new VM (with serial port), upload and attach your disk image (vmdk + img files). My guest OS type is: Other 3.x or later Linux (64-bit).

Share this post


Link to post
Share on other sites
Finally it is working! =)

VM in Proxmox running DSM 6.0.2-8451 Update 2.

With loader from 1st post from jun all working like a charm. =)

Thank you a lot!

 

 

Can you perhaps explain to me more exactly how you have proceeded under proxmox?

 

How did you convert synoboot.img to qcow2?

Share this post


Link to post
Share on other sites
This was on existing xpenology VM, but I've created this VM manually a month ago. I think that it is possible to create a new VM (with serial port), upload and attach your disk image (vmdk + img files). My guest OS type is: Other 3.x or later Linux (64-bit).

this version try to detect boot partition automatically, so manually built vm can work without change some magic numbers, but this feature is not fully tested

Share this post


Link to post
Share on other sites

Hi,

After writing the latest .img file (the 30/10 one) with Win32DiskImager, I can't access it from my Windows machine in order to edit the grub.cfg file. It just doesn't pop up in the Explorer. Same on my Mac.

 

With the other XPEnoboot img files I didn't have this problem, the USB drive was accessible directly in Windows explorer.

 

Thanks for any help provided.

Share this post


Link to post
Share on other sites
this version try to detect boot partition automatically, so manually built vm can work without change some magic numbers, but this feature is not fully tested

I've connected 3 disks - 2 SCSI disks with DSM 5.2 data and 1 SATA disk with image created by you. It works perfectly on VMware ESXI. I was worried about my virtual SCSI controller (VMware Paravirtual) and virtual network adapter (VMXNET 3), but they both are working fine. Very good job jun! Thanks!

Share this post


Link to post
Share on other sites
Hi,

After writing the latest .img file (the 30/10 one) with Win32DiskImager, I can't access it from my Windows machine in order to edit the grub.cfg file. It just doesn't pop up in the Explorer. Same on my Mac.

 

With the other XPEnoboot img files I didn't have this problem, the USB drive was accessible directly in Windows explorer.

 

Thanks for any help provided.

Just remove the key and plug it again.

:smile:

Share this post


Link to post
Share on other sites
Hi,

After writing the latest .img file (the 30/10 one) with Win32DiskImager, I can't access it from my Windows machine in order to edit the grub.cfg file. It just doesn't pop up in the Explorer. Same on my Mac.

 

With the other XPEnoboot img files I didn't have this problem, the USB drive was accessible directly in Windows explorer.

 

Thanks for any help provided.

Just remove the key and plug it again.

:smile:

 

This is because Jun uses EFI partition table to create the image instead of MBR. You won't be able to see the usb content with Windows 7. With Win 10 you will without any problem. With Mac OS, you will not be able to see the partition as well so you will need to issue the following commands:

diskutil list

this should bring the list of disks available. In my case it's:

/dev/disk0 (internal, physical):
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *640.1 GB   disk0
  1:                        EFI EFI                     209.7 MB   disk0s1
  2:                  Apple_HFS El Cap_TESTING_ENVIR... 214.1 GB   disk0s2
  3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
  4:                  Apple_HFS El Capitan              424.5 GB   disk0s4
  5:                 Apple_Boot Recovery HD             650.0 MB   disk0s5
/dev/disk1 (internal, physical):
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *640.1 GB   disk1
  1:                        EFI EFI                     209.7 MB   disk1s1
  2:                  Apple_HFS Mac 1                   639.8 GB   disk1s2
/dev/disk2 (internal, physical):
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *2.0 TB     disk2
  1:                        EFI EFI                     209.7 MB   disk2s1
  2:                  Apple_HFS Backup_OSX              1000.0 GB  disk2s2
  3:                  Apple_HFS Backup_DATA             999.9 GB   disk2s3
/dev/disk3 (external, physical):
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *4.0 GB     disk3
  1:                        EFI NO NAME                 31.5 MB    disk3s1
  2:           Linux Filesystem                         15.7 MB    disk3s2
  3:        Bios Boot Partition                         4.2 MB     disk3s3

 

find the EFI disk of the USB key. Mine is disk3s1 as you can see above. Then issue:

mkdir /Volumes/efi

followed by

sudo mount -t msdos /dev/disk3s1 /Volumes/efi

 

Note I have used disk3s1 in my last command. Your disk ID might not be the same so pay attention to what you are doing.

Edited by Guest

Share this post


Link to post
Share on other sites
Hi,

After writing the latest .img file (the 30/10 one) with Win32DiskImager, I can't access it from my Windows machine in order to edit the grub.cfg file. It just doesn't pop up in the Explorer. Same on my Mac.

 

With the other XPEnoboot img files I didn't have this problem, the USB drive was accessible directly in Windows explorer.

 

Thanks for any help provided.

Just remove the key and plug it again.

:smile:

 

This is because Jun uses EFI partition table to create the image instead of MBR. You won't be able to see the usb content with Windows 7. With Win 10 you will without any problem. With Mac OS, you will not be able to see the partition as well so you will need to issue the following commands:

diskutil list

this should bring the list of disks available. In my case it's:

/dev/disk0 (internal, physical):
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *640.1 GB   disk0
  1:                        EFI EFI                     209.7 MB   disk0s1
  2:                  Apple_HFS El Cap_TESTING_ENVIR... 214.1 GB   disk0s2
  3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
  4:                  Apple_HFS El Capitan              424.5 GB   disk0s4
  5:                 Apple_Boot Recovery HD             650.0 MB   disk0s5
/dev/disk1 (internal, physical):
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *640.1 GB   disk1
  1:                        EFI EFI                     209.7 MB   disk1s1
  2:                  Apple_HFS Mac 1                   639.8 GB   disk1s2
/dev/disk2 (internal, physical):
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *2.0 TB     disk2
  1:                        EFI EFI                     209.7 MB   disk2s1
  2:                  Apple_HFS Backup_OSX              1000.0 GB  disk2s2
  3:                  Apple_HFS Backup_DATA             999.9 GB   disk2s3
/dev/disk3 (external, physical):
  #:                       TYPE NAME                    SIZE       IDENTIFIER
  0:      GUID_partition_scheme                        *4.0 GB     disk3
  1:                        EFI NO NAME                 31.5 MB    disk3s1
  2:           Linux Filesystem                         15.7 MB    disk3s2
  3:        Bios Boot Partition                         4.2 MB     disk3s3

 

find the EFI disk of the USB key. Mine is disk3s1 as you can see above. Then issue:

mkdir /Volumes/efi

followed by

sudo mount -t msdos /dev/disk3s1 /Volumes/efi

 

Note I have used disk3s1 in my last command. Your disk ID might not be the same so pay attention to what you are doing.

Thanks that was exactly that! I'm indeed using Windows 7. Used the diskutil command on my Mac and it wen through.

Share this post


Link to post
Share on other sites

I want to update my USB key with the last version of this awesome bootloader.

Previously I had removed the SataPortMap function (my NAS is working very well).

 

With the new bootloader I see that this function is set to "1", do I need to delete it or modify it from the "set sata_args" line (I have 6 HDDs)?

 

Thanks in advance!

Share this post


Link to post
Share on other sites
I want to update my USB key with the last version of this awesome bootloader.

Previously I had removed the SataPortMap function (my NAS is working very well).

 

With the new bootloader I see that this function is set to "1", do I need to delete it or modify it from the "set sata_args" line (I have 6 HDDs)?

 

Thanks in advance!

 

Your answer is in the OP. I am quoting it for you:

 

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

Share this post


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

 

can help me out? is this driver issue or config issue?

Share this post


Link to post
Share on other sites

 

Your answer is in the OP. I am quoting it for you:

 

 

You don't say exactly the same thing in your tutorial:

 

Il est fortement recommandé aussi de rajouter le paramètre SataPortMap=[nombre de HDD présent] qui ne se trouve pas par default dans le fichier grub.cfg. Vous pouvez le mettre juste après HddHotplug=0 par example. En fin de ligne ca devrait aussi marcher, à priori, mais je n'ai pas essayé. Les personnes indiquant que le loader marche sans ce paramètre n'ont généralement qu'un seul disque. N'oubliez pas de mettre à jour ce paramètre si vous rajoutez des disques à votre NAS.

 

:grin:

Share this post


Link to post
Share on other sites

 

Your answer is in the OP. I am quoting it for you:

 

 

You don't say exactly the same thing in your tutorial:

 

Il est fortement recommandé aussi de rajouter le paramètre SataPortMap=[nombre de HDD présent] qui ne se trouve pas par default dans le fichier grub.cfg. Vous pouvez le mettre juste après HddHotplug=0 par example. En fin de ligne ca devrait aussi marcher, à priori, mais je n'ai pas essayé. Les personnes indiquant que le loader marche sans ce paramètre n'ont généralement qu'un seul disque. N'oubliez pas de mettre à jour ce paramètre si vous rajoutez des disques à votre NAS.

 

:grin:

 

We both know that this was prior Jun's v.1 new loader which was posted yesterday. Jun has made some major changes to the grub file. I recommend you have a look at it too.

Share this post


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.

 

I've tested your V.1 loader. All went smooth and is working fine so far. Didn't need to fiddle with SataPortMap=

I did add set mac2= in the grub file although not sure that was necessary.

Share this post


Link to post
Share on other sites

using "jun-amd-baremetal-hybrid-uefibios-arcao-v2.img" on a N54L and everything seems to work very well !

 

However 2 "issues" to report :

1) Processor is indicated to be a core i3

2)security issue :

tf6b.png

 

Thank you Jun, Arcao & everyone making this possible !!! :smile:

Share this post


Link to post
Share on other sites

Hi, I can go from 5.1-5022 to 6.0.2 without making another update?

 

I have an HP N40L with 6 HDD, the SataPortMap parameter must be 6 or 42?

 

Thank

Share this post


Link to post
Share on other sites

Apparently, with the very last loader, sata port map is not necessary anymore...

Try without.

If it don't work, try 51, it's what you have to use with a microserver g7 with 5 internal port and 1 esata port.

Share this post


Link to post
Share on other sites

Hi,

 

I found an updated Linux driver solving issue with Marvell 88SE92xx FBS support (e-sata port multiplier) ... https://github.com/freebsd/freebsd/blob ... hci/ahci.c

 

But I've not well understood how Arcao and the other experts managed to update modules/recompile from an external Linux Driver ...

 

Is it possible to include in a future release of kernel/ramdrive the AHCI driver update as listed ?

 

Thanks !

Edited by Guest

Share this post


Link to post
Share on other sites
thank

and I can go from 5.1-5022 to 6.0.2 without making another update?

You need to go to 5.2 first. You can't go directly to 6.0.2 from 5.1.

 

Sent from my SM-N920T using Tapatalk

Share this post


Link to post
Share on other sites
using "jun-amd-baremetal-hybrid-uefibios-arcao-v2.img" on a N54L and everything seems to work very well !

 

However 2 "issues" to report :

1) Processor is indicated to be a core i3

2)security issue :

tf6b.png

 

Thank you Jun, Arcao & everyone making this possible !!! :smile:

oops, so it is indeed better to not replace existing files, maybe I should provide a bugfix v1.01 to fix it

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.