gadreel

I tried ESXI... but I found it complicate. Let me know if you succeed.

No problem at all. I wish I could assist more...

@mrme01 What kind of hardware do you have?

It's really weird, I am out of ideas. I mean Unraid and OpenSuse use the Qemu/KVM I do not see any reason for them to have any difference. I wish I had a spare PC to test it somehow...

So, seeing that image your are good. It means the loader is loading fine. I do not think you need to change anything there, no need to put it to USB I believe. As you said you need to find a way to make the network to work.

But if you see this screen it means that your Synology is booting successfully. Your issue is the network card most probably.

This is the GUI version of the unraid. The primary vdisk bus is set as USB and the USB Controller I put it as 3.0 (qemu XHCI). The other disks you must set them as SATA since again I think Synology cannot recognize them otherwise.

What model is the chip of your NIC? For example I have the ASRock H370M-ITX/ac which has 2 NICs. The first NIC has the Intel I219V chip which is not supported by the Synology and the other one is the I211AT chip which is supported. If I was gonna install the XPenology as baremetal it wont work on the I219V and the Synology Assistant wont work if my ethernet cable is connected to the NIC. Synology will only find and load the I211 NIC. You will read this in a lot of topics in the forum. Now, if you are installing XPEnology into a VM, you do not need to worry about this because the Network Card is virtual, and you can set the model to e1000, I do not get it why it does not work on you.

No no. You extract the img from the ZIP file. Then you can use these XPEnology tools. From these tools you open the OSFMOUNT and mount the IMG file. This IMG has 3 partitions. Select the 1st partition 15MB. Do not forget to uncick the "Read-only Drive". Then a new Drive will be loaded to your Windows Explorer. Go to the grup folder and edit the configuration as said on the first guide I posted. Save the changes and dismount it. Then on your KVM you setup a USB to load that IMG file. This is how I have it on my Unraid... <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/isos/synoboot-ds918.img' index='5'/> <backingStore/> <target dev='hdc' bus='usb'/> <boot order='1'/> <alias name='usb-disk2'/> <address type='usb' bus='0' port='2'/> </disk>

If you want I could post you my Unraid XML but I do not know if that will help because it might be hard to understand what each segment does. Yes give it a go again because from my experience is much easier to install XPEnology into a VM than Baremetal.

I am using Jun's loader 1.04 for DS918+. I did not do anything specific on the loader other than changing the Serial Number and the MAC address. Do you want to post photos of your VM settings?

Try as network device model "e1000e". Your problem should be the network configuration because if you see from the VNC that black screen with the message to use the synology assistant it means that the bootloader booted just fine.

No, the MAC address is auto generated by the KVM. Yes, if you look most of the guides like ESXi for Virtual Network they use that e1000 model because it will work 100% if that is your issue.

On my Unraid which is also using KVM the problem was the model of the network card. By default Unraid enters "Virtio" as the model type which Synology does not have drivers or does not understand it somehow. But if I manually change the model type to e1000 the network bridge works fine. Also, if you have 2 network cards you can pass through one but again as long the Synology bootloader has drivers for it. <interface type='bridge'> <mac address='52:54:00:4b:b9:9e'/> <source bridge='br0'/> <model type='e1000'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> I hope this helps you.

Are you using Unraid's KVM?

@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