Tutorial: Install/Migrate to DSM 7.x with TinyCore RedPill (TCRP) Loader

yonn · November 18, 2022

On 11/16/2022 at 8:58 PM, yonn said:

tc@box:~$ df -h|grep sd
/dev/sda3       899M 899M     0 100% /mnt/sda3
/dev/sda1        48M   39M 9.5M 81% /mnt/sda1
/dev/sda2        75M   11M   65M 14% /mnt/sda2

Yes. No space on sda3 ?????? why ?😕

maxime · November 18, 2022

HI! I didn't know this post, and yesterday I tried to update on my own my 918+ DSM 7.0.1-42218 Update 2 with RedPill Tinycore 0.45 TO 7.1.1-42962, using RedPill Tinycore 0.93. The process failed and now I'm stucked in a loop. This are the commands I used for upgrade:

./rploader.sh identifyusb
./rploader.sh serialgen DS918+ realmac
./rploader.sh satamap
./rploader.sh backup now
./rploader.sh ext ds918p-7.1.1-42962 add https://raw.githubusercontent.com/pocopico/redpill-load/develop/redpill-acpid/rpext-index.json
./rploader.sh build ds918p-7.1.1-42962 withfriend

Now I read this post and I saw that I should have created a folder after the "build" command:

./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh backup now;

Is it correct?

Which is the best way to solve my problem? Should I'll create the folder and retry to update to DS918+ or do you think it should be better try to upgrade for example to DS3622xs+ or DS920+?
Thank you so much for your support!

maxime · November 18, 2022

1 hour ago, maxime said:
HI! I didn't know this post, and yesterday I tried to update on my own my 918+ DSM 7.0.1-42218 Update 2 with RedPill Tinycore 0.45 TO 7.1.1-42962, using RedPill Tinycore 0.93. The process failed and now I'm stucked in a loop. This are the commands I used for upgrade:
./rploader.sh identifyusb
./rploader.sh serialgen DS918+ realmac
./rploader.sh satamap
./rploader.sh backup now
./rploader.sh ext ds918p-7.1.1-42962 add https://raw.githubusercontent.com/pocopico/redpill-load/develop/redpill-acpid/rpext-index.json
./rploader.sh build ds918p-7.1.1-42962 withfriend
Now I read this post and I saw that I should have created a folder after the "build" command:
./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh backup now;
Is it correct?

Which is the best way to solve my problem? Should I'll create the folder and retry to update to DS918+ or do you think it should be better try to upgrade for example to DS3622xs+ or DS920+?
Thank you so much for your support!

YES! The problem was I didn't create the folder before upgrade from 7.0.1 to 7.1.1! Thanks for your support (and this guide)!

unlikely · December 5, 2022

Hi, thanks for this tutorial, I'm trying to follow it to setup DSM 7 on a VM under Hyper-V, but I'm getting this error

tc@box:~$ ./rploader.sh build broadwellnk-7.1.1-42951
Error : Platform not found
rploader.sh

Version : 0.9.3.0

My understanding is this platform should be supported:

----------------------------------------------------------------------------------------
Available platform versions:
----------------------------------------------------------------------------------------
ds3622xsp-7.0.1-42218
ds3622xsp-7.0.1-42218-JUN
ds3622xsp-7.1.0-42621
ds3622xsp-7.1.0-42661
ds3622xsp-7.1.1-42951
ds3622xsp-7.1.1-42962

I did all the previous commands and my config file is

tc@box:~$ cat user_config.json
{
  "general": {
    "model": "DS3622xs+",
    "version": "7.1.1-42951",
    "smallfixnumber": "0",
    "zimghash": "",
    "rdhash": "",
    "usb_line": "",
    "sata_line": "",
    "redpillmake": "",
    "friendautoupd": "true",
    "hidesensitive": "false"
  },
  "ipsettings": {
    "ipset": "",
    "ipaddr": "",
    "ipgw": "",
    "ipdns": "",
    "ipproxy": ""
  },
  "extra_cmdline": {
    "pid": "0xa4a5",
    "vid": "0x0525",
    "sn": "21...DGQT",
    "mac1": "...",
    "netif_num": "1",
    "SataPortMap": "1",
    "DiskIdxMap": "00"
  },
  "synoinfo": {
    "internalportcfg": "0xffff",
    "maxdisks": "16",
    "support_bde_internal_10g": "no",
    "support_disk_compatibility": "no",
    "support_memory_compatibility": "no"
  },
  "ramdisk_copy": {}
}

The exact command of the tutorial gives the same error

./rploader.sh build broadwellnk-7.1.0-42661

Any idea? Thanks

rojoone2 · December 5, 2022

1 hour ago, unlikely said:

Hi, thanks for this tutorial, I'm trying to follow it to setup DSM 7 on a VM under Hyper-V, but I'm getting this error

tc@box:~$ ./rploader.sh build broadwellnk-7.1.1-42951
Error : Platform not found
rploader.sh

Version : 0.9.3.0

My understanding is this platform should be supported:

----------------------------------------------------------------------------------------
Available platform versions:
----------------------------------------------------------------------------------------
ds3622xsp-7.0.1-42218
ds3622xsp-7.0.1-42218-JUN
ds3622xsp-7.1.0-42621
ds3622xsp-7.1.0-42661
ds3622xsp-7.1.1-42951
ds3622xsp-7.1.1-42962

I did all the previous commands and my config file is

tc@box:~$ cat user_config.json
{
  "general": {
    "model": "DS3622xs+",
    "version": "7.1.1-42951",
    "smallfixnumber": "0",
    "zimghash": "",
    "rdhash": "",
    "usb_line": "",
    "sata_line": "",
    "redpillmake": "",
    "friendautoupd": "true",
    "hidesensitive": "false"
  },
  "ipsettings": {
    "ipset": "",
    "ipaddr": "",
    "ipgw": "",
    "ipdns": "",
    "ipproxy": ""
  },
  "extra_cmdline": {
    "pid": "0xa4a5",
    "vid": "0x0525",
    "sn": "21...DGQT",
    "mac1": "...",
    "netif_num": "1",
    "SataPortMap": "1",
    "DiskIdxMap": "00"
  },
  "synoinfo": {
    "internalportcfg": "0xffff",
    "maxdisks": "16",
    "support_bde_internal_10g": "no",
    "support_disk_compatibility": "no",
    "support_memory_compatibility": "no"
  },
  "ramdisk_copy": {}
}

The exact command of the tutorial gives the same error

./rploader.sh build broadwellnk-7.1.0-42661

Any idea? Thanks

Pocopico changed the command about a month ago to reflect the model instead of the platform

./rploader.sh build ds3622xs+-7.1.0-42661

unlikely · December 7, 2022

Some progress in my first attempt to build under Hyper-V virtual machine, but sill far.

VM is configured with one virtual disk with TCRP and two physical disks directly attached.

Build process seems successful, but at reboot I can only boot again in Tiny Core Image Build.

Should'nt I see a boot menu with RedPill options after build/reboot?

Does I miss some step after ./rploader.sh build ds3622xsp-7.1.1-42962 and exitcheck.sh reboot ?

Latest build messages:

[#] Generating GRUB config... [OK]
[#] Creating loader image at loader.img... Killed

Full build log:

tc@box:~$ ./rploader.sh build ds3622xsp-7.1.1-42962
bspatch does not exist, bringing over from repo
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 10232  100 10232    0     0  18206      0 --:--:-- --:--:-- --:--:-- 18174
Rploader Version : 0.9.3.0
Loader source : https://github.com/pocopico/redpill-load.git Loader Branch : develop
Redpill module source : https://github.com/pocopico/redpill-lkm.git : Redpill module branch : master
Extensions :   redpill-misc
Extensions URL : "https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/rpext-index.json"
TOOLKIT_URL : https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.broadwellnk-7.0.dev.txz/download
TOOLKIT_SHA : 0d9edca67d9e7e14c2529bbb58341b623936124d5264f71f1e4acbacf3ea202d
SYNOKERNEL_URL : https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/25426branch/broadwellnk-source/linux-4.4.x.txz/download
SYNOKERNEL_SHA : d3e85eb80f16a83244fcae6016ab6783cd8ac55e3af2b4240455261396e1e1be
COMPILE_METHOD : toolkit_dev
TARGET_PLATFORM       : ds3622xsp
TARGET_VERSION    : 7.1.1
TARGET_REVISION : 42962
REDPILL_LKM_MAKE_TARGET : dev-v7
KERNEL_MAJOR : 4
MODULE_ALIAS_FILE :  modules.alias.4.json
SYNOMODEL : ds3622xsp_42962
MODEL : DS3622xs+
Local Cache Folder : /mnt/sda3/auxfiles
DATE Internet : 07122022 Local : 07122022
Checking Internet Access -> OK
Checking if a newer version exists on the main repo -> Version is current
Cloning into 'redpill-lkm'...
remote: Enumerating objects: 1545, done.
remote: Counting objects: 100% (617/617), done.
remote: Compressing objects: 100% (234/234), done.
remote: Total 1545 (delta 406), reused 523 (delta 370), pack-reused 928
Receiving objects: 100% (1545/1545), 5.78 MiB | 2.15 MiB/s, done.
Resolving deltas: 100% (969/969), done.
Cloning into 'redpill-load'...
remote: Enumerating objects: 2983, done.
remote: Counting objects: 100% (465/465), done.
remote: Compressing objects: 100% (223/223), done.
remote: Total 2983 (delta 239), reused 425 (delta 219), pack-reused 2518
Receiving objects: 100% (2983/2983), 118.51 MiB | 2.13 MiB/s, done.
Resolving deltas: 100% (1461/1461), done.
No extra build option or static specified, using default <static>
Using static compiled redpill extension
Removing any old redpill.ko modules
Looking for redpill for : ds3622xsp_42962
Getting file https://raw.githubusercontent.com/pocopico/rp-ext/master/redpillprod/releases/redpill-4.4.180plus-broadwellnk.tgz
Extracting module
Getting file https://raw.githubusercontent.com/pocopico/rp-ext/master/redpillprod/src/check-redpill.sh
Got redpill-linux-v4.4.180+.ko
Testing modules.alias.4.json -> File OK
------------------------------------------------------------------------------------------------
It looks that you will need the following modules :


------------------------------------------------------------------------------------------------
Starting loader creation
Found tinycore cache folder, linking to home/tc/custom-module
Checking user_config.json : Done
Entering redpill-load directory
Removing bundled exts directories
Cache directory OK
Found build request for revision greater than 42218
Getting required extraction tool
------------------------------------------------------------------
Checking tinycore cache folder
Found tinycore cache folder, linking to home/tc/custom-module
Creating temp folder /tmp/synoesp
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  345M  100  345M    0     0  2171k      0  0:02:42  0:02:42 --:--:-- 2257k
Entering synoesp
extract rd.gz
finish
cpio: dev/console: Cannot mknod: Operation not permitted
cpio: dev/net/tun: Cannot mknod: Operation not permitted
42506 blocks
extract rd
mkdir: cannot create directory '/mnt/sda3/auxfiles': File exists
Copying required files to local cache folder for future use
Copying usr/lib/libcurl.so.4 to /mnt/sda3/auxfiles
Copying usr/lib/libmbedcrypto.so.5 to /mnt/sda3/auxfiles
Copying usr/lib/libmbedtls.so.13 to /mnt/sda3/auxfiles
Copying usr/lib/libmbedx509.so.1 to /mnt/sda3/auxfiles
Copying usr/lib/libmsgpackc.so.2 to /mnt/sda3/auxfiles
Copying usr/lib/libsodium.so to /mnt/sda3/auxfiles
Copying usr/lib/libsynocodesign-ng-virtual-junior-wins.so.7 to /mnt/sda3/auxfiles
Copying usr/syno/bin/scemd to /mnt/sda3/auxfiles
Copying required libraries to local lib directory
Linking lib to lib64
Copying executable
Removing temp folder /tmp/synoesp
Checking if tools is accessible
/bin/syno_extract_system_patch: /usr/local/lib/libcurl.so.4: no version information available (required by /bin/syno_extract_system_patch)
Copyright (c) 2003-2021 Synology Inc. All rights reserved.

/bin/syno_extract_system_patch PATCH_PATH DEST_PATH
Executed succesfully
Creating temp folder /tmp/pat
Checking for cached pat file
Found tinycore cache folder, linking to home/tc/custom-module
Could not find pat file locally cached
Configdir : /home/tc/redpill-load/config/DS3622xs+/7.1.1-42962
Configfile: /home/tc/redpill-load/config/DS3622xs+/7.1.1-42962/config.json
Pat URL : https://global.download.synology.com/download/DSM/release/7.1.1/42962/DSM_DS3622xs%2B_42962.pat
Downloading pat file from URL : https://global.download.synology.com/download/DSM/release/7.1.1/42962/DSM_DS3622xs%2B_42962.pat
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  346M  100  346M    0     0  2206k      0  0:02:40  0:02:40 --:--:-- 2561k
File //mnt/sda3/auxfiles/ds3622xsp_42962.pat, is  encrypted
File //mnt/sda3/auxfiles/ds3622xsp_42962.pat, has been cached but its encrypted, re-running decrypting process
Checking for cached pat file
Found tinycore cache folder, linking to home/tc/custom-module
Found locally cached pat file /home/tc/custom-module/ds3622xsp_42962.pat
File /home/tc/custom-module/ds3622xsp_42962.pat, is  encrypted
Extracting encrypted pat file : /home/tc/custom-module/ds3622xsp_42962.pat to /tmp/pat
/bin/syno_extract_system_patch: /usr/local/lib/libcurl.so.4: no version information available (required by /bin/syno_extract_system_patch)
./rploader.sh: line 439: 49901 Killed                  sudo /bin/syno_extract_system_patch ${patfile} ${temp_pat_folder}
extract latest pat
Creating unecrypted pat file ds3622xsp_42962.pat to /home/tc/redpill-load/cache folder
./VERSION
Pat file  sha256sum is : f716fd4aeb2cbd23eed1260d03fd1907a32ecd9d3aa8be4b90562fc9a116dddc
Checking config file existence -> OK
Editing config file -> Verifying config file -> OK !
Clearing temp folders
Processing add_extensions entries found on custom_config.json file :   redpill-misc
Adding extension "https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/rpext-index.json"
[#] Checking runtime for required tools... [OK]
[#] Adding new extension from https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/rpext-index.json...
[#] Downloading remote file https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/rpext-index.json to /home/tc/redpill-load/custom/extensions/_new_ext_index.tmp_json
################################################################################################################################### 100.0%
[OK]
[#] ========================================== redpill-misc ==========================================
[#] Extension name: Misc shell
[#] Description: Misc shell
[#] To get help visit: https://github.com/pocopico/redpill-load/raw/develop/redpill-misc
[#] Extension preparer/packer: https://github.com/pocopico/redpill-load/raw/develop/redpill-misc
[#] Software author: https://github.com/pocopico/redpill-load/raw/develop/redpill-misc
[#] Update URL: https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/rpext-index.json
[#] Platforms supported: ds1621p_42218 ds1621p_42951 ds918p_41890 dva3221_42661 ds3617xs_42621 ds3617xs_42218 ds920p_42661 dva3221_42962 ds918p_42661 ds3622xsp_42962 ds3617xs_42951 ds920p_42962 ds1621p_42661 ds923p_42962 dva1622_42951 ds918p_25556 dva3221_42218 ds3615xs_42661 dva3221_42951 ds3622xsp_42661 ds2422p_42661 ds3622xsp_42218 ds2422p_42962 rs4021xsp_42621 dva1622_42962 sa6400_42962 ds2422p_42218 rs4021xsp_42962 dva3221_42621 ds3615xs_42962 ds3617xs_42962 ds3615xs_41222 ds920p_42951 rs4021xsp_42218 ds918p_42621 ds3617xs_42661 ds3615xs_25556 ds920p_42218 rs4021xsp_42951 ds920p_42621 ds918p_42962 ds3615xs_42951 ds3622xsp_42951 dva1622_42661 ds918p_42218 ds1621p_42621 ds3615xs_42621 ds3615xs_42218 ds1621p_42962 ds3622xsp_42621 rs4021xsp_42661
[#] =======================================================================================

Updating extension : redpill-misc contents for model : ds3622xsp_42962
[#] Checking runtime for required tools... [OK]
[#] Updating ds3622xsp_42962 platforms extensions...
[#] Downloading remote file https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/recipes/universal.json to /home/tc/redpill-load/custom/extensions/_ext_new_rcp.tmp_json
################################################################################################################################### 100.0%

[#] Filling-in newly downloaded recipe for extension redpill-misc platform ds3622xsp_42962
[#] Downloading remote file https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/releases/install.sh to /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42962/install.sh
################################################################################################################################### 100.0%
[#] Verifying /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42962/install.sh file...  [OK]
[#] Downloading remote file https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/releases/install-all.sh to /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42962/install-all.sh
################################################################################################################################### 100.0%
[#] Verifying /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42962/install-all.sh file...  [OK]
[#] Downloading remote file https://github.com/tsl0922/ttyd/releases/download/1.6.3/ttyd.x86_64 to /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42962/ttyd
################################################################################################################################### 100.0%
[#] Verifying /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42962/ttyd file...  [OK]
[#] Downloading remote file https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/releases/install_rd.sh to /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42962/install_rd.sh
################################################################################################################################### 100.0%
[#] Verifying /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42962/install_rd.sh file...  [OK]
[#] Downloading remote file https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/releases/lrzsz.tar.gz to /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42962/lrzsz.tar.gz
################################################################################################################################### 100.0%
[#] Verifying /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42962/lrzsz.tar.gz file...  [OK]
[#] Unpacking files from /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42962/lrzsz.tar.gz to /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42962/...  [OK]
[#] Successfully processed recipe for extension redpill-misc platform ds3622xsp_42962
[#] Unpacking files from /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42962/lrzsz.tar.gz to /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42962/...  [OK]
[#] Checking runtime for required tools... [OK]
[#] Updating extensions...

[#] Checking runtime for required tools... [OK]
[#] Adding new extension from https://github.com/pocopico/rp-ext/raw/main/redpill-boot-wait/rpext-index.json...
[#] Downloading remote file https://github.com/pocopico/rp-ext/raw/main/redpill-boot-wait/rpext-index.json to /home/tc/redpill-load/custom/extensions/_new_ext_index.tmp_json
################################################################################################################################### 100.0%
[OK]
[#] ========================================== redpill-boot-wait ==========================================
[#] Extension name: RedPill Bootwait
[#] Description: Simple extension which stops the execution early waiting for the boot device to appear
[#] To get help visit: https://github.com/pocopico/rp-ext/redpill-boot-wait
[#] Extension preparer/packer: https://github.com/pocopico/rp-ext/tree/main/redpill-boot-wait
[#] Update URL: https://raw.githubusercontent.com/pocopico/rp-ext/master/redpill-boot-wait/rpext-index.json
[#] Platforms supported: ds1621p_42218 ds1621p_42951 ds918p_41890 dva3221_42661 ds3617xs_42621 ds3617xs_42218 ds920p_42661 dva3221_42962 ds918p_42661 ds3622xsp_42962 ds3617xs_42951 ds920p_42962 ds1621p_42661 ds923p_42962 dva1622_42951 ds918p_25556 dva3221_42218 ds3615xs_42661 dva3221_42951 ds3622xsp_42661 ds2422p_42661 ds3622xsp_42218 ds2422p_42962 rs4021xsp_42621 dva1622_42962 ds2422p_42218 rs4021xsp_42962 dva3221_42621 ds3615xs_42962 ds3617xs_42962 ds3615xs_41222 ds920p_42951 rs4021xsp_42218 ds2422p_42951 ds918p_42621 ds3617xs_42661 ds3615xs_25556 ds920p_42218 rs4021xsp_42951 ds920p_42621 ds918p_42962 ds3615xs_42951 ds3622xsp_42951 ds920p_42550 dva1622_42661 ds918p_42218 ds2422p_42621 ds1621p_42621 ds3615xs_42621 ds3615xs_42218 ds1621p_42962 ds3622xsp_42621 rs4021xsp_42661
[#] =======================================================================================

[#] Checking runtime for required tools... [OK]
[#] Updating redpill-boot-wait extension...
[#] Downloading remote file https://raw.githubusercontent.com/pocopico/rp-ext/master/redpill-boot-wait/rpext-index.json to /home/tc/redpill-load/custom/extensions/_new_ext_index.tmp_json
################################################################################################################################### 100.0%

[#] Extension redpill-boot-wait index is already up to date
[#] Updating redpill-misc extension...
[#] Downloading remote file https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/rpext-index.json to /home/tc/redpill-load/custom/extensions/_new_ext_index.tmp_json
################################################################################################################################### 100.0%

[#] Extension redpill-misc index is already up to date
[#] Updating redpill-misc extension... [OK]
[#] Checking runtime for required tools... [OK]
[#] Updating ds3622xsp_42962 platforms extensions...
[#] Downloading remote file https://github.com/pocopico/rp-ext/raw/main/redpill-boot-wait/recipes/universal.json to /home/tc/redpill-load/custom/extensions/_ext_new_rcp.tmp_json
################################################################################################################################### 100.0%

[#] Filling-in newly downloaded recipe for extension redpill-boot-wait platform ds3622xsp_42962
[#] Downloading remote file https://github.com/pocopico/rp-ext/raw/main/redpill-boot-wait/src/boot-wait.sh to /home/tc/redpill-load/custom/extensions/redpill-boot-wait/ds3622xsp_42962/boot-wait.sh
################################################################################################################################### 100.0%
[#] Verifying /home/tc/redpill-load/custom/extensions/redpill-boot-wait/ds3622xsp_42962/boot-wait.sh file... [OK]
[#] Successfully processed recipe for extension redpill-boot-wait platform ds3622xsp_42962
[#] Downloading remote file https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/recipes/universal.json to /home/tc/redpill-load/custom/extensions/_ext_new_rcp.tmp_json
################################################################################################################################### 100.0%
[#] Extension redpill-misc for ds3622xsp_42962 platform is already up to date
[#] Verifying /home/tc/redpill-load/custom/extensions/redpill-boot-wait/ds3622xsp_42962/boot-wait.sh file... [OK]
[#] Updating extensions... [OK]
[#] Verifying /home/tc/redpill-load/cache/ds3622xsp_42962.pat file... [OK]
[#] Unpacking /home/tc/redpill-load/cache/ds3622xsp_42962.pat file to /home/tc/redpill-load/build/1670415747/pat-ds3622xsp_42962-unpacked... [OK]
[#] Verifying /home/tc/redpill-load/build/1670415747/pat-ds3622xsp_42962-unpacked/zImage file... [OK]
[#] Patching /home/tc/redpill-load/build/1670415747/pat-ds3622xsp_42962-unpacked/zImage to /home/tc/redpill-load/build/1670415747/zImage-patched... [OK]
[#] Verifying /home/tc/redpill-load/build/1670415747/pat-ds3622xsp_42962-unpacked/rd.gz file... [OK]
[#] Unpacking /home/tc/redpill-load/build/1670415747/pat-ds3622xsp_42962-unpacked/rd.gz file to /home/tc/redpill-load/build/1670415747/rd-ds3622xsp_42962-unpacked... [OK]
[#] Apply patches to /home/tc/redpill-load/build/1670415747/rd-ds3622xsp_42962-unpacked... [OK]
[#] Patching config files in ramdisk... [OK]
[#] Adding OS config patching... [OK]
[#] Repacking ramdisk to /home/tc/redpill-load/build/1670415747/rd-patched-ds3622xsp_42962.gz... [OK]
[#] Bundling extensions... [#] Checking runtime for required tools... [OK]
[#] Dumping ds3622xsp_42962 platform extensions to /home/tc/redpill-load/build/1670415747/custom-initrd/exts... [OK]
[#] Packing custom ramdisk layer to /home/tc/redpill-load/build/1670415747/custom.gz... [OK]
[#] Generating GRUB config... [OK]
[#] Creating loader image at loader.img... Killed
tc@box:~$
tc@box:~$
tc@box:~$
tc@box:~$ exitcheck.sh reboot

Boot menu after build:

image.png.c2efedf590fdd74e949d10555484fb13.png

asheenlevrai · December 8, 2022

Hello

Could you please add information/guidelines about TCRP with friends? Or is it still considered alpha territory?

Tx

-a-

asheenlevrai · December 8, 2022

On 12/5/2022 at 9:48 PM, rojoone2 said:

Pocopico changed the command about a month ago to reflect the model instead of the platform

./rploader.sh build ds3622xs+-7.1.0-42661

Yup... I was confused at first too.

Maybe an edit of the OP would be useful @flyride

tomoki · December 12, 2022

may I know if anyone got a problem when you try to build the system via " ./rploader.sh build ds3622xsp-7.0.1-42218 "

when the code try to access Synology to download the pat file, my N54L will be halted.

Quote

downloading from https://global.download.synology.com/download/DSM/release/7.0.1/42218/DSM_DS3622xs+_42218.pat
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
5 345M 5 17.4M 0 0 9093k 0 0:00:38 0:00:01 0:00:37 9088k

full build log

Quote

login as: tc
tc@192.168.1.210's password:
( '>')
/) TC (\ Core is distributed with ABSOLUTELY NO WARRANTY.
(/-_--_-\) www.tinycorelinux.net

tc@box:~$ ./rploader.sh update now
Checking Internet Access -> OK
Checking if a newer version exists on the main repo -> Version is current
tc@box:~$ ./rploader.sh fullupgrade now
Performing a full TCRP upgrade
Warning some of your local files will be moved to /home/tc/old/xxxx.2022-Dec-12-06-55
Updating custom_config.json
Updating custom_config_jun.json
Updating global_config.json
Updating modules.alias.3.json.gz
Updating modules.alias.4.json.gz
Updating rpext-index.json
Updating user_config.json
Updating rploader.sh
Please make sure you are using the latest 1GB img before using backup option
Current /home/tc size is 16M , try to keep it less than 1GB as it might not fit into your image
Should i update the sdf with your current files [Yy/Nn]
y
Backing up home files to sdf : Backing up files to /mnt/sdf3//mydata.tgz
Done.

tc@box:~$ ./rploader.sh serialgen DS3622xs+
Serial Number for Model = 2150SQRPYVZ0H
Mac Address for Model DS3622xs+ = 00:11:32:A3:98:58
Should i update the user_config.json with these values ? [Yy/Nn]
y
tc@box:~$ ./rploader.sh identifyusb now
Found PNY USB SerialNumber: 07016B6AAE276A40
Vendor ID : 0x154b Product ID : 0x6008
Should i update the user_config.json with these values ? [Yy/Nn]
y
tc@box:~$ ./rploader.sh satamap now

Found "00:11.0 Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40)"
Detected 6 ports/5 drives. Override # of ports or ENTER to accept <6>

Computed settings:
SataPortMap=6
DiskIdxMap=00

Should i update the user_config.json with these values ? [Yy/Nn] y
Done.
tc@box:~$ ./rploader.sh build
Error : Number of arguments : 1, options build
Syntax error, You have to specify one of the existing platforms
ds1621p-7.0.1-42218
ds1621p-7.0.1-42218-JUN
ds1621p-7.1.0-42621
ds1621p-7.1.0-42661
ds1621p-7.1.1-42951
ds1621p-7.1.1-42962
ds2422p-7.0.1-42218
ds2422p-7.1.0-42661
ds2422p-7.1.1-42951
ds2422p-7.1.1-42962
ds3615xs-7.0.1-42218
ds3615xs-7.0.1-42218-JUN
ds3615xs-7.1.0-42621
ds3615xs-7.1.0-42661
ds3615xs-7.1.1-42951
ds3615xs-7.1.1-42962
ds3617xs-7.0.1-42218
ds3617xs-7.0.1-42218-JUN
ds3617xs-7.1.0-42621
ds3617xs-7.1.0-42661
ds3617xs-7.1.1-42951
ds3617xs-7.1.1-42962
ds3622xsp-7.0.1-42218
ds3622xsp-7.0.1-42218-JUN
ds3622xsp-7.1.0-42621
ds3622xsp-7.1.0-42661
ds3622xsp-7.1.1-42951
ds3622xsp-7.1.1-42962
ds918p-7.0-41890
ds918p-7.0.1-42218
ds918p-7.0.1-42218-JUN
ds918p-7.1.0-42621
ds918p-7.1.0-42661
ds918p-7.1.1-42951
ds918p-7.1.1-42962
ds920p-7.0.1-42218
ds920p-7.0.1-42218-JUN
ds920p-7.1.0-42621
ds920p-7.1.0-42661
ds920p-7.1.1-42951
ds920p-7.1.1-42962
dva1622-7.1.0-42661
dva1622-7.1.1-42951
dva1622-7.1.1-42962
dva3221-7.0.1-42218
dva3221-7.0.1-42218-JUN
dva3221-7.1.0-42621
dva3221-7.1.0-42661
dva3221-7.1.1-42951
dva3221-7.1.1-42962
rs4021xsp-7.1.0-42661
rs4021xsp-7.1.1-42962
tc@box:~$ ^C
tc@box:~$ ds3622xsp-7.0.1-42218
-sh: ds3622xsp-7.0.1-42218: not found
tc@box:~$ ./rploader.sh build ds3622xsp-7.0.1-42218
bspatch does not exist, bringing over from repo
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 10232 100 10232 0 0 32482 0 --:--:-- --:--:-- --:--:-- 32379
Rploader Version : 0.9.3.0
Loader source : https://github.com/pocopico/redpill-load.git Loader Branch : develop
Redpill module source : https://github.com/pocopico/redpill-lkm.git : Redpill module branch : master
Extensions : redpill-misc
Extensions URL : "https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/rpext-index.json"
TOOLKIT_URL : https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.broadwellnk-7.0.dev.txz/download
TOOLKIT_SHA : 0d9edca67d9e7e14c2529bbb58341b623936124d5264f71f1e4acbacf3ea202d
SYNOKERNEL_URL : https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/25426branch/broadwellnk-source/linux-4.4.x.txz/download
SYNOKERNEL_SHA : d3e85eb80f16a83244fcae6016ab6783cd8ac55e3af2b4240455261396e1e1be
COMPILE_METHOD : toolkit_dev
TARGET_PLATFORM : ds3622xsp
TARGET_VERSION : 7.0.1
TARGET_REVISION : 42218
REDPILL_LKM_MAKE_TARGET : dev-v7
KERNEL_MAJOR : 4
MODULE_ALIAS_FILE : modules.alias.4.json
SYNOMODEL : ds3622xsp_42218
MODEL : DS3622xs+
Local Cache Folder : /mnt/sdf3/auxfiles
DATE Internet : 12122022 Local : 12122022
Checking Internet Access -> OK
Checking if a newer version exists on the main repo -> Version is current
Cloning into 'redpill-lkm'...
remote: Enumerating objects: 1545, done.
remote: Counting objects: 100% (617/617), done.
remote: Compressing objects: 100% (234/234), done.
remote: Total 1545 (delta 406), reused 523 (delta 370), pack-reused 928
Receiving objects: 100% (1545/1545), 5.78 MiB | 8.15 MiB/s, done.
Resolving deltas: 100% (969/969), done.
Cloning into 'redpill-load'...
remote: Enumerating objects: 2983, done.
remote: Counting objects: 100% (465/465), done.
remote: Compressing objects: 100% (223/223), done.
remote: Total 2983 (delta 239), reused 425 (delta 219), pack-reused 2518
Receiving objects: 100% (2983/2983), 118.51 MiB | 5.88 MiB/s, done.
Resolving deltas: 100% (1464/1464), done.
No extra build option or static specified, using default <static>
Using static compiled redpill extension
Removing any old redpill.ko modules
Looking for redpill for : ds3622xsp_42218
Getting file https://raw.githubusercontent.com/pocopico/rp-ext/master/redpillprod/releases/redpill-4.4.180plus-broadwellnk.tgz
Extracting module
Getting file https://raw.githubusercontent.com/pocopico/rp-ext/master/redpillprod/src/check-redpill.sh
Got redpill-linux-v4.4.180+.ko
Testing modules.alias.4.json -> File OK
------------------------------------------------------------------------------------------------
It looks that you will need the following modules :

Found SATA Controller : pciid 1002d00004391 Required Extension : ahci
Searching for matching extension for ahci
Found VGA Controller : pciid 1002d00009712 Required Extension :
No matching extension
[#] Checking runtime for required tools... [OK]
[#] Adding new extension from https://raw.githubusercontent.com/pocopico/rp-ext/master/tg3/rpext-index.json...
[#] Downloading remote file https://raw.githubusercontent.com/pocopico/rp-ext/master/tg3/rpext-index.json to /home/tc/redpill-load/custom/extensions/_new_ext_index.tmp_json
######################################################################## 100.0%
[OK]
[#] ========================================== pocopico.tg3 ==========================================
[#] Extension name: tg3
[#] Description: Adds Broadcom Tigon3 ethernet driver Support
[#] To get help visit: <todo>
[#] Extension preparer/packer: https://github.com/pocopico/rp-ext/tree/main/tg3
[#] Software author: https://github.com/pocopico
[#] Update URL: https://raw.githubusercontent.com/pocopico/rp-ext/master/tg3/rpext-index.json
[#] Platforms supported: ds1621p_42218 ds1621p_42951 dva3221_42661 ds3617xs_42621 ds3617xs_42218 ds920p_42661 dva3221_42962 ds918p_42661 ds3622xsp_42962 ds3617xs_42951 dva1622_42218 dva1622_42621 ds920p_42962 ds1621p_42661 dva1622_42951 ds918p_25556 dva3221_42218 ds3615xs_42661 dva3221_42951 ds3622xsp_42661 ds2422p_42661 ds3622xsp_42218 ds2422p_42962 rs4021xsp_42621 dva1622_42962 ds2422p_42218 rs4021xsp_42962 dva3221_42621 ds3615xs_42962 ds3617xs_42962 ds920p_42951 rs4021xsp_42218 ds2422p_42951 endofmodel ds918p_42621 ds3617xs_42661 ds3615xs_25556 ds920p_42218 rs4021xsp_42951 ds920p_42621 ds918p_42962 ds3615xs_42951 ds3622xsp_42951 dva1622_42661 ds918p_42218 ds2422p_42621 ds1621p_42621 ds918p_42951 ds3615xs_42621 ds3615xs_42218 ds1621p_42962 ds3622xsp_42621 rs4021xsp_42661
[#] =======================================================================================

Found Ethernet Interface : pciid 14e4d0000165b Required Extension : tg3
Searching for matching extension for tg3
Found matching extension :
"https://raw.githubusercontent.com/pocopico/rp-ext/master/tg3/rpext-index.json"
------------------------------------------------------------------------------------------------
Starting loader creation
Found tinycore cache folder, linking to home/tc/custom-module
Checking user_config.json : Done
Entering redpill-load directory
Removing bundled exts directories
Cache directory OK
cp: cannot stat '/home/tc/custom-module/*42218*.pat': No such file or directory
Processing add_extensions entries found on custom_config.json file : redpill-misc
Adding extension "https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/rpext-index.json"
[#] Checking runtime for required tools... [OK]
[#] Adding new extension from https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/rpext-index.json...
[#] Downloading remote file https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/rpext-index.json to /home/tc/redpill-load/custom/extensions/_new_ext_index.tmp_json
######################################################################### 100.0%
[OK]
[#] ========================================== redpill-misc ==========================================
[#] Extension name: Misc shell
[#] Description: Misc shell
[#] To get help visit: https://github.com/pocopico/redpill-load/raw/develop/redpill-misc
[#] Extension preparer/packer: https://github.com/pocopico/redpill-load/raw/develop/redpill-misc
[#] Software author: https://github.com/pocopico/redpill-load/raw/develop/redpill-misc
[#] Update URL: https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/rpext-index.json
[#] Platforms supported: ds1621p_42218 ds1621p_42951 ds918p_41890 dva3221_42661 ds3617xs_42621 ds3617xs_42218 ds920p_42661 dva3221_42962 ds918p_42661 ds3622xsp_42962 ds3617xs_42951 ds920p_42962 ds1621p_42661 ds923p_42962 dva1622_42951 ds918p_25556 dva3221_42218 ds3615xs_42661 dva3221_42951 ds3622xsp_42661 ds2422p_42661 ds3622xsp_42218 ds2422p_42962 rs4021xsp_42621 dva1622_42962 sa6400_42962 ds2422p_42218 rs4021xsp_42962 dva3221_42621 ds3615xs_42962 ds3617xs_42962 ds3615xs_41222 ds920p_42951 rs4021xsp_42218 ds918p_42621 ds3617xs_42661 ds3615xs_25556 ds920p_42218 rs4021xsp_42951 ds920p_42621 ds918p_42962 ds3615xs_42951 ds3622xsp_42951 dva1622_42661 ds918p_42218 ds1621p_42621 ds3615xs_42621 ds3615xs_42218 ds1621p_42962 ds3622xsp_42621 rs4021xsp_42661
[#] =======================================================================================

Updating extension : redpill-misc contents for model : ds3622xsp_42218
[#] Checking runtime for required tools... [OK]
[#] Updating ds3622xsp_42218 platforms extensions...
[#] Downloading remote file https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/recipes/universal.json to /home/tc/redpill-load/custom/extensions/_ext_new_rcp.tmp_json
######################################################################### 100.0%

[#] Filling-in newly downloaded recipe for extension redpill-misc platform ds3622xsp_42218
[#] Downloading remote file https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/releases/install.sh to /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42218/install.sh
######################################################################### 100.0%
[#] Verifying /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42218/install.sh file... [OK]
[#] Downloading remote file https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/releases/install-all.sh to /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42218/install-all.sh
######################################################################### 100.0%
[#] Verifying /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42218/install-all.sh file... [OK]
[#] Downloading remote file https://github.com/tsl0922/ttyd/releases/download/1.6.3/ttyd.x86_64 to /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42218/ttyd
######################################################################### 100.0%
[#] Verifying /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42218/ttyd file... [OK]
[#] Downloading remote file https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/releases/install_rd.sh to /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42218/install_rd.sh
######################################################################### 100.0%
[#] Verifying /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42218/install_rd.sh file... [OK]
[#] Downloading remote file https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/releases/lrzsz.tar.gz to /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42218/lrzsz.tar.gz
######################################################################### 100.0%
[#] Verifying /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42218/lrzsz.tar.gz file... [OK]
[#] Unpacking files from /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42218/lrzsz.tar.gz to /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42218/... [OK]
[#] Successfully processed recipe for extension redpill-misc platform ds3622xsp_42218
[#] Unpacking files from /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42218/lrzsz.tar.gz to /home/tc/redpill-load/custom/extensions/redpill-misc/ds3622xsp_42218/... [OK]
[#] Checking runtime for required tools... [OK]
[#] Updating extensions...

[#] Checking runtime for required tools... [OK]
[#] Adding new extension from https://github.com/pocopico/rp-ext/raw/main/redpill-boot-wait/rpext-index.json...
[#] Downloading remote file https://github.com/pocopico/rp-ext/raw/main/redpill-boot-wait/rpext-index.json to /home/tc/redpill-load/custom/extensions/_new_ext_index.tmp_json
######################################################################### 100.0%
[OK]
[#] ========================================== redpill-boot-wait ==========================================
[#] Extension name: RedPill Bootwait
[#] Description: Simple extension which stops the execution early waiting for the boot device to appear
[#] To get help visit: https://github.com/pocopico/rp-ext/redpill-boot-wait
[#] Extension preparer/packer: https://github.com/pocopico/rp-ext/tree/main/redpill-boot-wait
[#] Update URL: https://raw.githubusercontent.com/pocopico/rp-ext/master/redpill-boot-wait/rpext-index.json
[#] Platforms supported: ds1621p_42218 ds1621p_42951 ds918p_41890 dva3221_42661 ds3617xs_42621 ds3617xs_42218 ds920p_42661 dva3221_42962 ds918p_42661 ds3622xsp_42962 ds3617xs_42951 ds920p_42962 ds1621p_42661 ds923p_42962 dva1622_42951 ds918p_25556 dva3221_42218 ds3615xs_42661 dva3221_42951 ds3622xsp_42661 ds2422p_42661 ds3622xsp_42218 ds2422p_42962 rs4021xsp_42621 dva1622_42962 ds2422p_42218 rs4021xsp_42962 dva3221_42621 ds3615xs_42962 ds3617xs_42962 ds3615xs_41222 ds920p_42951 rs4021xsp_42218 ds2422p_42951 ds918p_42621 ds3617xs_42661 ds3615xs_25556 ds920p_42218 rs4021xsp_42951 ds920p_42621 ds918p_42962 ds3615xs_42951 ds3622xsp_42951 ds920p_42550 dva1622_42661 ds918p_42218 ds2422p_42621 ds1621p_42621 ds3615xs_42621 ds3615xs_42218 ds1621p_42962 ds3622xsp_42621 rs4021xsp_42661
[#] =======================================================================================

[#] Checking runtime for required tools... [OK]
[#] Updating pocopico.tg3 extension...
[#] Downloading remote file https://raw.githubusercontent.com/pocopico/rp-ext/master/tg3/rpext-index.json to /home/tc/redpill-load/custom/extensions/_new_ext_index.tmp_json
######################################################################### 100.0%

[#] Extension pocopico.tg3 index is already up to date
[#] Updating redpill-boot-wait extension...
[#] Downloading remote file https://raw.githubusercontent.com/pocopico/rp-ext/master/redpill-boot-wait/rpext-index.json to /home/tc/redpill-load/custom/extensions/_new_ext_index.tmp_json
######################################################################### 100.0%

[#] Extension redpill-boot-wait index is already up to date
[#] Updating redpill-misc extension...
[#] Downloading remote file https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/rpext-index.json to /home/tc/redpill-load/custom/extensions/_new_ext_index.tmp_json
######################################################################### 100.0%

[#] Extension redpill-misc index is already up to date
[#] Updating redpill-misc extension... [OK]
[#] Checking runtime for required tools... [OK]
[#] Updating ds3622xsp_42218 platforms extensions...
[#] Downloading remote file https://raw.githubusercontent.com/pocopico/rp-ext/master/tg3/releases/ds3622xsp_42218.json to /home/tc/redpill-load/custom/extensions/_ext_new_rcp.tmp_json
######################################################################### 100.0%

[#] Filling-in newly downloaded recipe for extension pocopico.tg3 platform ds3622xsp_42218
[#] Downloading remote file https://raw.githubusercontent.com/pocopico/rp-ext/master/tg3/releases/tg3-4.4.180plus-broadwellnk.tgz to /home/tc/redpill-load/custom/extensions/pocopico.tg3/ds3622xsp_42218/tg3-4.4.180plus-broadwellnk.tgz
######################################################################### 100.0%
[#] Verifying /home/tc/redpill-load/custom/extensions/pocopico.tg3/ds3622xsp_42218/tg3-4.4.180plus-broadwellnk.tgz file... [OK]
[#] Unpacking files from /home/tc/redpill-load/custom/extensions/pocopico.tg3/ds3622xsp_42218/tg3-4.4.180plus-broadwellnk.tgz to /home/tc/redpill-load/custom/extensions/pocopico.tg3/ds3622xsp_42218/... [OK]
[#] Downloading remote file https://raw.githubusercontent.com/pocopico/rp-ext/master/tg3/src/check-tg3.sh to /home/tc/redpill-load/custom/extensions/pocopico.tg3/ds3622xsp_42218/check-tg3.sh
######################################################################### 100.0%
[#] Verifying /home/tc/redpill-load/custom/extensions/pocopico.tg3/ds3622xsp_42218/check-tg3.sh file... [OK]
[#] Successfully processed recipe for extension pocopico.tg3 platform ds3622xsp_42218
[#] Downloading remote file https://github.com/pocopico/rp-ext/raw/main/redpill-boot-wait/recipes/universal.json to /home/tc/redpill-load/custom/extensions/_ext_new_rcp.tmp_json
######################################################################### 100.0%
[#] Filling-in newly downloaded recipe for extension redpill-boot-wait platform ds3622xsp_42218
[#] Downloading remote file https://github.com/pocopico/rp-ext/raw/main/redpill-boot-wait/src/boot-wait.sh to /home/tc/redpill-load/custom/extensions/redpill-boot-wait/ds3622xsp_42218/boot-wait.sh
######################################################################### 100.0%
[#] Verifying /home/tc/redpill-load/custom/extensions/redpill-boot-wait/ds3622xsp_42218/boot-wait.sh file... [OK]
[#] Successfully processed recipe for extension redpill-boot-wait platform ds3622xsp_42218
[#] Downloading remote file https://github.com/pocopico/redpill-load/raw/develop/redpill-misc/recipes/universal.json to /home/tc/redpill-load/custom/extensions/_ext_new_rcp.tmp_json
######################################################################### 100.0%
[#] Extension redpill-misc for ds3622xsp_42218 platform is already up to date
[#] Verifying /home/tc/redpill-load/custom/extensions/redpill-boot-wait/ds3622xsp_42218/boot-wait.sh file... [OK]
[#] Updating extensions... [OK]
[#] PAT file /home/tc/redpill-load/cache/ds3622xsp_42218.pat not found - downloading from https://global.download.synology.com/download/DSM/release/7.0.1/42218/DSM_DS3622xs+_42218.pat
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
5 345M 5 17.4M 0 0 9093k 0 0:00:38 0:00:01 0:00:37 9088k

unlikely · December 23, 2022

another small progress in my attempt but still stuck.

I understand that the "drivers" for my network card are missing.

Can I manually add? Should I try another platform to see if something change?

Or my hardware is definitely not supported by TCRP?

------------------------------------------------------------------------------------------------
It looks that you will need the following modules :


Found IDE Controller : pciid 8086d00007111  Required Extension : ata_piix
ata_piix
Searching for matching extension for ata_piix
Found VGA Controller : pciid 1414d00005353  Required Extension :
No matching extension
Found Ethernet Interface : pciid 1011d00000009 Required Extension :
No matching extension
------------------------------------------------------------------------------------------------

Edited December 23, 2022 by unlikely

HansDampfHH · December 26, 2022

Great work. everything works as described. However, there is a deviation. In the Info-Center of my Synology DS3622 i have a different Mac address than in the grub.cfg? I would have expected them to be the same.

I wanted to change the serial number and mac address to register a surveillance license. But if the mac address is not taken over correctly, it is probably difficult.

EDIT:

Nevermind, changed serial and mac in grub.cfg and everything is fine. Mac in Info-Center does not changed but i could register my licence.

Edited December 26, 2022 by HansDampfHH

droiduser22 · December 31, 2022

On 5/23/2022 at 2:47 AM, flyride said:
Loader Information and Background

RedPill is the core technology that enables DSM 7.x to run on non-Synology hardware. This post is intended to serve as a definitive tutorial/reference for configuring @pocopico's TinyCore RedPill (TCRP) loader. It explains how to install TCRP on baremetal, i.e. with DSM as the only operating system on your NAS hardware. A tutorial to install TCRP using the ESXi hypervisor is located here. There are other hypervisor tutorials in the Tutorials and Guides forum.

TCRP uses a two step-process. First, a Linux OS (TinyCore) boots and evaluates the NAS hardware configuration. Therefore, it is best to have the hardware you plan to use (disk controllers and network cards in particular) installed prior to starting the TCRP setup.

Then, an individualized loader (RedPill) is created. This loader is used to install and run DSM. After that, you can switch between starting DSM with RedPill, and booting back into TinyCore to adjust and rebuild the loader as needed.

Basic Linux command line skills are needed to complete the installation. The tutorial provides examples of the commands that are needed, but exact syntax and capitalization are critical. If unfamiliar, research and review the following minimal list of commands:

ls show the files in the current directory
cat <file> show the contents of the specified file
pwd show the current directory name
cd <directory path> change to the specified directory (same rules as Windows, except with forward slashes instead of backslashes). With no argument, it returns to the “home” TCRP directory
vi <file> a file editor, for manual editing of configuration files if required

Ongoing Development

This tutorial is maintained for consistency with the pocopico stable repository. Since TCRP is completely open-sourced, anyone can fork their own repo and contribute to development, and pocopico now maintains a separate development repo. As the best features and ideas are fully vetted and tested, they may be incorporated into the stable repo over time.

If you use a repo, script or shell other than the pocopico stable repo, the loader may behave quite differently and the instructions and troubleshooting steps in this tutorial might no longer apply. In an open-source community, you can use any development resource you want, but you add the additional responsibility of understanding, vetting and testing that code on your system.

Migration

Reveal hidden contents

DSM 6.x (with Jun’s loader) can be migrated to DSM 7.x using TCRP.

Do not attempt to upgrade from 6.x to 7.x using the Control Panel.

Complete the following tasks prior to migration:

Read through this reference thoroughly

Remove the 6.x loader USB and array disks (making sure to mark their order)

Build a TCRP loader on a new USB to practice and confirm the build process
(with all the same NAS hardware that will be used for the upgrade)

Trial install DSM 7.x to a test HDD/SDD

Verify DSM is working perfectly with all the NAS hardware

Remove the test USB and HDD/SDD, and restore the 6.x loader USB and array disks

VERIFY BACKUP of all data saved elsewhere before attempting an in-place upgrade

The actual migration process is simple:

Remove any existing SSD cache configuration (strongly recommended)

Shut down the NAS

Replace the existing 6.x USB loader with the TCRP 7.x USB loader from the process above

Boot the NAS and complete the DSM Migration when prompted

Restore SSD cache configuration as desired

NOTE: Depending on which DSM version was previously installed, the migration process may override the manual option for DSM updates and set it to automatic. Restore the manual option from Control Panel as soon as possible - it might be necessary to shutdown the Internet connection until that is complete.

Step 1. Choose a DSM Platform/Architecture

Evaluate your intended NAS hardware and your the intended use of DSM, and select a platform that best meets your needs. Reference information here: https://xpenology.com/forum/topic/61634-dsm-7x-loaders-and-platforms/

Write down the selected platform (e.g. DS918+), the corresponding architecture (e.g. apollolake) and whether the platform uses SataPortMap/DiskIdxMap or Device Tree for slot mapping. This information will be needed later.

Now, make sure the NAS hardware is compatible, and prepare it correctly:

x86-64-compatible CPU with two cores or more

Each platform have maximum threads support! Any threads in excess will be ignored

For certain platforms, Intel CPUs must be 4th generation “Haswell” or newer with FMA3 instruction set
The corresponding AMD CPU architecture is “Piledriver” or newer

AMD-based systems may require deactivation of the C1E option in the BIOS

2GB of RAM or more

2GB or larger USB flash drive

Configure the BIOS to boot from the USB flash drive ONLY

SATA disk controllers are preferred, but SCSI/SAS are compatible

IMPORTANT: All SATA controllers must be configured to AHCI mode

SATA controllers with port multipliers are not compatible

ATA controllers are not compatible (disable embedded ATA in BIOS if possible)

At least one SATA/SCSI/SAS drive (HDD or SSD), minimum size 21GB

IMPORTANT: Enable SATA port hotplug on each disk port, if hotplug is supported by the BIOS/controller

IMPORTANT: Disable M.2 SATA ports that are not in use, if supported by the BIOS/controller

NVMe drives are not usable except as dedicated cache devices

Host Bus Adapters are not currently compatible with Device Tree platforms

Install any NVMe drives intended as cache devices

On Device Tree platforms, NVMe drives must be installed prior to loader installation in order for them to be recognized

Step 2. Download TCRP and Write Image to the USB Flash Drive

The latest pocopico stable loader code is always linked here: https://xpenology.com/forum/topic/7848-links-to-loaders/

Download the tinycore-redpill 7.x loader and save it to your personal computer. Then, open it with a zip manager to show the boot images:

tinycore-redpill.vX.X.X.img.gz                    (for BIOS/CSM/Legacy boot from USB flash drive)
tinycore-redpill-uefi.vX.X.X.img.gz            (for UEFI/EFI boot from USB flash drive)
tinycore-redpill.vX.X.X.vmdk.gz                 (for virtual machine SATABOOT from disk image)

Select the boot image that matches the boot capability of the NAS motherboard. If unsure, choose BIOS/CSM/Legacy boot. Save the gzip file to your personal computer, then open it with a zip archive manager and save the uncompressed version.

Write the uncompressed image to the USB flash drive using Win32DiskImager or other appropriate tool.

The USB flash drive is used to store TinyCore and the RedPill loader that it generates. It is a permanent component of an operational XPEnology system. Do not remove it, even after the DSM installation is complete and the NAS is fully up and running.

Step 3. Boot into TinyCore and Complete Pre-Configuration Updates

Start your NAS with the USB flash drive installed and TinyCore will boot. Then, launch a command-line session with either of these methods:

Click the Terminal icon at the bottom right of the TinyCore desktop to launch a console window

Use a ssh client (e.g. PuTTY) on your computer to connect a network-based console

Consult your DHCP server/router for the IP address assignment (TinyCore's host name is "box")

Login credentials: tc/P@ssw0rd

When the Linux command line prompt ($) is displayed, update the TCRP script
./rploader.sh update
Checking Internet Access -> OK
Checking if a newer version exists -> There is a newer version on the repo should we use that ? [yY/nN] Y
OK, updating, please re-run after updating
Updating tinycore loader with latest updates
Backing up files to /mnt/sda3//mydata.tgz
Then, update the TCRP support files
./rploader.sh fullupgrade
<downloads snipped>
Current /home/tc size is 114M , try to keep it less than 1GB as it might not fit into your image
Should i update the sda with your current files [Yy/Nn] Y
Backing up home files to sda : Backing up files to /mnt/sda3//mydata.tgz
Finally, choose a DSM release number

Each DSM build as provided by Synology has a release number. You can display the combinations of platforms and releases supported by TCRP by just running the script with no arguments
./rploader.sh
<command help snipped>
Available platform versions:
----------------------------------------------------------------------------------------
apollolake-7.0-41890
apollolake-7.0.1-42218
apollolake-7.1.0-42661
broadwell-7.0.1-42218
broadwell-7.1.0-42661
broadwellnk-7.0.1-42218
broadwellnk-7.1.0-42661
bromolow-7.0.1-42218
bromolow-7.1.0-42661
denverton-7.0.1-42218
denverton-7.1.0-42661
geminilake-7.0.1-42218
geminilake-7.1.0-42661
v1000-7.0.1-42218
v1000-7.1.0-42661
Step 4. Configure System-Specific Parameters

Custom system parameters are stored in the user_config.json file. This can be manually edited, or TCRP can help determine appropriate values for the hardware.
USB flash drive VID/PID: TCRP can query the USB flash drive for the hardware vid/pid values that DSM uses to identify the loader during bootup
./rploader.sh identifyusb
Found: Superdisk Flash SerialNumber: 123456
Vendor ID: 0x1234 Product ID: 0x0001
Should i update the user_config.json with these values ? [Yy/Nn] Y
Serial number/MAC: TCRP can automatically generate a serial number for the platform selected in step 1. Additionally, it will generate a random MAC address for the NAS network card. If you prefer to use the actual hardware MAC address instead, append "realmac" to the command.

Example 1: random MAC address
./rploader.sh serialgen DS3622xs+
Serial Number for Model : 20C0SQRLR47QM
Mac Address for Model DS3622xs+ : 00:11:32:80:B2:36
Should i update the user_config.json with these values ? [Yy/Nn] Y
Example 2: real MAC address
./rploader.sh serialgen DS3622xs+ realmac
Serial Number for Model : 2150SQRGS7N5T
Mac Address for Model DS3622xs+ : 00:11:32:57:3A:9B
Real Mac Address : 00:0C:24:62:3E:3D
Notice : realmac option is requested, real mac will be used
Should i update the user_config.json with these values ? [Yy/Nn] Y
Drive Slot Mapping: TCRP can try to determine how to map the NAS disk controller ports to DSM slots. If the chosen platform uses SataPortMap/DiskIdxMap for port mapping, the command below will do this. If it uses Device Tree for slot mapping, the command may be skipped, as the Device Tree is configured automatically during the loader build.
./rploader.sh satamap
Found "02:02.0 SATA AHCI controller"
Detected 4 ports/2 drives. Override # of ports or ENTER to accept: <4>

Recommended settings:
SataPortMap=4
DiskIdxMap=00
  
Should I update the user_config with these values ? [Yy/Nn] Y
If the port count is not what you expect, it may be due to the motherboard design servicing physical ports with multiple controllers, or because of M.2 SATA slot support. If necessary, the port count can be overridden with whatever you like. NOTE: If you see a WARNING message, it is certain that either some of your drives are inaccessible or the DSM install will encounter problems. Evaluate and investigate the issue. The satamap command can be rerun as many times as needed to understand the system.
Manual Review: With prior loaders (such as Jun's), the configuration of these parameters was completely manual. There is no single setup that works for all hardware. Even after using the tools above, please review and verify the parameters, understand what they do, and manually edit if needed.

Whatever changes rploader.sh makes to the user_config.json file can be reviewed by displaying the file contents
cat user_config.json
and overridden by editing the file
vi user_config.json
You can also add a simpler editor, nano
tce-load -iw nano
nano user_config.json
And there is also a graphical editor accessible from the TinyCore desktop
Step 5. Optional: Manually Add Driver Extensions

While TCRP can automatically add drivers based on the detected NAS hardware, it isn’t foolproof. You might want to build a loader for a device you don’t actually have yet. And there are features that are "opt-in" only. So, a process exists to manually add drivers and other functionality. Extensions are stored in repositories hosted on the web. All the extensions in the main repository are viewable here: https://github.com/pocopico/rp-ext

To list all the extensions recommended by TCRP's hardware detection algorithm, use
./rploader.sh listmods <architecture>-<version>-<DSMreleasenumber>
./rploader.sh listmods apollolake-7.1.0-42661
To add a specific extension, choose from the list and reference the architecture from Step 1.
./rploader.sh ext <architecture>-<version>-<DSMreleasenumber> <extensionurl>
./rploader.sh ext apollolake-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/redpill-acpid/rpext-index.json
./rploader.sh ext denverton-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/v9fs/rpext-index.json
The examples illustrate adding ACPI and VIRTIO support. These are often chosen enhancements to a basic installation.

Step 6. Build the Loader

When all preparation steps are complete, build the loader using the command structure
./rploader.sh build <architecture>-<version>-<DSMreleasenumber>

Example #1: DS3622xs+, auto detect hardware
./rploader.sh build broadwellnk-7.1.0-42661
Example #2: DS918+, use preselected drivers
./rploader.sh build apollolake-7.1.0-42661 manual
TCRP will download resources from the Internet to complete the complex process of the loader build. When finished, it will write it to the USB flash drive and add new items to the GRUB boot menu. Review the output for any errors and make corrections if necessary.

Step 7. Optional Backup Tasks

Save the TinyCore configuration state as the default, so that the next boot of TInyCore starts with all your settings
./rploader.sh backup
Back up the generated RedPill loader partition to available space on the USB flash drive
./rploader.sh backuploader
Step 8: Restart and Boot DSM Using the Grub USB Option

Cleanly shutdown and reboot with the TinyCore command
exitcheck.sh reboot
First, the GRUB Menu is displayed. If necessary, use the arrow keys to ensure that USB is selected and press ENTER.

The loader will show some initialization information and silently boot DSM. Nothing else will be displayed unless a serial console is attached (see the Troubleshooting section below). Wait a few minutes, then launch either https://find.synology.com or the Synology Assistant desktop utility. If the loader is working properly, a new "SynologyNAS" will be displayed as Not installed (for a new build) or the name of your existing Migratable NAS (if upgrading from a previous version).

Use your browser to connect to the NAS.

If "Something went wrong" is displayed, jump to the Basic Troubleshooting section below.

Otherwise, browse to the Synology Download Center and download the DSM install PAT file that matches the platform and release number specified in the loader build. Do not use the PAT file stored in TinyCore. It has modifications that are incompatible with DSM installation. However, its name may help identify the correct PAT file to download below.

There can be several files that appear to be candidates. PAT files marked VirtualDSM will not work. Also there can be patch PAT files with the same numbering. These will not work and will usually be smaller than 50MB. The correct PAT file is 300MB or larger.

Once the correct DSM PAT file is saved to your personal computer, upload it to the NAS. Follow the prompts to complete the installation.

FOR UPGRADES ONLY: If Synology Assistant shows Not installed, or if prompted to erase the disks during the upgrade, STOP! Some or all of your array disks are not visible to DSM. This must be resolved via troubleshooting and reconfiguration before installing DSM 7.x.

IMPORTANT: During the install, always select DSM manual updates. If a new install completes normally, but then fails after the reboot, it may be that DSM has attempted to auto-update itself with incompatible code.

Basic Troubleshooting
Reveal hidden contents
Typical Problems:

If the DSM installation reports something went wrong/SATA ports disabled, or if WARNING: Bad port is returned by the TCRP configuration tools, there are three primary causes:

hotplug not enabled for all ports on controllers that support hotplug

ports supported by the chipset but omitted from the motherboard physical implementation

M.2 SATA-capable ports that have no hotplug option enabled

Consider these workarounds/solutions:

enable hotplug on all ports

install SATA drives on all ports (including M.2 SATA ports)

disable M.2 SATA ports in the BIOS (if the option exists)

reduce SataPortMap port count to exclude unimplemented or M.2 SATA ports
(this only works IF they are not the first ports on the controller)

install a different SATA controller and disable the onboard one

virtualize the DSM installation, possibly in concert with one of the above options

change the DSM platform to one that uses Device Tree (which can address only the good ports, leaving out the bad)

choose another motherboard which does not exhibit the causal issues

A loader or SATA controller configuration that disables valid ports in order to install DSM can be updated to enable those ports once the DSM installation is complete.

If the DSM installation reports that no drives are available, use the serial or TCRP console described below to help investigate the problem

If unable to locate the new SynologyNAS using Synology Assistant, either the loader has kernel panicked, or the network is not functioning (usually because of a missing or incompatible network driver, or no accessible DHCP server). The only way to verify the specific cause is to use a serial console.

Using the Serial Console for Troubleshooting

This involves configuring a physical serial port from the NAS hardware to your personal computer and using a terminal emulation program for access. The serial console is also mirrored to a special TCRP network console. If the network is functioning (i.e. you can see the IP in Synology Assistant), it can be accessed via a browser at https://<DSM IP>:7681

If DSM has not been installed, "SynologyNAS login:" will be displayed. If DSM has been installed but cannot start, "DiskStation login:" will be displayed. This is Junior mode. You can log in with root (you won't be prompted for a password).

If desired, the reason that Junior mode was started can be displayed with
cat /var/log/junior_mode
Disk port shutdown errors and missing disks are usually a SataPortMap/DiskIdxMap/Device Tree problem, but can be a driver issue if using SCSI or SAS host bus adapters. If SATA disks are missing, investigate DSM’s view of SataPortMap/DiskIdxMap and some other user_config.json parameters by typing
cat /proc/cmdline
If the loader device "/dev/synoboot" is not returned by the following command, the identifyusb step of the install may have been skipped
ls /dev/synoboot
Inspect DSM's view of the accessible disk devices with
ls –la /sys/block
If using a Device Tree platform, display the contents of the device tree with
dtc –I dtb -O dts /var/run/model.dtb
Where to Post for Help

It’s easy for requests for installation help to get lost in various unrelated forum threads. Post requests for help as a new topic in the DSM Installation Forum.

At a minimum, state the hardware configuration, selected platform, DSM version, user_config.json information (delete or redact the serial number and configured MAC address) and any information from debugging analysis that you have done.

DON’T post general requests for help on this thread.

Please DON’T post general requests for help on TCRP or RedPill development threads unless providing feedback on a dev issue.

Revision info (Reveal hidden contents)

2022-Jun-03 added disabled SATA port troubleshooting, removed some satamap complex description

2022-May-31 added restoresession argument

First- This is an AMAZING guide. THANKS Fly!!!!

I did notice a slight variation when I just setup my unit.

The RPloader will list the DS models and not the chipset that you wrote.

This section here...suggestion change it to pick your model and build # and add an example as you have in other sections.

Finally, choose a DSM release number

Each DSM build as provided by Synology has a release number. You can display the combinations of platforms and releases supported by TCRP by just running the script with no arguments

droiduser22 · December 31, 2022

Assistance please. I am being cautious.

I did read the Synology KB article.

In short they say to plug in my old drives to the new machine and all works (I guess it runs the migration after boot).

I am a bit apprehensive because I don't want to lose my data (backing up my photos).

It sounds "easy" as a plug in the old drives to new machine and boot then run migration and viola/done.

My setup -

I have 2 desktops:

1. HP8200 (sandy lake)

DS3615xs

DSM 6.2.3-25426 Update 3

I have 3 hard drives mirrored

Everything is working

I am moving to desktop 2

2. HP8300 (Ivy Bridge)

already setup with DSM 7 (redpill loader) and working with a test hard drive

DS3622xs+

I am not sure if the migration would work given that I am switching machines and DS models.

Do I simply install all of my current drive from desktop 1 into desktop 2 and THEN what do I do?

Do I install 1 or 2 drives to get things working THEN add the 3rd drive to the system?

Please let me know so I can proceed. I am on pause until further directions from you guys.

* I am backing up my files to external usb drive.

** Fly and others, just for the fun of it, I tried to setup using the DS920+.

It failed about 40% when trying to install the Synology DSM pat file.

The RPLoader allowed me to setup the usb key as a DS920+.

I resorted back to redoing the loader and setting up as DS3622xs+.

It worked.

*** Anyone using the HP8300SFF units, they are great, has 4 sata connectors. Just add 1 more power splitter. You can buy a cool replacment bay for the dvd drive and mount drives in it. I have 3 drives for NAS and 1 laptop drive to boot Windows should I want to use the desktop for other purposes.

I simply shutdown the NAS and remove the USB and it reboots into Windows/Linux drive.

I updated bios to ver. 2.09 (latest).

Turned off UEFI and set boot from USB as well as turned on AHCI per FLY's guide.

I did NOT have to format the usb key to hyrid ( pain in the rear, more steps) like I had to with the HP8200.

I made was able to follow the directions here and it all worked.

I am not sure if this procedure would work for me:

The actual migration process is simple:

Remove any existing SSD cache configuration (strongly recommended)

Shut down the NAS

Replace the existing 6.x USB loader with the TCRP 7.x USB loader from the process above

Boot the NAS and complete the DSM Migration when prompted

Restore SSD cache configuration as desired

Edited December 31, 2022 by droiduser22

droiduser22 · December 31, 2022

I am unable to edit my post above. I don't see the option, it was there before.

UPDATE:

I have to go back and reread this thread or others but if you know, I would appreciate the reply.

Does this TRPL setup allow us to download updates from Synology directly using the update feature?

I tried to check for updates but my NAS reported no network connection.

I have access because the time updated etc...

Is this a "bug" or are we only supposed to update manually with this setup?

I researched quite a bit last night. There are good Youtube videos showing between old and new synology units.

I moved the 3 drives from old to new desktop.

Booted up and followed the directions.

You will need your .pat file again to manually update from your local machine.

In terms of data protection. I don't know so I am asking.

Could I have connected 2 drives (not the 3rd) and did the migration to ensure it all worked THEN after a shutdown, connect the 3rd drive, reboot and let it add it to the pool? I am running 3 drives in raid 5 (mirror).

If something went wrong, then at least the 3rd drive is safe with all of the data.

This was helpful also.

https://kb.synology.com/en-us/DSM/tutorial/How_to_migrate_between_Synology_NAS_DSM_6_0_and_later

Peter Suh · January 1, 2023

11 hours ago, droiduser22 said:

I am unable to edit my post above. I don't see the option, it was there before.

UPDATE:

I have to go back and reread this thread or others but if you know, I would appreciate the reply.

Does this TRPL setup allow us to download updates from Synology directly using the update feature?

I tried to check for updates but my NAS reported no network connection.

I have access because the time updated etc...

Is this a "bug" or are we only supposed to update manually with this setup?

I researched quite a bit last night. There are good Youtube videos showing between old and new synology units.

I moved the 3 drives from old to new desktop.

Booted up and followed the directions.

You will need your .pat file again to manually update from your local machine.

In terms of data protection. I don't know so I am asking.

Could I have connected 2 drives (not the 3rd) and did the migration to ensure it all worked THEN after a shutdown, connect the 3rd drive, reboot and let it add it to the pool? I am running 3 drives in raid 5 (mirror).

If something went wrong, then at least the 3rd drive is safe with all of the data.

This was helpful also.

https://kb.synology.com/en-us/DSM/tutorial/How_to_migrate_between_Synology_NAS_DSM_6_0_and_later

I migrated to ds3622+xsp and things were working.

I manually updated to the newest update 7.1.1-42962 Update 3. I saw in a thread that someone else updated to the new UPdate 3 that's why I did it. I usually wait for a bit. I guess in my excitement I ignored caution.

after the update I got an error that it went into recovery mode.

I tried to recover it goes to the end and fails right at the end.

the syno assistant gave me a clue that when an RMA occurs the box OS is older than what's on the drive.

I am guessing the loader is older than what's on the drive.

System
bare metal
hp8300sff
3 (4tb drives) on raid 5

Everything was working before I tried the stupid update.
I am stuck.

--> I've moved your last question.
It would have been nice to continue asking questions here.
The topic on which this question was raised is an inappropriate topic that the question should not be raised on.

There are two ways.
1. It is to postupdate the loader with TCPP.
You need to go back to TC Linux and use the rploader.sh command.

2. It is to switch to the loader TCRP FRIEND.

( TCRP FRIEND automatically handles postupdate internally. )

This also requires going back to TC Linux and rebuilding the loader, but you can change it to a menu driven loader that is easier to build.
Execute the 3 commands below.

curl -L "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz" -O

tar -zxvf my.sh.gz

./menu.sh

Please refer to the link below for how to use the menu.

https://github.com/PeterSuh-Q3/tinycore-redpill/blob/main/README.md

Edited January 1, 2023 by Peter Suh

droiduser22 · January 1, 2023

12 hours ago, Peter Suh said:

Hi Peter,

Thanks for helping.

I did the update in fly's guide.

I tried what you said. I got error.

curl: (52) Empty reply from server

ran the command...error no such file or directory.

Did I miss something?

I wrote it EXACTLY how you posted with the "quotes" also.

12 hours ago, Peter Suh said:

2. It is to switch to the loader TCRP FRIEND.

( TCRP FRIEND automatically handles postupdate internally. )

This also requires going back to TC Linux and rebuilding the loader, but you can change it to a menu driven loader that is easier to build.
Execute the 3 commands below.

curl -L "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz" -O

tar -zxvf my.sh.gz

./menu.sh

Please refer to the link below for how to use the menu.

https://github.com/PeterSuh-Q3/tinycore-redpill/blob/main/README.md

droiduser22 · January 1, 2023

13 hours ago, Peter Suh said:

I migrated to ds3622+xsp and things were working.

I manually updated to the newest update 7.1.1-42962 Update 3. I saw in a thread that someone else updated to the new UPdate 3 that's why I did it. I usually wait for a bit. I guess in my excitement I ignored caution.

after the update I got an error that it went into recovery mode.

I tried to recover it goes to the end and fails right at the end.

the syno assistant gave me a clue that when an RMA occurs the box OS is older than what's on the drive.

I am guessing the loader is older than what's on the drive.

System
bare metal
hp8300sff
3 (4tb drives) on raid 5

Everything was working before I tried the stupid update.
I am stuck.

--> I've moved your last question.
It would have been nice to continue asking questions here.
The topic on which this question was raised is an inappropriate topic that the question should not be raised on.

There are two ways.
1. It is to postupdate the loader with TCPP.
You need to go back to TC Linux and use the rploader.sh command.

2. It is to switch to the loader TCRP FRIEND.

( TCRP FRIEND automatically handles postupdate internally. )

This also requires going back to TC Linux and rebuilding the loader, but you can change it to a menu driven loader that is easier to build.
Execute the 3 commands below.

curl -L "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz" -O

tar -zxvf my.sh.gz

./menu.sh

Please refer to the link below for how to use the menu.

https://github.com/PeterSuh-Q3/tinycore-redpill/blob/main/README.md

@PeterSuh

I made a new usb key using the automated redpill loader - everything went well, no errors

I am still getting error from syno assistant:

Failed to recover.

System has no response.

Connection timed out.

Just to clarify, I managed to install update 3 on my drives. I am guessing the redpill loader only has update 1 .

Is it possible you can add update 3 to the redpill update so my usb key will have the file that matches what's on the drives?

Thanks for your help.

*** just a thought...perhaps add a sentence at the end of the loader nothing will be displayed here anymore....add use synoassistant on your computer to further manage this new nas setup.

It's just an idea to help new users. What you guys are doing here is mind boggling. It makes my head spin knowing how cool what you guys are creating. IMPRESSIVE!!!

Edited January 1, 2023 by droiduser22

Peter Suh · January 2, 2023

7 hours ago, droiduser22 said:

@PeterSuh

I made a new usb key using the automated redpill loader - everything went well, no errors

I am still getting error from syno assistant:

Failed to recover.

System has no response.

Connection timed out.

Just to clarify, I managed to install update 3 on my drives. I am guessing the redpill loader only has update 1 .

Is it possible you can add update 3 to the redpill update so my usb key will have the file that matches what's on the drives?

Thanks for your help.

*** just a thought...perhaps add a sentence at the end of the loader nothing will be displayed here anymore....add use synoassistant on your computer to further manage this new nas setup.

It's just an idea to help new users. What you guys are doing here is mind boggling. It makes my head spin knowing how cool what you guys are creating. IMPRESSIVE!!!

My M shell for TCRP FRIEND is
A bit different from pocopico's original TCRP FRIEND
In the grub boot screen, the small revision of the built loader is indicated.

The smallrevision of the loader itself is always fixed to the smallrevision of the pat file used when building the loader.

For M shell for TCRP FRIEND, use 7.1.1-42962 smallrevision 0.

When the update is processed using the pat file for update in DSM Manager,
Within this second capture, the TCRP FRIEND boot screen,
DSM Version: 7.1.1-42962 Update: #
(currently 0 smallrevision )
This smallrevision # is changed.

Edited January 2, 2023 by Peter Suh

droiduser22 · January 2, 2023

11 minutes ago, Peter Suh said:

My M shell for TCRP FRIEND is
A bit different from pocopico's original TCRP FRIEND
In the grub boot screen, the small revision of the built loader is indicated.

The smallrevision of the loader itself is always fixed to the smallrevision of the pat file used when building the loader.

For M shell for TCRP FRIEND, use 7.1.1-42962 smallrevision 0.

When the update is processed using the pat file for update in DSM Manager,
Within this second capture, the TCRP FRIEND boot screen,
DSM Version: 7.1.1-42962 Update: #
(currently 0 smallrevision )
This smallrevision # is changed.

@Peter and Poco

It's FIXED!!!!

Peter, did you apply update 3 to the loader??

This is how I fixed it.

1. remade usb key (did it 3 times with 3 keys, that wasn't the issue)

I booted with the key, used syno assistant... IF you click recover here, it will FAIL giving you error and time out.

With a fresh key I amde about 15 minutes from posting here and Peter's post... I booted then went to syno assistant THEN I looked at the IP of my nas THEN I went to browser and typed the IP...I picked migrate...it took 10 minutes...It said FAILED at the end BUT...I rebooted the box and started with loader...then used syno assist then it showed me the name of my box with the manual ip I had set.

I was able to log in and it is showing DSM 7.1.1-42962 UPDATE 3.

I am assuming Peter and Poco did not change anything.

The TRICK/BUG is to assume the MIGRATE repair worked even though right at the end says failed.

Reboot and all should work for you.

THANKS PETER AND POCO!!! I was able to patch together ideas using the info you supplied.

It did not make sense that it took all that time, went to the last second then to say fail.

Peter Suh · January 2, 2023

12 minutes ago, droiduser22 said:

@Peter and Poco

It's FIXED!!!!

Peter, did you apply update 3 to the loader??

This is how I fixed it.

1. remade usb key (did it 3 times with 3 keys, that wasn't the issue)

I booted with the key, used syno assistant... IF you click recover here, it will FAIL giving you error and time out.

With a fresh key I amde about 15 minutes from posting here and Peter's post... I booted then went to syno assistant THEN I looked at the IP of my nas THEN I went to browser and typed the IP...I picked migrate...it took 10 minutes...It said FAILED at the end BUT...I rebooted the box and started with loader...then used syno assist then it showed me the name of my box with the manual ip I had set.

I was able to log in and it is showing DSM 7.1.1-42962 UPDATE 3.

I am assuming Peter and Poco did not change anything.

The TRICK/BUG is to assume the MIGRATE repair worked even though right at the end says failed.

Reboot and all should work for you.

THANKS PETER AND POCO!!! I was able to patch together ideas using the info you supplied.

It did not make sense that it took all that time, went to the last second then to say fail.

This is one last thing I wanted to confirm.
In the recaptured screen, Update: 2 (smallrevision) has been changed.

However, there is one strange thing.

I obviously used the Update 3 file, but it says 2 on this screen.
First, the Update 1 file was used on the screen, but it was marked as 0 on the screen.

I will test this part a little more and ask pocopico.

droiduser22 · January 2, 2023

44 minutes ago, Peter Suh said:

This is one last thing I wanted to confirm.
In the recaptured screen, Update: 2 (smallrevision) has been changed.

However, there is one strange thing.

I obviously used the Update 3 file, but it says 2 on this screen.
First, the Update 1 file was used on the screen, but it was marked as 0 on the screen.

I will test this part a little more and ask pocopico.

yes, i recall seeing update 0 also. That's why I knew I needed you guys to add update 3 then it would work. I am about to make another usb key (testing my keys).

Is it possible to use 2 DIFFERENT usb keys? I would like to keep a spare key ready to go. Or do they same to be identical physical keys (same brand etc...)

droiduser22 · January 2, 2023

@petersuh

just a small observation

in the tool creator

in the serial number menu, you have option 1 as generate and option 2 enter manual

BUT in the mac menu, you have them reversed

Can you please consider making them the same and default to generate

thx

droiduser22 · January 2, 2023

@petersuh

I just created another usb key

it now says UPDATE 2 (not 3)

side note - I used win32diskimager this time.

I used RUFUS before

I saw errors fly by something about disk characters 2^32

I am using a 32gb usb3 drive.

My 4gb usb 2 drive only boots to the grub recovery now. I used that when I posted it was fixed.

strange

The key note and maybe perhaps you guys can add this to your guides...when it says recovering/migrate and syno assistant says can't recover/failed...Open a browser window and go to the nas ip then do the migrate from there and it will take 10 minutes counting down then get to 0 and says fail...it didn't fail, just reboot everything and wait, then open syno assistant to see the nas then use browser to access the unit.

I sure come across strange errors and fixes

Edited January 2, 2023 by droiduser22

pocopico · January 2, 2023

4 hours ago, droiduser22 said:

@petersuh

I just created another usb key

it now says UPDATE 2 (not 3)

side note - I used win32diskimager this time.

I used RUFUS before

I saw errors fly by something about disk characters 2^32

I am using a 32gb usb3 drive.

My 4gb usb 2 drive only boots to the grub recovery now. I used that when I posted it was fixed.

strange

The key note and maybe perhaps you guys can add this to your guides...when it says recovering/migrate and syno assistant says can't recover/failed...Open a browser window and go to the nas ip then do the migrate from there and it will take 10 minutes counting down then get to 0 and says fail...it didn't fail, just reboot everything and wait, then open syno assistant to see the nas then use browser to access the unit.

I sure come across strange errors and fixes

FYI, I extracted the U3 update file and smallfixnumber is 2.

majorversion="7"
minorversion="1"
major="7"
minor="1"
micro="1"
productversion="7.1.1"
buildphase="GM"
buildnumber="42962"
smallfixnumber="2"
nano="2"
base="42962"
packing="nano"
packing_id="2"
derived="nano"
derived_id="2"
builddate="2022/10/18"
buildtime="14:51:38"
builddate="2022/10/18"
buildtime="15:30:48"
unique="synology_broadwellnk_3622xs+"
extractsize=855480
partitionversionlimit=0
syno_supported_hwrevision="r0"
indexdbextractsize=1428
synohdpackimgextractsize=23512
packagerootextractsize=0
packagevolumeextractsize=0

EDIT: After the update though, the /etc/VERSION file reports :

# cat /etc/VERSION
majorversion="7"
minorversion="1"
major="7"
minor="1"
micro="1"
productversion="7.1.1"
buildphase="GM"
buildnumber="42962"
smallfixnumber="3"
nano="3"
base="42962"
builddate="2022/12/07"
buildtime="17:44:52"

Edited January 2, 2023 by pocopico

Peter Suh · January 2, 2023

@pocopico

There was an update of TCRP FRIEND v0.0.4 about an hour ago.
I saw that you fixed a typo in user_config.json .

Anyway,

I tested with my main XPE, DS918+ 7.1.1-42962 U0.

Update step by step from Update 0 to Update 3
This is the result of comparing the Update : # information on the TCRP FRIEND Boot screen with the VERSION file.

Test result is Update 0, 2 is normal
There is a difference in notation in Update 1 and 3.

[DSM Update 0] -> TCRP FRIEND Boot Screen, Update : 0

admin2@NAS4:~$ cat /etc/VERSION

majorversion="7"

minorversion="1"

major="7"

minor="1"

micro="1"

productversion="7.1.1"

buildphase="GM"

buildnumber="42962"

smallfixnumber="0"

nano="0"

base="42962"

builddate="2022/09/04"

buildtime="00:54:56"

[DSM Update 1] -> TCRP FRIEND Boot Screen, Update : 0

admin2@NAS4:~$ cat /etc/VERSION

majorversion="7"

minorversion="1"

major="7"

minor="1"

micro="1"

productversion="7.1.1"

buildphase="GM"

buildnumber="42962"

smallfixnumber="1"

nano="1"

base="42962"

builddate="2022/09/16"

buildtime="20:01:57"

[DSM Update 2] -> TCRP FRIEND Boot Screen, Update : 2

admin2@NAS4:/$ cat /etc/VERSION

majorversion="7"

minorversion="1"

major="7"

minor="1"

micro="1"

productversion="7.1.1"

buildphase="GM"

buildnumber="42962"

smallfixnumber="2"

nano="2"

base="42962"

builddate="2022/10/18"

buildtime="14:49:40"

[DSM Update 3] -> TCRP FRIEND Boot Screen, Update : 2

cat /etc/VERSION

majorversion="7"

minorversion="1"

major="7"

minor="1"

micro="1"

productversion="7.1.1"

buildphase="GM"

buildnumber="42962"

smallfixnumber="3"

nano="3"

base="42962"

builddate="2022/12/07"

buildtime="17:44:52"

Tutorial: Install/Migrate to DSM 7.x with TinyCore RedPill (TCRP) Loader

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