Tutorial: Install/Migrate DSM 5.2 to 6.1.x (Jun's loader)

[polanskiman]

This is an updated tutorial version from the one I made last year. It will enable you to migrate from DSM 5.2 to DSM 6.1.7 directly without the need to upgrade to DSM 6.0.2 first. If for some reason you want to upgrade to DSM 6.0.2 first or simply you do not want to upgrade to DSM 6.1.7 but only to DSM 6.0.2 then use the link above.

To upgrade from DSM 6.0.2 to DSM 6.1.7 read here.

 

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 burn 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.1 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.1.7 PAT file. Chose the one you need: DS3615sx or  DS3617sx or DS916+. Download the ".pat" file not the ".pat.md5"

- Jun's official v1.02b loader (mirror). This is a hybrid UEFI/BIOS loader so it should work in most machines which are capable or reading GUID partition table (GPT). For older machines that can only read MBR the above loader will simply not boot. If that is your case then use @Genesys's v1.02b loader rebuilt image which is MBR based. Note: Jun's loader supports Intel CPUs. For AMD CPUs Jun has stated that the loader needs some work but it has been reported by many users using HP machines that it actually works. The C1E function in the bios (in some HP machines) needs to be deactivated. I am unsure for other motherboards brands therefore if you have an AMD machine that is not an HP you might be out of luck. Try looking in the bios configuration and play around. 

- Custom 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 and updated modules & firmwares. Credits go to @IG-88 for compiling the modules against the latest DSM 6.1.3 source code. I do not 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. If you a have question specific to the custom ramdisk please post it in the topic of IG-88, not here.

- If you are doing a fresh install 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 MoBo manufacturer for exact nomenclature.

- OSFMount to modify the grub.cfg file within the loader's image and if necessary to replace the extra.lzma ramdisk with the custom one. This is not strictly necessary as Jun has made it possible to configure what needs to be modified via the Grub Boot Menu. If you prefer using Jun's Grub Boot Menu configuration method, simply skip Point 4, read Note 4 instead and pick up at Point 5.

 

 

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 has a limited amount of modules (drivers) included. If it is fundamental for you to have a NAS operating as quick as possible I recommend you look at the included drivers very carefully at the bottom of this tutorial before attempting an upgrade. If they are not there you will have to compile your own modules/firmwares or use the custom ramdisk provided above. Don't ask me to compile modules for you. I wont do it.

One last thing:

DO NOT UPDATE DSM BEYOND VERSION 6.1.7 with loader v1.02b.

IN OTHER WORDS  DO NOT UPDATE TO DSM 6.2

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.1. 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.1 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 - Now launch OSFMount. Select Mount New, then select the image file you downloaded earlier (i.e. .img extension file) to open. Now select partition 0 (the one that is 15 MB). Click Ok. Then at the bottom of the window make sure to un-tick the "Read only drive". Click Ok. The partition should now be mounted in file explorer. At this point you can navigate to the /grub directory and edit the grub.cfg file.

If you need to replace the extra.lzma ramdisk with the custom ramdisk provided above then you will also need to mount partition 1 (the one that is 30 MB).

 

Below is what you will see in the grub.cfg 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 or DS 3617xs or DS916+ model (this will depend on which loader you chose)

Change mac1=0011322CA785 to mac1=[your NIC MAC address #1]. 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.

Recommended: 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 on screen.

 

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.

 

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

 

6 - 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 Jun official 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. 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.

 

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

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:

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.

 

8 - 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 your 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_15217.pat or DSM_DS3617xs_15217.pat or DSM_DS916+_15217.pat).

 

9 - When the migration is finished you will most probably have to update some of your packages. You can then proceed and update DSM 6.1.7 up to DSM 6.1.7 critical update 3. It is possible you might either need to hard reboot or re-image your usb drive. Make sure to deactivate auto-updates within DSM. Link to individual files (DSM and critical updates) can be found here: https://xpenology.com/forum/topic/7294-links-to-dsm-and-critical-updates/.

DO NOT UPDATE TO DSM 6.2. The loader is not compatible.

 

10 - 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 or not answered.

 

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

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 since the introduction of DSM 6. Root access through SSH is no longer possible out of the box. You can however use your admin account and elevate permissions with the following command if you need root permissions:

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 most certainly means your VID and/or PID is/are wrong. If you still have the same error message after verifying the VID/PID then try another USB drive.

 

Note 4: Configuration added to the grub.cfg file can also be done directly during the Grub Boot Menu, so technically you can skip Point 4 and burn the image on the USB drive without editing anything (read Point 5 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 (fake numbers) of how it looks under the Grub command line environment :

 

 

Note 5: If you encounter the error "We've detected errors on your hard drives [drive number] and the SATA ports have also been disabled" during installation, 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 Reinstall, 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 Reinstall 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 & firmwares in Jun's Loader #############

Spoiler

Modules
alx.ko
ata_piix.ko
atl1.ko
atl1c.ko
atl1e.ko
ax88179_178a.ko
bnx2.ko
bnx2x.ko
BusLogic.ko
button.ko
cnic.ko
e1000.ko
ipg.ko
jme.ko
libcrc32c.ko
libphy.ko
mdio.ko
megaraid_mbox.ko
megaraid_mm.ko
megaraid_sas.ko
megaraid.ko
mii.ko
mpt3sas.ko
mptbase.ko
mptctl.ko
mptsas.ko
mptscsih.ko
mptspi.ko
netxen_nic.ko
ohci-hcd.ko
pch_gbe.ko
pcnet32.ko
ptp_pch.ko
qla3xxx.ko
qlcnic.ko
qlge.ko
r8168.ko
r8169.ko
scsi_transport_spi.ko
sfc.ko
skge.ko
sky2.ko
tg3.ko
uio.ko
usbnet.ko
vmw_pvscsi.ko
vmxnet3.ko

Firmwares
bnx2/bnx2-rv2p-06-6.0.15.fw
bnx2/bnx2-rv2p-09-6.0.17.fw
bnx2/bnx2-rv2p-09ax-6.0.17.fw
tigon/tg3_tso.bin
tigon/tg3_tso5.bin
tigon/tg3.bin

 

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

Spoiler

[12/09/2017] Tutorial creation
[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."
[17/09/2017] Temporary removal of IG-88 custom ramddisk due to some modules creating issues.
[18/09/2017] Changed S/N generator link with updated version (https://xpenogen.github.io/serial_generator/index.html)
[27/09/2017] Added link to upgrade procedure from DSM 6.0.2 to DSM 6.1 in top paragraph
[22/10/2017] Update jun's loader link to https://mega.nz/#F!BtFQ2DgC!JgomNP3X8V9EuwxL4TXbng!EscjTCAB and mirror link to https://mega.nz/#F!yQpw0YTI!DQqIzUCG2RbBtQ6YieScWg!iJZjAJoa - Directly to v1.02b
[14/12/2017] Updated tutorial to 6.1.4. Removed Logs for Custom ramdisk; Instead a link to IG-88 custom ramdisk topic is provided.
[07/01/2018] Improved note about AMD compatibility.
[24/05/2018] Updated tutorial to reflect possible update to DSM 6.1.7-15284. DSM CANNOT be updated to DSM 6.2
[30/07/2018] Updated spoiler code plugin

[11/02/2010] Updated broken links (VID/PID & Notepad++). Updated tutorial to install DSM 6.1.7 instead of DSM 6.1.4.

 

 

Edited February 11, 2020 by Polanskiman
See Tutorial UPDATES log above ^

[dotslash]

Hi, it's possible install  6.1.3.15125 update 4?

 

tnx in adv.

[dotslash]

Oh! I'm running on HP proliant gen8 and works perfectly!

[infonator8]

15 minutes ago, dotslash said:

Hi, it's possible install  6.1.3.15125 update 4?

 

tnx in adv.

 

It's been reported by a bunch of members (including myself) that the update works fine. But it depends on the hardware that you're using. Make a test server and update, just to be sure before updating your main server.

[dotslash]

Works on my HP microserver GEN8

 

[wars_92]

It installed perfectly! I'm using AMD Ryzen 5 1500x 

[nleeies]

I'm having trouble with both this loader as well as the 1.01 loader with an Atheros 8151 NIC. It seems as though the atl1c driver does not detect the hardware - the grub menu shows nothing with a net_ls_cards command, and the light is solid amber after booting the kernel. No new DHCP requests show up in my router's logs.

 

I have (likely incorrectly) attempted to compile the driver with the 15152 build as reference for the 1.02b loader, but ended up with the same result.

 

The NIC is confirmed working, as an Ubuntu live USB has no issue using atl1c.

 

Any advice?

[kim82]

Ok Guys! I BEG for help!

 

I had my dsm 5,2 running on my esxi 6 and did work GREAT!

 

now I wanted to try the latest and now I cant get it to work. 

 

Please help me:

 

I want to install dsm 6.1.3 on my esxi 6. What am a I doing wrong? When xpenology reboots, im not getting any ip number at all. But first time I boot and I choose migrate it work until reboot. then no ip number again. Im kinda stuck.....PLEASE HELP im so desperate, I have so many things I cant loose in my discs.

 

regards Kim

[agent47SG1]

1 hour ago, kim82 said:

Ok Guys! I BEG for help!

 

I had my dsm 5,2 running on my esxi 6 and did work GREAT!

 

now I wanted to try the latest and now I cant get it to work. 

 

Please help me:

 

I want to install dsm 6.1.3 on my esxi 6. What am a I doing wrong? When xpenology reboots, im not getting any ip number at all. But first time I boot and I choose migrate it work until reboot. then no ip number again. Im kinda stuck.....PLEASE HELP im so desperate, I have so many things I cant loose in my discs.

 

regards Kim

Hello,

 

Wich loader use you ? Can you show your grub.cfg file

[kim82]

7 minutes ago, agent47SG1 said:

Hello,

 

Wich loader use you ? Can you show your grub.cfg file

Hello!

 

Ok so we take this from the begining. could you please point out what files I need for setting up in esxi? So I have the right ones. I wan to run the latest

[agent47SG1]

Just now, kim82 said:

Hello!

 

Ok so we take this from the begining. could you please point out what files I need for setting up in esxi? So I have the right ones. I wan to run the latest

After updateing DSM to 6.1.3 you should replace XPEnology.iso loader (used for DSM 5.2) by Jun's Loader but this loader need few modification tu work.

- Download Jun Loader 1.02b 3617xs https://mega.nz/#F!BtFQ2DgC!JgomNP3X8V9EuwxL4TXbng!k5NxiIjI

- On ESX in Datastore upload synoboot.img file in the VM directory

- On your computer create synoboot.txt file and paste following lines

 

Quote

# Disk DescriptorFile
version=1
CID=5a3f7f5f
parentCID=ffffffff
isNativeSnapshot="no"
createType="vmfs"

# Extent description
RW 102400 VMFS "synoboot.img" 0

# The Disk Data Base
#DDB

ddb.adapterType = "lsilogic"
ddb.deletable = "true"
ddb.encoding = "UTF-8"
ddb.longContentID = "5cfc609b86db2c06834ece425a3f7f5f"
ddb.thinProvisioned = "1"
ddb.toolsInstallType = "4"
ddb.toolsVersion = "10247"
ddb.uuid = "60 00 C2 9a ee da ca 33-df 5e 04 3f 80 55 f9 62"
ddb.virtualHWVersion = "10"

- After that rename synoboot.txt to synobbot.vmdk and upload it in VM folder

- On ESXi admin edit setting of VM to add existing hard drive and select synoboot.vmdk

If you see always nothing it is may by the order of hard drive, in VM setting remove all hard drive from config only except synoboot.vmdk, validate and after add again other all existinf vmdk

 

[kim82]

PLESE help!

 

if I use esxi 6.0 Do I still need the usbmemory? pid, vid and all that stuff?

I still cant get my xpenology online, please do help me =( or can I reverse back to 5.2 somehow?

[kim82]

when I do migrate my xepnology to the ds3717xs it starts installing but after the reboot and counting down 10 minutes.......the IPnumber dissapear from the xepnology. I cant see it in the router or ping it. what am I doing wrong?

 

pleease please hlp me......I have so much stuff I need to get back.

[polanskiman]

1 hour ago, kim82 said:

when I do migrate my xepnology to the ds3717xs it starts installing but after the reboot and counting down 10 minutes.......the IPnumber dissapear from the xepnology. I cant see it in the router or ping it. what am I doing wrong?

 

pleease please hlp me......I have so much stuff I need to get back.

 

I do not use ESXI so I am not sure what is going on. Check the forum there are several topics on the matter. All I can say is that your data should be safe since it is on separate partition so don't worry too much about that

 

Anyway what NIC are you using in ESXI?

[kim82]

 

40 minutes ago, Polanskiman said:

 

I do not use ESXI so I am not sure what is going on. Check the forum there are several topics on the matter. All I can say is that your data should be safe since it is on separate partition so don't worry too much about that

 

Anyway what NIC are you using in ESXI?

Hey Polanskiman!

 

I finally got it to work and with the latest update 4 aswell! 

 

now my last issue; why is the 50mb "wmware disc" visible when I look at the disk slots? in dsm 5.2 I know that partition was invisible....

can I hide that partition from dsm?

Edited September 14, 2017 by kim82

[polanskiman]

3 hours ago, kim82 said:

 

Hey Polanskiman!

 

I finally got it to work and with the latest update 4 aswell! 

 

now my last issue; why is the 50mb "wmware disc" visible when I look at the disk slots? in dsm 5.2 I know that partition was invisible....

can I hide that partition from dsm?

 

It might be a good idea to share what you did so that if others who came across the same problem then they can use your experience. For the visible disk you might want to read this: https://xpenology.com/forum/topic/7613-disablehide-50mb-vmware-virtual-disk/?do=findComment&comment=73440

[kim82]

5 hours ago, Polanskiman said:

 

It might be a good idea to share what you did so that if others who came across the same problem then they can use your experience. For the visible disk you might want to read this: https://xpenology.com/forum/topic/7613-disablehide-50mb-vmware-virtual-disk/?do=findComment&comment=73440

thank you! Yes I will update how I did.

 

one more qquestion. How much ram should I dedicate in esxi for the VM?(xpenology)

[gb77]

Anyone managed to do this bare metal on an N54L?

 

I've got one which has been running fine on 5.2 (5664 update 5) serving CCTV setup. But noticed openvpn package isn't getting updates any longer, whereas my Gen 8 running 6.02 (8451 update 11) has received a few updates since.

Edited September 14, 2017 by gb77

[polanskiman]

Anyone managed to do this bare metal on an N54L?
 
I've got one which has been running fine on 5.2 (5664 update 5) serving CCTV setup. But noticed openvpn package isn't getting updates any longer, whereas my Gen 8 running 6.02 (8451 update 11) has received a few updates since.

You might need to disable C1E in your bios prior the upgrade.

[gb77]

7 minutes ago, Polanskiman said:

You might need to disable C1E in your bios prior the upgrade.

 

Thanks, will give that a try.

[Dfds]

@gb77 jun's 1.02b loader definitely works with the N40L, as Polanskiman says just disable C1E support in the bios, reboot & upgrade to 6.1.3. After the install finishes you'll get an update notice saying that update 4 is available, you can go ahead & apply it but be warned it will reboot your system again.

[Gubti]

Big thanks to everybody: @Polanskiman, @jun, @quicknick, @Trantor, @IG-88 and everybody esle involved in R&D and testing. Finally with extra.lzma my system Gigabyte Z 170 Board with Intel Pro 1000 NIC and adaptec HBA 1000 SAS Controller is fully migrated to 6.1.3. I can confirm up and running with this combination.

[djelusion]

I would like to try this method on a production server running 5.2. However my previous attempts at getting to dsm 6. on a hp mediasmart server did not work well and I did lose data. having a backup of 30TB is not something I can or plan on doing. Luckily the system I have is a home brew H97I by asus. The other thing I forgot to mention was the whole mac and the model ds3615xs

[IG-88]

i would suggest the method i did with my barematel system

remove power cables from all disks (30 TB drives), remove usb stick

 

take new usb stick and empty single disk, prepare usb stick as in howto (vid/pid)

connect empty disk to first sata port of system, cennct usb stick and power on and try to install dsm 6.x (usualy 6.1.3 would be the first choice)

 

if you are finished testig reconnect first sata cable with old disk, reconnect 30 TB drives to power and use old stick to power up - no harm done and you know is your hardware working with the new bootloader (+extra.lzma for drivers if needed) and new dsm 6.1.3

[djelusion]

9 hours ago, IG-88 said:

i would suggest the method i did with my barematel system

remove power cables from all disks (30 TB drives), remove usb stick

 

take new usb stick and empty single disk, prepare usb stick as in howto (vid/pid)

connect empty disk to first sata port of system, cennct usb stick and power on and try to install dsm 6.x (usualy 6.1.3 would be the first choice)

 

if you are finished testig reconnect first sata cable with old disk, reconnect 30 TB drives to power and use old stick to power up - no harm done and you know is your hardware working with the new bootloader (+extra.lzma for drivers if needed) and new dsm 6.1.3

 

Thats something I was considering. The main question is can users using a 5.2 loader use the same mac info the 6.x loader? vid / pid is simple but the mac scheme im not sure if thats changed causing the newer loaders not to work properly?.