Erik Finskas

The issue seems to be this; ============bootup-smallupdate Failed to AssertFileKeyValueEqual value1: /etc.defaults/VERSION:smallfixnumber -> 0 value2: /tmpRoot/.syno/patch/VERSION:smallfixnumber => 1 Exit on error [7] root not matched with junior.. Which relates to the respective parameter in user_config.json I have changed that in the build phase but it seems to reset back to 0 What is the correct procedure to fix this? .. erik

I've been successfully running a previous version 7.0.1 of DSM in my ESXi server and decided boldly to upgrade it to 7.2.0 with the appropriate .pat file through DSM itself. That never worked, DSM did boot up to the recovery phase and stated I have moved the data disks and DSM wanted to initiate the recovery process, but would not finish it successfully. I decided to do a fresh installation of TCRP 0.9.4.9 and removed the RDM data disks from the VM and removed as well the DSM data disk and recreated the boot volume with the TCRP VMDK gzip file and ran the appropriate tasks with the image builder to get DS918+ DSM-7.2.0-64570. Installation was exactly by the guid I was once able to get the DSM up to the point of selecting how to install DSM, at which I selected to use the .pat file I had (DSM_DS918+_64570.pat). After installation I am back in the recovery stage even I don't have any of the RDM data disks attached to the VM Serial console works and through that I can access the logfiles. There is no /var/log/junior-mode file but a junior_reason which states something I don't understand why the system has dropped to junior mode. DiskStation> cat /var/log/junior_reason Exit on error [7] root not matched with junior... /var/log/messages throws all kind of errors which I'm not sure are they ignorable, here's few; Jul 23 00:55:17 kernel: [ 25.913996] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities Jul 23 00:55:17 root: Failed to curl [https://dataupdate7.synology.com/juniorexpansionpack/v1/getUpdate?platform=apollolake&buildnumber=64570][7] Jul 23 00:55:17 kernel: [ 26.033756] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities Jul 23 00:55:17 kernel: [ 26.043179] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null) Jul 23 00:55:17 findhostd: ninstaller.c:168 umount partition /tmpRoot insmod: can't insert '/lib/modules/syno_hddmon.ko': Operation not permitted /var/log/messages gets filled with this repeating error: Jul 23 01:16:26 getty[7810]: tcgetattr: Input/output error^M Here is the user_config.json file; Notable is that I had to manually correct the model and version information. Otherwise it always stayed as model DS3622xs and version 7.1.1-42962 { "general": { "model": "DS918+", "version": "7.2.0-64570", "smallfixnumber": "0", "zimghash": "00713e465ddf347e1683a41f7ffa75afd670945c568502d754d4a24c7cb9e4ab", "rdhash": "e6e1a1fd59ce864dd174b6fb733ceda511648a9e3727845b8c0c52995af91fa2", "usb_line": "withefi earlyprintk syno_hw_version=DS918+ console=ttyS0,115200n8 netif_num=1 pid=0xa4a5 earlycon=uart8250,io, 0x3f8,115200n8 syno_port_thaw=1 mac1=000C297BB4E3 sn=1860PDN019675 vid=0x0525 elevator=elevator loglevel=15 HddHotplug=0 DiskId xMap=1000 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=1 log_buf_len=32M root=/dev/md0 SataPortMap=18 ", "sata_line": "withefi earlyprintk syno_hw_version=DS918+ console=ttyS0,115200n8 netif_num=1 pid=0xa4a5 earlycon=uart8250,io ,0x3f8,115200n8 synoboot_satadom=2 syno_port_thaw=1 mac1=000C297BB4E3 sn=1860PDN019675 vid=0x0525 elevator=elevator loglevel=15 HddHotplug=0 DiskIdxMap=1000 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=1 log_buf_len=32M root=/dev/md0 Sa taPortMap=18 ", "redpillmake": "prod", "friendautoupd": "true", "staticboot": "false", "hidesensitive": "false" }, "ipsettings": { "ipset": "", "ipaddr": "", "ipgw": "", "ipdns": "", "ipproxy": "" }, "extra_cmdline": { "pid": "0xa4a5", "vid": "0x0525", "sn": "0000000000000", "mac1": "FFFFFFFFFFFF", "netif_num": "1", "SataPortMap": "18", "DiskIdxMap": "1000" }, "synoinfo": { "internalportcfg": "0xffff", "maxdisks": "16", "support_bde_internal_10g": "no", "support_disk_compatibility": "no", "support_memory_compatibility": "no", "maxlanport": "8", "netif_seq": "0 1 2 3 4 5 6 7" }, "ramdisk_copy": {} } I will try again with DSM 7.1.1 version to see is this something which fails specificly with 7.2.0 or is something else wrong. I appreciate all help and comments to get things back up .. Erik

Thanks! Updating worked out and now I got forward. Wasn't far, ESXi 7.03U3k .. Erik

Hi all, thanks for an excellent tutorial! I am having a strange issue though which I can't get past. For some reason my ESXi 7 does not like the TCRP vmdk file, and the new disk won't be imported to the system. Here's a screenshot of the VM edit view, for some reason all the fields of the new disk are blank, and it's size is not recognized correctly either. https://pasteboard.co/M60wEN0EDhk9.png All file sizes are correct though. The space in the file naming seem not to make any difference. Tried with and without. [root@Microserver-vmware-mgmt:/vmfs/volumes/6398a133-61e70cd4-de98-b47af133998a/Synology NAS] ls -lh total 34721856 -rw------- 1 root root 1.0G Apr 14 21:54 Synology NAS-TCRP-flat.vmdk -rw------- 1 root root 470 Apr 14 21:59 Synology NAS-TCRP.vmdk -rw------- 1 root root 32.0G Apr 14 21:15 Synology NAS-flat.vmdk -rw------- 1 root root 8.5K Apr 14 21:38 Synology NAS.nvram -rw------- 1 root root 452 Apr 14 21:15 Synology NAS.vmdk -rw-r--r-- 1 root root 0 Apr 14 21:15 Synology NAS.vmsd -rwxr-xr-x 1 root root 2.9K Apr 14 21:57 Synology NAS.vmx Best regards, Erik