Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

7 hours ago, Trabalhador Anonimo said:

 

Your NIC is Realtek RTL8111GR

For Ryzen (AMD) system, it is suggest to use DS1621+: look at the table on post #1

Also, AMD systems, at least mine, does not handle "withfriend".

 

Hi,

Thanks for your quick answer. Sadly I can't make it work :

 

I tried again like this:

Quote

./rploader.sh clean

./rploader.sh update

./rploader.sh fullupgrade

./rploader.sh serialgen DS1621+ realmac

./rploader.sh satamap

./rploader.sh identifyusb

./rploader.sh ext ds1621p-7.1.1-42962 auto

./rploader.sh build ds1621p-7.1.1-42962

exitcheck.sh reboot

 

It's stuck on :

Quote

Loading Linux...

Loading initramfs...

Starting kernel with USB boot

_

 

Nothing is happening, no ethernet activity either :(

Link to comment
Share on other sites

10 hours ago, Trabalhador Anonimo said:

Hi,

AMD system is not SataMap, it is device tree. I do not know if it has anything to do it, but it worth to try, so forget about "./rploader.sh satamap" command.

Thanks!

 

I'm about this close (picture a tinyyyyy space) to give up and go with openmediavault 😢

Link to comment
Share on other sites

В 04.03.2023 в 11:10, Igareok сказал:

Hello. I need to use DSM 7.0.1

I try to build loader for DS3615, or DS3622xs+, but its end with same error>

[#] 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
100  389M  100  389M    0     0  10.3M      0  0:00:37  0:00:37 --:--:-- 11.4M
[#] Verifying /home/tc/redpill-load/cache/ds3622xsp_42218.pat file... [ERR]
[!] Checksum mismatch - expected f38329b8cdc5824a8f01fb1e377d3b1b6bd23da365142a01e2158beff5b8a424 but computed a222d37f369d71042057ccb592f40c7c81e9b988a95d69fa166c7c2a611da99c

*** Process will exit ***
FAILED : Loader creation failed check the output for any errors

And this problem persist only on 7.0.1-42218 and 7.0.1-42218-JUN version.

Tried different USB sticks, different loader versions, different motherboards, every time - same error.

Please help.

The same issue with latest at the moment "tinycore-redpill-uefi.v0.9.4.5.img" for DS918+. Looks like synology changed the pat files with DSM_xxxxxx_42218 version and to fix the error "Checksum mismatch" during bilding process the checksum in installation script has to be updated but how to do it?.....

Please help

Link to comment
Share on other sites

6 hours ago, navhawk said:

The same issue with latest at the moment "tinycore-redpill-uefi.v0.9.4.5.img" for DS918+. Looks like synology changed the pat files with DSM_xxxxxx_42218 version and to fix the error "Checksum mismatch" during bilding process the checksum in installation script has to be updated but how to do it?.....

Please help

 

7.0.1-42218 U0 DSM PAT file has been changed in the middle. So, the sha256 checksum value has also been changed.
TCRP's config.json must be updated with the changed checksum value.
M SHELL for TCRP will be notified again once the update process is complete.
I hope that pocopico also takes and reflects my config related to 7.0.1-42218.

Link to comment
Share on other sites

21 hours ago, navhawk said:

The same issue with latest at the moment "tinycore-redpill-uefi.v0.9.4.5.img" for DS918+. Looks like synology changed the pat files with DSM_xxxxxx_42218 version and to fix the error "Checksum mismatch" during bilding process the checksum in installation script has to be updated but how to do it?.....

Please help

 

The config job for version 7.0.1-42218 is complete.
Pocopico's TCRP cannot build 7.0.1 until the config process is in progress.

 

How to switch to my M SHELL for TCRP
Run the command below inside Tinycore Linux.
A menu like the one below will appear where you can build the loader with the menu.

 

curl -kLO https://raw.githubusercontent.com/PeterSuh-Q3/tinycore-redpill/master/my.sh.gz
tar -zxvf my.sh.gz
./menu.sh

 

If you want to see the same screen as the screenshot, make a backup with the command below and restart.


./rploader.sh backup
sudo reboot

 

10234776_2023-05-0211_50_09.thumb.png.aad06c49de28e769f5490fd34b39cdde.png

Link to comment
Share on other sites

Gentle peeps,

I'm trying to get a NUC11 running which is reported an as a NUC11TNHv5/NUC11TNBv5. Had to wait forever for a serial port adapter for the NUC to arrive, so now I can finally see what is happening underneath. NUC11 has an nvme disk (which is not being used as of yet) and two sata disk (module and 2.5" disk) which will service as the DSM base disks. The sata disks are indeed detected when mapping using satamap.

 

When building for example building ds3622xsp-7.1.1-42962 (using TCRP v0.9.4.5) I add the igc module. but I don't see it when looking at the serial console booting USB
 

./rploader.sh serialgen DS3622xs+
./rploader.sh identifyusb now
./rploader.sh satamap now
# the internal Intel I225-LM
./rploader.sh ext ds3622xsp-7.1.1-42962 add https://raw.githubusercontent.com/pocopico/rp-ext/main/igc/rpext-index.json
# used an external usb-c ethernet dongle as well
./rploader.sh ext ds3622xsp-7.1.1-42962 add https://raw.githubusercontent.com/pocopico/rp-ext/main/r8152/rpext-index.json
./rploader.sh build ds3622xsp-7.1.1-42962

 

serial console on another machine:

Loading Linux...
Loading initramfs...
Starting kernel with USB boot
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Initializing cgroup subsys cpuacct
[    0.000000] Linux version 4.4.180+ (root@build13) (gcc version 8.5.0 (GCC) ) #42962 SMP Sat Sep 3 22:22:16 CST 2022
[    0.000000] Command line: BOOT_IMAGE=/zImage withefi earlyprintk syno_hw_version=DS3622xs+ console=ttyS0,115200n8 netif_num=1 pid=0xa4a5 earlycon=uart8250,io,0x3f8,115200n8 syno_port_thaw=1 mac1=48210B360286 sn=2030SQRYWCV3F vid=0x0525 elevator=elevator loglevel=15 HddHotplug=0 DiskIdxMap=00 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 log_buf_len=32M root=/dev/md0 SataPortMap=2
[    0.000000] KERNEL supported cpus:
[    0.000000]   Intel GenuineIntel
....
....
[    0.667967] pci_bus 0001:0c: busn_res: can not insert [bus 0c-ff] under domain [bus 00-ff] (conflicts with (null) [bus 09-ff])
[    0.668947] pci_bus 0001:0c: root bus resource [bus 00-ff]
[    0.669446] pci 0001:0c:00.0: [1b4b:9235] type 00 class 0x010601
[    0.669973] pci 0001:0c:00.0: Can't map mv9235 registers
[    0.670422] ahci: probe of 0001:0c:00.0 failed with error -22
[    0.671086] console [ttyS0] disabled


And it just sits there forever. This is pbl the final message when no network is detected as the next logs will be triggered from a network event.

 

But when I use the RedPill DS3622xs v7.1.1-42962 Beta (SATA, Verbose) boot option I do sometimes see the modules being started (the onboard Intel igc and the r8152 dongle) but understandable it will just error out at some point waiting for the boot device since I did not install anything yet. 

 

Can someone confirm explain what is going on here with the modules.

* Has this to do with the 7.1.1 version (other gave me different problems when building working with the v0.9.4.5)

* Is the hardware init on cold/warm boots? I have not figured it out yet.

* And it will indeed just sit there on the "console [ttyS0] disabled" when no network is detected?

 

Any hints how to get it working?

 

I know it is able to init. The ARPL is for example able to init the module everytime, I see way more on the serial console and it gives me a web interface. It will error out on a lot of different stuff though. Would be nice to make a clean TCRP install.

 

Cheers,

Martijn

 

 

Edited by Martijn
Link to comment
Share on other sites

Hi, I was on building loader for RS4021xs+ 7.2, on a gen8 server with microsd 8 gbyte card card,but it seems that TCRP has some space problem 

 

Mounting /dev/sdc1 to localdiskp1
Mounting /dev/sdc2 to localdiskp2
cp: error writing 'localdiskp1/rd.gz': No space left on device
cp: error writing 'localdiskp1/zImage': No space left on device
Replacing set root with filesystem UUID instead
sed: couldn't flush localdiskp1/boot/grub/sednFt9Pw: No space left on device
Creating tinycore entry
menuentry 'Tiny Core Image Build' {
        savedefault
        search --set=root --fs-uuid 6234-C863 --hint hd0,msdos3
        echo Loading Linux...
        linux /vmlinuz64 loglevel=3 cde waitusb=5 vga=791
        echo Loading initramfs...
        initrd /corepure64.gz
        echo Booting TinyCore for loader creation
}
Entries in Localdisk bootloader :
=======================================================================
menuentry 'RedPill RS4021xs+ v7.2.0-64551 Beta (USB, Verbose)' {
menuentry 'RedPill RS4021xs+ v7.2.0-64551 Beta (SATA, Verbose)' {
menuentry 'Tiny Core Image Build' {
Updated user_config with USB Command Line : withefi earlyprintk syno_hw_version=RS4021xs+ console=ttyS0,115200n8 netif_num=1 pid=0x4030 earlycon=uart8250,io,0x3f8,115200n8 syno_port_thaw=1 mac1=D0BF9C459480 sn=2250T2RB8WPWA vid=0x0424 elevator=elevator loglevel=15 HddHotplug=0 DiskIdxMap=00 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 log_buf_len=32M root=/dev/md0 SataPortMap=1
Updated user_config with SATA Command Line : withefi earlyprintk syno_hw_version=RS4021xs+ console=ttyS0,115200n8 netif_num=1 pid=0x4030 earlycon=uart8250,io,0x3f8,115200n8 synoboot_satadom=1 syno_port_thaw=1 mac1=D0BF9C459480 sn=2250T2RB8WPWA vid=0x0424 elevator=elevator loglevel=15 HddHotplug=0 DiskIdxMap=00 syno_hdd_detect=0 vender_format_version=2 syno_hdd_powerup_seq=0 log_buf_len=32M root=/dev/md0 SataPortMap=1
Cleaning up files
Caching files for future use
No adequate space on TCRP loader partition /mnt/sdc3 to cache pat file
Found /mnt/sdc3/auxfiles/rs4021xsp_64551.pat file
Removing older cached pat files to cache current
Found /home/tc/redpill-load/cache/rs4021xsp_64551.pat, copying to cache directory : /mnt/sdc3/auxfiles
Saving user session for future use. Saving current extensions  -> OK !
Saving current user_config.json  -> OK !

 

Link to comment
Share on other sites

For the life of me, I can't seem to get all 8 drives connected to my HBA to show up in dsm.

 

Using Proxmox with PCIe passthrough for my HBA. The only drive I need are the ones attached to the HBA

Here's the output of ./rploader.sh satamap now

 

Machine is VIRTUAL Hypervisor=KVM
Found SCSI HBAs, We need to install the SCSI modules
scsi-5.10.3-tinycore64 is already installed!
Succesfully installed SCSI modules

Found "00:1f.2 Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)"
Detected 6 ports/0 drives. Mapping KVM q35 bogus controller after maxdisks

Found "06:07.0 Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)"
Detected 6 ports/1 drives. Mapping SATABOOT drive after maxdisks

Found SCSI/HBA "01:00.0 LSI Logic / Symbios Logic SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05)" (7 drives)

Computed settings:
SataPortMap=11
DiskIdxMap=0C0C

 

Only the first three drives, in random order, show up in dsm.

 

I've tried..

SataPortMap=11

DiskIdxMap=0C0C

 

SataPortMap=01

DiskIdxMap=1010

 

SataPortMap=001

DiskIdxMap=000000

 

SataPortMap=008

DiskIdxMap=000000

 

 

I've read that sataportmap defines how many ports on each host is being used. So in this situation, I would, in theory, use SataPortMap=008, since I only need the 8 port from the HBA. Am I getting this right?

 

Link to comment
Share on other sites

Hello all, tried to build the loader for DS918+ with latest rp v0.9.4.5 but nothing worked 😪 :

for ds918p-7.2.0-64551 - no config file error

for ds918p-7.1.1-42962 - checksum mismatch error

Has anybody managed to build the loader with the latest version of RP? Has something changed in the build process?

Maybe I am doing something wrong but the process was very simple before and worked perfectly...

 

Link to comment
Share on other sites

Short version: Is is possible to set display resolution when booting tinycore?

 

Long version: I have just got a Pikvm v4 connected to my xpenelogy for remote management etc. the kvm shows the video connection etc is all good however i dont get display int he kvm window. After some discussions with the pikvm folks, we think it could be display resolution related(The kvm windows shows me inacive display with a 640x480 resolution)Though that doesnt explain why i donte even see the POST display for the xpenology but anyways i would like to see if its its possible to set the display resolution for when TC boots up.

Link to comment
Share on other sites

Hey guys, I need some help. I got a Dell Poweredge T20 that keeps giving me bad ports and its detecting 6 ports when only having 4 ports on the board. I ignore this and manually edit the user_config file setting disksatamap to "4" and diskmap to "00". I run the build and I see a checksum error, and gives a jumbled mess of letters and numbers. The build finishes, I backup, and reboot.  Oh and I also added withfriend. When I went to install dsm, it showed the 4 drives that I have filling the 4 actual sata ports. I upload the file, click to install and the install finishes. But after awhile I realize that it brings me back to the "welcome" as if I just turned it on after finishing the build. Any ideas? Thanks.

Edited by Dvalin21
Update: I was originally trying to install 3622xs+, but then switched to 923+..it actually installed (also did withfriend)
Link to comment
Share on other sites

17 hours ago, Dvalin21 said:

Hey guys, I need some help. I got a Dell Poweredge T20 that keeps giving me bad ports and its detecting 6 ports when only having 4 ports on the board. I ignore this and manually edit the user_config file setting disksatamap to "4" and diskmap to "00". I run the build and I see a checksum error, and gives a jumbled mess of letters and numbers. The build finishes, I backup, and reboot.  Oh and I also added withfriend. When I went to install dsm, it showed the 4 drives that I have filling the 4 actual sata ports. I upload the file, click to install and the install finishes. But after awhile I realize that it brings me back to the "welcome" as if I just turned it on after finishing the build. Any ideas? Thanks.

 

Can you show me the capture or log again in which part specifically the checksum error is coming out?

Link to comment
Share on other sites

On 5/16/2023 at 2:59 PM, alirz1 said:

Short version: Is is possible to set display resolution when booting tinycore?

 

Long version: I have just got a Pikvm v4 connected to my xpenelogy for remote management etc. the kvm shows the video connection etc is all good however i dont get display int he kvm window. After some discussions with the pikvm folks, we think it could be display resolution related(The kvm windows shows me inacive display with a 640x480 resolution)Though that doesnt explain why i donte even see the POST display for the xpenology but anyways i would like to see if its its possible to set the display resolution for when TC boots up.

ideally would be to stay in text mode similar to ARPL

Link to comment
Share on other sites

[NOTICE]

 

The functionality of cgetty has been further developed.


Depending on the situation, if key-in is impossible, you cannot log in as root.

 

So I added more processing like below.

 

cat /var/log/linuxrc.syno.log > /dev/tty1

 

Even if keying is not possible, the log you see now is the last part of the result of the above command.

 

Capture the above contents to a developer capable of log analysis and request an error analysis.

 

The loader needs to be rebuilt for the Getty Console to look like the one below.

 

2023-05-2011_39_57.thumb.png.426608de38516fcc806f8e183ee70359.png

 

 

2023-05-2011_53_24.thumb.png.7ac6a49cc772ca67918cf27e5e706a22.png

Link to comment
Share on other sites

5 hours ago, Peter Suh said:

 

Can you show me the capture or log again in which part specifically the checksum error is coming out?

Sorry, as I stated in my update, after switching to 923+ it installed. I didn't go back and try 3622xs+. The hardware was E3-1225 Intel Sata controller C220, which was suppose to have 6 sata ports, but only had 4. When I installed 923+, I made sure all satamap was 4 and Disk was 00. 

Link to comment
Share on other sites

5 minutes ago, Dvalin21 said:

Sorry, as I stated in my update, after switching to 923+ it installed. I didn't go back and try 3622xs+. The hardware was E3-1225 Intel Sata controller C220, which was suppose to have 6 sata ports, but only had 4. When I installed 923+, I made sure all satamap was 4 and Disk was 00. 

 

Since DS923+ is a Device-Tree based model, SataportMap is not used.

Link to comment
Share on other sites

6 minutes ago, Peter Suh said:

 

Since DS923+ is a Device-Tree based model, SataportMap is not used.

That would make since on why it worked. If it helps at all the checksum also said mismatch. There rest was a mile long. I can also say I didn't have this issue with the previous version 9.43.

Link to comment
Share on other sites

Hi all,

I have a problem with disk recognition.
This is my scenario:
I have a 2U server rack with 12bay connected to an LSI 3008 controller. VMware ESXi 7.0.3 is installed in the server. DSM is installed in a virtual machine with the LSI controller in passthrough. I followed this guide: https://xpenology.com/forum/topic/62547-tutorial-install-dsm-7x-with-tinycore-redpill-tcrp-loader-on-esxi/

 

 

2023-05-2009_13_14-Window.thumb.png.dc7a271cc2f71eae057fa2d59af070c2.png

So I have 2 SATA controllers and the LSI 3008 controller where the physical disks are connected. At the moment I have only 3 disks connected (/dev/sdn, /dev/sdo and /dev/sdp) and they are recognized.
If I add a disk (can I do it hotplug?) I see it via shell ssh, but DSM does not see it.

In my case I added a WD red 3TB disk as a test and the system recognizes it as /dev/sdq

 

root@NAStore:~# fdisk -l |grep /dev/sd
Disk /dev/sda: 21 GiB, 22548578304 bytes, 44040192 sectors
/dev/sda1           8192 16785407 16777216   8G fd Linux raid autodetect
/dev/sda2       16785408 20979711  4194304   2G fd Linux raid autodetect
Disk /dev/sdn: 14.6 TiB, 16000900661248 bytes, 31251759104 sectors
/dev/sdn1      8192    16785407    16777216    8G Linux RAID
/dev/sdn2  16785408    20979711     4194304    2G Linux RAID
/dev/sdn3  21241856 31251554303 31230312448 14.6T Linux RAID
Disk /dev/sdo: 14.6 TiB, 16000900661248 bytes, 31251759104 sectors
/dev/sdo1      8192    16785407    16777216    8G Linux RAID
/dev/sdo2  16785408    20979711     4194304    2G Linux RAID
/dev/sdo3  21241856 31251554303 31230312448 14.6T Linux RAID
Disk /dev/sdp: 14.6 TiB, 16000900661248 bytes, 31251759104 sectors
/dev/sdp1      8192    16785407    16777216    8G Linux RAID
/dev/sdp2  16785408    20979711     4194304    2G Linux RAID
/dev/sdp3  21241856 31251554303 31230312448 14.6T Linux RAID
Disk /dev/sdq: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors

 

Question: why do the unit letters of the LSI controller start from sdn for me? What did I do wrong?

 

 

2023-05-2009_21_05-Window.thumb.png.ba8b63d7e796fbea8d581b183a18c130.png

At this moment I have install DSM 7.1.1-42962 Update 5 with TCRP 0.9.4.4

 

Can you help me out so I can see the other disks (potentially 9 more  of 12 supported by the server)? Thanks

Link to comment
Share on other sites

Greetings to all. TCRP is used on ordinary hardware. Thank you for your work. But I've been trying to get it to work on my HP DL380P G8 for a couple of days now, and all without success Could you help me. Whatever I do, DSM doesn't see my disks. I am using an HP Smart Array P420i with 12 SATA drives connected to it.

 

Цитата

tc@box:~$ ./rploader.sh satamap now
Found SCSI HBAs, We need to install the SCSI modules
scsi-5.10.3-tinycore64 is already installed!
Succesfully installed SCSI modules

Found SCSI/HBA "02:00.0 Hewlett-Packard Company Smart Array Gen8 Controllers (rev 01)" (12 drives)
lspci: -s: Invalid slot number
Found SCSI/HBA "" (0 drives)
lspci: -s: Invalid slot number
Found SCSI/HBA "" (0 drives)
lspci: -s: Invalid bus number
Found SCSI/HBA "" (0 drives)
lspci: -s: Invalid slot number
Found SCSI/HBA "" (0 drives)
lspci: -s: Invalid slot number
Found SCSI/HBA "" (0 drives)
lspci: -s: Invalid slot number
Found SCSI/HBA "" (0 drives)
lspci: -s: Invalid slot number
Found SCSI/HBA "" (0 drives)
lspci: -s: Invalid slot number
Found SCSI/HBA "" (0 drives)
lspci: -s: Invalid slot number
Found SCSI/HBA "" (0 drives)
lspci: -s: Invalid slot number
Found SCSI/HBA "" (0 drives)
lspci: -s: Invalid slot number
Found SCSI/HBA "" (0 drives)

Computed settings:
SataPortMap=1
DiskIdxMap=00

Should i update the user_config.json with these values ? [Yy/Nn] y
Done.

 

dsm.png

Edited by extreen
Link to comment
Share on other sites

3 hours ago, extreen said:

Greetings to all. TCRP is used on ordinary hardware. Thank you for your work. But I've been trying to get it to work on my HP DL380P G8 for a couple of days now, and all without success Could you help me. Whatever I do, DSM doesn't see my disks. I am using an HP Smart Array P420i with 12 SATA drives connected to it.

 

 

dsm.png

 

Your best chance for SCSI disks would be DS3622xs+ , Try latest TCRP and lets see how it goes

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...