Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

1 hour ago, drobik said:

I absolutely agree with you about updates, i am just looking the way to make advanced media extension work, and i think this blocking affects this too.

 

Also one thing that was and might still be an issue, is that after the initial install and the first reboot after that, DSM tries to fetch the latest smallupdate (ie. 7.1 U3), leading to a junior vs root mismatch. That was bypassed also with the update server blocking.

 

Again after that a postupdate or jumkey or arpl solution has to run. Actually if junior version if lower than root, it should be fixed like that.

Edited by pocopico
Link to comment
Share on other sites

3 hours ago, Franks4fingers said:

What version was this updating from? I am running 7.1-42661 as my base. Can I go straight to Update 3 with certain commands?

 

I believe there is no need to install Update 1,2. If you install Update 3 should include the previous updates.

 

You go to the GUI and you install manually the Update 3, when the Syno reboots go back to TinyCore and just run the following command:

./rploader.sh postupdate {WITH YOUR MODEL}

 

  • Like 1
Link to comment
Share on other sites

6 hours ago, gadreel said:

 

I believe there is no need to install Update 1,2. If you install Update 3 should include the previous updates.

 

You go to the GUI and you install manually the Update 3, when the Syno reboots go back to TinyCore and just run the following command:

./rploader.sh postupdate {WITH YOUR MODEL}

 

That simple, thought there was more to it.

 

Many thanks @gadreel

Link to comment
Share on other sites

12 minutes ago, gadreel said:

 

By the way important. Make sure you have the latest tinycore.

 

You might need to also run these commands before postupdate

./rploader.sh update
./rploader.sh fullupgrade

 

Ok so......

 

Update from the GUI within Synology from 7.1-42661 U1 to U3

 

Then reboot, drop into TCRP and go with the following:

 

./rploader.sh update

./rploader.sh fullupgrade

./rploader.sh postupdate apollolake-7.1-42661

 

Is that last command right?

Link to comment
Share on other sites

On 7/10/2022 at 6:51 PM, SanKen said:

question for you

if the question for me? so..

after manual update just reboot to TC from USB

and open the terminal app and type flowing commands

need backup from user_config.json because after fullupdating this file is overwritten from repo by default

cp user_config.json backup.json
./rploader.sh fullupgrade now

then after full update script files copy backup json file  (overwrite the file) by:

cp backup.json user_config.json

then run

./rploader.sh postupdate apollolake-7.1-42661

and type Yes for add redpill entry to grub.cfg by automatically.... after the process is done just reboot and run redpill from grub menu!

Link to comment
Share on other sites

Hello everyone,

 

Someone can tell me if i can install driver of Adaptateur USB 3.0 Ethernet Gigabit RJ45 or if is plug and play?

The chipset is RTL8153

My motherboard has only one RJ45 and i can't plug RJ45 card on PCI-e...

 

I want plug 2 Adaptateurs USB 3.0 but i don't know if it's à great idee...

 

Many thanks in advance for answers!!

 

Link to comment
Share on other sites

21 hours ago, loveburn said:

after manual update just reboot to TC from USB

yes. but how to do this without display.

 

How to deal with yourself when it is Recovery Loop

 

21 hours ago, loveburn said:

if the question for me? so..

To all. bad, bad english. Sorry :(

Link to comment
Share on other sites

1 час назад, SanKen сказал:

yes. but how to do this without display.

 

How to deal with yourself when it is Recovery Loop

Before Recovery Loop 😀:

1) mount synoboot_part0 and edit grub.cfg (https://xpenology.com/forum/topic/14032-редактирование-grubcfg-и-замена-extralzma-на-флешке-на-работающей-хрени/) - You need to edit grub.cfg so that the menu item 'Tiny Core Image Build' is selected by default. For example, after these lines:

if [ -s $prefix/grubenv ]; then
    load_env --file $prefix/grubenv --skip-sig
    set has_env="1"
    if [ -n "${saved_entry}" ]; then
        set default="${saved_entry}"
    fi
else
    set has_env="0"
    echo "WARN: failed to load env. Default choice will NOT be saved!"
fi

insert a line:

set default="2"

(menuentry 'Tiny Core Image Build')

2) "You go to the GUI and you install manually the Update 3", reboot DSM to image build mode, connect via SSH, make an update

3) change the added line in grub.cfg to: set default="0"

(menuentry 'RedPill DS... (USB, Verbose)')

4) reboot to DSM, mount synoboot_part0, delete the added line from grub.cfg

 

After Recovery Loop: keyboard&display or preparing a new USB-flash and loading from it. ☹️

  • Like 1
Link to comment
Share on other sites

5 часов назад, SanKen сказал:

yes. but how to do this without display.

 

you can put flash to your PC and try to boot TC on your PC , make changes like in my post and put flash disk to your NAS again and boot DSM)

i think it's simple way to solve problem (NO DISPLAY)

Edited by loveburn
  • Like 1
Link to comment
Share on other sites

Confirmed - Update 3 using below steps!! Thanks Everyone!!

 

Manual update from the GUI within Synology from 7.1-42661 to U3

https://archive.synology.com/download/Os/DSM/7.1-42661-3

 

Then reboot, drop into TCRP and go with the following:

 

./rploader.sh update now

./rploader.sh fullupgrade

./rploader.sh postupdate broadwellnk-7.1.0-42661

 

  • Thanks 1
Link to comment
Share on other sites

Hi @ all

 

i have a 3622 with 7.1.0-42661 U3 running on a old r710 with ESXi 6.5 U3.

So far it runns stable and with tcrp all updates working.

i found i the vm.log, (syslog from synology) a lot of them:

 

AHCI-VMM:Aborting the command: 0xb0

 

this message i get for every drive in the system.

 

anyone who knows how to solve that?

 

greets 

Link to comment
Share on other sites

Are the drive temps reported thru dms, using redpill, HBA with pci passthrough in proxmox vm, accurate? or is the data shimmed or spoofed?

I remember reading certain smart data is spoofed or shimmed in redpill, and I am not sure if this is accurate.  My DS3622XS+ redpill build is in proxmox, with an HBA passthru to the DSM VM. I can accurately see s/n of drives, just not 100% sure about temp. Hoping @pocopico or @flyride can answer for sure for me.  Thanks.

image.thumb.png.691f12269dd01081ecb436cc4408d43f.png

Link to comment
Share on other sites

11 hours ago, phone guy said:

Are the drive temps reported thru dms, using redpill, HBA with pci passthrough in proxmox vm, accurate? or is the data shimmed or spoofed?

I remember reading certain smart data is spoofed or shimmed in redpill, and I am not sure if this is accurate.  My DS3622XS+ redpill build is in proxmox, with an HBA passthru to the DSM VM. I can accurately see s/n of drives, just not 100% sure about temp. Hoping @pocopico or @flyride can answer for sure for me.  Thanks.

image.thumb.png.691f12269dd01081ecb436cc4408d43f.png

with an hba in passthrough you get the real smart, if you rdm pass the disk and leave the hba on the host then you get fake smart.

  • Thanks 1
Link to comment
Share on other sites

Good afternoon! I bought an ASRock J4125-itx motherboard, put 1 ddr4 ram 8 gb, hdd WD Purple 1 Tb on it. I created the loader as follows:

./rploader.sh update
 ./rploader.sh fullupgrade
 ./rploader.sh identifyusb
 ./rploader.sh satamap
 ./rploader.sh serialgen DVA1622 realmac
 ./rploader.sh ext dva1622-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/r8152/rpext-index.json
 ./rploader.sh builddva1622-7.1.0-42661
 ./rploader.sh backup now
 sudo reboot

 

After that, I go to finds.synology.com in the browser, find my NAS, accept the agreements, then redirect to the IP address of the NAS, but the NAS setup page becomes unavailable.

In the interface of the router, the NAS has the status not available (before that, when assembling the bootloader, it was available and received an IP address from the router). What have I done wrong? Thank you!

Link to comment
Share on other sites

Hello

 

I did upgrade 918+ from 7.1.0 U2 to U3. It was successful. Then I add one more hdd to the syno. The DSM didnt found it.

I thought I make one new loader. I built one new 918+ 7.1.0 loader. All are successful, oh not. The DSM didnt boot.

 

Ok, I tired postupdate. But it is unsuccessful, it found:

 

Found Version : 7.1-42661-0
Do you want to use this for the loader ? [yY/nN] :

 

It didnt fount the U3.

 

What can I do now? How can I fix this?

 

Thanks!

Link to comment
Share on other sites

5 minutes ago, RedCat said:

Hello

 

I did upgrade 918+ from 7.1.0 U2 to U3. It was successful. Then I add one more hdd to the syno. The DSM didnt found it.

I thought I make one new loader. I built one new 918+ 7.1.0 loader. All are successful, oh not. The DSM didnt boot.

 

Ok, I tired postupdate. But it is unsuccessful, it found:

 

Found Version : 7.1-42661-0
Do you want to use this for the loader ? [yY/nN] :

 

It didnt fount the U3.

 

What can I do now? How can I fix this?

 

Thanks!

D you have hot plug enabled in your BIOS? The system should have recognized the new hard drive without the need to rebuild the loader.

How many HDDs do you currently have connected?

Link to comment
Share on other sites

Yes, hot plug is enabledin the bios, 4 hdd work perfectly. I disconnected the 5th hdd, but the systen don't boot.

 

I think, i did big mistake with the new loader creation.

We forget the 5th hdd, first we try to fix the boot process.

 

Thank you!

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