DSM 6.1.x Loader


Recommended Posts

1 hour ago, NoFate said:

realy strange, maybe i need to check it again

 

there were other people also that had the same issues : 

 

 

Lunzet, can you maybe make an export of your setup ?

 

thnx

 

 

 

so what kind of export are u interested in?

vm config? dsm config? smb config? not sure.....

Link to post
Share on other sites
Guest codedmidn

I have a testing VM running on ESXi with the this version (v1.02b (DS3615xs, DS3617xs and DS916+) ) i install it on 24/06/2017 today i get the "sorry page" can't access telnet/ssh or web the fileshare/samba still works

I have setup the install to download but manual install updates but last night a power failure occurs and tofay "sorry page"

 

I create a new VM with the same settings, create a snapshot and the update to the latest version (dsm 6.1.2-15132) and i loose access again.. so maybe exist a problem with this jun's version running in esxi and the latest version?

Link to post
Share on other sites

Hey guys, thanks for all the good work and help here.

Just wanted to share my successful migration from

DSM 6.0.2 DS3615 using loader 1.02a to

DSM 6.1.2 DS3617 using loader 1.02b

 

Server: DSM running as virtual machine on ESXI 6.5 Skylake Platform

The machine is bootet from m.2 NVMe disk which contains ESXI and all VMs.

The onboard SATA-Controller is set to passthrough to the DSM VM where 5 HDDs are attached.

 

I followed instructions from here with some additions / changes

 

# after first bootup it says old DS3615 disks were detected and it starts migration

# after second bootup it says it will now install my new DSM to the disks  <-- this step repeated over and over again until i changed the synoboot.vmdk to boot from virtual sata controller 0:0 instead of the virtual scsi controller 0:0

 

After that change everything runs very fine now. I did some restarts just to test and it was booting up perfectly everytime.

DSM was running for more than 3 days now. I then did a manuel restart just to test again and its still ok.

 

DS3617 feels much faster and more responsive on my hardware.

 

 

 

Link to post
Share on other sites

HI to everyone! I've a problem.. somebody can help me?

I've a XPenology 3615xs running DSM 5.2 and I'm trying to migrate it to DSM 6.1.2 15132 with jun's loader 1.02b.
The problem is that when I boot my PC, it shows:
 

Decompressing Linux... Parsing ELF... done.

Booting the kernel

 

And after 10 seconds the PC reboots 

 

My PC config:
Mainboard Asrock H81M-HDS

CPU Celeron G1840 2,80GHz
Ram 4Gb DDR3
 
What's the problem? What Can I do?!? Thanks for your support
Link to post
Share on other sites
1 hour ago, maxime said:

HI to everyone! I've a problem.. somebody can help me?

I've a XPenology 3615xs running DSM 5.2 and I'm trying to migrate it to DSM 6.1.2 15132 with jun's loader 1.02b.
The problem is that when I boot my PC, it shows:
 

Decompressing Linux... Parsing ELF... done.

Booting the kernel

 

And after 10 seconds the PC reboots 

 

My PC config:
Mainboard Asrock H81M-HDS

CPU Celeron G1840 2,80GHz
Ram 4Gb DDR3
 
What's the problem? What Can I do?!? Thanks for your support


I understand that the problem was modified extra.lzma file. I restored original extra.lzma file, and now the bootloader works!
But now I've another problem: when i choose "Migrate" and I choose DSM_DS3615xs_15132.pat, the installation stop at 58% saying the file is probably corrupted. 

What can I do, now? Thanks!

Edited by maxime
Link to post
Share on other sites
On 2/7/2017 at 3:43 PM, Schirocco said:

 

Hello @ all, 
I run an Acer Easystore H340 
 - CPU Intel® Atom 230
- Chipset: Intel® 945GC Express + ICH7R
- RAM: 2GB DDR2 SDRAM 667MHz

XPenology v1.02Loader with DSM 6.1.2 on external USB Stick

I updated from 5.1 -> 5.2 and then with the v1.02Loader to 6.1.2 Everything is working fine so far, but I can verify that till 5.1 the server shut down normally via webinterface and with newer software it reboots every time.

Maybe someone else has a fix meanwhile?
 

Sorry, I can't help you.. can I ask you a question?
Did I get it right? You boot your XPEnology DSM 5.2 with June's bootloader 1.02b and then you upgraded it to DSM 6.1.2 from web interface? You did it directly or step by step (5.2->6.0->6.1->6.1.2)? Thanks for your reply!

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

Sorry, I can't help you.. can I ask you a question?
Did I get it right? You boot your XPEnology DSM 5.2 with June's bootloader 1.02b and then you upgraded it to DSM 6.1.2 from web interface? You did it directly or step by step (5.2->6.0->6.1->6.1.2)? Thanks for your reply!

Seems clear to me. He went from 5.1 to 5.2 and then to 6.1.2  directly. There is no need to upgrade to 6.0.2. or 6.1 anyway if your objective is to upgrade to 6.1.2

Link to post
Share on other sites

Hi,

 

made yesterday a migration from real DS1815+ to Xpenology  DS3617xs  with 1.02b. Works perfect without data lost.

Thats the way I made it:

1. Bring DS1815+ to FW DSM 6.1.2-15132

2. Prepare USB Stick

3. shut down both boxes

4. move 8 hard disk 6 TB WD RED from old DS to new DS

5. Boot up new DS with grub menu 2 (reinstall)

6. find new ds with finder.

7. connect to new DS. Shows me "ready to migrate"

8. Choose leave data (think menu 1  default)

9. Download PAT manual with PC and select this

10. After some minutes new DS reboots and finish. (check that grub entry 1 is selected)

11. done

 

 

Hope that helps.

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

Seems clear to me. He went from 5.1 to 5.2 and then to 6.1.2  directly. There is no need to upgrade to 6.0.2. or 6.1 anyway if your objective is to upgrade to 6.1.2

Ok, thanks

Edited by maxime
Link to post
Share on other sites
On 12.7.2017 at 0:06 PM, Error404 said:

So anybody knows how to fix this issue? =) I guess I should to downgrade to 6.0 =(

Thank you guys!

 

i have the exact same problem on 2 machines (one with vm disks, one with rdm's), i have a third machine that is not having this problem at all (using another port than 5000/5001)

 

is it a time bomb or just a bug?

Link to post
Share on other sites
On 7/12/2017 at 1:20 PM, NoFate said:

guys running on ESX, dont you have slow SMB speeds when copying a large folder containg more then like 20-30 GB 

 

for me its starts at the expected speed at 110 MB/sec , but after like 20 sec, it drops to  10 kb ... and thetn stutters on 10 MB

the only way i get SMB speeds is to run on baremetal 

tried it on my older asrock device, now i have a hp micro gen 8 , same issue , also tried esx 5 and 6.5

Might be an esx issue; read about it here, there is also an easy fix; read at least the last 3 pages :

https://homeservershow.com/forums/topic/9602-esxi-notes/?page=10

this is the solution, from that topic (working for me with esxi 6.5):

"

downloaded the hpvsa-5.5.0-88.zip archive (as per HP advisory) and uploaded the vib to the datastore. eg  /datastore1/patch/scsi-hpvsa-5.5.0-88OEM.550.0.0.1331820.x86_64.vib via the ESXi web interface
 
8. remove the exsisting scsi-hpvsa_5.5.0.102-1O driver (via SSH) (enable maintenance mode first)
# esxcli software vib remove -n HPE:scsi-hpvsa
 
Removal Result
   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
   Reboot Required: true
   VIBs Installed:
   VIBs Removed: HPE_bootbank_scsi-hpvsa_5.5.0.102-1OEM.550.0.0.1331820
   VIBs Skipped:
 
9. Install the scsi-hpvsa-5.5.0-88 downgraded driver 
# esxcli software vib install --viburl=/vmfs/volumes/datastore1/patch/scsi-hpvsa-5.5.0-88OEM.550.0.0.1331820.x86_64.vib
 
Installation Result
   Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
   Reboot Required: true
   VIBs Installed: Hewlett-Packard_bootbank_scsi-hpvsa_5.5.0-88OEM.550.0.0.1331820
   VIBs Removed:
   VIBs Skipped:
 
10. Disable ESXi vmc_ahci module (if not completed, ahci is used by default. eg array is not initialised via hpvsa and ahci initialises disks as 4 separate physical disks) 
# esxcli system module set --enabled=false --module=vmw_ahci
 
11. Reboot Server
 
12. Re-test file write speed to local data store (disable maintenance mode and enable TSM-SSH first)
 
# cd /vmfs/volumes/datastore1 
# time dd if=/dev/zero of=tempfile bs=8k count=1000000
 
1000000+0 records in
1000000+0 records out
real    1m 40.79s
user    0m 3.70s
sys     0m 0.00s
 
much better
"
for esxi 6.0 you don't need to disable vmc_ahci module (step 10) but it is required on 6.5

 

Edited by koroziv
  • Like 2
Link to post
Share on other sites
Might be an esx issue; read about it here, there is also an easy fix; read at least the last 3 pages :
https://homeservershow.com/forums/topic/9602-esxi-notes/?page=10
this is the solution, from that topic (working for me with esxi 6.5):
"
downloaded the hpvsa-5.5.0-88.zip archive (as per HP advisory) and uploaded the vib to the datastore. eg  /datastore1/patch/scsi-hpvsa-5.5.0-88OEM.550.0.0.1331820.x86_64.vib via the ESXi web interface http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=c05026755   8. remove the exsisting scsi-hpvsa_5.5.0.102-1O driver (via SSH) (enable maintenance mode first) # esxcli software vib remove -n HPE:scsi-hpvsa   Removal Result    Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.    Reboot Required: true    VIBs Installed:    VIBs Removed: HPE_bootbank_scsi-hpvsa_5.5.0.102-1OEM.550.0.0.1331820    VIBs Skipped:   9. Install the scsi-hpvsa-5.5.0-88 downgraded driver  # esxcli software vib install --viburl=/vmfs/volumes/datastore1/patch/scsi-hpvsa-5.5.0-88OEM.550.0.0.1331820.x86_64.vib   Installation Result    Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.    Reboot Required: true    VIBs Installed: Hewlett-Packard_bootbank_scsi-hpvsa_5.5.0-88OEM.550.0.0.1331820    VIBs Removed:    VIBs Skipped:   10. Disable ESXi vmc_ahci module (if not completed, ahci is used by default. eg array is not initialised via hpvsa and ahci initialises disks as 4 separate physical disks)  # esxcli system module set --enabled=false --module=vmw_ahci   11. Reboot Server   12. Re-test file write speed to local data store (disable maintenance mode and enable TSM-SSH first)   # cd /vmfs/volumes/datastore1  # time dd if=/dev/zero of=tempfile bs=8k count=1000000   1000000+0 records in 1000000+0 records out real    1m 40.79s user    0m 3.70s sys     0m 0.00s   much better " for esxi 6.0 you don't need to disable vmc_ahci module (step 10) but it is required on 6.5  


Thanks for the info. Here is the link to the original thread which is better to read:
https://homeservershow.com/forums/topic/9602-esxi-notes/?do=findComment&comment=137174
Link to post
Share on other sites

bootloader 1.02b (3615xs, baremetal)

 

Updated from 
DSM 6.1.2-15132 Update 1
to
DSM 6.1.3-15152

 

Release Notes : 6.1.3-15152

https://www.synology.com/en-global/releaseNote/DS3615xs


so far so good

 

uname -a


Linux DS3615xs 3.10.102 #15152 SMP Thu Jul 13 04:20:59 CST 2017 x86_64 GNU/Linux synology_bromolow_3615xs

 

cat /etc/VERSION


majorversion="6"
minorversion="1"
productversion="6.1.3"
buildphase="GM"
buildnumber="15152"
smallfixnumber="0"
builddate="2017/07/13"
buildtime="07:04:22"

Edited by ad911
Link to post
Share on other sites
On 7/12/2017 at 1:06 PM, Error404 said:

So anybody knows how to fix this issue? =) I guess I should to downgrade to 6.0 =(

Thank you guys!

Could the time bomb be due to changing SN and MAC addresses?
Previously, I used version 3615xs, updated to 3617 and, of course, decided to change these settings.

Link to post
Share on other sites

Just ran two tests upgrades and both went without a hitch!

 

bootloader 1.02b ( DS3617xs, ESXi 6.5)

 

Updated from DSM 6.1.2-15132 Update 1   to   DSM 6.1.3-15152

 

So far running great!

Edited by maartenl
  • Like 1
Link to post
Share on other sites

Update from 6.1.2 to 6.1.3 on DS3615xs (ESXi 6.5) did not work, 

Did a snapshot before the update but cannot go back ... 

DS3615xs is found with a new IP and the system wants to restore it, but without success ...

 

So be careful ... 

I dig a bit to find out, what's going wrong.

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

Just ran two tests upgrades and both went without a hitch!

 

bootloader 1.02b ( DS3617xs, ESXi 6.5)

 

Updated from DSM 6.1.2-15132 Update 1   to   DSM 6.1.3-15152

 

So far running great!

 

Good. Did you do a classic automatic update from control panel on web interface?  

Link to post
Share on other sites

There's no way to upgrade my XPEnology! :?
I've always got this error:  ”Failed to install the file. The file is probably corrupted. (13)".
I'm 300% sure my VID and PID are right (I tried 3 differents USB Key), I also tried to edit grub on startup, but it doesn't work.
On tutorial for Jun's v1.01 
bootloader is written: If you got error 13 then try to 'Force Install'... but Jun's v1.02b bootloader have not this choose.

I choosed menù 2 REINSTALL but I've got the same error.
And now, what can I do?!? I'm so depressed... 

 

PS: I Tried DS3615 and DS3617 too

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