jun

DSM 6.1.x Loader

Recommended Posts

Some Info for N54L users (AMD based)

I burned the newest 1.01 Image on my USB Stick, adjusted PID, VID, SNR and MAC but still ran into "Booting the Kernel" without finding the NAS in my network.

 

After i adjusted the timeout to '5' i had the chance to see the grub menu, where i could choose the AMD entry, which did the trick :smile:

 

Thanks for the hard work :smile:

Share this post


Link to post
Share on other sites
Some Info for N54L users (AMD based)

I burned the newest 1.01 Image on my USB Stick, adjusted PID, VID, SNR and MAC but still ran into "Booting the Kernel" without finding the NAS in my network.

 

After i adjusted the timeout to '5' i had the chance to see the grub menu, where i could choose the AMD entry, which did the trick :smile:

 

Thanks for the hard work :smile:

 

I thought one second is enough :grin:

Share this post


Link to post
Share on other sites
DS3615xs 6.0.2 Jun's Mod V1.01 vhdx

https://d.pr/JZz/1RfOGd89+

 

Please fix Hyper-V operation.

The LAN driver is not supported.

 

 

Thanks.

 

Both XPEnoboot_DS3615xs_5.2-5967.1 and your VDK have two com ports, com 2 looks something like this on either; ID is the only thing changes.

 

get-vm | ?{ $_.name -like "DSM*" } | foreach { $_.comport2 | fl * }


VMCheckpointId   : 00000000-0000-0000-0000-000000000000
VMCheckpointName :
Path             :
DebuggerMode     : Off
Name             : COM 2
Id               : Microsoft:79F4A04C-0C0C-487A-83A4-2702C2229BD2\8E3A359F-559A-4B6A-98A9-1690A6100ED7\1
VMId             : 79f4a04c-0c0c-487a-83a4-2702c2229bd2
VMName           : XPEnoboot_DS3615xs_5.2-5967.1
VMSnapshotId     : 00000000-0000-0000-0000-000000000000
VMSnapshotName   :
CimSession       : CimSession: .
ComputerName     : SUPERWIN10
IsDeleted        : False

 

 

This is the info you get for the network adaptor, Again same for both.

 

Get-VMNetworkAdapter "dsm 6" | fl *


VMCheckpointId                 : 00000000-0000-0000-0000-000000000000
VMCheckpointName               :
ClusterMonitored               : True
MacAddress                     : 00155D00BD0D
DynamicMacAddressEnabled       : True
AllowPacketDirect              : False
IsLegacy                       : False
IsSynthetic                    : True
IPAddresses                    : {}
DeviceNaming                   : Off
IovWeight                      : 0
IovQueuePairsRequested         : 1
IovInterruptModeration         : Default
PacketDirectNumProcs           : 0
PacketDirectModerationCount    : 64
PacketDirectModerationInterval : 1000000
IovQueuePairsAssigned          : 0
IovUsage                       : 0
VirtualFunction                :
MandatoryFeatureId             : {}
MandatoryFeatureName           : {}
PoolName                       :
Connected                      : True
SwitchName                     : Virtual Switch
AdapterId                      : 6154E465-99CF-4EC9-88BB-034015ADB786
TestReplicaPoolName            :
TestReplicaSwitchName          :
StatusDescription              : {No Contact}
Status                         : {NoContact}
IsManagementOs                 : False
IsExternalAdapter              : False
Id                             : Microsoft:165311A2-F098-4448-BA9D-69A8E3071913\6154E465-99CF-4EC9-88BB-034015ADB786
SwitchId                       : d8efd56e-0c5c-4595-ad82-a98d7a8a609d
AclList                        : {}
ExtendedAclList                : {}
IsolationSetting               : VMNetworkAdapterIsolationSetting
RoutingDomainList              : {}
VlanSetting                    : VMNetworkAdapterVlanSetting
BandwidthSetting               :
CurrentIsolationMode           : Vlan
MacAddressSpoofing             : Off
DhcpGuard                      : Off
RouterGuard                    : Off
PortMirroringMode              : None
IeeePriorityTag                : Off
VirtualSubnetId                : 0
DynamicIPAddressLimit          : 0
StormLimit                     : 0
AllowTeaming                   : Off
FixSpeed10G                    : Off
VMQWeight                      : 100
IPsecOffloadMaxSA              : 512
VrssEnabled                    : False
VrssEnabledRequested           : True
VmmqEnabled                    : False
VmmqEnabledRequested           : False
VmmqQueuePairs                 : 0
VmmqQueuePairsRequested        : 16
VmqUsage                       : 0
IPsecOffloadSAUsage            : 0
VFDataPathActive               : False
VMQueue                        :
BandwidthPercentage            : 0
IsTemplate                     : False
Name                           : Network Adapter
VMId                           : 165311a2-f098-4448-ba9d-69a8e3071913
VMName                         : DSM 6
VMSnapshotId                   : 00000000-0000-0000-0000-000000000000
VMSnapshotName                 :
CimSession                     : CimSession: .
ComputerName                   : SUPERWIN10
IsDeleted                      : False

 

So if it's a network driver issue, I'm guessing it's because the Hyper-V drivers haven't been injected into the current build?

I found this site, http://windeploy.co.uk/blog/hyper-v/ext ... 2-drivers/

I don't know much about drivers windows drivers don't work with linux?

Share this post


Link to post
Share on other sites

Sorry in advance for a dumb question, but is it possible to upgrade to Version 6 and keep all data on a HP N40L. I only read about VM and EXSI running the latest version. Is there any kind of tutorial?

tia

Share this post


Link to post
Share on other sites

For the sake of testing, I tried Jun's latest loader v1.0.1 without any change to the grub (vid/pid, mac or sn) and the machine/DSM booted nicely. Of course the usb partitions appeared as shared folders but this is most certainly because I didn't modify vid/pid.

 

 

Sent from my iPhone using Tapatalk

Share this post


Link to post
Share on other sites
DS3615xs 6.0.2 Jun's Mod V1.01 vhdx

https://d.pr/JZz/1RfOGd89+

 

Please fix Hyper-V operation.

The LAN driver is not supported.

 

 

Thanks.

 

Both XPEnoboot_DS3615xs_5.2-5967.1 and your VDK have two com ports, com 2 looks something like this on either; ID is the only thing changes.

 

get-vm | ?{ $_.name -like "DSM*" } | foreach { $_.comport2 | fl * }


VMCheckpointId   : 00000000-0000-0000-0000-000000000000
VMCheckpointName :
Path             :
DebuggerMode     : Off
Name             : COM 2
Id               : Microsoft:79F4A04C-0C0C-487A-83A4-2702C2229BD2\8E3A359F-559A-4B6A-98A9-1690A6100ED7\1
VMId             : 79f4a04c-0c0c-487a-83a4-2702c2229bd2
VMName           : XPEnoboot_DS3615xs_5.2-5967.1
VMSnapshotId     : 00000000-0000-0000-0000-000000000000
VMSnapshotName   :
CimSession       : CimSession: .
ComputerName     : SUPERWIN10
IsDeleted        : False

 

 

This is the info you get for the network adaptor, Again same for both.

 

Get-VMNetworkAdapter "dsm 6" | fl *


VMCheckpointId                 : 00000000-0000-0000-0000-000000000000
VMCheckpointName               :
ClusterMonitored               : True
MacAddress                     : 00155D00BD0D
DynamicMacAddressEnabled       : True
AllowPacketDirect              : False
IsLegacy                       : False
IsSynthetic                    : True
IPAddresses                    : {}
DeviceNaming                   : Off
IovWeight                      : 0
IovQueuePairsRequested         : 1
IovInterruptModeration         : Default
PacketDirectNumProcs           : 0
PacketDirectModerationCount    : 64
PacketDirectModerationInterval : 1000000
IovQueuePairsAssigned          : 0
IovUsage                       : 0
VirtualFunction                :
MandatoryFeatureId             : {}
MandatoryFeatureName           : {}
PoolName                       :
Connected                      : True
SwitchName                     : Virtual Switch
AdapterId                      : 6154E465-99CF-4EC9-88BB-034015ADB786
TestReplicaPoolName            :
TestReplicaSwitchName          :
StatusDescription              : {No Contact}
Status                         : {NoContact}
IsManagementOs                 : False
IsExternalAdapter              : False
Id                             : Microsoft:165311A2-F098-4448-BA9D-69A8E3071913\6154E465-99CF-4EC9-88BB-034015ADB786
SwitchId                       : d8efd56e-0c5c-4595-ad82-a98d7a8a609d
AclList                        : {}
ExtendedAclList                : {}
IsolationSetting               : VMNetworkAdapterIsolationSetting
RoutingDomainList              : {}
VlanSetting                    : VMNetworkAdapterVlanSetting
BandwidthSetting               :
CurrentIsolationMode           : Vlan
MacAddressSpoofing             : Off
DhcpGuard                      : Off
RouterGuard                    : Off
PortMirroringMode              : None
IeeePriorityTag                : Off
VirtualSubnetId                : 0
DynamicIPAddressLimit          : 0
StormLimit                     : 0
AllowTeaming                   : Off
FixSpeed10G                    : Off
VMQWeight                      : 100
IPsecOffloadMaxSA              : 512
VrssEnabled                    : False
VrssEnabledRequested           : True
VmmqEnabled                    : False
VmmqEnabledRequested           : False
VmmqQueuePairs                 : 0
VmmqQueuePairsRequested        : 16
VmqUsage                       : 0
IPsecOffloadSAUsage            : 0
VFDataPathActive               : False
VMQueue                        :
BandwidthPercentage            : 0
IsTemplate                     : False
Name                           : Network Adapter
VMId                           : 165311a2-f098-4448-ba9d-69a8e3071913
VMName                         : DSM 6
VMSnapshotId                   : 00000000-0000-0000-0000-000000000000
VMSnapshotName                 :
CimSession                     : CimSession: .
ComputerName                   : SUPERWIN10
IsDeleted                      : False

 

So if it's a network driver issue, I'm guessing it's because the Hyper-V drivers haven't been injected into the current build?

I found this site, http://windeploy.co.uk/blog/hyper-v/ext ... 2-drivers/

I don't know much about drivers windows drivers don't work with linux?

 

Hyper-V Virtual Devices

http://oliveryang.net/2016/03/vm-basic-2/

https://github.com/LIS/lis-next

Share this post


Link to post
Share on other sites

Thx. I will give this a try. So this will give me back all my settings i had under DSM 5.2-5644 Update 5 after migration.

I recently made some settings for some backup jobs via ssh and private/openkey and won*t lose them.

Share this post


Link to post
Share on other sites

Ok, so had another go with the installation on my KVM (Virtualisation Station) which is running on my QNap NAS all all went perfectly.

 

I used the 1.01 image file. Changed the MAC and Serial (Left the VID & PID as is)

Converted the img file to q2cows

Created a new VM with IDE HD booting the synoboot.img

Created a SATA drive for files etc.

Used the Intel Network card and matched the MAC to the one on the grub.cfg

Booted and everything works hunky dory.

 

So far I've tried most of the packages including using BTFS and they seem to be working fine! So you have a very happy customer here!

 

Thanks guys for all your hard work!! Really appreciate it.

Share this post


Link to post
Share on other sites

I can not make it work QC

I used the same serial number for the 5.2 ( 5.2-5967.1) and everything works

tried generator - no result

I used 1.01 image

what else can I try?

Share this post


Link to post
Share on other sites
Hello, i would like to run the new bootloader under Proxmox.

I convert the synoboot.img to qcow2 and create a new VM HDD with the synoboot.qcow2.

http://imgur.com/cxvGlTy

 

and nothing else happened.

 

Anybody an idea?

 

Did you download the synology assistant or try find.synology.com?

 

It should come up after some minutes

Share this post


Link to post
Share on other sites
i tried find.synology.com and i also looked at the dhcp leases on my router but nothing.

 

What network adapter are you using in the proxmox vm?

Share this post


Link to post
Share on other sites
Thx. I will give this a try. So this will give me back all my settings i had under DSM 5.2-5644 Update 5 after migration.

I recently made some settings for some backup jobs via ssh and private/openkey and won*t lose them.

 

Most settings done under the gui should migrate. However if you did some changes to system files which are not supposed to be edited by the user, then those will most certainly be overwritten during the upgrade. Make a backup of your data and settings prior attempting anything

Share this post


Link to post
Share on other sites

Update went fine - thx al lot for your help. Had a few problems with sabnzbd, but these are solved. Can i run update 2 via webinterface or do i have load it manually with a pat-file.

And one bigger issue: I'm running a backup-job from another NAS to my diskstation using rsync with ssh-keys. After update the other NAS cannot connect to the rsync server on the disksation.

Login on console with ssh works.

I read about some changes on the dsm side, but i'm not sure how to what's the problem.

Share this post


Link to post
Share on other sites
Update went fine - thx al lot for your help. Had a few problems with sabnzbd, but these are solved. Can i run update 2 via webinterface or do i have load it manually with a pat-file.

And one bigger issue: I'm running a backup-job from another NAS to my diskstation using rsync with ssh-keys. After update the other NAS cannot connect to the rsync server on the disksation.

Login on console with ssh works.

I read about some changes on the dsm side, but i'm not sure how to what's the problem.

 

Make sure rsync is active on your machine. I would also re-issue those keys if I were you.

In order to use ssh-keys to log in, you must have had to edit the ssh deamon config file sshd_config and the authorized_keys file. If I were you I would check if thoses files weren't brought to default after the upgrade.

 

And yes you can update to update 2 through gui.

 

Synology has also made some security enhancements. You can no longer ssh with the root account directly out of the box.

Share this post


Link to post
Share on other sites

Just finished my migration from 5.2 to 6.0.2 using Jun 1.01 with minimal grub changes and it went smooth as silk. I spent about 3 days in preparation making backups and the upgrade took like 5 mins and the only issue I had was my NIC IP address had changed lol. I also downloaded and applied the update 2 for it and that had 0 issues. I did have to upgrade some packages that I had installed, but all of there configurations seems intact, along with my shares and settings.

 

My Specs for reference

P8Z68-V/GEN3 Motherboard

i7-2600k CPU @ 3.4Ghz

16GB RAM

2 x PERC H310 crossflashed to LSI-9211-8i IT Mode

7 x WD Red 3TB

All in a Rosewill 4U 15 bay chassis.

 

Thanks to everyone that has contributed there hard work here!

 

Jun, Trantor, Arcao, QuickNick, CtrlAltDel, Polanskiman and anyone else that I may have missed.

Share this post


Link to post
Share on other sites

The key files seems to be okay. I can use ssh in console at the remote nas and it does automatically connect to the local machine without asking for password (as root).

I activated rsync service and rsync account. The rsync account is new in DSM 6. May this is the culprit?

Share this post


Link to post
Share on other sites
The key files seems to be okay. I can use ssh in console at the remote nas and it does automatically connect to the local machine without asking for password (as root).

I activated rsync service and rsync account. The rsync account is new in DSM 6. May this is the culprit?

 

Yes that could be the reason. Use that account instead as it will hold future updates.

Share this post


Link to post
Share on other sites

I tried to login with user@IP-Diskstation after creating the authorized keys under homes/user but got publickey permission denied.

I don't know why i can't access rsync server as root.

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.