RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

I was successful at installing DSM 7 (3615xs) on a TheCUS N5550.  There were zero issues doing the install.  I configured 5 drives in RAID 6.  The system repeatedly would lock up or reboot over the next 2 days.   I used the TinyCore config tool so I'm not sure what it built.  I was using Jun's loader on this same NAS for the past few years with no issues with DSM 6.  

Link to post
Share on other sites

Does anyone have a Proxmox template to share? I have been trying to work this out off this tutorial but when I try to install the .pat I get a corruption error.

Edited by myswe
  • Like 1
Link to post
Share on other sites

Hi,
I need your help for create a volume on ssd nvme
My ssd is not visible on DSM7

 

I need to fill this ? I not have this in my apollolake_user_config.json and my all SATA HDD (6) is ok

"SasIdxMap": "0"
"SataPortMap": "00"
"DiskIdxMap": "00"

 

Edited by stefauresi
Link to post
Share on other sites

Hi PocoPico,

 

Everything's working fine with v0.4.4 image! Edited grub with vid, pid and mac1 and patched it with bromolow:

 

works like a charme on a hp prodesk 400 G2 mini  

 

thanx keasee

Bildschirmfoto 2022-01-14 um 16.29.42.png

  • Like 1
Link to post
Share on other sites

Hi PocoPico,
 
Everything works fine with image v0.4.4! Grub edited with vid, pid and mac1 for Proxmox, DSM 7.0.1-42218 Update 2

Everything to work perfectly, no mistakes.

Thank you for your work ^^

 

 

  • Like 1
Link to post
Share on other sites
9 hours ago, pocopico said:

 

its on @haydibe signature. 

 

 

 

Thank you!

 

I have now been able to build the boot loader but I am unable to install DSM. I get to the initial setup where I need to upload the .pat file but encounter a "corrupt file" error. Any pointers to what I could be doing wrong?

 

 

 

 

 

 

failed to install.PNG

Link to post
Share on other sites
44 minutes ago, myswe said:

 

Thank you!

 

I have now been able to build the boot loader but I am unable to install DSM. I get to the initial setup where I need to upload the .pat file but encounter a "corrupt file" error. Any pointers to what I could be doing wrong?

 

 

 

 

 

 

failed to install.PNG

Are you on proxmox right ? Make sure you have selected usb boot on grub and that the USB VID PID are set correctly 

Link to post
Share on other sites

 any chances for 3617xs 7.0.1 ? i read some posts but not understand where is problem ?

 

Everything works fine with others :) i put on one old machine with amd3 processor just for test, all working fine. reboot grub have 3 lines autoboot first, find with find synology install pat from cache, reboot and new nas is born :)

 

 

 

Link to post
Share on other sites
On 1/12/2022 at 8:42 PM, TheEvilSide said:

Hi all. I decided to try the redpill and I found a youtube video explaining how to compile the img, since my knowledge is very little. the video is a chinese one and it is called Vmware + xpenology DSM 7.0.1 with redpill. I am currently running the latest version of jun's loader with dsm 6.1.3 and it works fine. I have compiled and migrated and the result is very good.

 

- Outcome of the update:  SUCCESSFUL

- DSM version prior update: DSM 7.0.1-42218

- Lo ader version and model: redpill-tool-chain-master

- Using custom extra.lzma: NO

- Installation type: BAREMETAL - Msi B360m Pro-vd / Intel Celeron G5400 Gold / 4Gb ram DDR-4

- Additional comments: Reboot required

dsm7.thumb.jpg.c919d809e98d9de89d10d994bacdc302.jpg

 

Hello TheEvilSide and everyone, I wanted to ask you if you can better describe (step-by-step) the procedure you performed to upgrade (at least if I didn't get it wrong) from DSM 6.2.3 to 7.0.1. I also watched the video, I'm not an IT guru but I don't think I'm the last one, but I miss some steps that I don't understand in particular how to manage the red pill; this discussion does not help (I remember that it had started to upgrade from 6.2.3 to 6.2.4, then it went into everything as usual and made it practically useless, at least from how I see things, precisely because there is everything inside). Currently I have a server that I built specifically to run the DSM on 918+ loader which now I have version 6.2.3 up3 in barematal mode (for this I ask you, I saw you did it), with a Supermicro motherboard, an intel Xeon processor E2276 4 HHD sata, 64 Gb ram and 2 nvme ssd, thank you if you want to help me; particularly if it is a migration or a new installation. Thanks to those who will be able to help me bye

 

Link to post
Share on other sites
20 minutes ago, pocopico said:

Are you on proxmox right ? Make sure you have selected usb boot on grub and that the USB VID PID are set correctly 

 

Yes I am on Proxmox 7.

I mounted the image that you get after the creation as local disk SATA0.  I did not have success booting into the boot-loader any other way.

Are you saying I should try booting the image via USB?

Link to post
Share on other sites
3 minutes ago, myswe said:

 

Yes I am on Proxmox 7.

I mounted the image that you get after the creation as local disk SATA0.  I did not have success booting into the boot-loader any other way.

Are you saying I should try booting the image via USB?


The proxmox instructions are a bit different I think. The idea is to have the image set as usb device and boot from the usb device having the vid PID set to proxmox usb vid PID. 

Link to post
Share on other sites
30 minutes ago, gorski said:

 any chances for 3617xs 7.0.1 ? i read some posts but not understand where is problem ?

 

Everything works fine with others :) i put on one old machine with amd3 processor just for test, all working fine. reboot grub have 3 lines autoboot first, find with find synology install pat from cache, reboot and new nas is born :)

 

 

 


what is the issue you are facing ? You can use tinycore redpill for the loader creation. I have included @buggy25200 3617xs loader. 

Edited by pocopico
Link to post
Share on other sites

Is it possible to use the working 7.x redpill boot loader to downgrade to 6.2.4? I'm missing USB Audio and I plan to downgrade but I don't know if another specific 6.2.4 boot loader is needed. I would expect it can be done with the current working DSM 7 USB booter right?   

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

Yes I am on Proxmox 7.

I mounted the image that you get after the creation as local disk SATA0.  I did not have success booting into the boot-loader any other way.

Are you saying I should try booting the image via USB?

You didn't follow the link to my signature as @pocopico suggested, did you?

 

This will download tinycore, extract the image, create a preconfigured vm to use the extracted tinycore image with usb boot. It will also add a 100gb data disk, to be attached to sata0.

 

Run these command in the shell of your Proxmox server: 

# set vm id
id=930

# create image directory, download and uncomporess
mkdir -p /var/lib/vz/images/${id}
curl --location https://github.com/pocopico/tinycore-redpill/raw/main/tinycore-redpill.v0.4.4.img.gz --output /var/lib/vz/images/${id}/tinycore-redpill.img.gz
gzip --decompress /var/lib/vz/images/${id}/tinycore-redpill.img.gz --keep

# create vm
qm create ${id} \
  --args "-device 'qemu-xhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/${id}/tinycore-redpill.img,if=none,format=raw' -device 'usb-storage,drive=synoboot'" \
  --cores 2 \
  --cpu host \
  --machine q35 \
  --memory 2048 \
  --name DSM \
  --net0 virtio,bridge=vmbr0 \
  --numa 0 \
  --onboot 0 \
  --ostype l26 \
  --scsihw virtio-scsi-pci \
  --sata0 local-lvm:vm-${id}-disk-0,discard=on,size=100G,ssd=1 \
  --sockets 1 \
  --serial0 socket \
  --serial1 socket \
  --tablet 1

# create disk for sata0
pvesm alloc local-lvm ${id} vm-${id}-disk-0 100G

Make sure to change the value for id from 930 to an id of your choosing.

 

If you want a bigger data disk, just change 100G to how much G you want. Once the vm is created, the settings can be changed in the Proxmox frontend later.

 

A valid user_config.json for q35 machine looks something like this. The vid and pid are correct if usb-boot is used (the commands above exactly do that).

The SataPortMap and DiskIdxMap are valid for the q35 machine type - the values are not valid for i440fx machine type.

{
    "extra_cmdline": {
        "vid": "0x46f4",
        "pid": "0x0001",
        "sn": "1510LWN123456",
        "mac1": "00123456789A",
        "SasIdxMap": "0",
        "SataPortMap": "66",
        "DiskIdxMap": "0600"
    },
    "synoinfo": {
        "internalportcfg": "0xffff",
        "maxdisks": "16"
    },
    "ramdisk_copy": {}
}

 

Edited by haydibe
Link to post
Share on other sites

Now TinyCore did on Baremetal a lot to get this done.

This time I had may Drives (8x with lots of Data) Plugged off and leaved 2 SSDs on one of my HBA´s.

 

The Search finds a 3615XS, but no drives. MPT3 extension is added...

...LSI 2008 IT Mode...strange thing.

 

 

Anyone here got the HBA working here?  Mine shows as Fusion MPT2 2008 8-Port

If=yes --> HOW???

LSPCI ESXi.rtf

 

@pocopico does your Extension work with the provided Device IDs?

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

You didn't follow the link to my signature as @pocopico suggested, did you?

 

This will download tinycore, extract the image, create a preconfigured vm to use the extracted tinycore image with usb boot. It will also add a 100gb data disk, to be attached to sata0.

 

Run these command in the shell of your Proxmox server: 


# set vm id
id=930

# create image directory, download and uncomporess
mkdir -p /var/lib/vz/images/${id}
curl --location https://github.com/pocopico/tinycore-redpill/raw/main/tinycore-redpill.v0.4.4.img.gz --output /var/lib/vz/images/${id}/tinycore-redpill.img.gz
gzip --decompress /var/lib/vz/images/${id}/tinycore-redpill.img.gz --keep

# create vm
qm create ${id} \
  --args "-device 'qemu-xhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/${id}/tinycore-redpill.img,if=none,format=raw' -device 'usb-storage,drive=synoboot'" \
  --cores 2 \
  --cpu host \
  --machine q35 \
  --memory 2048 \
  --name DSM \
  --net0 virtio,bridge=vmbr0 \
  --numa 0 \
  --onboot 0 \
  --ostype l26 \
  --scsihw virtio-scsi-pci \
  --sata0 local-lvm:vm-${id}-disk-0,discard=on,size=100G,ssd=1 \
  --sockets 1 \
  --serial0 socket \
  --serial1 socket \
  --tablet 1

# create disk for sata0
pvesm alloc local-lvm ${id} vm-${id}-disk-0 100G

Make sure to change the value for id from 930 to an id of your choosing.

 

If you want a bigger data disk, just change 100G to how much G you want. Once the vm is created, the settings can be changed in the Proxmox frontend later.

 

A valid user_config.json for q35 machine looks something like this. The vid and pid are correct if usb-boot is used (the commands above exactly do that).

The SataPortMap and DiskIdxMap are valid for the q35 machine type - the values are not valid for i440fx machine type.


{
    "extra_cmdline": {
        "vid": "0x46f4",
        "pid": "0x0001",
        "sn": "1510LWN123456",
        "mac1": "00123456789A",
        "SasIdxMap": "0",
        "SataPortMap": "66",
        "DiskIdxMap": "0600"
    },
    "synoinfo": {
        "internalportcfg": "0xffff",
        "maxdisks": "16"
    },
    "ramdisk_copy": {}
}

 

 

Thank you very much again. Your help is very much appreciated.

I did look at the post but I assume my lack of technical understanding is the culprit, please excuse me.

I followed your instructions but its missing the USB boot portion. Would you mind sharing how to appropriately usb-boot the vm?

 

I tried adding a USB Device via pass-through (both via port and device id) which then enabled me to boot and create the image. However at the end of that process I am still presented with the corruption error. So I assume adding a USB device like I do is the issue and I am trying to work out how to boot from the image that gets downloaded at the beginning of your instructions.

Thanks again!

 

Link to post
Share on other sites

@myswe I understand the sequence of commands went over your head. 

 

The sole purpose of the commands is to make it easy for every Proxmox user to download tinycore and create a proxmox vm that uses the img-file as  usb-boot. The usb-boot configuration is NOT visible in the ui and can not be configured or changed from the ui.  But you can see the "real" configuration in /etc/pve/nodes/${nodename}/qemu-server/${id}.conf (at least that's the location in my 3 node Proxmox cluster).

 

This part is responsible to do so (only works if the sequence of commands I pasted, otherwise the variable ${id} will be empty: `

--args "-device 'qemu-xhci,addr=0x18' -drive 'id=synoboot,file=/var/lib/vz/images/${id}/tinycore-redpill.img,if=none,format=raw' -device 'usb-storage,drive=synoboot'" \`

 

Please throw away the created vm with all your customizations, and the hdd and re-execute the sequence of commands.

 

This time start the vm without changes, generate serial and mac, compare the created user_config.json with what I wrote above and then build your configuration. You will see that it works ootb.

 

There is no need to guess or do random things without understanding why they would be necessary or understanding the impact of your changes.

Please do not skip or modify parts of the command sequence you don't understand.

 

 

 

Edited by haydibe
Link to post
Share on other sites

Hello Community!

 

Any ideas to add a missing NVMe SSD to DSM7 bromolow? 

the internal sata ssd is found, but the additional NVMe will not be found (BIOS is ok, and we can find it by lspci)

 

my disk parameters on grub are :

sataportmap = 00

diskidxmap = 4

 

ash-4.4# lspci -nnq

0000:00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:190f] (rev 07)

0000:00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06)

0000:00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31)

0000:00:14.2 Signal processing controller [1180]: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem [8086:a131] (rev 31)

0000:00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31)

0000:00:17.0 SATA controller [0106]: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] [8086:a102] (rev 31)

0000:00:1c.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 [8086:a114] (rev f1)

0000:00:1d.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #10 [8086:a119] (rev f1)

0000:00:1f.0 ISA bridge [0601]: Intel Corporation H110 Chipset LPC/eSPI Controller [8086:a143] (rev 31)

0000:00:1f.2 Memory controller [0580]: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller [8086:a121] (rev 31)

0000:00:1f.3 Audio device [0403]: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller [8086:a170] (rev 31)

0000:00:1f.4 SMBus [0c05]: Intel Corporation 100 Series/C230 Series Chipset Family SMBus [8086:a123] (rev 31)

0000:01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller 980 [144d:a809]

0000:02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)

0001:07:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 11)

0001:08:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 11)

0001:09:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 11)

0001:0a:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 11)

Bildschirmfoto 2022-01-15 um 12.12.57.png

Edited by keasee
Link to post
Share on other sites
Hello Community!
 
Any ideas to add a missing NVMe SSD to DSM7 bromolow? 
the internal sata ssd is found, but the additional NVMe will not be found (BIOS is ok, and we can find it by lspci)
 
my disk parameters on grub are :
sataportmap = 00
diskidxmap = 4
 
ash-4.4# lspci -nnq
0000:00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers [8086:190f] (rev 07)
0000:00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06)
0000:00:14.0 USB controller [0c03]: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller [8086:a12f] (rev 31)
0000:00:14.2 Signal processing controller [1180]: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem [8086:a131] (rev 31)
0000:00:16.0 Communication controller [0780]: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 [8086:a13a] (rev 31)
0000:00:17.0 SATA controller [0106]: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] [8086:a102] (rev 31)
0000:00:1c.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 [8086:a114] (rev f1)
0000:00:1d.0 PCI bridge [0604]: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #10 [8086:a119] (rev f1)
0000:00:1f.0 ISA bridge [0601]: Intel Corporation H110 Chipset LPC/eSPI Controller [8086:a143] (rev 31)
0000:00:1f.2 Memory controller [0580]: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller [8086:a121] (rev 31)
0000:00:1f.3 Audio device [0403]: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller [8086:a170] (rev 31)
0000:00:1f.4 SMBus [0c05]: Intel Corporation 100 Series/C230 Series Chipset Family SMBus [8086:a123] (rev 31)
0000:01:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller 980 [144d:a809]
0000:02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
0001:07:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 11)
0001:08:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 11)
0001:09:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 11)
0001:0a:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller [1b4b:9235] (rev 11)
1703803987_Bildschirmfoto2022-01-15um12_12_57.thumb.png.2e2e9f12b9eb68eefc124ae754a911ea.png


The DS3615xs doesn't have a physical NVMe port, this was introduced in the DS918+, and therefore the utilities for managing NVMe disk cache is not available. Note that DS918+ also needs an Intel 6th gen CPU to boot because of the Intel atom extensions being used in that platform wasn't available in normal Intel CPU before that. Also as you may note, NVMe cannot be used for storage, only as cache.

Skickat från min LE2113 via Tapatalk




  • Thanks 1
Link to post
Share on other sites
il y a 21 minutes, Piteball a dit :

 


The DS3615xs doesn't have a physical NVMe port, this was introduced in the DS918+, and therefore the utilities for managing NVMe disk cache is not available. Note that DS918+ also needs an Intel 6th gen CPU to boot because of the Intel atom extensions being used in that platform wasn't available in normal Intel CPU before that. Also as you may note, NVMe cannot be used for storage, only as cache.

Skickat från min LE2113 via Tapatalk



 

 

Hi ,

With my Xpenology DS918+ (DSM7) I don't see nvme disk on storage manager 

0000:03:00.0 Non-Volatile memory controller [0108]: Micron Technology Inc Device [1344:5405]

 

image.thumb.png.914d6cfe3918b4e659f87dddd170260d.png

Edited by stefauresi
Link to post
Share on other sites
Hi ,
With my Xpenology DS918+ (DSM7) I don't see nvme disk on storage manager 
0000:03:00.0 Non-Volatile memory controller [0108]: Micron Technology Inc Device [1344:5405]
 
image.thumb.png.914d6cfe3918b4e659f87dddd170260d.png
That's because it only supports official Synology NVMe cache out of the box, you will have to hex edit the driver to replace device ID with the one of your NVMe device.

Skickat från min LE2113 via Tapatalk

Link to post
Share on other sites
7 minutes ago, stefauresi said:

Hi ,

With my Xpenology DS918+ (DSM7) I don't see nvme disk on storage manager 

0000:03:00.0 Non-Volatile memory controller [0108]: Micron Technology Inc Device [1344:5405]

 

image.thumb.png.914d6cfe3918b4e659f87dddd170260d.png

Stefauresi : do you use NVMe ? as Disk or DiskCache ?

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.