TinyCore RedPill Loader (TCRP)

Mentat · September 7, 2022

Yes, 6, but now find synology can detect my station and this is not responding for

http://192.168.1.xx/?privacy_confirmed=true&_dc=1662553987723

nemesis122 · September 7, 2022

On 9/7/2022 at 7:35 PM, Mentat said:

1. There are 4 main HDD.

2. I use the MicroSD card

3. The script detects 6 ports, but I only use 4 HDD. Should I use 4 or 6 in the config?

I get corrupted file at ~40%.

Do you have checkedthat the VID and PID is correct from your SD Card in the Loader grub.cfg ? Maybe the identitfy Command:

./rploader.sh identifyusb now

checked the usb and NOT the SD Card .... or try with en usb stick and rebuild the loader again or you can use/try arpl Loader

nemesis122 · September 7, 2022

Ok :

build a new Loader :

with this command because with manual the addional drivers will not be added:

- [DS3622xs+]

./rploader.sh update now
./rploader.sh fullupgrade now
./rploader.sh serialgen DS3622xs+
./rploader.sh identifyusb now
./rploader.sh satamap now
./rploader.sh build broadwellnk-7.1.0-42661 auto
./rploader.sh clean now
./rploader.sh build broadwellnk-7.1.0-42661 auto

and check that the VID and PID from your usb stick is correct in the grub.cfg for USB Booting / when you use your SD card as Bootdevice the VID and PID in the grub.cfg must be excatly the same as your VID and PID on the SD Card

Could you show your grub.cfg here in the forum or send me as private message

pigr8 · September 8, 2022

20 hours ago, Mentat said:
There are a lot of post here and I do not know where to look.

What version do I need to choose?

- DS3615XS

- What 7.1.xxx DSM?

Hardware: Hp Microserver Gen8, Xeon processor, original NIC.

I try to install DSM 7.1, but it fails on pat file upload.
sudo -i

./rploader.sh update now

./rploader.sh fullupgrade now

./rploader.sh serialgen DS3615xs realmac

./rploader.sh identifyusb now

./rploader.sh satamap now

(6 PORTS)

./rploader.sh ext bromolow-7.1.0-42661

./rploader.sh build bromolow-7.1.0-42661
./rploader.sh clean now

rm -rf /mnt/sdb3/auxfiles;  rm -rf /home/tc/custom-module; 

sudo reboot

i use the Microserver Gen8 (e3-1265L, 16gb ecc, 4x3tb + 1 250gb ssd) baremetal with a DS1520+ build and works perfectly.

Mentat · September 8, 2022

On 9/7/2022 at 8:08 PM, nemesis122 said:
Ok :

build a new Loader :

with this command because with manual the addional drivers will not be added:

- [DS3622xs+]
./rploader.sh update now
./rploader.sh fullupgrade now
./rploader.sh serialgen DS3622xs+
./rploader.sh identifyusb now
./rploader.sh satamap now
./rploader.sh build broadwellnk-7.1.0-42661 auto
./rploader.sh clean now
./rploader.sh build broadwellnk-7.1.0-42661 auto
and check that the VID and PID from your usb stick is correct in the grub.cfg for USB Booting / when you use your SD card as Bootdevice the VID and PID in the grub.cfg must be excatly the same as your VID and PID on the SD Card

Could you show your grub.cfg here in the forum or send me as private message

I see that this command is executed twice, is this correct?

./rploader.sh build broadwellnk-7.1.0-42661 auto

After running all the comands above, I have this in the user_config.json

{
  "extra_cmdline": {
    "pid": "0x4030",
    "vid": "0x0424",
    "sn": "2150xxxxxxLZVN",
    "mac1": "0011322B4B33",
    "SataPortMap": "6",
    "DiskIdxMap": "00"
  },
  "synoinfo": {
    "internalportcfg": "0xffff",
    "maxdisks": "16",
    "support_bde_internal_10g": "no",
    "support_disk_compatibility": "no",
    "support_memory_compatibility": "no"
  },
  "ramdisk_copy": {}
}

Same damn error

Mentat · September 8, 2022

DUMB question...

I've just read a tutorial that says to use the offial PAT file to upload on the last step, NOT the one created by TC and downloaded via WiSCP

Is this true?

:facepalm:

mmkt · September 8, 2022

yes

nemesis122 · September 8, 2022

Hi How is the system configured ? in special the Sata and the Raid Controller ?

Is the sata controller in the AHCi Mode ?

Do you have tested with en USB Stick because about the VID and PID ?

When you build the loader with tinycore redpill there is a loader.img that can be download with WINSCP and the open with OSF Mount for check that the VID and PID is corret relaeted to the VID and PID for the usb stick or SD card

i think it is here

/home/tc/redpill-load/cache/

Have a look and let me know we will do a teamviewer session and check what is the problem maybe on friday evening?

-check the bios settings

-check the loader config.

-recreate the loader with img file with OSF mount

Have a look

https://xpenology.club/install-dsm-7-on-baremetal-or-vm/

skywalker · September 8, 2022

Hi everyone, can someone help me please?

I had Jun loader on dsm 6, and now I want to migrate to redpill 7.

So, I follow upgrade instructions, but SynologyAssistant show status "Not Installed" instead migratable.

Sata settings in grub I took from Jun, cause autodetect works wrong for me.

So I have motherboard with 6 sata + 2 sata on separate chip (Asmedia?) + HBA LSI with 4 ports.

All together 12 drives.

For this LSI autodetect show only 2 ports available.

Settings:

SataPortMap=624

DiskIdxMap=000608

SasIdxMap=0

Installing DS918+ (was the same)

Tried different versions (7.0-7.1)

Thanks in advance.

Edited September 8, 2022 by skywalker

Itay1778 · September 8, 2022

On 9/6/2022 at 10:15 PM, apriliars3 said:

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

./rploader.sh serialgen DS918+
./rploader.sh identifyusb now #only baremetal
./rploader.sh satamap now #optional

./rploader.sh build apollolake-7.0.1-42218-JUN

sudo reboot

Fresh install to DSM 7.1.0-42661 and then update to DSM 7.1.1-42962. Works perfectly.

I tried to do it exactly according to what you wrote here, and it doesn't work for me. DSM failed to install.
I also re-burned the USB device and formatted the drives.
Just to be clear, I'm trying to upload: DSM_DS918+_42661.pat file
to apollolake-7.0.1-42218-JUN
Do you have any idea what to do?
Because if it doesn't work I'll just wait for TCRP to update...

apriliars3 · September 8, 2022

1 hour ago, Itay1778 said:

I tried to do it exactly according to what you wrote here, and it doesn't work for me. DSM failed to install.
I also re-burned the USB device and formatted the drives.
Just to be clear, I'm trying to upload: DSM_DS918+_42661.pat file
to apollolake-7.0.1-42218-JUN
Do you have any idea what to do?
Because if it doesn't work I'll just wait for TCRP to update...

pid/vid pendrive incorrect or .pat Download Center - DS918+ | Synology Inc.

Kaneske · September 9, 2022

@pocopicosome say TCRP won’t work with latest release?

Can you confirm that or will it be safe to update through GUI and run the post Install Process as done before as usual?

Does TCRP need an update or is that already done yet?

thanks in Advance for your reply!

pocopico · September 9, 2022

1 hour ago, Kaneske said:

Can you confirm that or will it be safe to update through GUI and run the post Install Process as done before as usual?

Does TCRP need an update or is that already

It should work~~, you cannot though create a new loader for 42962 yet.~~ and you should now be able to also create a new loader for 42962 as well.

Edited September 9, 2022 by pocopico

nutter · September 9, 2022

Spoiler

Hi fellow XPenologists,

Hopefully the question is not redundant, but I don't think I saw this anywhere.

What's a reliable way to set USB drives as internal with Redpill? Similarly to how I've done it before using esataportcfg/usbportcfg/internalportcfg masks in synoinfo.conf. Apparently that doesn't work anymore and the file gets overwritten during boot.

I saw that there's a section in user_config.json for "synoinfo", and I was able to add a usbportcfg mask as 0x0, which made the drives no longer detectable, however the default internalportcfg mask, which is 0xffff doesn't seem to apply to them. Extending the internalportcfg mask to e.g. 0xffffffff and maxdisks to 24, respectively has not worked and the internalportcfg mask is set to 0xffff in synoinfo every time. My sataportmap and USB vid/pids are auto-detected already.

For context, I'm running bromolow-7.1.0_42661 on a KVM VM in Proxmox 7. I have added virtio, acpid and misc modules from pocopico's repo. Prior to restoring the VM from backup the other day and accidentally nuking my data drives (which were RAW drive files on Proxmox directory shares) I didn't have this problem as the drives were emulated as internal, but now I want to attach them as USB drives again, similarly to how I have done with 6.x and prior.

The two USB drives used to appear as internal drives 21 and 22, if that helps. Currently, they show up as /dev/sdu and /dev/sdv, so I'm not sure what lettering offset rule applies here.

Thanks in advance for any insight.

Never mind, I solved it. This happens to me: I try something a million times, it doesn't work, I post a topic/ask for help, try once again and it works... :-).

If it might help anyone, here is the configuration that worked for me to enable USB drives as internal on bromolow-7.1.0-42661:

image.png.d7b12c78fafb52a16259fc12366c0034.png

Afterwards I ran:

Spoiler

sudo ./rploader.sh clean now
sudo ./rploader.sh ext bromolow-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/redpill-load/master/redpill-virtio/rpext-index.json
sudo ./rploader.sh ext bromolow-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/redpill-load/master/redpill-acpid/rpext-index.json
sudo ./rploader.sh ext bromolow-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/redpill-load/master/redpill-misc/rpext-index.json
sudo ./rploader.sh build bromolow-7.1.0-42661

(optional):
sudo ./rploader.sh backup now

Edited September 9, 2022 by nutter

sam juan · September 9, 2022

5 hours ago, pocopico said:

It should work~~, you cannot though create a new loader for 42962 yet.~~ and you should now be able to also create a new loader for 42962 as well.

this is for v0.9 only or will work with v0.8 as well? tnx

Kaneske · September 9, 2022

8 hours ago, pocopico said:

It should work~~, you cannot though create a new loader for 42962 yet.~~ and you should now be able to also create a new loader for 42962 as well.

Hmmm, ok, but I´m still a bit confused...exactly how is the procedure for my System now?

Sorry, I am careful because I have too much data on my Raid...

3622xs+ TCRP on ESXi with latest -4 Update...before the actual one.

THX

pocopico · September 10, 2022

13 hours ago, Kaneske said:

Hmmm, ok, but I´m still a bit confused...exactly how is the procedure for my System now?

Sorry, I am careful because I have too much data on my Raid...

3622xs+ TCRP on ESXi with latest -4 Update...before the actual one.

THXsuggestion

My suggestion is to always keep backups outside DSM. Test the process on a test system. Document the process and then perform the upgrade on your production system.

the process would be as usually, upgrade from DSM and then run postupdate from TC

apriliars3 · September 10, 2022

19 minutes ago, pocopico said:

My suggestion is to always keep backups outside DSM. Test the process on a test system. Document the process and then perform the upgrade on your production system.

the process would be as usually, upgrade from DSM and then run postupdate from TC

I test DS918+ DSM 7.1.1-42962 with Tinycore Jun mod DSM_DS918+_7.1-42661 and arpl v0.4 alpha 7 and works.

When I put Tinycore DSM 7.1.0-42661 start with recovery loop and run ./rploader.sh postupdate apollolake-7.1.0-42661, but no works, other time recovery loop and no fix the issue.

I try to create a new loader, but had errors and fail.

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

./rploader.sh build apollolake-7.1.1-42962

error.txt

Edited September 10, 2022 by apriliars3

sbv3000 · September 10, 2022

53 minutes ago, apriliars3 said:

I test DS918+ DSM 7.1.1-42962 with Tinycore Jun mod DSM_DS918+_7.1-42661 and arpl v0.4 alpha 7 and works.

When I put Tinycore DSM 7.1.0-42661 start with recovery loop and run ./rploader.sh postupdate apollolake-7.1.0-42661, but no works, other time recovery loop and no fix the issue.

I try to create a new loader, but had errors and fail.

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

./rploader.sh build apollolake-7.1.1-42962

error.txt 78.05 kB · 0 downloads

the issue is stated in the error message, the e1000 module is not in the rp-ext library (yet) for that build. Try a 'standard' 918-42661 build (with a newly made tcrp boot usb), once you are working then check the threads here for progress in loaders for the updates.

pocopico · September 10, 2022

1 hour ago, apriliars3 said:

I test DS918+ DSM 7.1.1-42962 with Tinycore Jun mod DSM_DS918+_7.1-42661 and arpl v0.4 alpha 7 and works.

When I put Tinycore DSM 7.1.0-42661 start with recovery loop and run ./rploader.sh postupdate apollolake-7.1.0-42661, but no works, other time recovery loop and no fix the issue.

I try to create a new loader, but had errors and fail.

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

./rploader.sh build apollolake-7.1.1-42962

error.txt 78.05 kB · 1 download

Fixed missing ds918 extension reference for build 42962. You should now be ok ..

Edited September 10, 2022 by pocopico

pcristi · September 10, 2022

Please also fix ds920p missing reference for build 42962.
Thanks.

Edited September 10, 2022 by pcristi

pocopico · September 10, 2022

4 minutes ago, pcristi said:

Please also fix ds920p missing reference for build 42962.
Thanks.

Can you share any logs ? I think i've got that covered already

pcristi · September 10, 2022

2 hours ago, pocopico said:

Can you share any logs ? I think i've got that covered already

I send PM.
Thanks.

Edited September 10, 2022 by pcristi

SWAGG3R · September 10, 2022

How long does it take after installing 7.0.1 JUN for it to appear on the network?

Edited September 10, 2022 by SWAGG3R

Itay1778 · September 10, 2022

On 9/9/2022 at 1:28 PM, pocopico said:

you should now be able to also create a new loader for 42962 as well.

How? I don't see an update...
And is it possible to update from DSM 7 7.1.0-42661 U1 to 42962? What is the process?
DS918+
and DS3622xs+

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