Jump to content
XPEnology Community

RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal


Peter Suh

Recommended Posts

14 hours ago, mattias93 said:

Hi @Peter Suh,

As you suggested, I tried to install DS920+. In this case, I can never access the DSM, after it reboots, it asks me for the PAT file again. I've attached the log.

The log looks like the previous one. @pocopico Peter said that you could understand what's going on :)

 

  linuxrc.syno.log (Reveal hidden contents)

SynologyNAS> more linuxrc.syno.log
START /linuxrc.syno.impl
'/etc.defaults/model.dtb' -> '/var/run/model.dtb'
Insert basic USB modules...
:: Loading module usb-common ... [  OK  ]
:: Loading module usbcore ... [  OK  ]
:: Loading module xhci-hcd ... [  OK  ]
:: Loading module xhci-pci ... [  OK  ]
:: Loading module usb-storage ... [  OK  ]
:: Loading kernel modules from extensions ...
Loading kmod #0 "e1000e.ko" for pocopico.e1000e (args: )
Loading kmod #0 "igb.ko" for pocopico.igb (args: )
:: Loading kernel modules from extensions ... [  OK  ]
:: Executing "on_boot" custom scripts ...
Running "check-e1000e.sh" for pocopico.e1000e->on_boot
Loading module e1000e -> Module e1000e loaded succesfully
Ran "check-e1000e.sh" for pocopico.e1000e->on_boot - exit=0
Running "check-igb.sh" for pocopico.igb->on_boot
Loading module igb -> Module igb loaded succesfully
Ran "check-igb.sh" for pocopico.igb->on_boot - exit=0
Running "boot-wait.sh" for redpill-boot-wait->on_boot
Still waiting for boot device (waited 1 of 30 seconds)
Still waiting for boot device (waited 2 of 30 seconds)
Still waiting for boot device (waited 3 of 30 seconds)
Still waiting for boot device (waited 4 of 30 seconds)
The /dev/synoboot device exists but it does not contain expected partitions (>=3 partitions)

========== BEGIN DUMP OF ALL PARTITIONS DETECTED ===========
/dev/sata1p1               8192        16785407        16777216  fd  
/dev/sata1p2           16785408        20979711         4194304  fd  
/dev/sata1p5           21257952      7813827135      7792569184  fd  


/dev/sata2p1               8192        16785407        16777216  fd  
/dev/sata2p2           16785408        20979711         4194304  fd  
/dev/sata2p5           21257952      7813827135      7792569184  fd  


/dev/sata3p1               2048       500103449       500101402  fd  


/dev/synobootp1            2048          100351           98304  83  
/dev/synobootp2          100352          253951          153600  83  
/dev/synobootp3          253952         2097151         1843200  83  


========== END OF DUMP OF ALL PARTITIONS DETECTED ==========
Ran "boot-wait.sh" for redpill-boot-wait->on_boot - exit=1
Running "install_rd.sh" for redpill-dtb->on_boot
'model_ds920p.dtb' -> '/etc.defaults/model.dtb'
'model_ds920p.dtb' -> '/var/run/model.dtb'
Ran "install_rd.sh" for redpill-dtb->on_boot - exit=0
Running "install_rd.sh" for redpill-misc->on_boot
Starting ttyd, listening on port: 7681
Ran "install_rd.sh" for redpill-misc->on_boot - exit=0
ERROR: Some of the scripts failed! See above for any with exit != 0
:: Executing "on_boot" custom scripts ... [  OK  ]
Exit on error [99] rp ext init exec failure...
Sat May  7 19:25:40 UTC 2022
none /sys/kernel/debug debugfs rw,relatime 0 0

 

linuxrc.syno.log 2.75 kB · 2 downloads

 

Build your loader without boot-wait extension. Extension is waiting for

 

if [ ! -b /dev/synoboot1 ] || [ ! -b /dev/synoboot2 ] || [ ! -b /dev/synoboot3 ] 

 

and instead it finds :

 

/dev/synobootp1            2048          100351           98304  83  
/dev/synobootp2          100352          253951          153600  83  
/dev/synobootp3          253952         2097151         1843200  83  

 

Is this a UEFI system ? You can also change to legacy. 

 

I think its DS920 that represents partitions with p1 at the end instead of the synoboot1/2/3. UEFI is not the issue.

 

No, i've verified on DS920 and UEFI or LEGACY should represent the same block device file in /dev/. Try without the boot-wait extension and see how it goes.

Edited by pocopico
Link to comment
Share on other sites

1 hour ago, pocopico said:

 

Build your loader without boot-wait extension. Extension is waiting for

 

if [ ! -b /dev/synoboot1 ] || [ ! -b /dev/synoboot2 ] || [ ! -b /dev/synoboot3 ] 

 

and instead it finds :

 

/dev/synobootp1            2048          100351           98304  83  
/dev/synobootp2          100352          253951          153600  83  
/dev/synobootp3          253952         2097151         1843200  83  

 

Is this a UEFI system ? You can also change to legacy. 

 

I think its DS920 that represents partitions with p1 at the end instead of the synoboot1/2/3. UEFI is not the issue.

 

No, i've verified on DS920 and UEFI or LEGACY should represent the same block device file in /dev/. Try without the boot-wait extension and see how it goes.

Pardon my ignorance, but using my.sh or following the guide at the beginning of this post, how do I disable the boot-wait extension?

Moreover, in the first log I reported here, while trying with the DS3622xs+

The mounts are without the trailing p:
/dev/synoboot1 2048 100351 98304 83
/dev/synoboot2 100352 253951 153600 83
/dev/synoboot3 253952 2097151 1843200 83

and, for a number of times before the install loop, the systems reboots fine.

Thanks!!

Link to comment
Share on other sites

2 hours ago, mattias93 said:

Pardon my ignorance, but using my.sh or following the guide at the beginning of this post, how do I disable the boot-wait extension?

Moreover, in the first log I reported here, while trying with the DS3622xs+

The mounts are without the trailing p:
/dev/synoboot1 2048 100351 98304 83
/dev/synoboot2 100352 253951 153600 83
/dev/synoboot3 253952 2097151 1843200 83

and, for a number of times before the install loop, the systems reboots fine.

Thanks!!

 

@mattias93

 

The boot-wait ext is included in the bundle, so there is no way to force it out.
So you can modify the bundle ext in the following way to bypass the boot-wait so that you don't download it.

./my.sh DS920+ noclean
sudo rm -rf ./redpill-load/cus*/e*/*boot-wait
vi ./redpill-load/bundled-exts.json

Change the content like this

 

from

{
 "redpill.bootwait": "https://github.com/pocopico/rp-ext/raw/main/redpill-boot-wait/rpext-index.json"
}

 

to

{
"": ""
}

Build it again like this, the bundle boot-wait will not be included.
./my.sh DS920+ noclean

 

Right, Pocopico?

 

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

hi, any try to add more than 16HDD?

i successful install 3615 and add 17HDD - 1 on MD sata and 16 on LSI,

edit user_config.json

    "SataPortMap": "616",
    "DiskIdxMap": "0001"

          "internalportcfg" : "0x3FFFFFFFF",
          "maxdisks" : "36",

but USB HDDs connect as internal

 

 

 

  • Like 1
Link to comment
Share on other sites

[NOTICE]

 

The ext, r8152, of the RealTek USB-type NIC has been replaced with the stable bb-qq's r8152.ko.

Normal use is now available.


Both 1GB and 2.5GB speed NICs are supported.

Currently, all six models except the DS1621+ have been tested successfully.
(The V1000 platform, DS1621+, is not yet on the repo of bb-qq.)


The test of the 2.5GB product was helped by @dolbycat.

Before building m-shell or just before building to TC rploader.sh

Please add the ext shared below first.

Since r8152 is not automatically added, there is no need to worry about duplicate generation.

 

------------------------------------------------------------------------

 

 

./rploader.sh ext apollolake-7.1.0-42661 add https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/r8152/rpext-index.json

 

./rploader.sh ext bromolow-7.1.0-42661 add https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/r8152/rpext-index.json

 

./rploader.sh ext broadwell-7.1.0-42661 add https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/r8152/rpext-index.json

 

./rploader.sh ext broadwellnk-7.1.0-42661 add https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/r8152/rpext-index.json

 

./rploader.sh ext denverton-7.1.0-42661 add https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/r8152/rpext-index.json

 

./rploader.sh ext geminilake-7.1.0-42661 add https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/r8152/rpext-index.json

Edited by Peter Suh
Link to comment
Share on other sites

56 minutes ago, Peter Suh said:

[NOTICE]

 

The ext, r8152, of the RealTek USB-type NIC has been replaced with the stable bb-qq's r8152.ko.

Normal use is now available.


Both 1GB and 2.5GB speed NICs are supported.

Currently, all six models except the DS1621+ have been tested successfully.
(The V1000 platform, DS1621+, is not yet on the repo of bb-qq.)


The test of the 2.5GB product was helped by @dolbycat.

Before building m-shell or just before building to TC rploader.sh

Please add the ext shared below first.

Since r8152 is not automatically added, there is no need to worry about duplicate generation.

 

------------------------------------------------------------------------

 

 

./rploader.sh ext apollolake-7.1.0-42661 add https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/r8152/rpext-index.json

 

./rploader.sh ext bromolow-7.1.0-42661 add https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/r8152/rpext-index.json

 

./rploader.sh ext broadwell-7.1.0-42661 add https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/r8152/rpext-index.json

 

./rploader.sh ext broadwellnk-7.1.0-42661 add https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/r8152/rpext-index.json

 

./rploader.sh ext denverton-7.1.0-42661 add https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/r8152/rpext-index.json

 

./rploader.sh ext geminilake-7.1.0-42661 add https://raw.githubusercontent.com/PeterSuh-Q3/rp-ext/master/r8152/rpext-index.json

 

The rp-ext repo of pocopico also just finished.

 

I want to use the pocopico one rather than my ext.

Link to comment
Share on other sites

Hi,

Trying to install 7.1 from 6.2.3 but i get no ip with my 10gbe card installed.

 

is there drivers i can install when making tcrp build on usb stick, as this is the only way i can get an ip if i take the Intel X520-2 10gbe card out.

 

Pocopico has been trying to help here https://xpenology.com/forum/topic/61547-no-ip-with-tcrp-046-img-loader

 

cheers guys

Link to comment
Share on other sites

19 hours ago, Spats said:

 

 

is there drivers i can install when making tcrp build on usb stick, as this is the only way i can get an ip if i take the Intel X520-2 10gbe card out.

 

19 hours ago, Spats said:

 

I am using Intel X520, RedPill TinyCore Loader can auto detect my card during custom_config.json, ./rploader.sh ext broadwellnk-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/igp/rpext-index.json should be the driver

 

  • Like 1
Link to comment
Share on other sites

 

[NOTICE]

 

@pocopico's ext, r8152, of the RealTek USB-type NIC has been replaced with the stable bb-qq's r8152.ko.

Normal use is now available.

Both 1GB and 2.5GB speed NICs are supported.

Currently, all six models except the DS1621+ have been tested successfully.
(The V1000 platform, DS1621+, is not yet on the repo of bb-qq.)


The test of the 2.5GB product was helped by @dolbycat.

This requires manual addition of the r8152 ext as "myv.sh" or "rploader.sh".

Since r8152 is not automatically added, there is no need to worry about duplicate generation.

 

@dolbycat's
Reporting for RealTek 2.5g usb NICs.
Maybe it's not limited to 2.5G, but it's also the same for 1G.

The xHCI of the USB option must not be disabled in the BIOS.
Activation must be enabled.

In addition, there is a phenomenon that USB NICs are recognized before internal NICs.

Edited by Peter Suh
Link to comment
Share on other sites

20 hours ago, Spats said:

Hi,

Trying to install 7.1 from 6.2.3 but i get no ip with my 10gbe card installed.

 

is there drivers i can install when making tcrp build on usb stick, as this is the only way i can get an ip if i take the Intel X520-2 10gbe card out.

 

Pocopico has been trying to help here https://xpenology.com/forum/topic/61547-no-ip-with-tcrp-046-img-loader

 

cheers guys

 

 

I think I will probably have the same problem with the 10G NIC of the same chipset as the post below.
See the answers in this post.

 

 

Link to comment
Share on other sites

5 minutes ago, Spats said:

 

 

You were DS918+, not DS3622xs+.
This is another matter.
I don't know how many NICs there are
It would be better to check the log first.
It may be difficult, but send the log using the method below.

If you can access the DSM installation request screen with ttyd as below,
Then send me the log with the command you see.

http://<youripaddr>:7681/

id : root / pw : ( no password )

cat /var/log/junior_reason

cat /var/log/*rc*

 

P.S: Are there any additional NICs other than this 10GB NIC?

 

You already have two NICs.
Then I should be able to get an IP grant from 1gbe
Perhaps the intel X520-2 is interfering as below
intel X520-2 10gbe
intel 1gbe

Loading kmod #0 "dca.ko" for pocopico.igb (args: )
Loading kmod #1 "igb.ko" for pocopico.igb (args: )
Loading kmod #0 "udp_tunnel.ko" for pocopico.ixgbe (args: )
Loading kmod #1 "ip6_udp_tunnel.ko" for pocopico.ixgbe (args: )
Loading kmod #2 "dca.ko" for pocopico.ixgbe (args: )
insmod: can't insert 'dca.ko': File exists
ERROR: kernel extensions "dca.ko" from pocopico.ixgbe failed to load
Exit on error [99] rp ext init exec failure...

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

6 minutes ago, Peter Suh said:

 

You were DS918+, not DS3622xs+.
This is another matter.
I don't know how many NICs there are
It would be better to check the log first.
It may be difficult, but send the log using the method below.

If you can access the DSM installation request screen with ttyd as below,
Then send me the log with the command you see.

http://<youripaddr>:7681/

id : root / pw : ( no password )

cat /var/log/junior_reason

cat /var/log/*rc*

 

P.S: Are there any additional NICs other than this 10GB NIC?

Yes mate Intel 1gbe port, so that makes the 3 mac addresses added to the user_config.json before building.

Edited by Spats
Link to comment
Share on other sites

27 minutes ago, Peter Suh said:

 

Does the Intel X520-2 have dual ports?

Yes mate, it worked ok in 6.2.3 before installing 7.1

 

Ttyd is just flashing on screen, using WinSCP but no junior_reason in var/log.

Edited by Spats
Link to comment
Share on other sites

Hi,

I have a strange issue with the "Update & restore" function.

It says "connection failed" and the "Release notes" link goes to example.com:

 

Example.thumb.png.893147780e0073da087868b5f39f30a1.png

 

All others functions works well (let's encrypt renew, hdd database update...)

I didn't have this problem in 6.2 (migrated configuration from 6.2, DS3617)

 

Regards.

 

Link to comment
Share on other sites

30 minutes ago, Spats said:

Yes mate, it worked ok in 6.2.3 before installing 7.1

 

Ttyd is just flashing on screen, using WinSCP but no junior_reason in var/log.

 

The order I guided was wrong.
Ttyd is not yet available
Do the following in TC Linux.

 

Use the command below to secure the ./redpill-load directory
./rploader.sh build apollolake-7.0.1-42218

Send the automatically added ext list with the command below first.
ll ./redpill-load/c*/e*

  • Like 1
Link to comment
Share on other sites

7 minutes ago, Biocef said:

Hi,

I have a strange issue with the "Update & restore" function.

It says "connection failed" and the "Release notes" link goes to example.com:

 

Example.thumb.png.893147780e0073da087868b5f39f30a1.png

 

All others functions works well (let's encrypt renew, hdd database update...)

I didn't have this problem in 6.2 (migrated configuration from 6.2, DS3617)

 

Regards.

 

 

Don't worry too much.
It can happen in XPENOLOGY.

Link to comment
Share on other sites

./redpill-load directory permission denied

./redpill-load/c*/e* permission denied

strange

 

tc@box:~$ ll ./redpill-load/c*/e*
total 4
-rw-r--r-- 1 tc   staff 920 May 11 14:37 REALLY_README.txt
drwxr-sr-x 3 tc   staff  80 May 11 14:38 pocopico.ixgbe/
drwxr-sr-x 3 tc   staff  80 May 11 14:38 pocopico.r8169/
drwxr-sr-x 3 root staff  80 May 11 14:38 thethorgroup.boot-wait/
drwxr-sr-x 3 root staff  80 May 11 14:38 thethorgroup.virtio/
tc@box:~$ ./redpill-load directory
-sh: ./redpill-load: Permission denied

 

Edited by Spats
Link to comment
Share on other sites

il y a 29 minutes, Peter Suh a dit :

 

Don't worry too much.
It can happen in XPENOLOGY.

 

Ok, thanks!

 

With Xpenology you had to delete the .xpenoboot folder located in the root folder apparently.

Is there a similar solution with Redpill?

 

Link to comment
Share on other sites

[Notice]

 

As TC is re-versioned, the method of copying and using modified dts files has changed a little.

 

The modified dts file need to copy it to this folder.

 

custom-module -> /mnt/sdb3/auxfiles

 

If you do that

 

./my.sh DS920+ manual

 

instead

 

./my.sh DS920+

 

It doesn't matter if you remove the manual like this.

 

The reason for using the original manual is to prevent automatic dts mapping in TC like that.

 

Now, if a file copied to a separate directory is found, dtc auto-mapping will stop automatically.

Edited by Peter Suh
Link to comment
Share on other sites

Hi Peter,

 

I am trying to install 918+ 7.1 on a Lenovo pc, but keep getting these errors. Can you please help? Thank you!

 

I installed 7.1 on this same pc successfully last month.

No idea why I keep getting this error this time. Tried different USB drives, tried 920+, tried more than 10 times yerterday...no luck.

 

 

These are the latest outputs:

tc@box:~$ ./rploader.sh build apollolake-7.0.1-42218
....
Mounting /dev/sda1 to localdiskp1 
/dev/sda2 localdiskp2
cp: error writing 'localdiskp1/zImage': No space left on device
Creating tinycore entry
....

 

tc@box:~$ ./rploader.sh build apollolake-7.1.0-42661
...
Mounting /dev/sda1 to localdiskp1 
/dev/sda2 localdiskp2
cp: error writing 'localdiskp1/boot/grub/i386-pc/gcry_tiger.mod': No space left on device
cp: error writing 'localdiskp1/boot/grub/locale/ru.mo': No space left on device
cp: error writing 'localdiskp1/boot/grub/x86_64-efi/gcry_sha512.mod': No space left on device
cp: error writing 'localdiskp1/custom.gz': No space left on device
cp: error writing 'localdiskp1/rd.gz': No space left on device
cp: error writing 'localdiskp1/zImage': No space left on device
Creating tinycore entry
...

 

 

This pc has a 4G RAM. I used tinycore-redpill-uefi.v0.4.6.img and followed these steps:

./rploader.sh update now
./rploader.sh fullupgrade now
./rploader.sh serialgen DS918+
./rploader.sh identifyusb now
./rploader.sh satamap now
./rploader.sh build apollolake-7.0.1-42218
./rploader.sh clean now
./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;

 

 

If I use this USB drive to boot the pc, I can see these outputs and then the pc reboots.  And then "Booting RedPill" again, and then the pc reboots again. It is a loop.

Booting 'RedPill BS918+ v7.1.0-42261 (USB, Verbose)'
Loading Linux...
Loading initramfs...
Starting kernel with USB boot

 

 

 

 

 

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