RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal

Prutzer · June 4, 2022

I am trying to install Xpenology 7.1 on a Gigabyte GA-N3150N-D3V mainboard with an Intel Celeron N3150 processor. I created a bootable usb drive with Tinycore Redpill 8.0.0. When booting I got the error: Failed in waitforx.

Ok: Solution: Use a faster USB drive. I'm now booting with an USB 3.0 drive and X is starting.

Edited June 4, 2022 by Prutzer

Peter Suh · June 7, 2022

I would like to share again some of the misconceptions about the jun mode build of TCRP.

Successfully updated from 7.0.1-42218 u4 to 7.1.0-42661 u2 on 6 models except for current ds920+.

Last month, @pocopico released version 0.7.1.4 of TCRP on 5/17.
He mentioned just one line, but I don't know if I didn't pay attention.

Since then, the use of jun mode in TCRP has not been promoted and there is no guide, so it seems that some users misunderstand that jun mode is not available in TCRP.

As in the text of the link above, you need to add one more jun option at the end.

./rploader.sh build broadwellnk-7.0.1-42218-JUN jun

However, if you build like this without this jun option as shown below, there is no error.

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

However, if you build like this, it will be built in abnormal mode, not in Jot mode or Jun mode.

As if it was built in Jun mode, the grub boot menu called Yet Another Jun's Mode also looks changed, so it is easy to be mistaken.
I also made a mistake on this part.

It has been modified to enable normal build by adding the missing jun option to the m shell.

./my.sh DS918+J

./my.sh DS3615xsJ

./my.sh DS3617xsJ

./my.sh DS3622xs+J

./my.sh DVA3221J

./my.sh DS920+J jumkey

./my.sh DS1621+J jumkey

When it is built in jun mode, the log that you normally can't see rises considerably.
Finally, it seems that the process of making a new custum.gz file and patching it goes into it.

It has been confirmed that it is currently working well on DS918+ DS3615xs DS3617xs DS3622xs DVA3221 DS1621+ baremetal.

As shared by @dolbycat, it takes a while for all of JUN to recognize the LAN. Please take that into consideration and use it.

Attached here are the test results.

Edited June 7, 2022 by Peter Suh

berzek · June 7, 2022

On 5/30/2022 at 9:44 PM, pocopico said:

A good alternative would be to change the usb port that you have your loader connected.

Quoted in relation to DSM setup getting stalled at 55% or 66%.

- After facing the same problem earlier, I managed to get to a working DS3622xs+ by simply trying out the USB Loader from another USB port on the Baremetal HW.

.hth

Peter Suh · June 8, 2022

The second parameter "now" is a completely unnecessary parameter.
It was initially misguided from pocopico.
Even if "now" is removed and used, everything works normally.
I am in the process of guiding again to remove this "now" from the guide I made.

cobra_mk · June 8, 2022

what is the difference between the normal and the jun version?

is it only the point that i can use the old config file?

And can i use the original origibal pat files from synology or is another file needed

Edited June 8, 2022 by cobra_mk

Peter Suh · June 9, 2022

8 hours ago, cobra_mk said:

what is the difference between the normal and the jun version?

is it only the point that i can use the old config file?

And can i use the original origibal pat files from synology or is another file needed

The difference between the regular version (JOT) and the JUN version is that in the JUN mode, it dynamically responds to DSM REVISION that is continuously updated in the future.

It is also called JUN's OLD TRICK as it was used in JUN's DSM 6 in the past.

The existing JOT mode sometimes requires a new loader build whenever a new DSM REVISION is released, but in the JUN mode, there is no need for that.

Instead, JUN mode must start build from 7.0.1-42218.

Peter Suh · June 9, 2022

And for the pat file used for XPE installation, the original file must be used in any case.

Please avoid using PAT files that have undergone encryption/decryption process.

Peter Suh · June 10, 2022

[NOTICE]

It seems that @pocopico has been very busy lately.

It was not possible to build the ds920+ jun mode because it was not fixed correctly yet.

I made it possible to build it through my m shell.

Download the latest version to ./my.sh again.

You can build it like this.

./my.sh DS920+J jumkey

Peter Suh · June 11, 2022

With the help of @dolbycat
ds920+ / ds1621+ jun mode build for TC
The nic waiting time was reduced from 3 minutes to 2 minutes and 10 seconds.

Modification of sha256sum of ds920+ 42218 config.json requested by @pocopico may not be necessary at this time.

As for the jun mode, it was completely switched to refer only to @jumkey's repo, and it was possible to build so that even the use of dynamic dtc patches was possible in TC without any problem.

It has been changed to be able to respond to both dtc models in m shell.

(jumkey option is whether or not to use dynamic dtc patch)

./my.sh ds920+J jumkey
./my.sh ds1621+J jumkey

If additional ext is needed in the VM environment, use it as follows.
./myv.sh ds920+J jumkey
./myv.sh ds1621+J jumkey

TheInternets · June 13, 2022

Hey there,

I just installed a 920+ baremetal on an asrock J4105 board. That one has 2 sata controllers on board - the intel one and an asmedia one - plus one that is plugged in via PCIE.
I had a baremetal DS3622xs+ installation before which recognized all drives - not so much on the 920. Any idea what i need to change?

I wanted to move to the 920p as the processor is closer to the one on the board and i've read that i could probably use hardware decoding by using the igpu.

PS: Great work on the tc launcher - really makes installing so much easier!

Edited June 13, 2022 by TheInternets

maxime · June 14, 2022

Probably I'm stupid, but I can't understand how to upgrade working DS3622xs+ 7.0.1-42218 to DSM 7.1.0-42661 😥
Can someone help me to understand? If I understand, I should do this:
1. manual update DSM to 7.1.0-42661 (within DSM)

2. reboot the XPEnology server and choose TinyCore on startup (3rd menù item)
3. execute this commands:

./rploader.sh clean now
./rploader.sh ext broadwellnk-7.1.0-42661 add https://github.com/jimmyGALLAND/redpill-ext/raw/master/acpid/rpext-index.json

./rploader.sh build bromolow-7.1.0-42661

./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh backup now
4. reboot DSM
5. manual update DSM to 7.1.0-42661-1 (within DSM)
6. reboot DSM
7. manual update DSM to 7.1.0-42661-2 (within DSM)

Is this correct? Thanks to all!

Peter Suh · June 14, 2022

14 hours ago, TheInternets said:

Hey there,

I just installed a 920+ baremetal on an asrock J4105 board. That one has 2 sata controllers on board - the intel one and an asmedia one - plus one that is plugged in via PCIE.
I had a baremetal DS3622xs+ installation before which recognized all drives - not so much on the 920. Any idea what i need to change?

I wanted to move to the 920p as the processor is closer to the one on the board and i've read that i could probably use hardware decoding by using the igpu.

PS: Great work on the tc launcher - really makes installing so much easier!

In the case of ds920+ using jumkey's dynamic dtb, the maximum supported number of drives is only 4, and there is a restriction that only the built-in sata port should be used.

Peter Suh · June 14, 2022

9 minutes ago, maxime said:

Probably I'm stupid, but I can't understand how to upgrade working DS3622xs+ 7.0.1-42218 to DSM 7.1.0-42661 😥
Can someone help me to understand? If I understand, I should do this:
1. manual update DSM to 7.1.0-42661 (within DSM)

2. reboot the XPEnology server and choose TinyCore on startup (3rd menù item)
3. execute this commands:

./rploader.sh clean now
./rploader.sh ext broadwellnk-7.1.0-42661 add https://github.com/jimmyGALLAND/redpill-ext/raw/master/acpid/rpext-index.json

./rploader.sh build bromolow-7.1.0-42661

./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh backup now
4. reboot DSM
5. manual update DSM to 7.1.0-42661-1 (within DSM)
6. reboot DSM
7. manual update DSM to 7.1.0-42661-2 (within DSM)

Is this correct? Thanks to all!

For DS3622xs+, it seems like the first thing to do is to unify them all with broadwellnk.

Change everything to broadwellnk and rebuild from scratch.

As below, perform the patch for 7.1.0-42661 update 2 once more.

./rploader.sh postupdate broadwellnk-7.1.0-42661

Edited June 14, 2022 by Peter Suh

maxime · June 14, 2022

8 minutes ago, Peter Suh said:

As below, perform the patch for 7.1.0-42661 update 2 once more.

./rploader.sh postupdate bromolow-7.1.0-42661

Where on my list do I have to execute ./rploader.sh postupdate bromolow-7.1.0-42661? At the end of "3."?

Edited June 14, 2022 by maxime

Peter Suh · June 14, 2022

13 minutes ago, maxime said:

Where on my list do I have to execute ./rploader.sh postupdate bromolow-7.1.0-42661? At the end of "3."?

Yes

maxime · June 14, 2022

error. sorry

Edited June 14, 2022 by maxime

Peter Suh · June 14, 2022

5 minutes ago, maxime said:

error. sorry

You're still not sure if it's broadwellnk or bromolow.
Did you choose bromolow (DS3615xs), not DS3622xs+?

maxime · June 14, 2022

1 minute ago, Peter Suh said:

You're still not sure if it's broadwellnk or bromolow.
Did you choose bromolow (DS3615xs), not DS3622xs+?

I wrote bromolow instead of broadwellnk 🤬

maxime · June 14, 2022

51 minutes ago, Peter Suh said:

You're still not sure if it's broadwellnk or bromolow.
Did you choose bromolow (DS3615xs), not DS3622xs+?

I did the procedure one more time. Now after "./rploader.sh postupdate broadwellnk-7.1.0-42661"
I have to edit user_config.json and change
SataPortMap=2
DiskIdxMap=00
After changed user_config.json and saved it, how do I apply the modified user_config.json? It seems that the system keep loading the original user_config.json...

Peter Suh · June 14, 2022

8 minutes ago, maxime said:

I did the procedure one more time. Now after "./rploader.sh postupdate broadwellnk-7.1.0-42661"
I have to edit user_config.json and change
SataPortMap=2
DiskIdxMap=00
After changed user_config.json and saved it, how do I apply the modified user_config.json? It seems that the system keep loading the original user_config.json...

Please tell me the model name of your motherboard.
Also, turn on all hot plug options in the bios.
Are you using only 2 HDDs for the built-in sata port?

maxime · June 14, 2022

4 minutes ago, Peter Suh said:

Please tell me the model name of your motherboard.
Also, turn on all hot plug options in the bios.
Are you using only 2 HDDs for the built-in sata port?

The mainboard is a ASUS P8H61-M LE/USB3; it has only 4 sata ports, I don't understand why the system find 6 ports... All the 4 sata ports are set as hotplug in the bios.
The only way i found to install is set only 2 sata ports

Peter Suh · June 15, 2022

20 hours ago, maxime said:

The mainboard is a ASUS P8H61-M LE/USB3; it has only 4 sata ports, I don't understand why the system find 6 ports... All the 4 sata ports are set as hotplug in the bios.
The only way i found to install is set only 2 sata ports

It is unfortunate that only 2 out of 4 Sata Ports can be used in DS3622xs which is None dtc method.

It remains to be seen whether all motherboards with the H61 chipset are like that.
Interesting fact.

Alternatively, use the Linux DT (Device Tree) as a DS920+ or DS1621+
Try changing the installation model.

There is no need to worry as the migration from the installed DS3622xs+ to DS920+ etc. will be smooth.

Even if something goes wrong, install DS3622xs+ again and migrate once more.

I will show you how to build more easily by using the m shell I developed.

Download and decompress my.sh with the following command in TC linux.

tc@box:~$
curl --location "https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz" --output my.sh.gz; tar -zxvf my.sh.gz;

After that, if you use the following command line, SN/MAC/VID/PID and build are processed at once.

./rploader.sh clean

./my.sh DS920+J jumkey

This option builds DS920+ in jun mode with jumkey's dynamic dtc method.

For jun mode, refer to the discussion in the forum,
The advantage of jumkey's dynamic dtc is that it can avoid the issue of ghost ports or muxed ports (M.2 + Sata Mix) as above.

Also, the newly added disk without using sataportmap automatically recognizes whether it is installed or not.

DS920+ supports up to 4 disks, DS1621+ supports up to 6 disks,
It must be used only with the built-in SATA port.

Edited June 15, 2022 by Peter Suh

The_Mole · June 17, 2022

Hi there,

you guys might be able to save me some time, figuring this out:

System is a Fujitsu Esprimo P720 E90, running on a Xeon E3-1275L V3 (Haswell based).

There are 13 disks in the system - 5 attached to the mainboard, 8 attached to a Fujitsu D2607-A21 SAS controller (LSI SAS2008), crossflashed to 9211-8i in IT Mode.

Another one of those controllers is sitting there empty until I need to add more space.

Currently, I'm running my install as DS3615xs on 6.2.3-25426 with Jun's loader 1.03b.

I tried upgrading to Redpill as DS918+ on 7.1.0-42661 to enable video encoding but I only get the 5 disks on the mainboard to show up.
The ones on the SAS controller that are working with mpt2sas-driver on 6.2.3 do not appear on 7.1.0, even if I add the driver to Redpill.

Latest approach was:

./rploader.sh update now
./rploader.sh fullupgrade now
./rploader.sh serialgen DS918+
./rploader.sh identifyusb now
./rploader.sh satamap now
tce-load -wi nano #because I hate vi
nano user_config.json #edited to hardware MAC, a different 918+ serial and set maxdisks to 24
./rploader.sh ext apollolake-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt2sas/rpext-index.json
./rploader.sh build apollolake-7.0.1-42218
./rploader.sh clean now
./rploader.sh ext apollolake-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt2sas/rpext-index.json
./rploader.sh build apollolake-7.1.0-42661
./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh backup now;
sudo reboot

Output from lspci -k (on 6.2.3) - Kernel driver won't show up on 7.1.0:

0000:01:00.0 Class 0104: Device 1000:0072 (rev 02)
        Subsystem: Device 1734:1177
        Kernel driver in use: mpt2sas
0000:03:00.0 Class 0104: Device 1000:0072 (rev 03)
        Subsystem: Device 1734:1177
        Kernel driver in use: mpt2sas

Output from ll /sys/block (on 6.2.3) - only sda-sde appear on 7.1.0:

lrwxrwxrwx  1 root root 0 Jun 17 14:47 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda
lrwxrwxrwx  1 root root 0 Jun 17 14:47 sdb -> ../devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb
lrwxrwxrwx  1 root root 0 Jun 17 14:47 sdc -> ../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdc
lrwxrwxrwx  1 root root 0 Jun 17 14:47 sdd -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdd
lrwxrwxrwx  1 root root 0 Jun 17 14:47 sde -> ../devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sde
lrwxrwxrwx  1 root root 0 Jun 17 14:47 sdh -> ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host7/port-7:0/end_device-:0/target7:0:0/7:0:0:0/block/sdh
lrwxrwxrwx  1 root root 0 Jun 17 14:47 sdi -> ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host7/port-7:1/end_device-:1/target7:0:1/7:0:1:0/block/sdi
lrwxrwxrwx  1 root root 0 Jun 17 14:47 sdj -> ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host7/port-7:2/end_device-:2/target7:0:2/7:0:2:0/block/sdj
lrwxrwxrwx  1 root root 0 Jun 17 14:47 sdk -> ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host7/port-7:3/end_device-:3/target7:0:3/7:0:3:0/block/sdk
lrwxrwxrwx  1 root root 0 Jun 17 14:47 sdl -> ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host7/port-7:4/end_device-:4/target7:0:4/7:0:4:0/block/sdl
lrwxrwxrwx  1 root root 0 Jun 17 14:47 sdm -> ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host7/port-7:5/end_device-:5/target7:0:5/7:0:5:0/block/sdm
lrwxrwxrwx  1 root root 0 Jun 17 14:47 sdn -> ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host7/port-7:6/end_device-:6/target7:0:6/7:0:6:0/block/sdn
lrwxrwxrwx  1 root root 0 Jun 17 14:47 sdo -> ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host7/port-7:7/end_device-:7/target7:0:7/7:0:7:0/block/sdo

I'd appreciate any ideas on how to get those disks on the SAS controller to show up on 7.1.0.
Thanks for your time.

Peter Suh · June 17, 2022

48 minutes ago, The_Mole said:

Hi there,

you guys might be able to save me some time, figuring this out:

System is a Fujitsu Esprimo P720 E90, running on a Xeon E3-1275L V3 (Haswell based).

There are 13 disks in the system - 5 attached to the mainboard, 8 attached to a Fujitsu D2607-A21 SAS controller (LSI SAS2008), crossflashed to 9211-8i in IT Mode.

Another one of those controllers is sitting there empty until I need to add more space.

Currently, I'm running my install as DS3615xs on 6.2.3-25426 with Jun's loader 1.03b.

I tried upgrading to Redpill as DS918+ on 7.1.0-42661 to enable video encoding but I only get the 5 disks on the mainboard to show up.
The ones on the SAS controller that are working with mpt2sas-driver on 6.2.3 do not appear on 7.1.0, even if I add the driver to Redpill.

The combination of DS918+ and HBA is still unstable.
The current HBA and the most stable model is the DS3622xs+.
I'm also using the HBA and DS3622xs+ as BIOS legacy storage options.

Edited June 17, 2022 by Peter Suh

yeric79 · June 18, 2022

hi,

i try install DS3622XS+ or DS920+ on ESXI, but HDD no detect after boot

also with No problem with DVA3221 or DS918+

an idea ?

Thanks

RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal

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