Jump to content
XPEnology Community

RedPill TinyCore Loader Installation Guide for DSM 7.1 BareMetal


Peter Suh

Recommended Posts

On 4/28/2022 at 11:12 AM, Peter Suh said:

(Notice)

The 42661 nano U1 download function, which has been changed this time in @pocopico's TC, has not been changed yet.
So, to make up for this, we added the function of pre-downloading 42661 nano U1 files to the new URL of the changed U1.
This feature allows you to avoid errors caused by downloading within TC, which is still before the change.

 

(Automatic updates are supported for users who downloaded after April 24, but users who downloaded before that should receive new updates.)

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

 

1.This is a shell script that executes several commands at once as described in the "Redpill Tinycore Loader DSM 7.1 Build" guide.

 

To use, you can download and untar it as follows and use it in the /home/tc directory.

 

Helps build DSM 7.1 by managing the PAT file directory required for decryption.

 

Automatically add mac2 to user_config.json file for dual NIC, a feature that TC doesn't have.

 

( Manual Response Version )

tc@box:~$ wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/m.sh.gz; tar -zxvf m.sh.gz;

 

( Auto Answer Version with y )
tc@box:~$ wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/my.sh.gz; tar -zxvf my.sh.gz;

 

Where y is unnecessarily asked, it automatically responds.


./my.sh DS918+

./my.sh DS3617xs

./my.sh DS3615xs

./my.sh DS3622xs+

./my.sh DVA3221

./my.sh DS920+

./my.sh DS1621+
 

1106259566_2022-04-248_32_51.thumb.png.9a36269259ddae7993e344fb7b4f5350.png.a7ab3e69a5e1228a4bd7a8458b64d83b.png

 

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

 

2. Deploy scripts that you can leverage if you need to add a separate ext manually for VM users.

It includes the fuction to add exts created by @FOXBI with multiple selections like capture.

 

For the instructions on how to use, you can download and decompress as below and use it in /home/tc directory.

 

( Auto Answer Version with y )

tc@box:~$ wget https://github.com/PeterSuh-Q3/tinycore-redpill/raw/main/myv.sh.gz; tar -zxvf myv.sh.gz;

 

The way to use it is existing same as my.sh. Where y is unnecessarily asked, it automatically responds.

 

./myv.sh DS918+

./myv.sh DS3617xs

./myv.sh DS3615xs

./myv.sh DS3622xs+

./myv.sh DVA3221

./myv.sh DS920+

./myv.sh DS1621+
1573609525_2022-04-199_54_07.thumb.png.f44c890de62c6f8b6d71d4abb9279c36.png.fb04d59fd3ad8bd8159478580256056d.png.150ef725e27aa575a7600ccaa439c456.png

 

CAUTION) Not all exts correspond to 7.1.0-42661.
Please check @pocopico's ext GITHUB in advance and use it.
We do not respond to errors caused by unsupported revisions.

Many thanks. After 2 days of getting nowhere. This worked perfectly for me. I am now rocking DS3622xs+ 7.1.0 on my HP Microserver Gen8 (Baremetal). All data migrated OK

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

Does anybody experience these errors after updating from 7.0.1 to 7.1?

Spoiler

[    2.821139] ahci: probe of 0001:01:00.0 failed with error -22
[    2.821414] ahci: probe of 0001:00:12.0 failed with error -22
[    2.821704] intel-lpss: probe of 0001:00:16.0 failed with error -22
[    2.821778] intel-lpss: probe of 0001:00:18.0 failed with error -22
[    2.821921] intel-lpss: probe of 0001:00:19.0 failed with error -22
[    2.821931] intel-lpss: probe of 0001:00:19.2 failed with error -22
[    3.712561] xhci_hcd: probe of 0001:00:15.0 failed with error -16
[    6.256939] <redpill/bios_shim.c:215> Symbol #54 in mfgBIOS "apollolake_synobios" {synobios_sata_error_report}<ffffffffa0107460>
[    6.258057] <redpill/bios_shim.c:215> Symbol #56 in mfgBIOS "apollolake_synobios" {synobios_record_scsi_error_event}<ffffffffa0107510>
[    6.258638] <redpill/bios_shim.c:215> Symbol #57 in mfgBIOS "apollolake_synobios" {synobios_error_btrfs_meta_corrupted_event}<ffffffffa0107570>
[    6.259260] <redpill/bios_shim.c:215> Symbol #58 in mfgBIOS "apollolake_synobios" {synobios_error_fs_btrfs_event}<ffffffffa01075c0>
[    6.259833] <redpill/bios_shim.c:215> Symbol #59 in mfgBIOS "apollolake_synobios" {synobios_error_fs_event}<ffffffffa0107610>
[    6.262062] <redpill/bios_shim.c:215> Symbol #63 in mfgBIOS "apollolake_synobios" {synobios_error_oom_event}<ffffffffa0107840>
[   15.008960] igb: probe of 0001:02:00.0 failed with error -5
[   15.009242] igb: probe of 0001:03:00.0 failed with error -5
[   15.255436] i915 0000:00:02.0: Direct firmware load for i915/kbl_dmc_ver1_04.bin failed with error -2
[   16.092482] <redpill/bios_shim.c:215> Symbol #54 in mfgBIOS "apollolake_synobios" {synobios_sata_error_report}<ffffffffa06a4460>
[   16.093609] <redpill/bios_shim.c:215> Symbol #56 in mfgBIOS "apollolake_synobios" {synobios_record_scsi_error_event}<ffffffffa06a4510>
[   16.094198] <redpill/bios_shim.c:215> Symbol #57 in mfgBIOS "apollolake_synobios" {synobios_error_btrfs_meta_corrupted_event}<ffffffffa06a4570>
[   16.094824] <redpill/bios_shim.c:215> Symbol #58 in mfgBIOS "apollolake_synobios" {synobios_error_fs_btrfs_event}<ffffffffa06a45c0>
[   16.095406] <redpill/bios_shim.c:215> Symbol #59 in mfgBIOS "apollolake_synobios" {synobios_error_fs_event}<ffffffffa06a4610>
[   16.097637] <redpill/bios_shim.c:215> Symbol #63 in mfgBIOS "apollolake_synobios" {synobios_error_oom_event}<ffffffffa06a4840>

 

 

The SSH command is

dmesg | grep error

 

Link to comment
Share on other sites

3 hours ago, jrockow said:

I have successfully installed DSM7.1 as a DS3615xs and it seems to work well.

My problem is I don't see a device "/dev/dri" which I need to do HW transcoding in Jellyfin.

Is there someway I can add that?

Thanx.

Ds3615xs can NOT transcode!!! 

 

For /dev/dri try DS918+......or DS920 model! 

Link to comment
Share on other sites

4 hours ago, jrockow said:

I have successfully installed DSM7.1 as a DS3615xs and it seems to work well.

My problem is I don't see a device "/dev/dri" which I need to do HW transcoding in Jellyfin.

Is there someway I can add that?

Thanx.

 

I know about ds918+ and ds920+ models that support H/W transcoding, isn't it?

The rest of the models are only available for S/W transcoding, and that directory can be checked in both models,

and it seems that it is not something that can be created by force?

Link to comment
Share on other sites

4 hours ago, giacomoleopardo said:

Does anybody experience these errors after updating from 7.0.1 to 7.1?

  dmesg | grep error (Reveal hidden contents)


[    2.821139] ahci: probe of 0001:01:00.0 failed with error -22
[    2.821414] ahci: probe of 0001:00:12.0 failed with error -22
[    2.821704] intel-lpss: probe of 0001:00:16.0 failed with error -22
[    2.821778] intel-lpss: probe of 0001:00:18.0 failed with error -22
[    2.821921] intel-lpss: probe of 0001:00:19.0 failed with error -22
[    2.821931] intel-lpss: probe of 0001:00:19.2 failed with error -22
[    3.712561] xhci_hcd: probe of 0001:00:15.0 failed with error -16
[    6.256939] <redpill/bios_shim.c:215> Symbol #54 in mfgBIOS "apollolake_synobios" {synobios_sata_error_report}<ffffffffa0107460>
[    6.258057] <redpill/bios_shim.c:215> Symbol #56 in mfgBIOS "apollolake_synobios" {synobios_record_scsi_error_event}<ffffffffa0107510>
[    6.258638] <redpill/bios_shim.c:215> Symbol #57 in mfgBIOS "apollolake_synobios" {synobios_error_btrfs_meta_corrupted_event}<ffffffffa0107570>
[    6.259260] <redpill/bios_shim.c:215> Symbol #58 in mfgBIOS "apollolake_synobios" {synobios_error_fs_btrfs_event}<ffffffffa01075c0>
[    6.259833] <redpill/bios_shim.c:215> Symbol #59 in mfgBIOS "apollolake_synobios" {synobios_error_fs_event}<ffffffffa0107610>
[    6.262062] <redpill/bios_shim.c:215> Symbol #63 in mfgBIOS "apollolake_synobios" {synobios_error_oom_event}<ffffffffa0107840>
[   15.008960] igb: probe of 0001:02:00.0 failed with error -5
[   15.009242] igb: probe of 0001:03:00.0 failed with error -5
[   15.255436] i915 0000:00:02.0: Direct firmware load for i915/kbl_dmc_ver1_04.bin failed with error -2
[   16.092482] <redpill/bios_shim.c:215> Symbol #54 in mfgBIOS "apollolake_synobios" {synobios_sata_error_report}<ffffffffa06a4460>
[   16.093609] <redpill/bios_shim.c:215> Symbol #56 in mfgBIOS "apollolake_synobios" {synobios_record_scsi_error_event}<ffffffffa06a4510>
[   16.094198] <redpill/bios_shim.c:215> Symbol #57 in mfgBIOS "apollolake_synobios" {synobios_error_btrfs_meta_corrupted_event}<ffffffffa06a4570>
[   16.094824] <redpill/bios_shim.c:215> Symbol #58 in mfgBIOS "apollolake_synobios" {synobios_error_fs_btrfs_event}<ffffffffa06a45c0>
[   16.095406] <redpill/bios_shim.c:215> Symbol #59 in mfgBIOS "apollolake_synobios" {synobios_error_fs_event}<ffffffffa06a4610>
[   16.097637] <redpill/bios_shim.c:215> Symbol #63 in mfgBIOS "apollolake_synobios" {synobios_error_oom_event}<ffffffffa06a4840>

 

 

The SSH command is


dmesg | grep error

 

 

I also upgraded from 7.0.1 to 7.1, and as a result of executing the command you gave me, I also see an error.
I'm curious as to what effect this error could have.

 

admin2@NAS4:~$ dmesg | grep error
[    6.280694] ahci: probe of 0001:09:00.0 failed with error -22
[    6.280698] ahci: probe of 0001:0c:00.0 failed with error -22
[    6.281264] parameter error. gpiobase=00000000, pin=0, pValue=ffff880421c5fd6c
[   19.863359] <redpill/bios_shim.c:215> Symbol #44 in mfgBIOS "broadwellnk_synobios" {synobios_sata_error_report}<ffffffffa022be60>
[   19.886542] <redpill/bios_shim.c:215> Symbol #46 in mfgBIOS "broadwellnk_synobios" {synobios_record_scsi_error_event}<ffffffffa022bf10>
[   19.898652] <redpill/bios_shim.c:215> Symbol #47 in mfgBIOS "broadwellnk_synobios" {synobios_error_btrfs_meta_corrupted_event}<ffffffffa022bf60>
[   19.911535] <redpill/bios_shim.c:215> Symbol #48 in mfgBIOS "broadwellnk_synobios" {synobios_error_fs_btrfs_event}<ffffffffa022bfb0>
[   19.923386] <redpill/bios_shim.c:215> Symbol #49 in mfgBIOS "broadwellnk_synobios" {synobios_error_fs_event}<ffffffffa022c000>
[   19.981603] <redpill/bios_shim.c:215> Symbol #54 in mfgBIOS "broadwellnk_synobios" {synobios_error_oom_event}<ffffffffa022c220>
[   40.354933] <redpill/bios_shim.c:215> Symbol #44 in mfgBIOS "broadwellnk_synobios" {synobios_sata_error_report}<ffffffffa0bf6e60>
[   40.379504] <redpill/bios_shim.c:215> Symbol #46 in mfgBIOS "broadwellnk_synobios" {synobios_record_scsi_error_event}<ffffffffa0bf6f10>
[   40.391614] <redpill/bios_shim.c:215> Symbol #47 in mfgBIOS "broadwellnk_synobios" {synobios_error_btrfs_meta_corrupted_event}<ffffffffa0bf6f60>
[   40.404503] <redpill/bios_shim.c:215> Symbol #48 in mfgBIOS "broadwellnk_synobios" {synobios_error_fs_btrfs_event}<ffffffffa0bf6fb0>
[   40.416356] <redpill/bios_shim.c:215> Symbol #49 in mfgBIOS "broadwellnk_synobios" {synobios_error_fs_event}<ffffffffa0bf7000>
[   40.474585] <redpill/bios_shim.c:215> Symbol #54 in mfgBIOS "broadwellnk_synobios" {synobios_error_oom_event}<ffffffffa0bf7220>
[   76.643234] [17006]: ocs_fc_lio: ocs_driver_print_module_params:1265::  sliport_pause_errors = disabled
                        disk read errors(0), disk write errors(0) ssd read errors(0) ssd write errors(0)

Link to comment
Share on other sites

m shell (m.sh / my.sh / myv.sh) This is today's version upgrade.

Option processing function has been added as shown in the help below.

 

Please refer to the pre-shared post below for the purpose of each script.

 

 

Usage: ./my.sh <Synology Model Name> <Options>

 

Options: noconfig, noclean, manual

 

- noconfig: SKIP automatic detection change processing such as SN/Mac/Vid/Pid/SataPortMap of user_config.json file.

 

- noclean: SKIP the 💊   RedPill LKM/LOAD directory without clearing it with the Clean now command. 
           However, m shell delete the Cache directory and loader.img.

 

- manual: Options for manual extension processing and manual dtc processing in build action (skipping extension auto detection)

 

Please type Synology Model Name after ./my.sh

 

./my.sh DS918+
./my.sh DS3617xs
./my.sh DS3615xs
./my.sh DS3622xs+
./my.sh DVA3221
./my.sh DS920+
./my.sh DS1621+

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

On 4/17/2022 at 6:40 PM, Peter Suh said:

 

Send a log of the two commands below from the TC Linux prompt.

lspci -tvnnq

 

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

 

If you followed my instructions and completed the backup,

The /home/tc/redpill-load directory would have been erased.

Then, do the rebuild as below and send the dts file contents

 

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

 

mkdir /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles; sudo ln -s /mnt/"$(mount | grep -i optional | grep cde | awk -F / '{print $3}' | uniq | cut -c 1-3)3"/auxfiles /home/tc/custom-module;

 

./rploader.sh build geminilake-7.1.0-42661


cat /home/tc/redpill-load/ds920p.dts

hi,all, @Peter Suh, My MB is a Asrock J5005itx, It is a geminilake system. MB's storage config - 2 x SATA3 6.0 Gb/s Connectors, support NCQ, AHCI and Hot Plug
- 2 x SATA3 6.0 Gb/s Connectors by ASMedia ASM1061, support NCQ, AHCI and Hot Plug. It is working normally when i installed the DSM7.1 as a DS918+, but the DSM7.1 donn't detect the disks which connect to the ASM1061 when i installed the DSM7.1 as a DS920+,other disks are working normally. Help me, Please.

tvnnq.PNG

ds920p.dts

Edited by Peter Qu
Link to comment
Share on other sites

15 hours ago, Peter Qu said:

hi,all, @Peter Suh, My MB is a Asrock J5005itx, It is a geminilake system. MB's storage config - 2 x SATA3 6.0 Gb/s Connectors, support NCQ, AHCI and Hot Plug
- 2 x SATA3 6.0 Gb/s Connectors by ASMedia ASM1061, support NCQ, AHCI and Hot Plug. It is working normally when i installed the DSM7.1 as a DS918+, but the DSM7.1 donn't detect the disks which connect to the ASM1061 when i installed the DSM7.1 as a DS920+,other disks are working normally. Help me, Please.

tvnnq.PNG

ds920p.dts 2.37 kB · 3 downloads

 

I don't see any trace of TC auto-mapping the dtc
Do You edit it manually and build it with a tool-chain?

 

Considering the lspci information, it should be configured as below.
For accurate ata_port settings,
Check and map the port to ll/sys/block on the Linux boot.

 

 

internal_slot@1 {

ahci {

pcie_root = "00:13.3,00.0";

ata_port = <0x0>;

};

 

internal_slot@2 {

ahci {

pcie_root = "00:13.3,00.0";

ata_port = <0x1>;

};

 

};

 

internal_slot@3 {

ahci {

pcie_root = "00:12.0";

ata_port = <0x0>;

};

};

 

internal_slot@4 {

ahci {

pcie_root = "00:12.0";

ata_port = <0x1>;

};

};

Edited by Peter Suh
Link to comment
Share on other sites

5 minutes ago, Peter Suh said:

 

I don't see any trace of TC auto-mapping the dtc
Do You edit it manually and build it with a tool-chain?

 

Considering the lspci information, it should be configured as below.
For accurate ata_port settings,
Check and map the port to ll/sys/block on the Linux boot.

 

 

internal_slot@1 {

ahci {

pcie_root = "00:13.3,00.0";

ata_port = <0x0>;

};

 

internal_slot@2 {

ahci {

pcie_root = "00:13.3,00.0";

ata_port = <0x1>;

};

 

};

 

internal_slot@3 {

ahci {

pcie_root = "00:12.0";

ata_port = <0x0>;

};

};

 

internal_slot@4 {

ahci {

pcie_root = "00:12.0";

ata_port = <0x1>;

};

};

thank you so much, i don't edit anything, i just build the bootloader in m.sh

Link to comment
Share on other sites

6 minutes ago, Peter Qu said:

thank you so much, i don't edit anything, i just build the bootloader in m.sh

 

 

If you have to rely entirely on "TC+m.sh", you have to do it differently.
m.sh should be updated to the latest version and built in the next order.

1 ./m.sh DS920+ noclean

2 vi ./redpill-load/ds920p.dts
(Change to the above information)

3. ./m.sh DS920+ manual

 

If you want to double-check what is clearly applied, just check with the command below.

cat ./redpill-load/custom/extensions/redpill-dtb/ds920p_42661/model_ds920p.dtb

It looks like a broken Hexa code, but you will see the figures of 13.3, 12.0, etc. you set.

Edited by Peter Suh
Link to comment
Share on other sites

Hi Peter Suh,

I'm a Asrock J4205 owner.

Actually i'm doing tests with J4205 and a spend a looooot of time tryin to make functionally the DSM 7.01 and 7.1.0

I dont'w know why but scripts and images form 918+ and 920+ doesn't work. Problems with SATA detection and DTS config.

When config is detected, in DTS apears the onboard NIC Gigabit 13.0 in internal slots. Maybe it's the reason because we loose the IP address during boot. 

 

image.thumb.png.7436afe932a570db43d6e653cca5c584.png

 

vi /home/tc/redpill-load/ds920p.dts

image.thumb.png.6c2a607dfcff53976b29eb8a2ccfa622.png

 

the motherboard has a m2 sata port also, but not have a esata port

 

This motherboard has 2 internal SATA controllers with 2 SATA port per controller = 4 SATA ports

image.png.9707dd4b46e9a224cfaa8e6726b29885.png

 

Edited by chechill
Link to comment
Share on other sites

New info recently discovered.

After a new manual installation using this manual --> 

 

I get whis info when DMS is installed.

Why i have new Marvell Technology Group 4 port SATA, not shown in last capture?

image.thumb.png.2229dbbe526a23cc467bb8d6f37a68ea.png

 

I dont wknow whitch one is the good one. 1 controller with 4 SATA ports or 2 controllers with 2 sata ports per controller :(

 

 

Edited by chechill
Link to comment
Share on other sites

3 hours ago, chechill said:

New info recently discovered.

After a new manual installation using this manual --> 

 

I get whis info when DMS is installed.

Why i have new Marvell Technology Group 4 port SATA, not shown in last capture?

image.thumb.png.2229dbbe526a23cc467bb8d6f37a68ea.png

 

I dont wknow whitch one is the good one. 1 controller with 4 SATA ports or 2 controllers with 2 sata ports per controller :(

 

 

 

Check the target number with the ll /sys/block command and map it to ata_port.
In fact, the disk mounted on the controller can also be checked with the above command.
In ds918+, the Marvel controller is a virtual SATA controller when verified by lspci -tvnnq. Ignore it.

Link to comment
Share on other sites

28 minutes ago, chechill said:

With 2 disks, one in each controller

00:12.0 and 00:13.2

image.thumb.png.33ad12b4e0151b5ca1fa8497d1ecb56d.png

 

Yoy know why it 's too slow to get IP. Normally 10 minutes. The NIC is a Realteck RTL8168B

 

 

The DS920+ takes a little more time to provide IP to the NIC, but not 10 minutes.

If you haven't installed DSM PAT yet, you should capture the log according to the method below and ask @pocopico.

 

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


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

http://<youripaddress>:7681/

id : root / pw : ( no password )

cat /var/log/junior_reason

cat /var/log/*rc*

Edited by Peter Suh
Link to comment
Share on other sites

I'll do it. 

You know if 918+ takes same time as 920+?

Normally i have the NAS shuwdown and i use a WOL. For me the less time to boot is better.

I supose that the best version for my J4205 with internal graphics is 918+ or 920+ witch supports transcoding

 

Thanks for all and for your support.

 

Edited by chechill
Link to comment
Share on other sites

9 minutes ago, chechill said:

I'll do it. 

You know if 918+ takes same time as 920+?

Normally i have the nas shuwdowns and i use a WOL. For me the less time to boot is better.

 

Thanks for all and for your support.

 

 

Restarting the NAS after shutting down the WOL and booting time of the NIC seem to have nothing to do with it.
It is important to check the log mentioned above first.

Looking at your PCI information, it seems that Intel dual NICs are also visible, not single NIC.
Sometimes the exts of these NICs affect each other and delay booting.
In any case, it is important to look at the log results first.

Link to comment
Share on other sites

Hope that will help :)

 

DiskStation> cat /var/log/junior_reason
Exit on error [7] root not matched with junior...

 

 

DiskStation> cat /var/log/*rc*
START /linuxrc.syno.impl
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 "mii.ko" for pocopico.r8169 (args: )
Loading kmod #1 "r8169.ko" for pocopico.r8169 (args: )
:: Loading kernel modules from extensions ... [  OK  ]
:: Executing "on_boot" custom scripts ...
Running "check-r8169.sh" for pocopico.r8169->on_boot
Loading module r8169 -> Module r8169 loaded succesfully
Ran "check-r8169.sh" for pocopico.r8169->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)
Still waiting for boot device (waited 5 of 30 seconds)
Still waiting for boot device (waited 6 of 30 seconds)
Still waiting for boot device (waited 7 of 30 seconds)
Still waiting for boot device (waited 8 of 30 seconds)
Still waiting for boot device (waited 9 of 30 seconds)
Still waiting for boot device (waited 10 of 30 seconds)
Still waiting for boot device (waited 11 of 30 seconds)
Still waiting for boot device (waited 12 of 30 seconds)
Still waiting for boot device (waited 13 of 30 seconds)
Still waiting for boot device (waited 14 of 30 seconds)
Still waiting for boot device (waited 15 of 30 seconds)
Still waiting for boot device (waited 16 of 30 seconds)
Still waiting for boot device (waited 17 of 30 seconds)
Still waiting for boot device (waited 18 of 30 seconds)
Still waiting for boot device (waited 19 of 30 seconds)
Still waiting for boot device (waited 20 of 30 seconds)
Still waiting for boot device (waited 21 of 30 seconds)
Confirmed a valid-looking /dev/synoboot device
Ran "boot-wait.sh" for redpill-boot-wait->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
:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
Insert synorbd kernel module
Insert synofsbd kernel module
Insert sha256 kernel module
Assemble args: -u 5361bf9c:5e47119b:3017a5a8:c86610be /dev/sda1
mdadm: /dev/md0 has been started with 1 drive (out of 16).
Partition Version=9
 /sbin/e2fsck exists, checking /dev/md0... 
e2fsck 1.44.1 (24-Mar-2018)
/sbin/e2fsck -yvf returns 0
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
Failed to found any patch
No upgrade file found
============upgrade
------------bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/VERSION:buildnumber -> 42661
  value2: /tmpRoot/etc.defaults/VERSION:buildnumber => 42621
Skip bootup smallupdate, because root is not matched to junior
============bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/VERSION:buildnumber -> 42661
  value2: /tmpRoot/etc.defaults/VERSION:buildnumber => 42621
Exit on error [7] root not matched with junior...
Tue May  3 14:19:21 UTC 2022
/dev/md0 /tmpRoot ext4 rw,relatime,prjquota,rootprjquota,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0

 

 

Other question, during installation, when i edit vi /home/tc/ds920p.dts before make the ./rploader.sh build apollolake-7.1.0-42661 command,

I must erase that config? Because always match the pcie_root nic adress with this esata port during the auto-detection process

 

image.png.e9f17edb47fbfac3e71883053c5d3389.png

 

Edited by chechill
Link to comment
Share on other sites

11 minutes ago, chechill said:

Hope that will help :)

 

DiskStation> cat /var/log/junior_reason
Exit on error [7] root not matched with junior...

 

 

DiskStation> cat /var/log/*rc*
START /linuxrc.syno.impl
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 "mii.ko" for pocopico.r8169 (args: )
Loading kmod #1 "r8169.ko" for pocopico.r8169 (args: )
:: Loading kernel modules from extensions ... [  OK  ]
:: Executing "on_boot" custom scripts ...
Running "check-r8169.sh" for pocopico.r8169->on_boot
Loading module r8169 -> Module r8169 loaded succesfully
Ran "check-r8169.sh" for pocopico.r8169->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)
Still waiting for boot device (waited 5 of 30 seconds)
Still waiting for boot device (waited 6 of 30 seconds)
Still waiting for boot device (waited 7 of 30 seconds)
Still waiting for boot device (waited 8 of 30 seconds)
Still waiting for boot device (waited 9 of 30 seconds)
Still waiting for boot device (waited 10 of 30 seconds)
Still waiting for boot device (waited 11 of 30 seconds)
Still waiting for boot device (waited 12 of 30 seconds)
Still waiting for boot device (waited 13 of 30 seconds)
Still waiting for boot device (waited 14 of 30 seconds)
Still waiting for boot device (waited 15 of 30 seconds)
Still waiting for boot device (waited 16 of 30 seconds)
Still waiting for boot device (waited 17 of 30 seconds)
Still waiting for boot device (waited 18 of 30 seconds)
Still waiting for boot device (waited 19 of 30 seconds)
Still waiting for boot device (waited 20 of 30 seconds)
Still waiting for boot device (waited 21 of 30 seconds)
Confirmed a valid-looking /dev/synoboot device
Ran "boot-wait.sh" for redpill-boot-wait->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
:: Executing "on_boot" custom scripts ... [  OK  ]
Extensions processed
Insert net driver(Mindspeed only)...
Starting /usr/syno/bin/synocfgen...
/usr/syno/bin/synocfgen returns 0
Insert synorbd kernel module
Insert synofsbd kernel module
Insert sha256 kernel module
Assemble args: -u 5361bf9c:5e47119b:3017a5a8:c86610be /dev/sda1
mdadm: /dev/md0 has been started with 1 drive (out of 16).
Partition Version=9
 /sbin/e2fsck exists, checking /dev/md0... 
e2fsck 1.44.1 (24-Mar-2018)
/sbin/e2fsck -yvf returns 0
Mounting /dev/md0 /tmpRoot
------------upgrade
Begin upgrade procedure
Failed to found any patch
No upgrade file found
============upgrade
------------bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/VERSION:buildnumber -> 42661
  value2: /tmpRoot/etc.defaults/VERSION:buildnumber => 42621
Skip bootup smallupdate, because root is not matched to junior
============bootup-smallupdate
Failed to AssertFileKeyValueEqual
  value1: /etc.defaults/VERSION:buildnumber -> 42661
  value2: /tmpRoot/etc.defaults/VERSION:buildnumber => 42621
Exit on error [7] root not matched with junior...
Tue May  3 14:19:21 UTC 2022
/dev/md0 /tmpRoot ext4 rw,relatime,prjquota,rootprjquota,data=ordered 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0

 

 

I don't know if pocopico will check if I leave a log like this here.
Do you know how to use annotations starting with @?

@chechill


Looking at the logs, I can't figure out why the r8169 NIC is delayed by 10 minutes.


And it seems to be trying to install DSM, but the revision seems to be inconsistent.
42661 and 42621 are different versions.
42661 is the official version, and 42621 is the RC version.

Edited by Peter Suh
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...