TinyCore RedPill Loader (TCRP)

[Peter Suh]

31 minutes ago, flyride said:

 

The script is keyed to SHA hashes of the PAT file itself as well as contained files.  That is the reason for the corruption error.

So this really does need an update when the script cannot pull down the original file any longer.

 

@flyride

 

As you can see in the log, there is no problem with update 1 link.

Do you know about the m shell I made?

I don't know if @pocopico has the will to modify config.json,

m shell is pre-downloading update 1 pat file to skip this issue.

 

 

tc@box:~$ curl -o /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles/ds3
622xsp_42661.pat "https://global.download.synology.com/download/DSM/release/7.1/42661-1/DSM_DS3622xs+_42661.pat"
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  352M  100  352M    0     0  22.8M      0  0:00:15  0:00:15 --:--:-- 23.2M
tc@box:~$ ll /mnt/sda3/a*
total 709532
-rwxrwxrwx 1 root root 369878630 May  7 01:01 ds3622xsp_42661.pat
-rwxrwxrwx 1 root root 356675410 May  6 14:24 ds920p_42661.pat
drwxrwxrwx 2 root root      4096 Apr 28 08:47 extractor/
tc@box:~$ curl -o /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles/ds3
622xsp_42661.pat "https://global.download.synology.com/download/DSM/release/7.1/42661/DSM_DS3622xs+_42661.pat"
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  3322  100  3322    0     0   7382      0 --:--:-- --:--:-- --:--:--  7365
tc@box:~$ 

Edited May 7, 2022 by Peter Suh

[Peter Suh]

1 hour ago, MajkelP said:

Does anyone know why DS3622xsp with DSM 7.1.42661 update 1 shows the CPU temperature about 20 C higher than it actually is.

In idle it is about 60 C which is not true. Heatsink is cool and I also checked temp. in BIOS and it is about 40C.  
I checked my configuration on DS3617xs (Jun 1.03b),DSM 6.2.3-25426 and temperature was 38-40 C. 
Is there any extension I might not have added when creating the RedPill loader? I used automatic mode.

 

And the second problem, it didn't seem to occur before or I did not notice, (7.0.1-42218). After rebooting, it does not find it on the network and is not visible, the leds on the network card do not blink. To get it work again I have to turn my system off with the power button and then on, then everything works. 

 

Thanks, 

 

 

 

I'd like to look at the second question
Aren't you using the HBA H310 in IT Mode?
I've had a similar phenomenon, and recently this issue has disappeared due to some measure.

As follows
I want to make sure that you are looking at the LSI controller bios screen every time you boot.

 

 

And we're going to enter the CTRT+C key, and we're going to enter the adapter property
Can you see the screen as below?

 

If this entry is not possible, you are operating in UEFI mode instead of legacy in the SATA storage option in the BIOS.

This is what I posted a few days ago in this regard.
 

 

 

Edited May 7, 2022 by Peter Suh

[Peter Suh]

40 minutes ago, Peter Suh said:

 

 

I'd like to look at the second question
Aren't you using the HBA H310 in IT Mode?
I've had a similar phenomenon, and recently this issue has disappeared due to some measure.

As follows
I want to make sure that you are looking at the LSI controller bios screen every time you boot.

 

 

And we're going to enter the CTRT+C key, and we're going to enter the adapter property
Can you see the screen as below?

 

If this entry is not possible, you are operating in UEFI mode instead of legacy in the SATA storage option in the BIOS.

This is what I posted a few days ago in this regard.
 

 

 

 

 

From the post contents of the link below, you seem to have much more expertise in HBAs than I do.
I don't think I made the same mistake as I posted above.
Should I find a problem somewhere else?

 

 

 

[MajkelP]

4 hours ago, Peter Suh said:

 

 

From the post contents of the link below, you seem to have much more expertise in HBAs than I do.
I don't think I made the same mistake as I posted above.
Should I find a problem somewhere else?

 

 

 

Thank you very much @Peter Suh for you respond.

Yes, I used UEFI mode on my motherboard and my Dell Perc H310 is flashed to LSI SAS9211-8i IT mode but without BIOS. 

What I will do now, I am going to start over again and create RedPill loader in BIOS legacy mode. (without BIOS on the card) and if fails again I am going flash BIOS/UEFI into card. This worked without any issues without BIOS on the card on Jun's Loader 1.03b and DS3617xs. 

I also found on the Broadcom (LSI) web page that there is a UEFI bios for this card. 

https://docs.broadcom.com/docs/12348628

and maybe LSI card will work again in UEFI mode after flashing with above UEFI BSD P20. ( I am not quite sure, I am only guessing) I have two of them so I can try

 

Thank you for the direction. 

 

 

[flyride]

13 hours ago, flyride said:

 

The script is keyed to SHA hashes of the PAT file itself as well as contained files.  That is the reason for the corruption error.

So this really does need an update when the script cannot pull down the original file any longer.

 

This post was able to solve the problem (acquire the original 42661 PAT file)

https://xpenology.com/forum/topic/53817-redpill-tinycore-loader/?do=findComment&comment=278684

 

[Peter Suh]

1 hour ago, flyride said:

 

This post was able to solve the problem (acquire the original 42661 PAT file)

https://xpenology.com/forum/topic/53817-redpill-tinycore-loader/?do=findComment&comment=278684

 

 

I shared the original PAT file that I had collected in advance because there was a problem with the SYNOLOGY download home at the time.

If you really need an original 42661 PAT file, you can use it.

However, since Update 1 is the final version, it is okay to use it after downloading it through M Shell.

[Al lex]

On 5/6/2022 at 6:03 PM, giacomoleopardo said:

All right it seems to be working. meanwhile I manage to correctly install acpid (power off button) and Realtek 2,5 Gb 8125 NIC extensions.

Here are my steps (thanks to Thor Group, @pocopico and @Peter Suh

 

 

Just wanted to say great thanks to you, @pocopico and @Peter Suh

I used your report as a global instruction and link to their posts and scripts. Could not get a couple of things. After all I got 7.1 with dedicated cash among volumes and 2,5 gb rtl 8125 bond. It is more than I dreamed. I was not so happy since Jun release some years ago.

Edited May 7, 2022 by Al lex

[sam juan]

3 hours ago, flyride said:

 

This post was able to solve the problem (acquire the original 42661 PAT file)

https://xpenology.com/forum/topic/53817-redpill-tinycore-loader/?do=findComment&comment=278684

 

can you please share the steps?
right before the build 42661 copy the pat file?
thanks.

[nullos]

I download the pat file for DS918+ and all works fine 😀

 

Migration ok from 6.2.4 to 7.1 on proxmox.

 

Thanks for your help👍.

[Peter Suh]

3 hours ago, sam juan said:

can you please share the steps?
right before the build 42661 copy the pat file?
thanks.

 

 

As mentioned above, there is no need to return to the previous version even though Update 1 is already out.
Build the TC loader using "M-Shell" utilizing Update 1 below.
The original link to the Synology download home has stopped, so this is the best way to do it at the moment.

 

 

[Al lex]

9 hours ago, Peter Suh said:

 

 

...

One more random question.

Is it possible to migrate from DS918+ 7.1 to DS3622 7.1?  I am to ask since actually upgrading to 7.1 is not typical mixing DSM update and changing boot flash in process.

 

Edited May 8, 2022 by Al lex

[MajkelP]

On 5/7/2022 at 9:01 AM, MajkelP said:

Thank you very much @Peter Suh for you respond.

Yes, I used UEFI mode on my motherboard and my Dell Perc H310 is flashed to LSI SAS9211-8i IT mode but without BIOS. 

What I will do now, I am going to start over again and create RedPill loader in BIOS legacy mode. (without BIOS on the card) and if fails again I am going flash BIOS/UEFI into card. This worked without any issues without BIOS on the card on Jun's Loader 1.03b and DS3617xs. 

I also found on the Broadcom (LSI) web page that there is a UEFI bios for this card. 

https://docs.broadcom.com/docs/12348628

and maybe LSI card will work again in UEFI mode after flashing with above UEFI BSD P20. ( I am not quite sure, I am only guessing) I have two of them so I can try

 

Thank you for the direction. 

 

 

 

I would like share with my testing results and some thoughts 

 

1. I can confirm that flashing my SAS card with BIOS [mptsas2.rom] Version no: 7.39.02.00  and UEFI BSD 20.0 [ebcsas2.rom] Version no: 7.27.01.01 resolved my issue with my NAS after reboot that could not be found it on the network and is not visible. My motherboard is set for Legacy and UEFI boot. I used tinycore-redpill.v0.4.6.img.gz version (no UEFI)

2 I also tried with clean UEFI version tinycore-redpill-uefi.v0.4.6.img.gz so I had to set my motherboard for UEFI only boot, and my motherboard could see all disks attached to the card, I was able to install DSM 7.1 but after reboots (2 or 3) times,  my storage pool became in critical state, not quite sure why. So I decided to switch to option 1. ( Legacy and UEFI boot) May Perhaps this requires longer testing.

 

3. I would also like notice that speed of copying files between NAS and computer. It is slower than on my DS3617xs (Jun 1.03b loader).

Copying iso file about 5GB I am getting about 100MB/s but on my previous build DS3617xs I was able to get 112-116MB/s. Everything is the same: switch router, cables etc.  

I am using Windows 10 SMB3. 

 

4.  I am thinking to test DS3617xs in version 6.2.4-25556u2 but I am not quite sure how to start preparing loader. I found this 

https://github.com/jimmyGALLAND/redpill-load/tree/add_support_ds3617xs_6.2.4-25556u2

Is there a big problem to prepare loader for DS3617 with the 6.2.4-25556 u2 or u5 the latest version? 

 

 

 

 

[Peter Suh]

30 minutes ago, Al lex said:

One more random question.

Is it possible to migrate from DS918+ 7.1 to DS3622 7.1?  I am to ask since actually upgrading to 7.1 is not typical mixing DSM update and changing boot flash in process.

 

 

Within the TC alone, for example, it is possible to migrate freely within five models (DS918+/DS3615xxs/DS3617xxs/DS3622xxs+/DVA3221).
In fact, DVA3221 was later released, so I didn't go through many tests.
Even if it is a DTC model, there will be no restrictions on migration of the two models if there is no issue in the Sata Port Mapping.

 

As far as the CPU generation is concerned, migration is originally free between each platform of the synology.

[Peter Suh]

13 minutes ago, MajkelP said:

 

I would like share with my testing results and some thoughts 

 

1. I can confirm that flashing my SAS card with BIOS [mptsas2.rom] Version no: 7.39.02.00  and UEFI BSD 20.0 [ebcsas2.rom] Version no: 7.27.01.01 resolved my issue with my NAS after reboot that could not be found it on the network and is not visible. My motherboard is set for Legacy and UEFI boot. I used tinycore-redpill.v0.4.6.img.gz version (no UEFI)

2 I also tried with clean UEFI version tinycore-redpill-uefi.v0.4.6.img.gz so I had to set my motherboard for UEFI only boot, and my motherboard could see all disks attached to the card, I was able to install DSM 7.1 but after reboots (2 or 3) times,  my storage pool became in critical state, not quite sure why. So I decided to switch to option 1. ( Legacy and UEFI boot) May Perhaps this requires longer testing.

 

3. I would also like notice that speed of copying files between NAS and computer. It is slower than on my DS3617xs (Jun 1.03b loader).

Copying iso file about 5GB I am getting about 100MB/s but on my previous build DS3617xs I was able to get 112-116MB/s. Everything is the same: switch router, cables etc.  

I am using Windows 10 SMB3. 

 

4.  I am thinking to test DS3617xs in version 6.2.4-25556u2 but I am not quite sure how to start preparing loader. I found this 

https://github.com/jimmyGALLAND/redpill-load/tree/add_support_ds3617xs_6.2.4-25556u2

Is there a big problem to prepare loader for DS3617 with the 6.2.4-25556 u2 or u5 the latest version? 

 

 

 

 

 

I think a little differently.

My friend's advice, who has long been using LSI controllers, was whether UEFI should be applied to the "DELL PERC H310", an older HBA card that uses PCIE x 2.0.

 

Legacy bios alone is sufficiently stabilized, so legacy, not UEFI, was recommended.

 

In my case, I am already showing sufficient stability in legacy bios and I am satisfied with this.

Edited May 8, 2022 by Peter Suh

[MajkelP]

3 minutes ago, Peter Suh said:

 

 

 

Legacy bios alone is sufficiently stabilized, so legacy, not UEFI, was recommended.

 

In my case, I am already showing sufficient stability in legacy bios and I am satisfied with this.

I agree with this. I am staying with legacy. Thanks for you answer. 

[pocopico]

On 4/27/2022 at 6:05 PM, Peter Suh said:

 

Temporarily share the pat files until the Synology Download Center is restored.
Copy it under /mnt/sd#3/auxfiles/ for permanent use.
Instead, you can store only about two due to the capacity limit.

 

https://drive.google.com/drive/folders/1fIvbwHLqe4GIIi5RcNayJKykqcaCbva1

 

Do not share pat files in this forum please respect the rules. : https://xpenology.com/forum/terms/

 

@Polanskiman PLEASE DELETE the post

[pocopico]

The issue with the latest update is fixed. Config files now reflect the latest release URL and SHA256SUM

 

The issue could have easily been tricked by modifying the platform config.json file in your cloned redpill-load folder. So in the future someone could edit the file : 

 

/home/tc/redpill-load/config/<PLATFORM>/<VERSION>/config.json and modify it to match the required URL and SHA256SUM.

 

Git will respect your local edited file and will not overwrite it unless you specifically tell git to do so.

 

eg. 

{

"os": {

"id": "ds3615xs_41222",

"pat_url": "XXXX",

"sha256": "XXX"

},

 

This of cource if all the other prerequisites are matched.

 

Edited May 8, 2022 by pocopico

[Peter Suh]

2 hours ago, pocopico said:

 

Do not share pat files in this forum please respect the rules. : https://xpenology.com/forum/terms/

 

@Polanskiman PLEASE DELETE the post

 

@pocopico

 

I'm sorry, I never thought of sharing a commercial OS.
I erased the file on the drive right now.

[Peter Suh]

5 hours ago, pocopico said:

The issue with the latest update is fixed. Config files now reflect the latest release URL and SHA256SUM

 

The issue could have easily been tricked by modifying the platform config.json file in your cloned redpill-load folder. So in the future someone could edit the file : 

 

/home/tc/redpill-load/config/<PLATFORM>/<VERSION>/config.json and modify it to match the required URL and SHA256SUM.

 

Git will respect your local edited file and will not overwrite it unless you specifically tell git to do so.

 

eg. 

{

"os": {

"id": "ds3615xs_41222",

"pat_url": "XXXX",

"sha256": "XXX"

},

 

This of cource if all the other prerequisites are matched.

 

 

@pocopico

Does this mean that each user should modify the config.json as they want and keep the redpill-load directory instead of erasing it?

Or do you plan to accept the modified config.json file if we request commit to your git repo?

I'm not sure what it means.

Edited May 8, 2022 by Peter Suh

[pocopico]

1 hour ago, Peter Suh said:

 

@pocopico

Does this mean that each user should modify the config.json as they want and keep the redpill-load directory instead of erasing it?

Or do you plan to accept the modified config.json file if we request commit to your git repo?

I'm not sure what it means.

 

I was just explaining the way to modify config files locally and not wait for me and anyone that holds a redpill-load repo.

 

As of the PR on the redpill-load repo, and as this will affect a big number of users, i prefer to not allow any commits to the redpill-load, unless i test it myself or the other repo holders.

 

Of course anyone is able to clone the redpill-load repo, perform their modifications and promote it to the community. 

 

 

[MajkelP]

I would like ask you about 3617xs and 3622xsp.

Are they the same in stability? I mean RedPill loader. I installed both and they extensions for both are the same. (network, mpts, boot wait etc) 
Or do you prefer one over another and why?
I know that 3622xsp will receive updates, but for 3617xs not quite sure when will be the last update. 
Thanks, 
 

[sam juan]

6 hours ago, pocopico said:

The issue with the latest update is fixed. Config files now reflect the latest release URL and SHA256SUM

 

The issue could have easily been tricked by modifying the platform config.json file in your cloned redpill-load folder. So in the future someone could edit the file : 

 

/home/tc/redpill-load/config/<PLATFORM>/<VERSION>/config.json and modify it to match the required URL and SHA256SUM.

 

Git will respect your local edited file and will not overwrite it unless you specifically tell git to do so.

 

eg. 

{

"os": {

"id": "ds3615xs_41222",

"pat_url": "XXXX",

"sha256": "XXX"

},

 

This of cource if all the other prerequisites are matched.

 

sorry to ask this noob question, what is sha256? is it the MD5?
for example:

{

"os": {

"id": "ds3622xs_42661",

"pat_url": "https://global.download.synology.com/download/DSM/release/7.1/42661-1/DSM_DS3622xs%2B_42661.pat?model=DS3622xs%2B&bays=12&dsm_version=7.1&build_number=42661&_ga=2.136455984.1823054508.1652027668-1552442944.1645047990",

"sha256": "7af76cca8226ecf95b25630bffa76b3d"

}

 

[pocopico]

12 minutes ago, sam juan said:

sorry to ask this noob question, what is sha256? is it the MD5?
for example:

{

"os": {

"id": "ds3622xs_42661",

"pat_url": "https://global.download.synology.com/download/DSM/release/7.1/42661-1/DSM_DS3622xs%2B_42661.pat?model=DS3622xs%2B&bays=12&dsm_version=7.1&build_number=42661&_ga=2.136455984.1823054508.1652027668-1552442944.1645047990",

"sha256": "7af76cca8226ecf95b25630bffa76b3d"

}

 

 

no the sha256sum does actually the same as md5sum but with sha256; Also you may skip the part of the URL after the question mark. So : 

 

"pat_url": "https://global.download.synology.com/download/DSM/release/7.1/42661-1/DSM_DS3622xs%2B_42661.pat",

 

Please keep in mind that this will not always be the case. The rest of the subcomponents might need update as well. Its just not the case in update1

 

Edited May 8, 2022 by pocopico

[pocopico]

7 minutes ago, MajkelP said:

I would like ask you about 3617xs and 3622xsp.

Are they the same in stability? I mean RedPill loader. I installed both and they extensions for both are the same. (network, mpts, boot wait etc) 
Or do you prefer one over another and why?
I know that 3622xsp will receive updates, but for 3617xs not quite sure when will be the last update. 
Thanks, 
 

 

There is no reason at all to install DS3617 unless you have the same one running and just want to perform an update.

[sam juan]

6 minutes ago, pocopico said:

 

no the sha256sum does actually the same as md5sum but with sha256

 

sorry i am still at lost;  
so for DS3622xs+, what should be the config.json looks like? sorry for spoon-feed.