jun

DSM 6.1.x Loader

Recommended Posts

On 30/06/2017 at 6:13 PM, mcdull said:

I have done 2 updates on my ESXi box.  Both required fresh install.

i.e. I need to manually format the first 2 partitions in the data disks and it will then allow me to install the new pat files.

Or else the recovery process will kill the DSM.

 

But it is weird that the DSM stop working in around 3 days.

 

Is there anything I can check if I managed to get back to the DSM screen or SSH console?

There are some chances that I can get it connected and then the instances will be stable.  But new connection cannot be made.

So my VM has now been stable and running for 3 days and 3 hours now.  Completely backed up the entire storage array to Crashplan using the docker image and there has been no issues with it what so ever.

 

Would still like to know what happens if I directly update the DSM version to latest with the newest bootloader?  I presume it will break?  Is the only way to rebuild the OS partitions on the array?

Share this post


Link to post
Share on other sites

Hi! Making a clear install of DSM 6.1 on a PC with 1.02b bootloader. Everything works fine until reboot. After reboot there's an grub error in rescue mode - no such partition. Flashing the stick again returns DSM to life but till next reboot. Is there a solution?

 

Moved to another topic. Deletable.

Edited by Riddick

Share this post


Link to post
Share on other sites

Hi,

 

I tried to update my Nas but unfortunately I have encountered an issue : the loader 1.02b or 1.01a don't launch the OS!

 

Everything is working well with the Loader 1.01, DS3615xs and DSM 6.0.2-8451 Update 11. And it was the same for every update until now.

So there is something different I can't catch with all the notices on this forum!

I put the extra package, copy my setup from grub.cfg, tried UEFI or Legacy, but at the best result, I can see loading kernel. And nothing else!

 

Would it be because I'm with the old SHR type ?

 

Thanks for any help!

 

Share this post


Link to post
Share on other sites
On 29/06/2017 at 8:54 AM, Designator said:

 

The problem for my amd system was that I couldn´t utilitize all of my ram. 30% was always marked as "not usable" by the system. Really annoying. So I switched to an Intel CPU and the amd system is laying aroun unused. I would love to have it as a fallback system.

same for me. have you "virtual machine manager" installed ? because but i wonder if it's not this package which eat all the ram.

Share this post


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

same for me. have you "virtual machine manager" installed ? because but i wonder if it's not this package which eat all the ram.

 

I had the first release of "virtual machine manager" installed on the amd system but the ram usage wasn´t related to the package.

Even after uninstalling DSM would not recognize all the installed ram.

 

I haven´t tested it with the latest loader yet.

Share this post


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

 

I had the first release of "virtual machine manager" installed on the amd system but the ram usage wasn´t related to the package.

Even after uninstalling DSM would not recognize all the installed ram.

 

I haven´t tested it with the latest loader yet.

I have an AMD on HP n54l, 16go of RAM working fine. Dsm 6.02 with juns loader 1.01. was running virtuabbox on dsm with multiple vm win and Linux.

 

 

I can't find spk of vbox for dsm 6.02 :'(

Share this post


Link to post
Share on other sites

was running virtuabbox on dsm with multiple vm win and Linux.

 

With dsm 5 

Share this post


Link to post
Share on other sites
 
I had the first release of "virtual machine manager" installed on the amd system but the ram usage wasn´t related to the package.
Even after uninstalling DSM would not recognize all the installed ram.
 
I haven´t tested it with the latest loader yet.

I'm on 1.02b with an amd 5350 Asus am1i-A with the latest update of ds3617xs 6.1.2.xxx
Before on 1.01a all my ram was recognize.

Envoyé de mon SM-G935F en utilisant Tapatalk

Share this post


Link to post
Share on other sites

How did you get this loader :
v1.02b (DS3615xs , DS3615xs and DS916+) is for DSM 6.1 - AMD not compatible - Latest version for DSM 6.1

 

on amd ?

 

When i try find.synology can't find the device

Share this post


Link to post
Share on other sites
15 minutes ago, ygor said:

How did you get this loader :
v1.02b (DS3615xs , DS3615xs and DS916+) is for DSM 6.1 - AMD not compatible - Latest version for DSM 6.1

 

on amd ?

 

When i try find.synology can't find the device

i think "(DS3615xs , DS3615xs and DS916+)" it's a mistake and it's rather : "(DS3615xs , DS3617xs and DS916+)" 

my MB AM1I-A got a Realtek® 8111GR, LAN controler and the driver is included in 1.02b.

it works but it's not fully compatible.

Share this post


Link to post
Share on other sites

I have a baremetal install on hp microserver gen8 of DSM 6.0.2 with loader v1.01.

I understand that in order to update to DSM 6.1, I would have to backup my data and do a clean install.

My data is currently backed up to an external drive using HyperBackup.

It is probably silly to ask, but I was hoping to get a quick confo that I will be able to restore from my HyperBackup archive once I have DSM 6.1 up and running?

 

Thanks!

Share this post


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

I have an AMD on HP n54l, 16go of RAM working fine. Dsm 6.02 with juns loader 1.01. was running virtuabbox on dsm with multiple vm win and Linux.

 

 

I can't find spk of vbox for dsm 6.02 :'(

after some research this is what i founed :

 

  • my bios is at the latest possible update
 
cat /proc/mtrr
reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back
reg01: base=0x080000000 ( 2048MB), size= 512MB, count=1: write-back
  • My physical memory is well recognized

 

dmidecode --type memory
# dmidecode 2.12                                                                                             
# SMBIOS entry point at 0x000f04c0                                                                           
SMBIOS 2.7 present.                                                                                          
                                                                                                             
Handle 0x0029, DMI type 16, 23 bytes                                                                         
Physical Memory Array                                                                                        
        Location: System Board Or Motherboard                                                                
        Use: System Memory                                                                                   
        Error Correction Type: None                                                                          
        Maximum Capacity: 8 GB                                                                               
        Error Information Handle: Not Provided                                                               
        Number Of Devices: 2                                                                                 
                                                                                                             
Handle 0x002B, DMI type 17, 34 bytes                                                                         
Memory Device                                                                                                
        Array Handle: 0x0029                                                                                 
        Error Information Handle: Not Provided                                                               
        Total Width: 64 bits                                                                                 
        Data Width: 64 bits                                                                                  
        Size: 4096 MB                                                                                        
        Form Factor: DIMM                                                                                    
        Set: None                                                                                            
        Locator: DIMM_A1                                                                                     
        Bank Locator: CHANNEL A                                                                              
        Type: DDR3                                                                                           
        Type Detail: Synchronous Unbuffered (Unregistered)                                                   
        Speed: 800 MHz                                                                                       
        Manufacturer: <BAD INDEX>                                                                            
        Serial Number: 070704B0                                                                              
        Asset Tag: <BAD INDEX>                                                                               
        Part Number: <BAD INDEX>                                                                             
        Rank: 1                                                                                              
        Configured Clock Speed: 667 MHz                                                                      
                                                                                                             
Handle 0x002C, DMI type 17, 34 bytes                                                                         
Memory Device                                                                                                
        Array Handle: 0x0029                                                                                 
        Error Information Handle: Not Provided                                                               
        Total Width: 64 bits                                                                                 
        Data Width: 64 bits                                                                                  
        Size: 4096 MB                                                                                        
        Form Factor: DIMM                                                                                    
        Set: None                                                                                            
        Locator: DIMM_A2                                                                                     
        Bank Locator: CHANNEL A                                                                              
        Type: DDR3                                                                                           
        Type Detail: Synchronous Unbuffered (Unregistered)                                                   
        Speed: 800 MHz                                                                                       
        Manufacturer: <BAD INDEX>                                                                            
        Serial Number: 070704B0                                                                              
        Asset Tag: <BAD INDEX>                                                                               
        Part Number: <BAD INDEX>                                                                             
        Rank: 1                                                                                              
        Configured Clock Speed: 667 MHz  

 

 

  • after look into kernel log : 
Linux version 3.10.102 (root@build3) (gcc version 4.
9.3 20150311 (prerelease) (crosstool-NG 1.20.0) ) #15132 SMP Wed Jun 14 12:26:43 CST 2017                    
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000] CPU: vendor_id 'AuthenticAMD' unknown, using generic
 init.                                                                                                       
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000] CPU: Your system may be unstable.                   
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000] efi: mem66: type=4, attr=0xf, range=[0x000000008fea3
000-0x000000008ffe1000) (1MB)                                                                                
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000] efi: mem67: type=7, attr=0xf, range=[0x000000008ffe1
000-0x000000008ffe2000) (0MB)                                                                                
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000] WARNING: BIOS bug: CPU MTRRs don't cover all of memo
ry, losing 5104MB of RAM.                                                                                    
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000] ------------[ cut here ]------------                
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000] WARNING: at arch/x86/kernel/cpu/mtrr/cleanup.c:971 m
trr_trim_uncached_memory+0x42d/0x456()                                                                       
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000] Modules linked in:                                  
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 3.10.102 #15
132                                                                                                          
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000] Hardware name: ASUS All Series/AM1I-A, BIOS 0801 03/
10/2016                                                                                                      
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000]  ffffffff814a8af8 ffffffff81033ee6 00000000000013f0 
ffffffff818fd480                                                                                             
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000]  0000000000000000 000000000023f000 ffffffff818fbd00 
ffffffff818835b5                                                                                             
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000]  070000000000000c 0000000000080000 0000000000000000 
0000000000000000                                                                                             
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000] Call Trace:                                         
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000]  [<ffffffff814a8af8>] ? dump_stack+0xc/0x15         
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000]  [<ffffffff81033ee6>] ? warn_slowpath_common+0x56/0x
70                                                                                                           
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000]  [<ffffffff818835b5>] ? mtrr_trim_uncached_memory+0x
42d/0x456                                                                                                    
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000]  [<ffffffff8187e07c>] ? setup_arch+0x555/0xc50      
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000]  [<ffffffff814a7e6b>] ? printk+0x4a/0x52            
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000]  [<ffffffff8187a957>] ? start_kernel+0x7b/0x3b0     
2017-06-20T19:19:52+02:00 berlioz kernel: [    0.000000] ---[ end trace 0d92bc4b6dbe0d45 ]---                

I will try some kernel/grub options to see if it's better.

 

 

 

Interested links :

https://comeandtechit.wordpress.com/tag/enable_mtrr_cleanup-mtrr_spare_reg_nr1/

https://bbs.archlinux.org/viewtopic.php?id=116080

http://www.linuxquestions.org/questions/slackware-14/how-to-properly-edit-mtrr-memory-type-range-registers-for-4gb-ram-memory-903691/

https://superuser.com/questions/1055097/mtrrs-do-not-cover-all-16gb-of-memory-on-n3150

http://my-fuzzy-logic.de/blog/index.php?/archives/41-Solving-linux-MTRR-problems.html

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

Share this post


Link to post
Share on other sites
19 hours ago, thomas1014 said:

i think "(DS3615xs , DS3615xs and DS916+)" it's a mistake and it's rather : "(DS3615xs , DS3617xs and DS916+)" 

Indeed. It's a typo. It has been corrected.

  • Like 1

Share this post


Link to post
Share on other sites

Hi everyone!
DSM on my gen8 was updated to 1.02b (DS3617xs). After a day I was not able to load any web page - "Sorry, the page you are looking for is not found."
I had reinstalled DSM and everything were working as before. Today I have received the same message again.

Edited by Error404

Share this post


Link to post
Share on other sites

 

Can you give some technical informations about your installation?
Baremetal or VM? What processor, memory? How did you update to 1.02b?

It's difficult to help, if there are so few infos.

Share this post


Link to post
Share on other sites

Hello. Thanks for the great work.
So upgrading from 6.0.2 to 6.1.2 (using the right bootloader) will or not lose the data on the disks? Thank you.

Share this post


Link to post
Share on other sites

Does any one know if Jun is "Still" working on AMD support? 

Or did anyone had success building a kernel with AMD modules for 6.1.X ?

Best Regards,

Toetje

Share this post


Link to post
Share on other sites
On 7/1/2017 at 5:54 AM, cmpugay said:

For past few days, I'm trying to upgrade existing Synology install to v. 6.1.15132 but after completing 56%, it throws an error :

 

Failed to install the file. The file is probably corrupt.

 

After this I'm not able to access my data.

 

As I had a backup, hence I removed all the HDDs from my Custom System and formatted it to remove any trace of Synology.

 

Then I replaced them back into my existing Synology system.

 

Now first time it displayed the SETUP and I started from Fresh but after completing approx. 56% it threw error as shown in attached screenshot.

 

After than I attempted to install again but now it is showing MIGRATE and even Migration option is throwing same error after completing 56%.

 

Please help... else I have to look for some other solution.

 

Document1.pdf

did you find answer i too have this problem

Share this post


Link to post
Share on other sites
8 hours ago, hpk said:

 

Can you give some technical informations about your installation?
Baremetal or VM? What processor, memory? How did you update to 1.02b?

It's difficult to help, if there are so few infos.

I'm sorry, I thought the information was displayed in my signature.

v1.02b , Baremetal  - DSM_DS3617xs_15047,  HP ProLiant MicroServer Gen8 Xeon(R) CPU E3-1220 V2/8Gb/2*1TB(RAID0)+2x4Tb(RAID1), USB loader, iLO 2.50 

I used @Polanskiman's tutorial.

Edited by Error404

Share this post


Link to post
Share on other sites
5 hours ago, dman4u1 said:

did you find answer i too have this problem

Finally I was able to do the task.

 

1. I used 1.02.a loader with older DSM

2. Then I upgraded to latest DSM.

Now it is working fine.

 

Share this post


Link to post
Share on other sites
13 hours ago, Error404 said:

Hi everyone!
DSM on my gen8 was updated to 1.02b (DS3617xs). After a day I was not able to load any web page - "Sorry, the page you are looking for is not found."
I had reinstalled DSM and everything were working as before. Today I have received the same message again.

 

Do I understand you right? After a day or so, you're not able to connect to the DS3617xs via webinterface?
Sounds like we have the timebomb again ... 


I got my HPE MicroServer with Xeon Processor yesterday and did two tests based on 1.02b and 3617xs:

- Running a baremetal installation of XPEnology ... no issues at all, took me less than 10 minutes

 

- Installing ESXi 6.5 and setup a virtual DS3617xs. Took me two hours or so, as I did some silly mistakes   :-)

Unfortunately, I did not run the baremetall installation for a long time, so I can't confirm, if there is an issue in general as you see it.
The VM is running since yesterday, backups running all night, filling up the disk nicely ... 

When I'm finished with the installation (a Linux and a Windows VM), I will take out the ESXi disks and run the baremetal one for a few days to see, if I can reproduce your error. But that will be next week ... 

Share this post


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

 

Do I understand you right? After a day or so, you're not able to connect to the DS3617xs via webinterface?
Sounds like we have the timebomb again ... 

Yes, that's right, you understand me correctly. Mobile applications were unavailable too. SMB, Plex and others were working.

I have reinstalled DSM again and it's working about 5 hours.

2017-07-04_22-15-34.png

Edited by Error404

Share this post


Link to post
Share on other sites

Just want to share my experience with this awesome project :-)

 

I am running the latest Bootloader 1.02b on ESXI 6.0 without issues or any timebomb problem:

595ca3ba9d191_2017-07-0510_29_57-diskstation-SynologyDiskStation.jpg.4384a6f406369af1b7c1fdd52434f38a.jpg

 

Had some issues initially after NIC Teaming (network not responding) and had some bad troubles to get the synoboot.img back to work (Serial + MAC) and DSM to respond to the Network again but after resetting serials and MAC's averything went fine again. In fact running this on VMWare is a very nice setup as you are still able to run other machines in parallel and backup/restore of the DSM VM should give some additional safety nets also.

 

Just wondering if there is any helpful Information available on

1) how the bootloader really works in detail e.g. sequence of loading (this might give evberyone better ideas on where to start troubleshooting).

2) How to attach to the serial port on the VM? Does anyone know?

3) How to map the virtual disk (vmdk) of the VM's system drive (tried some findings from google but the image is not recognized by osfmount for example) to adjust DSM settings in case of emergencies.

4) Is there an up-to-date wiki somewhere?

 

In Summary....highly appreciate all the work from devs and others on this project. Please keep up as this is really an essential good piece of work.

Is there any way to give you some donations? (sorry did not search here :-) )

 

Thanks

Edited by lunzet
jpg

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