Jump to content
XPEnology Community

RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

Hi, happy new year! 
I'm planning to update my DSM6 Gen8 bare metal NAS to DSM7, but i have several packages already installe that are not ported to DSM7, for example teamspeak server, what happens ? 
Simply DSM7 delete package? , the old package remain installed? 

Thanks 

Link to comment
Share on other sites

9 hours ago, Aigor said:

Hi, happy new year! 
I'm planning to update my DSM6 Gen8 bare metal NAS to DSM7, but i have several packages already installe that are not ported to DSM7, for example teamspeak server, what happens ? 
Simply DSM7 delete package? , the old package remain installed? 

Thanks 

Teamspeak has an official docker https://hub.docker.com/_/teamspeak

 

Link to comment
Share on other sites

15 hours ago, painkiller895 said:

have created a image with:
'DS3615xs' '7.0.1-412218 I keep getting this error,  where do I map sata hard drive bios is set to ACHI

I get the same error using 918+ loader

 

Please help

 

 

Screenshot 2022-01-01 at 13-15-35 Synology Web Assistant.png

 

Hi,

 

I'm getting the same problem, this my setup:

Asus B85M-G Bios version 3602
i5-4440
Booting from USB thumbdrive
RedPill DS918+ v7.0.1-42218

Tried IDE & AHCI mode, Hot plug ON/OFF; different HDDs; still doesn't work

 

Any thoughts?

Edited by MichelD
Link to comment
Share on other sites

15 hours ago, painkiller895 said:

have created a image with:
'DS3615xs' '7.0.1-412218 I keep getting this error,  where do I map sata hard drive bios is set to ACHI

I get the same error using 918+ loader

 

Please help

 

 

Try to modify grub.cfg , DiskIdxMap=00 SataPortMap=1 SasIdxMap=0

 

Link to comment
Share on other sites

4 hours ago, MichelD said:

 

Hi,

 

I'm getting the same problem, this my setup:

Asus B85M-G Bios version 3602
i5-4440
Booting from USB thumbdrive
RedPill DS918+ v7.0.1-42218

Tried IDE & AHCI mode, Hot plug ON/OFF; different HDDs; still doesn't work

 

Any thoughts?

 

RedPill DS918+ v7.0.1-42218 (USB, Verbose

 

I have the same problem for 4gen intel cpu, Intel QM87 Express Chipset.
No problems for 6gen intel.

 

I tested the settings:

SataPortMap=

SataPortMap=0

SataPortMap=1

SataPortMap=2

SataPortMap=6

SataPortMap=22

SataPortMap=44

 

 

Error no disk or error disk and replace

 

maybe the old chipset is not supported?

 

Edited by dvbmaniak
Link to comment
Share on other sites

6 hours ago, u357 said:

 

#
# ### !!! WARNING - READ ME !!! ###
#
# DO NOT edit this file. This file has been generated automatically by the loader generator.
# If you were asked to use a pre-made image and asked by someone to edit this file DO NOT do it. The only
# supported method of obtaining the loader image is generating it using the loader generator provided.
#

terminal_output console
if serial --unit=0 --speed=115200; then
    terminal_input --append serial_com0
    terminal_output --append serial_com0
fi

set default="0"
set timeout="5"
set timeout_style="menu"

if [ -s $prefix/grubenv ]; then
    load_env --file $prefix/grubenv --skip-sig
    set has_env="1"
    if [ -n "${saved_entry}" ]; then
        set default="${saved_entry}"
    fi
else
    set has_env="0"
    echo "WARN: failed to load env. Default choice will NOT be saved!"
fi


function savedefault {
    saved_entry="${chosen}"
    save_env --file $prefix/grubenv saved_entry
}


insmod usb_keyboard
insmod part_msdos
insmod ext2
insmod fat
insmod linux
insmod gzio

set gfxmode=auto
insmod vbe
insmod vga

# UEFI
insmod efi_gop
insmod efi_uga

insmod font
if loadfont ${prefix}/unicode.pf2
then
    insmod gfxterm
    set gfxmode=auto
    set gfxpayload=keep
    terminal_output gfxterm
fi

menuentry 'RedPill DS3615xs v7.0.1-42218 Beta (USB, Verbose)' {
    savedefault
    set root=(hd0,msdos1)
    echo Loading Linux...
    linux /zImage mac1=001132000000 netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=0 vid=0x5571 syno_hdd_detect=0 pid=0x0781 console=ttyS0,115200n8 elevator=elevator sn=1730000000000 root=/dev/md0 earlyprintk loglevel=15 log_buf_len=32M syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS3615xs vender_format_version=2
    echo Loading initramfs...
    initrd /rd.gz /custom.gz
    echo Starting kernel with USB boot
}

menuentry 'RedPill DS3615xs v7.0.1-42218 Beta (SATA, Verbose)' {
    savedefault
    set root=(hd0,msdos1)
    echo Loading Linux...
    linux /zImage mac1=001132000000 netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=0 vid=0x5571 synoboot_satadom=1 syno_hdd_detect=0 pid=0x0781 console=ttyS0,115200n8 elevator=elevator sn=17300000000 root=/dev/md0 earlyprintk loglevel=15 log_buf_len=32M syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS3615xs vender_format_version=2
    echo Loading initramfs...
    initrd /rd.gz /custom.gz
    echo Starting kernel with SATA boot
}

 

 

 

 

 

 

 

=======================================

SN: & Mac # were change on this; no to show actual.

 

 

It said not to edit file  o.k.

so where would I add sata port mapping here, I don't see any line to add it to or change....

Link to comment
Share on other sites

8 hours ago, dvbmaniak said:

 

RedPill DS918+ v7.0.1-42218 (USB, Verbose

 

I have the same problem for 4gen intel cpu, Intel QM87 Express Chipset.
No problems for 6gen intel.

 

I tested the settings:

SataPortMap=

SataPortMap=0

SataPortMap=1

SataPortMap=2

SataPortMap=6

SataPortMap=22

SataPortMap=44

 

 

Error no disk or error disk and replace

 

maybe the old chipset is not supported?

 

 

That'd be a bummer, the whole point is to run DSM on older (read more affordable) yet powerful H/W. Could somebody confirm abt the chipset?

Link to comment
Share on other sites

On 12/28/2021 at 3:01 PM, pocopico said:

 

You need to understand what every option means first. Start by reading : 

https://gugucomputing.wordpress.com/2018/11/11/experiment-on-sata_args-in-grub-cfg/

 

And continue testing

 

Same applies for you @pipsen

 

Thanks for the article, that helped me sort out the disk order/getting all disks to show up. But, it didn't solve the issue of virtual SCSI disks being wonky in DSM. I'll start by saying that SATA virtual disks with redpill continue to work fine and reliably. Using your extension for vmw_pvscsi (or mptsas) I am able to get virtual SCSI disks to show up in DSM. Attaching a few screenshots to walk through the issue.

57901411_ScreenShot2022-01-02at9_00_10PM.thumb.png.7335b449bb1345671b72364a6e10e6f4.png

Here we can see all disks attached. Loader VMDK is Drive 1 (hidden when redpill SATA boot option is used instead of USB) and a test SATA virtual disk is Drive 2 on the same SATA controller as the loader. Drive 3-Drive 6 are PV SCSI disks attached to a SCSI controller. SataPortMap=24 and DiskIdxMap=0002 so all is showing correctly. If I create a storage pool and volume with SATA disk, it works. But notice how only the 1st SCSI disk is showing up as "VMware Virtual disk (HDD)" and the other just show "Virtual disk". And if I expand Drive 3 vs Drive 4 you can see Drive 3 has fake smart values for it, and as such, the SMART shim gets DSM to think it is "Healthy" but Drive 4 (and 5 & 6 too) don't get fake SMART data and don't show healthy status.

270668010_ScreenShot2022-01-02at9_00_21PM.thumb.png.a3be7bce0b6fd4117800f67378d760b2.png

As to be expected.... if I create a storage pool and volume with Drive 3, it works.... but Drive 4-6 don't even show up as selectable since they are not marked "Healthy". Here's where it got weird too. After creating the Storage Pool and Volume with Drive 3 (the 1st SCSI disk), it magically just flipped position with Drive 4.... The below shot shows Drive 4 as having the Storage Pool along with Drive 3 (that I just created with only Drive 3 though) and Drive 3 as now being one of the generic "Virtual disk" ones without SMART data.

2079537460_ScreenShot2022-01-02at9_02_11PM.thumb.png.dd417f4b3434ccc144cec6d125c3da52.png

Very weird.... but after a minute, it flipped back.... and all was normal again, except Drive 4-6 still didn't have fake SMART data or a Healthy status allowing use in Storage Pools.

 

So.... building off my previous post, I am wondering if something is going on here with SCSI disks and the SMART shim from @ThorGroup. The disks clearly show up correctly once the proper driver extension is used, but it seems they show up unreliably and have issues getting fake SMART data, making them unstable, and unusable for storage pools.

 

That being said, I easily could be wrong and am curious what others are seeing especially those trying virtual SCSI disks. I am guessing (and I have no hardware on my end to try myself) that those using passthrough SCSI controllers are not seeing this issue, as I'm assuming SMART data passes through also, which means the redpill SMART shim isn't used to fake data.

Link to comment
Share on other sites

6 часов назад, ilovepancakes сказал:

 

Thanks for the article, that helped me sort out the disk order/getting all disks to show up. But, it didn't solve the issue of virtual SCSI disks being wonky in DSM. I'll start by saying that SATA virtual disks with redpill continue to work fine and reliably. Using your extension for vmw_pvscsi (or mptsas) I am able to get virtual SCSI disks to show up in DSM. Attaching a few screenshots to walk through the issue.

57901411_ScreenShot2022-01-02at9_00_10PM.thumb.png.7335b449bb1345671b72364a6e10e6f4.png

Here we can see all disks attached. Loader VMDK is Drive 1 (hidden when redpill SATA boot option is used instead of USB) and a test SATA virtual disk is Drive 2 on the same SATA controller as the loader. Drive 3-Drive 6 are PV SCSI disks attached to a SCSI controller. SataPortMap=24 and DiskIdxMap=0002 so all is showing correctly. If I create a storage pool and volume with SATA disk, it works. But notice how only the 1st SCSI disk is showing up as "VMware Virtual disk (HDD)" and the other just show "Virtual disk". And if I expand Drive 3 vs Drive 4 you can see Drive 3 has fake smart values for it, and as such, the SMART shim gets DSM to think it is "Healthy" but Drive 4 (and 5 & 6 too) don't get fake SMART data and don't show healthy status.

270668010_ScreenShot2022-01-02at9_00_21PM.thumb.png.a3be7bce0b6fd4117800f67378d760b2.png

As to be expected.... if I create a storage pool and volume with Drive 3, it works.... but Drive 4-6 don't even show up as selectable since they are not marked "Healthy". Here's where it got weird too. After creating the Storage Pool and Volume with Drive 3 (the 1st SCSI disk), it magically just flipped position with Drive 4.... The below shot shows Drive 4 as having the Storage Pool along with Drive 3 (that I just created with only Drive 3 though) and Drive 3 as now being one of the generic "Virtual disk" ones without SMART data.

2079537460_ScreenShot2022-01-02at9_02_11PM.thumb.png.dd417f4b3434ccc144cec6d125c3da52.png

Very weird.... but after a minute, it flipped back.... and all was normal again, except Drive 4-6 still didn't have fake SMART data or a Healthy status allowing use in Storage Pools.

 

So.... building off my previous post, I am wondering if something is going on here with SCSI disks and the SMART shim from @ThorGroup. The disks clearly show up correctly once the proper driver extension is used, but it seems they show up unreliably and have issues getting fake SMART data, making them unstable, and unusable for storage pools.

 

That being said, I easily could be wrong and am curious what others are seeing especially those trying virtual SCSI disks. I am guessing (and I have no hardware on my end to try myself) that those using passthrough SCSI controllers are not seeing this issue, as I'm assuming SMART data passes through also, which means the redpill SMART shim isn't used to fake data.

Thank you very much for such a detailed report.
I will tell you about my results. maybe it will be useful to someone.
I am using vmware 16 hypervisor.
I can say that I also have no problems with displaying disks on sata 0 controllers (for example, if you hook up working disks immediately after the 0: 1 0: 2 bootloader, etc.) and also all disks work correctly if they are installed on the sata 1 controller : 0 1: 1, etc. at the same time, I can connect disks directly as a RAW array natively and achieve maximum performance, also through a virtual disk, creating it manually by the virtual machine itself.
 BUT I could not connect any disks except on the SATA controllers (that is, NVMe and SCSI are not recognized), while I have both SATA and NVMe physical disks in the system. QUESTION. is it possible to connect an NVMe or SCSI disk via vmware so that it can be used as SSD cash in DSM? at the moment I have not found an opportunity to connect SSD cash in DSM, I am using vmware 16
 if someone has a solution to this issue, tell me where to look. THANKS everyone for their help!

Link to comment
Share on other sites

17 hours ago, painkiller895 said:

#
# ### !!! WARNING - READ ME !!! ###
#
# DO NOT edit this file. This file has been generated automatically by the loader generator.
# If you were asked to use a pre-made image and asked by someone to edit this file DO NOT do it. The only
# supported method of obtaining the loader image is generating it using the loader generator provided.
#

terminal_output console
if serial --unit=0 --speed=115200; then
    terminal_input --append serial_com0
    terminal_output --append serial_com0
fi

set default="0"
set timeout="5"
set timeout_style="menu"

if [ -s $prefix/grubenv ]; then
    load_env --file $prefix/grubenv --skip-sig
    set has_env="1"
    if [ -n "${saved_entry}" ]; then
        set default="${saved_entry}"
    fi
else
    set has_env="0"
    echo "WARN: failed to load env. Default choice will NOT be saved!"
fi


function savedefault {
    saved_entry="${chosen}"
    save_env --file $prefix/grubenv saved_entry
}


insmod usb_keyboard
insmod part_msdos
insmod ext2
insmod fat
insmod linux
insmod gzio

set gfxmode=auto
insmod vbe
insmod vga

# UEFI
insmod efi_gop
insmod efi_uga

insmod font
if loadfont ${prefix}/unicode.pf2
then
    insmod gfxterm
    set gfxmode=auto
    set gfxpayload=keep
    terminal_output gfxterm
fi

menuentry 'RedPill DS3615xs v7.0.1-42218 Beta (USB, Verbose)' {
    savedefault
    set root=(hd0,msdos1)
    echo Loading Linux...
    linux /zImage mac1=001132000000 netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=0 vid=0x5571 syno_hdd_detect=0 pid=0x0781 console=ttyS0,115200n8 elevator=elevator sn=1730000000000 root=/dev/md0 earlyprintk loglevel=15 log_buf_len=32M syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS3615xs vender_format_version=2
    echo Loading initramfs...
    initrd /rd.gz /custom.gz
    echo Starting kernel with USB boot
}

menuentry 'RedPill DS3615xs v7.0.1-42218 Beta (SATA, Verbose)' {
    savedefault
    set root=(hd0,msdos1)
    echo Loading Linux...
    linux /zImage mac1=001132000000 netif_num=1 earlycon=uart8250,io,0x3f8,115200n8 syno_hdd_powerup_seq=0 vid=0x5571 synoboot_satadom=1 syno_hdd_detect=0 pid=0x0781 console=ttyS0,115200n8 elevator=elevator sn=17300000000 root=/dev/md0 earlyprintk loglevel=15 log_buf_len=32M syno_port_thaw=1 HddHotplug=0 withefi syno_hw_version=DS3615xs vender_format_version=2
    echo Loading initramfs...
    initrd /rd.gz /custom.gz
    echo Starting kernel with SATA boot
}

 

 

 

 

 

 

 

=======================================

SN: & Mac # were change on this; no to show actual.

 

 

It said not to edit file  o.k.

so where would I add sata port mapping here, I don't see any line to add it to or change....


In the menuentry section, there is a line starting with linux. That’s a single line. On this line add SataPortMap= and DiskIdxMap= 

Edited by pocopico
Link to comment
Share on other sites

Hi together,

 

this is the result of lspci:

Spoiler

00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub (rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated Graphics Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 01)
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 01)
00:1c.2 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 3 (rev 01)
00:1c.3 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 4 (rev 01)
00:1c.4 PCI bridge: Intel Corporation 82801GR/GH/GHM (ICH7 Family) PCI Express Port 5 (rev 01)
00:1c.5 PCI bridge: Intel Corporation 82801GR/GH/GHM (ICH7 Family) PCI Express Port 6 (rev 01)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 01)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 01)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 01)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 01)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 01)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev e1)
00:1f.0 ISA bridge: Intel Corporation 82801GB/GR (ICH7 Family) LPC Interface Bridge (rev 01)
00:1f.2 SATA controller: Intel Corporation NM10/ICH7 Family SATA Controller [AHCI mode] (rev 01)
00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 01)
09:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8071 PCI-E Gigabit Ethernet Controller (rev 16)
0a:00.0 IDE interface: Marvell Technology Group Ltd. 88SE6111/6121 SATA II / PATA Controller (rev b2)
 

 

Here I can see my one and only SATA controller: 00:1f.2

lsscsi -Hv shows on the SATA controller 00:1f.2 4 hosts/devices.

 

Spoiler

[0]    ahci          
  dir: /sys/class/scsi_host//host0
  device dir: /sys/devices/pci0000:00/0000:00:1f.2/ata1/host0
[1]    ahci          
  dir: /sys/class/scsi_host//host1
  device dir: /sys/devices/pci0000:00/0000:00:1f.2/ata2/host1
[2]    ahci          
  dir: /sys/class/scsi_host//host2
  device dir: /sys/devices/pci0000:00/0000:00:1f.2/ata3/host2
[3]    ahci          
  dir: /sys/class/scsi_host//host3
  device dir: /sys/devices/pci0000:00/0000:00:1f.2/ata4/host3

[4]    usb-storage   
  dir: /sys/class/scsi_host//host4
  device dir: /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-5/1-5:1.0/host4
[5]    usb-storage   
  dir: /sys/class/scsi_host//host5
  device dir: /sys/devices/pci0000:00/0000:00:1d.7/usb1/1-8/1-8:1.0/host5
[6]    pata_marvell  
  dir: /sys/class/scsi_host//host6
  device dir: /sys/devices/pci0000:00/0000:00:1c.5/0000:0a:00.0/ata5/host6
[7]    pata_marvell  
  dir: /sys/class/scsi_host//host7
  device dir: /sys/devices/pci0000:00/0000:00:1c.5/0000:0a:00.0/ata6/host7

 

At the moment only host0/device is used with a hard disk.

 

When I try "SasIdxMap": "0", "SataPortMap": "4", "DiskIdxMap": "00"

the installer is not able to find any disk.  

 

If I try  "SasIdxMap": "0", "SataPortMap": "1", "DiskIdxMap": "00" I get the error like painkiller here but only one drive is listed (which is correct cause I only inserted one hard disk at the moment)

Any ideas how to solve that?

Edited by Dreadnought
use of spoiler widget
Link to comment
Share on other sites

1 minute ago, haydibe said:

Can you try this:  "SasIdxMap": "0", "SataPortMap": "42", "DiskIdxMap": "0004"

Why does it show two usb devices? One usb stick and one usb drive?

 

There is one usb stick connected and there is an additional internal usb storage with around 400 MB. (I am using an Acer H340 device)

I will try your config. Thanks in advance. 

Link to comment
Share on other sites

Hi all,

I'm using a Dell T1700 cpu is a E3-1225 v3 This was working fine with loder DSM 6.2.3-25426 Update 3

I took USB and hard drives out,  I have a brand new Seagate Barracuda 2TB and a 16 GB SanDisk USB Stick.

I builded the Redpill DSM 7.0.1-42218 I was able to setup a VMWARE system with no problem,  What I having problems is with a Bear-metal install

I getting this after adding this to

grub.cfg , DiskIdxMap=00 SataPortMap=1 SasIdxMap=0

 

 

1600605658_Screenshot2022-01-03at15-23-10SynologyWebAssistant.thumb.png.45a8244667c16b8e862de991ddeaa98d.png

 

 

if I take off the mapping I get this error

 

1947801223_Screenshot2022-01-01at13-15-35SynologyWebAssistant.thumb.png.1175d59902be45772de94353dc681585.png

 

 

I tried it on a different computer also:  6th gen Dell 5040 with a i5 6500 chip that gave me a error stating that the dsm install file was corrupted even having the

right PID and VID ...  SO I keep hitting these brick walls with ds3615 and ds918 with fresh installs.  VMWARE install is working with no problem.

 

Please help,

thanks for all the hard working getting us up to dsm 7

 

 

 

 

 

 

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...