TinyCore RedPill Loader (TCRP)

hendry · February 11, 2022

I tried to install DSM918+ pat file inside VM but always failed at around 55-56% as the screen below.

I follow step by step to create the loader.

How to fix it ?

I choose boot into sata on the loader.

I can telnet it using root without password to inspect the log when installing .pat file.

Here it is :

DiskStation> tail -f /var/log/messages
Jan 1 00:04:32 synoupgrade: autocleanup/mount.c:19 run '/usr/bin/mount /dev/md0 /_disk'
Jan 1 00:04:32 kernel: [ 2342.572463] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:04:33 synoupgrade: autocleanup/mount.c:27 mount's exit status is zero
Jan 1 00:04:33 synoupgrade: get_disk_dsm_version.c:99 try reading disk dsm's version at file '/_disk//etc.defaults/VERSION' of key 'buildnumber'
Jan 1 00:04:33 kernel: [ 2342.703594] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:04:33 synoupgrade: get_disk_dsm_version.c:76 failed to load key 'buildnumber' from /_disk/etc.defaults/VERSION
Jan 1 00:04:33 synoupgrade: get_disk_dsm_version.c:104 failed to read dsm version on '/_disk'
Jan 1 00:04:33 synoupgrade: autocleanup/mount.c:44 run '/usr/bin/umount -l /_disk'
Jan 1 00:04:33 synoupgrade: autocleanup/mount.c:54 umount's exit status is zero
Jan 1 00:04:33 synoupgrade: autocleanup/directory.c:38 remove directory /_disk, result is 0
Jan 1 00:04:33 synoupgrade: synoupgrade.c:245 unable to get dsm version from disk device
Jan 1 00:04:33 synoupgrade: synoupgrade.c:308 unable to append query string of disk dsm version
Jan 1 00:04:38 synoupgrade: autocleanup/mount.c:19 run '/usr/bin/mount /dev/md0 /_disk'
Jan 1 00:04:38 kernel: [ 2347.684385] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:04:38 kernel: [ 2347.801091] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:04:38 synoupgrade: autocleanup/mount.c:27 mount's exit status is zero
Jan 1 00:04:38 synoupgrade: get_disk_dsm_version.c:99 try reading disk dsm's version at file '/_disk//etc.defaults/VERSION' of key 'buildnumber'
Jan 1 00:04:38 synoupgrade: get_disk_dsm_version.c:76 failed to load key 'buildnumber' from /_disk/etc.defaults/VERSION
Jan 1 00:04:38 synoupgrade: get_disk_dsm_version.c:104 failed to read dsm version on '/_disk'
Jan 1 00:04:38 synoupgrade: autocleanup/mount.c:44 run '/usr/bin/umount -l /_disk'
Jan 1 00:04:38 synoupgrade: autocleanup/mount.c:54 umount's exit status is zero
Jan 1 00:04:38 synoupgrade: autocleanup/directory.c:38 remove directory /_disk, result is 0
Jan 1 00:04:38 synoupgrade: synoupgrade.c:245 unable to get dsm version from disk device
Jan 1 00:04:38 synoupgrade: synoupgrade.c:308 unable to append query string of disk dsm version
Jan 1 00:04:39 getty[19935]: tcgetattr: Input/output error^M
Jan 1 00:04:39 install.cgi: install.c:520 Unknown param localinstallreq=false
Jan 1 00:04:39 install.cgi: install.c:520 Unknown param _dc=1644550853826
Jan 1 00:04:39 install.cgi: ninstaller.c:683 Dev: sda, DiskPath: /dev/sda, Partition version: 8
Jan 1 00:04:39 install.cgi: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot
Jan 1 00:04:39 kernel: [ 2349.581812] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:04:40 kernel: [ 2349.657618] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:04:40 install.cgi: ninstaller.c:152 umount partition /tmpRoot
Jan 1 00:04:40 install.cgi: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot
Jan 1 00:04:40 kernel: [ 2349.855935] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:04:40 kernel: [ 2349.868193] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:04:40 install.cgi: ninstaller.c:152 umount partition /tmpRoot
Jan 1 00:04:40 install.cgi: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot
Jan 1 00:04:40 kernel: [ 2349.975150] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:04:40 kernel: [ 2349.988583] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:04:40 install.cgi: ninstaller.c:430 failed to get upnpmodelname from [/tmpRoot/etc.defaults/synoinfo.conf].
Jan 1 00:04:40 install.cgi: ninstaller.c:437 failed to get buildnumber from [/tmpRoot/etc.defaults/VERSION].
Jan 1 00:04:40 install.cgi: ninstaller.c:444 failed to get productversion from [/tmpRoot/etc.defaults/VERSION].
Jan 1 00:04:40 install.cgi: ninstaller.c:446 failed to get majorversion from [/tmpRoot/etc.defaults/VERSION].
Jan 1 00:04:40 install.cgi: ninstaller.c:449 failed to get minorversion from [/tmpRoot/etc.defaults/VERSION].
Jan 1 00:04:40 install.cgi: lib/system/system_platform_get.c:35 failed to get unique from /tmpRoot/etc.defaults/synoinfo.conf errno=[0x0900 file_get_key_value.c:28]
Jan 1 00:04:40 install.cgi: ninstaller.c:461 failed to get platform from [/tmpRoot/etc.defaults/synoinfo.conf].
Jan 1 00:04:40 install.cgi: lib/system/system_max_align_get.c:86 [/tmpRoot/.system_info/pgsql_alignment] doesn't exist, check model name for alignment
Jan 1 00:04:40 install.cgi: lib/system/system_endian_get.c:61 [/tmpRoot/.system_info/endian] doesn't exist, check model name for endian
Jan 1 00:04:40 install.cgi: lib/system/system_bit_get.c:57 [/tmpRoot/.system_info/bits] doesn't exist, check model name for bits
Jan 1 00:04:40 install.cgi: ninstaller.c:494 fail to get admin port from /tmpRoot/etc/synoinfo.conf... try another way
Jan 1 00:04:40 install.cgi: ninstaller.c:374 /tmpRoot/usr/syno/etc/www/DSM.json not exist
Jan 1 00:04:40 install.cgi: ninstaller.c:497 fail to get admin port from /tmpRoot/usr/syno/etc/www/DSM.json
Jan 1 00:04:40 install.cgi: ninstaller.c:525 failed to get nvr key from [/tmpRoot/etc.defaults/synoinfo.conf].
Jan 1 00:04:40 install.cgi: ninstaller.c:748 fail to read [unique] from [/tmpRoot//etc.defaults/synoinfo.conf]
Jan 1 00:04:40 install.cgi: ninstaller.c:847 unique not match
Jan 1 00:04:40 install.cgi: ninstaller.c:1207 SYSTEM_NORMAL, [Recoverable=0]
Jan 1 00:04:40 install.cgi: ninstaller.c:152 umount partition /tmpRoot
Jan 1 00:04:40 install.cgi: ninstaller.c:1114(FillUpgradeVolumeInfo): gszUpgradeVolDev = /dev/md0
Jan 1 00:04:40 install.cgi: ninstaller.c:1115(FillUpgradeVolumeInfo): gszUpgradeVolMnt = /tmpData
Jan 1 00:04:40 install.cgi: ninstaller.c:1223 gblSupportRaid: 1, gSysStatus: 1, gblCreateDataVol: 0, gblSystemRecoverable: 0
Jan 1 00:04:40 install.cgi: synoupgrade.c:762 system status = 2
Jan 1 00:04:40 install.cgi: ninstaller.c:1648 CreateDataVol=[0]
Jan 1 00:04:40 install.cgi: ninstaller.c:152 umount partition /tmpData
Jan 1 00:04:40 install.cgi: ninstaller.c:156 Fail to execute [/bin/umount -f /tmpData > /dev/null 2>&1]
Jan 1 00:04:40 install.cgi: ninstaller.c:1660 installer cmd=[/usr/syno/sbin/installer.sh -r >> /tmp/installer_sh.log 2>&1]
Jan 1 00:04:40 burnin: B1 not started
Jan 1 00:04:40 syno_swap_ctl: swap/swap_off.c:20 swap/swap_off.c(20): failed to swapoff /dev/md1, ret = -1
Jan 1 00:04:40 kernel: [ 2350.094663] md0: detected capacity change from 2549940224 to 0
Jan 1 00:04:40 kernel: [ 2350.095309] md: md0: set sda1 to auto_remap [0]
Jan 1 00:04:40 kernel: [ 2350.095792] md: md0 stopped.
Jan 1 00:04:40 kernel: [ 2350.096136] md: unbind<sda1>
Jan 1 00:04:40 kernel: [ 2350.096444] md: export_rdev(sda1)
Jan 1 00:04:40 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/mdadm -S /dev/md0" Error="mdadm: stopped /dev/md0 "
Jan 1 00:04:40 raidtool: raid_internal_lib.c:158 [Info] clean RAID superblock of /dev/md0
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not name, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: name
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram0
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram1
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram2
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram3
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram4
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram5
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram6
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram7
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram8
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram9
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram10
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram11
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram12
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram13
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram14
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram15
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not md, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: md1
Jan 1 00:04:40 synodiskport: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not md, not match any port type
Jan 1 00:04:40 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/mdadm --zero-superblock /dev/sda1" Error=""
Jan 1 00:04:40 raidtool: raid_internal_lib.c:90 [Info] Clean RAID superblock on '/dev/sda1'
Jan 1 00:04:40 kernel: [ 2350.268710] md1: detected capacity change from 2147418112 to 0
Jan 1 00:04:40 kernel: [ 2350.269349] md: md1: set sda2 to auto_remap [0]
Jan 1 00:04:40 kernel: [ 2350.269815] md: md1 stopped.
Jan 1 00:04:40 kernel: [ 2350.270146] md: unbind<sda2>
Jan 1 00:04:40 kernel: [ 2350.270446] md: export_rdev(sda2)
Jan 1 00:04:40 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/mdadm -S /dev/md1" Error="mdadm: stopped /dev/md1 "
Jan 1 00:04:40 raidtool: raid_internal_lib.c:158 [Info] clean RAID superblock of /dev/md1
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not name, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: name
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram0
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram1
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram2
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram3
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram4
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram5
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram6
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram7
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram8
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram9
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram10
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram11
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram12
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram13
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram14
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram15
Jan 1 00:04:40 synodiskport: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not md, not match any port type
Jan 1 00:04:40 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/sfdisk --fast-delete 1:2 /dev/sda" Error=""
Jan 1 00:04:40 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/sfdisk -M1 /dev/sda" Error=""
Jan 1 00:04:40 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/sfdisk -M1 /dev/sda" Error=""
Jan 1 00:04:40 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/sfdisk -N1 -uS -q -f -j2048 -z4980480 -tfd -F /dev/sda" Error=""
Jan 1 00:04:40 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/sfdisk -N2 -uS -q -f -j0 -z4194304 -tfd -F /dev/sda" Error=""
Jan 1 00:04:43 synodiskport: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not md, not match any port type
Jan 1 00:04:43 kernel: [ 2353.416963] md: bind<sda1>
Jan 1 00:04:43 kernel: [ 2353.419057] md/raid1:md0: active with 1 out of 16 mirrors
Jan 1 00:04:43 kernel: [ 2353.425898] md0: detected capacity change from 0 to 2549940224
Jan 1 00:04:43 synodiskport: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not md, not match any port type
Jan 1 00:04:46 synodiskport: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not md, not match any port type
Jan 1 00:04:46 kernel: [ 2356.520453] md: bind<sda2>
Jan 1 00:04:46 kernel: [ 2356.522805] md/raid1:md1: active with 1 out of 16 mirrors
Jan 1 00:04:46 raidtool: raidtool.c:716 system inited on [/dev/sda1 ], [/dev/sda2 ]
Jan 1 00:04:46 kernel: [ 2356.530151] md1: detected capacity change from 0 to 2147418112
Jan 1 00:04:46 synodiskport: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not md, not match any port type
Jan 1 00:04:47 kernel: [ 2357.172211] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:04:47 kernel: [ 2357.183006] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:04:48 install.cgi: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot
Jan 1 00:04:48 kernel: [ 2357.603994] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:04:48 install.cgi: ninstaller.c:152 umount partition /tmpRoot
Jan 1 00:04:48 kernel: [ 2357.687834] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:04:48 install.cgi: ninstaller.c:1688 retv=[0]
Jan 1 00:04:48 install.cgi: ninstaller.c:1689(ErrFHOSTDoFdiskFormat) retv=[0]
Jan 1 00:04:48 install.cgi: ninstaller.c:123 Mount partion /dev/md0 /tmpData
Jan 1 00:04:48 kernel: [ 2357.712928] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:04:48 kernel: [ 2357.724846] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:04:49 getty[20337]: tcgetattr: Input/output error^M
Jan 1 00:04:59 getty[20344]: tcgetattr: Input/output error^M
Jan 1 00:05:09 getty[20348]: tcgetattr: Input/output error^M
Jan 1 00:05:19 getty[20355]: tcgetattr: Input/output error^M
Jan 1 00:05:19 install.cgi: synoupgrade.c:1342 Extracting VERSION from Old Patch Format [/tmpData/@autoupdate/upload.pat][/tmpData/@autoupdate]
Jan 1 00:05:19 install.cgi: Remove /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1]
Jan 1 00:05:19 install.cgi: Create /tmpData/upd@te...cmd=[/bin/mkdir -p /tmpData/upd@te > /dev/null 2>&1]
Jan 1 00:05:19 install.cgi: ninstaller.c:1299 Extracting Old Patch Format [/tmpData/upd@te.pat][/tmpData/upd@te]
Jan 1 00:05:19 install.cgi: Untar /tmpData/upd@te.pat...cmd=[/bin/tar xpf "/tmpData/upd@te.pat" -C /tmpData/upd@te > /dev/null 2>&1]
Jan 1 00:05:19 install.cgi: Verify codesign of [/tmpData/upd@te]...
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (VERSION) = 0d669baefc39bc4de77fb8549501f3888d8c303d53170dc7c74c23e3912314e1
Jan 1 00:05:20 synocodesign: VERSION: OK
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (zImage) = 6a1b2c1ac669d8fede0401ce679bb9048078406a0376c91a6255d2d6d4e0472a
Jan 1 00:05:20 synocodesign: zImage: OK
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (updater) = 227500655d23fa5503ef338c443467d45f711bf740048e60fa461efe41cea522
Jan 1 00:05:20 synocodesign: updater: OK
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (GRUB_VER) = f04c3c49de90d20d820f6ec3039b7d1a77bab099c08a58726b9840252aa7ad62
Jan 1 00:05:20 synocodesign: GRUB_VER: OK
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (rd.gz) = da577203ce50532a60d8782a6089aefd5a9ad0f97aaf9631f1710a5a0a6e402b
Jan 1 00:05:20 synocodesign: rd.gz: OK
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (grub_cksum.syno) = 03bb57be2137cd1fbd174b43761790096cb7fbec1923b091f3db044fbcb29cfa
Jan 1 00:05:20 synocodesign: grub_cksum.syno: OK
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (H2OFFT-Lx64) = 5a289c5c00df6b52a5739165e82a4372379c6399a3ccd491413601d65c85e2ec
Jan 1 00:05:20 synocodesign: H2OFFT-Lx64: OK
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (bios.ROM) = f82f451861f674f2ef977227ee5d23b768fa677ee53404588ff1a9aff4ade768
Jan 1 00:05:20 synocodesign: bios.ROM: OK
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (platform.ini) = 0d8ad5777af60d054fb28cd454f5e9fb698e3e87c40c5431b10e81e302d173f8
Jan 1 00:05:20 synocodesign: platform.ini: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (hda1.tgz) = ff13a8732fed6259fae0ca7d06cf9f0aa7bc9bcc1bfa13b7242b13112dce7177
Jan 1 00:05:21 synocodesign: hda1.tgz: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (indexdb.txz) = c77e97e62418450adecba2a8eb2e69b3647c77a584819b5375a9a947f53b22ef
Jan 1 00:05:21 synocodesign: indexdb.txz: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (synohdpack_img.txz) = 8d03e5297bcb1587085e6a6bdf3e1508b990423ee77b9454a8806b68c05f4c58
Jan 1 00:05:21 synocodesign: synohdpack_img.txz: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/dsm6-ui-compatible-1.0.0-0090.spk) = 21f0ebcd955a0b7ddef976668c8bbcddc680e4cd0a08c051cc8eef81eb618520
Jan 1 00:05:21 synocodesign: packages/dsm6-ui-compatible-1.0.0-0090.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/USBCopy-x86_64-2.2.0-1076.spk) = 43d5accb1e160e73c261e2ee7e929816466141c00701c2217153c422194594d6
Jan 1 00:05:21 synocodesign: packages/USBCopy-x86_64-2.2.0-1076.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/SynologyUniversalSearch-x86_64-1.5.2-0516.spk) = d6a26cb39703f18248532a77598bfafa0c5c6a1af8f1bd21c3544a17bd65a366
Jan 1 00:05:21 synocodesign: packages/SynologyUniversalSearch-x86_64-1.5.2-0516.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/SecureSignIn-x86_64-1.0.3-0138.spk) = 1cbc1d2c29bd41c177462713beed98a194c903100c19acb611d34f26fdbb63e3
Jan 1 00:05:21 synocodesign: packages/SecureSignIn-x86_64-1.0.3-0138.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/ScsiTarget-x86_64-1.0.2-0207.spk) = cfcc18e7080d14ac49b0cc1d3b400765a3b52cdcb2852abb649b1cb25f10410d
Jan 1 00:05:21 synocodesign: packages/ScsiTarget-x86_64-1.0.2-0207.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/SMBService-x86_64-4.10.18-0316.spk) = 415d75a8b0317a6dee0142aaedc084efe4da80bd39f71520adf671972da1ea56
Jan 1 00:05:21 synocodesign: packages/SMBService-x86_64-4.10.18-0316.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/Python2-x86_64-2.7.18-1004.spk) = a081dba0d92d460b9828b50e3848bb09834d0cf46b6ece19721965c3b013b819
Jan 1 00:05:21 synocodesign: packages/Python2-x86_64-2.7.18-1004.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/OAuthService-x86_64-1.1.2-0071.spk) = d2c1a75b441827a159dd1662ef4deaf980f08850c16803bc2b0c997a3e82b167
Jan 1 00:05:21 synocodesign: packages/OAuthService-x86_64-1.1.2-0071.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/HybridShare-apollolake-1.2.0-0650.spk) = 1fd9e9c5ef0fd7e040dc08c6cf3e98bbbd244a99ef589f18ed46c7487f0599b9
Jan 1 00:05:21 synocodesign: packages/HybridShare-apollolake-1.2.0-0650.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/HighAvailability-x86_64-2.1.1-1279.spk) = 923bd2d1896fa6b5b0707a5363589c41c3f5574f83e1fb82aa5aae406030f2c7
Jan 1 00:05:21 synocodesign: packages/HighAvailability-x86_64-2.1.1-1279.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/FileStation-x86_64-1.3.1-1382.spk) = ae14221440cbbb1eccd348e7adf00c2daf85a18e5759390a32a634700fb1faf7
Jan 1 00:05:21 synocodesign: packages/FileStation-x86_64-1.3.1-1382.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/DhcpServer-x86_64-1.0.0-0034.spk) = 19369e16d3653d2adfd3054ecdf195e2f70a7081a7ae67469cb7e5f14e2e93f8
Jan 1 00:05:21 synocodesign: packages/DhcpServer-x86_64-1.0.0-0034.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/ActiveInsight-x86_64-1.1.0-1121.spk) = e3cd03d10840bec796f1d73757c68c81f09710ba94a7fd6745ed3132cb30a3b6
Jan 1 00:05:21 synocodesign: packages/ActiveInsight-x86_64-1.1.0-1121.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/chs/strings) = daaeffe8730f3b64dc5ff3012022d00ff9eccae6498fcc29b50b567db8214755
Jan 1 00:05:21 synocodesign: texts/chs/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/cht/strings) = 8bf545442dffdb3653fbbfc6c1a760cec6895e3c09ba1922c60d776de5f7f965
Jan 1 00:05:21 synocodesign: texts/cht/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/csy/strings) = 414b7446d4271621bb6a62ef756bc29be82881adc1bd8d3ba857e55271fc5d64
Jan 1 00:05:21 synocodesign: texts/csy/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/dan/strings) = 7875012a44709e6e96df56c634adce2b79fc399f655475f91acaeab00f03a39f
Jan 1 00:05:21 synocodesign: texts/dan/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/enu/strings) = 0bb2656537d29ca293dfb89a9b646802e4ab2df7897b7eac69984cf048b52e9c
Jan 1 00:05:21 synocodesign: texts/enu/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/fre/strings) = 4225e913f64e806446c4311ae204814bd381bdd743a95dd1619e8bf6705a6024
Jan 1 00:05:21 synocodesign: texts/fre/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/ger/strings) = 466d3092e6bca364bb9fb12c2b1f85e3c2fd66a9b5d2095ca21e247b97ea9388
Jan 1 00:05:21 synocodesign: texts/ger/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/hun/strings) = 49bdaf196a4a3ef23c6db88a7082770caa5be970c5f4f8b09a5f3f2facf41dbf
Jan 1 00:05:21 synocodesign: texts/hun/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/ita/strings) = 31260083120ac283cdffbcb5125276f986c653aedfb7b86ed695f0d805bfaf60
Jan 1 00:05:21 synocodesign: texts/ita/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/jpn/strings) = ed7e700421fbcbb235123cb9677878d1cf4e4a8aeb95d5c4672bd02a07f06050
Jan 1 00:05:21 synocodesign: texts/jpn/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/krn/strings) = 9fb3a65a09ba27ed467dc1f69c6018052b8cdb2a78f8777e5d78ea5520c512e2
Jan 1 00:05:21 synocodesign: texts/krn/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/nld/strings) = 0f85cdc97b7ceecee606e717c81e6aa8c95757390ba206c5f2016e448ecfcfb5
Jan 1 00:05:21 synocodesign: texts/nld/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/nor/strings) = 3bca34926da5beb7471c4eb7f0fa8548019f422e6d32bdf79586eae29cb8a9f3
Jan 1 00:05:21 synocodesign: texts/nor/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/plk/strings) = 16f1ad6aec35b00add15764bd61b89ce48385793361c967f1d61912b169b0e9d
Jan 1 00:05:21 synocodesign: texts/plk/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/ptb/strings) = 43d8df16073f55a31a35f48f0eb58bd0a1b5c933d3518404691769a430d3ef54
Jan 1 00:05:21 synocodesign: texts/ptb/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/ptg/strings) = 70959b1947a9084653b0f2c02a259ae384bed0f943f915fad36820e91b71a9f4
Jan 1 00:05:21 synocodesign: texts/ptg/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/rus/strings) = a7284a09f64c3b30e37b4277ed3f6ed353aa2f5b1b889ac35a26139a7e2b4696
Jan 1 00:05:21 synocodesign: texts/rus/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/spn/strings) = 4d23573dd30d3cd1237ebcbb5a245ec92fe64cd12df7e03ba7361acf9d70f687
Jan 1 00:05:21 synocodesign: texts/spn/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/sve/strings) = 962f68c534ccb1c2fb16203ead371c40086ed87d067266486b1397699d3f640f
Jan 1 00:05:21 synocodesign: texts/sve/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/tha/strings) = f6fe4677f6d67d40127a0f99984a040721ed0b6d5245e0426c809d3b78233c7d
Jan 1 00:05:21 synocodesign: texts/tha/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/trk/strings) = 1f45e3781d7357e229f76e8f6bb3a96b86c49bd6c3880c089bd74f4e6c9fe942
Jan 1 00:05:21 synocodesign: texts/trk/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (expired_models) = efbb8e376238e2ed1a5e064c89aae01f6eafcb75e9060a36d7a84b154da7fabd
Jan 1 00:05:21 synocodesign: expired_models: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (DiskCompatibilityDB.tar) = f6f3b3037c0daf35806555c453b6205b7ccef8c5cf69f4a3e8965bd9b6183228
Jan 1 00:05:21 synocodesign: DiskCompatibilityDB.tar: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (ha_dummy_ocf/infoset) = b1fc7004374f8532e0ee6b32e2ac17e53f64d45f09d9cccee2514c3440a44e9f
Jan 1 00:05:21 synocodesign: ha_dummy_ocf/infoset: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (ha_dummy_ocf/dsm_rear) = 5bfd7437657591952f30360fed3accc059187c322f50ec3f17dedf026b908796
Jan 1 00:05:21 synocodesign: ha_dummy_ocf/dsm_rear: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (ha_dummy_ocf/dsm_first) = 5bfd7437657591952f30360fed3accc059187c322f50ec3f17dedf026b908796
Jan 1 00:05:21 synocodesign: ha_dummy_ocf/dsm_first: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (ha_dummy_ocf/PromoteBegin) = 5bfd7437657591952f30360fed3accc059187c322f50ec3f17dedf026b908796
Jan 1 00:05:21 synocodesign: ha_dummy_ocf/PromoteBegin: OK
Jan 1 00:05:22 synocodesign: BLAKE2b-256 (synohamessaged-update) = b9b6ebc709777915453d9a402f9346190564cf8a899ad7c8112bed40d97c07da
Jan 1 00:05:22 synocodesign: synohamessaged-update: OK
Jan 1 00:05:22 install.cgi: RemoveUpgradeFile: Remove /tmpData/upd@te.pat...
Jan 1 00:05:22 install.cgi: Verify checksum of [/tmpData/upd@te]...
Jan 1 00:05:23 install.cgi: Pass checksum of /tmpData/upd@te...
Jan 1 00:05:23 updater: updater.c:6767 Start of the updater...
Jan 1 00:05:23 updater: updater.c:3227 orgBuildNumber = 42218, newBuildNumber=42218
Jan 1 00:05:23 updater: util/updater_util.cpp:86 fail to read company in /tmpRoot//etc.defaults/synoinfo.conf
Jan 1 00:05:23 updater: updater.c:7045 ==== Start flash update ====
Jan 1 00:05:23 updater: updater.c:7049 This is X86 platform
Jan 1 00:05:23 updater: boot/boot_lock.c(228): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2)
Jan 1 00:05:23 updater: updater.c:6510 Failed to mount boot partition
Jan 1 00:05:23 updater: updater.c:3134 No need to reset reason for v.42218
Jan 1 00:05:23 updater: updater.c:7652 Failed to accomplish the update! (errno = 21)
Jan 1 00:05:23 install.cgi: ninstaller.c:1546 Executing [/tmpData/upd@te/updater -v /tmpData > /dev/null 2>&1] error[21]
Jan 1 00:05:24 install.cgi: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot
Jan 1 00:05:24 install.cgi: ninstaller.c:1515 Moving updater for configuration upgrade...cmd=[/bin/mv -f /tmpData/upd@te/updater /tmpRoot/.updater > /dev/null 2>&1]
Jan 1 00:05:24 install.cgi: ninstaller.c:152 umount partition /tmpRoot
Jan 1 00:05:24 install.cgi: ErrFHOSTCleanPatchDirFile: After updating /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1]
Jan 1 00:05:24 install.cgi: ErrFHOSTCleanPatchDirFile: Remove /tmpData/upd@te.pat...
Jan 1 00:05:24 install.cgi: ErrFHOSTDoUpgrade(1794): child process failed, retv=-21
Jan 1 00:05:24 install.cgi: ninstaller.c:1811(ErrFHOSTDoUpgrade) err=[-1]
Jan 1 00:05:24 install.cgi: ninstaller.c:1815(ErrFHOSTDoUpgrade) retv=[-21]
Jan 1 00:05:24 install.cgi: install.c:409 Upgrade by the manual patch fail.
Jan 1 00:05:24 install.cgi: install.c:678 Upgrade by the uploaded patch /tmpData/@autoupdate/upload.pat fail.
Jan 1 00:00:00 install.cgi: ninstaller.c:152 umount partition /tmpData
Jan 1 00:00:04 getty[20497]: tcgetattr: Input/output error^M
Jan 1 00:00:14 getty[20498]: tcgetattr: Input/output error^M
Jan 1 00:00:24 synoupgrade: autocleanup/mount.c:19 run '/usr/bin/mount /dev/md0 /_disk'
Jan 1 00:00:24 kernel: [ 2418.608196] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:00:24 kernel: [ 2418.779108] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:00:24 synoupgrade: autocleanup/mount.c:27 mount's exit status is zero
Jan 1 00:00:24 synoupgrade: get_disk_dsm_version.c:99 try reading disk dsm's version at file '/_disk//etc.defaults/VERSION' of key 'buildnumber'
Jan 1 00:00:24 synoupgrade: get_disk_dsm_version.c:76 failed to load key 'buildnumber' from /_disk/etc.defaults/VERSION
Jan 1 00:00:24 synoupgrade: get_disk_dsm_version.c:104 failed to read dsm version on '/_disk'
Jan 1 00:00:24 synoupgrade: autocleanup/mount.c:44 run '/usr/bin/umount -l /_disk'
Jan 1 00:00:24 getty[20550]: tcgetattr: Input/output error^M
Jan 1 00:00:24 synoupgrade: autocleanup/mount.c:54 umount's exit status is zero
Jan 1 00:00:24 synoupgrade: autocleanup/directory.c:38 remove directory /_disk, result is 0
Jan 1 00:00:24 synoupgrade: synoupgrade.c:245 unable to get dsm version from disk device
Jan 1 00:00:24 synoupgrade: synoupgrade.c:308 unable to append query string of disk dsm version
Jan 1 00:00:34 getty[20641]: tcgetattr: Input/output error^M
Jan 1 00:00:35 synoupgrade: autocleanup/mount.c:19 run '/usr/bin/mount /dev/md0 /_disk'
Jan 1 00:00:35 kernel: [ 2429.381445] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:00:35 synoupgrade: autocleanup/mount.c:27 mount's exit status is zero
Jan 1 00:00:35 synoupgrade: get_disk_dsm_version.c:99 try reading disk dsm's version at file '/_disk//etc.defaults/VERSION' of key 'buildnumber'
Jan 1 00:00:35 synoupgrade: get_disk_dsm_version.c:76 failed to load key 'buildnumber' from /_disk/etc.defaults/VERSION
Jan 1 00:00:35 synoupgrade: get_disk_dsm_version.c:104 failed to read dsm version on '/_disk'
Jan 1 00:00:35 synoupgrade: autocleanup/mount.c:44 run '/usr/bin/umount -l /_disk'
Jan 1 00:00:35 kernel: [ 2429.468425] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:00:35 synoupgrade: autocleanup/mount.c:54 umount's exit status is zero
Jan 1 00:00:35 synoupgrade: autocleanup/directory.c:38 remove directory /_disk, result is 0
Jan 1 00:00:35 synoupgrade: synoupgrade.c:245 unable to get dsm version from disk device
Jan 1 00:00:35 synoupgrade: synoupgrade.c:308 unable to append query string of disk dsm version

DiskStation> fdisk -l
Disk /dev/sda: 20 GB, 21474836480 bytes, 41943040 sectors
2610 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/sda1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect
/dev/sda2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect
Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors
622544 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors
524272 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md1 doesn't contain a valid partition table

DiskStation> mount
rootfs on / type rootfs (rw)
/proc on /proc type proc (rw,relatime)
/tmp on /tmp type tmpfs (rw,relatime)
none on /dev type devtmpfs (rw,relatime,size=999916k,nr_inodes=249979,mode=755)
none on /dev/pts type devpts (rw,relatime,gid=4,mode=620,ptmxmode=000)
/sys on /sys type sysfs (rw,relatime)
none on /sys/kernel/debug type debugfs (rw,relatime)

Edited February 11, 2022 by hendry

Dvalin21 · February 11, 2022

How were you able to telnet in?

hendry · February 11, 2022

it seems it cannot found /dev/synoboot2 when start to update .pat file..

Jan 1 00:05:23 updater: updater.c:7045 ==== Start flash update ====
Jan 1 00:05:23 updater: updater.c:7049 This is X86 platform
Jan 1 00:05:23 updater: boot/boot_lock.c(228): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2)

then how ? why this loader cannot create /dev/synoboot2 ?

hendry · February 11, 2022

5 hours ago, jpbaril said:
Sorry to join the bandwagon of asking for help in a thread that should be development-focused.

Is anybody using RedPill TinyCore as a virtual machine through Virt-Manager/Libvirt ?

I can't succeed in installing the .pat file on first boot. Infamous error at 56 %.

I built TinyCore based on Apollolake 7.0.1-42218.

I updated user_config.json with the values from haydibe first page post and simply changed the serial number and mac address.

I added acpid extension then built.

No red errors.

tinycore-redpill.v0.4.4.img configured as a usb device.

When booting I both tried USB and SATA boot.

I tried creating the vm as uefi based then also as bios based vm, always as a q35 chipset machine. Same results.

(BTW: when first booting tinycore as uefi to create "image" it was not booting, I was brought to efi "console" and had to cd into dirs to finally boot core.efi)

I also added to the vm a virtual disk of 10 GB.

When faced with the error at 56%, I connected to the vm with telnet.

fsdisk results when booting as uefi based:
DiskStation> fdisk -l
Disk /dev/sdh: 10 GB, 10737418240 bytes, 20971520 sectors
1305 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device  Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdh1    0,32,33     310,37,47         2048    4982527    4980480 2431M fd Linux raid autodetect
/dev/sdh2    310,37,48   571,58,63      4982528    9176831    4194304 2048M fd Linux raid autodetect
Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors
622544 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors
524272 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md1 doesn't contain a valid partition table
Logs when booting as bios based:
DiskStation> [  125.397657] md1: detected capacity change from 2147418112 to 0
[  125.398386] md: md1: set sdh2 to auto_remap [0]
[  125.398928] md: md1 stopped.
[  125.399353] md: unbind<sdh2>
[  125.405037] md: export_rdev(sdh2)
[  128.443213] md: bind<sdh1>
[  128.444195] md/raid1:md0: active with 1 out of 16 mirrors
[  128.445431] md0: detected capacity change from 0 to 2549940224
[  131.458293] md: bind<sdh2>
[  131.459524] md/raid1:md1: active with 1 out of 16 mirrors
[  131.460842] md1: detected capacity change from 0 to 2147418112
[  131.749896] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
[  131.752160] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[  132.084506] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
(Yeah sorry I forgot to get both outputs for each booting)

Any idea of what's wrong?

Thank you!

same with me.. i also failed at around 55-56%.

pls check the log whether it cannot find /dev/synoboot2

i think it was the culprit why the installation process failed..

for now, i don't know how to fix it.. wait any others or the creator of this redpill loader reply this issue..

hendry · February 11, 2022

1 hour ago, Dvalin21 said:

How were you able to telnet in?

easy..

just using putty and telnet it using user=root without password. after u type root then enter, it will goes to linux prompt.

Dvalin21 · February 11, 2022

1 minute ago, hendry said:

same with me.. i also failed at around 55-56%.

pls check the log whether it cannot find /dev/synoboot2

i think it was the culprit why the installation process failed..

for now, i don't know how to fix it.. wait any others or the creator of this redpill loader reply this issue..

I get the same when doing baremetal.

Dvalin21 · February 11, 2022

49 minutes ago, hendry said:

it seems it cannot found /dev/synoboot2 when start to update .pat file..

Jan 1 00:05:23 updater: updater.c:7045 ==== Start flash update ====
Jan 1 00:05:23 updater: updater.c:7049 This is X86 platform
Jan 1 00:05:23 updater: boot/boot_lock.c(228): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2)

then how ? why this loader cannot create /dev/synoboot2 ?

The main person to show/share this with is @pocopico

I got the exact same error as you and @danellis12561

Feb 11 07:57:53 updater: updater.c:7045 ==== Start flash update ====
Feb 11 07:57:53 updater: updater.c:7049 This is X86 platform
Feb 11 07:57:53 updater: boot/boot_lock.c(228): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2)
Feb 11 07:57:53 updater: updater.c:6510 Failed to mount boot partition
Feb 11 07:57:53 updater: updater.c:3134 No need to reset reason for v.42218
Feb 11 07:57:53 updater: updater.c:7652 Failed to accomplish the update! (errno = 21)
Feb 11 07:57:53 install.cgi: ninstaller.c:1546 Executing [/tmpData/upd@te/updater -v /tmpData > /dev/null 2>&1] error[21]
Feb 11 07:58:00 install.cgi: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot
Feb 11 07:58:00 install.cgi: ninstaller.c:1515 Moving updater for configuration upgrade...cmd=[/bin/mv -f /tmpData/upd@te/updater /tmpRoot/.updater > /dev/null 2>&1]
Feb 11 07:58:01 install.cgi: ninstaller.c:152 umount partition /tmpRoot
Feb 11 07:58:01 install.cgi: ErrFHOSTCleanPatchDirFile: After updating /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1]
Feb 11 07:58:01 install.cgi: ErrFHOSTCleanPatchDirFile: Remove /tmpData/upd@te.pat...
Feb 11 07:58:01 install.cgi: ErrFHOSTDoUpgrade(1794): child process failed, retv=-21
Feb 11 07:58:01 install.cgi: ninstaller.c:1811(ErrFHOSTDoUpgrade) err=[-1]
Feb 11 07:58:01 install.cgi: ninstaller.c:1815(ErrFHOSTDoUpgrade) retv=[-21]
Feb 11 07:58:01 install.cgi: install.c:409 Upgrade by the manual patch fail.
Feb 11 07:58:01 install.cgi: install.c:678 Upgrade by the uploaded patch /tmpData/@autoupdate/upload.pat fail.
Jan 1 00:00:00 install.cgi: ninstaller.c:152 umount partition /tmpData
Feb 11 07:57:53 updater: boot/boot_lock.c(228): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2)
Feb 11 07:57:53 updater: updater.c:6510 Failed to mount boot partition

I also believe @painkiller895 had gotten this error as well but I cant remember.

Either way, like I said before im doing baremetal and not vm.

Edited February 11, 2022 by Dvalin21

Dvalin21 · February 11, 2022

@hendry Searching the error got me to this page synoboot2 error explained.

Written by https://community.synology.com/enu/user/jvelasquez*/profile

I've got a 12 drive DS2411+. It was put onto my desk after somebody gave up on it.
When using Synology Assistant to install DSM to it, we'd get an Error 15. Then after using a linux boot disk to investigate, and having setup DSM 1742, by manually installation, we could then never Update the DSM and we'd get an Error 15. Here's the /var/log/messages during an Attempt to do a Manual update using the DSM web interface. Note the line with "fail to backup images".

Sep 18 12:08:23 upgrade.cgi: UnpackFirmware: Clean //upd@te.pat...
Sep 18 12:08:23 upgrade.cgi: upgrade.cpp(1137): Remove //upd@te...cmd=[/bin/rm -rf //upd@te > /dev/null 2>&1]
Sep 18 12:08:23 upgrade.cgi: upgrade.cpp(1153): Create //upd@te...cmd=[/bin/mkdir -p //upd@te > /dev/null 2>&1]
Sep 18 12:08:23 upgrade.cgi: upgrade.cpp(1109): Untar //upd@te.pat...cmd=[/bin/tar xpf "//upd@te.pat" -C //upd@te > /dev/null 2>&1]
Sep 18 12:08:23 upgrade.cgi: upgrade.cpp(1055): Verify checksum of [//upd@te]...
Sep 18 12:08:29 upgrade.cgi: upgrade.cpp(1062): Pass checksum of //upd@te...
Sep 18 12:08:29 upgrade.cgi: LaunchUpdater: Executing //upd@te/updater -v /
Sep 18 12:08:29 updater: updater.c:6203 Start of the updater...
Sep 18 12:08:29 updater: updater.c:6256 This is X86 platform
Sep 18 12:08:31 updater: updater.c:1541 [CheckPackageSize] Find [1] internal volume, external volume count= [0]
Sep 18 12:08:31 updater: updater.c:1558 CheckPackageSize, err=0
Sep 18 12:08:31 updater: updater.c:285 fail to backup images. cp -f /tmp/bootmnt/rd.gz //synob@ckup
Sep 18 12:08:31 updater: updater.c:3574 failed to backup images
Sep 18 12:08:31 updater: updater.c:3780 Failed to accomplish the update! (errno = 15)
Sep 18 12:08:31 upgrade.cgi: upgrade.cpp:(1047) : failed to system cmd=[//upd@te/updater -v / > /dev/null 2>&1], r=3840
Sep 18 12:08:31 upgrade.cgi: upgrade.cpp(1137): Remove //upd@te...cmd=[/bin/rm -rf //upd@te > /dev/null 2>&1]
Sep 18 12:08:31 upgrade.cgi: upgrade.cpp:570 Failed to unpack firmware.
Sep 18 12:08:38 upgrade.cgi: upgrade.cpp:1014 Update Errno = 15[Error No:15]
Sep 18 12:09:10 afpd[12527]: [afp_config.c:349] DiskStation:AFPServer@* started on 65280.252:128 (2.0.1)

Ok. So here's my observations and how I fixed the issue for myself.
There is a USB storage device used for booting, see it here:

Model: Synology USBstation (scsi)
Disk /dev/synoboot: 128MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 32.3kB 16.5MB 16.4MB primary boot
2 16.5MB 115MB 98.7MB primary

Two partitions, /dev/synoboot1 and /dev/synoboot2. Now both are setup for booting using Grub.
However, /dev/synboot2 is actually the default, and synoboot1 operates as a fail-safe in the event that synoboot2 fails.
So our issue was that synboot2 is damaged, and so synboot1 was instead booting the system, except synboot1 doesn't have additional resources that DSM expects to be present on it's boot partition.
So my fix was simply to copy some things onto synoboot2, from DSM_DS2411+_1742.pat.

Here is the file listing from my working synboot1 and synoboot2.
drwxr-xr-x 3 root root 1024 Mar 16 2011 boot
drwx------ 2 root root 1024 Sep 13 21:43 lost+found
-rw-r--r-- 1 root root 2749350 Jun 10 2011 rd.gz
-rw-r--r-- 1 root root 2452528 Jun 10 2011 zImage
DiskStation> cd ../synoboot2
DiskStation> ls -l
-rwxr-xr-x 1 root root 209 Sep 19 07:37 VERSION
drwxr-xr-x 3 root root 1024 Mar 16 2011 boot
-rw-rw-rw- 1 root root 222 Sep 19 07:37 checksum.syno
-rw-r--r-- 1 root root 87 Sep 19 07:37 grub_cksum.syno
-rw-r--r-- 1 root root 74704896 Sep 19 07:37 hda1.tgz
drwx------ 2 root root 1024 Sep 13 21:43 lost+found
-rw-r--r-- 1 root root 5892792 Sep 19 07:37 rd.gz
-rwxr-xr-x 1 root root 3701176 Sep 19 07:37 updater
-rw-r--r-- 1 root root 65536 Dec 31 2003 vender
-rw-r--r-- 1 root root 2420832 Sep 19 07:37 zImage

Then after rebooting, we were able to install and update DSM freely and without further issues. Here's our /var/log/messages during a successful run:
Sep 18 18:11:16 upgrade.cgi: UnpackFirmware: Clean //upd@te.pat...
Sep 18 18:11:16 upgrade.cgi: upgrade.cpp(1137): Remove //upd@te...cmd=[/bin/rm -rf //upd@te > /dev/null 2>&1]
Sep 18 18:11:16 upgrade.cgi: upgrade.cpp(1153): Create //upd@te...cmd=[/bin/mkdir -p //upd@te > /dev/null 2>&1]
Sep 18 18:11:16 upgrade.cgi: upgrade.cpp(1109): Untar //upd@te.pat...cmd=[/bin/tar xpf "//upd@te.pat" -C //upd@te > /dev/null 2>&1]
Sep 18 18:11:16 upgrade.cgi: upgrade.cpp(1055): Verify checksum of [//upd@te]...
Sep 18 18:11:19 upgrade.cgi: upgrade.cpp(1062): Pass checksum of //upd@te...
Sep 18 18:11:19 upgrade.cgi: LaunchUpdater: Executing //upd@te/updater -v /
Sep 18 18:11:19 updater: updater.c:6203 Start of the updater...
Sep 18 18:11:19 updater: updater.c:6256 This is X86 platform
Sep 18 18:11:26 updater: updater.c:6171 successfully backup image for System Migration in path (/tmpRoot/.syno/patch).
Sep 18 18:11:26 updater: updater.c:6763 Congratulation!! The update has been completed!!
Sep 18 18:11:26 upgrade.cgi: upgrade.cpp(1137): Remove //upd@te...cmd=[/bin/rm -rf //upd@te > /dev/null 2>&1]
Sep 18 18:11:56 upgrade.cgi: upgrade.cpp(854): Reboot system
Sep 18 18:11:56 root: /usr/syno/etc/rc.d/S98findhostd.sh stop findhostd

I hope this will hope in some way. I wouldnt know where to begin with this.

hendry · February 11, 2022

19 minutes ago, Dvalin21 said:

@hendry Searching the error got me to this page synoboot2 error explained.

Written by https://community.synology.com/enu/user/jvelasquez*/profile

I've got a 12 drive DS2411+. It was put onto my desk after somebody gave up on it.
When using Synology Assistant to install DSM to it, we'd get an Error 15. Then after using a linux boot disk to investigate, and having setup DSM 1742, by manually installation, we could then never Update the DSM and we'd get an Error 15. Here's the /var/log/messages during an Attempt to do a Manual update using the DSM web interface. Note the line with "fail to backup images".

Sep 18 12:08:23 upgrade.cgi: UnpackFirmware: Clean //upd@te.pat...
Sep 18 12:08:23 upgrade.cgi: upgrade.cpp(1137): Remove //upd@te...cmd=[/bin/rm -rf //upd@te > /dev/null 2>&1]
Sep 18 12:08:23 upgrade.cgi: upgrade.cpp(1153): Create //upd@te...cmd=[/bin/mkdir -p //upd@te > /dev/null 2>&1]
Sep 18 12:08:23 upgrade.cgi: upgrade.cpp(1109): Untar //upd@te.pat...cmd=[/bin/tar xpf "//upd@te.pat" -C //upd@te > /dev/null 2>&1]
Sep 18 12:08:23 upgrade.cgi: upgrade.cpp(1055): Verify checksum of [//upd@te]...
Sep 18 12:08:29 upgrade.cgi: upgrade.cpp(1062): Pass checksum of //upd@te...
Sep 18 12:08:29 upgrade.cgi: LaunchUpdater: Executing //upd@te/updater -v /
Sep 18 12:08:29 updater: updater.c:6203 Start of the updater...
Sep 18 12:08:29 updater: updater.c:6256 This is X86 platform
Sep 18 12:08:31 updater: updater.c:1541 [CheckPackageSize] Find [1] internal volume, external volume count= [0]
Sep 18 12:08:31 updater: updater.c:1558 CheckPackageSize, err=0
Sep 18 12:08:31 updater: updater.c:285 fail to backup images. cp -f /tmp/bootmnt/rd.gz //synob@ckup
Sep 18 12:08:31 updater: updater.c:3574 failed to backup images
Sep 18 12:08:31 updater: updater.c:3780 Failed to accomplish the update! (errno = 15)
Sep 18 12:08:31 upgrade.cgi: upgrade.cpp:(1047) : failed to system cmd=[//upd@te/updater -v / > /dev/null 2>&1], r=3840
Sep 18 12:08:31 upgrade.cgi: upgrade.cpp(1137): Remove //upd@te...cmd=[/bin/rm -rf //upd@te > /dev/null 2>&1]
Sep 18 12:08:31 upgrade.cgi: upgrade.cpp:570 Failed to unpack firmware.
Sep 18 12:08:38 upgrade.cgi: upgrade.cpp:1014 Update Errno = 15[Error No:15]
Sep 18 12:09:10 afpd[12527]: [afp_config.c:349] DiskStation:AFPServer@* started on 65280.252:128 (2.0.1)

Ok. So here's my observations and how I fixed the issue for myself.
There is a USB storage device used for booting, see it here:

Model: Synology USBstation (scsi)
Disk /dev/synoboot: 128MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 32.3kB 16.5MB 16.4MB primary boot
2 16.5MB 115MB 98.7MB primary

Two partitions, /dev/synoboot1 and /dev/synoboot2. Now both are setup for booting using Grub.
However, /dev/synboot2 is actually the default, and synoboot1 operates as a fail-safe in the event that synoboot2 fails.
So our issue was that synboot2 is damaged, and so synboot1 was instead booting the system, except synboot1 doesn't have additional resources that DSM expects to be present on it's boot partition.
So my fix was simply to copy some things onto synoboot2, from DSM_DS2411+_1742.pat.

Here is the file listing from my working synboot1 and synoboot2.
drwxr-xr-x 3 root root 1024 Mar 16 2011 boot
drwx------ 2 root root 1024 Sep 13 21:43 lost+found
-rw-r--r-- 1 root root 2749350 Jun 10 2011 rd.gz
-rw-r--r-- 1 root root 2452528 Jun 10 2011 zImage
DiskStation> cd ../synoboot2
DiskStation> ls -l
-rwxr-xr-x 1 root root 209 Sep 19 07:37 VERSION
drwxr-xr-x 3 root root 1024 Mar 16 2011 boot
-rw-rw-rw- 1 root root 222 Sep 19 07:37 checksum.syno
-rw-r--r-- 1 root root 87 Sep 19 07:37 grub_cksum.syno
-rw-r--r-- 1 root root 74704896 Sep 19 07:37 hda1.tgz
drwx------ 2 root root 1024 Sep 13 21:43 lost+found
-rw-r--r-- 1 root root 5892792 Sep 19 07:37 rd.gz
-rwxr-xr-x 1 root root 3701176 Sep 19 07:37 updater
-rw-r--r-- 1 root root 65536 Dec 31 2003 vender
-rw-r--r-- 1 root root 2420832 Sep 19 07:37 zImage

Then after rebooting, we were able to install and update DSM freely and without further issues. Here's our /var/log/messages during a successful run:
Sep 18 18:11:16 upgrade.cgi: UnpackFirmware: Clean //upd@te.pat...
Sep 18 18:11:16 upgrade.cgi: upgrade.cpp(1137): Remove //upd@te...cmd=[/bin/rm -rf //upd@te > /dev/null 2>&1]
Sep 18 18:11:16 upgrade.cgi: upgrade.cpp(1153): Create //upd@te...cmd=[/bin/mkdir -p //upd@te > /dev/null 2>&1]
Sep 18 18:11:16 upgrade.cgi: upgrade.cpp(1109): Untar //upd@te.pat...cmd=[/bin/tar xpf "//upd@te.pat" -C //upd@te > /dev/null 2>&1]
Sep 18 18:11:16 upgrade.cgi: upgrade.cpp(1055): Verify checksum of [//upd@te]...
Sep 18 18:11:19 upgrade.cgi: upgrade.cpp(1062): Pass checksum of //upd@te...
Sep 18 18:11:19 upgrade.cgi: LaunchUpdater: Executing //upd@te/updater -v /
Sep 18 18:11:19 updater: updater.c:6203 Start of the updater...
Sep 18 18:11:19 updater: updater.c:6256 This is X86 platform
Sep 18 18:11:26 updater: updater.c:6171 successfully backup image for System Migration in path (/tmpRoot/.syno/patch).
Sep 18 18:11:26 updater: updater.c:6763 Congratulation!! The update has been completed!!
Sep 18 18:11:26 upgrade.cgi: upgrade.cpp(1137): Remove //upd@te...cmd=[/bin/rm -rf //upd@te > /dev/null 2>&1]
Sep 18 18:11:56 upgrade.cgi: upgrade.cpp(854): Reboot system
Sep 18 18:11:56 root: /usr/syno/etc/rc.d/S98findhostd.sh stop findhostd

I hope this will hope in some way. I wouldnt know where to begin with this.

how do i manage to fix it using this post ?

just thinking why /dev/synoboot2 missing and how to make it available..

hendry · February 11, 2022

50 minutes ago, Dvalin21 said:

The main person to show/share this with is @pocopico

I got the exact same error as @danellis12561

I also believe @painkiller895 had gotten this error as well but I cant remember.

Either way, like I said before im doing baremetal and not vm.

as long as it has been fixed, it will be valid if u're using proxmox, baremetal or vm.

Dvalin21 · February 11, 2022

Just now, hendry said:

as long as it has been fixed, it will be valid if u're using proxmox, baremetal or vm.

I was making sure there was much info as possible. Also, trying to mount the secondary boot myself brings up this error.

mount: can't find /dev/synoboot2 in /etc/fstab
Is it possible that the partition is missing from fstab? (fstab usually having list of partitions for the system)

hendry · February 11, 2022

5 minutes ago, Dvalin21 said:

I was making sure there was much info as possible. Also, trying to mount the secondary boot myself brings up this error.

mount: can't find /dev/synoboot2 in /etc/fstab
Is it possible that the partition is missing from fstab? (fstab usually having list of partitions for the system)

no,it's not fstab related.

the problem is the /dev itself didn't have synoboot.

only /dev/synobios.

there's no /dev/synoboot1, /dev/synoboot2, /dev/synoboot3

Dvalin21 · February 11, 2022

7 minutes ago, hendry said:

no,it's not fstab related.

the problem is the /dev itself didn't have synoboot.

only /dev/synobios.

there's no /dev/synoboot1, /dev/synoboot2, /dev/synoboot3

Then Im out of ideas. Like I said @pocopico will have to be the one to fix it.

pocopico · February 11, 2022

6 hours ago, hendry said:

I tried to install DSM918+ pat file inside VM but always failed at around 55-56% as the screen below.

I follow step by step to create the loader.

How to fix it ?

I choose boot into sata on the loader.

I can telnet it using root without password to inspect the log when installing .pat file.

Here it is :

DiskStation> tail -f /var/log/messages
Jan 1 00:04:32 synoupgrade: autocleanup/mount.c:19 run '/usr/bin/mount /dev/md0 /_disk'
Jan 1 00:04:32 kernel: [ 2342.572463] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:04:33 synoupgrade: autocleanup/mount.c:27 mount's exit status is zero
Jan 1 00:04:33 synoupgrade: get_disk_dsm_version.c:99 try reading disk dsm's version at file '/_disk//etc.defaults/VERSION' of key 'buildnumber'
Jan 1 00:04:33 kernel: [ 2342.703594] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:04:33 synoupgrade: get_disk_dsm_version.c:76 failed to load key 'buildnumber' from /_disk/etc.defaults/VERSION
Jan 1 00:04:33 synoupgrade: get_disk_dsm_version.c:104 failed to read dsm version on '/_disk'
Jan 1 00:04:33 synoupgrade: autocleanup/mount.c:44 run '/usr/bin/umount -l /_disk'
Jan 1 00:04:33 synoupgrade: autocleanup/mount.c:54 umount's exit status is zero
Jan 1 00:04:33 synoupgrade: autocleanup/directory.c:38 remove directory /_disk, result is 0
Jan 1 00:04:33 synoupgrade: synoupgrade.c:245 unable to get dsm version from disk device
Jan 1 00:04:33 synoupgrade: synoupgrade.c:308 unable to append query string of disk dsm version
Jan 1 00:04:38 synoupgrade: autocleanup/mount.c:19 run '/usr/bin/mount /dev/md0 /_disk'
Jan 1 00:04:38 kernel: [ 2347.684385] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:04:38 kernel: [ 2347.801091] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:04:38 synoupgrade: autocleanup/mount.c:27 mount's exit status is zero
Jan 1 00:04:38 synoupgrade: get_disk_dsm_version.c:99 try reading disk dsm's version at file '/_disk//etc.defaults/VERSION' of key 'buildnumber'
Jan 1 00:04:38 synoupgrade: get_disk_dsm_version.c:76 failed to load key 'buildnumber' from /_disk/etc.defaults/VERSION
Jan 1 00:04:38 synoupgrade: get_disk_dsm_version.c:104 failed to read dsm version on '/_disk'
Jan 1 00:04:38 synoupgrade: autocleanup/mount.c:44 run '/usr/bin/umount -l /_disk'
Jan 1 00:04:38 synoupgrade: autocleanup/mount.c:54 umount's exit status is zero
Jan 1 00:04:38 synoupgrade: autocleanup/directory.c:38 remove directory /_disk, result is 0
Jan 1 00:04:38 synoupgrade: synoupgrade.c:245 unable to get dsm version from disk device
Jan 1 00:04:38 synoupgrade: synoupgrade.c:308 unable to append query string of disk dsm version
Jan 1 00:04:39 getty[19935]: tcgetattr: Input/output error^M
Jan 1 00:04:39 install.cgi: install.c:520 Unknown param localinstallreq=false
Jan 1 00:04:39 install.cgi: install.c:520 Unknown param _dc=1644550853826
Jan 1 00:04:39 install.cgi: ninstaller.c:683 Dev: sda, DiskPath: /dev/sda, Partition version: 8
Jan 1 00:04:39 install.cgi: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot
Jan 1 00:04:39 kernel: [ 2349.581812] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:04:40 kernel: [ 2349.657618] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:04:40 install.cgi: ninstaller.c:152 umount partition /tmpRoot
Jan 1 00:04:40 install.cgi: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot
Jan 1 00:04:40 kernel: [ 2349.855935] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:04:40 kernel: [ 2349.868193] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:04:40 install.cgi: ninstaller.c:152 umount partition /tmpRoot
Jan 1 00:04:40 install.cgi: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot
Jan 1 00:04:40 kernel: [ 2349.975150] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:04:40 kernel: [ 2349.988583] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:04:40 install.cgi: ninstaller.c:430 failed to get upnpmodelname from [/tmpRoot/etc.defaults/synoinfo.conf].
Jan 1 00:04:40 install.cgi: ninstaller.c:437 failed to get buildnumber from [/tmpRoot/etc.defaults/VERSION].
Jan 1 00:04:40 install.cgi: ninstaller.c:444 failed to get productversion from [/tmpRoot/etc.defaults/VERSION].
Jan 1 00:04:40 install.cgi: ninstaller.c:446 failed to get majorversion from [/tmpRoot/etc.defaults/VERSION].
Jan 1 00:04:40 install.cgi: ninstaller.c:449 failed to get minorversion from [/tmpRoot/etc.defaults/VERSION].
Jan 1 00:04:40 install.cgi: lib/system/system_platform_get.c:35 failed to get unique from /tmpRoot/etc.defaults/synoinfo.conf errno=[0x0900 file_get_key_value.c:28]
Jan 1 00:04:40 install.cgi: ninstaller.c:461 failed to get platform from [/tmpRoot/etc.defaults/synoinfo.conf].
Jan 1 00:04:40 install.cgi: lib/system/system_max_align_get.c:86 [/tmpRoot/.system_info/pgsql_alignment] doesn't exist, check model name for alignment
Jan 1 00:04:40 install.cgi: lib/system/system_endian_get.c:61 [/tmpRoot/.system_info/endian] doesn't exist, check model name for endian
Jan 1 00:04:40 install.cgi: lib/system/system_bit_get.c:57 [/tmpRoot/.system_info/bits] doesn't exist, check model name for bits
Jan 1 00:04:40 install.cgi: ninstaller.c:494 fail to get admin port from /tmpRoot/etc/synoinfo.conf... try another way
Jan 1 00:04:40 install.cgi: ninstaller.c:374 /tmpRoot/usr/syno/etc/www/DSM.json not exist
Jan 1 00:04:40 install.cgi: ninstaller.c:497 fail to get admin port from /tmpRoot/usr/syno/etc/www/DSM.json
Jan 1 00:04:40 install.cgi: ninstaller.c:525 failed to get nvr key from [/tmpRoot/etc.defaults/synoinfo.conf].
Jan 1 00:04:40 install.cgi: ninstaller.c:748 fail to read [unique] from [/tmpRoot//etc.defaults/synoinfo.conf]
Jan 1 00:04:40 install.cgi: ninstaller.c:847 unique not match
Jan 1 00:04:40 install.cgi: ninstaller.c:1207 SYSTEM_NORMAL, [Recoverable=0]
Jan 1 00:04:40 install.cgi: ninstaller.c:152 umount partition /tmpRoot
Jan 1 00:04:40 install.cgi: ninstaller.c:1114(FillUpgradeVolumeInfo): gszUpgradeVolDev = /dev/md0
Jan 1 00:04:40 install.cgi: ninstaller.c:1115(FillUpgradeVolumeInfo): gszUpgradeVolMnt = /tmpData
Jan 1 00:04:40 install.cgi: ninstaller.c:1223 gblSupportRaid: 1, gSysStatus: 1, gblCreateDataVol: 0, gblSystemRecoverable: 0
Jan 1 00:04:40 install.cgi: synoupgrade.c:762 system status = 2
Jan 1 00:04:40 install.cgi: ninstaller.c:1648 CreateDataVol=[0]
Jan 1 00:04:40 install.cgi: ninstaller.c:152 umount partition /tmpData
Jan 1 00:04:40 install.cgi: ninstaller.c:156 Fail to execute [/bin/umount -f /tmpData > /dev/null 2>&1]
Jan 1 00:04:40 install.cgi: ninstaller.c:1660 installer cmd=[/usr/syno/sbin/installer.sh -r >> /tmp/installer_sh.log 2>&1]
Jan 1 00:04:40 burnin: B1 not started
Jan 1 00:04:40 syno_swap_ctl: swap/swap_off.c:20 swap/swap_off.c(20): failed to swapoff /dev/md1, ret = -1
Jan 1 00:04:40 kernel: [ 2350.094663] md0: detected capacity change from 2549940224 to 0
Jan 1 00:04:40 kernel: [ 2350.095309] md: md0: set sda1 to auto_remap [0]
Jan 1 00:04:40 kernel: [ 2350.095792] md: md0 stopped.
Jan 1 00:04:40 kernel: [ 2350.096136] md: unbind<sda1>
Jan 1 00:04:40 kernel: [ 2350.096444] md: export_rdev(sda1)
Jan 1 00:04:40 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/mdadm -S /dev/md0" Error="mdadm: stopped /dev/md0 "
Jan 1 00:04:40 raidtool: raid_internal_lib.c:158 [Info] clean RAID superblock of /dev/md0
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not name, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: name
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram0
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram1
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram2
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram3
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram4
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram5
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram6
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram7
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram8
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram9
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram10
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram11
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram12
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram13
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram14
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram15
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not md, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: md1
Jan 1 00:04:40 synodiskport: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not md, not match any port type
Jan 1 00:04:40 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/mdadm --zero-superblock /dev/sda1" Error=""
Jan 1 00:04:40 raidtool: raid_internal_lib.c:90 [Info] Clean RAID superblock on '/dev/sda1'
Jan 1 00:04:40 kernel: [ 2350.268710] md1: detected capacity change from 2147418112 to 0
Jan 1 00:04:40 kernel: [ 2350.269349] md: md1: set sda2 to auto_remap [0]
Jan 1 00:04:40 kernel: [ 2350.269815] md: md1 stopped.
Jan 1 00:04:40 kernel: [ 2350.270146] md: unbind<sda2>
Jan 1 00:04:40 kernel: [ 2350.270446] md: export_rdev(sda2)
Jan 1 00:04:40 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/mdadm -S /dev/md1" Error="mdadm: stopped /dev/md1 "
Jan 1 00:04:40 raidtool: raid_internal_lib.c:158 [Info] clean RAID superblock of /dev/md1
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not name, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: name
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram0
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram1
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram2
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram3
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram4
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram5
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram6
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram7
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram8
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram9
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram10
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram11
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram12
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram13
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram14
Jan 1 00:04:40 raidtool: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not ram, not match any port type
Jan 1 00:04:40 raidtool: disk/disk_port_to_container.c:38 Unknown diskType
Jan 1 00:04:40 raidtool: partition_path_enum.c:29 Failed to parsing device: ram15
Jan 1 00:04:40 synodiskport: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not md, not match any port type
Jan 1 00:04:40 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/sfdisk --fast-delete 1:2 /dev/sda" Error=""
Jan 1 00:04:40 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/sfdisk -M1 /dev/sda" Error=""
Jan 1 00:04:40 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/sfdisk -M1 /dev/sda" Error=""
Jan 1 00:04:40 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/sfdisk -N1 -uS -q -f -j2048 -z4980480 -tfd -F /dev/sda" Error=""
Jan 1 00:04:40 raidtool: space_error_log.c:47 SpaceCommand:command="/sbin/sfdisk -N2 -uS -q -f -j0 -z4194304 -tfd -F /dev/sda" Error=""
Jan 1 00:04:43 synodiskport: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not md, not match any port type
Jan 1 00:04:43 kernel: [ 2353.416963] md: bind<sda1>
Jan 1 00:04:43 kernel: [ 2353.419057] md/raid1:md0: active with 1 out of 16 mirrors
Jan 1 00:04:43 kernel: [ 2353.425898] md0: detected capacity change from 0 to 2549940224
Jan 1 00:04:43 synodiskport: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not md, not match any port type
Jan 1 00:04:46 synodiskport: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not md, not match any port type
Jan 1 00:04:46 kernel: [ 2356.520453] md: bind<sda2>
Jan 1 00:04:46 kernel: [ 2356.522805] md/raid1:md1: active with 1 out of 16 mirrors
Jan 1 00:04:46 raidtool: raidtool.c:716 system inited on [/dev/sda1 ], [/dev/sda2 ]
Jan 1 00:04:46 kernel: [ 2356.530151] md1: detected capacity change from 0 to 2147418112
Jan 1 00:04:46 synodiskport: external/external_disk_port_check.c:158 expected sdx or /dev/sdx, not md, not match any port type
Jan 1 00:04:47 kernel: [ 2357.172211] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:04:47 kernel: [ 2357.183006] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:04:48 install.cgi: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot
Jan 1 00:04:48 kernel: [ 2357.603994] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:04:48 install.cgi: ninstaller.c:152 umount partition /tmpRoot
Jan 1 00:04:48 kernel: [ 2357.687834] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:04:48 install.cgi: ninstaller.c:1688 retv=[0]
Jan 1 00:04:48 install.cgi: ninstaller.c:1689(ErrFHOSTDoFdiskFormat) retv=[0]
Jan 1 00:04:48 install.cgi: ninstaller.c:123 Mount partion /dev/md0 /tmpData
Jan 1 00:04:48 kernel: [ 2357.712928] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:04:48 kernel: [ 2357.724846] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:04:49 getty[20337]: tcgetattr: Input/output error^M
Jan 1 00:04:59 getty[20344]: tcgetattr: Input/output error^M
Jan 1 00:05:09 getty[20348]: tcgetattr: Input/output error^M
Jan 1 00:05:19 getty[20355]: tcgetattr: Input/output error^M
Jan 1 00:05:19 install.cgi: synoupgrade.c:1342 Extracting VERSION from Old Patch Format [/tmpData/@autoupdate/upload.pat][/tmpData/@autoupdate]
Jan 1 00:05:19 install.cgi: Remove /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1]
Jan 1 00:05:19 install.cgi: Create /tmpData/upd@te...cmd=[/bin/mkdir -p /tmpData/upd@te > /dev/null 2>&1]
Jan 1 00:05:19 install.cgi: ninstaller.c:1299 Extracting Old Patch Format [/tmpData/upd@te.pat][/tmpData/upd@te]
Jan 1 00:05:19 install.cgi: Untar /tmpData/upd@te.pat...cmd=[/bin/tar xpf "/tmpData/upd@te.pat" -C /tmpData/upd@te > /dev/null 2>&1]
Jan 1 00:05:19 install.cgi: Verify codesign of [/tmpData/upd@te]...
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (VERSION) = 0d669baefc39bc4de77fb8549501f3888d8c303d53170dc7c74c23e3912314e1
Jan 1 00:05:20 synocodesign: VERSION: OK
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (zImage) = 6a1b2c1ac669d8fede0401ce679bb9048078406a0376c91a6255d2d6d4e0472a
Jan 1 00:05:20 synocodesign: zImage: OK
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (updater) = 227500655d23fa5503ef338c443467d45f711bf740048e60fa461efe41cea522
Jan 1 00:05:20 synocodesign: updater: OK
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (GRUB_VER) = f04c3c49de90d20d820f6ec3039b7d1a77bab099c08a58726b9840252aa7ad62
Jan 1 00:05:20 synocodesign: GRUB_VER: OK
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (rd.gz) = da577203ce50532a60d8782a6089aefd5a9ad0f97aaf9631f1710a5a0a6e402b
Jan 1 00:05:20 synocodesign: rd.gz: OK
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (grub_cksum.syno) = 03bb57be2137cd1fbd174b43761790096cb7fbec1923b091f3db044fbcb29cfa
Jan 1 00:05:20 synocodesign: grub_cksum.syno: OK
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (H2OFFT-Lx64) = 5a289c5c00df6b52a5739165e82a4372379c6399a3ccd491413601d65c85e2ec
Jan 1 00:05:20 synocodesign: H2OFFT-Lx64: OK
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (bios.ROM) = f82f451861f674f2ef977227ee5d23b768fa677ee53404588ff1a9aff4ade768
Jan 1 00:05:20 synocodesign: bios.ROM: OK
Jan 1 00:05:20 synocodesign: BLAKE2b-256 (platform.ini) = 0d8ad5777af60d054fb28cd454f5e9fb698e3e87c40c5431b10e81e302d173f8
Jan 1 00:05:20 synocodesign: platform.ini: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (hda1.tgz) = ff13a8732fed6259fae0ca7d06cf9f0aa7bc9bcc1bfa13b7242b13112dce7177
Jan 1 00:05:21 synocodesign: hda1.tgz: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (indexdb.txz) = c77e97e62418450adecba2a8eb2e69b3647c77a584819b5375a9a947f53b22ef
Jan 1 00:05:21 synocodesign: indexdb.txz: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (synohdpack_img.txz) = 8d03e5297bcb1587085e6a6bdf3e1508b990423ee77b9454a8806b68c05f4c58
Jan 1 00:05:21 synocodesign: synohdpack_img.txz: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/dsm6-ui-compatible-1.0.0-0090.spk) = 21f0ebcd955a0b7ddef976668c8bbcddc680e4cd0a08c051cc8eef81eb618520
Jan 1 00:05:21 synocodesign: packages/dsm6-ui-compatible-1.0.0-0090.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/USBCopy-x86_64-2.2.0-1076.spk) = 43d5accb1e160e73c261e2ee7e929816466141c00701c2217153c422194594d6
Jan 1 00:05:21 synocodesign: packages/USBCopy-x86_64-2.2.0-1076.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/SynologyUniversalSearch-x86_64-1.5.2-0516.spk) = d6a26cb39703f18248532a77598bfafa0c5c6a1af8f1bd21c3544a17bd65a366
Jan 1 00:05:21 synocodesign: packages/SynologyUniversalSearch-x86_64-1.5.2-0516.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/SecureSignIn-x86_64-1.0.3-0138.spk) = 1cbc1d2c29bd41c177462713beed98a194c903100c19acb611d34f26fdbb63e3
Jan 1 00:05:21 synocodesign: packages/SecureSignIn-x86_64-1.0.3-0138.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/ScsiTarget-x86_64-1.0.2-0207.spk) = cfcc18e7080d14ac49b0cc1d3b400765a3b52cdcb2852abb649b1cb25f10410d
Jan 1 00:05:21 synocodesign: packages/ScsiTarget-x86_64-1.0.2-0207.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/SMBService-x86_64-4.10.18-0316.spk) = 415d75a8b0317a6dee0142aaedc084efe4da80bd39f71520adf671972da1ea56
Jan 1 00:05:21 synocodesign: packages/SMBService-x86_64-4.10.18-0316.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/Python2-x86_64-2.7.18-1004.spk) = a081dba0d92d460b9828b50e3848bb09834d0cf46b6ece19721965c3b013b819
Jan 1 00:05:21 synocodesign: packages/Python2-x86_64-2.7.18-1004.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/OAuthService-x86_64-1.1.2-0071.spk) = d2c1a75b441827a159dd1662ef4deaf980f08850c16803bc2b0c997a3e82b167
Jan 1 00:05:21 synocodesign: packages/OAuthService-x86_64-1.1.2-0071.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/HybridShare-apollolake-1.2.0-0650.spk) = 1fd9e9c5ef0fd7e040dc08c6cf3e98bbbd244a99ef589f18ed46c7487f0599b9
Jan 1 00:05:21 synocodesign: packages/HybridShare-apollolake-1.2.0-0650.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/HighAvailability-x86_64-2.1.1-1279.spk) = 923bd2d1896fa6b5b0707a5363589c41c3f5574f83e1fb82aa5aae406030f2c7
Jan 1 00:05:21 synocodesign: packages/HighAvailability-x86_64-2.1.1-1279.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/FileStation-x86_64-1.3.1-1382.spk) = ae14221440cbbb1eccd348e7adf00c2daf85a18e5759390a32a634700fb1faf7
Jan 1 00:05:21 synocodesign: packages/FileStation-x86_64-1.3.1-1382.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/DhcpServer-x86_64-1.0.0-0034.spk) = 19369e16d3653d2adfd3054ecdf195e2f70a7081a7ae67469cb7e5f14e2e93f8
Jan 1 00:05:21 synocodesign: packages/DhcpServer-x86_64-1.0.0-0034.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (packages/ActiveInsight-x86_64-1.1.0-1121.spk) = e3cd03d10840bec796f1d73757c68c81f09710ba94a7fd6745ed3132cb30a3b6
Jan 1 00:05:21 synocodesign: packages/ActiveInsight-x86_64-1.1.0-1121.spk: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/chs/strings) = daaeffe8730f3b64dc5ff3012022d00ff9eccae6498fcc29b50b567db8214755
Jan 1 00:05:21 synocodesign: texts/chs/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/cht/strings) = 8bf545442dffdb3653fbbfc6c1a760cec6895e3c09ba1922c60d776de5f7f965
Jan 1 00:05:21 synocodesign: texts/cht/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/csy/strings) = 414b7446d4271621bb6a62ef756bc29be82881adc1bd8d3ba857e55271fc5d64
Jan 1 00:05:21 synocodesign: texts/csy/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/dan/strings) = 7875012a44709e6e96df56c634adce2b79fc399f655475f91acaeab00f03a39f
Jan 1 00:05:21 synocodesign: texts/dan/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/enu/strings) = 0bb2656537d29ca293dfb89a9b646802e4ab2df7897b7eac69984cf048b52e9c
Jan 1 00:05:21 synocodesign: texts/enu/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/fre/strings) = 4225e913f64e806446c4311ae204814bd381bdd743a95dd1619e8bf6705a6024
Jan 1 00:05:21 synocodesign: texts/fre/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/ger/strings) = 466d3092e6bca364bb9fb12c2b1f85e3c2fd66a9b5d2095ca21e247b97ea9388
Jan 1 00:05:21 synocodesign: texts/ger/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/hun/strings) = 49bdaf196a4a3ef23c6db88a7082770caa5be970c5f4f8b09a5f3f2facf41dbf
Jan 1 00:05:21 synocodesign: texts/hun/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/ita/strings) = 31260083120ac283cdffbcb5125276f986c653aedfb7b86ed695f0d805bfaf60
Jan 1 00:05:21 synocodesign: texts/ita/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/jpn/strings) = ed7e700421fbcbb235123cb9677878d1cf4e4a8aeb95d5c4672bd02a07f06050
Jan 1 00:05:21 synocodesign: texts/jpn/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/krn/strings) = 9fb3a65a09ba27ed467dc1f69c6018052b8cdb2a78f8777e5d78ea5520c512e2
Jan 1 00:05:21 synocodesign: texts/krn/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/nld/strings) = 0f85cdc97b7ceecee606e717c81e6aa8c95757390ba206c5f2016e448ecfcfb5
Jan 1 00:05:21 synocodesign: texts/nld/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/nor/strings) = 3bca34926da5beb7471c4eb7f0fa8548019f422e6d32bdf79586eae29cb8a9f3
Jan 1 00:05:21 synocodesign: texts/nor/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/plk/strings) = 16f1ad6aec35b00add15764bd61b89ce48385793361c967f1d61912b169b0e9d
Jan 1 00:05:21 synocodesign: texts/plk/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/ptb/strings) = 43d8df16073f55a31a35f48f0eb58bd0a1b5c933d3518404691769a430d3ef54
Jan 1 00:05:21 synocodesign: texts/ptb/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/ptg/strings) = 70959b1947a9084653b0f2c02a259ae384bed0f943f915fad36820e91b71a9f4
Jan 1 00:05:21 synocodesign: texts/ptg/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/rus/strings) = a7284a09f64c3b30e37b4277ed3f6ed353aa2f5b1b889ac35a26139a7e2b4696
Jan 1 00:05:21 synocodesign: texts/rus/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/spn/strings) = 4d23573dd30d3cd1237ebcbb5a245ec92fe64cd12df7e03ba7361acf9d70f687
Jan 1 00:05:21 synocodesign: texts/spn/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/sve/strings) = 962f68c534ccb1c2fb16203ead371c40086ed87d067266486b1397699d3f640f
Jan 1 00:05:21 synocodesign: texts/sve/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/tha/strings) = f6fe4677f6d67d40127a0f99984a040721ed0b6d5245e0426c809d3b78233c7d
Jan 1 00:05:21 synocodesign: texts/tha/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (texts/trk/strings) = 1f45e3781d7357e229f76e8f6bb3a96b86c49bd6c3880c089bd74f4e6c9fe942
Jan 1 00:05:21 synocodesign: texts/trk/strings: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (expired_models) = efbb8e376238e2ed1a5e064c89aae01f6eafcb75e9060a36d7a84b154da7fabd
Jan 1 00:05:21 synocodesign: expired_models: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (DiskCompatibilityDB.tar) = f6f3b3037c0daf35806555c453b6205b7ccef8c5cf69f4a3e8965bd9b6183228
Jan 1 00:05:21 synocodesign: DiskCompatibilityDB.tar: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (ha_dummy_ocf/infoset) = b1fc7004374f8532e0ee6b32e2ac17e53f64d45f09d9cccee2514c3440a44e9f
Jan 1 00:05:21 synocodesign: ha_dummy_ocf/infoset: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (ha_dummy_ocf/dsm_rear) = 5bfd7437657591952f30360fed3accc059187c322f50ec3f17dedf026b908796
Jan 1 00:05:21 synocodesign: ha_dummy_ocf/dsm_rear: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (ha_dummy_ocf/dsm_first) = 5bfd7437657591952f30360fed3accc059187c322f50ec3f17dedf026b908796
Jan 1 00:05:21 synocodesign: ha_dummy_ocf/dsm_first: OK
Jan 1 00:05:21 synocodesign: BLAKE2b-256 (ha_dummy_ocf/PromoteBegin) = 5bfd7437657591952f30360fed3accc059187c322f50ec3f17dedf026b908796
Jan 1 00:05:21 synocodesign: ha_dummy_ocf/PromoteBegin: OK
Jan 1 00:05:22 synocodesign: BLAKE2b-256 (synohamessaged-update) = b9b6ebc709777915453d9a402f9346190564cf8a899ad7c8112bed40d97c07da
Jan 1 00:05:22 synocodesign: synohamessaged-update: OK
Jan 1 00:05:22 install.cgi: RemoveUpgradeFile: Remove /tmpData/upd@te.pat...
Jan 1 00:05:22 install.cgi: Verify checksum of [/tmpData/upd@te]...
Jan 1 00:05:23 install.cgi: Pass checksum of /tmpData/upd@te...
Jan 1 00:05:23 updater: updater.c:6767 Start of the updater...
Jan 1 00:05:23 updater: updater.c:3227 orgBuildNumber = 42218, newBuildNumber=42218
Jan 1 00:05:23 updater: util/updater_util.cpp:86 fail to read company in /tmpRoot//etc.defaults/synoinfo.conf
Jan 1 00:05:23 updater: updater.c:7045 ==== Start flash update ====
Jan 1 00:05:23 updater: updater.c:7049 This is X86 platform
Jan 1 00:05:23 updater: boot/boot_lock.c(228): failed to mount boot device /dev/synoboot2 /tmp/bootmnt (errno:2)
Jan 1 00:05:23 updater: updater.c:6510 Failed to mount boot partition
Jan 1 00:05:23 updater: updater.c:3134 No need to reset reason for v.42218
Jan 1 00:05:23 updater: updater.c:7652 Failed to accomplish the update! (errno = 21)
Jan 1 00:05:23 install.cgi: ninstaller.c:1546 Executing [/tmpData/upd@te/updater -v /tmpData > /dev/null 2>&1] error[21]
Jan 1 00:05:24 install.cgi: ninstaller.c:123 Mount partion /dev/md0 /tmpRoot
Jan 1 00:05:24 install.cgi: ninstaller.c:1515 Moving updater for configuration upgrade...cmd=[/bin/mv -f /tmpData/upd@te/updater /tmpRoot/.updater > /dev/null 2>&1]
Jan 1 00:05:24 install.cgi: ninstaller.c:152 umount partition /tmpRoot
Jan 1 00:05:24 install.cgi: ErrFHOSTCleanPatchDirFile: After updating /tmpData/upd@te...cmd=[/bin/rm -rf /tmpData/upd@te > /dev/null 2>&1]
Jan 1 00:05:24 install.cgi: ErrFHOSTCleanPatchDirFile: Remove /tmpData/upd@te.pat...
Jan 1 00:05:24 install.cgi: ErrFHOSTDoUpgrade(1794): child process failed, retv=-21
Jan 1 00:05:24 install.cgi: ninstaller.c:1811(ErrFHOSTDoUpgrade) err=[-1]
Jan 1 00:05:24 install.cgi: ninstaller.c:1815(ErrFHOSTDoUpgrade) retv=[-21]
Jan 1 00:05:24 install.cgi: install.c:409 Upgrade by the manual patch fail.
Jan 1 00:05:24 install.cgi: install.c:678 Upgrade by the uploaded patch /tmpData/@autoupdate/upload.pat fail.
Jan 1 00:00:00 install.cgi: ninstaller.c:152 umount partition /tmpData
Jan 1 00:00:04 getty[20497]: tcgetattr: Input/output error^M
Jan 1 00:00:14 getty[20498]: tcgetattr: Input/output error^M
Jan 1 00:00:24 synoupgrade: autocleanup/mount.c:19 run '/usr/bin/mount /dev/md0 /_disk'
Jan 1 00:00:24 kernel: [ 2418.608196] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:00:24 kernel: [ 2418.779108] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:00:24 synoupgrade: autocleanup/mount.c:27 mount's exit status is zero
Jan 1 00:00:24 synoupgrade: get_disk_dsm_version.c:99 try reading disk dsm's version at file '/_disk//etc.defaults/VERSION' of key 'buildnumber'
Jan 1 00:00:24 synoupgrade: get_disk_dsm_version.c:76 failed to load key 'buildnumber' from /_disk/etc.defaults/VERSION
Jan 1 00:00:24 synoupgrade: get_disk_dsm_version.c:104 failed to read dsm version on '/_disk'
Jan 1 00:00:24 synoupgrade: autocleanup/mount.c:44 run '/usr/bin/umount -l /_disk'
Jan 1 00:00:24 getty[20550]: tcgetattr: Input/output error^M
Jan 1 00:00:24 synoupgrade: autocleanup/mount.c:54 umount's exit status is zero
Jan 1 00:00:24 synoupgrade: autocleanup/directory.c:38 remove directory /_disk, result is 0
Jan 1 00:00:24 synoupgrade: synoupgrade.c:245 unable to get dsm version from disk device
Jan 1 00:00:24 synoupgrade: synoupgrade.c:308 unable to append query string of disk dsm version
Jan 1 00:00:34 getty[20641]: tcgetattr: Input/output error^M
Jan 1 00:00:35 synoupgrade: autocleanup/mount.c:19 run '/usr/bin/mount /dev/md0 /_disk'
Jan 1 00:00:35 kernel: [ 2429.381445] EXT4-fs (md0): couldn't mount as ext3 due to feature incompatibilities
Jan 1 00:00:35 synoupgrade: autocleanup/mount.c:27 mount's exit status is zero
Jan 1 00:00:35 synoupgrade: get_disk_dsm_version.c:99 try reading disk dsm's version at file '/_disk//etc.defaults/VERSION' of key 'buildnumber'
Jan 1 00:00:35 synoupgrade: get_disk_dsm_version.c:76 failed to load key 'buildnumber' from /_disk/etc.defaults/VERSION
Jan 1 00:00:35 synoupgrade: get_disk_dsm_version.c:104 failed to read dsm version on '/_disk'
Jan 1 00:00:35 synoupgrade: autocleanup/mount.c:44 run '/usr/bin/umount -l /_disk'
Jan 1 00:00:35 kernel: [ 2429.468425] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
Jan 1 00:00:35 synoupgrade: autocleanup/mount.c:54 umount's exit status is zero
Jan 1 00:00:35 synoupgrade: autocleanup/directory.c:38 remove directory /_disk, result is 0
Jan 1 00:00:35 synoupgrade: synoupgrade.c:245 unable to get dsm version from disk device
Jan 1 00:00:35 synoupgrade: synoupgrade.c:308 unable to append query string of disk dsm version

DiskStation> fdisk -l
Disk /dev/sda: 20 GB, 21474836480 bytes, 41943040 sectors
2610 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device Boot StartCHS EndCHS StartLBA EndLBA Sectors Size Id Type
/dev/sda1 0,32,33 310,37,47 2048 4982527 4980480 2431M fd Linux raid autodetect
/dev/sda2 310,37,48 571,58,63 4982528 9176831 4194304 2048M fd Linux raid autodetect
Disk /dev/md0: 2431 MB, 2549940224 bytes, 4980352 sectors
622544 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 2047 MB, 2147418112 bytes, 4194176 sectors
524272 cylinders, 2 heads, 4 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Disk /dev/md1 doesn't contain a valid partition table

DiskStation> mount
rootfs on / type rootfs (rw)
/proc on /proc type proc (rw,relatime)
/tmp on /tmp type tmpfs (rw,relatime)
none on /dev type devtmpfs (rw,relatime,size=999916k,nr_inodes=249979,mode=755)
none on /dev/pts type devpts (rw,relatime,gid=4,mode=620,ptmxmode=000)
/sys on /sys type sysfs (rw,relatime)
none on /sys/kernel/debug type debugfs (rw,relatime)

Yeah,

this almost always means two things,

For physical , you have either set the wrong USB VID:PID or you have selected SATA boot on GRUB menu -> Select USB

For VMware virtual, you have not selected SATA boot on GRUB menu. -> Select SATA

For proxmox/qemu virtual, you have not followed @haydibe instructions.

When you are not findind /dev/synoboot on your system it simply means that redpill was not able to properly shim a device as synoboot.

Edited February 11, 2022 by pocopico

pocopico · February 11, 2022

32 minutes ago, Dvalin21 said:

Then Im out of ideas. Like I said @pocopico will have to be the one to fix it.

I sure have to perform some enhancements and fixes, but i see nothing to be fixed for that issue.

Dvalin21 · February 11, 2022

1 minute ago, pocopico said:

Yeah,

this almost always means two things,

For physical , you have either set the wrong USB VID:PID of you have selected SATA boot on GRUB menu.

For VMware virtual, you have not selected SATA boot on GRUB menu.

For proxmox/qemu virtual, you have not followed @haydibe instructions.

When you are not findind /dev/synoboot on your system it simply means that redpill was not able to properly shim a device as synoboot.

Ive verified and checked multiple times to make sure that the USB VID:PID is correct. Also I use the identifyusb command in tinycore

pocopico · February 11, 2022

3 minutes ago, Dvalin21 said:

Ive verified and checked multiple times to make sure that the USB VID:PID is correct. Also I use the identifyusb command in tinycore

Do you select the USB boot while at GRUB ? Also what is your VID:PID ?

Edited February 11, 2022 by pocopico

Dvalin21 · February 11, 2022

Just now, pocopico said:

Do you select the USB boot while at GRUB ?

Everytime

pocopico · February 11, 2022

1 minute ago, Dvalin21 said:

Everytime

What is your USB , VID:PID ?

Dvalin21 · February 11, 2022

13 minutes ago, pocopico said:

What is your USB , VID:PID ?

Bus 001 Device 027: ID 0718:7722 Imation Corp. USB Flash Drive

Edited February 11, 2022 by Dvalin21

Dvalin21 · February 11, 2022

@pocopico

This is from my user_config.json

{
"extra_cmdline": {
"pid": "0x7722",
"vid": "0x0718",

hendry · February 11, 2022

35 minutes ago, pocopico said:

Yeah,

this almost always means two things,

For physical , you have either set the wrong USB VID:PID of you have selected SATA boot on GRUB menu.

For VMware virtual, you have not selected SATA boot on GRUB menu.

For proxmox/qemu virtual, you have not followed @haydibe instructions.

When you are not findind /dev/synoboot on your system it simply means that redpill was not able to properly shim a device as synoboot.

I always select SATA boot on GRUB menu..

then ?

pocopico · February 11, 2022

4 minutes ago, Dvalin21 said:

@pocopico

This is from my user_config.json

{
"extra_cmdline": {
"pid": "0x7722",
"vid": "0x0718",

That seems correct, do you see these values on GRUB if you highlight the USB boot entry and press "e" to edit ?

Aigor · February 11, 2022

Just now, hendry said:

I always select SATA boot on GRUB menu..

then ?

On bare metal you have to choice USB

hendry · February 11, 2022

2 minutes ago, Aigor said:

On bare metal you have to choice USB

no, i didn't use baremetal.

I'm using VM from my QNAP nas..

tc@box:~$ sudo ./rploader.sh identifyusb now
Machine is VIRTUAL Hypervisor=KVM
Sorry, no usb disk could be identified

Edited February 11, 2022 by hendry

TinyCore RedPill Loader (TCRP)

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation