Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

43 minutes ago, alexnoy123 said:

Command " od -bc autonano.pat } | head -1 | awk '{print $3}' "  = 255 -> encrypted.

I tried to unpack/decrypt "autonano.pat" with command " sudo /bin/syno_extract_system_patch autonano.pat /tmp/pat" , but the "/tmp/pat" directory is empty. Maybe another command need...

 

Hmmm... I probe fresh install with cached "nano" .pat file. DSM installed without problem. Probe update to "7.1-42661 Update 1" version -> updated, worked. File "autonano.pat" -> now no problem -> maybe future :) (need change paths in scripts for auto download new files...) (maybe now "autonano.pat" empty? 5mb -> added encryption?) (Sorry my bad english...)

Great start! - maybe @Peter Suhor @pocopico can provide more incite into this. 

Edited by cferra
Link to comment
Share on other sites

2 часа назад, Badger сказал:

Which file did you use?  It appears I can download the 4.5MB .pat file.... but  "error 403" when I try to download the big file (over 340MB).

You need manually download "big file" from synology site (https://archive.synology.com/download/Os/DSM/7.1-42661-1-NanoPacked) (or https://drive.google.com/drive/folders/1fIvbwHLqe4GIIi5RcNayJKykqcaCbva1 -> old original files) and put in "cache" folder (/mnt/sd#3/auxfiles/) and then "build" (example: "./rploader.sh build bromolow-7.1.0-42661").

---------------------------------------------------------------------------------------------------------

And more about "autonano.pat" in the file "updater" there is a mention of "autonano" (and in OLD full .pat file!!!). If I understand correctly, this is something like very small security updates. 

Sparse files don't exist. Skip Sparse Bootup SmallUpdate Sparse. Bootup SmallUpdate HDA1 install successful Unable to HandleBootupSmallUpdateViaChroot This failure is fatal. Boot to junior mode. Manually skipped auto nano update. patch exists. Skip download. https://update7.synology.com/smallupdate Failed to determine LookUpServer URL Failed to download security json via wget from url: Found there are no upgradeable packs for given version Fail to get user agent (smallupdate) synoinstall: autonano::ExecWgetWithRetry cancelled

 

And apparently if he does not find it, then he tries to download from the site "https://update7.synology.com/smallupdate". But it seems like "synology.com" is blocked by pocopico (changed to example.com?) - he himself will not download anything. But what is in this file now is the question....

---------------------------------------------------------

In "var/log/messages" from started DSM found:

"2022-04-28T00:01:43+03:00 dsm7 smallupd@ter[19841]: small_update.cpp:344 No need to workaround for HA autoupdate problem"

---------------------------------------------------------

By the way! Can anyone tell me if this is normal?

(Next log from "/var/log/messages" from started DSM)

2022-04-28T00:02:51+03:00 dsm7 kernel: [   25.728602] 30 0d bb a0 ff ff ff ff  [18] 0x090       ffffffffa0bb0d30        rtc_bandon_set_auto_poweron+0x0/0x90 [broadwellnk_synobios]
2022-04-28T00:02:51+03:00 dsm7 kernel: [   25.728839] c0 08 bb a0 ff ff ff ff  [19] 0x098       ffffffffa0bb08c0        rtc_get_auto_poweron+0x0/0x50 [broadwellnk_synobios]

------------------------------------------------------------

In the new .pat file, in addition to adding autonano.pat, SMBService * .spk is also updated (well, checksum with signatures too). I didn't find anything else changed...

Edited by alexnoy123
Link to comment
Share on other sites

6 hours ago, loomes said:

 

LOL of course not 😆

You dont understand me. The "old" 42661 complete Images are gone. They are replaced with the Update1 Images.

Have a look here: https://archive.synology.com/download/Os/DSM

The "7.1-42661-1" directory has the Update Files for running installations with the "old" 42661 Machines.

The "7.1-42661-1-NanoPacked" dir holds the new complete Images (dont know what NanoPacked means?!)

 

So the TC must Updated for the new complete Images.

 

I also checked the existence of 7.1-42661-1 or NanoPacked directory you are talking about.
However, as an example so far, there has been no case of deleting the already released version of the link.
It remains to be seen what happens as the link recovers.

Link to comment
Share on other sites

4 hours ago, Peter Suh said:

 

I also checked the existence of 7.1-42661-1 or NanoPacked directory you are talking about.
However, as an example so far, there has been no case of deleting the already released version of the link.
It remains to be seen what happens as the link recovers.

 

The link is working again.

 

https://www.synology.com/en-us/support/download/DS3622xs+?version=7.1#system

Edited by Peter Suh
Link to comment
Share on other sites

8 minutes ago, Peter Suh said:

 

 

As @looms said, the link to the 7.1.0-42661 original pat seems to be no longer available.
7.1.0-42661 It seems that the TC source of the @pocopico should be changed again with the link using the new nanopacked with the contents of u1.
It is the decision of the @pocopico whether to create a new 7.1.0-42661u1 with 7.1.0-42661 setting, but for now,
The 7.1.0-42621 RC link is missing and the 7.1.0-42661 link is missing too.
I think I should download the 7.1.0-42661 pat file I shared below and manually copy it to TC's partition before I wait for the revision of the pocopico.

 

https://drive.google.com/drive/folders/1fIvbwHLqe4GIIi5RcNayJKykqcaCbva1?usp=sharing


If necessary, I will provide these pat files to be downloaded directly using curl or wget in TC.

Link to comment
Share on other sites

In TC Linux, the pat file was separately downloaded and built with the command below, and the changed nanopacked u1 pat file was also able to be built without any problems.

 

curl -o /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles/ds3622xsp_42661.pat  "https://global.download.synology.com/download/DSM/release/7.1/42661-1/DSM_DS3622xs%2B_42661.pat"

Link to comment
Share on other sites

9 minutes ago, Peter Suh said:

In TC Linux, the pat file was separately downloaded and built with the command below, and the changed nanopacked u1 pat file was also able to be built without any problems.

 

curl -o /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles/ds3622xsp_42661.pat  "https://global.download.synology.com/download/DSM/release/7.1/42661-1/DSM_DS3622xs%2B_42661.pat"

 

 

This is the result of building the nanopacked u1 pat file on the VM using the manual download method above and installing the DSM directly to the 7.0.1-42661 u1 version.

It is installed well without any problems.

 

 

1714683005_2022-04-2812_11_51.thumb.png.fa8085f743107671e4fd3f3132a43ba6.png

Link to comment
Share on other sites

(Notice)

The 42661 nano U1 download function, which has been changed this time in @pocopico's TC, has not been changed yet.
So, to make up for this, we added the function of pre-downloading 42661 nano U1 files to the new URL of the changed U1.
This feature allows you to avoid errors caused by downloading within TC, which is still before the change.

 

(Automatic updates are supported for users who downloaded after April 24, but users who downloaded before that should receive new updates.)

----------------------------------------------------------------------------------------------------------------------------

 

1.This is a shell script that executes several commands at once as described in the "Redpill Tinycore Loader DSM 7.1 Build" guide.

 

To use, you can download and untar it as follows and use it in the /home/tc directory.

 

Helps build DSM 7.1 by managing the PAT file directory required for decryption.

 

Automatically add mac2 to user_config.json file for dual NIC, a feature that TC doesn't have.

 

( Manual Response Version )

tc@box:~$ wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/m.sh.gz; tar -zxvf m.sh.gz;

 

( Auto Answer Version with y )
tc@box:~$ wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz; tar -zxvf my.sh.gz;

 

Where y is unnecessarily asked, it automatically responds.


./my.sh DS918+

./my.sh DS3617xs

./my.sh DS3615xs

./my.sh DS3622xs+

./my.sh DVA3221

./my.sh DS920+

./my.sh DS1621+
 

 

1106259566_2022-04-248_32_51.thumb.png.9a36269259ddae7993e344fb7b4f5350.png.2993bf74cbba20fe98f4b0136cc539f9.png

 

-----------------------------------------------------------------------------------------------------

 

2. Deploy scripts that you can leverage if you need to add a separate ext manually for VM users.

It includes the fuction to add exts created by @FOXBI with multiple selections like capture.

 

For the instructions on how to use, you can download and decompress as below and use it in /home/tc directory.

 

( Auto Answer Version with y )

tc@box:~$ wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/myv.sh.gz; tar -zxvf myv.sh.gz;

 

The way to use it is existing same as my.sh. Where y is unnecessarily asked, it automatically responds.

 

./myv.sh DS918+

./myv.sh DS3617xs

./myv.sh DS3615xs

./myv.sh DS3622xs+

./myv.sh DVA3221

./myv.sh DS920+

./myv.sh DS1621+
 

1573609525_2022-04-199_54_07.thumb.png.f44c890de62c6f8b6d71d4abb9279c36.png.fb04d59fd3ad8bd8159478580256056d.png.c37e9f166bdb84c2ab64288c00e16ef4.png

 

CAUTION) Not all exts correspond to 7.1.0-42661.
Please check @pocopico's ext GITHUB in advance and use it.
We do not respond to errors caused by unsupported revisions.

 

Edited by Peter Suh
  • Like 3
Link to comment
Share on other sites

5 minutes ago, pocopico said:

Please read the release notes before performing any updates :

 

https://www.synology.com/en-us/releaseNote/DSM

 

Offline updates should be possible through the extra SMB package 

 

3. If users' Synology NAS aren't connected to the Internet, they must download SMB Service 4.10.18-0434 from the Download Center and manually install it after the DSM update to make sure the package functions properly. Note: Before users install SMB Service 4.10.18-0434, the package and its dependent package, Synology Directory Server, will be deactivated.

 

Link to comment
Share on other sites

During boot of a DS1621+ bootloader in Proxmox I see the following error:

 

Still waiting for boot device (waited 1 of 30 seconds)
[    5.100543] scsi 12:0:0:0: Direct-Access     QEMU     QEMU HARDDISK            2.5+ PQ: 0 ANSI: 5
[    5.101762] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim
[    5.102728] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications
[    5.103722] <redpill/boot_shim_base.c:29> scsi_is_boot_dev_target: it's not a SATA disk, ignoring
[    5.104697] <redpill/scsi_notifier.c:87> Calling original sd_probe()
[    5.105691] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0
[    5.107576] sd 12:0:0:0: [usb1] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB)
[    5.108808] sd 12:0:0:0: [usb1] Write Protect is off
[    5.109522] sd 12:0:0:0: [usb1] Mode Sense: 63 00 00 08
[    5.110491] sd 12:0:0:0: [usb1] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    5.112845]  usb1: p1 p2 p3
[    5.114160] sd 12:0:0:0: [usb1] Attached SCSI disk
Still waiting for boot device (waited 2 of 30 seconds)

etc.

etc.

until boot_wait is timed out and no boot device is found?

 

When I see this behaviour installation of teh PAT file always fails at 55%

 

the proxmox VM is created like this:

# set vm id
id=xxx

# create image directory, download and uncomporess
mkdir -p /var/lib/vz/images/${id}
curl --location https://github.com/pocopico/tinycore-redpill/raw/main/tinycore-redpill.v0.4.6.img.gz --output /var/lib/vz/images/${id}/tinycore-redpill.img.gz
gzip --decompress /var/lib/vz/images/${id}/tinycore-redpill.img.gz --keep


# create vm
qm create ${id} \
  --args "-drive 'if=none,id=synoboot,format=raw,file=/var/lib/vz/images/${id}/tinycore-redpill.img' -device 'qemu-xhci,addr=0x18' -device 'usb-storage,drive=synoboot,bootindex=5'" \
  --cores 2 \
  --cpu host \
  --machine q35 \
  --memory 2048 \
  --name DSM710 \
  --net0 virtio,bridge=vmbr0 \
  --numa 0 \
  --onboot 0 \
  --ostype l26 \
  --scsihw virtio-scsi-pci \
  --sata0 local-lvm:vm-${id}-disk-0,discard=on,size=10G,ssd=1 \
  --sockets 1 \
  --serial0 socket \
  --tablet 1

# create disk for sata0
pvesm alloc local-lvm ${id} vm-${id}-disk-0 10G

 

Is there anything that I'm missing causing the TC image attached as sata0 is not recognized?

 

 

 

Link to comment
Share on other sites

I am running KVM on AMD host, and have a working DSM 7.1 using the below:

sudo su
./rploader.sh update now
./rploader.sh fullupgrade now
./rploader.sh serialgen DS1621+
./rploader.sh satamap v1000-7.1.0-42661
./rploader.sh backup now
./rploader.sh ext v1000-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/redpill-load/master/redpill-virtio/rpext-index.json
./rploader.sh build v1000-7.1.0-42661 auto
poweroff

 

I have then added three 8TB SATA drive using disk/by-id method (SATA). I have been using these in a DSM6 for the past year, with no issues, these still contain the same RAID 5 config.
Now when in the new DSM7 gui, the 3 SATA drives are not visable, BUT they are visible if I SSH into the DSM.

using 'fdsik -l' shows this:

 

Disk /dev/sata2: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: HARDDISK                
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: D5DF9490-0AC3-4756-94E4-C32ADD7FFAA7

Device         Start         End     Sectors  Size Type
/dev/sata2p1    2048     4982527     4980480  2.4G Linux RAID
/dev/sata2p2 4982528     9176831     4194304    2G Linux RAID
/dev/sata2p3 9437184 15627848351 15618411168  7.3T Linux RAID
 

Why can't I see them in the GUI, what am I doing wrong please?

Link to comment
Share on other sites

7 hours ago, wimsan said:

During boot of a DS1621+ bootloader in Proxmox I see the following error:

 

Still waiting for boot device (waited 1 of 30 seconds)
[    5.100543] scsi 12:0:0:0: Direct-Access     QEMU     QEMU HARDDISK            2.5+ PQ: 0 ANSI: 5
[    5.101762] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim
[    5.102728] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications
[    5.103722] <redpill/boot_shim_base.c:29> scsi_is_boot_dev_target: it's not a SATA disk, ignoring
[    5.104697] <redpill/scsi_notifier.c:87> Calling original sd_probe()
[    5.105691] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0
[    5.107576] sd 12:0:0:0: [usb1] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB)
[    5.108808] sd 12:0:0:0: [usb1] Write Protect is off
[    5.109522] sd 12:0:0:0: [usb1] Mode Sense: 63 00 00 08
[    5.110491] sd 12:0:0:0: [usb1] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    5.112845]  usb1: p1 p2 p3
[    5.114160] sd 12:0:0:0: [usb1] Attached SCSI disk
Still waiting for boot device (waited 2 of 30 seconds)

etc.

etc.

until boot_wait is timed out and no boot device is found?

 

When I see this behaviour installation of teh PAT file always fails at 55%

 

the proxmox VM is created like this:

# set vm id
id=xxx

# create image directory, download and uncomporess
mkdir -p /var/lib/vz/images/${id}
curl --location https://github.com/pocopico/tinycore-redpill/raw/main/tinycore-redpill.v0.4.6.img.gz --output /var/lib/vz/images/${id}/tinycore-redpill.img.gz
gzip --decompress /var/lib/vz/images/${id}/tinycore-redpill.img.gz --keep


# create vm
qm create ${id} \
  --args "-drive 'if=none,id=synoboot,format=raw,file=/var/lib/vz/images/${id}/tinycore-redpill.img' -device 'qemu-xhci,addr=0x18' -device 'usb-storage,drive=synoboot,bootindex=5'" \
  --cores 2 \
  --cpu host \
  --machine q35 \
  --memory 2048 \
  --name DSM710 \
  --net0 virtio,bridge=vmbr0 \
  --numa 0 \
  --onboot 0 \
  --ostype l26 \
  --scsihw virtio-scsi-pci \
  --sata0 local-lvm:vm-${id}-disk-0,discard=on,size=10G,ssd=1 \
  --sockets 1 \
  --serial0 socket \
  --tablet 1

# create disk for sata0
pvesm alloc local-lvm ${id} vm-${id}-disk-0 10G

 

Is there anything that I'm missing causing the TC image attached as sata0 is not recognized?

 

 

 

Consult @haydibe signature for instructions

Link to comment
Share on other sites

Just an FYI, looks like Synology disabled/removed the ability to use "http://<dsm-ip-address>:5000/webman/start_telnet.cgi" in the 7.1-42661-1-NanoPacked update. Did a fresh install and got the below message. Also checked /usr/syno/synoman/webman/ and there is no longer a start_telnet.cgi file.

 

image.thumb.png.3d2a795a3faebab35d2e63542bd1dad0.png

Link to comment
Share on other sites

9 hours ago, wimsan said:

During boot of a DS1621+ bootloader in Proxmox I see the following error:

 

Still waiting for boot device (waited 1 of 30 seconds)
[    5.100543] scsi 12:0:0:0: Direct-Access     QEMU     QEMU HARDDISK            2.5+ PQ: 0 ANSI: 5
[    5.101762] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim
[    5.102728] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications
[    5.103722] <redpill/boot_shim_base.c:29> scsi_is_boot_dev_target: it's not a SATA disk, ignoring
[    5.104697] <redpill/scsi_notifier.c:87> Calling original sd_probe()
[    5.105691] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0
[    5.107576] sd 12:0:0:0: [usb1] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB)
[    5.108808] sd 12:0:0:0: [usb1] Write Protect is off
[    5.109522] sd 12:0:0:0: [usb1] Mode Sense: 63 00 00 08
[    5.110491] sd 12:0:0:0: [usb1] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    5.112845]  usb1: p1 p2 p3
[    5.114160] sd 12:0:0:0: [usb1] Attached SCSI disk
Still waiting for boot device (waited 2 of 30 seconds)

etc.

etc.

until boot_wait is timed out and no boot device is found?

 

When I see this behaviour installation of teh PAT file always fails at 55%

 

the proxmox VM is created like this:

# set vm id
id=xxx

# create image directory, download and uncomporess
mkdir -p /var/lib/vz/images/${id}
curl --location https://github.com/pocopico/tinycore-redpill/raw/main/tinycore-redpill.v0.4.6.img.gz --output /var/lib/vz/images/${id}/tinycore-redpill.img.gz
gzip --decompress /var/lib/vz/images/${id}/tinycore-redpill.img.gz --keep


# create vm
qm create ${id} \
  --args "-drive 'if=none,id=synoboot,format=raw,file=/var/lib/vz/images/${id}/tinycore-redpill.img' -device 'qemu-xhci,addr=0x18' -device 'usb-storage,drive=synoboot,bootindex=5'" \
  --cores 2 \
  --cpu host \
  --machine q35 \
  --memory 2048 \
  --name DSM710 \
  --net0 virtio,bridge=vmbr0 \
  --numa 0 \
  --onboot 0 \
  --ostype l26 \
  --scsihw virtio-scsi-pci \
  --sata0 local-lvm:vm-${id}-disk-0,discard=on,size=10G,ssd=1 \
  --sockets 1 \
  --serial0 socket \
  --tablet 1

# create disk for sata0
pvesm alloc local-lvm ${id} vm-${id}-disk-0 10G

 

Is there anything that I'm missing causing the TC image attached as sata0 is not recognized?

 

 

 

Having exactly the same problem here! Is a solution for this known? Especially when using a HBA card? Tried the exact same steps in my proxmox setup but always failed.

Link to comment
Share on other sites

2 hours ago, OzTechGeek said:

Just an FYI, looks like Synology disabled/removed the ability to use "http://<dsm-ip-address>:5000/webman/start_telnet.cgi" in the 7.1-42661-1-NanoPacked update. Did a fresh install and got the below message. Also checked /usr/syno/synoman/webman/ and there is no longer a start_telnet.cgi file.

 

image.thumb.png.3d2a795a3faebab35d2e63542bd1dad0.png

Maybe we can add that functionality back by taking the files and manually copying them back to the appropriate destination?

Link to comment
Share on other sites

5 hours ago, pocopico said:

Actually there is an extension called early-telnet. It serves the same purpose. Also redpill-misc adds a perfect solution 

 

I also use most convenient ttyd through redpill-misc.
However, if ttyd merge does not work, early-telnet has been used as an alternative.
If this part is blocked, it is regrettable.

Edited by Peter Suh
Link to comment
Share on other sites

10 hours ago, speedyrazor said:

I am running KVM on AMD host, and have a working DSM 7.1 using the below:

sudo su
./rploader.sh update now
./rploader.sh fullupgrade now
./rploader.sh serialgen DS1621+
./rploader.sh satamap v1000-7.1.0-42661
./rploader.sh backup now
./rploader.sh ext v1000-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/redpill-load/master/redpill-virtio/rpext-index.json
./rploader.sh build v1000-7.1.0-42661 auto
poweroff

 

I have then added three 8TB SATA drive using disk/by-id method (SATA). I have been using these in a DSM6 for the past year, with no issues, these still contain the same RAID 5 config.
Now when in the new DSM7 gui, the 3 SATA drives are not visable, BUT they are visible if I SSH into the DSM.

using 'fdsik -l' shows this:

 

Disk /dev/sata2: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: HARDDISK                
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: D5DF9490-0AC3-4756-94E4-C32ADD7FFAA7

Device         Start         End     Sectors  Size Type
/dev/sata2p1    2048     4982527     4980480  2.4G Linux RAID
/dev/sata2p2 4982528     9176831     4194304    2G Linux RAID
/dev/sata2p3 9437184 15627848351 15618411168  7.3T Linux RAID
 

Why can't I see them in the GUI, what am I doing wrong please?

 

@speedyrazor

 

Although DS1621+ is a platform specialized for AMD, I do not know the advantages compared to the INTEL series platform.
TC has a function that automatically maps DTC SATAPORT when building DS1621+,
Sometimes it is necessary to manually map with prior knowledge of DTC.
If you do not have a deep understanding of DTC,
Rather, consider installing a migration to DS3622xs+, which is also available on AMD platforms.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...