Jump to content
XPEnology Community

Automated RedPill Loader (ARPL)


fbelavenuto

Recommended Posts

I successfully used arpl v0.4 alpha 7 on one of my VMs running ESXi 7.0, but had problems with another.

ESXi 7.0 U3 running on HP Microserver Gen8. Was using Tinycore 0.8 and DSM 7.1.0, but want to upgrade to DSM 7.1.1.

ARPL v0.4 alpha 7 didn't give me vmxnet3 and paravirtual scsi, but once I realized alpha 6 worked, I was able to install 7.1.1 pat file.

Problem is, I am passing my 4 physical SATA disks in the Microserver (built-in B120i controller) to this VM as RDM, and once booted into DSM, it only saw 2 of the 4 disks and maybe it was not even seeing as same disks (different serial number). Can't roll back to my Tinycore 0.8 vmdk by now (recovery loop), so I took the plunge and moved to Tinycore 0.9, and all 4 disks were found.

arpl is more user-friendly with the menu system, but too bad didn't work for my RDM setup.

Link to comment
Share on other sites

13 hours ago, apriliars3 said:

@fbelavenuto One question, I update to arpl v0.4 alpha 8 from update menu while compile github and crash the boot. I have download older v0.4 alpha 7 to recovery. Is it possible to update from update menu when not is possible to download from github the new version?

 

ARPL v0.4 alpha 8 works well. I am testing now with Proxmox.

Captura de pantalla 2022-09-16 001413.jpg

Sorry, I was supposed to have fixed this problem in the previous release! Back to the drawing board!

  • Like 2
Link to comment
Share on other sites

6 hours ago, mxmx said:

I successfully used arpl v0.4 alpha 7 on one of my VMs running ESXi 7.0, but had problems with another.

ESXi 7.0 U3 running on HP Microserver Gen8. Was using Tinycore 0.8 and DSM 7.1.0, but want to upgrade to DSM 7.1.1.

ARPL v0.4 alpha 7 didn't give me vmxnet3 and paravirtual scsi, but once I realized alpha 6 worked, I was able to install 7.1.1 pat file.

Problem is, I am passing my 4 physical SATA disks in the Microserver (built-in B120i controller) to this VM as RDM, and once booted into DSM, it only saw 2 of the 4 disks and maybe it was not even seeing as same disks (different serial number). Can't roll back to my Tinycore 0.8 vmdk by now (recovery loop), so I took the plunge and moved to Tinycore 0.9, and all 4 disks were found.

arpl is more user-friendly with the menu system, but too bad didn't work for my RDM setup.

Please try the alpha8 release.

Link to comment
Share on other sites

There is a new script not yet documented for the command line in this last release (v0.4-alpha8). In junior mode and normal mode the user can type "arpl-reboot.sh" with the options "junior" or "config".

With the "junior" option the system restarts and automatically selects the grub option "Force re-install". The "config" option selects the "Configure".

 

arpl-reboot.sh junior

arpl-reboot.sh config

 

  • Like 2
Link to comment
Share on other sites

I am interested in exploring VMM High Availability between two xpenology boxes, but this requires VMM Pro license. A free trial license still requires a synology account, which I have for an old real syno box. However, I think access to sign in to syno account is blocked in redpill - can this corrected (e.g. via syninfo entry) or is it "too dangeroous" to connect? (In the past, with Jun's loader, it was possible to connect to syno account, although not recommended)

Link to comment
Share on other sites

23 hours ago, dferara said:

 

Hi fbelavenuto!!

 

Here is the list of a few that I have, I have more on VM, but because are repeated configuration I didn't include here on the pictures.

 

You can see that the E1000 and E1000E that i HAVE with DSM 6.2.X JUN loader with the DSM 6 works fine, I forgot to include the picture of the DSM 6 with E1000E. 

The peculiar thing is the VM with DSM 6.2X with E1000E migrated to DSM 7 keep the settings of MTU9000 but if I would try to change, on the options only show 1500.

I have a lot of RAM on my ESXi and a lot of CPU power so I can try to test any special driver you can give me.

I don't know how to include the ADDON, when i click on download from a external addon and put the link you copy on the post it gives me this error.

 

image.png.ac21751a887cddb12cd7b51301f4e691.png

 

List of my VMs and Baremetal:

 

image.thumb.png.d0ae03e1b99fbe30c8a5a417c4cd365e.png

 

Ok Fabio, I did a lot of research yesterday, I installed like 4 Vms on ESXi 6.0 and 4 VMs on Vmware Workstation Pro 16. Here is the info about. I tried the models ds3615, ds3617, ds3622, dva1622, dva3221.

 

All the models with the 10GB virtual network VMXNET3 work with perfection and have the MTU9000 option open on all the DSM 7.x.

The ds3622xs and the dva1622 with intel E1000 and E1000E on DSM 7.X doesn't give me the option to change from MTU1500 to more.

 

I don't know if the driver's version on the loader scripts is different for each model, or they are the same and use the same source for every model.

 

If you can compile a new version of e1000 and e1000e for the DS3622 and the DVA1622, then I can test them on ESXi, VMware Workstation Pro and BareMetal. They all have the old intel network card. 

 

PS: I couldn't add the GitHub URL with e1000e on the loader, I tried to copy the whole URL and the error was: file format no recognized

 

image.thumb.png.fa55ee301bb7fb15a9688250688a8c8a.png

Edited by dferara
Link to comment
Share on other sites

On 9/17/2022 at 3:20 AM, fbelavenuto said:

There is an issue detected by a user that affects all loaders. I didn't know but it's old.

The synobios module corrupts the CMOS of some machines and when resetting the BIOS it drops to the "CMOS Checksum bad" screen.

More information:

https://github.com/fbelavenuto/arpl/issues/174

 

I encountered this problem on my Gigabyte motherboard, but only on the DS920+ model. And the result is the same whether it is ARPL, TCRP or TCRP-JUN.

Link to comment
Share on other sites

В 15.09.2022 в 22:48, Drones сказал:

Good evening!
I tried booting without CC2531. Nothing changed.
I also tried migrating to 918+. The migration was successful, but the situation has not changed.
I don't know what else to try (

Still trying to overcome this strange problem.
I noticed that the export of virtual machines works at a very low speed. About 2-6 MB / sec. At the same time, when copying files from / to SSD through File Station, the speed is more than 250MB / s
From the last checks, VMM was reinstalled. I'll also try to clear the storage when I make backups.

SlowExport.jpg

 

UPD1: 
I did a complete reinstall of VMM, including cleaning out the VMM store. Trying a clean install with Win10 produces the same results (terrible lags).

 

UPD2:

When installing Windows 10 (copying new files), the write speed to the disk is no more than 1.5 MB / s.

 

SlowInstall.jpg

Edited by Drones
  • Thanks 1
Link to comment
Share on other sites

On 9/16/2022 at 9:34 PM, dferara said:

 

Ok Fabio, I did a lot of research yesterday, I installed like 4 Vms on ESXi 6.0 and 4 VMs on Vmware Workstation Pro 16. Here is the info about. I tried the models ds3615, ds3617, ds3622, dva1622, dva3221.

 

All the models with the 10GB virtual network VMXNET3 work with perfection and have the MTU9000 option open on all the DSM 7.x.

The ds3622xs and the dva1622 with intel E1000 and E1000E on DSM 7.X doesn't give me the option to change from MTU1500 to more.

 

I don't know if the driver's version on the loader scripts is different for each model, or they are the same and use the same source for every model.

 

If you can compile a new version of e1000 and e1000e for the DS3622 and the DVA1622, then I can test them on ESXi, VMware Workstation Pro and BareMetal. They all have the old intel network card. 

 

PS: I couldn't add the GitHub URL with e1000e on the loader, I tried to copy the whole URL and the error was: file format no recognized

 

image.thumb.png.fa55ee301bb7fb15a9688250688a8c8a.png

Please update the modules in the "Update" menu, rebuild the loader and boot. I've added the most recent version of e1000e for all models.

 

  • Like 1
Link to comment
Share on other sites

В 16.09.2022 в 00:50, renegadeBE сказал:

Maybe try another loader?  Have you tried with TCRP v0.9 (develop)?

Yes, it helped, thanks! Now VMM works as it should.
Dear fbelavenuto, you have made a very convenient way to create a bootloader, I really hope that you will be able to find and fix the problem. If you need tests, I'm happy to help!

  • Like 1
Link to comment
Share on other sites

12 hours ago, Drones said:

Yes, it helped, thanks! Now VMM works as it should.
Dear fbelavenuto, you have made a very convenient way to create a bootloader, I really hope that you will be able to find and fix the problem. If you need tests, I'm happy to help!

Good news! It's a problem with the drivers. Can you run the command 'lspci -nnk' in the TCRP shell?

Link to comment
Share on other sites

On 9/16/2022 at 12:14 PM, fbelavenuto said:

Please try the last release, alpha8

Dear fbelavenuto,

 

Thanks, i have tested alpha 9 as it came out in the meantime.

I already have built system with TCRP and used 42962

So Alpha9 did build the loader -- booted and it just loaded fine i could log in to my built system. Restarted few times now and works as it should.

I will try to build again from scratch to test if i have a bit of time.

 

Thank you

Link to comment
Share on other sites

On 9/20/2022 at 7:35 AM, fbelavenuto said:

Guys, please update the modules and recreate the loader. I put new drivers (r8125, r8168, r8169, tg3)

 

Do I need to manually add any other drivers?

 

00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [8086:590f] (rev 06)
        Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers [1462:7a71]
        Kernel driver in use: skl_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 630 [8086:5912] (rev 04)
        DeviceName:  Onboard IGD
        Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 630 [1462:7a71]

00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [8086:1911]
        Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model [1462:7a71]

00:14.0 USB controller [0c03]: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller [8086:a2af]
        Subsystem: Micro-Star International Co., Ltd. [MSI] 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller [1462:7a71]
        Kernel driver in use: xhci_hcd

00:14.2 Signal processing controller [1180]: Intel Corporation 200 Series PCH Thermal Subsystem [8086:a2b1]
        Subsystem: Micro-Star International Co., Ltd. [MSI] 200 Series PCH Thermal Subsystem [1462:7a71]

00:16.0 Communication controller [0780]: Intel Corporation 200 Series PCH CSME HECI #1 [8086:a2ba]
        Subsystem: Micro-Star International Co., Ltd. [MSI] 200 Series PCH CSME HECI [1462:7a71]

00:17.0 SATA controller [0106]: Intel Corporation 200 Series PCH SATA controller [AHCI mode] [8086:a282]
        Subsystem: Micro-Star International Co., Ltd. [MSI] 200 Series PCH SATA controller [AHCI mode] [1462:7a71]
        Kernel driver in use: ahci

00:1c.0 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #1 [8086:a290] (rev f0)
        Kernel driver in use: pcieport

00:1c.3 PCI bridge [0604]: Intel Corporation 200 Series PCH PCI Express Root Port #4 [8086:a293] (rev f0)
        Kernel driver in use: pcieport

00:1f.0 ISA bridge [0601]: Intel Corporation 200 Series PCH LPC Controller (Z270) [8086:a2c5]
        Subsystem: Micro-Star International Co., Ltd. [MSI] 200 Series PCH LPC Controller (Z270) [1462:7a71]

00:1f.2 Memory controller [0580]: Intel Corporation 200 Series/Z370 Chipset Family Power Management Controller [8086:a2a1]
        Subsystem: Micro-Star International Co., Ltd. [MSI] 200 Series/Z370 Chipset Family Power Management Controller [1462:7a71]

00:1f.3 Audio device [0403]: Intel Corporation 200 Series PCH HD Audio [8086:a2f0]
        Subsystem: Micro-Star International Co., Ltd. [MSI] 200 Series PCH HD Audio [1462:fa71]

00:1f.4 SMBus [0c05]: Intel Corporation 200 Series/Z370 Chipset Family SMBus Controller [8086:a2a3]
        Subsystem: Micro-Star International Co., Ltd. [MSI] 200 Series/Z370 Chipset Family SMBus Controller [1462:7a71]
        Kernel driver in use: i801_smbus

02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
        Subsystem: Micro-Star International Co., Ltd. [MSI] RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1462:7a71]
        Kernel driver in use: r8169
        Kernel modules: r8169

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