knopserl

SOrry for bother you again: Just one question (I read the steps in the lik): Since you did not just upgrade from 5.1 to 6.2 you also did a platform migration (3615 to 918). That was no problem for the DSM to migrate also the HW platform and going from 32Bit (3615) to 64Bit (918)?. Just boot from the new 1.04b and the Synology wizzard was offering an upgradable system?

@Enzo-fr I'm on ds3617 and 1.03b (on a VMware machine) and also wanted tomigrate to ds918+ and 1.04b. I have two disks attached and a some SW installed like Video Surveillance and TVHeadend and don't want to loose SW, settings, data ... I'm also interested in the steps/order you did the migration. Thanks

- Outcome of a fresh install: SUCCESSFUL - DSM version DSM 6.2.1: Fresh install on a N4200 Apollo Lake using VMware Workstation 14 - Loader version and model: Jun's Loader v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: VM - Additional comments: Used standard VMware NIC, SATA for boot and SCSI for DSM installation (disk1)

I run my DSM with VMware and changed from DS3615 to DS3617 using DM 6.2 and Jun's BL 1.03b. I observe, that newest version are released first for the DSM918+. I have tested DSM918+ on VMware 14 with Jun's BL 1.04b and it works with DM 6.2.1, but for "productive" usage, I'm still on DS3617 with DS6.2 and BL 1.03b. No my question to the experts of this forum: Is it recommeneded to switch from DS3615/17 to DS918+ as it's based on newer HW (I use a N4200 Apollo lake CPU in my VMware machine)? Do you see June focus more on the DS918+ rather than the older DS3615/17?

@hoidoi Thanks for the hint. I run already legacy/BIOS boot and I hve no CSM boot option, only BIOS or UEFI and BIOS is selected. So it might be the NIC or ??? DS918 images boots but it's unstable and not usable.

I have the same problem and have described a few posts before yours: I have a N4200 board with a Realtec Gigabit PCIe Family NIC (RTL8168/8111 or RTL8169?). It boots but never apears in the network. When I use the 918+ V1.03a2 loader it boots and is visibly in the nextwork and I can install 6.2 but it's instable, need 10min to boot DSM, crashes and then you cant no longer reinstall. It would have been nice to have either an installable DS3617xs version for the very engergie efficient N4200 mini PC or a stable DS918+ version.

So now I have tested the V1.03a2 DS918+ bootloader and the host was found (N4200 Realtek PCIe Gigabit Family) as DS918+ and I was able to install it. But then it took too long to restart and the installer says timeout. Later it was found but starts very slow, after 6+minutes it stays service starting but the nit switches off and I was not able to reinstall it (I get at error 21). So I gave up the DS918+ However the DS3617 boots (VD/PID of course corected) and it never get visible in the network. So I guess it does not really boot properly after the last console mesage. So I'm stuck. I would use a working 918+ bootloader or a DS3617 is alo fine, but both dont work.

I have tried to install on a barbone/HW box with an Appolo Lake N4200 with a built in Realtek PCIe Gigabit Family NIC with the HW ID's (from Windows) PCI\VEN_10EC&DEV_8168&SUBSYS_012310EC&REV_07 which I guess its a Realtek RTL8168/8111 (or RTL8169?). Maybe the network adapter is not known/found? I used the V1.03b bootimage for DS3617xs and the devices is not found. I'll try to use the bootimage for the DS918+ with the only availble version 1.03a2 and hope it works with that model. Does anybody know if we'll also get an update/newer version for the DS918+ like 1.03b)? How can I debug output without a serial port at the install host and the remote host? Is there a USB to Serial to USB cable available (USB on both ends or two cables with USB to Serial and a adapter in between how are you doing it)

Hi sound like a similar problem I have. I used a N4200 CPU/box but with a VMware host and the v1.03b did not detect the SATA HDD's. I had to switch to SCSI disks and then it installed (see my communication above). Only the boot image disk can/has to be be SATA the installation disk(s) have to be SCSI otherwise no HDD is detected.

ok, this time it really worked with the SCSI LSIlogic disk and the corrected boot order! Thanks again for the hint! BTW: There is a menu item in VMware "Boot to Firmware" which boots directly into the BIOS. So I got the 3617 to work by a fresh install. I have checked the 918 with bootimage 1.03a2 and the older 1.02b, both work with all SATA disks, only the 1.03b requires SCSI disk. So there is something strange in the 1.03b with SATA (except the bootdisk which has to be SATA). So now the key question: I have a running productive VM 3615xs with DSM 6.1.x and bootloader 1.02b. Is there a chance to upgrade to 6.2.x and change the bootloader to 1.03b and modify the disk from SATA to SCSI? Because I did the procedure but ather the update to DSM 6.2 and exchanging the bootloader to 1.03b, it does no longer boot. I assume because of the same reason, 1.03b does no longer accept SATA disks but requires SCSI disks. What do you think?

I have also tried SCSI LSIlogic but then it does not boot at all and tries to do a network boot. I have tried all kind of combination what you can do in VMware Pro 14 (HW version 12, 14, SATA, SCSI, BIOS, UEFI does not boot). The v1.03a2 boots immediatly and it finds disks and installation works. So there must be something whoch does not work with VM's in 1.0.3b

Thanks for the hint. I have always been in BIOS and not UEFI mode. I still get the Server Error 38 (no disk found) although I have two SATA Disks defined.

Has anybody tried to setup a VMware host with 1.03b either 3615 or 3617? Seems that some physical host are able to update or do a fresh install but I did not manage to install it with any VMware configuration, it starts the installation but after network setting and starting to format the system partition, it always ends up with error code 38 or in the web install windows it says no disk found. I can select whatever disk mode is available (SATA, SCSI Buslogic, LSIlogic) it never found a disk. The same with the 1.03a2 boot image for 918+ works. Anybody has any ideas?

Since neither the 1.03b DS3615 nor the DS3617 finds disk for installation (SATA, SCSI, BusLogic, LSILogic ...) I have tried the 1.03a2 DS 918+ bootimage and this finds immediatly any disk and everything worked. Complete installation with 6.2 update 2 applied, installed packages etc. I was using VMware hosts with HW compatibility v12 and v14. I only got the v103a2 DS918+ to run. Could it be, that in the new 1.03b boot images there are some disk controller/driver missing which are available in the older boot images and in the 1.03a2? I got always the error 38 and in the web install UI is says that it does not find any disk, whatever I have tried the whole evening.

is it a better idea to use the ds918+ bootloader and will this be also futher maintained (the ds3615 / 17 has 1.03b and the 918 is still on 1.03a2). So what DS are you recommending to use in terms of support by June?