gadreel

@sbv3000 I am also trying through the command line with no success. ( I wish I was able to read and understand the code of the synoupgrade binary) I do not see anything on the logs. I have this synoupdate.log which does not say anything because the smallgixnumber: 5 I manually installed it. I am almost certain that the previous small updates back on September and November I received a notification. 2019/09/14 10:54:56 start critical update to buildnumber: 24922 original smallfixnumber: 0 new_smallfixnumber: 3 build date: 2019/08/19 2019/09/14 10:54:56 Start of the update... 2019/09/14 10:54:57 Congratulations!! The update has been completed!! Do configupdate when next bootup. 2019/09/14 10:55:33 Finished apply small update! 2019/09/14 10:55:33 Finished update before reboot! 2019/11/12 06:41:39 start critical update to buildnumber: 24922 original smallfixnumber: 3 new_smallfixnumber: 4 build date: 2019/10/30 2019/11/12 06:41:45 Finished apply small update! 2019/11/12 06:41:45 Finished update before reboot! 2020/03/26 07:04:40 start critical update to buildnumber: 24922 original smallfixnumber: 4 new_smallfixnumber: 5 build date: 2020/01/14 2020/03/26 07:04:41 Start of the update... 2020/03/26 07:04:43 Congratulations!! The update has been completed!! Do configupdate when next bootup. 2020/03/26 07:04:45 Finished apply small update! 2020/03/26 07:04:45 Finished update before reboot! The syslog.log has these latest entries... 2020-03-27T13:30:57+02:00 DS918Plus syslog-ng[7803]: syslog-ng starting up; version='3.7.3' 2020-03-27T22:48:02+02:00 DS918Plus syslog-ng[7803]: syslog-ng shutting down; version='3.7.3' 2020-03-27T22:48:02+02:00 DS918Plus syslog-ng[2788]: syslog-ng starting up; version='3.7.3' 2020-03-30T15:36:11+03:00 DS918Plus syslog-ng[2788]: syslog-ng shutting down; version='3.7.3' 2020-03-30T15:36:12+03:00 DS918Plus syslog-ng[818]: syslog-ng starting up; version='3.7.3' 2020-03-31T10:06:50+03:00 DS918Plus syslog-ng[818]: syslog-ng shutting down; version='3.7.3' 2020-03-31T10:06:51+03:00 DS918Plus syslog-ng[29460]: syslog-ng starting up; version='3.7.3' 2020-04-01T09:17:27+03:00 DS918Plus syslog-ng[29460]: syslog-ng shutting down; version='3.7.3' 2020-04-01T09:17:28+03:00 DS918Plus syslog-ng[23464]: syslog-ng starting up; version='3.7.3' 2020-04-02T10:40:04+03:00 DS918Plus syslog-ng[23464]: syslog-ng shutting down; version='3.7.3' 2020-04-02T10:40:05+03:00 DS918Plus syslog-ng[27979]: syslog-ng starting up; version='3.7.3' 2020-04-03T12:06:42+03:00 DS918Plus syslog-ng[27979]: syslog-ng shutting down; version='3.7.3' 2020-04-03T12:06:43+03:00 DS918Plus syslog-ng[24994]: syslog-ng starting up; version='3.7.3'

@Polanskiman As an Admin and more experienced than me do you think there is a chance that when the DSM sends the request to check for a DSM update is also sending my S/N and somehow Synology blacklisted that S/N or something? If I change the S/N on my boot ISO (to test this) will it cause the DSM to do a fresh install and lost my data?

Update: The package updates work fine...I do not know what happened with that specific package but the DSM still no update. Update 6 was recalled but if you visit Synology's website they removed that part now, therefore it should be available.

6.2.2-24922-6 was released yesterday. Let's see if I will get any notification this time.

Update: 18/02/2020 I just received a notification that HyperBackup has a newer version. Not the one I was missing "2.2.3-1117" but the newest version that was released today "2.2.4-1213". So package updates seems to work fine...I do not know what happened before... But still no notification for DSM update 6.2.2-24922-5...

Spoke with Synology's live chat and they sent me this: "try 1) While logged into DSM navigate to Main Menu->Control Panel>-Network and input 8.8.8.8 as your "Alternative DNS Address" and then apply the changed settings. If connected to a Active Directory Server please check your DNS settings on the ADS server.2) Go to Control Panel->Network and make sure the "Default gateway" is set to the router's IP address. If it is incorrect you will need to change it in the Control Panel->Network->Network Interface tab by editing the active connection.3) Go to Control Panel->Regional Options and choose "Synchronize with NTP server". If you are already using this option then please choose a different server address and hit apply."

When I find a few minutes I might send a support message to Synology for the DS213j. Hopefully they will answer with something helpful. Also DSM 6 it feels like is coming to an end and Synology does not release any more updates very often to check if something is wrong or not.

Hi. This is what I have in the update settings. I do not want to install the updates automatically in case something breaks. Even if the desktop notifications are off when I go to the control panel to check for any updates I get "Your DSM is up-to-date". The firewalls on the synology is disable. I have also an official DS213j and I have a similar issue with packages. Hyper Backup newest update is Version: 2.2.2-1113

I might be wrong but I remember that the first time I installed DSM it was notifying me about any DSM and package updates. DS918+ has 6.2.2-24922-5 since 15/01 and I do not get any notification. Every time I go to Control Panel I get "Your DSM Version is up to date". Same goes for packages. Hyper Backup package version 2.2.3-1117 was released 2 months ago and I still have 2.2.2-1113 even on the control panel it is set to automatically update the packages. Any idea what is going on?

Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 3 - Loader version and model: Jun's Loader v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: UNRAID - ASRock H370M itx/ac - RAM 32Gb DDR4 NON-ECC - Intel Core i5 9400F - Pass-through Integrated LAN Intel I211 - Additional comments: Reboot required by the update

@Olegin Hi. Thanks for replying. I am using the DSM with Unraid KVM. Can you explain me what I need to do? I mean explain me how that works with ESXI and I will check if I can follow a similar approach on Unraid's KVM.

I have an NVME Samsung 970 Evo plus 500GB. Reading the previous post there is no way for the synology DSM to recognize the NVME?

Here it is: root@DS3615xs:~# dmidecode -t processor # dmidecode 3.2 Scanning /dev/mem for entry point. SMBIOS 2.8 present. Handle 0x0400, DMI type 4, 42 bytes Processor Information Socket Designation: CPU 0 Type: Central Processor Family: Other Manufacturer: QEMU ID: EA 06 09 00 FF FB 8B 0F Version: pc-q35-3.1 Voltage: Unknown External Clock: Unknown Max Speed: 2000 MHz Current Speed: 2000 MHz Status: Populated, Enabled Upgrade: Other L1 Cache Handle: Not Provided L2 Cache Handle: Not Provided L3 Cache Handle: Not Provided Serial Number: Not Specified Asset Tag: Not Specified Part Number: Not Specified Core Count: 2 Core Enabled: 2 Thread Count: 1 Characteristics: None

Outcome of the installation/update: SUCCESSFUL - DSM version prior update: DSM 6.2.2-24922 Update 2 - Loader version and model: Jun v1.03b - DS3615xs - Using custom extra.lzma: NO - Installation type: UNRAID - ASRock H370M itx/ac - RAM 32Gb DDR4 NON-ECC - Intel Core i5 9400F - Passthrough Integrated LAN Intel I211

Does it work with VMs? I am using DS3615xs as a VM under Unraid and the CPU is "pc-q35-3.1" with cat /proc/cpuinfo I get model name : Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz