RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal

[mosfit]

Hello. Is ddns in RedPill disabled? Can this function be turned on somehow

Edited July 18, 2022 by mosfit

[flyride]

DDNS itself works fine.  You may be unable to use a Synology account and the synology.me DDNS because a generated serial is not valid for this service (nor should you expect to use it for free).

 

Any of the other DDNS providers work, or you can use a Docker DDNS.

[mosfit]

I've always used the registered original serial number + mac and it worked, on 7.1 can't login to ddns service from synology

[burtal]

Hello ... quick question :

 

i made a test on a baremetal upgrade from 3615xs 6.2.3-u3 to 3622xs 7.1.0 ...on a Microserver Gen8  and all worked fine 

The only issue is that i cannot change the MTU to 9000..... is this a loader issue ?  do i need to add more or updated drivers ? 

Anyone with Gen8 can confirm ?

 

Before attempting the upgrade with the live disks in, and do the real migration i would like to also fix this , if is possible.

Edited July 19, 2022 by burtal

[burtal]

ok ... so i tried the stick that successfully migrated 3615xz 6.2.3-3 to 3622xs 7.1  on one test disk , but now the live update in "prod" is not working

 

i get the error to either check the network , or that the file is corrupted.

 

pulled all the disk out, put in the test disk ....and all boots fine to 7.1 update 1

 

SynologyNAS login: root

Synology strongly advises you not to run commands as the root user, who has
the highest privileges on the system. Doing so may cause major damages
to the system. Please note that if you choose to proceed, all consequences are
at your own risk.

 

BusyBox v1.30.1 () built-in shell (ash)

SynologyNAS> cat /var/log/*rc*
START /linuxrc.syno.impl
Insert Marvell 1475 SATA controller driver
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore ... [  OK  ]
:: Loading module ehci-hcd ... [  OK  ]
:: Loading module ehci-pci ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module xhci-pci ... [  OK  ]
:: Loading module usb-storage ... [  OK  ]
:: Loading kernel modules from extensions ...
Loading kmod #0 "libphy.ko" for pocopico.tg3 (args: )
Loading kmod #1 "tg3.ko" for pocopico.tg3 (args: )
:: Loading kernel modules from extensions ... [  OK  ]
:: Executing "on_boot" custom scripts ...
Running "check-tg3.sh" for pocopico.tg3->on_boot
Loading module tg3 -> Module tg3 loaded succesfully
Ran "check-tg3.sh" for pocopico.tg3->on_boot - exit=0
Running "boot-wait.sh" for redpill-boot-wait->on_boot
Still waiting for boot device (waited 1 of 30 seconds)
Still waiting for boot device (waited 2 of 30 seconds)
Still waiting for boot device (waited 3 of 30 seconds)
Confirmed a valid-looking /dev/synoboot device
Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0
Running "install_rd.sh" for redpill-misc->on_boot
Starting ttyd, listening on port: 7681
Ran "install_rd.sh" for redpill-misc->on_boot - exit=0
:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
Insert synorbd kernel module
Insert synofsbd kernel module
Insert sha256 kernel module
All disk ready or timeout execeed
Assemble args: -u 1db88863:19f94f8f:3017a5a8:c86610be /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1
mdadm: /dev/md0 has been started with 4 drives (out of 12).
Partition Version=8
 /sbin/e2fsck exists, checking /dev/md0...
e2fsck 1.44.1 (24-Mar-2018)
/sbin/e2fsck -yvf returns 0
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
Failed to found any patch
No upgrade file found
============upgrade
------------bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/synoinfo.conf:unique -> synology_broadwellnk_3622xs+
  value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_bromolow_3615xs
Skip bootup smallupdate, because root is not matched to junior
============bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/synoinfo.conf:unique -> synology_broadwellnk_3622xs+
  value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_bromolow_3615xs
Exit on error [7] root not matched with junior...
Wed Jul 20 07:58:09 UTC 2022
/dev/md0 /tmpRoot ext4 rw,relatime,data=ordered 0

 

 

 

any ideea on this ?

 

./my.sh DS3622xs+    was used for boot loader creation i used the script from this thread  

 

Edited July 20, 2022 by burtal

[Peter Suh]

1 hour ago, burtal said:

ok ... so i tried the stick that successfully migrated 3615xz 6.2.3-3 to 3622xs 7.1  on one test disk , but now the live update in "prod" is not working

 

i get the error to either check the network , or that the file is corrupted.

 

pulled all the disk out, put in the test disk ....and all boots fine to 7.1 update 1

 

SynologyNAS login: root

Synology strongly advises you not to run commands as the root user, who has
the highest privileges on the system. Doing so may cause major damages
to the system. Please note that if you choose to proceed, all consequences are
at your own risk.

 

BusyBox v1.30.1 () built-in shell (ash)

SynologyNAS> cat /var/log/*rc*
START /linuxrc.syno.impl
Insert Marvell 1475 SATA controller driver
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore ... [  OK  ]
:: Loading module ehci-hcd ... [  OK  ]
:: Loading module ehci-pci ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module xhci-pci ... [  OK  ]
:: Loading module usb-storage ... [  OK  ]
:: Loading kernel modules from extensions ...
Loading kmod #0 "libphy.ko" for pocopico.tg3 (args: )
Loading kmod #1 "tg3.ko" for pocopico.tg3 (args: )
:: Loading kernel modules from extensions ... [  OK  ]
:: Executing "on_boot" custom scripts ...
Running "check-tg3.sh" for pocopico.tg3->on_boot
Loading module tg3 -> Module tg3 loaded succesfully
Ran "check-tg3.sh" for pocopico.tg3->on_boot - exit=0
Running "boot-wait.sh" for redpill-boot-wait->on_boot
Still waiting for boot device (waited 1 of 30 seconds)
Still waiting for boot device (waited 2 of 30 seconds)
Still waiting for boot device (waited 3 of 30 seconds)
Confirmed a valid-looking /dev/synoboot device
Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0
Running "install_rd.sh" for redpill-misc->on_boot
Starting ttyd, listening on port: 7681
Ran "install_rd.sh" for redpill-misc->on_boot - exit=0
:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
Insert synorbd kernel module
Insert synofsbd kernel module
Insert sha256 kernel module
All disk ready or timeout execeed
Assemble args: -u 1db88863:19f94f8f:3017a5a8:c86610be /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1
mdadm: /dev/md0 has been started with 4 drives (out of 12).
Partition Version=8
 /sbin/e2fsck exists, checking /dev/md0...
e2fsck 1.44.1 (24-Mar-2018)
/sbin/e2fsck -yvf returns 0
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
Failed to found any patch
No upgrade file found
============upgrade
------------bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/synoinfo.conf:unique -> synology_broadwellnk_3622xs+
  value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_bromolow_3615xs
Skip bootup smallupdate, because root is not matched to junior
============bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/synoinfo.conf:unique -> synology_broadwellnk_3622xs+
  value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_bromolow_3615xs
Exit on error [7] root not matched with junior...
Wed Jul 20 07:58:09 UTC 2022
/dev/md0 /tmpRoot ext4 rw,relatime,data=ordered 0

 

 

 

any ideea on this ?

 

./my.sh DS3622xs+    was used for boot loader creation i used the script from this thread  

 

 

 

Try the below command in junior
ll /dev/syno*
If there is only one result, synoboots are not properly mounted.
Displays a file corruption error message.

 

If this is your first migration from DSM 6.2.3 to DSM 7.1
Rather, jun mode is more advantageous.

./my.sh DS3622xs+J
Try making the bootloader again with

 

Edited July 20, 2022 by Peter Suh

[burtal]

i just remade the bootloader using manual commands , no scripts

Now i got the "check network" error ..... sometimes i got the network , sometimes the corupt file

 

 

SynologyNAS> ll /dev/syno*
crw-r--r--    1 root     root      201,   0 Jul 20 09:28 /dev/synobios
brw-------    1 root     root      135, 240 Jul 20 09:28 /dev/synoboot
brw-------    1 root     root      135, 241 Jul 20 09:28 /dev/synoboot1
brw-------    1 root     root      135, 242 Jul 20 09:28 /dev/synoboot2
brw-------    1 root     root      135, 243 Jul 20 09:28 /dev/synoboot3

 

 

yes is first migration for the live disks ......I`ll retry the jun mode ..... but what are the benefits ?  vs the regular mode.

i see that jun mode is for 7.0.1 not 7.1 ?

 

so i need to download the .pat for 7.0.1?

 

 

The question is , does DSM write something on the stick ?  i mean the number of disks ?    cause the same stick ..all the versions that i made, works with the single migrated disk , but does not want to migrate the main 4 disks

 

 

Edited July 20, 2022 by burtal

[Peter Suh]

1 hour ago, burtal said:

i just remade the bootloader using manual commands , no scripts

Now i got the "check network" error ..... sometimes i got the network , sometimes the corupt file

 

 

SynologyNAS> ll /dev/syno*
crw-r--r--    1 root     root      201,   0 Jul 20 09:28 /dev/synobios
brw-------    1 root     root      135, 240 Jul 20 09:28 /dev/synoboot
brw-------    1 root     root      135, 241 Jul 20 09:28 /dev/synoboot1
brw-------    1 root     root      135, 242 Jul 20 09:28 /dev/synoboot2
brw-------    1 root     root      135, 243 Jul 20 09:28 /dev/synoboot3

 

 

yes is first migration for the live disks ......I`ll retry the jun mode ..... but what are the benefits ?  vs the regular mode.

i see that jun mode is for 7.0.1 not 7.1 ?

 

so i need to download the .pat for 7.0.1?

 

 

The question is , does DSM write something on the stick ?  i mean the number of disks ?    cause the same stick ..all the versions that i made, works with the single migrated disk , but does not want to migrate the main 4 disks

 

 

 

 

It is your choice whether to apply the latest version of 7.1 update 3 using 7.0.1.

 

If you want to migrate only 1 out of 4 disks
Shouldn't the other 3 be careless?

 

It is a dangerous idea to ignore and process the remaining three disks only by adjusting the sataportmap.
Physically separate the 3 disks from the PC.
If it is bare metal, it will be possible to migrate to one disk with only sataportmap = 1.

[burtal]

hello

 

No ... is an entire separate disk  used only for testing....i wanted to check and get familiar with the migration process before using the 4 main disks that have data.

 

But it dosen`t seem to be important as i made /remade multiple times the the bootloader, but it seem to always fail with either network or file corruption errors.

Is either something in the config file (sata mapping maybe ) ... or maybe someting in my original disks it does not like it.... 

 

 

tc@box:~$ ./rploader.sh satamap

Found "00:1f.2 Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05)"
Detected 6 ports/4 drives. Override # of ports or ENTER to accept <6>

Computed settings:
SataPortMap=6
DiskIdxMap=00

 

i should choose 4 instead of 6 ?

 

 

Ran "install_rd.sh" for redpill-misc->on_boot - exit=0
:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
Insert synorbd kernel module
Insert synofsbd kernel module
Insert sha256 kernel module
All disk ready or timeout execeed
Assemble args: -u 1db88863:19f94f8f:3017a5a8:c86610be /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1
mdadm: /dev/md0 has been started with 4 drives (out of 12).
Partition Version=8
 /sbin/e2fsck exists, checking /dev/md0...
e2fsck 1.44.1 (24-Mar-2018)
/sbin/e2fsck -yvf returns 0
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
Failed to found any patch
No upgrade file found
============upgrade
------------bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/synoinfo.conf:unique -> synology_broadwellnk_3622xs+
  value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_bromolow_3615xs
Skip bootup smallupdate, because root is not matched to junior
============bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/synoinfo.conf:unique -> synology_broadwellnk_3622xs+
  value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_bromolow_3615xs
Exit on error [7] root not matched with junior...
Wed Jul 20 07:58:09 UTC 2022
/dev/md0 /tmpRoot ext4 rw,relatime,data=ordered 0 

Spoiler

 

 

 

 

Ok, ill reformat the usb stick agan  install redpill v0.8 then run ./my.sh DS3622xs+J   to see how it goes .... and use the 7.1 pat file.

 

 

 

 

 

LE: 

 

made the bootloader with  ./my.sh DS3622xs+J   and try to install the DSM_DS3622xs+_42661.pat

 

TART /linuxrc.syno.impl
Insert Marvell 1475 SATA controller driver
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore ... [  OK  ]
:: Loading module ehci-hcd ... [  OK  ]
:: Loading module ehci-pci ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module xhci-pci ... [  OK  ]
:: Loading module usb-storage ... [  OK  ]
:: Loading kernel modules from extensions ...
Loading kmod #0 "libphy.ko" for pocopico.tg3 (args: )
Loading kmod #1 "tg3.ko" for pocopico.tg3 (args: )
Checking if kmods for thethorgroup.virtio should run using check-virtio.sh script
Checking for VirtIO
*No* VirtIO hypervisor detected
NOT loading kmods for thethorgroup.virtio
:: Loading kernel modules from extensions ... [  OK  ]
:: Executing "on_boot" custom scripts ...
Running "check-tg3.sh" for pocopico.tg3->on_boot
Loading module tg3 -> Module tg3 loaded succesfully
Ran "check-tg3.sh" for pocopico.tg3->on_boot - exit=0
Running "boot-wait.sh" for redpill-boot-wait->on_boot
Still waiting for boot device (waited 1 of 30 seconds)
Still waiting for boot device (waited 2 of 30 seconds)
Still waiting for boot device (waited 3 of 30 seconds)
Confirmed a valid-looking /dev/synoboot device
Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0
Running "install_rd.sh" for redpill-dtb-static->on_boot
'model_ds3622xsp.dtb' -> '/etc.defaults/model.dtb'
'model_ds3622xsp.dtb' -> '/var/run/model.dtb'
Ran "install_rd.sh" for redpill-dtb-static->on_boot - exit=0
Running "install_rd.sh" for redpill-misc->on_boot
Starting ttyd, listening on port: 7681
Ran "install_rd.sh" for redpill-misc->on_boot - exit=0
:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
All disk ready or timeout execeed
Assemble args: -u 1db88863:19f94f8f:3017a5a8:c86610be /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1
mdadm: /dev/md0 has been started with 2 drives (out of 12).
Partition Version=8
 /sbin/e2fsck exists, checking /dev/md0... 
e2fsck 1.44.1 (24-Mar-2018)
/sbin/e2fsck -yvf returns 0
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
Mount data partition: /dev/md0 -> /tmpData
No upgrade file exists
End upgrade procedure
============upgrade
------------bootup-smallupdate
Try bootup smallupdate
Total:  22 packages
{"action":"stop","id":"SynologyApplicationService","status":"skip"}
{"action":"stop","id":"VirtualHere","status":"skip"}
{"action":"stop","id":"TextEditor","status":"skip"}
{"action":"stop","id":"SurveillanceStation","status":"skip"}
{"action":"stop","id":"VideoStation","status":"skip"}
{"action":"stop","id":"MediaServer","status":"skip"}
{"action":"stop","id":"FileStation","status":"begin"}
{"action":"stop","id":"SynoFinder","status":"begin"}
{"action":"stop","id":"Node.js_v12","status":"begin"}
{"action":"stop","id":"Plex Media Server","status":"begin"}
{"action":"stop","id":"HyperBackup","status":"begin"}
{"action":"stop","id":"git","status":"begin"}
{"action":"stop","id":"Node.js_v8","status":"begin"}
{"action":"stop","id":"Java8","status":"begin"}
{"action":"stop","id":"nano","status":"begin"}
{"action":"stop","id":"py3k","status":"begin"}
{"action":"stop","id":"DownloadStation","status":"begin"}
{"action":"stop","id":"OAuthService","status":"begin"}
{"action":"stop","id":"Docker","status":"begin"}
{"action":"stop","id":"PHP7.2","status":"begin"}
{"action":"stop","id":"ffmpeg","status":"begin"}
{"action":"stop","id":"mc","status":"begin"}
Failed to stop all packages 150
BOOTUP_UPGRADE_SMALLUPDATE
Fail to bootup smallupdate
Failed to synoupgrade --bootup-smallupdate [255]
Exit on error [6] bootup-smallupdate failed...
Wed Jul 20 13:00:03 UTC 2022
/dev/md0 /tmpRoot ext4 rw,relatime,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0

 

I got the network error this time ....and failed

Edited July 20, 2022 by burtal

[Peter Suh]

35 minutes ago, burtal said:

hello

 

No ... is an entire separate disk  used only for testing....i wanted to check and get familiar with the migration process before using the 4 main disks that have data.

 

But it dosen`t seem to be important as i made /remade multiple times the the bootloader, but it seem to always fail with either network or file corruption errors.

Is either something in the config file (sata mapping maybe ) ... or maybe someting in my original disks it does not like it.... 

 

 

tc@box:~$ ./rploader.sh satamap

Found "00:1f.2 Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05)"
Detected 6 ports/4 drives. Override # of ports or ENTER to accept <6>

Computed settings:
SataPortMap=6
DiskIdxMap=00

 

i should choose 4 instead of 6 ?

 

 

:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
Insert synorbd kernel module
Insert synofsbd kernel module
Insert sha256 kernel module
All disk ready or timeout execeed
Assemble args: -u 1db88863:19f94f8f:3017a5a8:c86610be /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1
mdadm: /dev/md0 has been started with 2 drives (out of 12).
Partition Version=8
 /sbin/e2fsck exists, checking /dev/md0...
e2fsck 1.44.1 (24-Mar-2018)
/sbin/e2fsck -yvf returns 0
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
Failed to found any patch
No upgrade file found
============upgrade
------------bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/synoinfo.conf:unique -> synology_broadwellnk_3622xs+
  value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_bromolow_3615xs
Skip bootup smallupdate, because root is not matched to junior
============bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/synoinfo.conf:unique -> synology_broadwellnk_3622xs+
  value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_bromolow_3615xs
Exit on error [7] root not matched with junior...
Wed Jul 20 10:13:21 UTC 2022
/dev/md0 /tmpRoot ext4 rw,relatime,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0

 

 

 

 

Ok, ill reformat the usb stick agan  install redpill v0.8 then run ./my.sh DS3622xs+J   to see how it goes .... and use the 7.1 pat file.

 

 

 

You seem to be trying to automatically migrate one disk after successful migration by plugging the other three disks into disk. right?

If so, how about doing this?

 

./my.sh DS3615xs
After completing the first migration of all disks to DS3615xs

 

again
./my.sh DS3622xs+
It would be better to do a secondary migration to

 

The reason for returning to jot mode instead of jun mode is
Multiple jun mode migrations can cause damage to the system partition if done incorrectly.

 

In this process, be sure to use the DSM PAT file up to 7.1 Update 1.
The moment Update 2 or higher version is used, it falls into a restoration loop.

Edited July 20, 2022 by Peter Suh

[burtal]

no ,  i try to auto migrate  4 disks  3615xs 6.2.3-3 to 3622xs 7.1 latest available on my microserver gen8 HP

 

The one disk migration that worked is a separate thing ..... that one disk migration was made for me to see and understand the process of bootload creation and how things work.....

 

So you say the best path will be small and incremental updates, upgrading  DSM first and then the platform ?

And to use the regular command not the J version

 

 

FYI 

J command also failing

 

TART /linuxrc.syno.impl
Insert Marvell 1475 SATA controller driver
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore ... [  OK  ]
:: Loading module ehci-hcd ... [  OK  ]
:: Loading module ehci-pci ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module xhci-pci ... [  OK  ]
:: Loading module usb-storage ... [  OK  ]
:: Loading kernel modules from extensions ...
Loading kmod #0 "libphy.ko" for pocopico.tg3 (args: )
Loading kmod #1 "tg3.ko" for pocopico.tg3 (args: )
Checking if kmods for thethorgroup.virtio should run using check-virtio.sh script
Checking for VirtIO
*No* VirtIO hypervisor detected
NOT loading kmods for thethorgroup.virtio
:: Loading kernel modules from extensions ... [  OK  ]
:: Executing "on_boot" custom scripts ...
Running "check-tg3.sh" for pocopico.tg3->on_boot
Loading module tg3 -> Module tg3 loaded succesfully
Ran "check-tg3.sh" for pocopico.tg3->on_boot - exit=0
Running "boot-wait.sh" for redpill-boot-wait->on_boot
Still waiting for boot device (waited 1 of 30 seconds)
Still waiting for boot device (waited 2 of 30 seconds)
Still waiting for boot device (waited 3 of 30 seconds)
Confirmed a valid-looking /dev/synoboot device
Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0
Running "install_rd.sh" for redpill-dtb-static->on_boot
'model_ds3622xsp.dtb' -> '/etc.defaults/model.dtb'
'model_ds3622xsp.dtb' -> '/var/run/model.dtb'
Ran "install_rd.sh" for redpill-dtb-static->on_boot - exit=0
Running "install_rd.sh" for redpill-misc->on_boot
Starting ttyd, listening on port: 7681
Ran "install_rd.sh" for redpill-misc->on_boot - exit=0
:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
All disk ready or timeout execeed
Assemble args: -u 1db88863:19f94f8f:3017a5a8:c86610be /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1
mdadm: /dev/md0 has been started with 2 drives (out of 12).
Partition Version=8
 /sbin/e2fsck exists, checking /dev/md0...
e2fsck 1.44.1 (24-Mar-2018)
/sbin/e2fsck -yvf returns 0
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
Mount data partition: /dev/md0 -> /tmpData
No upgrade file exists
End upgrade procedure
============upgrade
------------bootup-smallupdate
Try bootup smallupdate
Total:  22 packages
{"action":"stop","id":"SynologyApplicationService","status":"skip"}
{"action":"stop","id":"VirtualHere","status":"skip"}
{"action":"stop","id":"TextEditor","status":"skip"}
{"action":"stop","id":"SurveillanceStation","status":"skip"}
{"action":"stop","id":"VideoStation","status":"skip"}
{"action":"stop","id":"MediaServer","status":"skip"}
{"action":"stop","id":"FileStation","status":"begin"}
{"action":"stop","id":"SynoFinder","status":"begin"}
{"action":"stop","id":"Node.js_v12","status":"begin"}
{"action":"stop","id":"Plex Media Server","status":"begin"}
{"action":"stop","id":"HyperBackup","status":"begin"}
{"action":"stop","id":"git","status":"begin"}
{"action":"stop","id":"Node.js_v8","status":"begin"}
{"action":"stop","id":"Java8","status":"begin"}
{"action":"stop","id":"nano","status":"begin"}
{"action":"stop","id":"py3k","status":"begin"}
{"action":"stop","id":"DownloadStation","status":"begin"}
{"action":"stop","id":"OAuthService","status":"begin"}
{"action":"stop","id":"Docker","status":"begin"}
{"action":"stop","id":"PHP7.2","status":"begin"}
{"action":"stop","id":"ffmpeg","status":"begin"}
{"action":"stop","id":"mc","status":"begin"}
Failed to stop all packages 150
BOOTUP_UPGRADE_SMALLUPDATE
Fail to bootup smallupdate
Failed to synoupgrade --bootup-smallupdate [255]
Exit on error [6] bootup-smallupdate failed...
Wed Jul 20 13:00:03 UTC 2022
/dev/md0 /tmpRoot ext4 rw,relatime,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0

 

[Peter Suh]

 

This log and capture is currently only available in my.sh
This is the migration process of DS1621xs+ -> RS4021xs+.

 

Isn't it similar to your log?

By the way, it seems that you are trying to judge only by looking at the junior log.

 

As shown below, on the DSM installation screen, you will be prompted to proceed with the migration.
Don't be fooled by the error code

Connect to the DSM installation URL of port 5000, capture the result and attach it together.

 

 

Spoiler

SynologyNAS> cat linuxrc.syno.log
START /linuxrc.syno.impl
Insert Marvell 1475 SATA controller driver
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore ... [  OK  ]
:: Loading module ehci-hcd ... [  OK  ]
:: Loading module ehci-pci ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module xhci-pci ... [  OK  ]
:: Loading module usb-storage ... [  OK  ]
:: Loading kernel modules from extensions ...
Loading kmod #0 "e1000.ko" for PeterSuh-Q3.e1000 (args: )
Loading kmod #0 "e1000e.ko" for PeterSuh-Q3.e1000e (args: )
Checking if kmods for thethorgroup.virtio should run using check-virtio.sh script
Checking for VirtIO
VirtIO hypervisor detected
Loading kmod #0 "virtio.ko" for thethorgroup.virtio (args: )
Loading kmod #1 "virtio_ring.ko" for thethorgroup.virtio (args: )
Loading kmod #2 "virtio_mmio.ko" for thethorgroup.virtio (args: )
Loading kmod #3 "virtio_pci.ko" for thethorgroup.virtio (args: )
Loading kmod #4 "virtio_blk.ko" for thethorgroup.virtio (args: )
Loading kmod #5 "virtio_net.ko" for thethorgroup.virtio (args: )
Loading kmod #6 "virtio_scsi.ko" for thethorgroup.virtio (args: )
:: Loading kernel modules from extensions ... [  OK  ]
:: Executing "on_boot" custom scripts ...
Running "check-e1000.sh" for PeterSuh-Q3.e1000->on_boot
Loading module e1000 -> Module e1000 loaded succesfully
Ran "check-e1000.sh" for PeterSuh-Q3.e1000->on_boot - exit=0
Running "check-e1000e.sh" for PeterSuh-Q3.e1000e->on_boot
Loading module e1000e -> Module e1000e loaded succesfully
Ran "check-e1000e.sh" for PeterSuh-Q3.e1000e->on_boot - exit=0
Running "install_rd.sh" for redpill-misc->on_boot
Starting ttyd, listening on port: 7681
Ran "install_rd.sh" for redpill-misc->on_boot - exit=0
Running "boot-wait.sh" for thethorgroup.boot-wait->on_boot
Confirmed a valid-looking /dev/synoboot device
Ran "boot-wait.sh" for thethorgroup.boot-wait->on_boot - exit=0
:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
insmod: can't insert '/lib/modules/etxhci-hcd.ko': No such file or directory
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
Insert synorbd kernel module
Insert synofsbd kernel module
Insert sha256 kernel module
All disk ready or timeout execeed
Assemble args: -u 82bc97f7:9024f1fa:05d949f7:b0bbaec7 /dev/sdb1 /dev/sdc1
mdadm: /dev/md0 has been started with 2 drives (out of 16).
Partition Version=8
 /sbin/e2fsck exists, checking /dev/md0... 
e2fsck 1.44.1 (24-Mar-2018)
/sbin/e2fsck -yvf returns 0
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
Failed to found any patch
No upgrade file found
============upgrade
------------bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/synoinfo.conf:unique -> synology_broadwellnk_rs4021xs+
  value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_broadwellnk_1621xs+
Skip bootup smallupdate, because root is not matched to junior
============bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/synoinfo.conf:unique -> synology_broadwellnk_rs4021xs+
  value2: /tmpRoot/etc.defaults/synoinfo.conf:unique => synology_broadwellnk_1621xs+
Exit on error [7] root not matched with junior...
Wed Jul 20 14:50:16 UTC 2022
/dev/md0 /tmpRoot ext4 rw,relatime,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0

 

 

[burtal]

yes is similar and yes  i got that migration screen also (everytime) but when i gave it the .pat file it say is corrupted or network errors at about 50% during upload.

 

 

now i put back the old bootloader and went back  to 6.23

 

I will retry later, cause now i got another issue, that might cause the .pat upload to fail

 

 

I need to fix this in 6.2.3 before re attepting the upload ..... looks like 7.1 installer managed to put some files on the disk but gets corupted as there is not enough space.

 

any ideeas on how to clean up ? or what partitions i need to clean up ?

Edited July 20, 2022 by burtal

[burtal]

2 hours ago, burtal said:

yes is similar and yes  i got that migration screen also (everytime) but when i gave it the .pat file it say is corrupted or network errors at about 50% during upload.

 

 

now i put back the old bootloader and went back  to 6.23

 

I will retry later, cause now i got another issue, that might cause the .pat upload to fail

 

 

I need to fix this in 6.2.3 before re attepting the upload ..... looks like 7.1 installer managed to put some files on the disk but gets corupted as there is not enough space.

 

any ideeas on how to clean up ? or what partitions i need to clean up ?

 

this has about 300MB left over .... but still the .pat has 350 so .....maybe is getting corrupted during the upload because the lack of space ?

 

 

cleared out the space ...redid the bootloader ...got in the same situation .... network or file corupted , this time network

Edited July 20, 2022 by burtal

[CiViCKiDD]

I am also having a satamap issue trying to get tinycore set up to migrate my primary NAS. Here are my specs:

 

ASRock H97M-ITX/ac motherboard, with 5 onboard SATA ports (I have another SATA card for a 6th drive)

Intel i3 cpu

6x hdd's of varying sizes

 

It works great with DSM 6.x using Jun's bootloader. I tested the migration process on my NUC - which went perfectly and runs great over a week later. Here is the error I am getting on my primary NAS:

 

tc@box:~$ ./rploader.sh satamap now

Found "00:1f.2 Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]"
Detected 6 ports/5 drives. Bad ports: 6. Override # of ports or ENTER to accept <6> ^C
tc@box:~$

 

I have tried enabling hotplug in the BIOS for each sata port, I've tried running this command with just one test drive and then again with all my primary drives connected, etc. I think I need to manually tackle this at this point but don't really understand how to generate the right information - help?
 

 

[burtal]

ok ... i managed to install 7.1.0 update 2 (is the latest right? for 3622xs i see some have update 3 but on here is dont see any for broawell 7.1 https://archive.synology.com/download/Os/DSM/7.1-42661-3)

all data is still there ... some permission issues and some apps that no longer works ....but is fine.

 

 

Also i dont know why is say connection failed .... because is all working

 

 

There was indeed less then 600MB on  "/" partition, sufficient not to trigger the warning in 6.2.3 but less than it actually it needed for a full upgrade .... the was a small backupfolder from a docker in "/"  that should not be there(made it some years ago) ...after i cleared deleted it  got around 760 mb of free space and the install proceed fine

 

Thanks for your help and input /creating this fine script.

 

As a suggestion @pocopico and @Peter Suh maybe you can add a check in your scripts for "/" to have the required space so you can avoid guys like me wasting your time:D with stupid questions 

Synolo team also dumb as they put out a corrupted file error, while actually there is no space on the patition

 

Thanks again

Edited July 21, 2022 by burtal

[Peter Suh]

6 minutes ago, burtal said:

ok ... i managed to install 7.1.0 update 2 (is the latest right? for 3622xs i see some have update 3 but on here is dont see any for broawell 7.1 https://archive.synology.com/download/Os/DSM/7.1-42661-3)

all data is still there ... some permission issues and some apps that no longer works ....but is fine.

 

 

Also i dont know why is say connection failed .... because is all working

 

 

There was indeed less then 600MB on  "/" partition, sufficient not to trigger the warning in 6.2.3 but less than it actually it needed for a full upgrade .... the was a small backupfolder from a docker in "/"  that should not be there(made it some years ago) ...after i cleared deleted it  got around 760 mb of free space and the install proceed fine

 

Thanks for your help and input /creating this fine script.

 

As a suggestion @pocopico and @Peter Suh maybe you can add a check in your scripts for "/" to have the required space so you can avoid guys like me wasting your time:D with stupid questions 

Synolo team also dumb as they put out a corrupted file error, while actually there is no space on the patition

 

Thanks again

 

There is no functional problem about the failure to connect to the Internet in the update menu, so you do not have to worry too much.

 

To put it bluntly, the method you built is called jot mode, and the case of using the J option is jun mode.
See FlyRide's guide on the differences between the two modes.

 

In this jot mode, a virtual URL such as sample.com is recorded inside to prevent automatic update of DSM.
When the automatic update takes place, the XPE will either fail to boot or encounter the DSM recovery screen.

[Peter Suh]

7 hours ago, CiViCKiDD said:

I am also having a satamap issue trying to get tinycore set up to migrate my primary NAS. Here are my specs:

 

ASRock H97M-ITX/ac motherboard, with 5 onboard SATA ports (I have another SATA card for a 6th drive)

Intel i3 cpu

6x hdd's of varying sizes

 

It works great with DSM 6.x using Jun's bootloader. I tested the migration process on my NUC - which went perfectly and runs great over a week later. Here is the error I am getting on my primary NAS:

 

tc@box:~$ ./rploader.sh satamap now

Found "00:1f.2 Intel Corporation 9 Series Chipset Family SATA Controller [AHCI Mode]"
Detected 6 ports/5 drives. Bad ports: 6. Override # of ports or ENTER to accept <6> ^C
tc@box:~$

 

I have tried enabling hotplug in the BIOS for each sata port, I've tried running this command with just one test drive and then again with all my primary drives connected, etc. I think I need to manually tackle this at this point but don't really understand how to generate the right information - help?
 

 

 

Don't rely on tcrp's automatic mapping process and write your own sataportmap.
In general, if you record only the actual number of physical disks, there is no problem during the DSM installation process.
In the case of VM, you can record it as +1 considering the number of loader disks.

[burtal]

well that is good ...as we dont want auto updates anyway ....and is "bad" as i dont see if a new update is released....but i can live with that.....ill check it one in couple of moths and update then if there is also a loader patch for that update.

 

maybe on the next update ill migrate if possible to J option

 

Thanks

[CiViCKiDD]

7 hours ago, Peter Suh said:

 

Don't rely on tcrp's automatic mapping process and write your own sataportmap.
In general, if you record only the actual number of physical disks, there is no problem during the DSM installation process.
In the case of VM, you can record it as +1 considering the number of loader disks.

 

Thanks for the reply! I'm busy with work and family most of today, but hoping to try understand enough to tackle this again after hours tonight.

 

A few ignorant questions on writing my own sataportmap:

1. Can I leverage anything from my working Jun / DSM 6.x install (either an existing sataportmap on the usb stick, or other information from storage manager?)

2. I have to get a better look but I think the reason satamap thinks I have 6 SATA ports is because I have an eSATA port on the back of my mobo. I definitely only have 5 internal SATA plugs. Do I just need to update the SataPortMap variable (and in my case I assume it would be SataPortMap=510 because I have 5 drives connected to the onboard SATA,and 1 drive connected to the secondary SATA card?)? When do I need to worry about the DiskIdxMap, sata_remap, and DiskSeqReverse variables?

 

Closest I could find to a guide was this but I'm not sure I'm fully tracking the right way to do this:

 

[micgo]

On 7/1/2022 at 6:17 PM, Peter Suh said:

 

VPS is so new to me, I don't know if I can help.
Is the booted OS environment linux?

 

Is the default path for logging in as tc user /home/tc?
What image from TC did you use? vmdk ? img ?

 

If you can use the curl command, you can restore the TC environment by downloading it with the command below.

 

curl --location "https://github.com/pocopico/tinycore-redpill/raw/main/rploader.sh" --output rploader.sh

 

chmod +x rploader.sh

 

./rploader.sh fullupgrade

 

i booted up my vps using ubuntu and dd tinycore .img to the VPS. and then i reboot my vps and login with KVM console. i have to ifconfig to set my ip and routing.

 

after the bootup i m at /home/tc but with 0 file inside.

i m using .img

 

when i sudo ./rploader.sh fullupgrade

i get return 

./rploader.sh: line 8 syntax error: unexpected newline

Edited July 27, 2022 by micgo

[Castelrink]

Hello everyone,

One question please: I can't find where to enter the password tc/P@ssw0rd? How should I do it to be able to continue?

Thanks.

[Peter Suh]

1 hour ago, Castelrink said:

Hello everyone,

One question please: I can't find where to enter the password tc/P@ssw0rd? How should I do it to be able to continue?

Thanks.

 

4. Adjust CONFIG after SSH connection

 

Ssh connection with putty etc. from PC other than Xpenology. ( id:tc / pass : P@ssw0rd )

 

-> Do you not understand what this means?

 

[Peter Suh]

On 7/27/2022 at 9:18 AM, micgo said:

 

i booted up my vps using ubuntu and dd tinycore .img to the VPS. and then i reboot my vps and login with KVM console. i have to ifconfig to set my ip and routing.

 

after the bootup i m at /home/tc but with 0 file inside.

i m using .img

 

when i sudo ./rploader.sh fullupgrade

i get return 

./rploader.sh: line 8 syntax error: unexpected newline

 

Also, sometimes files in /home/tc disappear. In that case, download and restore with the curl command below.

 

curl --location "https://github.com/pocopico/tinycore-redpill/raw/main/rploader.sh" --output rploader.sh

[MikeaP]

Hello fellow users,

 

I need a hand in doing baremetal installation and I beg your pardon upfront if I'm posting in the wrong forum thread (I have read through quite a lot of stuff here and this one seemed most appropriate).

 

I have previously done a successful installation using this guide on the very same hardware I'm trying to do an installation now.

However it was quite some time ago with redpill v 0.4.something.

 

This time following instructions and modifications I did last time to meet my hardware I face an issue - after running redpill I'm able to see my NAS on the network asking me for the initial installation of DSM, I feed in the PAT file and installation fails at around 55% telling me the file is wrong.

 

My hardware is Dell R210II (pretty old one) which most closely meets bromolow image.

 

Having started a fresh build with redpill and looking into the system via serial console I can see that:

1) there are no /dev/synoboot* entries (I made sure pid/vid of my USB stick are correct; /dev/synobios is there).

2) in dmesg output I see kernel lpc_ich is complaining about unknown LPC device with devId 0x1C52

3) I don't see any trace of USB block device drivers / USB as such in the system

 

Could you please help me with some guidance on where to look further:

1) given a very first start after building image with redpill: should there be /dev/synoboot* entries (though not mounted) ? or are they expected to appear only after successfully installing DSM from PAT file?

2) Do I suspect it right that failing to start ICH (in my case Intel C202 south bridge) kernel also fails to load USB support appropriately?

3) Were kernel files used by redpill modified somehow to drop ICH support which seems to be a part of standard lpc_ich.c according to "conventional" kernel sources ?

 

P.S. I have tried both bromolow (seems to be 3.x kernel) and broadwellnk (4.x kernel) with the same result - complaining about unknown LPC device 0x1c52 and failing to install PAT file.