Polanskiman

Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)

Recommended Posts

I created a tutorial for the French section so I thought, what the heck, let's do it for the English one as well. Here it goes.

 

As most of you know by now Jun was able to find a way to install DSM 6 on non Synology boxes. Here is the thread that I recommend reading. At least make an effort and read the OP: https://xpenology.com/forum/topic/6253-dsm-6xx-loader/

 

Below is what you need for the operation. I will assume you are doing all this under Windows 10, 8, 7 or XP. If you are on a MAC computer have a look at this post I made on how to burning the image to a USB drive and then mounting the USB drive for editing the content. The rest of the tutorial still applies.

 

If you are currently using DSM 5.1 or below first update to DSM 5.2. If you are doing a fresh install of DSM 6.0 then carry on with the tutorial and omit references to DSM 5.2.

- Win32 Disk Imager to make a bootable USB drive;

- A 4GB (or any size really) USB drive (flash drive) to install the loader. Not that this is necessary but use preferably a brand name (Kingston, SanDisk...);

- A way to read your USB drive VID/PID. Here is a how-to >>> VID and PID;

- A good text editor: Notepad++ I really don't recommend using Windows's Notepad;

- DSM 6.0.2. The file comes straight from Synology servers;

- Jun's official v1.01 loader (mirror). This is a hybrid UEFI/BIOS loader so it should work in most machines. Loader supports Intel and AMD CPUs;

- Customized extra.lzma ramdisk. This ramdisk is optional and should only be used if the default ramdisk included in the loader is not detecting your hardware. I am just providing it for those who are having issues with network detection or unrecognised HDD controllers. This custom ramdisk contains additional modules (drivers) that were mostly taken from Quicknick's loader. I don't warranty they all work but I think most do. If you chose to use this ramdisk, you will need to replace (or rename, so you can revert) the default extra.lzma ramdisk from Jun's loader with this one. See change log at the end of the tutorial for additional modules.

- Make sure your drives are plugged in direct succession starting from the 1st SATA port. Usually the first port is described as SATA0 on motherboards. Check with your MB manufacturer for exact nomenclature.

OSFMount to modify the grub.cfg file within the loader's image. This is not strictly necessary as Jun has made it possible to configure what needs to be modified via the Grub Boot Menu. I recommend you use OSFMount for now although it adds an extra step. If you prefer using Jun's new feature simply skip Point 5read Note 4 instead and pick up at Point 6.

 

 

PLEASE READ EVERYTHING PRIOR ATTEMPTING ANYTHING

 

Use this loader at your own risk. I wont be held responsible for any loss of data or black smokes that may result in the use of this loader. Please note that this loader is based on DSM 6.0 Beta 2 branch 7274 and that a limited amount of drivers are included in the loader. If it is fundamental for you to have a NAS operating as quick as possible I recommend you look at the included drivers first at the bottom of this tutorial. If they are not there you will have to compile your own drivers.

One last thing:

:!:DO NOT UPDATE DSM BEYOND VERSION 6.0.2 (6.0.3, 6.1, 6.1.1, 6.1.2, 6.1.3 etc) with loader v1.01.:!:

You have been warned.

 

Here we go:

 

1 - BACKUP your data and save your configuration prior any attempts to migrate from DMS 5.2 to DSM 6.0.2. I can't stress this enough. JUST DO IT, as Nike likes to say. Also, print this tutorial if you can. It will make your life easier.

 

2 - Turn off your NAS and unplug the USB drive you are currently using with DSM 5.2. I recommend you put this USB drive aside in case migration to DSM 6.0.2 doesn’t go as expected and you need to revert to DSM 5.2. It will just make your life easier.

 

3 - Now go to your workstation/PC, plug a new USB drive (or the old one if you really don’t have any spare USB drives). Use the link I provided earlier to check your USB drive VID/PID. Write down the info somewhere as we will need it later.

 

4 - Unzip the loader you downloaded earlier. You will end up with a folder containing several files. Since we are installing on bare-metal you will only need the image file "synoboot.img". 

 

5 - Now launch OSFMount. Select Mount New, then select the image file (i.e. synoboot.img) to open. Now select partition 0 (the one that is 30 MB). Click Ok. Then at the bottom of the window make sure to un-tick the "Read only drive". Click Ok. The EFI partition of the image file should now be mounted in file explorer.

At this point you can navigate to the /image/DS3615xs directory and replace the extra.lzma ramdisk with the one provided above. When you are done come back to the root directory and go to the /grub directory and edit the grub.cfg file. Below is what you will see in the file.

 

I am only showing below the portion of the code that is relevant for the purpose of this tutorial

[...]

set extra_initrd="extra.lzma"
set info="info.txt"

set vid=0x058f
set pid=0x6387
set sn=C7LWN09761
set mac1=0011322CA785
set rootdev=/dev/md0
set netif_num=1
set extra_args_3615=''

set common_args_3615='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet'

set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=1 SasIdxMap=0'

set default='0'
set timeout='1'
set fallback='1'

[...]
 

 

:!: You want to modify the following: :!:

 

Change vid=0x090C to vid=0x[your usb drive vid]

Change pid=0x1000 to pid=0x[your usb drive pid]

Change sn=C7LWN09761 to sn=generate your sn here with DS3615xs model

Change mac1=0011322CA785 to mac1=[your NIC MAC address]. You can also add set mac2=[your NIC MAC address #2] and so on until mac4 if you have multiple NICs. However, this is not necessary.

Optional: Change set timeout='1' to set timeout='4' - This will allow you more time to make a selection in the Grub Boot Menu when it appears. 

 

Once you are done editing the grub.cfg file, save it and close your text editor. Now in OSFMount click on Dismount all & Exit.

You are now ready to burn the image to your USB drive.

 

6 - Now use Win32 Disk Imager to burn the image file onto the USB drive. This will also make the USB drive bootable.

 

7 - Eject and unplug the USB drive from your workstation. Plug it in your NAS (avoid USB 3.0 ports. Use USB 2.0 port if available). Boot your NAS and before doing anything fancy, access your BIOS so to make your USB drive the 1st boot drive if it's not the case. The loader can boot in UEFI or in legacy BIOS, so you chose what suits you best. Also, make sure your HDDs are booting in AHCI mode and not in IDE, else it wont work. Finally, if disabled, also enable the serial port in BIOS. Some BIOS don't have this option so don't get too cranky on this if you can't find it. Save changes to the BIOS and REBOOT the NAS.

 

8 - Once rebooted, if you have a monitor connected to your NAS you will see the following Grub Boot Menu:

95WsOj3.jpg

If you are on an Intel based machine you can simply let it be and the loader will automatically start. However, if you are on a AMD based machine you will need to select the 4th line and then press enter. ADVICE: even before you see the Grub Boot Menu press the up/down key. This will stop the countdown so you will be able to select the desired line. You won’t see much other than the following after you press enter:

3IVfKcu.jpg

If you booted the USB drive in EFI mode then you will see the same text without the last 3 lines but that's ok.

 

9 - Now go back to your workstation, and launch Synology Assitant or go to http://find.synology.com. Within one minute or so you should normally be able to see your NAS on the local network (it took 55 seconds on a test I did on a VM). Just follow the instructions and either chose "Install" if you wish to have a clean install or chose “Migration” if you are coming from DMS 5.2 and wish to update while retaining your data. You will be asked to provide the .PAT file you downloaded earlier (DSM_DS3615xs_8451.pat).

 

10 - When the migration is finished you will most probably have to update some of your packages. You can then proceed and update DSM 6.0 up to DSM 6.0.2-8451 update 11. It is possible you might either need to hard reboot or re-image your usb drive. DO NOT UPDATE DSM TO VERSIONS 6.0.3, 6.1, 6.1.1 or 6.1.2 with loader v1.01. Make sure to deactivate auto-updates within DSM.

 

11 - You are done. If you have questions, first search the forum and/or Google then leave a comment if nothing helps. Please provide your hardware specifications (motherboard model, LAN controller, driver controller etc). Failure to prove such information will lead to the post being deleted. Click the 'Like this' button if you liked the tutorial.

 

--------------

Note 1: If after following the tutorial you can’t find your NAS through http://find.synology.com ou Synology Assistant it is highly possible that the drivers of your NIC are not included in the ramdisk of the loader. Make an effort and use Google to know what modules your NIC and HDD controller are using, then check if those modules are included in the custom extra.lzma ramdisk. If yes then use the custom ramdisk. Don't ask me to look for you. If nothing works then ask your question.

 

Note 2: Synology increased security in DSM 6. Root access through SSH is no longer available out of the box. You can however use your admin account and elevate permissions with the following command

sudo -i
 

Note 3: Please check you have the right VID/PID prior proceeding. If you get the following error ”Failed to install the file. The file is probably corrupted. (13)" it means your VID and/or PID is wrong. If you are 200% sure that your VID/PID is correct and you still get that error message then try to 'Force Install'. If that doesn't work then try another USB drive.

 

Note 4: Changes made to the grub.cfg file can also be done directly during the Grub Boot Menu, so technically you can skip Point 5 and burn the image on the USB drive without editing anything (read Point 6 onward first). If you wish to do the changes from the Grub Boot Menu directly you need to press the letter 'C' when you see the Boot Menu. You will literally only have one second, so be fast. Once you press C you will be in a Grub command line environment. To change your VID enter the following:

vid 0xYOUR 4 DIGITS USB DRIVE VID
 

Do the same for pid, sn and mac1. Press enter at each command. The commands are:

pid 0xYOUR 4 DIGITS USB DRIVE PID
sn YOUR NAS SERIAL NUMBER
mac1 YOUR NAS MAC1 ADDRESS
 

If you have multiple NICs you can also issue mac2, mac3 and mac4 as commands. Maximum is mac4. See below:

mac2 YOUR NAS MAC2 ADDRESS
mac3 YOUR NAS MAC3 ADDRESS
mac4 YOUR NAS MAC4 ADDRESS
 

 

If you think you made a mistake in the numbers simply re-issue the command. When you are done press esc and select the appropriate menu entry. Below is an example of how it looks under the Grub command line environment:

 

WYEIN2f.jpg

 

Note 5: If your encounter the error "We've detected errors on your hard drives [drive number] and the SATA ports have also been disabled" during installation, try the Force Install menu entry in the Grub Boot Menu. If this does not work then you have to fallback to adding SataPortMap to the grub environment. Press the letter 'C' at the Grub Boot Menu and then add the following:

 

append SataPortMap=XX
 

where XX is the number of drives. Don’t forget to update this parameter if you add additional drives to your machine.

If you use Force Install, don't forget to re-select the first line of the Boot Menu once the NAS has rebooted after the installation else the Loader will re-select Force Install and you will be faced with some issues so please beware of this.

 

@@@@@@@@ What does SataPortMap mean? @@@@@@@

setsunakawa said:

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 controler.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

 

############## Know issues #####################

- When running on a slow single core machine, there is a race condition that causes the patcher to load too late. The most obvious sign is that console is not working properly.

- Some ethernet drivers crash when set MTU above about 4096 (Jumbo frame).

 

############# Included default modules in Jun's Loader #############

Change log - Trantor » 23 Oct 2016 20:50 - Click HERE 

Original Post

Updated broadcom tg3, bnx2, bnx2x, cnic
Updated intel e1000e (I219 support)
Add/Updated realtek r8168, r8169 and r8101 (r8169 from realtek website no the one inside the kernel tree)

Hide  

 

Change log - Arcao » 25 Oct 2016 20:22 - Click HERE 

Original Post

Added below kernel modules:
r8101: RTL8100E/RTL8101E/RTL8102E-GR/RTL8103E(L) RTL8102E(L)/RTL8101E/RTL8103T RTL8401/RTL8401P/RTL8105E RTL8402/RTL8106E/RTL8106EUS
r8168: RTL8111B/RTL8168B/RTL8111/RTL8168 RTL8111C/RTL8111CP/RTL8111D(L) RTL8168C/RTL8111DP/RTL8111E
r8168: RTL8168E/RTL8111F/RTL8411 RTL8111G/RTL8111GUS/RTL8411B(N) RTL8118AS
* Note: r8169 from Trantor archive doesn't work with my on-board Realtek RTL8111GR. So I kept the existing which is also much bigger.

e1000e: 82573L/82572EI/82571EB/82573E/82573V/82567/82574L/82566MM/82566MC
e1000e: 82566DM/82566DC/82563EB/82574IT/82583V/82579LM/82579V/82577LC/82577LM
e1000e: 82578DC/82578DM/Gigabit CT Desktop Adapter/PRO/1000 PT/PF/I217-LM/V/I218-V/LM/I219 LM/V

bnx2: Broadcom NetXtremeII BCM5706/BCM5708/5709/5716
bnx2x: Broadcom NetXtremeII 10Gb BCM57710/BCM57711/BCM57711E/BCM57712
tg3: Broadcom Tigon3 BCM5705/BCM5703/BCM5702/BCM5701/BCM5700/BCM5721/BCM5751/BCM5788/BCM5704/BCM5752/BCM5789
tg3 : BCM5723/BCM5761/BCM5787/BCM5755/BCM5722/BCM5754/BCM57781/BCM57785/BCM5718BCM57765/BCM57761
tg3: BCM5719/BCM5725/BCM5762/BCM5720/BCM57790/BCM57795/BCM57766/BCM57780
* Note: Existing modules updated with version from Trantor archive. I also added missing firmware files.

ax88179_178a : ASIX AX88179/178A USB 3.0/2.0 to Gigabit Ethernet

mpt2sas: LSI SAS 6Gb/s Host Adapters SAS2004, SAS2008, SAS2108, SAS2116, SAS2208, SAS2308 and SSS6200
* Note: It's already included in existing ramdisk but not loaded. By dmesg it's started correctly.

evdev, button: for acpid

Hide  

 

Change log - Arcao » 28 Oct 2016 10:47 - Click HERE 

Original Post

* Fixed loading modules after installation step and upgrading from previous ramdisk version
* Fixed order of loading kernel modules (cause not loading cnic)

--------------------------------------------------------------------------------
Recompiled kernel modules:

r8169: r8169-6.022.00 sources
* Note: Compiled by Trantor

igb: igb-5.3.5.4 sources
ixgbe: ixgbe-4.4.6 sources
* Note: Compiled from latest sources at intel.com

megaraid_sas: megaraid_sas-06.812.07.00 sources
mpt2sas: mpt2sas-20.00.04.00 sources
* Note: Compiled from latest sources at lsi.com/avagotech.com

--------------------------------------------------------------------------------
Added kernel modules:

mpt3sas: mpt3sas-14.00.00.00 sources
* Note: Compiled from latest sources at lsi.com/avagotech.com

ftdi_sio, cp210x, ch341, pl2303
* Note: ftdi_sio is compiled by Synology, others are compiled from 7274 kernel sources

Hide  

 

############# Additional modules in the custom extra.lzma ramdisk #############

Change log - Click HERE 

3c59x.ko
3w-9xxx.ko
3w-sas.ko
3w-xxxx.ko
8021q.ko
8139cp.ko
8139too.ko
a100u2w.ko
aacraid.ko
advansys.ko
ahci_platform.ko
aic79xx.ko
aic7xxx.ko
aic94xx.ko
amd8111e.ko
ata_generic.ko
atl2.ko
atp870u.ko
b44.ko
broadcom.ko
caif.ko
catc.ko
ch.ko
cn.ko
crc-ccitt.ko
crc-itu-t.ko
cxgb.ko
cxgb3.ko
cxgb4.ko
dl2k.ko
dm-log.ko
dm-mirror.ko
dm-region-hash.ko
dummy.ko
forcedeth.ko
gf128mul.ko
isci.ko
iscsi_boot_sysfs.ko
isp116x-hcd.ko
isp1362-hcd.ko
isp1760.ko
kaweth.ko
macvlan.ko
mlx4_core.ko
mlx4_en.ko
mpt2sas.ko
mvsas.ko
mvumi.ko
nvme.ko
pata_ali.ko
pata_amd.ko
pata_artop.ko
pata_atp867x.ko
pata_cmd64x.ko
pata_hpt366.ko
pata_hpt37x.ko
pata_hpt3x2n.ko
pata_hpt3x3.ko
pata_it8213.ko
pata_it821x.ko
pata_jmicron.ko
pata_marvell.ko
pata_netcell.ko
pata_ninja32.ko
pata_oldpiix.ko
pata_pdc2027x.ko
pata_pdc202xx_old.ko
pata_rdc.ko
pata_sch.ko
pata_serverworks.ko
pata_sis.ko
pata_via.ko
pdc_adma.ko
pegasus.ko
pm80xx.ko
qla1280.ko
r8152.ko
rng-core.ko
rtl8150.ko
sata_highbank.ko
sata_inic162x.ko
sata_nv.ko
sata_promise.ko
sata_qstor.ko
sata_sil.ko
sata_sis.ko
sata_svw.ko
sata_sx4.ko
sata_uli.ko
sata_via.ko
sata_vsc.ko
sc92031.ko
scsi_transport_srp.ko
sis190.ko
ssb.ko
stex.ko
sundance.ko
sym53c8xx.ko
udf.ko
via-velocity.ko
zlib_deflate.ko
zlib.ko

Hide  

 

############## Tutorial UPDATES ##################

Change log - Click HERE 

[30/10/2016] Jun loader updated to version v1.0. This loader now supports AMD
[03/11/2016] Jun's loader updated to version v1.01
[18/11/2016] Overhaul of the tutorial to reflect new features and fixes in the loader
[19/11/2016] Minor edits and clarifications
[20/11/2016] Minor edits + added link on how to burn & mount image in MAC OS. 3rd Paragraph
[05/12/2016] Added note about SATA0. Modified/improved warning + detailed note 5 (Force Install)
[09/12/2016] Title changed from "Tutorial: Migrate from DSM 5.2 to 6.0 - Baremetal" to "Tutorial: Install/Migrate DSM 5.2 to 6.0 (Jun's loader)"
[19/01/2017] Point 10. Added following comment: "Update 9 seems to be causing some issues, so stay on update 8 until further notice"
[20/01/2017] Minor edits
[30/01/2017] Note 5 clarified
[22/02/2017] Edit Warning message due to inaccuracy: DSM 6.0.2 Beta branch 7274 to DSM 6.0 Beta 2 branch 7274
[23/02/2017] Point 10. Added following comment: DO NOT UPDATE DSM TO VERSION 6.1.
[27/02/2017] Trantor added a mirror to loader
[02/03/2017] Link to Loader updated
[08/03/2017] Added following comment to Warning message: DO NOT UPDATE DSM TO VERSION 6.1 with loader v1.01 + Minor edits
[24/04/2017] Point 10. You can update to Update 11
[28/04/2017] Do not update to DSM 6.1.1
[09/05/2017] Do not update to DSM 6.0.3
[12/05/2017] Added link to serial generator & clarification about MAC address
[19/05/2017] Added custom extra.lzma ramdisk link + how to replace ramdisk in loader + ramdisk change log + additional minor edits
[28/05/2017] Updated custom ramdisk -- broadcom.ko module was not loading due to module not being mentioned in to rc.modules
[18/06/2017] Updated tutorial links to new forum platform
[21/06/2017] Do not update to DSM 6.1.2 + Title changed from "Tutorial: Install/Migrate DSM 5.2 to 6.0 (Jun's loader)" to "Tutorial: Install/Migrate DSM 5.2 to 6.0.2 (Jun's loader)"
[21/08/2017] Modified warning message: DO NOT UPDATE DSM BEYOND VERSION 6.0.2 (6.0.3, 6.1, 6.1.1, 6.1.2, 6.1.3 etc) with loader v1.01. + minor edits
[03/09/2017] Temporarily removed custom ramdisk
[10/09/2017] Removed 'amd-rng.ko', 'via-rng.ko' and 'pata_atiixp.ko' modules from custom extra.lzma ramdisk. All modules were failing and 'pata_atiixp.ko' was cause a kernel panic.
[15/09/2017] "[...] Please provide your hardware specifications (motherboard model, LAN controller, driver controller etc). Failure to prove such information will lead to the post being deleted. Click the 'Like this' button if you liked the tutorial."

Hide  
Edited by Polanskiman
See Tutorial UPDATES log above ^
  • Like 4

Share this post


Link to post
Share on other sites

I have some questions.

 

1. I have a Xpeno Nas DSM 5.2 currently running on bare metal AMD PC. Can I migrate to DSM 6.0?

2. I saw your instruction how to setup SataPortMap. It's useful.

I'm however just confused how we call which one is controller 1, 2, 3, blah..blah... :oops:

let say I have a mobo that has 3 sata ports. I attached 2 more sata cards that has 2 ports and the other 4 ports to build my 9 HDDs nas. So, in this case, which one should I setup for SataPortMap?

It should be SataPortMap=234, SataPortMap=243, SataPortMap=324, SataPortMap=342, SataPortMap=432, or SataPortMap=423?

An extra question. What if I set it wrong?

3. What's wrong if I use Windows Notepad instead of Notepad++ to edit grub.cfg?

4. Because the value "console=ttyS0,115200n8" is unique, people don't have to change console=uart,io,0x3f8,115200n8 to console=ttyS0,115200n8 if you originally changed and posted?

 

Finally, thank you very much for the tutorial. It helps me as a newbie a lot.

Share this post


Link to post
Share on other sites
I have some questions.

 

1. I have a Xpeno Nas DSM 5.2 currently running on bare metal AMD PC. Can I migrate to DSM 6.0?

 

The new loader doesn't work with AMD based mother boards at the moment. It would require the kernel to be recompiled from the source. That can't be done because the source isn't available. The new system is a Dynamic patch and it can only work based on the core of the kernel which is Intel based. That's my understanding of how things stand at present using Jun's method and the associated derivatives.

 

AMD is now supported.

Edited by Guest

Share this post


Link to post
Share on other sites

No not that I'm aware of. My first install was a migration from 5.2 to with shr and the shr was recognised in DSM 6 no problem. After that I did a fresh install on the same box and by default shr isn't an option under DSM 6. You can edit the config file to re-enable shr which works perfectly. I have drives using shr with btrfs on the new DSM 6 build. I can't say for sure about shr 2 as I have no first hand knowledge, but my guess would be that it should be fine. I'm not sure if a migrated system would allow a new disk group/volume to use shr by default, but editing the config file should soon fix that problem.

Share this post


Link to post
Share on other sites
No not that I'm aware of. My first install was a migration from 5.2 to with shr and the shr was recognised in DSM 6 no problem. After that I did a fresh install on the same box and by default shr isn't an option under DSM 6. You can edit the config file to re-enable shr which works perfectly. I have drives using shr with btrfs on the new DSM 6 build. I can't say for sure about shr 2 as I have no first hand knowledge, but my guess would be that it should be fine. I'm not sure if a migrated system would allow a new disk group/volume to use shr by default, but editing the config file should soon fix that problem.

That sounds good to hear. Thank you for the information. I'll need to do some testing myself as YMMV of course. How would one edit the config file for SHR? You said soon so I'm guessing it's not possible as of now?

Share this post


Link to post
Share on other sites
I have some questions.

 

1. I have a Xpeno Nas DSM 5.2 currently running on bare metal AMD PC. Can I migrate to DSM 6.0?

2. I saw your instruction how to setup SataPortMap. It's useful.

I'm however just confused how we call which one is controller 1, 2, 3, blah..blah... :oops:

let say I have a mobo that has 3 sata ports. I attached 2 more sata cards that has 2 ports and the other 4 ports to build my 9 HDDs nas. So, in this case, which one should I setup for SataPortMap?

It should be SataPortMap=234, SataPortMap=243, SataPortMap=324, SataPortMap=342, SataPortMap=432, or SataPortMap=423?

An extra question. What if I set it wrong?

3. What's wrong if I use Windows Notepad instead of Notepad++ to edit grub.cfg?

4. Because the value "console=ttyS0,115200n8" is unique, people don't have to change console=uart,io,0x3f8,115200n8 to console=ttyS0,115200n8 if you originally changed and posted?

 

Finally, thank you very much for the tutorial. It helps me as a newbie a lot.

 

I've uploaded a patched kernel for AMD users on the original post, but its not tested at the moment, you could have a try if you are brave enough :grin:

Share this post


Link to post
Share on other sites

 

I've uploaded a patched kernel for AMD users on the original post, but its not tested at the moment, you could have a try if you are brave enough :grin:

 

Thanks Jun. Was going to mention that but you were faster!

Share this post


Link to post
Share on other sites

 

I've uploaded a patched kernel for AMD users on the original post, but its not tested at the moment, you could have a try if you are brave enough :grin:

 

Thanks Jun. Was going to mention that but you were faster!

 

I am waiting for volunteers :grin: .

BTW, good tutorial, this would help many people.

Share this post


Link to post
Share on other sites

 

I've uploaded a patched kernel for AMD users on the original post, but its not tested at the moment, you could have a try if you are brave enough :grin:

 

Thanks Jun. Was going to mention that but you were faster!

 

I am waiting for volunteers :grin: .

BTW, good tutorial, this would help many people.

 

Thanks, hopefully it will alivate your thread from basic questions that can be answered here. I think I saw one person who tried your new bzimage in your thread. It seems it was successful. I was going to try it myself but I am lacking a hardrive. I'll put my hands on one that I have in the office next week.

Share this post


Link to post
Share on other sites

What about running DSM6 under ESXi ? I read things about a USB-stick, but with ESXi this wouldn't be the case.

Can someone tell me what steps are different when running DSM 6 through ESXi (6u2)?

Share this post


Link to post
Share on other sites
What about running DSM6 under ESXi ? I read things about a USB-stick, but with ESXi this wouldn't be the case.

Can someone tell me what steps are different when running DSM 6 through ESXi (6u2)?

 

I recommend you go to the main thread. There is a specific loader for esxi and some people have sucessfully used it I beleive.

Share this post


Link to post
Share on other sites

I managed to figure it out, installing DSM 6.0.2.-8451 on my ESXi 6u2 host:

 

- Used the loader from here

- Extracted the .zip, uploaded the .ovf to my ESXi server

- Edited the VM, added a serial port (physical port on the host)

- You now need to add a virtual disk, or your real HDD's. I used PCI-Passthrough to passthrough my 2x 2TB RAID1 connected to a ASM1061 card

- Start the VM

- Use Synology Assistant to find the XPEnology

- Use the DSM_DS3615xs_8451.pat file to install. It didn't touch my data disks

- DSM is now installed, it recognized the RAID1-array from my DS715 (sold) and also the shared folders. Nice!

 

Still some questions:

  • DSM says an update to '6.0.2-8451 Update 2' is available. I clicked the install button in DSM, but after a reboot i am welcomed by the setup wizard again (where you configure an administrator account, QuickConnect and such. When finishing that wizard, it is still on 6.0.2-8451. How do i upgrade to '6.0.2-8451 Update 2' ?
  • DSM seems to work fine now, however i didn't change the serialnumber or MAC-address during the installation. Should i have done that, or is it fine this way?The MAC-adress is seen by my router as 00:11:32:XX:XX:XX, so that is set already to the correct Synology format by the .ovf i guess. But what about the serial number?

Share this post


Link to post
Share on other sites
imaleecher said:

That sounds good to hear. Thank you for the information. I'll need to do some testing myself as YMMV of course. How would one edit the config file for SHR? You said soon so I'm guessing it's not possible as of now?

 

You can find the answer here > https://xpenology.com/forum/topic/6253-dsm-6xx-loader/?do=findComment&comment=55037

Share this post


Link to post
Share on other sites

Official version 1 of Jun loader has been released.

 

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.
    > Remembers last boot entry.
    > Autodetects 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.
    > Adds grub menu for reinstallation.
    > Adds grub menu to force installation when interrupted due to "Disks Disabled" message, not extensively tested
    > Automatically applies workaround for boards without serial port.
    > Fixes SATA disk order remap, and allow to set SAS disk starting no, but disk order are still not deterministic between SAS disks.
    > Fixes SAS disk naming, not extensively tested, only with one SAS2008 based HBA and synology provided mpt2sas driver.
    > Adds 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 do 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

Note to all

 

Jun's new Loader v.1 implies lots of changes to the tutorial. If fact it will be simplified. I will update it once I have some time. In the meantime, if you have a INTEL CPU machine can you still use Arcao's Loader v.2 which works fine.

 

However, if you have an AMD machine you will be forced to use Jun's v.1 loader as it's the only one presently that supports AMD. Here are some instructions written by Jun himself on the OP of his thread >>> https://xpenology.com/forum/topic/6253-dsm-6xx-loader/?do=findComment&comment=54156

 

I have already tried Jun's v.1 loader and is working fine on my machine.

Share this post


Link to post
Share on other sites

Thank you Jun and everyone that’s worked on the new loader.

 

After failing miserably over the past few weeks with the earlier loaders (Jun, setsunakawa), I was finally able to create a baremetal install with Arcao's loader. I’m guessing it finally had the drivers I needed.

 

Except for a brief mention by hotshots on page 85, I haven't seen any mention of hibernation issues. Does the current loader allow for HDD hibernation and auto poweroff?

 

Hibernation and auto poweroff worked fine for me in DSM 5.2-5644 and previous loaders. It stopped working in the 5.2-5967 updates (it was a known issue).

 

Has the 5.2-5967 hibernation issue carried over to the DSM 6 loader? OR is it just me and hotshots?

 

Polanskiman: Appreciate your effort in creating an up-to-date tutorial on using Jun’s loader.

 

I’m just wondering if any of the additional modifications (after vid and pid edits, etc.) that were suggested for the the 5.2 xpenology installs can be included in your tutorial? Controlling the CPU power state and the power off button issue for example. Possible to include up-to-date links and newer(?) instructions if any?

 

Or should we forgo these for the moment?

 

Thanks

Share this post


Link to post
Share on other sites

Totally agreed with Faro.

So far, we haven't had tutorial about

1. HDD hibernation/ auto power off.

2. Power off button.

3. CPU power state.

 

I appreciate if someone spends his hard time to write it down here.

Thanks.

Share this post


Link to post
Share on other sites
Faro said:
Thank you Jun and everyone that’s worked on the new loader.

 

After failing miserably over the past few weeks with the earlier loaders (Jun, setsunakawa), I was finally able to create a baremetal install with Arcao's loader. I’m guessing it finally had the drivers I needed.

 

Except for a brief mention by hotshots on page 85, I haven't seen any mention of hibernation issues. Does the current loader allow for HDD hibernation and auto poweroff?

 

Hibernation and auto poweroff worked fine for me in DSM 5.2-5644 and previous loaders. It stopped working in the 5.2-5967 updates (it was a known issue).

 

Has the 5.2-5967 hibernation issue carried over to the DSM 6 loader? OR is it just me and hotshots?

 

Polanskiman: Appreciate your effort in creating an up-to-date tutorial on using Jun’s loader.

 

I’m just wondering if any of the additional modifications (after vid and pid edits, etc.) that were suggested for the the 5.2 xpenology installs can be included in your tutorial? Controlling the CPU power state and the power off button issue for example. Possible to include up-to-date links and newer(?) instructions if any?

 

Or should we forgo these for the moment?

 

Thanks

 

Power button info is here > https://xpenology.com/forum/topic/6253-dsm-6xx-loader/?do=findComment&comment=55463 afaik that's still current but things are moving so fast things my have changed. Don't extract the zip in the root copy the files up individually and set executable for scripts.

 

Power Save seems to work out of the box. On my system the governor is set to performance rather than power save/conservative. I used the old method to set power save. That's because I couldn't find the file to set the governor state in the default build.

 

WOL works once you add the shutdown fix and make it executable. Note rc.d has moved in DSM 6 it's now in /usr/local/etc/rc.d.

Edit: You need to use the MAC that you used in the grub config.

 

You can get SHR functionality back and use btrfs. This post gives some detail but it's now out of date in some respects > https://xpenology.com/forum/topic/6253-dsm-6xx-loader/?do=findComment&comment=55037 .

Share this post


Link to post
Share on other sites
Thank you Jun and everyone that’s worked on the new loader.

 

After failing miserably over the past few weeks with the earlier loaders (Jun, setsunakawa), I was finally able to create a baremetal install with Arcao's loader. I’m guessing it finally had the drivers I needed.

 

Except for a brief mention by hotshots on page 85, I haven't seen any mention of hibernation issues. Does the current loader allow for HDD hibernation and auto poweroff?

 

Hibernation and auto poweroff worked fine for me in DSM 5.2-5644 and previous loaders. It stopped working in the 5.2-5967 updates (it was a known issue).

 

Has the 5.2-5967 hibernation issue carried over to the DSM 6 loader? OR is it just me and hotshots?

 

Polanskiman: Appreciate your effort in creating an up-to-date tutorial on using Jun’s loader.

 

I’m just wondering if any of the additional modifications (after vid and pid edits, etc.) that were suggested for the the 5.2 xpenology installs can be included in your tutorial? Controlling the CPU power state and the power off button issue for example. Possible to include up-to-date links and newer(?) instructions if any?

 

Or should we forgo these for the moment?

 

Thanks

 

Totally agreed with Faro.

So far, we haven't had tutorial about

1. HDD hibernation/ auto power off.

2. Power off button.

3. CPU power state.

 

I appreciate if someone spends his hard time to write it down here.

Thanks.

 

 

For now I will focus on the DMS upgrade process. When the loader updates have stabilised a bit I will include other upgrade options once they become available and are tested by others. I don't want to keep changing the tutorial every two days or so because new loaders keep coming out nearly on a daily basis and some features could very well be impacted by these loader updates.

Share this post


Link to post
Share on other sites
this work fine on my HP proliant micro gen 8. standard.

 

but!

 

sonologys antivirus tells me that there is fiddled with some file, eventhough I havent installed any 3 part. only a couple of sonology apps.

 

have some of you seen the same ??

 

https://s16.postimg.org/t4pzoiwpx/Clipboard02.jpg

Jun have updated some drivers; you can safely ignore that message. He wrote that he will fix this when he has time.

Share this post


Link to post
Share on other sites
For now I will focus on the DMS upgrade process. When the loader updates have stabilised a bit I will include other upgrade options once they become available and are tested by others. I don't want to keep changing the tutorial every two days or so because new loaders keep coming out nearly on a daily basis and some features could very well be impacted by these loader updates.

 

Thanks. Probably best for now.

 

On the upside, WOL is working without a problem (internal network) and my baremetal now keeps the correct time, which it never did in the previous 5-5.2 Xpenology installs.

Share this post


Link to post
Share on other sites
this work fine on my HP proliant micro gen 8. standard.

 

but!

 

sonologys antivirus tells me that there is fiddled with some file, eventhough I havent installed any 3 part. only a couple of sonology apps.

 

have some of you seen the same ??

 

https://s16.postimg.org/t4pzoiwpx/Clipboard02.jpg

Jun have updated some drivers; you can safely ignore that message. He wrote that he will fix this when he has time.

 

ok np.

happy for your work JUN. :grin::grin::grin:

 

it running very good here on my HP proliant micro gen8. Have edited the serial/mac in ( by assigning the usb a letter and using explorer++ to edit grub ) som quickconnect works. and HDD spindown work.. everything works mutch better.

:mrgreen:

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now