RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

Thanks but it seems I am blind, I can`t find the new toolchain docker image :)

 

Quote

The Current State
As of now the DSM installs & boots properly (sort of, continue reading). We are currently working on a toolset for generating the loader image automatically so that testing new iterations is easier for people not familiar with full inner workings of the kernel component & the bootloader itself. The tool with instructions will be published in a separate repo.

 

Edited by ct85msi
Link to post
Share on other sites
7 hours ago, ThorGroup said:

It will be a problem with booting from SAS but isn't DSM seeing them as data disks? Which LSI card are you running? Can you put an issue on GH in the kernel module repo for this, so we don't forget?


it's a common LSI 9211-8i (actually a Dell Perc H200 crossflashed to LSI and in IT mode), enabling the supportsas flag loads mpt2sas at boot correctly and drivers attached show up but not in the guy, so DSM wont use them as data disk (shows no disks attached).

i'm not the only one facing this problem, as i wrote with jun's loader the drivers show up as /dev/sdX but with redpill they show up as /dev/sasN, DSM should work with them natively without anyway?

Link to post
Share on other sites
4 minutes ago, pigr8 said:


it's a common LSI 9211-8i (actually a Dell Perc H200 crossflashed to LSI and in IT mode), enabling the supportsas flag loads mpt2sas at boot correctly and drivers attached show up but not in the guy, so DSM wont use them as data disk (shows no disks attached).

i'm not the only one facing this problem, as i wrote with jun's loader the drivers show up as /dev/sdX but with redpill they show up as /dev/sasN, DSM should work with them natively without anyway?

+1 for this issue, 3615xs should have native sas2 support at the very least, while the driver shows up with lsmod, disks are not available in the UI.  Can also confirm that it did work out of the box with Jun's loader previously with 3615xs and 3617xs.

Link to post
Share on other sites
53 minutes ago, shibby said:

they working on it and it will be published in a separate repo, but at the moment it`s not available.

 

but IMO @haydibe`s toolchain still should works well. Just first do "./redpill_tool_chain.sh clean" to be sure that docker will build image using latest sources from git.

 

Nope,I just tried and now I’m reinstalling my DSM😂.The new img is the same size as the old one.

屏幕截图 2021-09-13 161752.png

屏幕截图 2021-09-13 161834.png

Link to post
Share on other sites
6 hours ago, ThorGroup said:

1 - If you dd the raw image (dd if=file.img of=/dev/rdiskX => make sure you sure rdisk and not disk) you don't need to manually modify the partition. Before you do that you should check the disk with diskutil list to get the number and unmount all existing partitions using diskutil unmount (not eject from the Finder).

 

 

2 - That smells like an ancient docker version in the DSM itself... we saw this before and they fixed the issue after like 6-7 months. It may be the case again.

1 - I'm writing with dd to /dev/rdiskX and absolutely do have to mark it as active afterwards. I've created loads of images now and every time there is no partition marked as active. This isn't a problem for most hardware, but the Gen8 (which as you've pointed out elsewhere is quite picky) *needs* to have the first partition marked as active to boot from it

 

2 - DSM 7.0.1-RC1 is running docker 20.10.3. This appears to be from February 2021, and only five patch levels behind current (20.10.8). To be clear: this problem only ever manifested with docker containers running influxdb, but across numerous versions of influxdb tried. Lots of Googling suggests no one else is experiencing problems like this, but I'm curious to know if anyone else here sees it.

Link to post
Share on other sites
On 9/11/2021 at 8:27 PM, Kamele0N said:

Regarding your SN..... 

 

SNs for ds918 are different then those intended for Ds3615xs 

 

3615xs = xxxxLWNxxx

Ds918 = xxxxPDNxxx

 

So you need to get a proper SN for your loader/model! You can not just add any SN you can get! 

 

The SN and MAC added is from a real DS3615xs device, that's why I don't understand anything. SN is the correct one if I check it thru DSM Info panel but it does not work in terms of device activation/recognition it as an original. 

  

On 9/11/2021 at 10:53 PM, loomes said:

Same here. Also real SN/MAC Bug in 7.0.1 RC Version?! 

BUT, Face Detection in Photos is working here with the 3615 version, 918 dont work.

 

You're lucky! Anyway, I can't test 918 version in my server, as I have a G8 device, which is incompatible.

Link to post
Share on other sites
29 minutes ago, Zardozlv said:

The new img is the same size as the old one.

 

this is not a proof. When docker image is made then sources of redpill are downloaded from git:

 

[stage-1 3/9] RUN git clone https://github.com/RedPill-TTG/redpill-lkm.git  -b master  /opt/redpill-lkm &&     git clone https://github.com/chchia/redpill-load.git -b master /opt/redpill-load 

 

this is the reason why command "redpill_tool_chain.sh clean all" is so important

Edited by shibby
  • Like 1
Link to post
Share on other sites
9 minutes ago, shibby said:

 

this is not a proof. When docker image is made then sources of redpill are downloaded from git:

 


[stage-1 3/9] RUN git clone https://github.com/RedPill-TTG/redpill-lkm.git  -b master  /opt/redpill-lkm &&     git clone https://github.com/chchia/redpill-load.git -b master /opt/redpill-load 

 

this is the reason why command "redpill_tool_chain.sh clean all" is so important

Thanks, I'll try to rebuild it with redownloaded toolchain and I‘ll delete docker image in my Ubuntu, wish me good luck!😂

Link to post
Share on other sites

I have been using @haydibe redpill-tool-chain_x86_64_v0.7.2.zip to build images successfully . however today when I try and run ./redpill_tool_chain.sh auto bromolow-7.0.1-42214 , it errors at the following , am I doing something wrong ? 

 

create mode 100644 shim/storage/virtio_storage_shim.h
Pulled latest commits.
Check if redpill-load sources require pull.

*** Please tell me who you are.

Run

  git config --global user.email "you@example.com"
  git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: unable to auto-detect email address (got 'root@redpill-tool-chain.(none)')

 

Link to post
Share on other sites
1 minute ago, scoobdriver said:

it errors at the following , am I doing something wrong ? 

first run "redpill_tool_chain.sh clean all"

then "docker image ls" and check is there any of redpill image. If does then remove them all.

 

after that build new image. I made new image apollolake-7.0.1-42214 few minutes ago without issue.

Link to post
Share on other sites
32 minutes ago, scoobdriver said:

I have been using @haydibe redpill-tool-chain_x86_64_v0.7.2.zip to build images successfully . however today when I try and run ./redpill_tool_chain.sh auto bromolow-7.0.1-42214 , it errors at the following , am I doing something wrong ? 

 




create mode 100644 shim/storage/virtio_storage_shim.h
Pulled latest commits.
Check if redpill-load sources require pull.

*** Please tell me who you are.

Run

  git config --global user.email "you@example.com"
  git config --global user.name "Your Name"

to set your account's default identity.
Omit --global to set the identity only in this repository.

fatal: unable to auto-detect email address (got 'root@redpill-tool-chain.(none)')

 

7.0.1 is not from official Redpill repo, I guess @jumkey removed "develop" branch. So it does not work anymore.

You should currently go back to "official" 7.0-41222 from redpill repo.

 

Edit : develop branch is there, I was blind or it was added back in the meantime.

 

@ThorGroup I updated the ticket with ESXi SMART issue... I can't install anymore. Tried with 7.0, il will try with 6.2.4

 

Edit 2 : It works with 6.2.4 loader

Edited by Orphée
Link to post
Share on other sites
5 hours ago, ThorGroup said:

To our knowledge the absolute max is 26 as DSM doesn't support /dev/sdaa /dev/sdab /dev/sdac etc. naming. Since there's only 26 letters you can only use 26 disks. Their eboxes work differently and that's how on a real DS you can get >26 drives.

Maybe is not related but this is how DSM is showing drives on the second controller on my bare metal ASRock N3700 and is working fine. 

image.png.337075c7b1ca893ca29f7ed48798875a.png

 

image.png.2062e3d4c28b80e0f9d9b6b7f508f2a5.png

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

7.0.1 is not from official Redpill repo, I guess @jumkey removed "develop" branch. So it does not work anymore.

You should currently go back to "official" 7.0-41222 from redpill repo.

 

Edit : develop branch is there, I was blind or it was added back in the meantime.

 

@ThorGroup I updated the ticket with ESXi SMART issue... I can't install anymore. Tried with 7.0, il will try with 6.2.4

😂sorry  rebase and git push -f

 

can fix pull with 

git fetch --all && git reset --hard origin/develop && git pull

 

Edited by jumkey
  • Haha 1
Link to post
Share on other sites

Just asking, this has nothing to do with xpenology/bootloader, right?

 

root@Apollo:~# tail -f /var/log/messages
2021-09-13T11:46:56+03:00 Apollo synosnmpcd[9578]: scemd_connector/scemd_connector.c:118 Fail to lockf() for scemd connector client.
2021-09-13T11:46:56+03:00 Apollo synosnmpcd[9578]: scemd_connector/scemd_connector.c:204 Fail to SYNOScemdConnectorClient() for scemd conncetor client
2021-09-13T11:46:56+03:00 Apollo synosnmpcd[9578]: scemd_connector/scemd_connector.c:118 Fail to lockf() for scemd connector client.
2021-09-13T11:46:56+03:00 Apollo synosnmpcd[9578]: scemd_connector/scemd_connector.c:204 Fail to SYNOScemdConnectorClient() for scemd conncetor client
2021-09-13T11:46:56+03:00 Apollo synosnmpcd[9578]: scemd_connector/scemd_connector.c:118 Fail to lockf() for scemd connector client.
2021-09-13T11:46:56+03:00 Apollo synosnmpcd[9578]: scemd_connector/scemd_connector.c:204 Fail to SYNOScemdConnectorClient() for scemd conncetor client
2021-09-13T12:02:01+03:00 Apollo synosnmpcd[9578]: scemd_connector/scemd_connector.c:118 Fail to lockf() for scemd connector client.
2021-09-13T12:02:01+03:00 Apollo synosnmpcd[9578]: scemd_connector/scemd_connector.c:204 Fail to SYNOScemdConnectorClient() for scemd conncetor client
2021-09-13T12:03:09+03:00 Apollo synosnmpcd[9578]: scemd_connector/scemd_connector.c:150 Fail to recvfrom() for scemd connector client.
2021-09-13T12:03:09+03:00 Apollo synosnmpcd[9578]: scemd_connector/scemd_connector.c:204 Fail to SYNOScemdConnectorClient() for scemd conncetor client
 

Link to post
Share on other sites
7 hours ago, ThorGroup said:
On 9/7/2021 at 4:06 PM, WiteWulf said:

Oh, that's cool, didn't realise that! That opens up the possibility of getting a better/additional HBA to go in there at some point...

Yes, the built-in card was broken only for a short while. 6.2.3 restored the driver. We didn't test if v7 removed it again (hopefully not).

I just re-enabled the internal NIC on my Gen8 and rebooted into 7.0.1-RC1 and confirm the internal NIC is not seen, either in DSM or running 'ifconfig' from the command line. I guess that confirms the drivers are not included; others' experience suggested this earlier in the thread.

Link to post
Share on other sites
8 hours ago, ThorGroup said:
On 9/7/2021 at 10:46 AM, WiteWulf said:

Question: I have an HP NC360T PCIe NIC card in my system. I'm only using one interface, so have only declared one of them in my user_config.json. Is this a problem?

 

I notice in Control Panel in DSM that two interfaces are detected, and both have the same MAC address (the one I declared for the interface that I'm actually using). Likewise, running 'ifconfig' from the cli reports two interfaces with the same MAC address. I know that an OSI 7-layer network stack shouldn't have an issue with multiple interfaces on a system having the same MAC address (it's standard on Sun machines, for example), but will DSM complain about this?

 

You should define both. DSM is... hacky... in terms of ethernet interfaces. All of them should be accounted for with different MAC addresses.

Okay, I figured out why DSM was showing two adapters with the same MAC address: I was declaring/assigning the MAC addresses in the wrong order in user_config.json

 

I originally had:

{
  "extra_cmdline": {
    "pid": "0x1000",
    "vid": "0x090c",
    "sn": "xxxxLWNxxxxxx",
    "mac1": "xxxxxxxxxx75",
    "mac2": "xxxxxxxxxx74"
  },
  "synoinfo": {},
  "ramdisk_copy": {}
}

Which manifested as "mac2=xxxxxxxxxx74 mac1=xxxxxxxxxx75" in my grub.cfg. This resulted in DSM seeing two adapters with the same MAC address of xxxxxxxxxx75

 

Swapping them around to:

{
  "extra_cmdline": {
    "pid": "0x1000",
    "vid": "0x090c",
    "sn": "xxxxLWNxxxxxx",
    "mac1": "xxxxxxxxxx74",
    "mac2": "xxxxxxxxxx75"
  },
  "synoinfo": {},
  "ramdisk_copy": {}
}

Gives me a grub.cfg with  "mac2=xxxxxxxxxx75 mac1=xxxxxxxxxx74" and two NICs with the correct, different, MAC addresses in DSM. This is obviously to do with the order in which the kernel enumerates the NIC interfaces, and the MAC addresses have to be declared in a way that matches that order or linux/DSM gets confused.

Link to post
Share on other sites

ok, something is wrong with new driver (or maybe i something thing screw up).

I have 7.0.1 DS918+ installed. Today i compile new redpill and "burn" on new flashdrive. Everything seems to launch correct, ping to NAS working, Synology Assistant found NAS with status "ready". But when i try go to IP:5000 then NAS goes to hard reboot. Does anyone has the same issue?

Link to post
Share on other sites

So with latest loader with ESXi Smart patch. I'm not able to install DSM 7.0 anymore. It fails at 55%.

 

My json file :

Quote

{
  "extra_cmdline": {
    "pid": "0x0001",
    "vid": "0x46f4",
    "sn": "1330LWNXXXXXX",
    "mac1": "001132XXXXXX",
    "DiskIdxMap": "1000",
    "SataPortMap": "4"
  },
  "synoinfo": {
    "supportsystemperature": "no",
    "supportsystempwarning": "no"
  },
  "ramdisk_copy": {}
}

 

Lot of errors like this in serial console :

Quote

[   40.250478] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   41.374985] md: bind<sda1>
[   41.375642] md/raid1:md0: active with 1 out of 15 mirrors
[   41.378224] md0: detected capacity change from 0 to 2549940224
[   41.505472] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   43.505906] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   44.390874] md: bind<sda2>
[   44.391552] md/raid1:md1: active with 1 out of 15 mirrors
[   44.394133] md1: detected capacity change from 0 to 2147418112
[   44.399904]  md1: unknown partition table
[   44.412256]  md0: unknown partition table
[   44.760830] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   45.514641] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0)
[   45.516233] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0)
[   45.527836] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[   45.583100] synobios write r to /dev/ttyS1 failed
[   45.587024] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0)
[   45.588626] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0)
[   45.599715] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[   45.606322] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0)
[   45.607891] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0)
[   45.618772] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[   46.761253] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   48.016171] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   50.016607] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   51.271585] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   53.272041] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   54.526899] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   56.527327] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   57.782338] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   59.782790] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   61.037687] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   63.038119] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   64.293090] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   66.293501] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   67.548452] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   68.616764] EXT3-fs (md0): error: couldn't mount because of unsupported optional features (2c0)
[   68.618339] EXT2-fs (md0): error: couldn't mount because of unsupported optional features (2c0)
[   68.630789] EXT4-fs (md0): mounted filesystem with ordered data mode. Opts: (null)
[   69.548911] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   70.803832] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc
[   72.804282] parameter error. gpiobase=00000000, pin=4, pValue=ffff880134faf9bc

 

Link to post
Share on other sites
1 minute ago, shibby said:

ok, something is wrong with new driver (or maybe i something thing screw up).

I have 7.0.1 DS918+ installed. Today i compile new redpill and "burn" on new flashdrive. Everything seems to launch correct, ping to NAS working, Synology Assistant found NAS with status "ready". But when i try go to IP:5000 then NAS goes to hard reboot. Does anyone has the same issue?

I've not had that issue (not using the new image yet), but can you get the output from the serial console to see what's causing the crash?

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

I've not had that issue (not using the new image yet), but can you get the output from the serial console to see what's causing the crash?

if you tell me how can i do this from bare-metal i can try

Edited by shibby
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.