Polanskiman

Please read the READ ME topic before posting:

 

Message added by Polanskiman

Recommended Posts

Posted (edited)

This is an INTERMEDIATE update of DSM.

DO NOT UPDATE TO DSM 6.2.1 with Jun's loader 1.03a2 or  1.03b or earlier.

You will most certainly brick your box because of a change in the kernel config that breaks all non official PCIe devices drivers. This has been confirmed by Jun.

 

 You have been warned.

 

 

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

Spoiler

(2018-08-29)

Important Note

The update is expected to be available for all regions within the next few weeks, although the time of release in each region may vary slightly.

After system upgrades to DSM 6.2.1, the HASP package will not be supported.

For the following models, DSM 6.2 will be the last upgradable version. DSM 6.2 will continue to receive critical and security updates for a minimum of 2 years after the official release.

XS Series : RS3412xs, RS3412RPxs, RS3411xs, RS3411RPxs, DS3612xs, DS3611xs

Plus Series : RS2212+, RS2212RP+, RS2211+, RS2211RP+, RS812+, RS812RP+,

DS2411+, DS1812+, DS1512+, DS1511+, DS712+, DS412+, DS411+II, DS411+,

DS213+, DS212+, DS211+, DS112+

Value Series : RS812, RS212, DS413, DS411, DS213, DS212, DS211, DS112, DS111

J Series : DS413j, DS411j, DS411slim, DS213air, DS212j, DS211j, DS112j

Others : NVR216, NVR1218, DDSM

What's New in DSM 6.2.1

Space reclamation speed of legacy Advanced LUNs is now adjustable.

You can now convert legacy Advanced LUNs into new Advanced LUNs, which come with instant snapshots and performance improvements.

Added password strength meter for creating and modifying passwords.

When you install or upgrade your DSM version through the Internet, it will now automatically be upgraded to the corresponding DSM version with critical and security updates. The following models are not available due to hardware performance limitations.

11 series: RS411, DS411slim, DS411j, DS411, DS211j, DS211+, DS211, DS111

12 series: RS812, RS212, DS212j, DS212+, DS212, DS112j, DS112+, DS112

13 series: DS413j, DS413, DS213j, DS213air, DS213+, DS213

14 series: RS814, DS414slim, DS414j, DS414, RS214, DS214se, DS214+, DS214, DS114

15 series: RS815, DS215j, DS115j, DS115

16 series: DS216se

Fixed Issues

Fixed an issue where users may not be able to delete snapshots when the volume is full.

Fixed an issue where Windows may falsely detect an error on an exFAT format USB drive after it is used as the backup destination of Hyper Backup.

Improved Snapshot Replication package stability.

Fixed an issue where incorrect or incomplete update information may be displayed in the DSM Update tab.

Fixed an issue where a single RAID with over 24 drives may fail to assemble a RAID 5/6/F1 or SHR 1/2 storage pool.

Fixed an issue where boot failure might occur if the system was rebooted during the conversion process from RAID 5 to RAID 6.

Enhanced the compatibility of certain drives on Synology NAS and Expansion Unit models.

Fixed an issue where local users may fail to log in via SMB on specific Windows versions after adding their NAS to a Synology Active Directory domain.

Improved Windows client's clock synchronization with DSM after it is added to a Synology Active Directory domain. Upgrading Active Directory Server to version 4.4.5-0077 or above is required.

Modified HDD hibernation mechanism to prevent HDDs from entering hibernation when a volume is degraded, crashed, or not created.

Fixed multiple security vulnerabilities regarding Linux kernel (CVE-2018-1000199, CVE-2018-8897, CVE-2017-0861).

Fixed a security vulnerability regarding OpenSSL (CVE-2018-0739).

Fixed a security vulnerability regarding procps-ng (CVE-2018-1124).

Fixed a security vulnerability regarding ISC DHCP (CVE-2017-3144).

Fixed multiple security vulnerabilities (Synology-SA-18:51).

Minor bug fixes.

 

Edited by Polanskiman
Updated warning as the loader itself is not the problem but modules contained in it. See recommended post.
  • Like 1
  • Sad 1

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: UNSUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: VM - HP Microserver GEN 8 - esxi 6.7 

- Additional comments: None

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: UNSUCCESSFUL

- DSM version prior update: DSM 6.2-23739 update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3617xs

- Using custom extra.lzma: NO

- Installation type: VM - HP Microserver GEN 8 - esxi 6.7

- Additional comments: None

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: UNSUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3617xs

- Using custom extra.lzma: NO

- Installation type: HP Microserver GEN 8 Baremetal

 

Reason:

The update provides a new zImage and rd.gz and is causing a kernel exception. It will not work without a new bootloader.

 

How to downgrade:

Replace zImage, extra.gz and rd.gz (open synology.img -> image.img with 7Zip) with the one from DS3615xs (use the opposite of what you have installed currently) so you will force a reinstall of DSM. You cannot migrate the settings, so you have to do a clean install (keeps your data). Afterwards replace the above files again with your original bootloader, for me its DS3617xs and do a fresh install again.

 

 

Spoiler

patching file etc/rc
patching file etc/synoinfo.conf
Hunk #1 FAILED at 261.
1 out of 1 hunk FAILED -- saving rejects to file etc/synoinfo.conf.rej
patching file linuxrc.syno
Hunk #3 succeeded at 552 (offset 1 line).
patching file usr/sbin/init.post
cat: can't open '/etc/synoinfo_override.conf': No such file or directory
START /linuxrc.syno
Insert Marvell 1475 SATA controller driver
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore ... [  OK  ]
:: Loading module ehci-hcd ... [  OK  ]
:: Loading module ehci-pci[    3.514331] kernel tried to execute NX-protected page - exploit attempt? (uid: 0)
[    3.550763] BUG: unable to handle kernel paging request at ffff880141d11f20
[    3.583998] IP: [<ffff880141d11f20>] 0xffff880141d11f1f
[    3.609062] PGD 1ac2067 PUD 1ac5067 PMD 8000000141c000e3
[    3.634944] Oops: 0011 [#1] SMP
[    3.650392] Modules linked in: ehci_pci(F+) ehci_hcd(F) usbcore usb_common mv14xx(O) m(OF)
[    3.689991] CPU: 0 PID: 3730 Comm: insmod Tainted: GF          O 3.10.105 #23824
[    3.725738] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 11/02/2015
[    3.759600] task: ffff880141dec040 ti: ffff88013e3f0000 task.ti: ffff88013e3f0000
[    3.795146] RIP: 0010:[<ffff880141d11f20>]  [<ffff880141d11f20>] 0xffff880141d11f1f
[    3.832126] RSP: 0018:ffff88013e3f3b78  EFLAGS: 00010046
[    3.857682] RAX: ffff880141913210 RBX: 0000000000000006 RCX: 0000000000000002
[    3.891721] RDX: 0000000000000006 RSI: 0000000000000000 RDI: ffff880141dc9800
[    3.926018] RBP: ffff880141dc9800 R08: ffff88013e3f3b84 R09: 000000000000fffb
[    3.960327] R10: 0000000000000000 R11: 000000000000000a R12: 0000000000000000
[    3.994344] R13: ffff88013e3f3bbe R14: 0000000000000246 R15: ffffffffa00ebb40
[    4.028838] FS:  00007faeb31c8700(0000) GS:ffff880147a00000(0000) knlGS:0000000000000000
[    4.067766] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[    4.095223] CR2: ffff880141d11f20 CR3: 000000013dace000 CR4: 00000000000607f0
[    4.129638] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    4.163832] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    4.197906] Stack:
[    4.207452]  ffffffff81292ea5 000000003e3f3bd8 0000000000000010 000000000000000a
[    4.242925]  ffff880141dc8ff8 0000000000000000 ffff880141dc9090 ffffffff81297fc6
[    4.278947]  0000000000000001 ffff880141dc8ff8 ffffffff8129800b ffff88013e0cc800
[    4.314259] Call Trace:
[    4.326162]  [<ffffffff81292ea5>] ? pci_bus_read_config_word+0x65/0x90
[    4.357374]  [<ffffffff81297fc6>] ? __pci_bus_find_cap_start+0x16/0x40
[    4.388912]  [<ffffffff8129800b>] ? pci_find_capability+0x1b/0x50
[    4.418067]  [<ffffffffa00eb09d>] ? ehci_pci_setup+0x9d/0x5a0 [ehci_pci]
[    4.450440]  [<ffffffffa00aac4d>] ? usb_add_hcd+0x1bd/0x660 [usbcore]
[    4.481258]  [<ffffffffa00b99d3>] ? usb_hcd_pci_probe+0x363/0x410 [usbcore]
[    4.514498]  [<ffffffff8129bd00>] ? pci_device_probe+0x60/0xa0
[    4.542750]  [<ffffffff813056da>] ? really_probe+0x5a/0x220
[    4.569743]  [<ffffffff81305961>] ? __driver_attach+0x81/0x90
[    4.597051]  [<ffffffff813058e0>] ? __device_attach+0x40/0x40
[    4.624804]  [<ffffffff813039d3>] ? bus_for_each_dev+0x53/0x90
[    4.652544]  [<ffffffff81304e78>] ? bus_add_driver+0x158/0x250
[    4.680508]  [<ffffffffa00ed000>] ? 0xffffffffa00ecfff
[    4.704941]  [<ffffffff81305f68>] ? driver_register+0x68/0x150
[    4.733129]  [<ffffffffa00ed000>] ? 0xffffffffa00ecfff
[    4.757936]  [<ffffffff810003aa>] ? do_one_initcall+0xea/0x140
[    4.785752]  [<ffffffff8108baf4>] ? load_module+0x1a04/0x2120
[    4.813385]  [<ffffffff81088cb0>] ? store_uevent+0x40/0x40
[    4.839772]  [<ffffffff8108c2a1>] ? SYSC_init_module+0x91/0xc0
[    4.867470]  [<ffffffff814c0dc4>] ? system_call_fastpath+0x22/0x27
[    4.896674]  [<ffffffff814c0d11>] ? system_call_after_swapgs+0xae/0x13f
[    4.928470] Code: 88 ff ff 00 00 00 00 00 00 00 00 30 00 50 30 43 30 32 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <70> 63 69 30 30 30 30 3a 30 30 00 00 00 00 00 00 00 00 00 00 00
[    5.019018] RIP  [<ffff880141d11f20>] 0xffff880141d11f1f
[    5.044485]  RSP <ffff88013e3f3b78>
[    5.061083] CR2: ffff880141d11f20
[    5.077034] ---[ end trace 15d40ebac4b70dfe ]---
 ... [FAILED]
:: Loading module ohci-hcd[    5.103741] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
 ... [  OK  ]
:: Loading module uhci-hcd[    5.137837] uhci_hcd: USB Universal Host Controller Interface driver
[   33.576195] Kernel panic - not syncing: Watchdog detected hard LOCKUP on cpu 2

 

  • Like 2

Share this post


Link to post
Share on other sites
On 8/29/2018 at 5:05 PM, luchuma said:

- Outcome of the installation/update: UNSUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: VM - HP Microserver GEN 8 - esxi 6.7 

 

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: VM - HP Microserver GEN 8 - esxi 6.7

- Additional comments: works with vm disks SATA, NIC E1000E, do not work with SCSI, SAS disks, NIC VMXNET3

  • Like 1

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3617xs

- Using custom extra.lzma: NO

- Installation type: i5 Baremetal

- Additional comments: None

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: UNSUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03a - DS918+

- Using custom extra.lzma: NO

- Installation type: Baremetal

- Additional comments: None

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.1 to DSM 6.2.1-23824

- Loader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: VM - HP Microserver GEN 8 - esxi 6.5 Update 1 - LSI 9211 passthrough

- Additional comments: See below

========================================================================================

*xpenoboot vmdk (osfmount and starwind method) loaded as a SATA disk (0:0) <- boot from this partition,

*system partition 15Go on a SATA disk (0:1) <- tricky to detect by Installer:  SataPortMap=88 , DiskIdxMap=0 in grub.cfg and choice 3 ESXI on boot screen. The xpenoboot partition is visible from DSM.

*two NIC E1000E (in esxi pay attention to the virtual switch which includes a security layer, if applicable ("authorize MAC override" and "Forged transmit" ). Symptom : no DHCP attribution from a server, no Ping)

*vmdk on SSD not recognized as SSD => put cache SSD volumes on the LSI 9211 passthrough card

*do not detect Virutal SCSI disk anymore. => SCSI controller ad disks removed

*VMXNET3 does not work anymore. // *open-vm-tools.spk 6.1_10.1.15-4 works ok with DSM 6.2 // transcoding does not work with old format SN

 

  • Like 2

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: UNSUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3617xs

- Using custom extra.lzma: NO

- Installation type: Baremetal (J1900)

 

Downgraded successfully manually installing 6.2 with DS3615xs loader (asks for reinstall keeping data)

Edited by m3rlin76

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: Optiplex 780

 

Capture.thumb.PNG.5d2988ce60518daceb67fe06013547ff.PNG

Share this post


Link to post
Share on other sites

- Outcome of the update: UNSUCCESSFUL

- DSM version prior update: DSM 6.1.7-15284 Update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - HP MicroServer Gen8 with Xeon 1265L and LSI SAS9220-8i in IT Mode.

- Additional comments: Tried upgrading from both 6.1.x and from 6.2. I can login in console but there is no network. NIC drivers are not loaded. A lot of kernel errors.

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: Fresh install on 6.2.1

- Loader version and model: JUN'S LOADER v1.03b - DS3617xs

- Using custom extra.lzma: NO

- Installation type: VM - ESXi 6.7 Virtual Machine on 3770k/16GB Ram/Intel Dual port NIC/Various disks drives for testing

- Additional comments: Works fine.. Just need to ensure you edit serial/mac's to suit your VM and install an additional SATA controller (in VM properties) then keep the Data disks on the second SATA controller (the 50MB boot drive on the first controller). SCSI disk types don't work (for me)..

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: Fresh install on 6.2.1

- Loader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: Baremetal - ASRock H110M ITX (Intel NIC), i5 7400, 8GB RAM

- Additional comments: Seems to work fine. Additional SATA ports from 88SE9128 PCIe card also work.

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: None.. This is a fresh install on 6.2.1

- Loader version and model: JUN'S LOADER v1.03b - DS3617xs

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - Asrock J3455 with single SATA drive and PCIe Intel NIC. 12GB RAM. This is the 4x SATA port version of the board.

- Additional comments: Very important, as always, to get your VID/PID/serial correct.. After upgrade, my onboard NIC didn't show up - but the PCIe Intel NIC works OK. Read and write speeds are pretty good actually; 110-113MB/s. All over Gbit ethernet & CAT6.

Thankfully it was a fresh test install - and not an upgrade (due to the onboard NIC).. More testing required..

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: BAREMETAL

-Additional Comments:

Intel 82579V, 1 x Gigabit LAN Controller On-Board
Intel 82574L, 1 x Gigabit LAN Controller On-Board

2x LSI9211-8i Card

Emulex OneConnect OCe11102, Dual-Port 10GBe SFP+ LAN Controller Card

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: UNSUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: Baremetal - HP Proliant Microserver N40L

-Additional Comments: Manual reset but the onboard NIC isn't reachable anymore, had to do a reinstall.

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03a - DS3918+

- Using custom extra.lzma: NO

- Installation type: BAREMETAL

-Additional Comments: Only NIC i211v ok , i219v ko

  • Like 1

Share this post


Link to post
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: DSM 6.2-23739 UPDATE 2

- Loader version and model: JUN'S LOADER v1.02a2 - DS918+

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - DELL Poweredge T30 (Intel Xeon)  

- Additional comments: Second Reboot required - No Problems with onboard Intel NIC

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03a - DS3615xs

- Using custom extra.lzma: NO

- Installation type: QEMU on Unraid 

-Additional Comments: NIC: e1000 changed to e1000e

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03a - DS3615xs

- Using custom extra.lzma: NO

- Installation type: BAREMETAL

- Additional comments: Normal boot does not work. Using Reinstall option. System boots ok

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - Asrock J3455

- Additional comments: Onboard lan not working, all ok with PCIE Intel NIC

Share this post


Link to post
Share on other sites

 

 Outcome of the installation/update: UNSUCCESSFUL

- DSM version prior update: DSM 6.2-23739 Update 2

- Loader version and model: JUN'S LOADER v1.03b - DS3617xs

- Using custom extra.lzma: NO

- Installation type: Asus H87 Baremetal

- Additional comments: None

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.2.1-23824 + JUN'S LOADER v1.03b - DS3615xs

- Loader version and model: JUN'S LOADER v1.03a2 - DS918+

- Using custom extra.lzma: NO

- Installation type: Baremetal (Asrock J3455)

- Additional comments: Onboard lan not tested, all ok with PCIE Intel NIC. Reinstalled 6.2.1 DS918+ over 6.2.1 DS3615xs with loader change... All data and settings ok.

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