Jump to content
XPEnology Community

RedPill - the new loader for 6.2.4 - Discussion

ThorGroup

By ThorGroup
in Developer Discussion Room

 Share

Recommended Posts

Orphée Guru Master

Orphée

Posted
Posted (edited)
9 minutes ago, pocopico said:

 

I've tested them and they load ... i dont own an mpt2sas controller myself to test.

I probably failed somewere :

 

Added them in rd.gz /lib/modules/

then added a file in /lib/modules-load.d/

  

:: Loading module scsi_transport_sas[    2.409201] scsi_transport_sas: exports duplicate symbol sas_attach_transport (owned by kernel)
[    2.414065] scsi_transport_sas: exports duplicate symbol sas_attach_transport (owned by kernel)
 ... [FAILED]
:: Load[    2.425386] WARNING: module 'libsas' built without retpoline-enabled compiler, may affect Spectre v2 mitigation
in[    2.426028] libsas: exports duplicate symbol sas_prep_resume_ha (owned by kernel)
g module libsas[    2.435978] BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
[    2.436920] IP: [<ffffffff810ff57c>] free_percpu+0x5c/0x140
[    2.438944] PGD 135642067 PUD 135558067 PMD 0 
[    2.438965] Oops: 0000 [#1] SMP 
[    2.438987] Modules linked in: usb_storage xhci_hcd uhci_hcd ehci_pci ehci_hcd usbcore usb_common redpill(OF)
[    2.441935] CPU: 1 PID: 4543 Comm: insmod Tainted: GF          O 3.10.108 #42218
[    2.441956] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020
[    2.444930] task: ffff880136441040 ti: ffff8801355bc000 task.ti: ffff8801355bc000
[    2.444951] RIP: 0010:[<ffffffff810ff57c>]  [<ffffffff810ff57c>] free_percpu+0x5c/0x140
[    2.447941] RSP: 0018:ffff8801355bfd90  EFLAGS: 00010046
[    2.447962] RAX: 0000000000000000 RBX: 000188753dc00001 RCX: ffff880000000000
[    2.447983] RDX: 0000000000000000 RSI: 00003ffffffff000 RDI: 000188753dd00001
[    2.448005] RBP: 0000000000000203 R08: ffff8801355bc000 R09: 000000009131e78a
[    2.448026] R10: 0000000000000000 R11: ffff88013dd12fb0 R12: fffffffffffffff8
[    2.448048] R13: ffff88013dfd9d00 R14: ffffffff8160dee8 R15: ffffffffa00e3360
[    2.448069] FS:  00007fa982c87740(0000) GS:ffff88013dd00000(0000) knlGS:0000000000000000
[    2.450934] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[    2.450955] CR2: 0000000000000010 CR3: 000000013566c000 CR4: 00000000001607e0
[    2.450977] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    2.450998] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    2.451019] Stack:
[    2.451041]  ffff8801355bfec8 ffff8801355bfeb8 fffffffffffffff8 0000000000000000
[    2.453933]  ffffffff8109490b ffff8801355bffd8 00007ffffffff000 ffff8801355bfec8
[    2.456917]  ffff8801355bfed0 ffff880136441040 ffff880136441040 00000000364957c0
[    2.459925] Call Trace:
[    2.459957]  [<ffffffff8109490b>] ? load_module+0x134b/0x2540
[    2.459988]  [<ffffffff81095c9d>] ? SYSC_finit_module+0x7d/0xc0
[    2.460021]  [<ffffffff814affbe>] ? system_call_fastpath+0x1c/0x21
[    2.460042] Code: eb 00 00 00 00 49 8b 45 18 48 39 c3 73 59 48 8b 15 ba a6 7a 00 65 8b 04 25 20 e0 00 00 48 98 48 8b 3c c2 48 01 df e8 c4 43 01 00 <4c> 8b 68 10 44 8b 25 cd a6 7a 00 49 8b 45 18 48 89 de 4c 89 ef 
[    2.468908] RIP  [<ffffffff810ff57c>] free_percpu+0x5c/0x140
[    2.468929]  RSP <ffff8801355bfd90>
[    2.468951] CR2: 0000000000000010
[    2.468972] ---[ end trace 3c4678b0672f1a10 ]---
 ... [FAILED]
:: Loading module raid_class

 

Then I removed file from module-load.d and added them manually on VM once booted

  

root@Xpen_70:/usr/lib/modules# cp /volume1/homes/orphee/*.ko .
root@Xpen_70:/usr/lib/modules# chmod 644 *.ko
root@Xpen_70:/usr/lib/modules# insmod scsi_transport_sas.ko
insmod: ERROR: could not insert module scsi_transport_sas.ko: Invalid module format
root@Xpen_70:/usr/lib/modules# insmod libsas.ko
Killed
root@Xpen_70:/usr/lib/modules# insmod raid_class.ko (freeze)

 

message from dmesg when I insmod manually : 

[   42.904271] scsi_transport_sas: exports duplicate symbol sas_attach_transport (owned by kernel)

 

Edited by Orphée
Link to comment
Share on other sites
pocopico Guru Master

pocopico

Posted
Posted
37 minutes ago, Orphée said:

I probably failed somewere :

 

Added them in rd.gz /lib/modules/

then added a file in /lib/modules-load.d/

  


:: Loading module scsi_transport_sas[    2.409201] scsi_transport_sas: exports duplicate symbol sas_attach_transport (owned by kernel)
[    2.414065] scsi_transport_sas: exports duplicate symbol sas_attach_transport (owned by kernel)
 ... [FAILED]
:: Load[    2.425386] WARNING: module 'libsas' built without retpoline-enabled compiler, may affect Spectre v2 mitigation
in[    2.426028] libsas: exports duplicate symbol sas_prep_resume_ha (owned by kernel)
g module libsas[    2.435978] BUG: unable to handle kernel NULL pointer dereference at 0000000000000010
[    2.436920] IP: [<ffffffff810ff57c>] free_percpu+0x5c/0x140
[    2.438944] PGD 135642067 PUD 135558067 PMD 0 
[    2.438965] Oops: 0000 [#1] SMP 
[    2.438987] Modules linked in: usb_storage xhci_hcd uhci_hcd ehci_pci ehci_hcd usbcore usb_common redpill(OF)
[    2.441935] CPU: 1 PID: 4543 Comm: insmod Tainted: GF          O 3.10.108 #42218
[    2.441956] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 11/12/2020
[    2.444930] task: ffff880136441040 ti: ffff8801355bc000 task.ti: ffff8801355bc000
[    2.444951] RIP: 0010:[<ffffffff810ff57c>]  [<ffffffff810ff57c>] free_percpu+0x5c/0x140
[    2.447941] RSP: 0018:ffff8801355bfd90  EFLAGS: 00010046
[    2.447962] RAX: 0000000000000000 RBX: 000188753dc00001 RCX: ffff880000000000
[    2.447983] RDX: 0000000000000000 RSI: 00003ffffffff000 RDI: 000188753dd00001
[    2.448005] RBP: 0000000000000203 R08: ffff8801355bc000 R09: 000000009131e78a
[    2.448026] R10: 0000000000000000 R11: ffff88013dd12fb0 R12: fffffffffffffff8
[    2.448048] R13: ffff88013dfd9d00 R14: ffffffff8160dee8 R15: ffffffffa00e3360
[    2.448069] FS:  00007fa982c87740(0000) GS:ffff88013dd00000(0000) knlGS:0000000000000000
[    2.450934] CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
[    2.450955] CR2: 0000000000000010 CR3: 000000013566c000 CR4: 00000000001607e0
[    2.450977] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[    2.450998] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
[    2.451019] Stack:
[    2.451041]  ffff8801355bfec8 ffff8801355bfeb8 fffffffffffffff8 0000000000000000
[    2.453933]  ffffffff8109490b ffff8801355bffd8 00007ffffffff000 ffff8801355bfec8
[    2.456917]  ffff8801355bfed0 ffff880136441040 ffff880136441040 00000000364957c0
[    2.459925] Call Trace:
[    2.459957]  [<ffffffff8109490b>] ? load_module+0x134b/0x2540
[    2.459988]  [<ffffffff81095c9d>] ? SYSC_finit_module+0x7d/0xc0
[    2.460021]  [<ffffffff814affbe>] ? system_call_fastpath+0x1c/0x21
[    2.460042] Code: eb 00 00 00 00 49 8b 45 18 48 39 c3 73 59 48 8b 15 ba a6 7a 00 65 8b 04 25 20 e0 00 00 48 98 48 8b 3c c2 48 01 df e8 c4 43 01 00 <4c> 8b 68 10 44 8b 25 cd a6 7a 00 49 8b 45 18 48 89 de 4c 89 ef 
[    2.468908] RIP  [<ffffffff810ff57c>] free_percpu+0x5c/0x140
[    2.468929]  RSP <ffff8801355bfd90>
[    2.468951] CR2: 0000000000000010
[    2.468972] ---[ end trace 3c4678b0672f1a10 ]---
 ... [FAILED]
:: Loading module raid_class

 

Then I removed file from module-load.d and added them manually on VM once booted

  


root@Xpen_70:/usr/lib/modules# cp /volume1/homes/orphee/*.ko .
root@Xpen_70:/usr/lib/modules# chmod 644 *.ko
root@Xpen_70:/usr/lib/modules# insmod scsi_transport_sas.ko
insmod: ERROR: could not insert module scsi_transport_sas.ko: Invalid module format
root@Xpen_70:/usr/lib/modules# insmod libsas.ko
Killed
root@Xpen_70:/usr/lib/modules# insmod raid_class.ko (freeze)

 

 

Actually i think you've missed the edit i did on my earlier post . On 3615 libsas/scsi_transport_sas/raid_class are already statically linked. You do not need to load them again.

 

Link to comment
Share on other sites
Orphée Guru Master

Orphée

Posted
Posted
2 minutes ago, pocopico said:

 

Actually i think you've missed the edit i did on my earlier post . On 3615 libsas/scsi_transport_sas/raid_class are already statically linked. You do not need to load them again.

 

Oh my bad.

So as original mpt2sas module show disks as /dev/sas* ...

Maybe yours will work as @flybird08 on DS918+ and make them appear as /dev/sdX

 

Or dependency linked modules will block it do work as /dev/sdX (and will have to wait for Thorgroup magic)

Link to comment
Share on other sites
pocopico Guru Master

pocopico

Posted
Posted
2 minutes ago, Orphée said:

Oh my bad.

So as original mpt2sas module show disks as /dev/sas* ...

Maybe yours will work as @flybird08 on DS918+ and make them appear as /dev/sdX

 

Or dependency linked modules will block it do work as /dev/sdX (and will have to wait for Thorgroup magic)

 

Do you get any SAS device with fdisk -l ? 

Link to comment
Share on other sites
pocopico Guru Master

pocopico

Posted
Posted

On VMware workstation when i set scsi0.virtualDev = "lsisas1068" and load mptbase.ko/mptscsih.ko and mptsas.ko

 

i get :

  

[   81.422175] mptbase: ioc0: Initiating bringup
[   81.442796] ioc0: LSISAS1068 B0: Capabilities={Initiator}
[   81.485990] scsi60 : ioc0: LSISAS1068 B0, FwRev=01032920h, Ports=1, MaxQ=128, IRQ=19
[   81.489996] mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 0, phy 0, sas_addr 0x5000c29f43fdb9d3
[   81.492826] scsi 60:0:0:0: Direct-Access     VMware,  VMware Virtual S         1.0  PQ: 0 ANSI: 2
[   81.495317] sd 60:0:0:0: [sdbi] 67108864 512-byte logical blocks: (34.3 GB/32.0 GiB)
[   81.497500] sd 60:0:0:0: [sdbi] Write Protect is off
[   81.498732] sd 60:0:0:0: [sdbi] Mode Sense: 61 00 00 00
[   81.500093] sd 60:0:0:0: [sdbi] Cache data unavailable
[   81.501401] sd 60:0:0:0: [sdbi] Assuming drive cache: write through
[   81.503056] sd 60:0:0:0: Attached scsi generic sg2 type 0
[   81.505090] sd 60:0:0:0: [sdbi] Cache data unavailable
[   81.506367] sd 60:0:0:0: [sdbi] Assuming drive cache: write through
[   81.508114]  sdbi: unknown partition table
[   81.509514] sd 60:0:0:0: [sdbi] Cache data unavailable
[   81.510908] sd 60:0:0:0: [sdbi] Assuming drive cache: write through
[   81.512985] sd 60:0:0:0: [sdbi] Attached SCSI disk

 

Still the disk though is not available in DSM, maybe i need something else as well.

 

Also what is your PCI ID ?

Link to comment
Share on other sites
Orphée Guru Master

Orphée

Posted
Posted (edited)
19 minutes ago, pocopico said:

On VMware workstation when i set scsi0.virtualDev = "lsisas1068" and load mptbase.ko/mptscsih.ko and mptsas.ko

 

i get :

 

[   81.422175] mptbase: ioc0: Initiating bringup
[   81.442796] ioc0: LSISAS1068 B0: Capabilities={Initiator}
[   81.485990] scsi60 : ioc0: LSISAS1068 B0, FwRev=01032920h, Ports=1, MaxQ=128, IRQ=19
[   81.489996] mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 0, phy 0, sas_addr 0x5000c29f43fdb9d3
[   81.492826] scsi 60:0:0:0: Direct-Access     VMware,  VMware Virtual S         1.0  PQ: 0 ANSI: 2
[   81.495317] sd 60:0:0:0: [sdbi] 67108864 512-byte logical blocks: (34.3 GB/32.0 GiB)
[   81.497500] sd 60:0:0:0: [sdbi] Write Protect is off
[   81.498732] sd 60:0:0:0: [sdbi] Mode Sense: 61 00 00 00
[   81.500093] sd 60:0:0:0: [sdbi] Cache data unavailable
[   81.501401] sd 60:0:0:0: [sdbi] Assuming drive cache: write through
[   81.503056] sd 60:0:0:0: Attached scsi generic sg2 type 0
[   81.505090] sd 60:0:0:0: [sdbi] Cache data unavailable
[   81.506367] sd 60:0:0:0: [sdbi] Assuming drive cache: write through
[   81.508114]  sdbi: unknown partition table
[   81.509514] sd 60:0:0:0: [sdbi] Cache data unavailable
[   81.510908] sd 60:0:0:0: [sdbi] Assuming drive cache: write through
[   81.512985] sd 60:0:0:0: [sdbi] Attached SCSI disk

 

Still the disk though is not available in DSM, maybe i need something else as well.

 

Also what is your PCI ID ?

  

[   57.891796] mpt2sas version 14.100.00.00 loaded
[   57.892719] scsi34 : Fusion MPT SAS Host
[   57.894012] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (4022256 kB)
[   57.895558] mpt2sas 0000:0b:00.0: irq 75 for MSI/MSI-X
[   57.898843] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 75
[   57.899717] mpt2sas0: iomem(0x00000000fd3fc000), mapped(0xffffc9000b3d8000), size(16384)
[   57.901089] mpt2sas0: ioport(0x0000000000005000), size(256)
[   58.018301] mpt2sas0: Allocated physical memory: size(7418 kB)
[   58.019331] mpt2sas0: Current Controller Queue Depth(3307), Max Controller Queue Depth(3432)
[   58.020756] mpt2sas0: Scatter Gather Elements per IO(128)
[   58.080252] mpt2sas0: LSISAS2008: FWVersion(20.00.07.00), ChipRevision(0x03), BiosVersion(07.39.02.00)
[   58.081769] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
[   58.083909] mpt2sas0: sending port enable !!
[   58.087429] mpt2sas0: host_add: handle(0x0001), sas_addr(0x5003005703dbf193), phys(8)
[   58.095629] mpt2sas0: port enable: SUCCESS
[   58.098972] scsi 34:0:0:0: Direct-Access     Samsung  SSD 850 EVO 250GB        XXXX PQ: 0 ANSI: 6
[   58.100476] scsi 34:0:0:0: SATA: handle(0x0009), sas_addr(0x4433221103000000), phy(3), device_name(0x5002538d40XXXXXX)
[   58.102172] scsi 34:0:0:0: SATA: enclosure_logical_id(0x5003005703dbf193), slot(0)
[   58.103519] scsi 34:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[   58.104905] scsi 34:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[   58.106366] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim
[   58.107560] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications
[   58.108835] <redpill/native_sata_boot_shim.c:153> Found new SCSI disk vendor="Samsung SSD 850         XXXXXXXXXXXXX     " model="SSD 850 EVO 250GB       ": checking boot shim viability
[   58.111623] <redpill/boot_shim_base.c:29> scsi_is_boot_dev_target: it's not a SATA disk, ignoring
[   58.113080] <redpill/scsi_notifier.c:87> Calling original sd_probe()
[   58.114168] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0
[   58.115789] sd 34:0:0:0: Attached scsi generic sg3 type 0
[   58.116879] sd 34:0:0:0: [sdai] 488397168 512-byte logical blocks: (250 GB/232 GiB)
[   58.120201] sd 34:0:0:0: [sdai] Write Protect is off
[   58.121055] sd 34:0:0:0: [sdai] Mode Sense: 7f 00 10 08
[   58.122243] sd 34:0:0:0: [sdai] Write cache: enabled, read cache: enabled, supports DPO and FUA
[   58.128010]  sdai: sdai1 sdai2 sdai3
[   58.131220] sd 34:0:0:0: [sdai] Attached SCSI disk

 

  

root@Xpen_70:/lib/modules# fdisk -l

Disk /dev/sdai: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk model: SSD 850 EVO 250GB       
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: BA8B3786-95CC-4D3D-8CAA-080962FC10AA

Device       Start       End   Sectors   Size Type
/dev/sdai1      34      2047      2014  1007K BIOS boot
/dev/sdai2    2048   1050623   1048576   512M EFI System
/dev/sdai3 1050624 488397134 487346511 232.4G Linux LVM

 

from /var/log/messages 

2021-09-29T12:37:50+01:00 Xpen_70 synostorage[13417]: synostorage_int_disk.c:434 Disk [sdai] info cache generated
2021-09-29T12:37:51+01:00 Xpen_70 hotplugd[8500]: hotplugd.c:1211 ##### ACTION:add
2021-09-29T12:37:51+01:00 Xpen_70 hotplugd[8500]: DEVNAME:sdai
2021-09-29T12:37:51+01:00 Xpen_70 hotplugd[8500]: DEVGUID:XXXXXXXXX     0
2021-09-29T12:37:51+01:00 Xpen_70 hotplugd[8500]: DEVPATH:sdai
2021-09-29T12:37:51+01:00 Xpen_70 hotplugd[8500]: SUBSYSTEM:block
2021-09-29T12:37:51+01:00 Xpen_70 hotplugd[8500]: PHYSDEVPATH:/devices/pci0000:00/0000:00:16.0/0000:0b:00.0/host34/port-34:0/end_device-34:0/target34:0:0/34:0:0:0
2021-09-29T12:37:51+01:00 Xpen_70 hotplugd[8500]: hotplugd.c:1367 ==== SATA disk [sdai] hotswap [add] ====
2021-09-29T12:37:51+01:00 Xpen_70 hotplugd[8500]: disk/disk_is_mv_soc_driver.c:71 Can't get sata chip name from pattern /sys/block/sdai/device/../../scsi_host/host*/proc_name
2021-09-29T12:37:51+01:00 Xpen_70 hotplugd[8500]: disk/disk_config_single.c:122 apply /usr/syno/bin/DiskApmSet.sh 255  /dev/sdai 1>/dev/null 2>&1
2021-09-29T12:37:51+01:00 Xpen_70 hotplugd[8500]: disk/disk_config_single.c:122 apply /usr/syno/bin/syno_disk_ctl --ncq-on  /dev/sdai 1>/dev/null 2>&1
2021-09-29T12:37:51+01:00 Xpen_70 syno_disk_ctl[13517]: disk/disk_is_mv1475_driver.c:71 Can't get sata chip name from pattern /sys/block/sdai/device/../../scsi_host/host*/proc_name
2021-09-29T12:37:51+01:00 Xpen_70 hotplugd[8500]: hotplugd.c:1403 ==== SATA disk [sdai] Model: [SSD 850 EVO 250GB] ====
2021-09-29T12:37:51+01:00 Xpen_70 hotplugd[8500]: hotplugd.c:1404 ==== SATA disk [sdai] Serial number: [XXXXXXXXXX] ====
2021-09-29T12:37:51+01:00 Xpen_70 hotplugd[8500]: hotplugd.c:1405 ==== SATA disk [sdai] Firmware version: [XXXXXXX] ====

 

image.thumb.png.cafd44edb11ed7aef3effa7a9973268f.png

 

OMG !!!

 

image.thumb.png.7af49df94a1a3ad23b6169372da66504.png

Edited by Orphée
  • Like 2
Link to comment
Share on other sites
pocopico Guru Master

pocopico

Posted
Posted

Yeah ! I've tested it and it works for my baremetal Gen7 with LSISAS1068E loading MPTSAS.ko as well :

  

[ 1845.535722] mptsas: ioc0: attaching sata device: fw_channel 0, fw_id 0, phy 0, sas_addr 0x1d225
[ 1845.548867] scsi 5:0:0:0: Direct-Access     ATA      HTE7275          A170 PQ: 0 ANSI: 5
[ 1845.551109] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim
[ 1845.551402] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications
[ 1845.551707] <redpill/scsi_notifier.c:87> Calling original sd_probe()
[ 1845.552027] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0
[ 1845.552792] sd 5:0:0:0: Attached scsi generic sg2 type 0
[ 1845.553461] sd 5:0:0:0: [sdf] 488397168 512-byte logical blocks: (250 GB/232 GiB)
[ 1845.565267] sd 5:0:0:0: [sdf] Write Protect is off
[ 1845.565465] sd 5:0:0:0: [sdf] Mode Sense: 73 00 00 08
[ 1845.570430] sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1845.620149]  sdf: sdf1 sdf2
[ 1845.641743] sd 5:0:0:0: [sdf] Attached SCSI disk


image.thumb.png.985ba96f589be3a2fd3eb559781152b5.png

 

  • Like 2
  • Thanks 1
Link to comment
Share on other sites
WiteWulf Super Member

WiteWulf

Posted
Posted
1 hour ago, Kaneske said:

Since it seems to be „quite“ stable and also usable by many, and it’s already on 7.01 on the Syno Side…

 

…is there a way to post a to-do by step, or a summary, what and when to act for getting this incredible cool new loader done?

 

It seems hard for me to get things together.

 

https://github.com/RedPill-TTG/redpill-load

 

image.thumb.png.055c24e26dd2977f83d059abc3bb6933.png

  • Like 1
Link to comment
Share on other sites
stefauresi Advanced Member

stefauresi

Posted
Posted

Hi,

 

The intel x520-DA2 is already include in Redpill loader ?

I try inject ixgbe in https://github.com/pocopico/4.4.180plus-modules

  

[  266.390932] ixgbe: Unknown symbol dca_remove_requester (err 0)
[  266.391522] ixgbe: Unknown symbol dca_add_requester (err 0)
[  266.392063] ixgbe: Unknown symbol SynoSfpUnsupportNotifySet (err 0)
[  266.392683] ixgbe: Unknown symbol dca_unregister_notify (err 0)
[  266.393249] ixgbe: Unknown symbol dca_register_notify (err 0)
[  266.393802] ixgbe: Unknown symbol dcb_getapp (err 0)
[  266.394285] ixgbe: Unknown symbol dcb_setapp (err 0)
[  266.394763] ixgbe: Unknown symbol dca3_get_tag (err 0)
[  266.395278] ixgbe: Unknown symbol dcb_ieee_delapp (err 0)
[  266.395798] ixgbe: Unknown symbol dcb_ieee_setapp (err 0)
[  270.794070] ixgbe: Unknown symbol dca_remove_requester (err 0)
[  270.794670] ixgbe: Unknown symbol dca_add_requester (err 0)
[  270.795214] ixgbe: Unknown symbol SynoSfpUnsupportNotifySet (err 0)
[  270.795833] ixgbe: Unknown symbol dca_unregister_notify (err 0)
[  270.796404] ixgbe: Unknown symbol dca_register_notify (err 0)
[  270.796964] ixgbe: Unknown symbol dcb_getapp (err 0)
[  270.797480] ixgbe: Unknown symbol dcb_setapp (err 0)
[  270.798068] ixgbe: Unknown symbol dca3_get_tag (err 0)
[  270.798600] ixgbe: Unknown symbol dcb_ieee_delapp (err 0)
[  270.799136] ixgbe: Unknown symbol dcb_ieee_setapp (err 0)

 

i have try to add 4 NIC but i see only 2 NIC (1Gb on motherboard) 

  

[    0.844793] <redpill/cmdline_delegate.c:393> Param #9: |mac1=001100000000|
[    0.846423] <redpill/cmdline_delegate.c:393> Param #10: |mac2=001100000000|
[    0.848136] <redpill/cmdline_delegate.c:393> Param #11: |mac3=001100000000|
[    0.849854] <redpill/cmdline_delegate.c:393> Param #12: |mac4=001100000000|

 

mac1&2 = real mac address (918+)

 

Best regards 

Link to comment
Share on other sites
Buny74 Newbie

Buny74

Posted
Posted (edited)

Hi guys,

 

I have successfully installed the 42214 and today the last one 42218 but i have a problem.

 

When i try to make a research in the config panel my server reboot. 

Does anyone have the same issue ? (I have docker with only pihole running and saw the reported issues related to docker)

 

Also for VMM on my Gen 8 in my config file i put my real mac adresse of my NC360T adapter but on LAN 1 it's not the right one in the settings. So VMM do not work.

 

Did i made a mistake when making my config file ?

 

Edited by Buny74
Link to comment
Share on other sites
WiteWulf Super Member

WiteWulf

Posted
Posted
48 minutes ago, Buny74 said:

Hi guys,

 

I have successfully installed the 42214 and today the last one 42218 but i have a problem.

 

When i try to make a research in the config panel my server reboot. 

Does anyone have the same issue ? (I have docker with only pihole running and saw the reported issues related to docker)

 

Also for VMM on my Gen 8 in my config file i put my real mac adresse of my NC360T adapter but on LAN 1 it's not the right one in the settings. So VMM do not work.

 

Did i made a mistake when making my config file ?

 

DS3615xs image is known to be unstable on some setups (https://github.com/RedPill-TTG/redpill-lkm/issues/21)

 

If you can capture the output of kernel panic from iLO’s vsp when it crashes it could be helpful. 

 

For the NC360T you need to declare both interfaces in your config json file, even if you’re only using one. If the MAC addresses are swapped around, just swap them

in your json file and rebuild. 

  • Like 1
Link to comment
Share on other sites
Buny74 Newbie

Buny74

Posted
Posted
il y a 11 minutes, WiteWulf a dit :

DS3615xs image is known to be unstable on some setups (https://github.com/RedPill-TTG/redpill-lkm/issues/21)

 

If you can capture the output of kernel panic from iLO’s vsp when it crashes it could be helpful. 

 

For the NC360T you need to declare both interfaces in your config json file, even if you’re only using one. If the MAC addresses are swapped around, just swap them

in your json file and rebuild. 

I will try to grab logs about the crash.

 

About the MAC adresses, i have only declared two of them for exemple at the end d8 and d9 but when booting on the system the second one is right (d9) but the first one become from d8 to 00

Link to comment
Share on other sites
seanone Junior Member

seanone

Posted
Posted
5 hours ago, RedwinX said:

Hey everyone ! 

 

My bad, my brother has update the baremetal DS918+ to 7.0.1-42218... Any bsp available to fix broken NAS? Or maybe a method to downgrade?

Thx in advance,

 

Red

 

I have downgraded syno version before.

 

Boot with other linux LiveCD, format the DSM disk partition 1 and 2 (two small partitions, they are syno system partitions, without personal data).

BE CAREFUL DO NOT format partition 3 (the biggest one, it's your data partition)!

After format, reboot from old redpill bootloader, you can do reinstall DSM without loss your data, but your system config will lost.

 

Backup/clone your disk data before if you can.

Link to comment
Share on other sites
WiteWulf Super Member

WiteWulf

Posted
Posted (edited)
13 hours ago, Buny74 said:

I will try to grab logs about the crash.

 

About the MAC adresses, i have only declared two of them for exemple at the end d8 and d9 but when booting on the system the second one is right (d9) but the first one become from d8 to 00

Yeah, I had this problem. I’d declared the interfaces in the wrong order in the config.json file. Swap them around and rebuild the image and it should work.

 

The top port on the NC360T is LAN1 in DSM and will be the MAC address ending in d8 for you, declare this as mac1 in the config.json. The lower port will be LAN2 and have the MAC address ending in d9, declare this as mac2 in the config.json. 

 

*edit*

 

Also, have you disabled the onboard NIC in the BIOS?

Edited by WiteWulf
Link to comment
Share on other sites
WiteWulf Super Member

WiteWulf

Posted
Posted

@ThorGroup hey guys, sorry to '@' you on this, I know you're busy people, but I wonder if you'd been able to look at the kernel panic problems on DS3615xs? My system is now stable, but only with no docker containers running and Plex Media Server stopped. Starting PMS or a docker container results in a kernel panic anywhere between a few seconds or two to three minutes later. I'm happy to carry out any testing you suggest and feedback diagnostic output.

  • Like 2
Link to comment
Share on other sites
robertoakira1 Newbie

robertoakira1

Posted
Posted (edited)
On 9/28/2021 at 5:23 AM, yanjun said:

Maybe I need to update some information. The latest situation is that the 918 I installed on the pve can perform face detection. The operation that needs to be noted is that when the pass-through core display (mine is UHD630), the parameter legacy-igd=1 needs to be added , So the complete parameter of the command line displayed by the pass-through core is hostpci0: 0000:00:02, legacy-igd=1,by the way,here is the full code: 



args: -device 'qemu-xhci,addr=0x18' -drive 'id=synoboot,file=/root/synoboot701fo.img,if=none,format=raw' -device 'usb-storage,id=synoboot,drive=synoboot,bootindex=0'
bios: ovmf
boot: order=sata0;ide2;net0
cores: 4
cpu: host
efidisk0: local-lvm:vm-101-disk-1,size=4M
hostpci0: 0000:00:02,legacy-igd=1
ide2: none,media=cdrom
memory: 12000
net0: e1000e=BE:0F:6F:02:39:48,bridge=vmbr0,firewall=1
net1: e1000e=F2:21:D3:30:E7:AE,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
sata0: local-lvm:vm-101-disk-0,size=32G
scsihw: virtio-scsi-pci
serial0: socket
smbios1: uuid=b33f1107-a6de-4bc1-848c-0e00dc7d0542
sockets: 2
vcpus: 8
vga: none
vmgenid: fca33db9-1087-446b-9a57-e1424171250e

after this operation, it works.

 

Hi @yanjun

 

How did you boot xpenology using ovmf bios? I can boot only when I set to SeaBios.

 

Thank you

Edited by robertoakira1
Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...