TinyCore RedPill Loader (TCRP)

[alex.god007]

1 hour ago, flyride said:

 

Did you build the loader again after making the user_config.json change?  Anything in user_config.json will override what is in synoinfo.conf

Nope, I just changed the config and rebooted. Should I use standard ./rploader.sh build syntax to update loader?

[flyride]

1 minute ago, alex.god007 said:

Nope, I just changed the config and rebooted. Should I use standard ./rploader.sh build syntax to update loader?

 

Yes, any changes to user_config.json require a rebuild of the loader to take effect.

[Deniska]

11 час назад, pocopico сказал:

@Deniska I did an update on the r8125 extension. I recompiled from latest available realtek sources 9.009.04. 

@pocopico thank you. 

 

Work and home tasks cover me... 

 

I've created loader from scratch and it was not work properly with your extension.

But i've tested with @dolbycat version extension of r8125 and it helped me. I can check it again with your extension if you want. I have a few usb flashes.

ACPI extension from Dolbycat have been installed without any mistakes. 

 

And main news - r8125 extension work!

I see DSM with one my hdd and installed it!

 

 

Thank you very much guys!🤝

 

Now i'm looking for how to install second update for 42661 and adding NVME and second HDD disks. 

And interesting why DSM see my system with AMD CPU with only 4 cores. 

 

 

 

[sam juan]

./rploader.sh update now

./rploader.sh fullupgrade now

./rploader.sh backup

./rploader.sh postupdate <platform>

for the above steps, is there a way to do this without attaching keyboard/mouse/monitor to the box?
thanks.

[pocopico]

48 minutes ago, Deniska said:

@pocopico thank you. 

 

Work and home tasks cover me... 

 

I've created loader from scratch and it was not work properly with your extension.

But i've tested with @dolbycat version extension of r8125 and it helped me. I can check it again with your extension if you want. I have a few usb flashes.

ACPI extension from Dolbycat have been installed without any mistakes. 

 

And main news - r8125 extension work!

I see DSM with one my hdd and installed it!

 

 

Thank you very much guys!🤝

 

Now i'm looking for how to install second update for 42661 and adding NVME and second HDD disks. 

And interesting why DSM see my system with AMD CPU with only 4 cores. 

 

 

 

the cpu is cosmetic, DSM thinks it is running on Ds1621 

[pocopico]

1 hour ago, Deniska said:

@pocopico thank you. 

 

Work and home tasks cover me... 

 

I've created loader from scratch and it was not work properly with your extension.

But i've tested with @dolbycat version extension of r8125 and it helped me. I can check it again with your extension if you want. I have a few usb flashes.

ACPI extension from Dolbycat have been installed without any mistakes. 

 

And main news - r8125 extension work!

I see DSM with one my hdd and installed it!

 

 

Thank you very much guys!🤝

 

Now i'm looking for how to install second update for 42661 and adding NVME and second HDD disks. 

And interesting why DSM see my system with AMD CPU with only 4 cores. 

 

 

 

Since I don’t have the hardware, it will be nice to know it the extension works or not 

[blamaster]

I used tinycore to install DS3622xs+ with DSM 7.1-42661 Update 1 on my N54L hardware.

The install process worked without issues 🙂

 

On my prvious DSM 6 install i succesfully used zigbee usb dongles with homeassistant.

I tried two different dongles with different driver chips (FTDI and CP210x) on the new DSM 7.1 install.

 

For the FTDI based dongle the drivers are already included in the stock kernel so i just loaded them as previously done with DSM6:

 

sudo insmod /lib/modules/usbserial.ko
sudo insmod /lib/modules/ftdi_sio.ko

 

Unfortunately both tested usb dongles are not detected by the system.

 

The "dmesg" command shows no log output if the dongles are plugged in. (Not a single line related to the USB dongle, seems like no events are created)

If i plug a USB drive in the same USB port the drive i loaded and available in DSM so the USB hub and port seem to work fine in general. 

 

Here is the output of "dmesg | grep usb" after the usb dongle was replugged several times:

 

[    2.265247] <redpill/usb_boot_shim.c:229> Registering USB boot device shim
[    2.265487] <redpill/usb_boot_shim.c:194> Registered usbcore module notifier
[    2.269655] <redpill/usb_boot_shim.c:247> Successfully registered USB boot device shim
[   13.933321] usbcore: registered new interface driver usbfs
[   13.933528] usbcore: registered new interface driver hub
[   13.933736] usbcore: registered new interface driver ethub
[   13.933943] usbcore: registered new device driver usb
[   13.934137] <redpill/usb_boot_shim.c:166> usbcore registered, adding device watcher
[   13.934405] <redpill/call_protected.c:112> Got ptr ffffffffa00d7db0 for usb_register_notify
[   13.934698] <redpill/usb_boot_shim.c:127> Registered USB device notifier
[   13.972036] <redpill/usb_boot_shim.c:75> Found new device <vid=xxxx, pid=xxxx> - didn't match expected <vid=xxxx, pid=xxxx> (prev_shimmed=0)
[   13.979871] <redpill/usb_boot_shim.c:75> Found new device <vid=xxxx, pid=xxxx> - didn't match expected <vid=xxxx, pid=xxxx> (prev_shimmed=0)
[   13.988036] <redpill/usb_boot_shim.c:75> Found new device <vid=xxxx, pid=xxxx> - didn't match expected <vid=xxxx, pid=xxxx> (prev_shimmed=0)
[   14.044782] usbcore: registered new interface driver usb-storage
[   14.302061] usb 2-3: new high-speed USB device number 2 using ehci-pci
[   14.440089] usb-storage 2-3:1.0: USB Mass Storage device detected
[   14.442075] scsi host6: usb-storage 2-3:1.0
[   14.442352] <redpill/usb_boot_shim.c:91> Device <vid=xxxx, pid=xxxx> shimmed to <vid=xxxx, pid=xxxx>
[   16.494373] <redpill/bios_shim.c:215> Symbol #59 in mfgBIOS "broadwellnk_synobios" {syno_usb_prohibit_event}<ffffffffa018a470>
[   25.413853] systemd[1]: Starting Mount usb fs...
[   25.914175] usbcore: registered new interface driver usblp
[   25.931881] usbcore: registered new interface driver usbhid
[   25.932107] usbhid: USB HID core driver
[   25.973474] <redpill/bios_shim.c:215> Symbol #59 in mfgBIOS "broadwellnk_synobios" {syno_usb_prohibit_event}<ffffffffa0b59470>
[   48.955098] usbcore: registered new interface driver usbserial
[   48.998396] usbcore: registered new interface driver ftdi_sio
[   48.998620] usbserial: USB Serial support registered for FTDI USB Serial Device

 

The "lsusb" command also only shows connected USB drives. The zigbee dongles dont show up in the lsusb output:

 

|__usb1          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (ehci_hcd 0000:00:12.2) hub
|__usb2          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (ehci_hcd 0000:00:13.2) hub
  |__2-3         f400:f400:0200 00  2.00  480MBit/s 100mA 1IF  (USB Disk 2.0 HEADER1397438310856)
|__usb3          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (ehci_hcd 0000:00:16.2) hub

 

Is this related to the redpill loader ?

[blamaster]

I used tinycore to install DS3622xs+ with DSM 7.1-42661 Update 1 on my N54L hardware.

The install process worked without issues 🙂

 

On my prvious DSM 6 install i succesfully used zigbee usb dongles with homeassistant.

I tried two different dongles with different driver chips (FTDI and CP210x) on the new DSM 7.1 install.

 

For the FTDI based dongle the drivers are already included in the stock kernel so i just loaded them as previously done with DSM6:

 

sudo insmod /lib/modules/usbserial.ko
sudo insmod /lib/modules/ftdi_sio.ko

 

Unfortunately both tested usb dongles are not detected by the system.

 

The "dmesg" command shows no log output if the dongles are plugged in. (Not a single line related to the USB dongle, seems like no events are created)

If i plug a USB drive in the same USB port the drive i loaded and available in DSM so the USB hub and port seem to work fine in general. 

 

Here is the output of "dmesg | grep usb" after the usb dongle was replugged several times:

 

[    2.265247] <redpill/usb_boot_shim.c:229> Registering USB boot device shim
[    2.265487] <redpill/usb_boot_shim.c:194> Registered usbcore module notifier
[    2.269655] <redpill/usb_boot_shim.c:247> Successfully registered USB boot device shim
[   13.933321] usbcore: registered new interface driver usbfs
[   13.933528] usbcore: registered new interface driver hub
[   13.933736] usbcore: registered new interface driver ethub
[   13.933943] usbcore: registered new device driver usb
[   13.934137] <redpill/usb_boot_shim.c:166> usbcore registered, adding device watcher
[   13.934405] <redpill/call_protected.c:112> Got ptr ffffffffa00d7db0 for usb_register_notify
[   13.934698] <redpill/usb_boot_shim.c:127> Registered USB device notifier
[   13.972036] <redpill/usb_boot_shim.c:75> Found new device <vid=xxxx, pid=xxxx> - didn't match expected <vid=xxxx, pid=xxxx> (prev_shimmed=0)
[   13.979871] <redpill/usb_boot_shim.c:75> Found new device <vid=xxxx, pid=xxxx> - didn't match expected <vid=xxxx, pid=xxxx> (prev_shimmed=0)
[   13.988036] <redpill/usb_boot_shim.c:75> Found new device <vid=xxxx, pid=xxxx> - didn't match expected <vid=xxxx, pid=xxxx> (prev_shimmed=0)
[   14.044782] usbcore: registered new interface driver usb-storage
[   14.302061] usb 2-3: new high-speed USB device number 2 using ehci-pci
[   14.440089] usb-storage 2-3:1.0: USB Mass Storage device detected
[   14.442075] scsi host6: usb-storage 2-3:1.0
[   14.442352] <redpill/usb_boot_shim.c:91> Device <vid=xxxx, pid=xxxx> shimmed to <vid=xxxx, pid=xxxx>
[   16.494373] <redpill/bios_shim.c:215> Symbol #59 in mfgBIOS "broadwellnk_synobios" {syno_usb_prohibit_event}<ffffffffa018a470>
[   25.413853] systemd[1]: Starting Mount usb fs...
[   25.914175] usbcore: registered new interface driver usblp
[   25.931881] usbcore: registered new interface driver usbhid
[   25.932107] usbhid: USB HID core driver
[   25.973474] <redpill/bios_shim.c:215> Symbol #59 in mfgBIOS "broadwellnk_synobios" {syno_usb_prohibit_event}<ffffffffa0b59470>
[   48.955098] usbcore: registered new interface driver usbserial
[   48.998396] usbcore: registered new interface driver ftdi_sio
[   48.998620] usbserial: USB Serial support registered for FTDI USB Serial Device

 

The "lsusb" command also only shows connected USB drives. The zigbee dongles dont show up in the lsusb output:

 

|__usb1          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (ehci_hcd 0000:00:12.2) hub
|__usb2          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (ehci_hcd 0000:00:13.2) hub
  |__2-3         f400:f400:0200 00  2.00  480MBit/s 100mA 1IF  (USB Disk 2.0 HEADER1397438310856)
|__usb3          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (ehci_hcd 0000:00:16.2) hub

 

Is this related to the redpill loader ?

[flyride]

44 minutes ago, blamaster said:

Is this related to the redpill loader ?

 

More likely to be this:

https://macandegg.com/2021/06/synology-dsm-7-0-ends-support-for-usb-devices/#:~:text=DSM 7.0%3A No more USB sticks&text=First%2C the support for external,LTE sticks%2C Bluetooth dongles anymore.

[techhit]

6 hours ago, flyride said:

 

As you can see the PCI ids of the controllers that are reported by satamap are different than the error.  The red highlighting is yours.

My understanding is that this particular controller is part of the RedPill model and no extension is required. You might have missed that notice on your previous build.

 

I think you are okay to proceed.  However, if you use the full test procedure as outlined in the tutorial, however, your risk would be minimal.

 

EDIT: Are you saying you have a third controller?  The 1b21.0612 is the second on-board controller, which has TCRP support.  Did you build with the manual argument?  If so, omit "manual" and see if you get a different result.

 

If you really have a third controller and it is an HBA, it may not behave as an AHCI SATA controller.  If that is the case, it is treated as a SCSI controller which is unaffected by sataportmap/diskidxmap.  There is a pending update for rploader.sh which will confirm the status of HBAs in satamap because that question is a common one.

 

 

Hi. 1b21.0612 Is my pcie sata controller card (si3132).  I built it using the auto method. I saw your follow up reply saying the driver hasn't been compiled for TCRP so I will hold off on the upgrade. Thanks for your input

[Deniska]

1 час назад, Deniska сказал:

@pocopico thank you. 

 

Work and home tasks cover me... 

 

I've created loader from scratch and it was not work properly with your extension.

But i've tested with @dolbycat version extension of r8125 and it helped me. I can check it again with your extension if you want. I have a few usb flashes.

ACPI extension from Dolbycat have been installed without any mistakes. 

 

And main news - r8125 extension work!

I see DSM with one my hdd and installed it!

 

 

Thank you very much guys!🤝

 

Now i'm looking for how to install second update for 42661 and adding NVME and second HDD disks. 

And interesting why DSM see my system with AMD CPU with only 4 cores. 

 

 

 

 

About adding new HDD with DTS on DS1621+.

I can add second HDD after rebuild Loader by "./rploader.sh build v1000-7.1.0-42661 manual"  

How i understand i must rebuild loader if i add new hdd. Is it correct?

 

 

I've seen what NVME disk was found but DSM doesn't show it:

There is part of loader's log:

Found 2 disks and 5 nvme
Collecting disk paths
Found local disk sda with path 00:17.0, adding into internal_slot 1 with portnumber 2
Found local disk sdb with path 00:17.0, adding into internal_slot 2 with portnumber 3
Collecting nvme paths
Found local nvme nvme0n1 with path 00:1d.0,00.0, adding into m2_card 1
device node not found
Found local nvme |-nvme0n1p1 with path , adding into m2_card 4
device node not found
Found local nvme |-nvme0n1p2 with path , adding into m2_card 4
device node not found
Found local nvme |-nvme0n1p3 with path , adding into m2_card 4
device node not found
Found local nvme `-nvme0n1p4 with path , adding into m2_card 4
Patching USB to include your loader. Loader found in 1-3 port
Converting dts file : ds1621p.dts to dtb file : >ds1621p.dtb
Copying patched dtb file ds1621p.dtb to /home/tc/redpill-load/custom/extensions/redpill-dtb-static/ds1621p_42661/model_ds1621p.dtb -> OK ! File copied and verified !
 

❓ Could you help with NVME disk? Where can i find it in DSM (I hasn't experience about it in DSM, maybe i can't find some option)? 

 I can't find any notes about NVME in DSM.

But what i see in terminal:

$ sudo lspci -nnq

00:00.0 Host bridge [0600]: Intel Corporation Comet Lake-S 6c Host Bridge/DRAM Controller [8086:9b53] (rev 03)
00:02.0 VGA compatible controller [0300]: Intel Corporation CometLake-S GT2 [UHD Graphics 630] [8086:9bc8] (rev 03)
00:14.0 USB controller [0c03]: Intel Corporation Tiger Lake-H USB 3.2 Gen 2x1 xHCI Host Controller [8086:43ed] (rev 11)
00:14.2 RAM memory [0500]: Intel Corporation Tiger Lake-H Shared SRAM [8086:43ef] (rev 11)
00:16.0 Communication controller [0780]: Intel Corporation Tiger Lake-H Management Engine Interface [8086:43e0] (rev 11)
00:17.0 SATA controller [0106]: Intel Corporation Device [8086:43d2] (rev 11)
00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:43bd] (rev 11)
00:1c.6 PCI bridge [0604]: Intel Corporation Device [8086:43be] (rev 11)
00:1d.0 PCI bridge [0604]: Intel Corporation Tiger Lake-H PCI Express Root Port #9 [8086:43b0] (rev 11)
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:4386] (rev 11)
00:1f.3 Audio device [0403]: Intel Corporation Device [8086:f0c8] (rev 11)
00:1f.4 SMBus [0c05]: Intel Corporation Tiger Lake-H SMBus Controller [8086:43a3] (rev 11)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-H SPI Controller [8086:43a4] (rev 11)
00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (14) I219-V [8086:15fa] (rev 11)
01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller [10ec:8125] (rev 05)
02:00.0 Network controller [0280]: Intel Corporation Dual Band Wireless-AC 3168NGW [Stone Peak] [8086:24fb] (rev 10)
03:00.0 Non-Volatile memory controller [0108]: Kingston Technology Company, Inc. A2000 NVMe SSD [2646:2263] (rev 03)

$ lspci -v

Скрытый текст

 

00:00.0 Class 0600: Device 8086:9b53 (rev 03)
        Subsystem: Device 1849:9b53
        Flags: bus master, fast devsel, latency 0
        Capabilities: <access denied>

00:02.0 Class 0300: Device 8086:9bc8 (rev 03)
        Subsystem: Device 1849:9bc8
        Flags: bus master, fast devsel, latency 0, IRQ 255
        [virtual] Memory at 6000000000 (64-bit, non-prefetchable) [size=16M]
        [virtual] Memory at 4000000000 (64-bit, prefetchable) [size=256M]
        I/O ports at 4000 [size=64]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: <access denied>

00:14.0 Class 0c03: Device 8086:43ed (rev 11) (prog-if 30)
        Subsystem: Device 1849:43ed
        Flags: bus master, medium devsel, latency 0, IRQ 139
        Memory at 6001100000 (64-bit, non-prefetchable) [size=64K]
        Capabilities: <access denied>
        Kernel driver in use: xhci_hcd

00:14.2 Class 0500: Device 8086:43ef (rev 11)
        Flags: fast devsel
        Memory at 6001114000 (64-bit, non-prefetchable) [disabled] [size=16K]
        Memory at 600111a000 (64-bit, non-prefetchable) [disabled] [size=4K]
        Capabilities: <access denied>

00:16.0 Class 0780: Device 8086:43e0 (rev 11)
        Subsystem: Device 1849:43e0
        Flags: fast devsel, IRQ 255
        Memory at 6001119000 (64-bit, non-prefetchable) [disabled] [size=4K]
        Capabilities: <access denied>

00:17.0 Class 0106: Device 8086:43d2 (rev 11) (prog-if 01)
        Subsystem: Device 1849:43d2
        Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 127
        Memory at 9fb20000 (32-bit, non-prefetchable) [size=8K]
        Memory at 9fb23000 (32-bit, non-prefetchable) [size=256]
        I/O ports at 4090 [size=8]
        I/O ports at 4080 [size=4]
        I/O ports at 4060 [size=32]
        Memory at 9fb22000 (32-bit, non-prefetchable) [size=2K]
        Capabilities: <access denied>
        Kernel driver in use: ahci

00:1c.0 Class 0604: Device 8086:43bd (rev 11)
        Flags: bus master, fast devsel, latency 0, IRQ 123
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        I/O behind bridge: 00003000-00003fff [size=4K]
        Memory behind bridge: 9fa00000-9fafffff [size=1M]
        Prefetchable memory behind bridge: None
        Capabilities: <access denied>
        Kernel driver in use: pcieport

00:1c.6 Class 0604: Device 8086:43be (rev 11)
        Flags: bus master, fast devsel, latency 0, IRQ 124
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
        I/O behind bridge: None
        Memory behind bridge: 9f900000-9f9fffff [size=1M]
        Prefetchable memory behind bridge: None
        Capabilities: <access denied>
        Kernel driver in use: pcieport

00:1d.0 Class 0604: Device 8086:43b0 (rev 11)
        Flags: bus master, fast devsel, latency 0, IRQ 125
        Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
        I/O behind bridge: None
        Memory behind bridge: 9f800000-9f8fffff [size=1M]
        Prefetchable memory behind bridge: None
        Capabilities: <access denied>
        Kernel driver in use: pcieport

00:1f.0 Class 0601: Device 8086:4386 (rev 11)
        Subsystem: Device 1849:4386
        Flags: bus master, fast devsel, latency 0

00:1f.3 Class 0403: Device 8086:f0c8 (rev 11)
        Subsystem: Device 1849:1897
        Flags: fast devsel, IRQ 255
        Memory at 6001110000 (64-bit, non-prefetchable) [disabled] [size=16K]
        Memory at 6001000000 (64-bit, non-prefetchable) [disabled] [size=1M]
        Capabilities: <access denied>

00:1f.4 Class 0c05: Device 8086:43a3 (rev 11)
        Subsystem: Device 1849:43a3
        Flags: medium devsel, IRQ 255
        Memory at 6001118000 (64-bit, non-prefetchable) [size=256]
        I/O ports at efa0 [size=32]

00:1f.5 Class 0c80: Device 8086:43a4 (rev 11)
        Subsystem: Device 1849:43a4
        Flags: fast devsel
        Memory at 9fb24000 (32-bit, non-prefetchable) [size=4K]

00:1f.6 Class 0200: Device 8086:15fa (rev 11)
        Subsystem: Device 1849:15fa
        Flags: fast devsel, IRQ 16
        Memory at 9fb00000 (32-bit, non-prefetchable) [size=128K]
        Capabilities: <access denied>

01:00.0 Class 0200: Device 10ec:8125 (rev 05)
        Subsystem: Device 1849:8125
        Flags: bus master, fast devsel, latency 0, IRQ 140
        I/O ports at 3000 [size=256]
        Memory at 9fa00000 (64-bit, non-prefetchable) [size=64K]
        Memory at 9fa10000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: r8125

02:00.0 Class 0280: Device 8086:24fb (rev 10)
        Subsystem: Device 8086:2110
        Flags: fast devsel, IRQ 255
        Memory at 9f900000 (64-bit, non-prefetchable) [disabled] [size=8K]
        Capabilities: <access denied>

03:00.0 Class 0108: Device 2646:2263 (rev 03) (prog-if 02)
        Subsystem: Device 2646:2263
        Flags: bus master, fast devsel, latency 0, IRQ 16
        Memory at 9f800000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: nvme

 

ls /sys/block/
dm-0  dm-2  dm-4  loop0  loop2  loop4  loop6  md0  md2  nvme0n1  ram1   ram11  ram13  ram15  ram3  ram5  ram7  ram9   sata2     zram0  zram2  zram4
dm-1  dm-3  dm-5  loop1  loop3  loop5  loop7  md1  md3  ram0     ram10  ram12  ram14  ram2   ram4  ram6  ram8  sata1  synoboot  zram1  zram3  zram5
 

 

 

About update to 42661 update 2.

I did manual update via pat file. 
After reboot, run Tynicore loader and do "./rploader.sh postupdate v1000-7.1.0-42661".

It works!

 

 

About version CPU.

Will DSM use only 4 cores instead of 6? 

 

Thank you!

 

 

[flyride]

8 minutes ago, Deniska said:

I can add second HDD after rebuild Loader by "./rploader.sh build v1000-7.1.0-42661 manual"  

How i understand i must rebuild loader if i add new hdd. Is it correct?

With TCRP and DS1621+, if adding more drives to ports that have not yet been used, the loader will need to be rebuilt.

 

8 minutes ago, Deniska said:

Could you help with NVME disk? Where can i find it in DSM (I hasn't experience about it in DSM, maybe i can't find some option)? 

 I can't find any notes about NVME in DSM.

DSM only supports NVMe as cache.  In Storage Manager, if you can see the NVMe device, it is working.

 

 

8 minutes ago, Deniska said:

Will DSM use only 4 cores instead of 6? 

DS1621+ supports up to 16 threads (8 cores + 8 hyperthreads, or 16 cores).

[Deniska]

8 минут назад, flyride сказал:

With TCRP and DS1621+, if adding more drives to ports that have not yet been used, the loader will need to be rebuilt.

 

DSM only supports NVMe as cache.  In Storage Manager, if you can see the NVMe device, it is working.

 

 

DS1621+ supports up to 16 threads (8 cores + 8 hyperthreads, or 16 cores).

Flyride thank you for quick answer.

 

I don't see NVME in Storage manager:(

I hope in future we can use NVME as ordinary disk. I like silent:). Maybe we can use some patch for it?

But first task - to see NVME disk in DSM. Do you have any ideas?

 

 

"DS1621+ supports up to 16 threads (8 cores + 8 hyperthreads, or 16 cores)."

Yes, and ,y CPU has 6 cores and 12 threads. I hope i can use all of them on DSM.

 

[flyride]

10 minutes ago, Deniska said:

But first task - to see NVME disk in DSM. Do you have any ideas?

 

There are different methods of making NVMe functional depending on the platform.  I doubt all combinations have been tested so you may need to experiment.

 

On DS918+, lib file needs to be patched.

On DS3622xs+, there is a configuration file for the NVMe PCIe addresses

DS3617xs is probably like DS3622xs+

DVA3221 method is not known, although I saw a post saying no lib file so it may be configuration file like DS3622xs+

 

On DS920+ and DS1621+, NVMe is supposed to be configured with Device Tree.

If the Device Tree patchdtc script that is part of the loader build gets it wrong, DSM may not find it.  Underlying Linux will probably see it, but DSM will not.

 

This command reports detailed information about the NVMe PCIe address: udevadm info /dev/nvme0n1

 

You should review the Device Tree configuration and see if it is consistent with what is returned by udevadm.

https://xpenology.com/forum/topic/62894-only-hdd-in-bay-1-are-found-by-storage-manager/#comment-285068

 

If necessary, you can edit the Device Tree manually but it is not fun:

https://xpenology.com/forum/topic/62894-only-hdd-in-bay-1-are-found-by-storage-manager/?do=findComment&comment=285075

 

You could try the lib file and configuration file methods, although I doubt they will work for DS1621+

[Deniska]

26 минут назад, flyride сказал:

 

There are different methods of making NVMe functional depending on the platform.  I doubt all combinations have been tested so you may need to experiment.

 

On DS918+, lib file needs to be patched.

On DS3622xs+, there is a configuration file for the NVMe PCIe addresses

DS3617xs is probably like DS3622xs+

DVA3221 method is not known, although I saw a post saying no lib file so it may be configuration file like DS3622xs+

 

On DS920+ and DS1621+, NVMe is supposed to be configured with Device Tree.

If the Device Tree patchdtc script that is part of the loader build gets it wrong, DSM may not find it.  Underlying Linux will probably see it, but DSM will not.

 

This command reports detailed information about the NVMe PCIe address: udevadm info /dev/nvme0n1

 

You should review the Device Tree configuration and see if it is consistent with what is returned by udevadm.

https://xpenology.com/forum/topic/62894-only-hdd-in-bay-1-are-found-by-storage-manager/#comment-285068

 

If necessary, you can edit the Device Tree manually but it is not fun:

https://xpenology.com/forum/topic/62894-only-hdd-in-bay-1-are-found-by-storage-manager/?do=findComment&comment=285075

 

You could try the lib file and configuration file methods, although I doubt they will work for DS1621+

Fryride thank you!

I will check different ways and come back.

 

I've got detail infromation about the NVMe PCIe address and will check.

$ udevadm info /dev/nvme0n1
P: /devices/pci0000:00/0000:00:1d.0/0000:03:00.0/nvme/nvme0/nvme0n1
N: nvme0n1
E: DEVNAME=/dev/nvme0n1
E: DEVPATH=/devices/pci0000:00/0000:00:1d.0/0000:03:00.0/nvme/nvme0/nvme0n1
E: DEVTYPE=disk
E: MAJOR=259
E: MINOR=0
E: PHYSDEVBUS=pci
E: PHYSDEVDRIVER=nvme
E: PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.0/0000:03:00.0
E: SUBSYSTEM=block
E: SYNO_ATTR_SERIAL=50026B76846391BD
E: SYNO_DEV_DISKPORTTYPE=UNKNOWN
E: SYNO_INFO_PLATFORM_NAME=v1000
E: SYNO_KERNEL_VERSION=4.4
E: SYNO_SUPPORT_XA=no
E: TAGS=:systemd:
E: USEC_INITIALIZED=277947
 

[keasee]

3 hours ago, sam juan said:

./rploader.sh update now

./rploader.sh fullupgrade now

./rploader.sh backup

./rploader.sh postupdate <platform>

for the above steps, is there a way to do this without attaching keyboard/mouse/monitor to the box?
thanks.

 what do you mean by: without ... attached ............. ever used : ssh? 

... that means, you should be connected on LAN and nic should work ...

Edited June 6, 2022 by keasee

[sam juan]

4 minutes ago, keasee said:

 what do you mean by: without ... attached ............. ever used : ssh? 

... that means, you should be connected on LAN and nic should work ...

before running those commands either in ssh; or inside TCRP, you will still need to choose the 3rd option in the boot menu, no?

and then after running those commands, you will select the 1st option in the boot menu; 

or is there a better way?

[neonflx]

After several failed attempts on an AMD Ryzen with a Z570 mobo tryinh DS162 and DS3622 been able to boot but not finding the hard rives I tried 918 and it worked perfectly

 

haha no idea but really like to get 1621 or 3622 installed

 

???

 

Thanks

[Polanskiman]

⚠️ Anyone not using the code tag for posting code, please do so. Some posts are just unreadable 

[irishj]

On 6/4/2022 at 11:40 PM, dolbycat said:

 

Until now, using the below pocopico Ext for DS1621+ for bare-metal failed.
Attempted to attach the 4.4.180plus-denverton expansion driver to the DS1621+.
Pocopico's was modified a little bit and applied as below, and igb, r8125 all succeeded with Intel NIC.

 

./rploader.sh ext v1000-7.1.0-42661 add https://raw.githubusercontent.com/dolbycat/rp-ext/main/igb/rpext-index.json
./rploader.sh ext v1000-7.1.0-42661 add https://raw.githubusercontent.com/dolbycat/rp-ext/main/r8125/rpext-index.json

 

Please refer to the above, I may be wrong as I am a beginner.

 

Receiving a "404" when attempting to use these extensions.  Since moving to v8.0.0 of the loader, I can't get my 10G Intel NIC to work.  TC see's it fine, but after loader creation it's not detected on the network, which worked before with earlier versions of the loader.  Wanted to try @dolbycatextensions to see if they made a difference.

 

curl: (22) The requested URL returned error: 404 Not Found                                                                                                                                                                            
[!] Failed to download https://raw.githubusercontent.com/dolbycat/rp-ext/main/igb/rpext-index.json to /home/tc/redpill-load/custom/extensions/_new_ext_index.tmp_json

*** Process will exit ***

[!] Failed to add "https://raw.githubusercontent.com/dolbycat/rp-ext/main/igb/rpext-index.json" as an extension:

*** Process will exit ***

 

 

[Deniska]

21 час назад, pocopico сказал:

Since I don’t have the hardware, it will be nice to know it the extension works or not 

@pocopico

 

I've tested loader from scratch with your extension for r8125 NIC and it works properly!
I did it so: ./rploader.sh ext v1000-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/r8125/rpext-index.json 

 

Thank you for support! 

I will go to fight with finding NVME disk.:) 

 

 

 

I have some idea. If i add external PCI-E to NVME device, can i use NVME disk like ordinary disk? May be somebody know how it work?

Thank you! 

[pocopico]

16 minutes ago, Deniska said:

@pocopico

 

I've tested loader from scratch with your extension for r8125 NIC and it works properly!
I did it so: ./rploader.sh ext v1000-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/r8125/rpext-index.json 

 

Thank you for support! 

I will go to fight with finding NVME disk.:) 

 

 

 

I have some idea. If i add external PCI-E to NVME device, can i use NVME disk like ordinary disk? May be somebody know how it work?

Thank you! 

 

Thanks a million for testing ! 

 

I have not tested extensively NVME for hosting data, but, I think it makes no sense to use NVME for hosting home purpose data, for the following reasons.

 

- Motherboards have one or maximum two NVME slots available, so even if you manage to include NVME as local disk you will have no redundancy.

- There is no real benefit on NVME bandwidth and IOPS is not a real issue on a NAS device unless you are after serving hypervisor loads, or transfer data between NVME disks inside the same NAS.

- Maximum LAN bandwith will most probably be saturated before you saturate SSD bandwidth *Maybe 25/50/100G but its not likely to be found in a home LAB. 

- You will never reach NVME IOPS over LAN as IP stuck will be the bottleneck again, unless you USE NVMEoF which is not possible with syno boxes yet.

 

Even on big datacenters, we are just starting to use all NVME storage devices.  I would personaly prefer to use enterprise grade SAS/SATA SSDs cause of the price, availability and redundancy.

 

Edited June 7, 2022 by pocopico

[Deniska]

5 минут назад, pocopico сказал:

 

Thanks a million for testing ! 

 

I have not tested extensively NVME for hosting data, but, I think it makes no sense to use NVME for hosting home purpose data, for the following reasons.

 

- Motherboards have one or maximum two NVME slots available, so even if you manage to include NVME as local disk you will have no redundancy.

- There is no real benefit on NVME bandwidth and IOPS is not a real issue on a NAS device unless you are after serving hypervisor loads, or transfer data between NVME disks inside the same NAS.

- Maximum LAN bandwith will most probably be saturated before you saturate SSD bandwidth *Maybe 25/50/100G but its not likely to be found in a home LAB. 

- You will never reach NVME IOPS over LAN as IP stuck will be the bottleneck again, unless you USE NVMEoF which is not possible with syno boxes yet.

 

Even on big datacenters, we are just starting to use all NVME storage devices.  I would personaly prefer to use enterprise grade SAS/SATA SSDs cause of the price, availability and redundancy.

 

 

About testing - it's small part than i can help you. You and another guys do big work for many people. Thank you very much!

 

I agree with you about using nvme disk! 

I'm not going to reach high speed for backup or transfer data. I like my 1Gb\s NIC and switch, it's enough for my targets. 

But i'm ready to use nvme SSD for silent work. I have some target for it.

If i can get SAS SSD i will use it for it, it's good idea, thanks.

But now i have nvme disk as gift and i think how i can use it. In bad case i will install it in table PC but i have already had one there.

Thank you!

[pocopico]

19 minutes ago, Deniska said:

But i'm ready to use nvme SSD for silent work. I have some target for it.

 

I have found the following step by step guide. 

 

 

I've used this process in the past and works.

 

 

[Andy Miller]

Fixed my own issue. FYI for anyone having trouble updating the rploader check your bios time and date.

 

 

Edited June 7, 2022 by Andy Miller