RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

48 minutes ago, pocopico said:

After converting with qemu you can log into the esxi and run :

 

# vmkfstools -i <oldvmdkname> <newvmdkname>

 

this will clone the disk and fix any incompatibilities

I checked and it works.

But after looking inside, the result is the same as V2V converter.

It build a vmdk index file pointing to "flat" file, and actually, there is no need to do anything with flat file.

 

You can keep original IMG built loader, you just have to set the index file with the right name of img file...

 

So once you have the correct VMDK index file, you just need to overwrite the IMG file on the storage pool ESXi.

 

Quote

# Disk DescriptorFile
version=1
CID=eb5a515c
parentCID=ffffffff
createType="vmfs"

# Extent description
RW 262144 VMFS "redpill-DS3615xs_7.0.img"

# The Disk Data Base
#DDB

ddb.adapterType = "lsilogic"
ddb.deletable = "true"
ddb.encoding = "UTF-8"
ddb.geometry.cylinders = "260"
ddb.geometry.heads = "16"
ddb.geometry.sectors = "63"
ddb.longContentID = "f7bd9734e2bccfe5510ceb0bfffffffe"
ddb.uuid = "60 00 C2 9a 05 67 32 29-a7 36 cd 1c 68 64 22 f1"
ddb.virtualHWVersion = "4"

 

The only main difference between V2V and qemu-img once fixed with vmkfstool is :

image.thumb.png.96547f88bed545c13788cb42f87b0aa0.png

(left is qemu-img, right is V2V where I replaced flat file with original loader's IMG)

 

So now I don't need to convert the IMG each time a build it. I only overwrite the old one and keep VMDK index as this.

Edited by Orphée
  • Like 2
Link to post
Share on other sites
2 minutes ago, jforts said:

Hi, I try the redpill-loader with baremetal, I cannot access to any serial port, how to access the console from a monitor and keyboard?

Because the screen froze at Booting the kernel...

You don't need serial console, but at now you must use intel network card and  Synology assistant to found new uninstalled system.
If you have access on a machine that act as DHCP, you can  view ip address assigned and use them via browser 

 

Link to post
Share on other sites
2 minutes ago, Aigor said:

You don't need serial console, but at now you must use intel network card and  Synology assistant to found new uninstalled system.
If you have access on a machine that act as DHCP, you can  view ip address assigned and use them via browser 

 

Thanks for the information. I am able to get the IP address but I couldn't install DSM because it cannot detect my SATA drive. I want to check the log to see whether it is detect during boot. How do I check that?

Link to post
Share on other sites
2 minutes ago, jforts said:

Thanks for the information. I am able to get the IP address but I couldn't install DSM because it cannot detect my SATA drive. I want to check the log to see whether it is detect during boot. How do I check that?

try to telnet to ip address 

Link to post
Share on other sites

@ThorGroup I have some errors after install DSM7.0 on my hardware.

 

[    2.574597] redpill: module verification failed: signature and/or required key missing - tainting kernel
[    3.243540] <redpill/override_symbol.c:404> Failed to locate vaddr for sys_call_table using kallsyms - falling back to memory search
[    7.654945] intel-lpss: probe of 0001:00:16.0 failed with error -22
[    7.661824] intel-lpss: probe of 0001:00:18.0 failed with error -22
[    7.668735] intel-lpss: probe of 0001:00:19.0 failed with error -22
[    7.675644] intel-lpss: probe of 0001:00:19.2 failed with error -22
[   16.797306] ahci: probe of 0001:01:00.0 failed with error -22
[   16.803420] ahci: probe of 0001:00:12.0 failed with error -22
[   17.338180] xhci_hcd 0001:00:15.0: init 0001:00:15.0 fail, -16
[   17.344410] xhci_hcd: probe of 0001:00:15.0 failed with error -16
[   17.755953] <redpill/bios_shim.c:207> Symbol #29 in mfgBIOS "apollolake_synobios" {synobios_record_scsi_error_event}<ffffffffa00ba480>
  [   17.794780] <redpill/bios_shim.c:207> Symbol #32 in mfgBIOS "apollolake_synobios" {synobios_disk_reset_fail_report}<ffffffffa00ba580>
  [   17.832428] <redpill/bios_shim.c:207> Symbol #35 in mfgBIOS "apollolake_synobios" {synobios_sata_error_report}<ffffffffa00ba690>
  [   17.891199] <redpill/bios_shim.c:207> Symbol #39 in mfgBIOS "apollolake_synobios" {synobios_error_fs_btrfs_event}<ffffffffa00ba7e0>
  [   17.903689] <redpill/bios_shim.c:207> Symbol #40 in mfgBIOS "apollolake_synobios" {synobios_error_fs_event}<ffffffffa00ba830>
  [   17.952685] <redpill/bios_shim.c:207> Symbol #44 in mfgBIOS "apollolake_synobios" {synobios_error_oom_event}<ffffffffa00baa50>
  [   18.418432] <redpill/bios_shim.c:207> Symbol #83 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa00c4800>
  [   18.535314] <redpill/bios_shim.c:207> Symbol #93 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa00c4c40>
  [   18.647725] <redpill/bios_shim.c:207> Symbol #103 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa00c5080>
  [   18.761576] <redpill/bios_shim.c:207> Symbol #113 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa00c54c0>
  [   18.881884] <redpill/bios_shim.c:207> Symbol #123 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa00c5900>
  [   18.995030] <redpill/bios_shim.c:207> Symbol #133 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa00c5d40>
  [   19.112728] <redpill/bios_shim.c:207> Symbol #143 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa00c6180>
  [   19.226639] <redpill/bios_shim.c:207> Symbol #153 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa00c65c0>
  [   19.339744] <redpill/bios_shim.c:207> Symbol #163 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa00c6a20>
  [   20.754211] usb 1-12: device descriptor read/64, error -71
  [   20.979213] usb 1-12: device descriptor read/64, error -71
  [   21.336220] usb 1-12: device descriptor read/64, error -71
  [   21.570232] usb 1-12: device descriptor read/64, error -71
  [   22.743253] usb 1-12: device not accepting address 6, error -71
  [   23.293258] usb 1-12: device not accepting address 7, error -71
  [   32.515336] systemd[1]: Cannot add dependency job for unit SynoLedBrightness.service, ignoring: Unit SynoLedBrightness.service is masked.
[   32.528516] systemd[1]: Cannot add dependency job for unit pkg-install-high-priority-builtin.service, ignoring: Unit pkg-install-high-priority-builtin.service failed to load: No such file or directory.
[   32.547485] systemd[1]: Cannot add dependency job for unit pkg-install-low-priority-builtin.service, ignoring: Unit pkg-install-low-priority-builtin.service failed to load: No such file or directory.
  [   34.688838] igb: probe of 0001:02:00.0 failed with error -5
[   34.694790] igb: probe of 0001:03:00.0 failed with error -5
  [   35.247539] i915 0000:00:02.0: Direct firmware load for i915/kbl_dmc_ver1_04.bin failed with error -2
  [   35.257396] i915 0000:00:02.0: Falling back to user helper
  [   36.132828] <redpill/bios_shim.c:207> Symbol #29 in mfgBIOS "apollolake_synobios" {synobios_record_scsi_error_event}<ffffffffa064b480>
  [   36.171822] <redpill/bios_shim.c:207> Symbol #32 in mfgBIOS "apollolake_synobios" {synobios_disk_reset_fail_report}<ffffffffa064b580>
  [   36.209524] <redpill/bios_shim.c:207> Symbol #35 in mfgBIOS "apollolake_synobios" {synobios_sata_error_report}<ffffffffa064b690>
  [   36.261526] <redpill/bios_shim.c:207> Symbol #39 in mfgBIOS "apollolake_synobios" {synobios_error_fs_btrfs_event}<ffffffffa064b7e0>
  [   36.274110] <redpill/bios_shim.c:207> Symbol #40 in mfgBIOS "apollolake_synobios" {synobios_error_fs_event}<ffffffffa064b830>
  [   36.323244] <redpill/bios_shim.c:207> Symbol #44 in mfgBIOS "apollolake_synobios" {synobios_error_oom_event}<ffffffffa064ba50>
  [   36.778878] <redpill/bios_shim.c:207> Symbol #83 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa0655800>
  [   36.891358] <redpill/bios_shim.c:207> Symbol #93 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa0655c40>
  [   37.004279] <redpill/bios_shim.c:207> Symbol #103 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa0656080>
  [   37.118604] <redpill/bios_shim.c:207> Symbol #113 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa06564c0>
  [   37.232185] <redpill/bios_shim.c:207> Symbol #123 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa0656900>
  [   37.345777] <redpill/bios_shim.c:207> Symbol #133 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa0656d40>
  [   37.459209] <redpill/bios_shim.c:207> Symbol #143 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa0657180>
  [   37.573346] <redpill/bios_shim.c:207> Symbol #153 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa06575c0>
  [   37.687032] <redpill/bios_shim.c:207> Symbol #163 in mfgBIOS "apollolake_synobios" {fan_fail}<ffffffffa0657a20>
  [   42.673054] i915 0000:00:02.0: Failed to load DMC firmware i915/kbl_dmc_ver1_04.bin. Disabling runtime power management.

1968850318_2021-08-3021_00_26.thumb.png.cb4bce30668463eeb8f1d35ccabda172.png

Link to post
Share on other sites
On 8/29/2021 at 8:45 PM, Amoureux said:

Thanks @ThorGroup for RedPill, and @haydibe for simple way to create image for bootloader with Docker.

 

A little instruction how to use last version toolchain in macOS Big Sur 11.5.2 :

 

1. Install Xcode, Xcode command line tools, and Docker on Mac. Run Docker. Download last version toolchain, moved to Desktop and unzip.

 

2.  Install HomeBrew in Terminal


/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"

 

3. Instal jq and coreutils in Terminal


brew install jq
brew install coreutils

 

4. 


cd ~/Desktop/redpill-tool-chain_x86_64_v0.6
sudo chmod 777 redpill_tool_chain.sh

 

5. In Finder rewrite  config in bromolow_user_config.json or apollolake_user_config.json for your setup.

 

6. After choosing config use the commands for:

  • build toolchain image

./redpill_tool_chain.sh build bromolow-6.2.4-25556
./redpill_tool_chain.sh build bromolow-7.0-41222
./redpill_tool_chain.sh build apollolake-6.2.4-25556
./redpill_tool_chain.sh build apollolake-7.0-41890
  • create redpill bootloader image

./redpill_tool_chain.sh auto bromolow-6.2.4-25556
./redpill_tool_chain.sh auto bromolow-7.0-41222
./redpill_tool_chain.sh auto apollolake-6.2.4-25556
./redpill_tool_chain.sh auto apollolake-7.0-41890

 

771819093_2021-08-2920_45_19.thumb.png.44833890df6a7759a4ac333db6e173d5.png

 

For Proxmox what is the recommended platform ? Also SATA vs USB boot ?

Link to post
Share on other sites

Hi guys,

 

I am using the 918+ ApolloLake configuration. PID, VID and Mac address where set correctly. I get this error when I try to install DSM:

 

We've detected errors on the hard drives (1, 3), and the SATA ports have also been disabled. Please shut down your DS918+ to replace or remove the hard drives and try again. 

 

I have a HP EliteBook 840 G2 with Intel Core i5 5300U, 16 GB RAM, Samsung SSD 500 GB.

 

For booting off I am using a Kingston DataTravler 32 GB stick.

Link to post
Share on other sites

You are trying to install RP Xpenology on a laptop... Good luck ! It may work but usually laptops are quite tricky with their componants...

 

if you can access it from network, you should be able to telnet to it on port 21, 22 and 23 I guess.

 

Link to post
Share on other sites
56 minutes ago, Orphée said:

You are trying to install RP Xpenology on a laptop... Good luck ! It may work but usually laptops are quite tricky with their componants...

 

if you can access it from network, you should be able to telnet to it on port 21, 22 and 23 I guess.

 

 

@ThorGroup

 

It worked with Juno's loader on 6.2.1 so shall be fine. I disabled from BIOS: camera, smart card, M2 slot, etc... leaving just a PC basic stuff including one SATA drive.

 

// No luck with telnet port. I tried 21,22,23

// Web interface works with the error message I described above

// Tried both apollolake and bromolow on 7.0. Same error.

// Tried with smaller USB and 6.2.4. Same issue

 

Any ideea why I get this ?

 

We've detected errors on the hard drives (1, 3), and the SATA ports have also been disabled. Please shut down your DS918+ to replace or remove the hard drives and try again. 

 

So I have one SATA controller under Linux: 00:1f.2 -> Intel Corporation Wildcat Point-LP SATA Controller AHCI Mode rev 03

Edited by maxhartung
Link to post
Share on other sites

Actually Serial to Telnet is a ESXi / Proxmox feature. I'm not sure telnet can access to real baremetal serial port.

I mean on VM, you add a serial port, and you link it to telnet with a VM parameter.

BTW, do you actually have a serial port on your laptop ?

Link to post
Share on other sites
1 hour ago, Orphée said:

Actually Serial to Telnet is a ESXi / Proxmox feature. I'm not sure telnet can access to real baremetal serial port.

I mean on VM, you add a serial port, and you link it to telnet with a VM parameter.

BTW, do you actually have a serial port on your laptop ?

 

I don't think so. I will try to install Proxmox again on my laptop and see if I can get this running. For Proxmox I think I need the SATA mappings. 

 

Proxmox:

I get file is corrupted...

 

I used these config

 

{

"extra_cmdline": {

"pid": "0x1666",

"vid": "0x0951",

"sn": "REMOVED",

"mac1": "0687940FE75F"

},

"synoinfo": {

"DiskIdxMap": "OC",

"SataPortMap": "1",

"SasIdxMap": "0"

},

"ramdisk_copy": {}

}

 

Logs: https://hastebin.com/ofehukocev.sql

Edited by maxhartung
Link to post
Share on other sites
1 hour ago, maxhartung said:

 

I don't think so. I will try to install Proxmox again on my laptop and see if I can get this running. For Proxmox I think I need the SATA mappings. 

 

Proxmox:

I get file is corrupted...

 

I used these config

 

{

"extra_cmdline": {

"pid": "0x1666",

"vid": "0x0951",

"sn": "REMOVED",

"mac1": "0687940FE75F"

},

"synoinfo": {

"DiskIdxMap": "OC",

"SataPortMap": "1",

"SasIdxMap": "0"

},

"ramdisk_copy": {}

}

 

Logs: https://hastebin.com/ofehukocev.sql

Try to change to :

 

"DiskIdxMap": "1000",

"SataPortMap": "4",

Link to post
Share on other sites
3 hours ago, maxhartung said:

We've detected errors on the hard drives (1, 3), and the SATA ports have also been disabled. Please shut down your DS918+ to replace or remove the hard drives and try again. 

 

You have wrong sataportmap values in GRUB below, try removing them.

 

"synoinfo": {

"DiskIdxMap": "OC",

"SataPortMap": "1",

"SasIdxMap": "0"

}

 

Telnet service will start by default after installation failure (e.g. error13),for Synology troubleshooting.

 

But in your case you even fail to start installation. 

 

 

Edited by pocopico
Link to post
Share on other sites
37 minutes ago, WowaDriver said:

Many thanks to the development to all involved!

 

Has anyone managed to create a useful VM with DSM 7 under Unraid?

In my case I would have to pass an LSI 9211-8i HBA and an intel NIC for native ethernet?

 

Would anyone share their configuration? 

I did. If you go pages back you will find one of my posts that I shared my XML. I think ThorGroup replied back that for ethernet I slould use virtio.

 

Edit: Of course if you want to try to pass through your intel nic go ahead...

Edited by gadreel
Link to post
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.