TinyCore RedPill Loader (TCRP)

[ditheo]

I am getting now this error

 

Disk /dev/synoboot: 7634 MB, 8005787648 bytes, 15636304 sectors
1021 cylinders, 247 heads, 62 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device       Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/synoboot1 *  0,32,33     6,62,56           2048     100351      98304 48.0M 83 Linux
Partition 1 has different physical/logical start (non-Linux?):
     phys=(0,32,33) logical=(0,33,3)
Partition 1 has different physical/logical end:
     phys=(6,62,56) logical=(6,136,36)
/dev/synoboot2    6,62,57     15,205,62       100352     253951     153600 75.0M 83 Linux
Partition 2 has different physical/logical start (non-Linux?):
     phys=(6,62,57) logical=(6,136,37)
Partition 2 has different physical/logical end:
     phys=(15,205,62) logical=(16,143,62)
/dev/synoboot3    15,205,63   130,138,8       253952    2097151    1843200  900M 83 Linux
Partition 3 has different physical/logical start (non-Linux?):
     phys=(15,205,63) logical=(16,144,1)
Partition 3 has different physical/logical end:
     phys=(130,138,8) logical=(136,233,2)

 

 

Tried new usb disk getting the same error again and again

tcrp-diag-2022-Mar-28-13-26.html

[pocopico]

38 minutes ago, FunThomas said:

Hello,

i have problems with the hard drive errors and sata ports being disabled aka satamapping problem
the synology webpage reports hard drives 1,2,3,6 broken and disabled, i dont know why its 4 drives since there are only 2 hdds (2x8TB) and the usb inserted

Loader results:
 

sudo ./rploader.sh satamap now
HBA: 00:1f.2 Disks : 6
SataPortMap=6
DiskIdxMap=00

so for me it looks ok -> 6 ports on 1st controller and mapping with no offset

tc@box:~$ lsscsi -Hv
[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]    ahci
  dir: /sys/class/scsi_host//host4
  device dir: /sys/devices/pci0000:00/0000:00:1f.2/ata5/host4
[5]    ahci
  dir: /sys/class/scsi_host//host5
  device dir: /sys/devices/pci0000:00/0000:00:1f.2/ata6/host5
[6]    usb-storage
  dir: /sys/class/scsi_host//host6
  device dir: /sys/devices/pci0000:00/0000:00:14.0/usb3/3-10/3-10:1.0/host6

but i see the hdds are connected to sata port 3+4 on mainboard (error -> hdd 1,2,3,6 broken)

tc@box:~$ ls -ldtr /sys/class/scsi_host/host*/device/port*
ls: cannot access '/sys/class/scsi_host/host*/device/port*': No such file or directory
tc@box:~$ ls -ldtr /sys/class/scsi_host/host*/device/target*
drwxr-xr-x 4 root root 0 Mar 28 08:22 /sys/class/scsi_host/host4/device/target4:0:0/
drwxr-xr-x 4 root root 0 Mar 28 08:22 /sys/class/scsi_host/host3/device/target3:0:0/
drwxr-xr-x 4 root root 0 Mar 28 08:22 /sys/class/scsi_host/host6/device/target6:0:0/
tc@box:~$ ls -ldtr /sys/class/scsi_host/host*/device/phy*
ls: cannot access '/sys/class/scsi_host/host*/device/phy*': No such file or directory

when i change hdds to sata port 0+1 (without changing config) i get error on hdd 3,4,5,6

DiskStation> ls -ldtr /sys/class/scsi_host/host*/device/target*
drwxr-xr-x    4 root     root             0 Jan  1 00:07 /sys/class/scsi_host/host6/device/target6:0:0
drwxr-xr-x    4 root     root             0 Mar 28  2022 /sys/class/scsi_host/host1/device/target1:0:0
drwxr-xr-x    4 root     root             0 Mar 28  2022 /sys/class/scsi_host/host0/device/target0:0:0

is it normal start it starts with index 6 and then counts down to 0 of the targets?

 

does someone have some hints for me with the setting of SataPortMap and DiskIdxMap?

 

some additional info outputs if maybe needed:
here fdisk -l with skipped /dev/ram0-7 and /dev/loop0-51

tc@box:~$ fdisk -l            
Disk /dev/sda: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: TOSHIBA HDWG480
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: xxx

Device     Start         End     Sectors  Size Type
/dev/sda1   2048 15628052479 15628050432  7.3T Microsoft basic data


Disk /dev/sdb: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: TOSHIBA HDWG480
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: xxx

Device     Start         End     Sectors  Size Type
/dev/sdb1   2048 15628052479 15628050432  7.3T Microsoft basic data


Disk /dev/sdc: 29.3 GiB, 31457280000 bytes, 61440000 sectors
Disk model: Flash Disk
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: dos
Disk identifier: xxx

Device     Boot  Start     End Sectors  Size Id Type
/dev/sdc1  *      2048  100351   98304   48M 83 Linux
/dev/sdc2       100352  253951  153600   75M 83 Linux
/dev/sdc3       253952 2097151 1843200  900M 83 Linux

 

tc@box:~$ lspci -nnqk
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06)
        Subsystem: Fujitsu Technology Solutions Device [1734:11e7]
        Kernel driver in use: hsw_uncore
00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06)
        Subsystem: Fujitsu Technology Solutions Device [1734:11e7]
00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06)
        Subsystem: Fujitsu Technology Solutions Device [1734:11e7]
00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 04)
        Subsystem: Fujitsu Technology Solutions Device [1734:11ea]
        Kernel driver in use: xhci_hcd
00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
        Subsystem: Fujitsu Technology Solutions Device [1734:11ea]
        Kernel driver in use: mei_me
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I217-LM [8086:153a] (rev 04)
        Subsystem: Fujitsu Technology Solutions Device [1734:11ed]
        Kernel driver in use: e1000e
00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 04)
        Subsystem: Fujitsu Technology Solutions Device [1734:11ea]
        Kernel driver in use: ehci-pci
00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [8086:8c20] (rev 04)
        Subsystem: Fujitsu Technology Solutions Device [1734:11eb]
00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d4)
        Kernel driver in use: pcieport
00:1c.1 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 [8086:8c12] (rev d4)
        Kernel driver in use: pcieport
00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] (rev 04)
        Subsystem: Fujitsu Technology Solutions Device [1734:11ea]
        Kernel driver in use: ehci-pci
00:1f.0 ISA bridge [0601]: Intel Corporation Q87 Express LPC Controller [8086:8c4e] (rev 04)
        Subsystem: Fujitsu Technology Solutions Device [1734:11ea]
        Kernel driver in use: lpc_ich
00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c02] (rev 04)
        Subsystem: Fujitsu Technology Solutions Device [1734:11ea]
        Kernel driver in use: ahci
00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 04)
        Subsystem: Fujitsu Technology Solutions Device [1734:11ea]
00:1f.6 Signal processing controller [1180]: Intel Corporation 8 Series Chipset Family Thermal Management Controller [8086:8c24] (rev 04)
        Subsystem: Fujitsu Technology Solutions Device [1734:11ea]
        Kernel driver in use: intel_pch_thermal
02:00.0 PCI bridge [0604]: Integrated Device Technology, Inc. [IDT] PES3T3 PCI Express Switch [111d:8039] (rev 0e)
        Kernel driver in use: pcieport
03:02.0 PCI bridge [0604]: Integrated Device Technology, Inc. [IDT] PES3T3 PCI Express Switch [111d:8039] (rev 0e)
        Kernel driver in use: pcieport
03:03.0 PCI bridge [0604]: Integrated Device Technology, Inc. [IDT] PES3T3 PCI Express Switch [111d:8039] (rev 0e)
        Kernel driver in use: pcieport
04:00.0 FireWire (IEEE 1394) [0c00]: LSI Corporation FW643 [TrueFire] PCIe 1394b Controller [11c1:5901] (rev 08)
        Subsystem: IOI Technology Corp FWB-PCIE1X2x [1546:0643]
05:00.0 FireWire (IEEE 1394) [0c00]: LSI Corporation FW643 [TrueFire] PCIe 1394b Controller [11c1:5901] (rev 08)
        Subsystem: IOI Technology Corp FWB-PCIE1X2x [1546:0643]

 

 

Can you press e while at grub and try SataPortMap=58 and DiskIdxMap=0F00 ?

 

 

[FunThomas]

5 minutes ago, pocopico said:

 

Can you press e while at grub and try SataPortMap=58 and DiskIdxMap=0F00 ?

 

 

i found out that the reported error hard disk drives are the numbers not working (1..9)

so 1,2,3,6 broken means on controller 0..5 -> 0,1,2 and 5 are broken(not used/not connected)

so 3&4 is connected and working

so i switched the hdds to sata ports 0+1 and the error switched to error on hdd 3,4,5,6

so i changed the config manually to

    "SataPortMap": "2",
    "DiskIdxMap": "00"

and now all hdds are detected as working

 

is there a way to mask out ports 2-5 on controller to not use and have SataPortMap still set to 6?
 

Edited March 28, 2022 by FunThomas

[Vodka2014]

Good Day,

 

Is there an guide on how to install and set this up ? Also is this stable now and will there be an official release

 

Thanks

[phone guy]

2 hours ago, D.S said:

Both lan port controller are realtek and both showed inside "Network" tab? I saw one driver was added only. I have 2 lan port as well, but only one was detected by tinycore and one have to add by manually.  Please check the model of lan controller to make sure have driver added.

 

Yes this is a branded nas box with two 1gbe realtek ports. When I checked in dsm 7, one of the realtek ports is configured and shows up as a usb device, and when I saw 1 I mean the only one that shows up.... there is still a second lan port (nic adapter) that is not being detected. I assume they are both the same?

[phone guy]

6 hours ago, blackmix said:

 

Add manual lan and link on your usb.

example:

ip link add eth1 link "usbcard" type macvlan mode bridge

ip addr add 192.168.1.1/32 dev eth1

ip link set eth1 up

 

so go to network tab.

Quote

u need add udev map lan usb before it.

because dsm dont auto add usb network in dev devices 

I really appreciate your help, but we @Jizar Stoffel and myself need just a little more detail please, as I am not familiar with linux/unix enviroments to just understand how to do what your suggesting.

[phone guy]

using command lsusb and lspci shows these results.

 

root@DS:~# lsusb -i
|__usb1          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (Linux 4.4.180+ xhc                                                                              i-hcd xHCI Host Controller 0000:00:15.0) hub
  |__1-4         f400:f400:0100 00  2.00  480MBit/s 200mA 1IF  (SanDisk' Cruzer                                                                               Fit 03021609022521204300)
  1-4:1.0         (IF) 08:06:50 2EPs () usb-storage host6 (synoboot)
|__usb2          1d6b:0003:0404 09  3.00 5000MBit/s 0mA 1IF  (Linux 4.4.180+ xhc                                                                              i-hcd xHCI Host Controller 0000:00:15.0) hub
  |__2-5         0bda:8153:3100 00  3.00 5000MBit/s 288mA 2IFs (Realtek USB 10/1                                                                              00/1000 LAN 001000001)
  2-5:2.0         (IF) 02:06:00 1EP  ()
  2-5:2.1         (IF) 0a:00:00 0EPs ()
root@DS:~# 

root@DS:~# lspci -nnqk
0000:00:00.0 Host bridge [0600]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Host Bridge [8086:5af0] (rev 0b)
        Subsystem: Intel Corporation Device [8086:7270]
0000:00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 500 [8086:5a85] (rev 0b)
        DeviceName:  Onboard IGD
        Subsystem: Intel Corporation Device [8086:2212]
        Kernel driver in use: i915
0000:00:0e.0 Audio device [0403]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster [8086:5a98] (rev 0b)
        Subsystem: Intel Corporation Device [8086:7270]
0000:00:0f.0 Communication controller [0780]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Trusted Execution Engine [8086:5a9a] (rev 0b)
        Subsystem: Intel Corporation Device [8086:7270]
0000:00:12.0 SATA controller [0106]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller [8086:5ae3] (rev 0b)
        Subsystem: Intel Corporation Device [8086:7270]
        Kernel driver in use: ahci
0000:00:13.0 PCI bridge [0604]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1 [8086:5ad8] (rev fb)
        Kernel driver in use: pcieport
0000:00:13.2 PCI bridge [0604]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #3 [8086:5ada] (rev fb)
        Kernel driver in use: pcieport
0000:00:14.0 PCI bridge [0604]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1 [8086:5ad6] (rev fb)
        Kernel driver in use: pcieport
0000:00:14.1 PCI bridge [0604]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #2 [8086:5ad7] (rev fb)
        Kernel driver in use: pcieport
0000:00:15.0 USB controller [0c03]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI [8086:5aa8] (rev 0b)
        Subsystem: Intel Corporation Device [8086:7270]
        Kernel driver in use: xhci_hcd
0000:00:1f.0 ISA bridge [0601]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Low Pin Count Interface [8086:5ae8] (rev 0b)
        Subsystem: Intel Corporation Device [8086:7270]
0000:00:1f.1 SMBus [0c05]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller [8086:5ad4] (rev 0b)
        Subsystem: Intel Corporation Device [8086:7270]
        Kernel driver in use: i801_smbus
0000:02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
        Subsystem: Realtek Semiconductor Co., Ltd. Device [10ec:0123]
        Kernel driver in use: r8169
0000:03:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 02)
        Subsystem: ASMedia Technology Inc. Device [1b21:1060]
        Kernel driver in use: ahci
0000:04:00.0 SATA controller [0106]: ASMedia Technology Inc. ASM1062 Serial ATA Controller [1b21:0612] (rev 02)
        Subsystem: ASMedia Technology Inc. Device [1b21:1060]
        Kernel driver in use: ahci
0001:00:12.0 SATA controller [0106]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller [8086:5ae3]
0001:00:13.0 Non-VGA unclassified device [0000]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1 [8086:5ad8]
0001:00:14.0 Non-VGA unclassified device [0000]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1 [8086:5ad6]
0001:00:15.0 USB controller [0c03]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI [8086:5aa8]
0001:00:16.0 Signal processing controller [1180]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series I2C Controller #1 [8086:5aac]
0001:00:18.0 Signal processing controller [1180]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 [8086:5abc]
0001:00:19.0 Signal processing controller [1180]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #3 [8086:5ac6]
        DeviceName:  Onboard LAN
0001:00:19.2 Signal processing controller [1180]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #3 [8086:5ac6]
0001:00:1f.0 SMBus [0c05]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller [8086:5ad4]
0001:00:1f.1 SMBus [0c05]: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller [8086:5ad4]
0001:01:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller [1b4b:9215] (rev 11)
0001:02:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
0001:03:00.0 Ethernet controller [0200]: Intel Corporation I211 Gigabit Network Connection [8086:1539] (rev 03)
root@DS:~#

 

So, if DSM is seeing the Realtek usb eth0 lan, does it look like the onboard lan is Intel i211? and that would be the one to add as eth1 ?

which I still do not understand how to do?

[Jizar Stoffel]

1 hour ago, phone guy said:

 

I really appreciate your help, but we @Jizar Stoffel and myself need just a little more detail please, as I am not familiar with linux/unix enviroments to just understand how to do what your suggesting.

Agreed...

I know this is a Devs area. and we should know all the basics, and I do know most linux commands. but DSM syntax does not really work that way... I have tried so many commands only to get "this is not a valid command" or " does not exits" etc.

Normally, when I help people with tech stuff, I try to dumb it down by simplifying things and giving step by step instructions. Needless to say that I spent most of the day searching on the web on how to fix this, but nothing I tried worked. This is why I decided to post here.... to see if I can get the help needed.

Edited March 28, 2022 by Jizar Stoffel

[Penguin Power]

On 3/25/2022 at 5:53 PM, IG-88 said:

maybe not, imho tg3 silicon is way to old for that, check if the tigon firmware is present

as far as i have seen the rp loaders and extensions seem not to care about firmware files needed by drivers

for tg3.ko there should be /lib/firmware/tigon/

tg3.bin

tg3_tso.bin

tg3_tso5.bin

you can download them by kernel.org

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/tigon

or extract them from jun's or my extra.lzma of loader for 6.2

usually it can be checked with "modinfo" if there are any dependencies on firmware, but synology does not provide modinfo in dsm so you would need a chroot or any linux with modinfo and point to dsm's drivers files to get the info (but thats usually something the provider of the driver needs to do)

these infos are only ascii in the *.ko file, if you use a hex editor anything that will show the raw file you can look for "vermagic" and in the area before that you will see things like pci id's and also "firmware=" and these are the firmware dependencies of the kernel driver (there is also "depends=" naming the dependencies of other kernel modules or "version=" that will tell you about the version of the driver)

@IG-88

Thank you very much for the detailed explanation!!

 

To verify content of my modules + firmware path, I executed below command.

 

➜  tg3-4.4.180plus-broadwellnk - strings tg3.ko | egrep -E "version|magic|firmware"
%s: Trying to load TX cpu firmware which is 5705
No firmware running
Failed to load firmware "%s"
tg3_load_tso_firmware
tg3_load_firmware_cpu
tg3_load_5701_a0_firmware_fix
firmware=tigon/tg3_tso5.bin
firmware=tigon/tg3_tso.bin
firmware=tigon/tg3.bin
version=3.137
srcversion=0737AAA138EA5CF848588B8
vermagic=4.4.180+ SMP mod_unload 
tg3_load_firmware_cpu

 

I used pocopico tg3+libphy modules from - https://github.com/pocopico/4.4.180plus-modules which I have copied to DSM's /lib/modules folder.

and firmware from - https://github.com/pocopico/4.4.180plus-modules/tree/main/firmware which I have copied on DSM's /lib/firmware/tigon folder.

 

I tried to "insmod" manually + tried rebooting DSM without any luck. (yes, after reboot file persist)

 

After that I tried firmware files from kernel.org without any luck.

 

Please note that, I am already up and running using 2nd nic card (r8168) and now I am trying to make my tg3 work.

 

Just to be clear, I have to copy modules + firmware to DSM's /lib/modules + /lib/firmware/tigon folder and don't have to do anything with RP loader/image file system correct?

Not sure if extra.lzma of loader for 6.2 have modules + firmware for 4.x kernel?

 

On a fresh startup of the DSM, I see that tg3 modules gets loaded (because I have build with tg3 extension) but it fails to bring up interface because of possible missing firmware files. So for anything to try, I first have to rmmod tg3+libphy first and try insmod /lib/modules/tg3.ko+libphy after making sure firmware files exist at correct location.

 

What else can I try? 

 

Thanks again in advance!! 

 

 

 

 

 

 

 

[blackmix]

2 hours ago, Jizar Stoffel said:

Agreed...

I know this is a Devs area. and we should know all the basics, and I do know most linux commands. but DSM syntax does not really work that way... I have tried so many commands only to get "this is not a valid command" or " does not exits" etc.

Normally, when I help people with tech stuff, I try to dumb it down by simplifying things and giving step by step instructions. Needless to say that I spent most of the day searching on the web on how to fix this, but nothing I tried worked. This is why I decided to post here.... to see if I can get the help needed.

Sorry, i can do later.. atm on work now.

 

[Jizar Stoffel]

Just now, blackmix said:

Sorry, i can do later.. atm on work now.

 

hey man, don't be sorry, I got nothing but respect for you guys that try to help us out!!!

[alienman]

Hi @pocopicoand others,

 

As I've described here 

with the recent version of redpill-tinycore we can create and use virtual SSD disks for cache. However, when using them one trouble exists: With the current implementation of the "smart_shim.c" when the disk is connected with the pvscsi controller all the SMART data is FAKE, including the SERIAL NUMBER. And the DSM uses the SERIAL NUMBER to identify the disk. So when you add more than one disk, then the UI will show only one of these disks... because all share the same serial number.

 

So I prepared a dirty patch that solves this problem:

root@redpill-tool-chain:/opt/redpill-lkm/shim/storage# diff smart_shim.c smart_shim.c.bak
272c272
< static int populate_ata_id(const u8 *req_header, void __user *buff_ptr, const char* const disk_name)
---
> static int populate_ata_id(const u8 *req_header, void __user *buff_ptr)
277d276
<       char disk_serial[DISK_NAME_LEN];
287,289c286
<     //set_ata_string(did->serial_no, "VH1132", 20);
<       strscpy(disk_serial, disk_name, DISK_NAME_LEN > 20 ? 20 : DISK_NAME_LEN);
<     set_ata_string(did->serial_no, disk_serial, 20);
---
>     set_ata_string(did->serial_no, "VH1132", 20);
291c288
<     set_ata_string(did->model, "Virtual-HDD", 40);
---
>     set_ata_string(did->model, "Virtual HDD", 40);
329c326
< static int handle_ata_cmd_identify(int org_ioctl_exec_result, const u8 *req_header, void __user *buff_ptr, const char* const disk_name)
---
> static int handle_ata_cmd_identify(int org_ioctl_exec_result, const u8 *req_header, void __user *buff_ptr)
336c333
<         return populate_ata_id(req_header, buff_ptr, disk_name);
---
>         return populate_ata_id(req_header, buff_ptr);
698c695
<             return handle_ata_cmd_identify(ioctl_out, req_header, buff_ptr, bdev->bd_disk->disk_name);
---
>             return handle_ata_cmd_identify(ioctl_out, req_header, buff_ptr);
817c814
< //#ifdef DBG_SMART_PRINT_ALL_IOCTL
---
> #ifdef DBG_SMART_PRINT_ALL_IOCTL
819c816
< //#endif
---
> #endif
834c831
< //#       ifdef DBG_SMART_PRINT_ALL_IOCTL
---
> #       ifdef DBG_SMART_PRINT_ALL_IOCTL
836c833
< //#       endif
---
> #       endif
1083c1080
< }
---
> }
\ No newline at end of file

What does this patch is to use the device name (from the "/dev/block_device_path") as the serial for such disks. And with this simple technique you can add as many cache disks as you want.

 

I attached a compiled version of the redpill.ko module for the ds3622xs+ platform for convenience. But please @pocopicoadd to your "rploader.sh" script the option to use a user-compiled-custom-redpill.ko module. At time it's a pain to edit your script only to "inject" it!

 

Regards.

 

redpill.ko.tgz

[phone guy]

Trying to figure this out. I re-installed dsm623 on jun104b loader on my baremetal nas box (branded nas box) in dsm6 with jun104b I have 2 working nic lan ports eth0 and eth1 - seems like one is on the pci bus and one is on the usb bus.

root@dsm6jun104b:~# ethtool -i eth0
driver: r8168
version: 8.048.03-NAPI
firmware-version:
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
root@dsm6jun104b:~# ethtool -i eth1
driver: r8152
version: v2.15.0 (2021/04/15)
firmware-version:
bus-info: usb-0000:00:15.0-5
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
root@dsm6jun104b:~#

 

lsusb -i (on dsm623 jun104b loader)

root@dsm6jun104b:~# lsusb -i
|__usb1          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (Linux 4.4.59+ xhci-hcd xHCI Host Controller 0000:00:15.0) hub
  |__1-4         f400:f400:0100 00  2.00  480MBit/s 200mA 1IF  (SanDisk' Cruzer Fit 03036809040721180816)
  1-4:1.0         (IF) 08:06:50 2EPs () usb-storage host6 (synoboot)
|__usb2          1d6b:0003:0404 09  3.00 5000MBit/s 0mA 1IF  (Linux 4.4.59+ xhci-hcd xHCI Host Controller 0000:00:15.0) hub
  |__2-5         0bda:8153:3100 00  3.00 5000MBit/s 288mA 1IF  (Realtek USB 10/100/1000 LAN 001000001)
  2-5:1.0         (IF) ff:ff:00 3EPs () r8152 net/eth1
root@dsm6jun104b:~#

 

lsusb -i (dsm7 w/RP loader)

root@DS:~# lsusb -i
|__usb1          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (Linux 4.4.180+ xhc                                                                              i-hcd xHCI Host Controller 0000:00:15.0) hub
  |__1-4         f400:f400:0100 00  2.00  480MBit/s 200mA 1IF  (SanDisk' Cruzer                                                                               Fit 03021609022521204300)
  1-4:1.0         (IF) 08:06:50 2EPs () usb-storage host6 (synoboot)
|__usb2          1d6b:0003:0404 09  3.00 5000MBit/s 0mA 1IF  (Linux 4.4.180+ xhc                                                                              i-hcd xHCI Host Controller 0000:00:15.0) hub
  |__2-5         0bda:8153:3100 00  3.00 5000MBit/s 288mA 2IFs (Realtek USB 10/1                                                                              00/1000 LAN 001000001)
  2-5:2.0         (IF) 02:06:00 1EP  ()
  2-5:2.1         (IF) 0a:00:00 0EPs ()
root@DS:~# 

 

lspci -k (dsm6 jun104b loader)

root@dsm6jun104b:~# lspci -k
0000:00:00.0 Host bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Host Bridge (rev 0b)
        Subsystem: Intel Corporation Device 7270
0000:00:02.0 VGA compatible controller: Intel Corporation HD Graphics 500 (rev 0b)
        Subsystem: Intel Corporation Device 2212
        Kernel driver in use: i915
0000:00:0e.0 Audio device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster (rev 0b)
        Subsystem: Intel Corporation Device 7270
0000:00:0f.0 Communication controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Trusted Execution Engine (rev 0b)
        Subsystem: Intel Corporation Device 7270
0000:00:12.0 SATA controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller (rev 0b)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: ahci
0000:00:13.0 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1 (rev fb)
        Kernel driver in use: pcieport
0000:00:13.2 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #3 (rev fb)
        Kernel driver in use: pcieport
0000:00:14.0 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1 (rev fb)
        Kernel driver in use: pcieport
0000:00:14.1 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #2 (rev fb)
        Kernel driver in use: pcieport
0000:00:15.0 USB controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI (rev 0b)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: xhci_hcd
0000:00:1f.0 ISA bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Low Pin Count Interface (rev 0b)
        Subsystem: Intel Corporation Device 7270
0000:00:1f.1 SMBus: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller (rev 0b)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: i801_smbus
0000:02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
        Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
        Kernel driver in use: r8168
0000:03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
        Subsystem: ASMedia Technology Inc. Device 1060
        Kernel driver in use: ahci
0000:04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
        Subsystem: ASMedia Technology Inc. Device 1060
        Kernel driver in use: ahci
0001:00:12.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller (rev ff)
0001:00:13.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1 (rev ff)
0001:00:14.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1 (rev ff)
0001:00:15.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI (rev ff)
0001:00:16.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series I2C Controller #1 (rev ff)
0001:00:18.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev ff)
0001:00:19.2 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #3 (rev ff)
0001:00:1f.1 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller (rev ff)
0001:01:00.0 Non-VGA unclassified device: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller (rev ff)
0001:02:00.0 Non-VGA unclassified device: Intel Corporation I211 Gigabit Network Connection (rev ff)
0001:03:00.0 Non-VGA unclassified device: Intel Corporation I211 Gigabit Network Connection (rev ff)
root@dsm6jun104b:~#

 

lspci -k (dsm7 w/RP loader)

root@DS:~# lspci -k
0000:00:00.0 Host bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Host Bridge (rev 0b)
        Subsystem: Intel Corporation Device 7270
0000:00:02.0 VGA compatible controller: Intel Corporation HD Graphics 500 (rev 0b)
        DeviceName:  Onboard IGD
        Subsystem: Intel Corporation Device 2212
        Kernel driver in use: i915
0000:00:0e.0 Audio device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster (rev 0b)
        Subsystem: Intel Corporation Device 7270
0000:00:0f.0 Communication controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Trusted Execution Engine (rev 0b)
        Subsystem: Intel Corporation Device 7270
0000:00:12.0 SATA controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller (rev 0b)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: ahci
0000:00:13.0 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1 (rev fb)
        Kernel driver in use: pcieport
0000:00:13.2 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #3 (rev fb)
        Kernel driver in use: pcieport
0000:00:14.0 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1 (rev fb)
        Kernel driver in use: pcieport
0000:00:14.1 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #2 (rev fb)
        Kernel driver in use: pcieport
0000:00:15.0 USB controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI (rev 0b)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: xhci_hcd
0000:00:1f.0 ISA bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Low Pin Count Interface (rev 0b)
        Subsystem: Intel Corporation Device 7270
0000:00:1f.1 SMBus: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller (rev 0b)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: i801_smbus
0000:02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
        Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
        Kernel driver in use: r8169
0000:03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
        Subsystem: ASMedia Technology Inc. Device 1060
        Kernel driver in use: ahci
0000:04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
        Subsystem: ASMedia Technology Inc. Device 1060
        Kernel driver in use: ahci
0001:00:12.0 SATA controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller
0001:00:13.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1
0001:00:14.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1
0001:00:15.0 USB controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI
0001:00:16.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series I2C Controller #1
0001:00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1
0001:00:19.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #3
        DeviceName:  Onboard LAN
0001:00:19.2 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #3
0001:00:1f.0 SMBus: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller
0001:00:1f.1 SMBus: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller
0001:01:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller (rev 11)
0001:02:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
0001:03:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
root@DS:~#

 

So, what am I missing? the xhci bus seems to be there, even reporting the usb realtek ... why does it show up on 1 system/loader and not on the other?

 

Does this give anyone more information on how to access the second nic lan port eth1 on dsm7 with rp?

Edited March 29, 2022 by phone guy
added more code

[alirz1]

So im giving the latest tinycore a try and trying to setup the 7.0.1 dsm using VMware work station in windows. Its all good, untill tinycore downloads the PAT file and starts to unpack it. But it the whole vm jsut freezes there, like it has kernel panicked in the background or something.

i've tried starting clean a few times but it fails at this point always.

 

Any ideas if i could be doing something wrong. Just using the basic steps listed on the tinycore github page.

[Peter Suh]

On 3/23/2022 at 5:01 AM, sam juan said:

anyone able to make WOL wake-on-lan worked for baremetal installs? tnx

Sent from my Pixel 6 Pro using Tapatalk
 

 

I am also currently testing DS3622xs+ and WAKE-ON-LAN issues.
The previously used WAKE-ON-LAN on the GIGABYTE Z87N-WIFI motherboard worked without any problems.
However, the new Asus IOT H310i-IM-A R2.0 industrial motherboard WAKE-ON-LAN is a bit unique.
Instead of simply supporting WAKE-ON-LAN on each LAN port on a dual-port,
The PCIE-mounted NIC also supports WAKE-ON-LAN.
When I turned on this WAKE-ON-LAN option and rebooted, the DS3622xs+ bootloader did not recognize the existing installed DSM and requested a new DSM installation.
It seems to work as if you have met a new environment related to NIC.
So, an additional scheduled test will try to find another stable model for the HBA card and see if it can be migrated to a platform other than DS3622xs+.

[Peter Suh]

On 3/28/2022 at 6:32 AM, Dvalin21 said:

I do have another question. On the Diskid I've seen so many variants of this being posted and shared. What is the conversion from what to what to get the Diskid? If there is nothing exact, then what would be the closest thing to look at?  Same thing with the Satamap?  The satamap identify function seems to only work with onboard sata controllers and I have a perc h310 which it doesnt sees (unless something has changed all of a sudden). Either way Im thankful that I can install DSM on my device as I never could on 3617, 3615, and 918. Something with this has something to do with the system marking the drives as (null) Unsupported. I also noticed that after I install, DSM seems to change my hdd from gpt to mbr. I can understand the one of them as it needs to have a bootable, but all of them?  Thanks

 

As far as I know, DS3622xs+ is the only platform that has a stable H310 HBA, why not try this platform?
On the three platforms you know, even if you can't see or see the HBA at all, there are still errors that appear to be NULL HDD.

[pocopico]

17 hours ago, ditheo said:

I am getting now this error

 

Disk /dev/synoboot: 7634 MB, 8005787648 bytes, 15636304 sectors
1021 cylinders, 247 heads, 62 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device       Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/synoboot1 *  0,32,33     6,62,56           2048     100351      98304 48.0M 83 Linux
Partition 1 has different physical/logical start (non-Linux?):
     phys=(0,32,33) logical=(0,33,3)
Partition 1 has different physical/logical end:
     phys=(6,62,56) logical=(6,136,36)
/dev/synoboot2    6,62,57     15,205,62       100352     253951     153600 75.0M 83 Linux
Partition 2 has different physical/logical start (non-Linux?):
     phys=(6,62,57) logical=(6,136,37)
Partition 2 has different physical/logical end:
     phys=(15,205,62) logical=(16,143,62)
/dev/synoboot3    15,205,63   130,138,8       253952    2097151    1843200  900M 83 Linux
Partition 3 has different physical/logical start (non-Linux?):
     phys=(15,205,63) logical=(16,144,1)
Partition 3 has different physical/logical end:
     phys=(130,138,8) logical=(136,233,2)

 

 

Tried new usb disk getting the same error again and again

tcrp-diag-2022-Mar-28-13-26.html 52.61 kB · 1 download

 

 

Nice to see that the diag report is being used.

 

What is the issue ? Does this result on an error during install ? What program do you use to write the TCRP image to the usb stick ? 

 

 

[D.S]

6 hours ago, phone guy said:

Trying to figure this out. I re-installed dsm623 on jun104b loader on my baremetal nas box (branded nas box) in dsm6 with jun104b I have 2 working nic lan ports eth0 and eth1 - seems like one is on the pci bus and one is on the usb bus.

root@dsm6jun104b:~# ethtool -i eth0
driver: r8168
version: 8.048.03-NAPI
firmware-version:
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: yes
supports-priv-flags: no
root@dsm6jun104b:~# ethtool -i eth1
driver: r8152
version: v2.15.0 (2021/04/15)
firmware-version:
bus-info: usb-0000:00:15.0-5
supports-statistics: yes
supports-test: no
supports-eeprom-access: no
supports-register-dump: no
supports-priv-flags: no
root@dsm6jun104b:~#

 

lsusb -i (on dsm623 jun104b loader)

root@dsm6jun104b:~# lsusb -i
|__usb1          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (Linux 4.4.59+ xhci-hcd xHCI Host Controller 0000:00:15.0) hub
  |__1-4         f400:f400:0100 00  2.00  480MBit/s 200mA 1IF  (SanDisk' Cruzer Fit 03036809040721180816)
  1-4:1.0         (IF) 08:06:50 2EPs () usb-storage host6 (synoboot)
|__usb2          1d6b:0003:0404 09  3.00 5000MBit/s 0mA 1IF  (Linux 4.4.59+ xhci-hcd xHCI Host Controller 0000:00:15.0) hub
  |__2-5         0bda:8153:3100 00  3.00 5000MBit/s 288mA 1IF  (Realtek USB 10/100/1000 LAN 001000001)
  2-5:1.0         (IF) ff:ff:00 3EPs () r8152 net/eth1
root@dsm6jun104b:~#

 

lsusb -i (dsm7 w/RP loader)

root@DS:~# lsusb -i
|__usb1          1d6b:0002:0404 09  2.00  480MBit/s 0mA 1IF  (Linux 4.4.180+ xhc                                                                              i-hcd xHCI Host Controller 0000:00:15.0) hub
  |__1-4         f400:f400:0100 00  2.00  480MBit/s 200mA 1IF  (SanDisk' Cruzer                                                                               Fit 03021609022521204300)
  1-4:1.0         (IF) 08:06:50 2EPs () usb-storage host6 (synoboot)
|__usb2          1d6b:0003:0404 09  3.00 5000MBit/s 0mA 1IF  (Linux 4.4.180+ xhc                                                                              i-hcd xHCI Host Controller 0000:00:15.0) hub
  |__2-5         0bda:8153:3100 00  3.00 5000MBit/s 288mA 2IFs (Realtek USB 10/1                                                                              00/1000 LAN 001000001)
  2-5:2.0         (IF) 02:06:00 1EP  ()
  2-5:2.1         (IF) 0a:00:00 0EPs ()
root@DS:~# 

 

lspci -k (dsm6 jun104b loader)

root@dsm6jun104b:~# lspci -k
0000:00:00.0 Host bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Host Bridge (rev 0b)
        Subsystem: Intel Corporation Device 7270
0000:00:02.0 VGA compatible controller: Intel Corporation HD Graphics 500 (rev 0b)
        Subsystem: Intel Corporation Device 2212
        Kernel driver in use: i915
0000:00:0e.0 Audio device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster (rev 0b)
        Subsystem: Intel Corporation Device 7270
0000:00:0f.0 Communication controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Trusted Execution Engine (rev 0b)
        Subsystem: Intel Corporation Device 7270
0000:00:12.0 SATA controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller (rev 0b)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: ahci
0000:00:13.0 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1 (rev fb)
        Kernel driver in use: pcieport
0000:00:13.2 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #3 (rev fb)
        Kernel driver in use: pcieport
0000:00:14.0 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1 (rev fb)
        Kernel driver in use: pcieport
0000:00:14.1 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #2 (rev fb)
        Kernel driver in use: pcieport
0000:00:15.0 USB controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI (rev 0b)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: xhci_hcd
0000:00:1f.0 ISA bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Low Pin Count Interface (rev 0b)
        Subsystem: Intel Corporation Device 7270
0000:00:1f.1 SMBus: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller (rev 0b)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: i801_smbus
0000:02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
        Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
        Kernel driver in use: r8168
0000:03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
        Subsystem: ASMedia Technology Inc. Device 1060
        Kernel driver in use: ahci
0000:04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
        Subsystem: ASMedia Technology Inc. Device 1060
        Kernel driver in use: ahci
0001:00:12.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller (rev ff)
0001:00:13.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1 (rev ff)
0001:00:14.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1 (rev ff)
0001:00:15.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI (rev ff)
0001:00:16.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series I2C Controller #1 (rev ff)
0001:00:18.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1 (rev ff)
0001:00:19.2 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #3 (rev ff)
0001:00:1f.1 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller (rev ff)
0001:01:00.0 Non-VGA unclassified device: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller (rev ff)
0001:02:00.0 Non-VGA unclassified device: Intel Corporation I211 Gigabit Network Connection (rev ff)
0001:03:00.0 Non-VGA unclassified device: Intel Corporation I211 Gigabit Network Connection (rev ff)
root@dsm6jun104b:~#

 

lspci -k (dsm7 w/RP loader)

root@DS:~# lspci -k
0000:00:00.0 Host bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Host Bridge (rev 0b)
        Subsystem: Intel Corporation Device 7270
0000:00:02.0 VGA compatible controller: Intel Corporation HD Graphics 500 (rev 0b)
        DeviceName:  Onboard IGD
        Subsystem: Intel Corporation Device 2212
        Kernel driver in use: i915
0000:00:0e.0 Audio device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Audio Cluster (rev 0b)
        Subsystem: Intel Corporation Device 7270
0000:00:0f.0 Communication controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Trusted Execution Engine (rev 0b)
        Subsystem: Intel Corporation Device 7270
0000:00:12.0 SATA controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller (rev 0b)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: ahci
0000:00:13.0 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1 (rev fb)
        Kernel driver in use: pcieport
0000:00:13.2 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #3 (rev fb)
        Kernel driver in use: pcieport
0000:00:14.0 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1 (rev fb)
        Kernel driver in use: pcieport
0000:00:14.1 PCI bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #2 (rev fb)
        Kernel driver in use: pcieport
0000:00:15.0 USB controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI (rev 0b)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: xhci_hcd
0000:00:1f.0 ISA bridge: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series Low Pin Count Interface (rev 0b)
        Subsystem: Intel Corporation Device 7270
0000:00:1f.1 SMBus: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller (rev 0b)
        Subsystem: Intel Corporation Device 7270
        Kernel driver in use: i801_smbus
0000:02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
        Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
        Kernel driver in use: r8169
0000:03:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
        Subsystem: ASMedia Technology Inc. Device 1060
        Kernel driver in use: ahci
0000:04:00.0 SATA controller: ASMedia Technology Inc. ASM1062 Serial ATA Controller (rev 02)
        Subsystem: ASMedia Technology Inc. Device 1060
        Kernel driver in use: ahci
0001:00:12.0 SATA controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SATA AHCI Controller
0001:00:13.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port A #1
0001:00:14.0 Non-VGA unclassified device: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series PCI Express Port B #1
0001:00:15.0 USB controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series USB xHCI
0001:00:16.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series I2C Controller #1
0001:00:18.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series HSUART Controller #1
0001:00:19.0 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #3
        DeviceName:  Onboard LAN
0001:00:19.2 Signal processing controller: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SPI Controller #3
0001:00:1f.0 SMBus: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller
0001:00:1f.1 SMBus: Intel Corporation Celeron N3350/Pentium N4200/Atom E3900 Series SMBus Controller
0001:01:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9215 PCIe 2.0 x1 4-port SATA 6 Gb/s Controller (rev 11)
0001:02:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
0001:03:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
root@DS:~#

 

So, what am I missing? the xhci bus seems to be there, even reporting the usb realtek ... why does it show up on 1 system/loader and not on the other?

 

Does this give anyone more information on how to access the second nic lan port eth1 on dsm7 with rp?

Your NAS has 2 different lan controller. One is realtek, one is Intel. Pls figure out which one is working on DSM 7 first. 

[ditheo]

1 hour ago, pocopico said:

What is the issue ? Does this result on an error during install ? What program do you use to write the TCRP image to the usb stick ? 

 

I tried to write the tcrp image with balena etcher and rufus. Gave me the same error. I throw all these usb sticks on the bin (kingston variants usb 2.0 4-8-16 GB)

Now I wrote the iamge on sandisk usb that is compiling ok but i cannot proceed to the installation of DSM. Always the webpage gives me "connection refused" even after of 30 minutes.

 

One silly question.

Which commands must run with sudo and wich with not?

my last effort was with sudo in the commands of identifyusb,satamap,serialgen, build. without sudo the extensions. 

 

 

tcrp-diag-2022-Mar-28-16-00.html

[pocopico]

1 hour ago, ditheo said:

I tried to write the tcrp image with balena etcher and rufus. Gave me the same error. I throw all these usb sticks on the bin (kingston variants usb 2.0 4-8-16 GB)

Now I wrote the iamge on sandisk usb that is compiling ok but i cannot proceed to the installation of DSM. Always the webpage gives me "connection refused" even after of 30 minutes.

 

One silly question.

Which commands must run with sudo and wich with not?

my last effort was with sudo in the commands of identifyusb,satamap,serialgen, build. without sudo the extensions. 

 

 

tcrp-diag-2022-Mar-28-16-00.html 51.49 kB · 0 downloads

 

 

netstat -an

Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State Active UNIX domain sockets (servers and established) Proto RefCnt Flags Type State I-Node Path

 

 

[phone guy]

2 hours ago, D.S said:

Your NAS has 2 different lan controller. One is realtek, one is Intel. Pls figure out which one is working on DSM 7 first. 

On this nas box, in dsm623 jun104b loader both nic lan ports are realtek. One is on the PCI bus and one is USB bus, I think. Both work 100% (again dsm623jun104b).

 

In dsm7 with rp046 loader, only 1 realtek nic lan port is working. (both ports work while in tinycore, and both have valid ip's while booted into tinycore) after building the apollolake loader, and installing and booting to dsm7, one 1 nic lan port works, while in dsm7 control panel>info center shows it as realtek r8153 usb device, but the ssh/terminal shows as only the pci realtek loaded and working.

 

 

 

that post above has logs from both a dsm623 jun104b build and dsm701 rp046 loader build.

In the dsm6 it loads both realtek nic and shows drivers used for each.

in dsm7 however, only the pci realtek is used and shown having a driver (r8169) in dsm7, again no usb realtek, but dsm7 shows the only eth0 as a usb device.

 

In dsm6 that same realtek is using driver R8168, the other realtek is using driver R8152, and both working.

 

I then tried to rebuild the rploader with using the ./rploader.sh ext add url command to add r8152 ext package (which it does download and add) but after building the loader it will not start in to dsm7 <- if I add the R8152 ext

when the loader builds, it installs dsm7 and restarts and just hangs forever - monitor output shows starting usb kernel but hangs, never loads the hdds... pointing back to synoip I just get the welcome to diskstation message waiting to install dsm7 again.

 

if I do NOT add the R8152 driver, it builds and loads fine and first try (but with only 1 working eth0 nic lan port)

@pocopico I hope you can read this and explain what adding the R8152 driver to an apollolake build causes this system to hang immediately after installing dsm7 and never actually loading into dsm?

 

 

Edited March 29, 2022 by phone guy

[ditheo]

1 minute ago, pocopico said:

netstat -an

i saw that... I can ping DSM when it starts. but It did not respond to any http request. The only thing I saw after a couple of minutes (6-8 min ) is that DSM request something from the dns server. 

 

I already have block internet access to the ip of DSM

[alienman]

Hi @pocopico,

 

Please could you merge this (now clean) patch for supporting any number of SCSI disks with redpill-lkm?

 

diff --git a/shim/storage/smart_shim.c b/shim/storage/smart_shim.c
index 6d94e68..0b7eaf4 100644
--- a/shim/storage/smart_shim.c
+++ b/shim/storage/smart_shim.c
@@ -269,11 +269,12 @@ static __always_inline void put_ioctl_buffer(unsigned char *buffer)
 }

 /*************************************** ATAPI/WIN command interface handling *****************************************/
-static int populate_ata_id(const u8 *req_header, void __user *buff_ptr)
+static int populate_ata_id(const u8 *req_header, void __user *buff_ptr, const char* const disk_name)
 {
     pr_loc_dbg("Generating completely fake ATA IDENTITY");

     unsigned char *kbuf;
+    char disk_serial[DISK_NAME_LEN];
     kzalloc_or_exit_int(kbuf, HDIO_DRIVE_CMD_HDR_OFFSET + sizeof(struct rp_hd_driveid));
     struct rp_hd_driveid *did = (void *)(kbuf + HDIO_DRIVE_CMD_HDR_OFFSET); //did=drive ID

@@ -283,7 +284,8 @@ static int populate_ata_id(const u8 *req_header, void __user *buff_ptr)
     kbuf[HDIO_DRIVE_CMD_RET_SEC_CNT] = ATA_CMD_ID_ATA_SECTORS;

     did->config = 0x0000; //15th bit = ATA device, rest is reserved/obsolete
-    set_ata_string(did->serial_no, "VH1132", 20);
+    strscpy(disk_serial, disk_name, DISK_NAME_LEN > 20 ? 20 : DISK_NAME_LEN);
+    set_ata_string(did->serial_no, disk_serial, 20);
     set_ata_string(did->fw_rev, "1.13.2", 8);
     set_ata_string(did->model, "Virtual HDD", 40);
     did->reserved50 = (1 << 14); //"shall be set to one"
@@ -323,14 +325,14 @@ static int populate_ata_id(const u8 *req_header, void __user *buff_ptr)
  * @return definitive exit code for the ioctl(); in practice 0 when succedded [regardless of the modifications made] or
  *         the same error code as org_ioctl_exec_result passed
  */
-static int handle_ata_cmd_identify(int org_ioctl_exec_result, const u8 *req_header, void __user *buff_ptr)
+static int handle_ata_cmd_identify(int org_ioctl_exec_result, const u8 *req_header, void __user *buff_ptr, const char* const disk_name)
 {
     //ATA IDENTIFY should not fail - it may mean a problem with a disk or the "disk" is a adapter (e.g. IDE>SATA) with
     // no disk connected, or if executed against a USB flash drive... or it's an VirtIO SCSI disk read as ATA
     if (unlikely(org_ioctl_exec_result != 0)) {
         pr_loc_dbg("sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=%d, attempting to emulate something",
                    org_ioctl_exec_result);
-        return populate_ata_id(req_header, buff_ptr);
+        return populate_ata_id(req_header, buff_ptr, disk_name);
     }

     //sanity check if requested ATA IDENTIFY sector count is really what we're planning to copy
@@ -692,7 +694,7 @@ static int handle_hdio_drive_cmd_ioctl(struct block_device *bdev, fmode_t mode,
         // we need to modify it to indicate SMART support
         case ATA_CMD_ID_ATA:
             pr_loc_dbg_ioctl(cmd, "ATA_CMD_ID_ATA", bdev);
-            return handle_ata_cmd_identify(ioctl_out, req_header, buff_ptr);
+            return handle_ata_cmd_identify(ioctl_out, req_header, buff_ptr, bdev->bd_disk->disk_name);

         //this command asks directly for the SMART data of the drive and will fail on drives with no real SMART support
         case ATA_CMD_SMART: //if the drive supports SMART it will just return the data as-is, no need to proxy

 

And why this patch?

With the recent version of redpill-tinycore we can create and use virtual SSD disks for cache. However, when using them one trouble exists: With the current implementation of the "smart_shim.c" when the disk is connected with the pvscsi controller all the SMART data is FAKE, including the SERIAL NUMBER. And the DSM uses the SERIAL NUMBER to identify the disk. So when you add more than one disk, then the UI will show only one of these disks... because all share the same serial number.

What does this patch is to use the device name (from the "/dev/block_device_path") as the serial for such disks. And with this simple technique you can add as many cache disks as you want.

 

Regards.

Edited March 29, 2022 by alienman

[pocopico]

5 minutes ago, alienman said:

Hi @pocopico,

 

Please could you merge this (now clean) patch for supporting any number of SCSI disks with redpill-lkm?

 

diff --git a/shim/storage/smart_shim.c b/shim/storage/smart_shim.c
index 6d94e68..0b7eaf4 100644
--- a/shim/storage/smart_shim.c
+++ b/shim/storage/smart_shim.c
@@ -269,11 +269,12 @@ static __always_inline void put_ioctl_buffer(unsigned char *buffer)
 }

 /*************************************** ATAPI/WIN command interface handling *****************************************/
-static int populate_ata_id(const u8 *req_header, void __user *buff_ptr)
+static int populate_ata_id(const u8 *req_header, void __user *buff_ptr, const char* const disk_name)
 {
     pr_loc_dbg("Generating completely fake ATA IDENTITY");

     unsigned char *kbuf;
+    char disk_serial[DISK_NAME_LEN];
     kzalloc_or_exit_int(kbuf, HDIO_DRIVE_CMD_HDR_OFFSET + sizeof(struct rp_hd_driveid));
     struct rp_hd_driveid *did = (void *)(kbuf + HDIO_DRIVE_CMD_HDR_OFFSET); //did=drive ID

@@ -283,7 +284,8 @@ static int populate_ata_id(const u8 *req_header, void __user *buff_ptr)
     kbuf[HDIO_DRIVE_CMD_RET_SEC_CNT] = ATA_CMD_ID_ATA_SECTORS;

     did->config = 0x0000; //15th bit = ATA device, rest is reserved/obsolete
-    set_ata_string(did->serial_no, "VH1132", 20);
+    strscpy(disk_serial, disk_name, DISK_NAME_LEN > 20 ? 20 : DISK_NAME_LEN);
+    set_ata_string(did->serial_no, disk_serial, 20);
     set_ata_string(did->fw_rev, "1.13.2", 8);
     set_ata_string(did->model, "Virtual HDD", 40);
     did->reserved50 = (1 << 14); //"shall be set to one"
@@ -323,14 +325,14 @@ static int populate_ata_id(const u8 *req_header, void __user *buff_ptr)
  * @return definitive exit code for the ioctl(); in practice 0 when succedded [regardless of the modifications made] or
  *         the same error code as org_ioctl_exec_result passed
  */
-static int handle_ata_cmd_identify(int org_ioctl_exec_result, const u8 *req_header, void __user *buff_ptr)
+static int handle_ata_cmd_identify(int org_ioctl_exec_result, const u8 *req_header, void __user *buff_ptr, const char* const disk_name)
 {
     //ATA IDENTIFY should not fail - it may mean a problem with a disk or the "disk" is a adapter (e.g. IDE>SATA) with
     // no disk connected, or if executed against a USB flash drive... or it's an VirtIO SCSI disk read as ATA
     if (unlikely(org_ioctl_exec_result != 0)) {
         pr_loc_dbg("sd_ioctl(HDIO_DRIVE_CMD ; ATA_CMD_ID_ATA) failed with error=%d, attempting to emulate something",
                    org_ioctl_exec_result);
-        return populate_ata_id(req_header, buff_ptr);
+        return populate_ata_id(req_header, buff_ptr, disk_name);
     }

     //sanity check if requested ATA IDENTIFY sector count is really what we're planning to copy
@@ -692,7 +694,7 @@ static int handle_hdio_drive_cmd_ioctl(struct block_device *bdev, fmode_t mode,
         // we need to modify it to indicate SMART support
         case ATA_CMD_ID_ATA:
             pr_loc_dbg_ioctl(cmd, "ATA_CMD_ID_ATA", bdev);
-            return handle_ata_cmd_identify(ioctl_out, req_header, buff_ptr);
+            return handle_ata_cmd_identify(ioctl_out, req_header, buff_ptr, bdev->bd_disk->disk_name);

         //this command asks directly for the SMART data of the drive and will fail on drives with no real SMART support
         case ATA_CMD_SMART: //if the drive supports SMART it will just return the data as-is, no need to proxy

 

Regards.

 

Hi, i'm sorry but you will have to PR the main loader repo holders. Mainly @jumkey @yanjun and @buggy25200

 

 

[pocopico]

19 minutes ago, ditheo said:

i saw that... I can ping DSM when it starts. but It did not respond to any http request. The only thing I saw after a couple of minutes (6-8 min ) is that DSM request something from the dns server. 

 

I already have block internet access to the ip of DSM

 

The DS3622xp+ at least to my knowledge, does not have an issue with the internet while installing. Please open access and retry.