jun

DSM 6.2 Loader

Recommended Posts

1 hour ago, roadx said:

1.- install and stays with DSM 6.1.7 on ds3615xs, w Jun's BL v1.02b (...! and never update/upgrade to 6.2!); (I read that is much stable...)

go this one matey. nothing really new in 6.2 and saves you accidently upgrading to 6.2.1 (which won't work with your realtek NICs.

 

once you're on 6.1.7, just set your update settings to this:

 

image.thumb.png.badd2434d135187ab7fe66555d8ed6a0.png

  • Like 1

Share this post


Link to post
Share on other sites

@ideasman69: Thank you for you advise! This is what I was waiting for..  Also do I, thinking 6.1.7 is much better (and safer!) than 6.2 regarding the updates...

Speaking of this, in 6.1.7, once I've make the settings as you suggest, the OS never bothers me with 6.2 announcements. But in 6.2, even I choose the 2nd option (as you suggest for 6.1.7 case) , the OS always bothers me with 6.2.1 update (which is fatal for my HW)

 

Thank You!

 

Share this post


Link to post
Share on other sites

Anyone who knows what syno_hdd_powerup_seq and syno_hdd_detect does? It was set to 0 in the older bootloaders, but now it's set to 1 by default.

Anyone who is using ESXi and has successfully migrated from ds3615xs to ds918+? Any particular VM setting that should be changed?

 

I'm still struggling to get the latest loader to list all my disks (using LSI in passthrough mode). Anyone who can explain what the sata_args are and how to figure out what values to use?

Edited by NeoID

Share this post


Link to post
Share on other sites

Hi all.

Сan't make my GA-J3455N-D3H work.

Bios version F.2

C1E disabled

On loader 1.04b i get crazy nubmers.

Transcoding works, but video freezes each 4-5 seconds

At the same time i got flawless working ds3617xs on 1.02b loader

Any help is appreciated

2018-12-15 (1).png

2018-12-15 (3).png

Share this post


Link to post
Share on other sites
On 8/2/2018 at 10:58 AM, JBark said:

HP MicroServer Gen8 with E3-1256L V2 boots fine with new loader and upgraded OK from 6.1 to 6.2, but getting some odd behaviour when I log into DSM.  If I don't mess with DSM, it runs fine, including the VM I have configured under VMM.  The second I log into DSM, it shuts down every service and I lose connection about 30 seconds later.  It's not a hard crash, as I can watch the logs and see it's shutting down/pausing every service that's running.  Pretty odd, I'm guessing something didn't upgrade nicely from 6.1 -> 6.2, I doubt it's loader related.

 

From /var/log/messages:


2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgtool.cpp:2284 chmod failed for /var/packages (Operation not permitted)
2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgtool.cpp:2293 chmod failed for /usr/local/etc/rc.d (Operation not permitted)
2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-phpMyAdmin (err=-1) [0x0900 servicecfg_root_object_set.c:43]
2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-PHP5.6 (err=-1) [0x0900 servicecfg_root_object_set.c:43]
2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-MariaDB10 (err=-1) [0x0900 servicecfg_root_object_set.c:43]
2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-Apache2.2 (err=-1) [0x0900 servicecfg_root_object_set.c:43]
2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-FileStation (err=-1) [0x0900 servicecfg_root_object_set.c:43]
2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-TextEditor (err=-1) [0x0900 servicecfg_root_object_set.c:43]
2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-tvheadend (err=-1) [0x0900 servicecfg_root_object_set.c:43]
2018-08-02T12:20:52+08:00 HPGEN8 synopkg: pkgstartstop.cpp:379 Failed to stop pkgctl-SynoFinder (err=-1) [0x0900 servicecfg_root_object_set.c:43]

Tons of entries like that, followed by....


2018-08-02T12:21:55+08:00 HPGEN8 ore.Desktop.Initdata_1_get: service_pause_all.c:173 Pause service [synosnmpcd] by reason of [unidentified] failed.
2018-08-02T12:21:55+08:00 HPGEN8 ore.Desktop.Initdata_1_get: service_pause_all.c:173 Pause service [synogpoclient] by reason of [unidentified] failed.
2018-08-02T12:21:55+08:00 HPGEN8 ore.Desktop.Initdata_1_get: service_pause_all.c:173 Pause service [crond] by reason of [unidentified] failed.
2018-08-02T12:21:55+08:00 HPGEN8 ore.Desktop.Initdata_1_get: service_pause_all.c:173 Pause service [iscsitrg] by reason of [unidentified] failed.
2018-08-02T12:21:55+08:00 HPGEN8 ore.Desktop.Initdata_1_get: service_pause_all.c:173 Pause service [atalk] by reason of [unidentified] failed.

 

Continues like that until I lose the connection.  If I check messages after the next boot, it's shutdown everything like it's planning to reboot or something, but never actually finishes.

 

 

I have the same problem, how did you solve it?

Share this post


Link to post
Share on other sites

Hi, I have a question.


I currently have versions DS3617xs - DSM 6.1.7-15284.


My equipment is nothing special, HP 400 G2 Mini:

 

- Intel i5-6500T (Skylake)
- 8GB DDR4 2133 mhz
- Intel 100 Series H110 Chipset
- Realtek RTL8111HSH-CG GbE Ethernet Controller

 

Will he successfully install the latest DSM 6.2 on this equipment from the thread: https://xpenology.com/forum/topic/12952-dsm-62-loader/?

If so, should updating should also edit GRUB for VID / PID etc?

 

Currently, everything works very well except one important thing. I can not run the latest Windows 10 builid in Virtual Machine Manager. The last working version is build 1511. This works. However, after the update is bluescreen. When he tries to install the latest one directly from an ISO file, he also displays bluescreen :(

 

I used to have some other versions of DSM for the DS918 + model, but after some update more did not start, I could not find which version it was and threw the current DS3617xs - DSM 6.1.7-15284.

 

I will be grateful for your help. I remember that some time ago I installed several different versions and none of them wanted to run :(

Share this post


Link to post
Share on other sites
On 12/22/2018 at 1:55 AM, luchuma said:

anyone tested Version: 6.2.1-23824-3 for DS3615xs ?

Works for me.  But you need to perform a progressive update.

 

Meaning,

1) You need a synoboot.img that's never been installed over/touched by DSM install (the one you wrote to your USB or the ESXI datastore, after you modified the serial)

*****If you had already attempted any types of install or reconfigure on that usb/synoinfo.img, it is already useless, please note*****

2) You need to use the older PAT file, preferrably the one specified in your Synology Assistant indicated version (in this case, 6.2.x if you use 1.03b)

3) after the initial install is completed and initial setup is completed THEN you install 6.2.x.

 

Through this method it always works for me, whether in ESXi or baremetal.

Share this post


Link to post
Share on other sites
Hi, I have a question.

I currently have versions DS3617xs - DSM 6.1.7-15284.

My equipment is nothing special, HP 400 G2 Mini:
 
- Intel i5-6500T (Skylake)
- 8GB DDR4 2133 mhz
- Intel 100 Series H110 Chipset
- Realtek RTL8111HSH-CG GbE Ethernet Controller
 

You can update with loader 1.04b for 918+ up to DSM 6.2.1 update2 for sure.
Create new usb memory with vid/pid, Mac/SN from real syno for HW transcoding, if required
  • Like 1

Share this post


Link to post
Share on other sites

@deloza

 

Thank you!


Yesterday I spent the whole evening on tests. After many attempts I managed to upload:

Jun's Loader v1.02a2 DS918 + with the version DSM_DS918 + _23739.pat.

 

This is DSM version 6.2-23739. Unfortunately, if I wanted to do an update from the administration panel to 6.2.1-23824, after the server restart, there are no drivers for LAN - the station does not respond to PING.

 

By uploading what you wrote 1.04b (https://mega.nz/#F!Fgk01YoT!7fN9Uxe4lpzZWPLXPMONMA), the latest 6.2.1 update 2 should work on my configuration?

Share this post


Link to post
Share on other sites

You have use loader 1.04b for DSM 6.2.1.

Loader’s 1.02 and 1.03b support only DSM 6.2.

 

Loader 1.04 should work on your configuration, as I have same for test proposes.

  • Like 1

Share this post


Link to post
Share on other sites

Revelation!
I confirm the action. I made update to 1.04b, updated from DSM to 6.2.1 update 1, then to update 2 and everything works great.

DSM 6.2.1-23824 Update 2 on board :)

Thank you for your help!

  • Like 2

Share this post


Link to post
Share on other sites

If im building a barebones xpenology

with an i7-8700t with a mobo that has a single 1gb nic

 

if i add a dual 10gbe nic known to work with synology

will a 918+ pat work?

or wouldi need something that can actually use a 10gbe card like the 3617xs? Would the 3018xs pat work?

 

for hw transcoding etc. Do i need to map the built in mobo 1gbe nic mac address copied from an official synobox, and i can just use thepv 10gbe ports as is?

 

thanks for help

Share this post


Link to post
Share on other sites
On 8/31/2018 at 4:20 AM, sbv3000 said:

if you open the 30mb partition of the img file in ofsmount, its in there

Sorry, I am just dumb. using the OSFmount, I can mount the 30Mb partition and see  the extra file. now what? what do i do with it? thanks

Share this post


Link to post
Share on other sites

Hello, I just got a 1.04b DS918+ running on a VM in ESXi for testing. I was able to hide the 50mb disk (set the sata port/slot number to a higher number) but in the storage manager in DSM, I see a total of 16 disk slots. The loader has the sata port map set to 4. Is there anyway to have it only show 4 slots like an actual DS918+? 

Share this post


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

Hello, I just got a 1.04b DS918+ running on a VM in ESXi for testing. I was able to hide the 50mb disk (set the sata port/slot number to a higher number) but in the storage manager in DSM, I see a total of 16 disk slots. The loader has the sata port map set to 4. Is there anyway to have it only show 4 slots like an actual DS918+? 

Edit synoinfo.conf

Share this post


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

Edit synoinfo.conf

 

Thanks for the reply, I will look into it. Will modifying synoinfo.conf for the disk slots affect functionality with packages and/or DSM updates?

Share this post


Link to post
Share on other sites

Hi,

Could someone tell me if I can do the update from 6.0.2 to 6.1.7 with the following configuration?

 

- MSI N3150 ICO with 8Go ram and 2 x 3Tb WD red

- Current version 6.0.2   DS3615xs

- I think my network controller is a  "Realtek® RTL8111G Gigabit LAN"  not compatible with 6.2

 

Thanks’ in advance

Edited by digueche

Share this post


Link to post
Share on other sites
1 час назад, digueche сказал:

"Realtek® RTL8111G Gigabit LAN"  not compatible with 6.2

It seem's that you can try with fresh HDD and loader on the new usb stic, but you must to disconnect all working HDD's and replsce usb.

Share this post


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

 

Thanks for the reply, I will look into it. Will modifying synoinfo.conf for the disk slots affect functionality with packages and/or DSM updates?

You will sometimes have to make edit again after updates.

Share this post


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

Does anyone know if 1.04b works with the intel 82567lm, It is in a Dell Optiplex 760,  I cannot seem to get it to show up on my network ?

All I find for that model are Core 2 models, the CPU is way too old if that’s the case. DS918+ only works on Haswell and newer. 

Share this post


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

You will sometimes have to make edit again after updates.

 

Ah ok, maybe in that case I'll consider leaving it alone then, its more of a cosmetic thing really.

Regarding hiding the 50MB drive, after some extensive testing, I noticed that if you hide the 50MB drive by moving the SATA port in the VM settings to a higher number before installing DSM fresh, the installation fails with I think a code 13 stating that the file is probably corrupt. However, if it is set to a lower port number, the initial installation goes through smoothly no problems. This got me thinking perhaps during future security updates, if the 50MB drive is set back to a higher port number in the VM settings to where it is hidden, could subsequent DSM updates/security patches fail installing? Meaning I'd have to "reveal" the 50MB drive before an update then hide it again? 

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