IG-88 Posted October 24, 2017 Share #1 Posted October 24, 2017 (edited) hi, does anyone sucseeded in using 916+ in VitualBox? (test system is skylake, so it does boot/work on a processor/basic level) the vm configuration that works for 3615/3617 (IDE boot jun's loader and SCSI for DSM disks) does not work for 916+, it does not find disks, also buslogic or SAS do not work only SATA disk is found but after starting to copy DSM from the pat file it stops with error 21 (sysnology assistent) other funny fthing is if no disk is found then the nic gets a dhcp adress (can bee seen in serial console and log) but the systerm in synology assistent (and browser) is reachable under a APIPA address 169.254.x.y (x,y are the values from the dhcp address it used), if the webinterface ist opend it shows that no disk was found, but that just odd and of no real value as without disks found its no working configuration here is the log of sata disk with unsuccsessfull copy of dsm (md5 of dsm is ok, tryed 15047 and 15152, also tryed 1.02a2 and 1.02b) tryed migration of 3615 working vm/config and clean install with empty 100GB dynamic disk, same error (creation of partitions work, "using" them does not) log Jan 1 00:00:13 findhostd: ninstaller.c:1571(ErrFHOSTReceiveUpgradeFile) cRead=[4], ulFileSize=[218398720] Jan 1 00:00:14 findhostd: Estimated time =[1] Jan 1 00:00:14 findhostd: ErrFHOSTTcpResponseCmd: cmd=[5], ulErr=[0] Jan 1 00:00:14 findhostd: Starting ErrFHOSTDoUpgrade()... Jan 1 00:00:14 findhostd: ErrFHOSTTcpResponseCmd: cmd=[5], ulErr=[0] Jan 1 00:00:14 findhostd: ErrFHOSTTcpResponseCmd: cmd=[5], ulErr=[0] Jan 1 00:00:14 findhostd: Remove /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1] Jan 1 00:00:14 findhostd: ninstaller.c:2372(ErrFHOSTDoUpgrade) retv=[0] Jan 1 00:00:14 findhostd: ErrFHOSTDoUpgrade() Done Jan 1 00:00:14 findhostd: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:14 findhostd: alz=[0], prg=[0], cfg=[0], retv=[0] Jan 1 00:00:14 findhostd: Create /tmpData/upd@te...cmd=[/bin/mkdir -p /tmpData/upd@te > /dev/null 2>&1] Jan 1 00:00:14 findhostd: Untar /tmpData/upd@te.pat...cmd=[/bin/tar xpf "/tmpData/upd@te.pat" -C /tmpData/upd@te > /dev/null 2>&1] Jan 1 00:00:14 kernel: [ 68.824062] hrtimer: interrupt took 4916523 ns Jan 1 00:00:15 findhostd: ErrFHOSTCheckUpgradeFile: Remove /tmpData/upd@te.pat... Jan 1 00:00:15 findhostd: Verify codesign of [/tmpData/upd@te]... Jan 1 00:00:16 findhostd: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:16 findhostd: alz=[0], prg=[0], cfg=[0], retv=[0] Jan 1 00:00:16 findhostd: Verify checksum of [/tmpData/upd@te]... Jan 1 00:00:17 findhostd: Pass checksum of /tmpData/upd@te... Jan 1 00:00:17 findhostd: ErrFHOSTTcpResponseCmd: cmd=[5], ulErr=[0] Jan 1 00:00:17 updater: updater.c:5773 Start of the updater... Jan 1 00:00:17 updater: updater.c:2746 orgBuildNumber = 15047, newBuildNumber=15152 Jan 1 00:00:17 updater: updater_util.c:49 fail to read company in /tmpRoot//etc.defaults/synoinfo.conf Jan 1 00:00:17 updater: file_check_key_value.c:25 SLIBCFileGetKeyValue(runccc) failed [0x0900 file_get_key_value.c:29] Jan 1 00:00:17 updater: updater.c:6028 ==== Start flash update ==== Jan 1 00:00:17 updater: updater.c:6032 This is X86 platform Jan 1 00:00:17 updater: boot/boot_lock.c(227): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2) Jan 1 00:00:17 updater: updater.c:5583 Failed to mount boot partition Jan 1 00:00:17 updater: updater.c:2645 No need to reset reason for v.15047 Jan 1 00:00:17 updater: updater.c:6549 Failed to accomplish the update! (errno = 21) Jan 1 00:00:17 findhostd: ninstaller.c:1779 Executing [/tmpData/upd@te/updater -v /tmpData > /dev/null 2>&1] error[21] Jan 1 00:00:17 findhostd: ninstaller.c:196 Mount partion /dev/md0 /tmpRoot Jan 1 00:00:17 findhostd: ninstaller.c:1748 Moving updater for configuration upgrade...cmd=[/bin/mv -f /tmpData/upd@te/updater /tmpRoot/.updater > /dev/null 2>&1] Jan 1 00:00:17 findhostd: ninstaller.c:225 umount partition /tmpRoot Jan 1 00:00:17 findhostd: ErrFHOSTCleanPatchDirFile: After updating /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1] Jan 1 00:00:17 findhostd: ErrFHOSTCleanPatchDirFile: Remove /tmpData/upd@te.pat... Jan 1 00:00:17 findhostd: ErrFHOSTDoUpgrade(2355): child process failed, retv=-21 Jan 1 00:00:17 findhostd: ninstaller.c:2363(ErrFHOSTDoUpgrade) err=[-1] Jan 1 00:00:17 findhostd: ninstaller.c:225 umount partition /tmpData Jan 1 00:00:18 findhostd: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:18 findhostd: alz=[0], prg=[0], cfg=[0], retv=[-21] Jan 1 00:00:18 findhostd: ninstaller.c:1869(ErrFHOSTUpdaterProgress) retv=-21 Jan 1 00:00:19 getty[5504]: console: TCGETS: Input/output error^M Jan 1 00:00:20 findhostd: query prog, szBuf = ^R4VxSYNONI^A^D^A Jan 1 00:00:20 findhostd: alz=[0], prg=[0], cfg=[0], retv=[-21] Jan 1 00:00:20 findhostd: ninstaller.c:1869(ErrFHOSTUpdaterProgress) retv=-21 Jan 1 00:00:20 findhostd: ninstaller.c:1364(ErrFHOSTNetInstaller) read socket fail, ret=[0], errno=[10] Jan 1 00:00:20 findhostd: ninstaller.c:1455(ErrFHOSTNetInstaller) retSel=[1] err=(10)[No child processes] Jan 1 00:00:20 findhostd: ninstaller.c:721 Dev: sda, DiskPath: /dev/sda, Partition version: 8 Jan 1 00:00:20 findhostd: ninstaller.c:196 Mount partion /dev/md0 /tmpRoot Jan 1 00:00:20 kernel: [ 74.779589] EXT4-fs (md0): barriers disabled Jan 1 00:00:20 kernel: [ 74.787905] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: Jan 1 00:00:20 findhostd: ninstaller.c:225 umount partition /tmpRoot Jan 1 00:00:20 findhostd: ninstaller.c:196 Mount partion /dev/md0 /tmpRoot Jan 1 00:00:20 kernel: [ 74.832806] EXT4-fs (md0): barriers disabled Jan 1 00:00:20 findhostd: ninstaller.c:225 umount partition /tmpRoot Jan 1 00:00:20 kernel: [ 74.840000] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: Jan 1 00:00:20 findhostd: ninstaller.c:196 Mount partion /dev/md0 /tmpRoot Jan 1 00:00:20 kernel: [ 74.851958] EXT4-fs (md0): barriers disabled Jan 1 00:00:20 kernel: [ 74.860958] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: Jan 1 00:00:20 findhostd: ninstaller.c:538 failed to get upnpmodelname from [/tmpRoot/etc.defaults/synoinfo.conf]. Jan 1 00:00:20 findhostd: ninstaller.c:545 failed to get buildnumber from [/tmpRoot/etc.defaults/VERSION]. Jan 1 00:00:20 findhostd: ninstaller.c:552 failed to get productversion from [/tmpRoot/etc.defaults/VERSION]. Jan 1 00:00:20 findhostd: ninstaller.c:554 failed to get majorversion from [/tmpRoot/etc.defaults/VERSION]. Jan 1 00:00:20 findhostd: ninstaller.c:557 failed to get minorversion from [/tmpRoot/etc.defaults/VERSION]. Jan 1 00:00:20 findhostd: lib/system/system_platform_get.c:35 failed to get unique from /tmpRoot/etc.defaults/synoinfo.conf errno=[0x0900 file_get_key_value.c:29] Jan 1 00:00:20 findhostd: ninstaller.c:569 failed to get platform from [/tmpRoot/etc.defaults/synoinfo.conf]. Jan 1 00:00:20 findhostd: lib/system/system_max_align_get.c:86 [/tmpRoot/.system_info/pgsql_alignment] doesn't exist, check model name for alignment Jan 1 00:00:20 findhostd: lib/system/system_endian_get.c:61 [/tmpRoot/.system_info/endian] doesn't exist, check model name for endian Jan 1 00:00:20 findhostd: lib/system/system_bit_get.c:57 [/tmpRoot/.system_info/bits] doesn't exist, check model name for bits Jan 1 00:00:20 findhostd: ninstaller.c:602 fail to get admin port from /tmpRoot/etc/synoinfo.conf... try another way Jan 1 00:00:20 findhostd: ninstaller.c:482 /tmpRoot/usr/syno/etc/www/DSM.json not exist Jan 1 00:00:20 findhostd: ninstaller.c:605 fail to get admin port from /tmpRoot/usr/syno/etc/www/DSM.json Jan 1 00:00:20 findhostd: ninstaller.c:633 failed to get nvr key from [/tmpRoot/etc.defaults/synoinfo.conf]. Jan 1 00:00:20 findhostd: ninstaller.c:783 fail to read [unique] from [/tmpRoot//etc.defaults/synoinfo.conf] Jan 1 00:00:20 findhostd: ninstaller.c:851 unique not match Jan 1 00:00:20 findhostd: ninstaller.c:1311 SYSTEM_NORMAL, [Recoverable=0] Jan 1 00:00:20 findhostd: ninstaller.c:225 umount partition /tmpRoot Jan 1 00:00:20 findhostd: ninstaller.c:1244(FillUpgradeVolumeInfo): gszUpgradeVolDev = /dev/md0 Jan 1 00:00:20 findhostd: ninstaller.c:1245(FillUpgradeVolumeInfo): gszUpgradeVolMnt = /tmpData Jan 1 00:00:20 findhostd: ninstaller.c:1327 gblSupportRaid: 1, gSysStatus: 1, gblCreateDataVol: 0, gblSystemRecoverable: 0 Jan 1 00:00:20 findhostd: ninstaller.c:1473(ErrFHOSTNetInstaller) Jan 1 00:00:20 findhostd: Return from TcpServer() Jan 1 00:00:29 getty[5557]: console: TCGETS: Input/output error^M Hide Edited October 24, 2017 by IG-88 Quote Link to comment Share on other sites More sharing options...
Huberer Posted October 30, 2017 Share #2 Posted October 30, 2017 (edited) @IG-88 when I saw your post I didn't have time to write and than I've forgotten about it. Back home I have an OMV server (latest OMV v4) with Fujitsu-MoBo (intel nic) and haswell cpu (i5-4590S with 4 cores). Under OMV I've installed virtualbox from the official OMV repo and set it up according to this how-to here. I guess I didn't install the extensions pack and for the mac address I have one from an original DS916+ (as well the serial number). I hope that a link to an another forum is allowed. Also you can see me Virtualbox settings and how DSM looks like under Virtualbox. For me it was a long try and error to get the DS916 system definiton to work. So I don't know exactly anymore what I did and where I got the DS916 synoboot.vmdk. The second virtual HDD is the data drive "Syno-DS916plus2.vhd". Unfortunately under DSM the synoboot.vmdk shows up and I didn't have time to check how I can hide it. I hope I could help you further Edited October 30, 2017 by Huberer 1 Quote Link to comment Share on other sites More sharing options...
IG-88 Posted October 31, 2017 Author Share #3 Posted October 31, 2017 hi, thanks, that helped to find the problem i had a IDE controller with the bootimage (jun's loader), that works with 3615/3617 (and you don't see the disk after installation) but does'nt with 916+ with sata as boot controller and first disk the bootloader image and 2nd the data disk it does work now i can test new compiled 916+ drivers for a new extra.lzma Quote Link to comment Share on other sites More sharing options...
Huberer Posted October 31, 2017 Share #4 Posted October 31, 2017 Hello, good to hear that it works. And also good to hear that you test new compiled 916+ drivers. Maybe with that I can get my Intel Nur with DS916 bootloader to work. Looking forward to test it. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.