DSM 6.2 Loader


Recommended Posts

1 hour ago, luchuma said:

i wrote that in tutorial section

 

 

 

 

I read your post yesterday I think. But I missed that 0.0 detail :) it did not seem so important. It is, apparently, most important. The other disks, though, don't need to be SATA. They can also be SCSI.

Link to post
Share on other sites
On 8/18/2018 at 10:35 PM, ygor said:

 

 

you should add     disable_mtrr_trim     to the grub.cfg

 

Example: set common_args_3615='disable_mtrr_trim syno_hdd_pow ......

 

it is know issue, also required on G7 (amd)

 

 

what does this actually do? what does MTRR Trim stand for/mean?

Link to post
Share on other sites
2 hours ago, captainfred said:

 

what does this actually do? what does MTRR Trim stand for/mean?

 

There is more details here:

https://www.oradba.ch/2013/08/avdf-linux-kernel-could-not-recognize-whole-ram/

 

 

looks to be caused by a bios issue, disabling is a workaround if there is no bios update

 

 

 

Link to post
Share on other sites

On my HP Microserver Gen 8 I did a dirty update from 6.1 DS3615xs to update 6.2 DS3615xs . When it wanted to restart, I changed the boot USB to the new loader 1.03b.

After that, I switched the boot USB again to 1.03b DS3617xs and migration went without problems.

 

I read that for DSM 6.2, the linux kernel would be version 4.4, but I run the DS3617xs version and it's still on 3.10. Is this only the case for XPenology?

Edited by alpakay
Link to post
Share on other sites
1 hour ago, alpakay said:

On my HP Microserver Gen 8 I did a dirty update from 6.1 DS3615xs to update 6.2 DS3615xs . When it wanted to restart, I changed the boot USB to the new loader 1.03b.

After that, I switched the boot USB again to 1.03b DS3617xs and migration went without problems.

 

I read that for DSM 6.2, the linux kernel would be version 4.4, but I run the DS3617xs version and it's still on 3.10. Is this only the case for XPenology?


If im looking at the below link correctly. Ds3617, which is Broadwell based, seems to still have the 3.10 kernel in DSM 6.2? while some other models, e.g DS918 are up at the 4.4 kernel.

https://sourceforge.net/projects/dsgpl/files/DSM 6.2 Tool Chains/

 

Edited by alirz1
Link to post
Share on other sites
3 hours ago, alpakay said:

On my HP Microserver Gen 8 I did a dirty update from 6.1 DS3615xs to update 6.2 DS3615xs . When it wanted to restart, I changed the boot USB to the new loader 1.03b.

After that, I switched the boot USB again to 1.03b DS3617xs and migration went without problems.

 

I read that for DSM 6.2, the linux kernel would be version 4.4, but I run the DS3617xs version and it's still on 3.10. Is this only the case for XPenology?

 

It has nothing to do with XPEnology. The loader is merely a boot loader and as the name states, it simply enable DSM to boot on a non-Synology hardware. Beyond that the DSM you have installed on the machine is as genuine as the one on a real Synology box.

 

Now to the kernel version. Not all models have the same kernel version. A simple

uname -a

gives you the kernel version of the model you are running:

 

Linux jun103b3615xs 3.10.105 #23739 SMP Tue Jul 3 19:47:13 CST 2018 x86_64 GNU/Linux synology_bromolow_3615xs

Linux jun103b3617xs 3.10.105 #23739 SMP Tue Jul 10 00:17:06 CST 2018 x86_64 GNU/Linux synology_broadwell_3617xs

Linux jun103a2918 4.4.59+  #23739 SMP PREEMPT Tue Jul 10 00:18:17 CST 2018 x86_64 GNU/Linux synology_apollolake_918+

 

 

Link to post
Share on other sites
On 8/21/2018 at 9:24 PM, Aigor said:

Hi, have you did some tweaking to install into N40L? some bios settings or similar, i wasn't able to fresh install into N40L 
Many thanks 

 

nothing special , just 3 120Gb drives and everything in BIOS is default except booting sequence


used the ds3617_6.2 to create the bootdisk 
and use DSM_DS3617xs_23739.pat for manual install , done
 

all CLEAN install and cannot create RAID or JBOD volume

changed to XPEnoboot_DS3615xs_5.2-5644.5.img 
+ DSM_DS3615xs_5644.pat

and everything seems fine ... maybe I need to download something in between 

 

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 Had the same problem, i spend a lot of time trying to fix it, but in the end i chose to use the "downgrade" method so the system thinks it is running 6.0 but it was running 6.2, i did that so o got the possibility to reset all setting but keeping my data, and now, after a entire weekend it is golden once more.. now it runs as i should.

 

if you have the time..... reset or as they say "downgrade".

 

 

- i made this account just to write this to you xD

 

 

MJ 

Link to post
Share on other sites

I have a evga nforce 680i sli and it used to work fine with the xneboot image on 3615xs, but I cant get this to work. Screen stops on 'Screen willl stop updating shortly.... ' and cant find the pc on my home network and obviously not even on the synology assistant.

Are there any work arounds please...

Link to post
Share on other sites

disconnected the usb drive and re-imaged it with 6.2 loader and then rebooted the nas after plugging the usb back in ... auto detected and asking for migrate and upgrade ... done that and all went smoooth.

 

THANK YOU JUN .. MUCH APPRECIATED EVERY SECOND YOU SPENT ON THIS :)

 

BareMetal Dell 7010, Intel i5 3rd Gen, 32GB Ram, 2X500GB WD Blue

 

image.png.9240ce77f44d3e56c9f18e3e08667b7a.png

Link to post
Share on other sites
4 hours ago, Fabry815 said:

after a reinstallation of the loader, now the nas acquire the ip address from the DHCP, but is not discover in synology assist or http://find.synology.com

 

is enough to wait or we have a different workaround?

 

 

 

I had the same issue. Just find the ip in your router connected devices and enter it manually in your browser

Link to post
Share on other sites

I did it.... from DSM 6.1 to 6.2 AND at same moment I changed with migration option from (older model) DS3615xs to (newer model) DS918+ (baremetal)..... I only use(d) a Raid 1 with two disks.

 

Call me stupid boy. It was risky my working productive system to change Model and DSM parallel but I´m lucky now. It was very easy with the right loader (thanks @jun 👍) and i had much luck/fortune😉.

 

Update succesful

 

The hardware (look at my signature) is the same as before; only the booting usb-Stick I changed.

 

Everything migrated from 3615xs to 918+ : all datas, all users, all packages (except "...stat.." (?), I don´t remember the name, cause i didn´t use it often), and many other adjustments.

 

I will see in the next days if really all my needed functions are ok. If not i will report next days/weeks.

 

But warning! I´m a noob and this is only my personal experience. It is not a guarantee that it will be ok for other users with the same/similar hardware. Do it at your own risk.

 

Now the system is synchronizing.

Edited by Guest
add last sentence, update succesful
Link to post
Share on other sites
3 hours ago, sunshine said:

I did it.... from DSM 6.1 to 6.2 AND at same moment I changed with migration option from (older model) DS3615xs to (newer model) DS918+ (baremetal)..... I only use(d) a Raid 1 with two disks.

 

Call me stupid boy. It was risky my working productive system to change Model and DSM parallel but I´m lucky now. It was very easy with the right loader (thanks @jun 👍) and i had much luck/fortune😉.

 

Update succesful

 

The hardware (look at my signature) is the same as before; only the booting usb-Stick I changed.

 

Everything migrated from 3615xs to 918+ : all datas, all users, all packages (except "...stat.." (?), I don´t remember the name, cause i didn´t use it often), and many other adjustments.

 

I will see in the next days if really all my needed functions are ok. If not i will report next days/weeks.

 

But warning! I´m a noob and this is only my personal experience. It is not a guarantee that it will be ok for other users with the same/similar hardware. Do it at your own risk.

 

Now the system is synchronizing.

what hardware did you use to do this ? Motherboard, CPU ??

Link to post
Share on other sites

Update Successful

 

HP ML10V2 

E1270V3

20Gb Ram (6 Gb assigned to DSM)

ESXI 6.5u2 

 

I am stuck with a degraded array but DSM appears to be functioning perfectly. All I did was replace the loader (v1.02 w v 1.03) and migrated. Had to make a few edit to grub config to bring my disks down from #33, and this is what crashed the disk 2. Stupid me didn't read the whole thread and installed DSM to just one disk. I don't think it liked having 2 different copies spread over 4 disks.

 

Fortunately I was planning to upgrade the disks, so the upgrade will take a little longer:

Backup the array to two 8Tb disks (if both these should fail, highly unlikely as they will be brand new toshiba's, I always have my tapes!)

Blow away the array (start from scratch).

Reinstall all my apps, recreate the array as SHR2 instead of SHR1 and copy back the data.

In the end I'll have a 40Tb shr2 array. :)

 

Thanks Jun!

Link to post
Share on other sites
2 minutes ago, painkiller895 said:

what hardware did you use to do this ? Motherboard, CPU ??

 

 I wrote it in the text: "see at my signature".

 

Gigabyte GA-H270N-Wifi , Intel G4560

Link to post
Share on other sites
3 hours ago, Dubon said:

 

I had the same issue. Just find the ip in your router connected devices and enter it manually in your browser

I’ve tried but thw connectio  do not work :( provably the port is wrong. Do you have used the standard http 5000 port or a custom one?

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

I’ve tried but thw connectio  do not work :( provably the port is wrong. Do you have used the standard http 5000 port or a custom one?

 

I didnt specify any port actually. Just entered ip in browser. 

Link to post
Share on other sites

I own some dell servers poweredge 2950 using DSM 6.1 and loader 1.02b.

All work fine since 1 year. perfect.

i tried to remplace old loader 1.02b with 1.03b...work fine exept my ssd in sata port is not recognized.

I think sata driver is missing in loader. worked fine before.

so i can't migrate or install.

 

Could you do add same drivers in loader 1.03b than previous one?

 

thank you for your wonderful job. congrats.

 

Best regards

 

Config

Dell poweredge 2950 bi XEON 2.4 32go RAM

Link to post
Share on other sites

@neeiro

 

DSM 6.2 is stable, but the loader is Beta. At my system (see signature) DSM 6.2 runs since yesterday without problems.

 

I don´t know if the loader is for your (older) Board perfect. Try it and test the functions and packages you need before you use as a productive NAS.

 

Good luck. 

Edited by Guest
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.