Jump to content
XPEnology Community

TinyCore RedPill Loader (TCRP)


pocopico

Recommended Posts

Hello

 

I use proxmox. I tired to install 918+7.0.1 on VM. It is work.

With 7.1 teh loader is finish, but dont boot...

 

Now I try to make 920+ 7.0.1 with redpill. It start to build loader, and it stop with error:

 

TARGET_PLATFORM       : geminilake
TARGET_VERSION    : 7.0.1
TARGET_REVISION : 42218
REDPILL_LKM_MAKE_TARGET : test-v7
KERNEL_MAJOR : 4
MODULE_ALIAS_FILE :  modules.alias.4.json
SYNOMODEL : ds920p_42218
MODEL : DS920+
Checking Internet Access -> OK
Checking if a newer version exists on the repo -> Version is current
Cloning into 'redpill-lkm'...
remote: Enumerating objects: 1248, done.
remote: Counting objects: 100% (1248/1248), done.
remote: Compressing objects: 100% (570/570), done.
remote: Total 1248 (delta 862), reused 1047 (delta 661), pack-reused 0
Receiving objects: 100% (1248/1248), 476.52 KiB | 3.75 MiB/s, done.
Resolving deltas: 100% (862/862), done.
Cloning into 'redpill-load'...
remote: Enumerating objects: 1656, done.
remote: Counting objects: 100% (1656/1656), done.
remote: Compressing objects: 100% (876/876), done.
remote: Total 1656 (delta 808), reused 1453 (delta 660), pack-reused 0
Receiving objects: 100% (1656/1656), 28.43 MiB | 15.41 MiB/s, done.
Resolving deltas: 100% (808/808), done.
No extra build option specified, using default <static>
Using static compiled redpill extension
Removing any old redpill.ko modules
Looking for redpill for : ds920p_42218
Module does not contain platorm information for ds920p_42218
tc@box:~$

 

What is wrong?

 

920+ 7.1 also successfully complied, booting, but dont find any hard drive :((

What can I try?

 

Thx

Edited by RedCat
Link to comment
Share on other sites

Hi All,

 

First of all, thank you @pocopico and @Peter Suh

 

Here are my findings.

Last week I was testing to install DSM 7.0.1-42218 on several machines.

 

First I used a SuperMicro server with an Intel Xeon L5630 cpu and 24Gb of ram.

So far so good, I could install version 7.0.1-42218 and installation is successfull.

 

After reading a lot posts over here, I tried to upgrade from 7.0.1-42218 to 7.1.0-42661 and it failed using the instruction of @Peter Suh

Even if I first installed 7.0.1-42218 complete and then upgrade, it failed, keeps nagging about corrupt file.

When I tried to do a fresh install, samething, keeps nagging about corrupt file, even when I downloaded the file from the cache on TC, same thing.

The following instructions was entered:

 

Quote

[DS3622xs+]

 

./rploader.sh update now

./rploader.sh fullupgrade now

 

./rploader.sh serialgen DS3622xs+

./rploader.sh identifyusb now

./rploader.sh satamap now (changed the diskidxmap to: 0000)

 

./rploader.sh build broadwellnk-7.0.1-42218

./rploader.sh clean now

./rploader.sh build broadwellnk-7.1.0-42661

 

./rploader.sh clean now;  rm -rf /mnt/sdb3/auxfiles;  rm -rf /home/tc/custom-module;  ./rploader.sh backup now;

 

Then after hours of trying I used the Dell R320 to give it a try.

Installing DSM 7.0.1-42218, perfect it runs and see all the drives.

The did a full wipe (so to have a clean installation, even drives where wiped).

Entered the instructions as noted by @Peter Suh

And it starts up to DSM 7.1, but just with one drive (no other sataport/drive where found).

 

Again, started to TC, did a clean instruction and changed the satamap to the following:

    "SataPortMap": "46",
    "DiskIdxMap": "0000"

 

rebuild everything again with ./rploader.sh build broadwellnk-7.1.0-42661

 

rebooted the server and started to DSM 7.1, did the installation steps en all drives where found.

 

It looks like something about which components you use ?

 

With every server I used, I have changed the mac adres to the mac adres from the nic's

 

I have installed now DS918+ on an asrock motherbord with an Apollo Lake cpu on it running DSM 7.0.1-42218

Will try to do an upgrade to DSM 7.1.0-42661 next time and will write to outcome here.

 

Thank you for reading this post

Kind regards

 

dsm71r320.png

Edited by MSXGames
Uploaded image of DSM 7.1.0
  • Like 1
Link to comment
Share on other sites

Thanks @pocopico !!!

 

Did it! force_junior was the right thing to get the System installed again with keeping my Raid-Set alive.

Great. Maybe my previous Installation was running, as I saw my PCIe Passthrough Devices weren't complete (X540-T2 was missing) so I powered off my ESXi VM while that.

 

That caused system failure in the OS I think.

 

Anyway, is running like Charm again.

 

114550945_Bildschirmfoto2022-04-11um18_07_14.thumb.png.bad808d817728bc295080d3eb28af5df.png

 

May somebody knows how I get my first Disk to my real first disk and not the VM Disk with the Bootloader on it???

 

Just cosmetic but may be easy? please @ me so I can read about it if you have an solution for this.

 

Config:  2x HBA (LSI 2008 IT) PCIe Passthrough; VM ESXi with 1 Disk (SATA) for TCRP; X540-T2 PCIe Passthrough, 4 Cores CPU; 16GB RAM

Edited by Kaneske
  • Like 2
Link to comment
Share on other sites

26 minutes ago, MSXGames said:

Hi All,

 

Here are my findings.

Last week I was testing to install DSM 7.0.1-42218 on several machines.

 

First I used a SuperMicro server with an Intel Xeon L5630 cpu and 24Gb of ram.

So far so good, I could install version 7.0.1-42218 and installation is successfull.

 

After reading a lot posts over here, I tried to upgrade from 7.0.1-42218 to 7.1.0-42661 and it failed using the instruction of @Peter Suh

Even if I first installed 7.0.1-42218 complete and then upgrade, it failed, keeps nagging about corrupt file.

When I tried to do a fresh install, samething, keeps nagging about corrupt file, even when I downloaded the file from the cache on TC, same thing.

The following instructions was entered:

 

 

Then after hours of trying I used the Dell R320 to give it a try.

Installing DSM 7.0.1-42218, perfect it runs and see all the drives.

The did a full wipe (so to have a clean installation, even drives where wiped).

Entered the instructions as noted by @Peter Suh

And it starts up to DSM 7.1, but just with one drive (no other sataport/drive where found).

 

Again, started to TC, did a clean instruction and changed the satamap to the following:

    "SataPortMap": "46",
    "DiskIdxMap": "0000"

 

rebuild everything again with ./rploader.sh build broadwellnk-7.1.0-42661

 

rebooted the server and started to DSM 7.1, did the installation steps en all drives where found.

 

It looks like something about which components you use ?

 

With every server I used, I have changed the mac adres to the mac adres from the nic's

 

I have installed now DS918+ on an asrock motherbord with an Apollo Lake cpu on it running DSM 7.0.1-42218

Will try to do an upgrade to DSM 7.1.0-42661 next time and will write to outcome here.

 

Thank you for reading this post

Kind regards

I have the t320 on 7.1. if your using SAS card (h310,h200, etc) one make sure the card is flashed to IT Mode, in user_config.json get rid of satamap and diskid and add "SasIdxMap": "0". If you are using the embedded Satas controller (6 Sata) then you need to us satamap and diskid: Satamap 6 and Diskid 00 and keep SasIdxMap. Hope this helps.

 

Edit @MSXGames Sorry I miss read your post. But I do have a question, did you use the cache pat file to install 7.1? I had to download it from the Synology website and install it as I kept getting the corrupted Fe when I would try and install. I had to go in and enable the shr settings but that was it.

Edited by Dvalin21
Link to comment
Share on other sites

45 minutes ago, ditheo said:

 

log in to serial console

 

and then go to /usr/syno/lib/systemd/scripts

 

give command : sudo ./syno-kernel-modules-load.sh

 

That I ran to my proxmox and the problem is gone. See if you can solve with this temporary solution

 

 

 

I was able to connect via telnet and execute the command.

Now my test NAS was not shutting down itself automatically!

 

While executing sudo ./syno-kernel-modules-load.sh I received the following error message: 
modprobe: ERROR: could not insert 'aesni_intel': No such device

 

Is it necessary to execute these command on each boot?

 

@pocopico is there a fix on horizon regarding this issue?

Link to comment
Share on other sites

1 minute ago, Dreadnought said:

 

I was able to connect via telnet and execute the command.

Now my test NAS was not shutting down itself automatically!

 

While executing sudo ./syno-kernel-modules-load.sh I received the following error message: 
modprobe: ERROR: could not insert 'aesni_intel': No such device

 

Is it necessary to execute these command on each boot?

 

@pocopico is there a fix on horizon regarding this issue?

 

I'm having the same issue on AMD systems. DSM is missing some prerequisites

 

70-crypto-kernel.conf :crc32c-intel
 

SynologyNAS> insmod /tmpRoot/lib/modules/crc32c-intel.ko
insmod: can't insert '/tmpRoot/lib/modules/crc32c-intel.ko': No such device

Link to comment
Share on other sites

1 minute ago, pocopico said:

 

I'm having the same issue on AMD systems. DSM is missing some prerequisites

 

70-crypto-kernel.conf :crc32c-intel
 

SynologyNAS> insmod /tmpRoot/lib/modules/crc32c-intel.ko
insmod: can't insert '/tmpRoot/lib/modules/crc32c-intel.ko': No such device

 

😅 but I have a Intel system.

Regarding the execution of the command "sudo ./syno-kernel-modules-load.sh" is there something you can fix?
Cause so I have to execute this command (with time presure) on each reboot/restart. 

 

Link to comment
Share on other sites

Just now, Dreadnought said:

 

😅 but I have a Intel system.

Regarding the execution of the command "sudo ./syno-kernel-modules-load.sh" is there something you can fix?
Cause so I have to execute this command (with time presure) on each reboot/restart. 

 

 

Did you add the redpill-misc extension ? 

Link to comment
Share on other sites

Just now, totikk said:

How did you activate telnet ?

 

A little work around.

  1. I installed 7.0.1 activated telnet via DSM-Settings
  2. Then I upgraded to DSM 7.1, via DSM settings too
  3. Reboot with a new stick with tinyLoader and created the 7.1 Loader
  4. while booting connected via telnet and executed the command
  • Thanks 1
Link to comment
Share on other sites

3 minutes ago, pocopico said:

 

Did you add the redpill-misc extension ? 

 

Yes I did and the following extensions:

 

./rploader.sh ext broadwellnk-7.1.0-42661 add https://github.com/pocopico/redpill-load/raw/master/redpill-misc/rpext-index.json
./rploader.sh ext broadwellnk-7.1.0-42661 add https://github.com/pocopico/redpill-load/raw/master/redpill-virtio/rpext-index.json 
./rploader.sh ext broadwellnk-7.1.0-42661 add https://github.com/pocopico/redpill-load/raw/master/redpill-acpid/rpext-index.json 
./rploader.sh ext broadwellnk-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/e1000e/rpext-index.json
./rploader.sh ext broadwellnk-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/sky2/rpext-index.json

 

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

17 minutes ago, Dvalin21 said:

I have the t320 on 7.1. if your using SAS card (h310,h200, etc) one make sure the card is flashed to IT Mode, in user_config.json get rid of satamap and diskid and add "SasIdxMap": "0". If you are using the embedded Satas controller (6 Sata) then you need to us satamap and diskid: Satamap 6 and Diskid 00 and keep SasIdxMap. Hope this helps.

Thank you for the tip and explanation.

 

I do not use a raid card, not on the SuperMicro or the Dell server for this test.

I know you need it in IT mode, but the sata ports are fast enough, so I do use the build in sata controller.

If the satamap is on 6, DSM does not see any drives and sata is off.

But if I use 46 in the satamap and diskid 0000 as I mentioned before, all sata ports are active and I can use the drives.

 

 

Link to comment
Share on other sites

Its a little bit strange i have 3615xs 7.1.461  working! :-)

but 3617 and 3622 said always error 13 55% or 60 % the file is damaged but the vid and pid is 100 % correct and the pat file for 3617 and 3622 downloaded again and again.

Do you know why maybe i have to disconnect the internet?

thank you

 

Edited by nemesis122
Link to comment
Share on other sites

6 minutes ago, nemesis122 said:

Its a little bit strange i have 3615xs 7.1.461  working! :-)

but 3617 and 3622 said always error 13 55% or 60 % the file is damaged but the vid and pid is 100 % correct and the pat file for 3617 and 3622 downloaded again and again.

Do you know why maybe i have to disconnect the internet?

thank you

 

 

I've noticed that during the installation the DSM goes and grabs some more files from syno. Maybe that is causing an issue

 

  • Thanks 1
Link to comment
Share on other sites

On 4/9/2022 at 7:15 PM, Peter Suh said:

[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.0.1-42218

./rploader.sh clean now

./rploader.sh build broadwellnk-7.1.0-42661

 

./rploader.sh clean now;  rm -rf /mnt/sdb3/auxfiles;  rm -rf /home/tc/custom-module;  ./rploader.sh backup now;

 

1655034970_3622_2022-04-1012_02_58.thumb.png.b8df5ab6659d29c4d606d716bd4f38d7.png

 

super duper !

worked first try 

 

image.png.1b569d254a554419b3431910dc785b13.png

  • Like 1
Link to comment
Share on other sites

Maybe 3617xs DSM 7 and 3622xs cant running o a gen8 ?

with 3617 with 7.142661

[    2.714707] Call Trace:
[    2.715531]  [<ffffffff812dca8b>] dump_stack+0x4d/0x72
[    2.717237]  [<ffffffff811216d7>] panic+0xc6/0x21e
[    2.718845]  [<ffffffff81099279>] ? vprintk_default+0x9/0x10
[    2.720799]  [<ffffffffa0025000>] ? 0xffffffffa0025000
[    2.722500]  [<ffffffffa000ef7f>] rp_crash+0x10/0x10 [redpill]
[    2.724441]  [<ffffffffa0025146>] init_+0x146/0x176 [redpill]
[    2.726350]  [<ffffffff81000340>] do_one_initcall+0x80/0x130
[    2.728217]  [<ffffffff811620c9>] ? __vunmap+0x99/0xf0
[    2.730009]  [<ffffffff810bf16b>] do_init_module+0x5b/0x1d0
[    2.732223]  [<ffffffff810c0f44>] load_module+0x1be4/0x2080
[    2.734112]  [<ffffffff810bde40>] ? __symbol_put+0x40/0x40
[    2.735961]  [<ffffffff8118a3ac>] ? kernel_read+0x3c/0x50
[    2.737770]  [<ffffffff810c159d>] SYSC_finit_module+0x7d/0xa0
[    2.739767]  [<ffffffff810c15d9>] SyS_finit_module+0x9/0x10
[    2.741612]  [<ffffffff8156380a>] entry_SYSCALL_64_fastpath+0x1e/0x8e
[    2.743783] ---[ end Kernel panic - not syncing: Fatal exception
[    2.745776] ------------[ cut here ]------------
[    2.747298] WARNING: CPU: 0 PID: 427 at arch/x86/kernel/smp.c:125 native_smp_send_reschedule+0x55/0x60()
[    2.750482] Modules linked in: redpill(OE+)
    2.780524] Hardware name: HP ProLiant MicroServer Gen8, BIOS J06 04/04/2019 #42661
[    2.857137]  0000000000000000 ffff880309603db0 ffffffff812dca8b 0000000000000009
[    2.859833]  0000000000000000 ffff880309603de8 ffffffff81050f82 0000000000000001
[    2.862458]  ffff880309656340 0000000000000000 ffff8802fafb3fc0 ffff880309612380
[    2.865088] Call Trace:
[    2.865940]  <IRQ>  [<ffffffff812dca8b>] dump_stack+0x4d/0x72
[    2.867918]  [<ffffffff81050f82>] warn_slowpath_common+0x82/0xa0
[    2.869995]  [<ffffffff81051055>] warn_slowpath_null+0x15/0x20
[    2.871948]  [<ffffffff8102ff35>] native_smp_send_reschedule+0x55/0x60
[    2.874158]  [<ffffffff81085d19>] trigger_load_balance+0x209/0x210
[    2.876207]  [<ffffffff81078f38>] scheduler_tick+0xa8/0xd0
[    2.878034]  [<ffffffff810a9345>] update_process_times+0x45/0x70
[    2.880099]  [<ffffffff810b7090>] tick_sched_handle.isra.21+0x20/0x50
[    2.882236]  [<ffffffff810b72d8>] tick_sched_timer+0x38/0x70
[    2.884118]  [<ffffffff810b72a0>] ? tick_sched_do_timer+0x30/0x30
[    2.886131]  [<ffffffff810a9b23>] __hrtimer_run_queues+0xe3/0x250
[    2.888151]  [<ffffffff810aa1fb>] hrtimer_interrupt+0xab/0x180
[    2.890157]  [<ffffffffa0025000>] ? 0xffffffffa0025000
[    2.891872]  [<ffffffff81031d6d>] local_apic_timer_interrupt+0x3d/0x40
[    2.894036]  [<ffffffff8103263e>] smp_apic_timer_interrupt+0x3e/0x60
[    2.896144]  [<ffffffff8156459b>] apic_timer_interrupt+0x9b/0xa0
[    2.898148]  <EOI>  [<ffffffffa0025000>] ? 0xffffffffa0025000
[    2.900197]  [<ffffffff811217eb>] ? panic+0x1da/0x21e
[    2.901888]  [<ffffffff81099279>] ? vprintk_default+0x9/0x10
[    2.903777]  [<ffffffffa0025000>] ? 0xffffffffa0025000
[    2.905474]  [<ffffffffa000ef7f>] rp_crash+0x10/0x10 [redpill]
[    2.907454]  [<ffffffffa0025146>] init_+0x146/0x176 [redpill]
[    2.909475]  [<ffffffff81000340>] do_one_initcall+0x80/0x130
[    2.911386]  [<ffffffff811620c9>] ? __vunmap+0x99/0xf0
[    2.913061]  [<ffffffff810bf16b>] do_init_module+0x5b/0x1d0
[    2.914862[<ffffffff810c0f44>] load_module+0x1be4/0x2080
[    3.016737]  [<ffffffff810bde40>] ? __symbol_put+0x40/0x40
[    3.018509]  [<ffffffff8118a3ac>] ? kernel_read+0x3c/0x50
[    3.020335]  [<ffffffff810c159d>] SYSC_finit_module+0x7d/0xa0
[    3.022199]  [<ffffffff810c15d9>] SyS_finit_module+0x9/0x10
[    3.024010]  [<ffffffff8156380a>] entry_SYSCALL_64_fastpath+0x1e/0x8e

 

Edited by nemesis122
Link to comment
Share on other sites

3 hours ago, pocopico said:

I'm having the same issue on AMD systems. DSM is missing some prerequisites

 

70-crypto-kernel.conf :crc32c-intel
 

SynologyNAS> insmod /tmpRoot/lib/modules/crc32c-intel.ko
insmod: can't insert '/tmpRoot/lib/modules/crc32c-intel.ko': No such device

 I do the same, like Dreadnought and it's work for me too

I also got error: modprobe: ERROR: could not insert 'aesni_intel': No such device

but after that DSM boot but FileStation doesn't work.

Baremetall Asus P5Q-E + Intel Q9550.

It turns out that the whole thing is in the AES-NI instruction unsupported by the processor. It is strange that for 7.0 this was not a problem.

It's sad, a lot of good boards are left behind, for example GA-C1007UN

Maybe you can do something

 

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

Ok so I finally gave up on migrating and started from scratch.  I created a linux mint disk and am trying to delete the partitions on the hard drives (3 2TB Drives).  Gparted would not let me delete one of the partitions (locked).  I left that partition on each disk.... built a new 7.0.1 loader and upon boot and connection to the new DSM... it still forces me to "recover".  I know that won't work.  Can anyone council me on how to delete a locked partition?

 

 

Link to comment
Share on other sites

On 4/9/2022 at 10:15 AM, Peter Suh said:

[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.0.1-42218

./rploader.sh clean now

./rploader.sh build broadwellnk-7.1.0-42661

 

./rploader.sh clean now;  rm -rf /mnt/sdb3/auxfiles;  rm -rf /home/tc/custom-module;  ./rploader.sh backup now;

 

i will be trying this now, will post the results soon.. :)

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