Polanskiman

Please read the READ ME topic before posting:

 

Message added by Polanskiman

Recommended Posts

This is a critical update of DSM.

A change in the kernel config will breaks all non official PCIe devices drivers.

Read more here: https://xpenology.com/forum/topic/13074-dsm-621-23824-warning/

 

 

Screen Shot 2018-10-18 at 3.36.32 PM.jpg

 

https://www.synology.com/en-uk/releaseNote/DS3617xs#ver_23824-1

Spoiler

(2018-10-16)

Important Note

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

This update will restart your Synology NAS.

 

Fixed Issues

Improve Package Center system mechanisms to enhance user experience.

Enhanced the ext4 file system stability.

Fixed an issue where external hard drives of WD My Book might not be recognized if DSM is rebooted while the drives are in hibernation.

Fixed an issue where Microsoft Office files might not be renamed in Windows File Explorer through SMB protocol.

Fixed an issue where the HASP package might not be usable after upgrading to DSM 6.2-23739-2 and DSM 6.2.1-23824.

Fixed multiple security vulnerabilities regarding Linux kernel (Synology-SA-18:44).

Fixed a security vulnerability (Synology-SA-18:55).

Fixed a security vulnerability regarding wpa_supplicant (CVE-2018-14526).

Fixed a security vulnerability regarding OpenSSH (CVE-2018-15473).

Fixed multiple security vulnerabilities regarding Samba (CVE-2018-10858, CVE-2018-10919).

 

Edited by Polanskiman
Edited to conform to Guidelines + added link.

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

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

- Using custom extra.lzma: NO

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

- Additional comments: Works fine.. No problems upgrading from 6.2.1 on ESXi..

  • 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.1-23824

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

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - W-B250 from taobao (link: https://item.taobao.com/item.htm?spm=a1z09.2.0.0.37f02e8d1Ge3Zv&id=573141435687&_u=i2qem6r130df) - CPU: i7 7700T

  • 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.1-23824

- Loader version and model: JUN'S LOADER v1.04b - DS918

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - ASRock J5005-ITX

  • 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-23739U2

- Loader version and model: Jun v1.04b - DS918

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - J4105-ITX

- Additional comments:

  • tested on ESXi first, upgrading from 1.03a loader to 1.04b.
  • then upgraded DSM to 6.2.1 and validated both vmxnet3 and e1000 VLAN drivers
  • baremetal upgrade to 6.2.1 is working with Realtek NIC
  • also /dev/dri is active for the first time on baremetal J4105 (Gemini Lake)
  • Thanks 3

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: 6.2.1-23824

- Loader version and model: Jun v1.04b - DS918

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - To Be Filled By O.E.M./N3150DC-ITX, BIOS P1.90 04/13/2018

- Additional comments: baremetal Jun v1.04b 6.2.1 is working with Realtek NIC

r8168 Gigabit Ethernet driver 8.045.08-NAPI loaded

 

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: 6.2-23739 Update 2

- Loader version and model: Jun v1.04b - DS918+

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - H110M ITX, i5 7400, Intel I219V NIC

- Additional comments: Boot 6.2U2 with 1.04b, install 6.2.1, install 6.2.1u1.

 

 

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

- Loader version and model: Jun v1.04b - DS918+

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - Intel Core i3-8100t   GIGA-BYTE  H370 AORUS GAMING 3 WIFI

 

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

- Loader version and model: Jun v1.04b - DS918+

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - Asrock B250 Pro4 / NIC I219-V  / I7-6700K / 16Go

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

- Loader version and model: Jun v1.04b - DS918+

- Using custom extra.lzma: NO

- Installation type: BAREMETAL 

Share this post


Link to post
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update:  DSM 6.2.1-23824

- Loader version and model: Jun's Loader v1.04b - DS918+

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - on  DELL PowerEdge T30 (Intel Xeon)

- Additional comments: Reboot required

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.2 U1 (on DS3617)

- Loader version and model: JUN'S LOADER v1.04b - DS918+

- Using custom extra.lzma: NO

- Installation type: Upgrade from another DSM model, using a new loader - because I'm crazy...  J3455-ITX with 12GB RAM. 2x SSD and 1xHDD..

- Additional comments: Took a long time, compared to others and it was basically a fresh install (it didn't really work as an upgrade)..

I had my config backed up and Surveillance station camera config (and others) backed up, so it was relatively straight-forward to restore..

Data was never at risk (not that there was anything that was irreplacable)..

Top tip.. If you have LACP set up on a network BOND, plug the cables into a non-LACP enabled port until the 'upgrade' is finished (change them as needed) OR break the Bond and change your switch config before the upgrade..

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

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

- Using custom extra.lzma: NO

- Installation type: VM - ESXi 6.5 Virtual Machine on i3-4160/16GB Ram/Intel Dual port NIC/Various disks drives for testing

- Additional comments: Works fine..
                                           Fresh install using DSM 6.2-23739 Update 2

                                                           -> update DSM 6.2.1-23824

                                                           -> update DSM 6.2.1-23824 - Update 1

 

  • Thanks 1

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

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

- Using custom extra.lzma: NO

- Installation type: VM - ESXi 6.7 Update 1 - VM on HP DL360p Gen8

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

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

- Using custom extra.lzma: NO

- Installation type: VM - ESXi 6.7 Update 1 - VM on HP Microserver Gen8 (Xeon)

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

- Loader version and model: JUN'S LOADER v1.04b - DS918+

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - GA-N3150N-D3V

  • Thanks 1

Share this post


Link to post
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: 6.2.1-23824

- Loader version and model: Jun's loader v1.03b - DS3617xs

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - ASRock E3C236D2I

  • Thanks 1

Share this post


Link to post
Share on other sites

- Outcome of the update: SUCCESSFUL

- DSM version prior update: DSM 6.2.1-23824

- Loader version and model: Jun's loader v1.03b - DS3615xs

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - ASRock H110M-ITX/AC

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, Jun v1.03b - DS3617

- Loader version and model: Jun v1.04b - DS918+

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - ASRock E3C226D2I, Xeon E3-1285L v3

- Additional comments: Migration to 6.2.1 Ok, HW trancoding NOSW transcoding Ok, net transfer speed 100+ MB/s, webUI poweroff Ok.

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: UNSUCCESSFUL

- DSM version prior update: fresh installation

- Loader version and model: JUN'S LOADER v1.04b - DS918+

- Using custom extra.lzma: NO

- Installation type: BAREMETAL -  ASUS E35M1-I Deluxe (AMD APU platform, disabled CnQ, C6)

- Additional comments: Realtek 8111E - fault, cannot get IP from DHCP (not sure why, as I saw other using Realtek NIC works with v1.04b)

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 v1.04b (DS918+)

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - AMD X370

  • CPU: AMD Ryzen 7 1700X
  • Mobo: ASUS ROG Strix X370-F Gaming
  • LAN: Intel I350-T2
  • HBA: LSI 9300-8i (IT mode)

- Additional comments: Chipset SATA and LSI card both work fine.

Edited by ACiDxCHRiST

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.1.7

- Loader version and model: jun's v1.04b (DS918+)

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - Intel Q170  / CPU: Intel Pentium G4560 / Mobo: Gigabyte Q170M-MK bios F21 / LAN: Intel I219, I210

- Additional comments: Chipset SATA working. HW transcoding working, NO 4K though.

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 - Supermicro X8DTI-F / NIC: Intel 82576 Dual-Port Gigabit Ethernet, plus an Intel EXPI9301CTBLK PRO1000 Network Card CT PCIex / Chipset: Dual Intel E5620 Xeon / SATA Additional Controllers: Lindy 4 port SATA 3 PCIe /  Disks: 8 x 4TB WD Red, 2 x 256GB SSD

- Additional comments: Everything recognised and working

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

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

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

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - HP Microserver Gen 8 /  NIC: Intel I350-T2

- Additional comments: Internal NIC not recognized

 

Share this post


Link to post
Share on other sites

- Outcome of the installation/update: SUCCESSFUL

- DSM version prior update: DSM 6.1-7-15284

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

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - Supermicro X10SL7-F with Xeon E3-1241 V3 cpu and 16 GB (2 x 8 GB) ECC  / NIC: Onboard Dual Gigabit Ethernet LAN ports via Intel® i210AT

- Additional comments: Rebuilt RAID as part of the upgrade from: 10 x 8 TB WD Reds Volume 1 (RAID 6) (btrfs)

          to: 6(attached to SATA controller) x 8 TB WD Reds in Volume 1 (RAID 6) and

               4(attached to 4 of 8 x SAS2 (6Gbps) via Broadcom 2308) x 8 TB WD Reds in RAID 5 (Volume 2). Retained btrfs for both RAID volumes.

               Primary purpose was to create smaller arrays to minimise stress from rechecking/rebuilding after about 3 or 4 intermittent disk disconnections over the past 6~8 months. 

               Cause of this was never identified. All SATA cables were connected and no entries in logs indicating cause of these disconnections.  

It should also be noted that it was intended to do the upgrade using Jun's 1.03b and the 6.2.23739.pat.  The system refused the use of 6.2.23739 and demanded 6.2.23824.

Edited by Polanskiman
more info on system

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