TinyCore RedPill Loader (TCRP)

benok · June 2, 2022

13 hours ago, pocopico said:

That’s a very good idea if it serves and fits your purpose. Unfortunately though I have to say that if you want to release it you can of course do so and take care of any future adjustments after a TCRP update.

That of course is controllable as TCRP stable version 0.8.0.0 will not change in features and all future development will now go to development releases 0.9.0.0

Ok, I understand.

But if it's not included in your (official) repository, I think it's not useful and confusing.

(Additional download steps required, additional tutorial variation, like m.sh.)

I don't want to add another unofficial method, please forget my proposal. sorry.

tdutrieux · June 2, 2022

Hi everybody.

I currently have a problem for building DS918+ (7.0.1 - 42218)

Platform is ESXI 7.0u3

Install went smooth but when DSM is installed, I get 'Recoverable' is Synology Assistant.

Then I do 'recovery' and reboot -> still 'Recoverable'.

BTW, I tried exactly the same setup and installation steps but with DS3622xs, and it works perfectly.

Seems then to have a specific problem with DS918+.

Anybody experienced the same problem ?

Thanks in advance,

TitiD

Edited June 2, 2022 by tdutrieux

pocopico · June 2, 2022

2 minutes ago, tdutrieux said:

Hi everybody.

I currently have a problem for building DS918+ (7.0.1 - 42218)

Platform is ESXI 7.0u3

Install went smooth but when DSM is installed, I get 'Recoverable' is Synology Assistant.

Then I do 'recovery' and reboot -> still 'Recoverable'.

BTW, I tried exactly the same setup and installation steps but with DS3622xs, and it works perfectly.

Seems then to have a specific problem with DS918+.

Anybody experienced the same problem ?

Thanks in advance,

TitiD

you should check for failing extensions. If an extension fails to load, this usually exits to recovery

flyride · June 2, 2022

2 hours ago, Peter Suh said:

@flyride

Can I continue to ask and answer questions about TCRP installation in this topic?
If there are no problems, I will participate.

Of course you can.

tdutrieux · June 2, 2022

2 hours ago, pocopico said:

you should check for failing extensions. If an extension fails to load, this usually exits to recovery

Do you mean when building the loader, or when bootlng the loader after building ?

If it's when booting, how to access the log ?

Sorry for being a bit noob... Thanks.

pocopico · June 2, 2022

1 minute ago, tdutrieux said:

Do you mean when building the loader, or when bootlng the loader after building ?

If it's when booting, how to access the log ?

Sorry for being a bit noob... Thanks.

you can open your browser to <yourip>:7681 , login with user root and no pass

then get the logs under /var/log/ and post them here

cat /var/log/junior_reason*

cat /var/log/linux*

pocopico · June 2, 2022

@all,

I'm trying to test and standardize the update from update1 to update2 process. So please be patient with the update. Nothing special on update2, so there is really no need to rush.

Deniska · June 2, 2022

Hello guys.

Thanks Pocopico and all team for redpill loader.

I will share my situation below and i hope you can help me. I have been fighting with sata port problem many days and i think i missed something.

I have Asrock h570-itx (4 SATA+ 2 M2)/i5-10400/16Gb/one HDD connected to sata3_0 motherboard port/one M2 disk in M2_2 motherboard slot. The HDD hasn`t any partitions. Motherboard has 2 NIC - 2,5Gb\s and 1Gb\s. NIC with 2,5Gb\s is working well.

I`m trying to install DS3615sx 7.1.0-42661 via Redpill tinycore-redpill-uefi.v0.8.0.0.img.gz (and before i had installed unsuccessful 0.4.6 version).

I see HDD and M2 in BIOS well. HHD hot plug option is enable. I use AHCI mode for HDD and don`t use quick loading in BIOS.

Making loader.

I haven't seen any errors, loader has found 2,5Gb\s NIC. I've attached different logs of dmesg, lspci, fdisk, lsscsi to the message.

Satamap now:
"SataPortMap": "4",
"DiskIdxMap": "00",
When i used 7.0.1 version of DS3615sx i got "SataPortMap": "60", "DiskIdxMap": "0001", but it does not help.

I tried to use DS920+ and DS3622sx but these version didn't see NIC.

What is problem:

After connect to DS via web i've got message:

What i think.

I've read many internet articles about SATA, XPenology and forums threads of Redpill loader. I've tried to use different option for SataPortMap и DiskIdxMap and sata_remap but it didn't help me.

If i had used sataportmap=1 or sataportmap=2 then Diskstation can't find any disks. If i had used sataportmap=3 and more then Diskstation have showed problem above.

I see in dmesg that SATA port 0 and 1 is disable on motherboard:
[ 0.429214] ata1: DUMMY
[ 0.429215] ata2: DUMMY
[ 0.429220] ata3: SATA max UDMA/133 abar m2048@0x9fb22000 port 0x9fb22200 irq 125
[ 0.429221] ata4: SATA max UDMA/133 abar m2048@0x9fb22000 port 0x9fb22280 irq 125
[ 0.429223] ata5: SATA max UDMA/133 abar m2048@0x9fb22000 port 0x9fb22300 irq 125
[ 0.429224] ata6: SATA max UDMA/133 abar m2048@0x9fb22000 port 0x9fb22380 irq 125

I think it's main reason of problem but sata_remap option didn't help me:(.

I had use sata_remap via grub loader as "sata_remap": "2\>0:3\>1" and wrote in user_config.json as "sata_remap": "2\\>0:3\\>1".

It doesn't help me too.

Next idea that Redpill loader doesn't support SATA controller. But I can't find any extension for it here https://github.com/pocopico/rp-ext.

Could you help what i can try more?

Thank you very much!

lsscsi-Hv.txt lspci-v.txt lspci-nnq.txt fdisk-l.txt dmesg.txt

Edited June 2, 2022 by Deniska
fix error

neonflx · June 2, 2022

Have the same issue on AMD setup, either it tells me there were errors and controller disabled or can'tfind drives pulling whatever hair I have left, really want to get this goinf

pocopico · June 2, 2022

25 minutes ago, Deniska said:

Hello guys.

Thanks Pocopico and all team for redpill loader.

I will share my situation below and i hope you can help me. I have been fighting with sata port problem many days and i think i missed something.

I have Asrock h570-itx (4 SATA+ 2 M2)/i5-10400/16Gb/one HDD connected to sata3_0 motherboard port/one M2 disk in M2_2 motherboard slot. The HDD hasn`t any partitions. Motherboard has 2 NIC - 2,5Gb\s and 1Gb\s. NIC with 2,5Gb\s is working well.

I`m trying to install DS3615sx 7.1.0-42661 via Redpill tinycore-redpill-uefi.v0.8.0.0.img.gz (and before i had installed unsuccessful 0.4.6 version).

I see HDD and M2 in BIOS well. HHD hot plug option is enable. I use AHCI mode for HDD and don`t use quick loading in BIOS.

Making loader.

I haven't seen any errors, loader has found 2,5Gb\s NIC. I've attached different logs of dmesg, lspci, fdisk, lsscsi to the message.

Satamap now:
"SataPortMap": "4",
"DiskIdxMap": "00",
When i used 7.0.1 version of DS3615sx i got "SataPortMap": "60", "DiskIdxMap": "0001", but it does not help.

I tried to use DS920+ and DS3622sx but these version didn't see NIC.

What is problem:

After connect to DS via web i've got message:

What i think.

I've read many internet articles about SATA, XPenology and forums threads of Redpill loader. I've tried to use different option for SataPortMap и DiskIdxMap and sata_remap but it didn't help me.

If i had used sataportmap=1 or sataportmap=2 then Diskstation can't find any disks. If i had used sataportmap=3 and more then Diskstation have showed problem above.

I see in dmesg that SATA port 0 and 1 is disable on motherboard:
[ 0.429214] ata1: DUMMY
[ 0.429215] ata2: DUMMY
[ 0.429220] ata3: SATA max UDMA/133 abar m2048@0x9fb22000 port 0x9fb22200 irq 125
[ 0.429221] ata4: SATA max UDMA/133 abar m2048@0x9fb22000 port 0x9fb22280 irq 125
[ 0.429223] ata5: SATA max UDMA/133 abar m2048@0x9fb22000 port 0x9fb22300 irq 125
[ 0.429224] ata6: SATA max UDMA/133 abar m2048@0x9fb22000 port 0x9fb22380 irq 125

I think it's main reason of problem but sata_remap option didn't help me:(.

I had use sata_remap via grub loader as "sata_remap": "2\>0:3\>1" and wrote in user_config.json as "sata_remap": "2\\>0:3\\>1".

It doesn't help me too.

Next idea that Redpill loader doesn't support SATA controller. But I can't find any extension for it here https://github.com/pocopico/rp-ext.

Could you help what i can try more?

Thank you very much!

lsscsi-Hv.txt 1020 B · 2 downloads lspci-v.txt 8.53 kB · 1 download lspci-nnq.txt 1.64 kB · 0 downloads fdisk-l.txt 13.15 kB · 1 download dmesg.txt 53.04 kB · 1 download

well if you could send fdisk -l and dmesg from DSM then maybe we get an idea of what is happening

flyride · June 2, 2022

Post the output of satamap, and also ls -la /sys/block from TinyCore.

Fdisk -l and dmesg aren't bad ideas either

There is no need for driver extension for SATA controller as long as it is AHCI compliant.

flyride · June 2, 2022

I have a conjecture about all the recent hard drive port errors, mostly encountered on X570, but now we have a current Intel motherboard example.

The errors all seem to be on dual-definable ports that can be either NVMe slots or SATA (via M.2 port). For whatever reason, DSM is choking on unpopulated M.2 SATA ports.

I realize that few people have M.2 SATA SSD's. But it would be very helpful to tabulate comparative results with a motherboard that exhibits the characteristics.

1) with nothing populated in M.2 slots

2) with all M.2 slots populated by NVMe drives

3) with all M.2 slots populated by M.2 SATA drives

4) with all M.2 slots completely disabled (if functionally configurable on the motherboard)

Without additional information, there may be no baremetal satamap based solution that will work. In that case, we will want to confirm functionality with a Device Tree-based model.

Of course, virtualization is and will continue to be a solution for these motherboards.

Firs · June 2, 2022

22 часа назад, Firs сказал:

Я попытался обновить загрузчик до версии v0.8.0.0 и получил ошибку:

Найдено новое устройство <vid=0627, pid=0001> — не соответствует ожидаемому <vid=46f4, pid=0001>

I managed to update the bootloader v0.8.0.0
I once again went through all the compilation steps, starting with downloading the file from github.
Probably last time, I made some mistake at the configuration stage

d3mone · June 3, 2022

10 hours ago, pocopico said:

you can open your browser to <yourip>:7681 , login with user root and no pass

then get the logs under /var/log/ and post them here

cat /var/log/junior_reason*

cat /var/log/linux*

Here is the output:

Try bootup smallupdate
/usr/syno/sbin/synoupgrade: unrecognized option '--bootup-smallupdate'
Copyright (c) 2003-2022 Synology Inc. All rights reserved.

        --auto
        --auto-dsm=DSM_PAT_VERSION
        --check
        --check-dsm=DSM_PAT_VERSION
        --download
        --start
        --patch ABSOULATE_UPGRADE_FILE_PATH
        --cksum
        --auto-smallupdate
        --check-smallupdate
        --download-smallupdate
        --check-pat ABSOULATE_UPGRADE_FILE_PATH
        --migration-check-pat ABSOULATE_UPGRADE_FILE_PATH
        --prepare-upgrade-files-to-root
        --prepare-smallupdate-downloaded-info ABSOLUTE_PATH_FOR_PREPARATION
        --get-smallupdate-install-files-path
Failed to synoupgrade --bootup-smallupdate [255]
Exit on error [6] bootup-smallupdate failed...

puls200 · June 3, 2022

I am installing a clean DMS on a 918+ clean disk. I take the PAT file (https://global.download.synology.com/download/DSM/release/7.1/42661-1/DSM_DS918%2B_42661.pat) and get an error "Recoverable" after loading system. With the installation of 920+ everything is fine. Something is wrong in 918+.

DiskStation> cat /var/log/junior_reason*
Exit on error [7] root not matched with junior...
DiskStation> cat /var/log/junior_reason
Exit on error [7] root not matched with junior...
DiskStation> cat /var/log/linux*
START /linuxrc.syno.impl
Insert basic USB modules...
:: Loading module usb-common ... [ OK ]
:: Loading module usbcore ... [ OK ]
:: Loading module xhci-hcd ... [ OK ]
:: Loading module xhci-pci ... [ OK ]
:: Loading module usb-storage ... [ OK ]
:: Loading kernel modules from extensions ...
Loading kmod #0 "mii.ko" for pocopico.r8169 (args: )
Loading kmod #1 "r8169.ko" for pocopico.r8169 (args: )
:: Loading kernel modules from extensions ... [ OK ]
:: Executing "on_boot" custom scripts ...
Running "check-r8169.sh" for pocopico.r8169->on_boot
Loading module r8169 -> Module r8169 loaded succesfully
Ran "check-r8169.sh" for pocopico.r8169->on_boot - exit=0
Running "boot-wait.sh" for redpill-boot-wait->on_boot
Still waiting for boot device (waited 1 of 30 seconds)
Still waiting for boot device (waited 2 of 30 seconds)
Confirmed a valid-looking /dev/synoboot device
Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=0
Running "install_rd.sh" for redpill-misc->on_boot
Starting ttyd, listening on port: 7681
Ran "install_rd.sh" for redpill-misc->on_boot - exit=0
:: Executing "on_boot" custom scripts ... [ OK ]
Extensions processed
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
Insert synorbd kernel module
Insert synofsbd kernel module
Insert sha256 kernel module
Assemble args: -u 0d8e0817:2fb6fac5:3017a5a8:c86610be /dev/sdb1
mdadm: /dev/md0 has been started with 1 drive (out of 16).
Partition Version=9
/sbin/e2fsck exists, checking /dev/md0...
e2fsck 1.44.1 (24-Mar-2018)
/sbin/e2fsck -yvf returns 0
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
Failed to found any patch
No upgrade file found
============upgrade
------------bootup-smallupdate
Failed to AssertFileKeyValueEqual
value1: /etc.defaults/VERSION:smallfixnumber -> 0
value2: /tmpRoot/.syno/patch/VERSION:smallfixnumber => 2
Skip bootup smallupdate, because root is not matched to junior
============bootup-smallupdate
Failed to AssertFileKeyValueEqual
value1: /etc.defaults/VERSION:smallfixnumber -> 0
value2: /tmpRoot/.syno/patch/VERSION:smallfixnumber => 2
Exit on error [7] root not matched with junior...
Fri Jun 3 03:01:27 UTC 2022
/dev/md0 /tmpRoot ext4 rw,relatime,prjquota,rootprjquota,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0

Edited June 3, 2022 by puls200

pocopico · June 3, 2022

3 hours ago, puls200 said:

Failed to AssertFileKeyValueEqual
value1: /etc.defaults/VERSION:smallfixnumber -> 0
value2: /tmpRoot/.syno/patch/VERSION:smallfixnumber => 2
Skip bootup smallupdate, because root is not matched to junior

Hi, did you perform the update to update2 or it came up like this after the install ?

vbz14216 · June 3, 2022

I just toyed around with DS918+ loader yesterday on 5775C+H97(baremetal, clean install, TCRP v0.8) and same Recoverable state problem occurs when I tried to install DSM7.1 with the nano packed pat file. I assume DSM tries to go directly into the newest update whenever it can.

Try disconnecting ethernet connection(WAN) when you're prompted to upload the PAT file, I did that and successfully installed DSM.

Edited June 3, 2022 by vbz14216
fix errors

pocopico · June 3, 2022

The temporary fix would be to recreate the ramdisk including the smallupdate version of update2 so select tinycore boot option at GRUB and boot into TCRP.

then copy paste the following in a terminal :

#!/bin/bash

#

# Temp fix for update2

loaderdisk="$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)"

cd /home/tc

mkdir /home/tc/ramdisk

sudo mount /dev/${loaderdisk}1

sudo mount /dev/${loaderdisk}2

cd ramdisk

unlzma -c /mnt/${loaderdisk}2/rd.gz | cpio -idm

cat /mnt/${loaderdisk}1/rd.gz | cpio -idm

find . 2>/dev/null | cpio -o -H newc -R root:root | xz -9 --format=lzma >../rd.gz

cd ..

# add fake sign

dd if=/dev/zero of=rd.gz bs=68 count=1 conv=notrunc oflag=append

sudo cp -f rd.gz /mnt/${loaderdisk}1/rd.gz

rm -rf ramdisk

echo "Done"

###################################################

The update2 pat file payload includes also a kernel image but we are OK without it.

Edited June 3, 2022 by pocopico

pocopico · June 3, 2022

1 hour ago, vbz14216 said:

I just toyed around with DS918+ loader yesterday on 5775C+H97(baremetal, clean install, TCRP v0.8) and same Recoverable state problem occurs when I tried to install DSM7.1 with the nano packed pat file. I assume DSM tries to go directly into the newest update whenever it can.

Try disconnecting ethernet connection(WAN) when you're prompted to upload the PAT file, I did that and successfully installed DSM.

I thought i had that fixed in my repo, but its not for all platforms as this was not required in the past. In the config file of the platform there is an entry for masking updates and have this fixed. I will push that to the repo soon.

@jumkey It will not be a problem for you as you take care of that early at the boot stage.

I will also release an update to the stable release of rploader.sh 0.8.0.0 so that the postupdate works.

EDIT: rploader.sh update 0.8.0.1 includes the postupdate fix for update2.

In case you update to update2 please boot into TCRP and run the following commands :

./rploader.sh update

./rploader.sh postupdate <yourplatform>

Edited June 3, 2022 by pocopico

MajkelP · June 3, 2022

1 hour ago, pocopico said:

EDIT: rploader.sh update 0.8.0.1 includes the postupdate fix for update2.

In case you update to update2 please boot into TCRP and run the following commands :

./rploader.sh update

./rploader.sh postupdate <yourplatform>

Hi,

If I would like update from my working DSM_DS3622xs+_42661 update 1, (currently I am on tinycore-redpill.v0.4.6) to 0.8.0.1 DSM_DS3622xs+_42661 update 2?

Do I need recreate only loader on the same USB stick or something else is required?

Thank you,

pocopico · June 3, 2022

24 minutes ago, MajkelP said:

Hi,

If I would like update from my working DSM_DS3622xs+_42661 update 1, (currently I am on tinycore-redpill.v0.4.6) to 0.8.0.1 DSM_DS3622xs+_42661 update 2?

Do I need recreate only loader on the same USB stick or something else is required?

Thank you,

No need to recreate the loader. It will be a two stage update process.

First update to update2 from DSM GUI

Second boot into TCRP and run

./rploader.sh update now

./rploader.sh fullupgrade now

./rploader.sh backup

./rploader.sh postupdate <yourplatform>

Edited June 3, 2022 by pocopico

ct85msi · June 3, 2022

it doesn`t work on DS918+...it says Recoverable after updating to TCRP 0.8.0.1 and ran postupdate.

pocopico · June 3, 2022

7 minutes ago, ct85msi said:

it doesn`t work on DS918+...it says Recoverable after updating to TCRP 0.8.0.1 and ran postupdate.

what is your junior exit reason ?

ct85msi · June 3, 2022

I don`t understand the question. What junior exit reason ?:)

pocopico · June 3, 2022

Anyway i've found a typo ... i'm pushing the update soon.

TinyCore RedPill Loader (TCRP)

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Join the conversation