DSM 6.1.x Loader


Recommended Posts

@ordimans

 

I upgraded from 5.2 to 6.0 and am now at 6.1 with the 1.02 3615xs alpha loader(yeah, i lost all my data in the process) and im not having any issues with my dell UPS connected through a usb cable. I have not done the update 1 for dsm 6.1 yet as i'm not sure if it breaks anything yet or not.

Link to post
Share on other sites

Thanks you

So it's a problem with DSM 6.0 and not with the loader ? I thought it was a driver problem....

 

 

But now I have another problem after power off the Dsm interface is not reachable ....

 

And SHR work with this loader or not ? I saw it's disable...

But I had no problem during the update from 5.2 to 6.0...

Link to post
Share on other sites
Yes, it seems that the loader for 3617xs doesn't patch all the system files correctly and a timebomb gets activated. Same problem here unfortunately (however, for the moment I'm saved due to having a working snapshot on ESXi). @Jun, are there any plans to update your 3617xs image to get rid of this?

 

I had the same problem but have used Jun's 3615XS loader and everything is working fine so far (no 'Page not found' error that happened in my 3617xs install and system has been up 24 hours+).

Link to post
Share on other sites
This thread needs be broken into one for each loader version. Each one has its own issues and following along is just confusing as hell. Who's the moderator around here?

 

I agree. Maybe per platform as well. So separate thread for barebones / Hyper V / ESXi / Virtual Box

 

 

Sent from my iPhone using Tapatalk

Link to post
Share on other sites

I sadly did the Upgrade from 6.0 to 6.1 on my N40L with Juns Loader 1.01 ... After the Upgrade he offers me to recover the system. The Recovery aborts at 2% and the System will reboot.

The System is not available on the Network, when I boot another Option than "DS3615xs 6.02 Baremetal AMD $VERSION" and there is no Force Install or Reinstall Option for AMD. What I tried was the following:

menuentry "DS3615xs 6.02 Baremetal AMD $VERSION Reinstall" --class os {
       set img=/image/DS3615xs
       set zImage=bzImage
       savedefault
       loadlinux 3615 usb mfg
       loadinitrd
       showtips
}

menuentry "DS3615xs 6.02 Baremetal AMD $VERSION Force Install" --class os {
       set img=/image/DS3615xs
       set zImage=bzImage
       savedefault
       loadlinux 3615 usb mfg syno_port_thaw=1
       loadinitrd

 

But this makes no difference. He is just offering the 'Recovery'.

Using the 1.02a Image with the lack of an AMD Boot option is not working for my N40L because the Device is not going to be available on the network.

Was someone else able to fix this? Neither through Downgrading to 6.0 or bringing 6.1 to work?

 

EDIT1:

I booted with a linux usb stick(ubuntu) and used gparted to format the first linux raid partition (2.36GB, sdX1) on all 4 HDD's as 'unformatted'.

After a reboot I have been asked to install DSM again and I was able to chose an image manually. The Install Process was quiet fast and my DSM is up again.

My data is still there but all system-settings are lost. So there is a lot of work to do now, but I'm happy to have the system up again without losing my private data.

 

Greets

Philipp

Link to post
Share on other sites
EDIT1:

I booted with a linux usb stick(ubuntu) and used gparted to format the first linux raid partition (2.36GB, sdX1) on all 4 HDD's as 'unformatted'.

After a reboot I have been asked to install DSM again and I was able to chose an image manually. The Install Process was quiet fast and my DSM is up again.

My data is still there but all system-settings are lost. So there is a lot of work to do now, but I'm happy to have the system up again without losing my private data.

 

Greets

Philipp

 

Glad to hear you have been able to get your system up and running again without losing any data. Would you say, from your experience under the currently known situation that a clean install is the only way to run DSM 6.1 without problems, by formating the first linus parition with gparted and install DSM again is effectively same as a clean install of DSM 6.1 but without losing any data? thus could be the way out for now aside from the migrating route.

Link to post
Share on other sites

This works to make a clean installation of DSM again without losing your data ... But I've installed a 6.0 Image because there seems to be no AMD support for the 6.1 loader at the moment.

If there are no filesystem changes on 6.1 this should also work for 6.1 but I've not tested this.

 

For downgrading a previously made 6.0 to 6.1 upgrade back to 6.0 this is working. As soon as the new loader is working on AMD Systems like my HP N40L, I will try to upgrade to 6.1 again. But next time I will have a Backup of my Systemsettings :wink:

Link to post
Share on other sites
I sadly did the Upgrade from 6.0 to 6.1 on my N40L with Juns Loader 1.01 ... After the Upgrade he offers me to recover the system. The Recovery aborts at 2% and the System will reboot.

The System is not available on the Network, when I boot another Option than "DS3615xs 6.02 Baremetal AMD $VERSION" and there is no Force Install or Reinstall Option for AMD. What I tried was the following:

menuentry "DS3615xs 6.02 Baremetal AMD $VERSION Reinstall" --class os {
       set img=/image/DS3615xs
       set zImage=bzImage
       savedefault
       loadlinux 3615 usb mfg
       loadinitrd
       showtips
}

menuentry "DS3615xs 6.02 Baremetal AMD $VERSION Force Install" --class os {
       set img=/image/DS3615xs
       set zImage=bzImage
       savedefault
       loadlinux 3615 usb mfg syno_port_thaw=1
       loadinitrd

 

But this makes no difference. He is just offering the 'Recovery'.

Using the 1.02a Image with the lack of an AMD Boot option is not working for my N40L because the Device is not going to be available on the network.

Was someone else able to fix this? Neither through Downgrading to 6.0 or bringing 6.1 to work?

 

EDIT1:

I booted with a linux usb stick(ubuntu) and used gparted to format the first linux raid partition (2.36GB, sdX1) on all 4 HDD's as 'unformatted'.

After a reboot I have been asked to install DSM again and I was able to chose an image manually. The Install Process was quiet fast and my DSM is up again.

My data is still there but all system-settings are lost. So there is a lot of work to do now, but I'm happy to have the system up again without losing my private data.

 

Greets

Philipp

 

Strange.

Why we need to format the first linux raid ?

 

Did you check the ping over the network ? Or just web interface ??

 

 

Did you use 1.02a from Jun or Trantor release ?

Link to post
Share on other sites

Unfortunately, I also installed the DS3617xs Image on my Vmware Workstation machine. Now, after about two days, the DSM is offline as well.

 

Hopfully, somebody will identify the reason and find a solution :lol:

Link to post
Share on other sites

Help please, I added the driver for hyper-v hv_netvsc.ko, hv_storvsc.co.uk, hv_vmbus.o hv_balloon.ko to extral.lzma \usr\lib\modules\ and updated rc.modules, but the network does not work.

What am I doing wrong?

How to display enable the log boot?

Link to post
Share on other sites

Hello Everyone,

 

I am new here. I am busy with installing my own DIY server.

Now I follow all the steps for synology but everytime I get status "recoverable".

 

I wipe the disks, install again, restart and again recoverable...

and again.. and again..

 

What do I wrong? What is the problem?

Link to post
Share on other sites

So I'm backing up, again, all my data on my 6.0.2 update 9 box..

My 'real' Syno box is ticking away on 6.1 nicely..

 

I'm not going anywhere near 6.1 on my custom, until I've tested it on my other test box - and the loader comes out of Alpha..

Good work as always guys.. :smile:

 

One thing.. Might it be better to start a shiny new topic for 6.1 - rather than in this DSM 6.0.2 loader topic?

Would keep things nice and organised - and avoid confusion between the versions, IMHO! :smile:

 

#H

Link to post
Share on other sites

Ok thanks. I will try.

 

 

I tried Trantor release too, but it's same. Not network signal... on the N40L motherboard and on the RTL8111...

 

 

EDIT: Same with it...

I tried :

DS3615xs 6.1 Jun's Mod V1.02-alpha

DS3617xs 6.1 Jun's Mod V1.02-alpha

DS3615xs 6.1 Jun's Mod V1.02-alpha-TEST

 

Any working on N40l, no network...

 

 

Stay on 1.01 and 6.02/

Link to post
Share on other sites

Hi, I'm new to the forum, thank PhilAd, after upgrading to 6.1, the system would not start and the "DS3615xs 6.1 Jun's Mod V1.02-alpha" was not working. I did as instructed by PhilAd, with USB and GParted Live Ubunto I deleted the partition sdX1. I created the USB with "DS3615xs 6.1 Jun's Mod V1.02-alpha" using the grub.cfg the set values vid = xxxx set pid = xxxxx set sn = xxxxxxxxxx set mac1 = xxxxxxxxxx, I used in the previous version. So synology assistant on PC sees the NAS and allowing the installation of new DSM_DS3615xs_15047. The system must be reconfigured but recognizes the hard disk and you do not lose data. It also works quick connect and WOL. All with the system based on ASRock 3150 and WD 3TB

Link to post
Share on other sites

 

Strange.

Why we need to format the first linux raid ?

 

Did you check the ping over the network ? Or just web interface ??

 

 

Did you use 1.02a from Jun or Trantor release ?

 

I tried all of the three 1.02a images on mega.nz. Are there more available with AMD driver package?

 

Non of the Images worked with my N40L so far. There was no Network-Connection for sure. I checked the port on my switch and also the ARP-Table.

Because the System was stuck with 6.1 on loader 1.01 and 1.02 not working, I had to format the first partition to downgrade from 6.1 to 6.0 because he just offered me to recover the system which did not work. A reinstallation or forced installation was not possible on the N40L as I've described before.

Link to post
Share on other sites

 

Non of the Images worked with my N40L so far. There was no Network-Connection for sure. I checked the port on my switch and also the ARP-Table.

Because the System was stuck with 6.1 on loader 1.01 and 1.02 not working, I had to format the first partition to downgrade from 6.1 to 6.0 because he just offered me to recover the system which did not work. A reinstallation or forced installation was not possible on the N40L as I've described before.

 

When jun originally posted 1.02a he said "no AMD yet"

Link to post
Share on other sites

Hi, with Jun's Mod v1.01 and Jun's Mod v1.02-alpha for DS3615xs on vmware esxi 6.5 with vmxnet3 nic you can not set

the MTU higher than to 3050. with a MTU of 3051 the kernel panic happens.

 

[  148.828737] kernel BUG at /linux/syno/linux/drivers/net/vmxnet3/vmxnet3_drv.c:1314!
[  148.830679] invalid opcode: 0000 [#1] SMP 
[  148.831806] Modules linked in: cifs udf isofs loop nfsd exportfs rpcsec_gss_krb5 hid_generic usbhid hid usblp iscsi_target_mod(O) target_core_ep(O) target_core_file(O) target_core_iblock(O) target_core_mod(O) syno_extent_pool(PO) rodsp_ep(O) bromolow_synobios(PO) button ax88179_178a usbnet tg3 r8169 cnic bnx2 vmxnet3 pcnet32 e1000 sfc netxen_nic qlge qlcnic qla3xxx pch_gbe ptp_pch sky2 skge jme ipg uio alx atl1c atl1e atl1 libphy mii btrfs synoacl_vfs(PO) zlib_deflate hfsplus md4 hmac bnx2x(O) libcrc32c mdio mlx5_core(O) mlx4_en(O) mlx4_core(O) mlx_compat(O) compat(O) tn40xx(O) i40e(O) ixgbe(O) be2net(O) igb(O) i2c_algo_bit e1000e(O) dca fuse vfat fat crc32c_intel aesni_intel glue_helper lrw gf128mul ablk_helper arc4 cryptd ecryptfs sha512_generic sha256_generic sha1_generic ecb aes_x86_64 authenc des_generic ansi_cprng cts md5 cbc cpufreq_conservative cpufreq_powersave cpufreq_performance cpufreq_ondemand mperf processor thermal_sys cpufreq_stats freq_table dm_snapshot crc_itu_t crc_ccitt quota_v2 quota_tree psnap p8022 llc sit tunnel4 ip_tunnel ipv6 zram(C) sg mpt3sas mpt2sas(O) megaraid_sas ata_piix mptctl mptsas mptspi mptscsih mptbase scsi_transport_spi megaraid megaraid_mbox megaraid_mm vmw_pvscsi BusLogic usb_storage etxhci_hcd xhci_hcd uhci_hcd ohci_hcd ehci_pci ehci_hcd usbcore usb_common el000(O) [last unloaded: bromolow_synobios]
[  148.869803] CPU: 1 PID: 0 Comm: swapper/1 Tainted: P         C O 3.10.102 #15047
[  148.871911] Hardware name: VMware, Inc. VMware7,1/440BX Desktop Reference Platform, BIOS VMW71.00V.0.B64.1605280101 05/28/2016
[  148.875127] task: ffff88013a14a7b0 ti: ffff88013a154000 task.ti: ffff88013a154000
[  148.877243] RIP: 0010:[]  [] vmxnet3_rq_rx_complete+0x500/0x870 [vmxnet3]
[  148.880087] RSP: 0018:ffff88013fc43e30  EFLAGS: 00010246
[  148.881599] RAX: 0000000000000000 RBX: ffff880137f42f00 RCX: ffff880134cd6010
[  148.883690] RDX: 0000000000000100 RSI: 0000000000000002 RDI: 00000000000000fe
[  148.885783] RBP: ffff880137f42f00 R08: 0000000000000000 R09: 0000000000000001
[  148.887868] R10: ffff880137f42700 R11: 000000000101a8c0 R12: ffff880137b00000
[  148.889948] R13: ffff880136630880 R14: ffff880137480000 R15: 0000000000000000
[  148.892043] FS:  0000000000000000(0000) GS:ffff88013fc40000(0000) knlGS:0000000000000000
[  148.894398] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[  148.896092] CR2: 0000000000fd5008 CR3: 000000013734f000 CR4: 00000000001007e0
[  148.898237] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[  148.900412] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[  148.902504] Stack:
[  148.903123]  0000ffff81058e52 0000004000000000 ffff880137f42f20 ffff880137f42700
[  148.905465]  ffff880137f42700 ffff880137f42700 ffff880137f42f20 0000000000000040
[  148.907787]  ffff880137f42f00 00000000fffdb0ff ffff88013fc50d90 ffffffffa0a52bb0
[  148.910118] Call Trace:
[  148.910865]  
[  148.911494]  [] ? vmxnet3_poll_rx_only+0x30/0xa0 [vmxnet3]
[  148.913685]  [] ? net_rx_action+0xf9/0x160
[  148.915367]  [] ? __do_softirq+0xc6/0x1a0
[  148.917013]  [] ? call_softirq+0x1c/0x30
[  148.918643]  [] ? do_softirq+0x35/0x70
[  148.920249]  [] ? irq_exit+0x95/0xa0
[  148.921761]  [] ? do_IRQ+0x49/0xb0
[  148.923212]  [] ? common_interrupt+0x6a/0x6a
[  148.924870]  
[  148.925457]  [] ? arch_remove_reservations+0x110/0x110
[  148.927481]  [] ? default_idle+0x2/0x10
[  148.929014]  [] ? arch_cpu_idle+0x5/0x20
[  148.930569]  [] ? cpu_startup_entry+0x7d/0x160
[  148.932292] Code: 00 00 48 8b 7c 24 10 4c 89 ee e8 4c 75 99 e0 4c 8b 54 24 18 48 c7 85 d0 00 00 00 00 00 00 00 45 31 c0 e9 2d fc ff ff 0f 1f 40 00 <0f> 0b 66 0f 1f 44 00 00 0f 0b 66 0f 1f 44 00 00 3b 85 e4 00 00 
[  148.940228] RIP  [] vmxnet3_rq_rx_complete+0x500/0x870 [vmxnet3]
[  148.942405]  RSP 
[  148.943499] ---[ end trace 786e60951055932f ]---
[  148.944831] Kernel panic - not syncing: Fatal exception in interrupt
[  148.946813] Rebooting in 3 seconds..
[  152.025628] ACPI MEMORY or I/O RESET_REG.

 

best regards

zhschwan

Link to post
Share on other sites
Hello Everyone,

 

I am new here. I am busy with installing my own DIY server.

Now I follow all the steps for synology but everytime I get status "recoverable".

 

I wipe the disks, install again, restart and again recoverable...

and again.. and again..

 

What do I wrong? What is the problem?

 

 

Nobody?

Link to post
Share on other sites

Think I've spotted a potential little bug in the grub.cfg file (or in how it's applied)..

 

set common_args_3615='syno_hdd_powerup_seq=0 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet'

set sata_args='sata_uid=1 sata_pcislot=1 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=2 SasIdxMap=0'

 

If I leave SataPortMap=2 (I have 2 disks in my test box, so =2) in the set sata_args line, it doesnt work.. I get the old reported issues 'we've detected errors on disks 3,4,5 etc.

However, If I move the command up into the common_args line.......

 

set common_args_3615='syno_hdd_powerup_seq=0 SataPortMap=2 HddHotplug=0 syno_hw_version=DS3615xs vender_format_version=2 console=ttyS0,115200n8 withefi elevator=elevator quiet'

set sata_args='sata_uid=1 sata_pcislot=1 synoboot_satadom=1 DiskIdxMap=0C SasIdxMap=0'

 

...It works! :grin::grin::grin:

 

It boots fine and I get the 'Install' prompt - rather than a load of reported disk errors..

After applying the 6.1 PAT file and restarting, disks are fine, data is fine, it's now on 6.1.. :grin:

DSM61_zpsatcdqb2z.jpg~original

DSM61-2_zpsws2p4dgh.jpg~original

 

So........ Might there be an issue with applying the sata_args?

 

(Bare metal upgrade on an old Dell - for testing. 2x Sata disks)

 

Cheers,

 

#Hostilian

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.