RedPill - the new loader for 6.2.4 - Discussion


Recommended Posts

8 minutes ago, shibby said:

@pocopico can you compile tn40xx module for DS710+ 7.0.1 - (Tehuti Networks Ltd. TN9710P 10GBase-T/NBASE-T Ethernet Adapter) for Edimax EN-9320TX-E?

 

Best Regards.

 

It not in the kernel tree, had to download and compile, nevertheless you can try 

 

Can you try : https://github.com/pocopico/4.4.180plus-modules/raw/main/tn40xx.ko

 

Link to post
Share on other sites
8 minutes ago, Orphée said:

There is an unused SATA1 Vmware controller (no virtual disk plugged on it)

Only having :

DiskIdxMap=0C

SataPortMap=1

SasIdxMap=0

I'm not very sure that DiskIdxMap is taken consideration, i need to further test. But in your case it makes sence to use something like 

 

SataPortMap=<number of disks in controller 1><number of disks in controller 2><number of disks in controller 3>

e.g. 

SataPortMap=188

 

 

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

 

It not in the kernel tree, had to download and compile, nevertheless you can try 

 

Can you try : https://github.com/pocopico/4.4.180plus-modules/raw/main/tn40xx.ko

 

 

root@nas:~# insmod /volume1/dane/tn40xx.ko
insmod: ERROR: could not insert module /volume1/dane/tn40xx.ko: Unknown symbol in module

#dmesg
[  115.098302] tn40xx: Unknown symbol __fentry__ (err 0)
[  115.103362] tn40xx: Unknown symbol __stack_chk_fail (err 0)
[  115.108953] tn40xx: Unknown symbol pv_irq_ops (err 0)
[  115.114019] tn40xx: Unknown symbol _raw_spin_unlock (err 0)
[  115.119589] tn40xx: Unknown symbol alloc_pages_current (err 0)

 

Link to post
Share on other sites
6 minutes ago, scoobdriver said:

 

 

Did you do a upgrade, or a build a new boot loader as your previous post shows you building with bromolow-7.0-41222 , yet this shows 7.0.1-42218 ?

I put build command (docker) but I guess that will not required because it is just point release, drivers are same I just added and rename them but pocopico updated later and for config/_common orphee have branch I just wget those but I have to make better Docker-toolchain

I have to build new image and flash on usb, migration assistance will prompt and install latest 42218.pat and it done with SAS drivers.

Edited by psychoboi32
Link to post
Share on other sites
10 minutes ago, shibby said:

 


root@nas:~# insmod /volume1/dane/tn40xx.ko
insmod: ERROR: could not insert module /volume1/dane/tn40xx.ko: Unknown symbol in module

#dmesg
[  115.098302] tn40xx: Unknown symbol __fentry__ (err 0)
[  115.103362] tn40xx: Unknown symbol __stack_chk_fail (err 0)
[  115.108953] tn40xx: Unknown symbol pv_irq_ops (err 0)
[  115.114019] tn40xx: Unknown symbol _raw_spin_unlock (err 0)
[  115.119589] tn40xx: Unknown symbol alloc_pages_current (err 0)

 

 

OK, my fault, used wrong compiler version, can you re-download and try again ? 

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

I'm not very sure that DiskIdxMap is taken consideration, i need to further test. But in your case it makes sence to use something like 

 

SataPortMap=<number of disks in controller 1><number of disks in controller 2><number of disks in controller 3>

e.g. 

SataPortMap=188

 

 

 

I started redpill with only SATA0 = loader

LSI passthrough card

DiskIdxMap=1000

SataPortMap=18

SasIdxMap=0

 

root@Xpen70:~# fdisk -l
Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk model: SSD 850 EVO 250GB       
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x9bcfbffa

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sdb1          2048   4982527   4980480   2.4G fd Linux raid autodetect
/dev/sdb2       4982528   9176831   4194304     2G fd Linux raid autodetect
/dev/sdb3       9437184 488192351 478755168 228.3G fd Linux raid autodetect


Disk /dev/md0: 2.4 GiB, 2549940224 bytes, 4980352 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/zram0: 1.2 GiB, 1236271104 bytes, 301824 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram1: 1.2 GiB, 1236271104 bytes, 301824 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md1: 2 GiB, 2147418112 bytes, 4194176 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/md2: 228.3 GiB, 245121548288 bytes, 478753024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/vg1-syno_vg_reserved_area: 12 MiB, 12582912 bytes, 24576 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/vg1-volume_1: 228 GiB, 244813135872 bytes, 478150656 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/cachedev_0: 228 GiB, 244813135872 bytes, 478150656 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

 

DSM currently already installed on SSD.

 

I'm quite sure if I start from 0 with DSM install, it fails with no /dev/synoboot detected.

image.png.acfb1f71dd1b5c87c70df15653e783fd.png

 

lspci -k

 

0000:02:00.0 USB controller: VMware USB1.1 UHCI Controller
        DeviceName: usb
        Subsystem: VMware Device 1976
        Kernel driver in use: uhci_hcd
0000:02:01.0 USB controller: VMware USB2 EHCI Controller
        DeviceName: ehci
        Subsystem: VMware USB2 EHCI Controller
        Kernel driver in use: ehci-pci
0000:02:03.0 SATA controller: VMware SATA AHCI controller
        DeviceName: sata0
        Subsystem: VMware SATA AHCI controller
        Kernel driver in use: ahci
0000:03:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
        DeviceName: Ethernet0
        Subsystem: VMware Device 07d0
        Kernel driver in use: e1000e
0000:0b:00.0 RAID bus controller: Broadcom / LSI SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03)
        DeviceName: pciPassthru0
        Subsystem: Fujitsu Technology Solutions HBA Ctrl SAS 6G 0/1 [D2607]
        Kernel driver in use: mpt2sas
Link to post
Share on other sites

If I change to SataPortMap=48

 

image.png.0f507aadaf8deefb5b19d9551646ccc5.png

 

It really seems DiskIdxMap=1000 is totally ignored.

 

Edit :

If I switch to the opposit :

DiskIdxMap=0010

SataPortMap=84

 

DSM start as new install with no disk detected...

 

Edit 2 :

DiskIdxMap=0010

SataPortMap=48

 

image.png.7dc6cb00f39f38f83458528979eaa982.png

 

So I must keep SataPortMap=4x (I already tested with only SataPortMap=1x and DSM fails to install from fresh with only 1)

DiskIdxMap does not seems to do anything revelant.

 

Edited by Orphée
Link to post
Share on other sites

 

root@Xpen70:~# fdisk -l
Disk /dev/synoboot: 128 MiB, 134217728 bytes, 262144 sectors
Disk model: TYPE D 3SE
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: 0xf110ee87

Device         Boot  Start    End Sectors Size Id Type
/dev/synoboot1        2048 100351   98304  48M 83 Linux
/dev/synoboot2      100352 253951  153600  75M 83 Linux
/dev/synoboot3      253952 262143    8192   4M 83 Linux


Disk /dev/sde: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk model: SSD 850 EVO 250GB       
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x9bcfbffa

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sde1          2048   4982527   4980480   2.4G fd Linux raid autodetect
/dev/sde2       4982528   9176831   4194304     2G fd Linux raid autodetect
/dev/sde3       9437184 488192351 478755168 228.3G fd Linux raid autodetect


Disk /dev/md0: 2.4 GiB, 2549940224 bytes, 4980352 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/zram0: 1.2 GiB, 1236271104 bytes, 301824 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram1: 1.2 GiB, 1236271104 bytes, 301824 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md1: 2 GiB, 2147418112 bytes, 4194176 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/md2: 228.3 GiB, 245121548288 bytes, 478753024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/vg1-syno_vg_reserved_area: 12 MiB, 12582912 bytes, 24576 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/vg1-volume_1: 228 GiB, 244813135872 bytes, 478150656 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/cachedev_0: 228 GiB, 244813135872 bytes, 478150656 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

 

As you can see with SataPortMap=4x /dev/synoboot is detected with fdisk -l

Link to post
Share on other sites
3 minutes ago, Orphée said:

 


root@Xpen70:~# fdisk -l
Disk /dev/synoboot: 128 MiB, 134217728 bytes, 262144 sectors
Disk model: TYPE D 3SE
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: 0xf110ee87

Device         Boot  Start    End Sectors Size Id Type
/dev/synoboot1        2048 100351   98304  48M 83 Linux
/dev/synoboot2      100352 253951  153600  75M 83 Linux
/dev/synoboot3      253952 262143    8192   4M 83 Linux


Disk /dev/sde: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk model: SSD 850 EVO 250GB       
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x9bcfbffa

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sde1          2048   4982527   4980480   2.4G fd Linux raid autodetect
/dev/sde2       4982528   9176831   4194304     2G fd Linux raid autodetect
/dev/sde3       9437184 488192351 478755168 228.3G fd Linux raid autodetect


Disk /dev/md0: 2.4 GiB, 2549940224 bytes, 4980352 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/zram0: 1.2 GiB, 1236271104 bytes, 301824 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram1: 1.2 GiB, 1236271104 bytes, 301824 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/md1: 2 GiB, 2147418112 bytes, 4194176 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/md2: 228.3 GiB, 245121548288 bytes, 478753024 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/vg1-syno_vg_reserved_area: 12 MiB, 12582912 bytes, 24576 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/vg1-volume_1: 228 GiB, 244813135872 bytes, 478150656 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/mapper/cachedev_0: 228 GiB, 244813135872 bytes, 478150656 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

 

As you can see with SataPortMap=4x /dev/synoboot is detected with fdisk -l

 

Yes, actually when your are telling SataPortMap=48 the system will keep 4 slots for controller 1 and 8 slots for controller 2 thus controller 2 attached drives will start from like in your case. If you change that to SataPortMap=18 it will start from and the first will be occupied by synoboot

  • Like 1
Link to post
Share on other sites
4 minutes ago, pocopico said:

 

Yes, actually when your are telling SataPortMap=48 the system will keep 4 slots for controller 1 and 8 slots for controller 2 thus controller 2 attached drives will start from like in your case. If you change that to SataPortMap=18 it will start from and the first will be occupied by synoboot

Actually it seems not.

 

If I set SataPortMap=18, as already written, no /dev/synoboot.

I don't have this :

Disk /dev/synoboot: 128 MiB, 134217728 bytes, 262144 sectors
Disk model: TYPE D 3SE
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: 0xf110ee87

Device         Boot  Start    End Sectors Size Id Type
/dev/synoboot1        2048 100351   98304  48M 83 Linux
/dev/synoboot2      100352 253951  153600  75M 83 Linux
/dev/synoboot3      253952 262143    8192   4M 83 Linux

 

and DSM only boot because already installed on SSD disk.

If I start fresh install with SataPortMap=1(x)

Install fails at 5x%.

Setting it back to 4(x) make install works again.

 

Edit : I agree setting it to 18 makes SSD as disk 2, but no more /dev/synoboot

Edited by Orphée
Link to post
Share on other sites
21 minutes ago, pocopico said:

 

OK, my fault, used wrong compiler version, can you re-download and try again ? 

 

Link is the same? Because i have the same error

 

root@nas:/volume1/dane# rm tn40xx.ko
root@nas:/volume1/dane# wget https://github.com/pocopico/4.4.180plus-modules/raw/main/tn40xx.ko
--2021-10-07 11:00:11--  https://github.com/pocopico/4.4.180plus-modules/raw/main/tn40xx.ko
Resolving github.com... 140.82.121.4
Connecting to github.com|140.82.121.4|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://raw.githubusercontent.com/pocopico/4.4.180plus-modules/main/tn40xx.ko [following]
--2021-10-07 11:00:11--  https://raw.githubusercontent.com/pocopico/4.4.180plus-modules/main/tn40xx.ko
Resolving raw.githubusercontent.com... 185.199.111.133, 185.199.108.133, 185.199.109.133, ...
Connecting to raw.githubusercontent.com|185.199.111.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 6150984 (5.9M) [application/octet-stream]
Saving to: 'tn40xx.ko'

tn40xx.ko                             100%[========================================================================>]   5.87M  32.6MB/s    in 0.2s

2021-10-07 11:00:12 (32.6 MB/s) - 'tn40xx.ko' saved [6150984/6150984]

root@nas:/volume1/dane# insmod /volume1/dane/tn40xx.ko
insmod: ERROR: could not insert module /volume1/dane/tn40xx.ko: Unknown symbol in module


#dmesg
[ 1807.238227] tn40xx: Unknown symbol __fentry__ (err 0)
[ 1807.243326] tn40xx: Unknown symbol __stack_chk_fail (err 0)
[ 1807.248927] tn40xx: Unknown symbol pv_irq_ops (err 0)
[ 1807.254011] tn40xx: Unknown symbol _raw_spin_unlock (err 0)
[ 1807.259608] tn40xx: Unknown symbol alloc_pages_current (err 0)

 

Link to post
Share on other sites

@pocopicoSame error with SataPortMap=18. And as you can see, your driver load and see the 8 disks

image.thumb.png.ed3715574fd404204084b42743012dbd.png

Quote

Loading kmod #0 "libphy.ko" for pocopico.tg3 (args: )
[    1.980814] WARNING: module 'libphy' built without retpoline-enabled compiler, may affect Spectre v2 mitigation
Loading kmod #1 "tg3.ko" for pocopico.tg3 (args: )
Loading kmod #0 "mptbase.ko" for pocopico.mptsas (args: )
[    1.990015] Fusion MPT base driver 3.04.20
[    1.990390] Copyright (c) 1999-2008 LSI Corporation
Loading kmod #1 "mptscsih.ko" for pocopico.mptsas (args: )
Loading kmod #2 "mptsas.ko" for pocopico.mptsas (args: )
[    1.995030] Fusion MPT SAS Host driver 3.04.20
Loading kmod #3 "mptctl.ko" for pocopico.mptsas (args: )
[    1.997847] Fusion MPT misc device (ioctl) driver 3.04.20
[    1.998495] mptctl: Registered with Fusion MPT base driver
[    1.999221] mptctl: /dev/mptctl @ (major,minor=10,220)
Loading kmod #0 "mpt2sas.ko" for pocopico.mpt2sas (args: )
[    2.003700] mpt2sas version 14.100.00.00 loaded
[    2.004376] scsi1 : Fusion MPT SAS Host
[    2.006014] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (65983500 kB)
[    2.007517] mpt2sas 0000:03:00.0: irq 73 for MSI/MSI-X
[    2.008318] mpt2sas 0000:03:00.0: irq 74 for MSI/MSI-X
[    2.009533] mpt2sas 0000:03:00.0: irq 75 for MSI/MSI-X
[    2.010560] mpt2sas 0000:03:00.0: irq 76 for MSI/MSI-X
[    2.011535] mpt2sas 0000:03:00.0: irq 77 for MSI/MSI-X
[    2.012549] mpt2sas 0000:03:00.0: irq 78 for MSI/MSI-X
[    2.013544] mpt2sas 0000:03:00.0: irq 79 for MSI/MSI-X
[    2.014560] mpt2sas 0000:03:00.0: irq 80 for MSI/MSI-X
[    2.016542] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 73
[    2.017528] mpt2sas0-msix1: PCI-MSI-X enabled: IRQ 74
[    2.018549] mpt2sas0-msix2: PCI-MSI-X enabled: IRQ 75
[    2.019530] mpt2sas0-msix3: PCI-MSI-X enabled: IRQ 76
[    2.020531] mpt2sas0-msix4: PCI-MSI-X enabled: IRQ 77
[    2.021543] mpt2sas0-msix5: PCI-MSI-X enabled: IRQ 78
[    2.022534] mpt2sas0-msix6: PCI-MSI-X enabled: IRQ 79
[    2.023534] mpt2sas0-msix7: PCI-MSI-X enabled: IRQ 80
[    2.024551] mpt2sas0: iomem(0x00000000fd4f0000), mapped(0xffffc90008820000), size(65536)
[    2.026523] mpt2sas0: ioport(0x0000000000004000), size(256)
[    2.170709] mpt2sas0: Allocated physical memory: size(16690 kB)
[    2.171709] mpt2sas0: Current Controller Queue Depth(9979), Max Controller Queue Depth(10240)
[    2.172709] mpt2sas0: Scatter Gather Elements per IO(128)
[    2.202800] tsc: Refined TSC clocksource calibration: 2200.003 MHz
[    2.203758] Switching to clocksource tsc
[    2.234235] mpt2sas0: LSISAS2308: FWVersion(20.00.07.00), ChipRevision(0x05), BiosVersion(00.00.00.00)
[    2.234799] mpt2sas0: 0x1F38: Vendor(0x1000), Device(0x0087), SSVID(0x1028), SSDID(0x1F38)
[    2.235796] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
[    2.237883] mpt2sas0: sending port enable !!
[    2.242815] mpt2sas0: host_add: handle(0x0001), sas_addr(0x5b82a720d32ad200), phys(8)
[    2.255105] scsi 1:0:0:0: Direct-Access     ATA      ST8000NM0055-1RM112      SN05 PQ: 0 ANSI: 6
[    2.255830] scsi 1:0:0:0: SATA: handle(0x0009), sas_addr(0x4433221100000000), phy(0), device_name(0x5000c500c39d2d7a)
[    2.257836] scsi 1:0:0:0: SATA: enclosure_logical_id(0x5b82a720d32ad200), slot(3)
[    2.258979] scsi 1:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.260847] scsi 1:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.265442] sd 1:0:0:0: [sdb] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[    2.266804] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[    2.268292] scsi 1:0:1:0: Direct-Access     ATA      ST8000VN0022-2EL112      SC61 PQ: 0 ANSI: 6
[    2.268843] scsi 1:0:1:0: SATA: handle(0x000a), sas_addr(0x4433221101000000), phy(1), device_name(0x5000c500b62bce05)
[    2.270865] scsi 1:0:1:0: SATA: enclosure_logical_id(0x5b82a720d32ad200), slot(2)
[    2.271930] scsi 1:0:1:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.273908] scsi 1:0:1:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.274900] sd 1:0:0:0: [sdb] Write Protect is off
[    2.276304] sd 1:0:0:0: [sdb] Mode Sense: 7f 00 10 08
[    2.276838] usb 2-1: new full-speed USB device number 2 using uhci_hcd
[    2.277377] sd 1:0:1:0: [sdc] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[    2.277380] sd 1:0:1:0: [sdc] 4096-byte physical blocks
[    2.280446] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    2.286954] scsi 1:0:2:0: Direct-Access     ATA      ST8000VN0022-2EL112      SC61 PQ: 0 ANSI: 6
[    2.288913] scsi 1:0:2:0: SATA: handle(0x000b), sas_addr(0x4433221102000000), phy(2), device_name(0x5000c500b61f7abb)
[    2.290895] scsi 1:0:2:0: SATA: enclosure_logical_id(0x5b82a720d32ad200), slot(1)
[    2.291931] sd 1:0:1:0: [sdc] Write Protect is off
[    2.292002] scsi 1:0:2:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.292006] scsi 1:0:2:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.294354] sd 1:0:2:0: [sdd] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[    2.294356] sd 1:0:2:0: [sdd] 4096-byte physical blocks
[    2.297985] sd 1:0:1:0: [sdc] Mode Sense: 7f 00 10 08
[    2.298035] scsi 1:0:3:0: Direct-Access     ATA      ST8000VN004-2M2101       SC60 PQ: 0 ANSI: 6
[    2.298040] scsi 1:0:3:0: SATA: handle(0x000c), sas_addr(0x4433221103000000), phy(3), device_name(0x5000c500c02f0786)
[    2.298043] scsi 1:0:3:0: SATA: enclosure_logical_id(0x5b82a720d32ad200), slot(0)
[    2.298142] scsi 1:0:3:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.298146] scsi 1:0:3:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.300060] sd 1:0:3:0: [sde] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[    2.300062] sd 1:0:3:0: [sde] 4096-byte physical blocks
[    2.305022] sd 1:0:3:0: [sde] Write Protect is off
[    2.305026] sd 1:0:3:0: [sde] Mode Sense: 7f 00 10 08
[    2.306970] sd 1:0:3:0: [sde] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    2.308019] scsi 1:0:4:0: Direct-Access     ATA      ST8000NM0055-1RM112      SN05 PQ: 0 ANSI: 6
[    2.308025] scsi 1:0:4:0: SATA: handle(0x000d), sas_addr(0x4433221104000000), phy(4), device_name(0x5000c500b6aa83ab)
[    2.308028] scsi 1:0:4:0: SATA: enclosure_logical_id(0x5b82a720d32ad200), slot(7)
[    2.308126] scsi 1:0:4:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.308130] scsi 1:0:4:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.310602] sd 1:0:4:0: [sdf] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[    2.310605] sd 1:0:4:0: [sdf] 4096-byte physical blocks
[    2.312559] sd 1:0:2:0: [sdd] Write Protect is off
[    2.312562] sd 1:0:2:0: [sdd] Mode Sense: 7f 00 10 08
[    2.314956] sd 1:0:2:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    2.321978] scsi 1:0:5:0: Direct-Access     ATA      ST8000NM0055-1RM112      SN05 PQ: 0 ANSI: 6
[    2.322925] scsi 1:0:5:0: SATA: handle(0x000e), sas_addr(0x4433221105000000), phy(5), device_name(0x5000c500c3a145a0)
[    2.323891] scsi 1:0:5:0: SATA: enclosure_logical_id(0x5b82a720d32ad200), slot(6)
[    2.324008] scsi 1:0:5:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.324946] scsi 1:0:5:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.327470] sd 1:0:4:0: [sdf] Write Protect is off
[    2.328732] sd 1:0:4:0: [sdf] Mode Sense: 7f 00 10 08
[    2.329951] sd 1:0:5:0: [sdg] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[    2.329954] sd 1:0:5:0: [sdg] 4096-byte physical blocks
[    2.329962] sd 1:0:1:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    2.333446]  sdb: sdb1 sdb2 sdb5
[    2.336891] sd 1:0:4:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    2.341825] scsi 1:0:6:0: Direct-Access     ATA      ST8000NM0055-1RM112      SN05 PQ: 0 ANSI: 6
[    2.343280] scsi 1:0:6:0: SATA: handle(0x000f), sas_addr(0x4433221106000000), phy(6), device_name(0x5000c500c3a38bc5)
[    2.345269] scsi 1:0:6:0: SATA: enclosure_logical_id(0x5b82a720d32ad200), slot(5)
[    2.346736] scsi 1:0:6:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.348313] scsi 1:0:6:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.349410]  sde: sde1 sde2 sde5
[    2.353124] sd 1:0:5:0: [sdg] Write Protect is off
[    2.353728] sd 1:0:6:0: [sdh] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[    2.353731] sd 1:0:6:0: [sdh] 4096-byte physical blocks
[    2.357445] sd 1:0:5:0: [sdg] Mode Sense: 7f 00 10 08
[    2.362258] sd 1:0:5:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    2.369020] sd 1:0:3:0: [sde] Attached SCSI disk
[    2.372026] sd 1:0:0:0: [sdb] Attached SCSI disk
[    2.372990] scsi 1:0:7:0: Direct-Access     ATA      ST8000VN0022-2EL112      SC61 PQ: 0 ANSI: 6
[    2.375011] scsi 1:0:7:0: SATA: handle(0x0010), sas_addr(0x4433221107000000), phy(7), device_name(0x5000c500b6225371)
[    2.376041] scsi 1:0:7:0: SATA: enclosure_logical_id(0x5b82a720d32ad200), slot(4)
[    2.376345] sd 1:0:6:0: [sdh] Write Protect is off
[    2.376349] sd 1:0:6:0: [sdh] Mode Sense: 7f 00 10 08
[    2.377878]  sdd: sdd1 sdd2 sdd5
[    2.379273] scsi 1:0:7:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.379420] sd 1:0:6:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    2.383307] scsi 1:0:7:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.387332] sd 1:0:7:0: [sdi] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[    2.388625] sd 1:0:7:0: [sdi] 4096-byte physical blocks
[    2.393969] mpt2sas0: port enable: SUCCESS


As you can see, the fdisk -l see the 8 disk


 

Quote

 

root@FRAHQFIL503:~# fdisk -l
Disk /dev/synoboot: 128 MiB, 134217728 bytes, 262144 sectors
Disk model: TYPE D 3SE
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: 0xf110ee87

Device         Boot  Start    End Sectors Size Id Type
/dev/synoboot1        2048 100351   98304  48M 83 Linux
/dev/synoboot2      100352 253951  153600  75M 83 Linux
/dev/synoboot3      253952 262143    8192   4M 83 Linux


Disk /dev/sdb: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000NM0055-1RM112
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: 67FC142E-D83C-11EB-90D4-B496916F9E98

Device       Start         End     Sectors  Size Type
/dev/sdb1     2048     4982527     4980480  2.4G Linux RAID
/dev/sdb2  4982528     9176831     4194304    2G Linux RAID
/dev/sdb5  9453280 15627846239 15618392960  7.3T Linux RAID


Disk /dev/sde: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000VN004-2M2101
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: 6C43C76F-D83C-11EB-90D4-B496916F9E98

Device       Start         End     Sectors  Size Type
/dev/sde1     2048     4982527     4980480  2.4G Linux RAID
/dev/sde2  4982528     9176831     4194304    2G Linux RAID
/dev/sde5  9453280 15627846239 15618392960  7.3T Linux RAID


Disk /dev/sdd: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000VN0022-2EL112
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: 67126838-D83C-11EB-90D4-B496916F9E98

Device       Start         End     Sectors  Size Type
/dev/sdd1     2048     4982527     4980480  2.4G Linux RAID
/dev/sdd2  4982528     9176831     4194304    2G Linux RAID
/dev/sdd5  9453280 15627846239 15618392960  7.3T Linux RAID


Disk /dev/sdc: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000VN0022-2EL112
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: 6B62881B-D83C-11EB-90D4-B496916F9E98

Device       Start         End     Sectors  Size Type
/dev/sdc1     2048     4982527     4980480  2.4G Linux RAID
/dev/sdc2  4982528     9176831     4194304    2G Linux RAID
/dev/sdc5  9453280 15627846239 15618392960  7.3T Linux RAID


Disk /dev/sdf: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000NM0055-1RM112
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: 6BAD6B80-D83C-11EB-90D4-B496916F9E98

Device       Start         End     Sectors  Size Type
/dev/sdf1     2048     4982527     4980480  2.4G Linux RAID
/dev/sdf2  4982528     9176831     4194304    2G Linux RAID
/dev/sdf5  9453280 15627846239 15618392960  7.3T Linux RAID


Disk /dev/sdg: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000NM0055-1RM112
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: 6BBA0433-D83C-11EB-90D4-B496916F9E98

Device       Start         End     Sectors  Size Type
/dev/sdg1     2048     4982527     4980480  2.4G Linux RAID
/dev/sdg2  4982528     9176831     4194304    2G Linux RAID
/dev/sdg5  9453280 15627846239 15618392960  7.3T Linux RAID


Disk /dev/sdh: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000NM0055-1RM112
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: 69062E8B-D83C-11EB-90D4-B496916F9E98

Device       Start         End     Sectors  Size Type
/dev/sdh1     2048     4982527     4980480  2.4G Linux RAID
/dev/sdh2  4982528     9176831     4194304    2G Linux RAID
/dev/sdh5  9453280 15627846239 15618392960  7.3T Linux RAID


Disk /dev/sdi: 7.3 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: ST8000VN0022-2EL112
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: 69DAB975-D83C-11EB-90D4-B496916F9E98

Device       Start         End     Sectors  Size Type
/dev/sdi1     2048     4982527     4980480  2.4G Linux RAID
/dev/sdi2  4982528     9176831     4194304    2G Linux RAID
/dev/sdi5  9453280 15627846239 15618392960  7.3T Linux RAID

 

Edited by RedwinX
Link to post
Share on other sites

@pocopico at least with SataPortMap=28

 

/dev/synoboot is detected :

 

# fdisk -l
Disk /dev/synoboot: 128 MiB, 134217728 bytes, 262144 sectors
Disk model: TYPE D 3SE
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: 0xf110ee87

Device         Boot  Start    End Sectors Size Id Type
/dev/synoboot1        2048 100351   98304  48M 83 Linux
/dev/synoboot2      100352 253951  153600  75M 83 Linux
/dev/synoboot3      253952 262143    8192   4M 83 Linux


Disk /dev/sdc: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk model: SSD 850 EVO 250GB       
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x9bcfbffa

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sdc1          2048   4982527   4980480   2.4G fd Linux raid autodetect
/dev/sdc2       4982528   9176831   4194304     2G fd Linux raid autodetect
/dev/sdc3       9437184 488192351 478755168 228.3G fd Linux raid autodetect

 

Edit : completly removing DiskIdxMap value makes no difference.

Edit 2 : removing SasIdxMap does not change anything too.

 

as long as I have at least SataPortMap=2x

it is OK

 

Edit 3 :

If I remove DiskIdxMap / SataPortMap / SasIdxMap

No disk detected.

 

fdisk -l

DiskStation> fdisk -l
Disk /dev/synoboot: 128 MB, 134217728 bytes, 262144 sectors
16 cylinders, 255 heads, 63 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
/dev/synoboot2    6,62,57     15,205,62       100352     253951     153600 75.0M 83 Linux
/dev/synoboot3    15,205,63   16,81,1         253952     262143       8192 4096K 83 Linux
Disk /dev/sdae: 233 GB, 250059350016 bytes, 488397168 sectors
30401 cylinders, 255 heads, 63 sectors/track
Units: sectors of 1 * 512 = 512 bytes

Device   Boot StartCHS    EndCHS        StartLBA     EndLBA    Sectors  Size Id Type
/dev/sdae1    0,32,33     310,37,47         2048    4982527    4980480 2431M fd Linux raid autodetect
/dev/sdae2    310,37,48   571,58,63      4982528    9176831    4194304 2048M fd Linux raid autodetect
/dev/sdae3    587,111,37  1023,254,63    9437184  488192351  478755168  228G fd Linux raid autodetect

 

Edited by Orphée
Link to post
Share on other sites
9 minutes ago, RedwinX said:

@pocopicoSame error with SataPortMap=18. And as you can see, your driver load and see the 8 disks

image.thumb.png.ed3715574fd404204084b42743012dbd.png

Loading kmod #0 "libphy.ko" for pocopico.tg3 (args: )
[    1.980814] WARNING: module 'libphy' built without retpoline-enabled compiler, may affect Spectre v2 mitigation
Loading kmod #1 "tg3.ko" for pocopico.tg3 (args: )
Loading kmod #0 "mptbase.ko" for pocopico.mptsas (args: )
[    1.990015] Fusion MPT base driver 3.04.20
[    1.990390] Copyright (c) 1999-2008 LSI Corporation
Loading kmod #1 "mptscsih.ko" for pocopico.mptsas (args: )
Loading kmod #2 "mptsas.ko" for pocopico.mptsas (args: )
[    1.995030] Fusion MPT SAS Host driver 3.04.20
Loading kmod #3 "mptctl.ko" for pocopico.mptsas (args: )
[    1.997847] Fusion MPT misc device (ioctl) driver 3.04.20
[    1.998495] mptctl: Registered with Fusion MPT base driver
[    1.999221] mptctl: /dev/mptctl @ (major,minor=10,220)
Loading kmod #0 "mpt2sas.ko" for pocopico.mpt2sas (args: )
[    2.003700] mpt2sas version 14.100.00.00 loaded
[    2.004376] scsi1 : Fusion MPT SAS Host
[    2.006014] mpt2sas0: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED, total mem (65983500 kB)
[    2.007517] mpt2sas 0000:03:00.0: irq 73 for MSI/MSI-X
[    2.008318] mpt2sas 0000:03:00.0: irq 74 for MSI/MSI-X
[    2.009533] mpt2sas 0000:03:00.0: irq 75 for MSI/MSI-X
[    2.010560] mpt2sas 0000:03:00.0: irq 76 for MSI/MSI-X
[    2.011535] mpt2sas 0000:03:00.0: irq 77 for MSI/MSI-X
[    2.012549] mpt2sas 0000:03:00.0: irq 78 for MSI/MSI-X
[    2.013544] mpt2sas 0000:03:00.0: irq 79 for MSI/MSI-X
[    2.014560] mpt2sas 0000:03:00.0: irq 80 for MSI/MSI-X
[    2.016542] mpt2sas0-msix0: PCI-MSI-X enabled: IRQ 73
[    2.017528] mpt2sas0-msix1: PCI-MSI-X enabled: IRQ 74
[    2.018549] mpt2sas0-msix2: PCI-MSI-X enabled: IRQ 75
[    2.019530] mpt2sas0-msix3: PCI-MSI-X enabled: IRQ 76
[    2.020531] mpt2sas0-msix4: PCI-MSI-X enabled: IRQ 77
[    2.021543] mpt2sas0-msix5: PCI-MSI-X enabled: IRQ 78
[    2.022534] mpt2sas0-msix6: PCI-MSI-X enabled: IRQ 79
[    2.023534] mpt2sas0-msix7: PCI-MSI-X enabled: IRQ 80
[    2.024551] mpt2sas0: iomem(0x00000000fd4f0000), mapped(0xffffc90008820000), size(65536)
[    2.026523] mpt2sas0: ioport(0x0000000000004000), size(256)
[    2.170709] mpt2sas0: Allocated physical memory: size(16690 kB)
[    2.171709] mpt2sas0: Current Controller Queue Depth(9979), Max Controller Queue Depth(10240)
[    2.172709] mpt2sas0: Scatter Gather Elements per IO(128)
[    2.202800] tsc: Refined TSC clocksource calibration: 2200.003 MHz
[    2.203758] Switching to clocksource tsc
[    2.234235] mpt2sas0: LSISAS2308: FWVersion(20.00.07.00), ChipRevision(0x05), BiosVersion(00.00.00.00)
[    2.234799] mpt2sas0: 0x1F38: Vendor(0x1000), Device(0x0087), SSVID(0x1028), SSDID(0x1F38)
[    2.235796] mpt2sas0: Protocol=(Initiator,Target), Capabilities=(TLR,EEDP,Snapshot Buffer,Diag Trace Buffer,Task Set Full,NCQ)
[    2.237883] mpt2sas0: sending port enable !!
[    2.242815] mpt2sas0: host_add: handle(0x0001), sas_addr(0x5b82a720d32ad200), phys(8)
[    2.255105] scsi 1:0:0:0: Direct-Access     ATA      ST8000NM0055-1RM112      SN05 PQ: 0 ANSI: 6
[    2.255830] scsi 1:0:0:0: SATA: handle(0x0009), sas_addr(0x4433221100000000), phy(0), device_name(0x5000c500c39d2d7a)
[    2.257836] scsi 1:0:0:0: SATA: enclosure_logical_id(0x5b82a720d32ad200), slot(3)
[    2.258979] scsi 1:0:0:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.260847] scsi 1:0:0:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.265442] sd 1:0:0:0: [sdb] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[    2.266804] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[    2.268292] scsi 1:0:1:0: Direct-Access     ATA      ST8000VN0022-2EL112      SC61 PQ: 0 ANSI: 6
[    2.268843] scsi 1:0:1:0: SATA: handle(0x000a), sas_addr(0x4433221101000000), phy(1), device_name(0x5000c500b62bce05)
[    2.270865] scsi 1:0:1:0: SATA: enclosure_logical_id(0x5b82a720d32ad200), slot(2)
[    2.271930] scsi 1:0:1:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.273908] scsi 1:0:1:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.274900] sd 1:0:0:0: [sdb] Write Protect is off
[    2.276304] sd 1:0:0:0: [sdb] Mode Sense: 7f 00 10 08
[    2.276838] usb 2-1: new full-speed USB device number 2 using uhci_hcd
[    2.277377] sd 1:0:1:0: [sdc] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[    2.277380] sd 1:0:1:0: [sdc] 4096-byte physical blocks
[    2.280446] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    2.286954] scsi 1:0:2:0: Direct-Access     ATA      ST8000VN0022-2EL112      SC61 PQ: 0 ANSI: 6
[    2.288913] scsi 1:0:2:0: SATA: handle(0x000b), sas_addr(0x4433221102000000), phy(2), device_name(0x5000c500b61f7abb)
[    2.290895] scsi 1:0:2:0: SATA: enclosure_logical_id(0x5b82a720d32ad200), slot(1)
[    2.291931] sd 1:0:1:0: [sdc] Write Protect is off
[    2.292002] scsi 1:0:2:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.292006] scsi 1:0:2:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.294354] sd 1:0:2:0: [sdd] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[    2.294356] sd 1:0:2:0: [sdd] 4096-byte physical blocks
[    2.297985] sd 1:0:1:0: [sdc] Mode Sense: 7f 00 10 08
[    2.298035] scsi 1:0:3:0: Direct-Access     ATA      ST8000VN004-2M2101       SC60 PQ: 0 ANSI: 6
[    2.298040] scsi 1:0:3:0: SATA: handle(0x000c), sas_addr(0x4433221103000000), phy(3), device_name(0x5000c500c02f0786)
[    2.298043] scsi 1:0:3:0: SATA: enclosure_logical_id(0x5b82a720d32ad200), slot(0)
[    2.298142] scsi 1:0:3:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.298146] scsi 1:0:3:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.300060] sd 1:0:3:0: [sde] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[    2.300062] sd 1:0:3:0: [sde] 4096-byte physical blocks
[    2.305022] sd 1:0:3:0: [sde] Write Protect is off
[    2.305026] sd 1:0:3:0: [sde] Mode Sense: 7f 00 10 08
[    2.306970] sd 1:0:3:0: [sde] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    2.308019] scsi 1:0:4:0: Direct-Access     ATA      ST8000NM0055-1RM112      SN05 PQ: 0 ANSI: 6
[    2.308025] scsi 1:0:4:0: SATA: handle(0x000d), sas_addr(0x4433221104000000), phy(4), device_name(0x5000c500b6aa83ab)
[    2.308028] scsi 1:0:4:0: SATA: enclosure_logical_id(0x5b82a720d32ad200), slot(7)
[    2.308126] scsi 1:0:4:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.308130] scsi 1:0:4:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.310602] sd 1:0:4:0: [sdf] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[    2.310605] sd 1:0:4:0: [sdf] 4096-byte physical blocks
[    2.312559] sd 1:0:2:0: [sdd] Write Protect is off
[    2.312562] sd 1:0:2:0: [sdd] Mode Sense: 7f 00 10 08
[    2.314956] sd 1:0:2:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    2.321978] scsi 1:0:5:0: Direct-Access     ATA      ST8000NM0055-1RM112      SN05 PQ: 0 ANSI: 6
[    2.322925] scsi 1:0:5:0: SATA: handle(0x000e), sas_addr(0x4433221105000000), phy(5), device_name(0x5000c500c3a145a0)
[    2.323891] scsi 1:0:5:0: SATA: enclosure_logical_id(0x5b82a720d32ad200), slot(6)
[    2.324008] scsi 1:0:5:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.324946] scsi 1:0:5:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.327470] sd 1:0:4:0: [sdf] Write Protect is off
[    2.328732] sd 1:0:4:0: [sdf] Mode Sense: 7f 00 10 08
[    2.329951] sd 1:0:5:0: [sdg] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[    2.329954] sd 1:0:5:0: [sdg] 4096-byte physical blocks
[    2.329962] sd 1:0:1:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    2.333446]  sdb: sdb1 sdb2 sdb5
[    2.336891] sd 1:0:4:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    2.341825] scsi 1:0:6:0: Direct-Access     ATA      ST8000NM0055-1RM112      SN05 PQ: 0 ANSI: 6
[    2.343280] scsi 1:0:6:0: SATA: handle(0x000f), sas_addr(0x4433221106000000), phy(6), device_name(0x5000c500c3a38bc5)
[    2.345269] scsi 1:0:6:0: SATA: enclosure_logical_id(0x5b82a720d32ad200), slot(5)
[    2.346736] scsi 1:0:6:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.348313] scsi 1:0:6:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.349410]  sde: sde1 sde2 sde5
[    2.353124] sd 1:0:5:0: [sdg] Write Protect is off
[    2.353728] sd 1:0:6:0: [sdh] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[    2.353731] sd 1:0:6:0: [sdh] 4096-byte physical blocks
[    2.357445] sd 1:0:5:0: [sdg] Mode Sense: 7f 00 10 08
[    2.362258] sd 1:0:5:0: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    2.369020] sd 1:0:3:0: [sde] Attached SCSI disk
[    2.372026] sd 1:0:0:0: [sdb] Attached SCSI disk
[    2.372990] scsi 1:0:7:0: Direct-Access     ATA      ST8000VN0022-2EL112      SC61 PQ: 0 ANSI: 6
[    2.375011] scsi 1:0:7:0: SATA: handle(0x0010), sas_addr(0x4433221107000000), phy(7), device_name(0x5000c500b6225371)
[    2.376041] scsi 1:0:7:0: SATA: enclosure_logical_id(0x5b82a720d32ad200), slot(4)
[    2.376345] sd 1:0:6:0: [sdh] Write Protect is off
[    2.376349] sd 1:0:6:0: [sdh] Mode Sense: 7f 00 10 08
[    2.377878]  sdd: sdd1 sdd2 sdd5
[    2.379273] scsi 1:0:7:0: atapi(n), ncq(y), asyn_notify(n), smart(y), fua(y), sw_preserve(y)
[    2.379420] sd 1:0:6:0: [sdh] Write cache: enabled, read cache: enabled, supports DPO and FUA
[    2.383307] scsi 1:0:7:0: qdepth(32), tagged(1), simple(0), ordered(0), scsi_level(7), cmd_que(1)
[    2.387332] sd 1:0:7:0: [sdi] 15628053168 512-byte logical blocks: (8.00 TB/7.27 TiB)
[    2.388625] sd 1:0:7:0: [sdi] 4096-byte physical blocks
[    2.393969] mpt2sas0: port enable: SUCCESS
 

 

So you are only having the system partition failed issue ? Can you post the overview page ? 

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

 

So you are only having the system partition failed issue ? Can you post the overview page ? 

No, it missing one disk (drive 1), instead of it appear on the fdisk. You can forgot the system partition failed, there is no problem with that, just because the upgrade was not complete. If I have the 8 disk, I just rebuild the RAID and click on repair, and that's working fine (tested with RDM). 

My real problem is to know why there is one disk missing on DSM, because it was detected at boot, and present into fdisk list

As you can see, it missed one disk

image.thumb.png.6b4406c5b1057f4d1a9cbf85eabf741f.png

 

And FYI for VMXNET3 

image.thumb.png.7fe0a7b3b2f5a08dcec4964bdf67dd2d.png

Edited by RedwinX
Link to post
Share on other sites
5 minutes ago, RedwinX said:

No, it missing one disk (drive 1), instead of it appear on the fdisk. You can forgot the system partition failed, there is no problem with that, just because the upgrade was not complete. If I have the 8 disk, I just rebuild the RAID and click on repair, and that's working fine (tested with RDM). 

My real problem is to know why there is one disk missing on DSM, because it was detected at boot, and present into fdisk list

 

And FYI for VMXNET3 

image.thumb.png.7fe0a7b3b2f5a08dcec4964bdf67dd2d.png

 

Should be ok now

Link to post
Share on other sites
46 minutes ago, Orphée said:

It really seems DiskIdxMap=1000 is totally ignored.

 

Can you try DiskIdxMap=0F00 (which should be drive 17 for the fist controller, and 1 for the the 2nd)

Not that it's just an issue with interpreting the first hex digit of the two hex digit value.

 

I use this on Proxmox (virtual usb drive, no passthrough on my test rig):

    "SasIdxMap": "0",
    "SataPortMap": "66",
    "DiskIdxMap": "0600"

I did set the number of ports on each controller to 6, as I've read the claim that Proxmox would only suppot up to 6 drives (tbh, I never verified that claim)

 

update: I forget to mention that my sata drives start with drive 1 -> without these settings, they start at 7.

 

Update2: probably it makes sense to add the device list

lspci -k | grep -A2 -E '(SCSI|SATA)'
0000:00:1f.2 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
        Subsystem: Red Hat, Inc. Device 1100
        Kernel driver in use: ahci
--
0000:06:07.0 SATA controller: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] (rev 02)
        Subsystem: Red Hat, Inc. Device 1100
        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: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)

 

Edited by haydibe
Link to post
Share on other sites
5 minutes ago, haydibe said:

Can you try DiskIdxMap=0F00 (which should be drive 17 for the fist controller, and 1 for the the 2nd)

Not that it's just an issue with interpreting the first hex digit of the two hex digit value.

 

I use this on Proxmox (virtual usb drive, no passthrough on my test rig):



    "SasIdxMap": "0",
    "SataPortMap": "66",
    "DiskIdxMap": "0600"

I did set the number of ports on each controller to 6, as I've read the claim that Proxmox would only suppot up to 6 drives (tbh, I never verified that claim)

 

 

# fdisk -l
Disk /dev/synoboot: 128 MiB, 134217728 bytes, 262144 sectors
Disk model: TYPE D 3SE
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: 0xf110ee87

Device         Boot  Start    End Sectors Size Id Type
/dev/synoboot1        2048 100351   98304  48M 83 Linux
/dev/synoboot2      100352 253951  153600  75M 83 Linux
/dev/synoboot3      253952 262143    8192   4M 83 Linux


Disk /dev/sde: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Disk model: SSD 850 EVO 250GB       
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x9bcfbffa

Device     Boot   Start       End   Sectors   Size Id Type
/dev/sde1          2048   4982527   4980480   2.4G fd Linux raid autodetect
/dev/sde2       4982528   9176831   4194304     2G fd Linux raid autodetect
/dev/sde3       9437184 488192351 478755168 228.3G fd Linux raid autodetect

 

Same : DiskIdxMap=0F00 / SataPortMap=4 / SasIdxMap=0

 

I updated the ticket with my experiments :

https://github.com/RedPill-TTG/redpill-lkm/issues/19#issuecomment-937615881

Edited by Orphée
  • Like 1
Link to post
Share on other sites

Ok I catched why SataPortMap=1 did not work

Actually I'm dumb...

 

When you create a new VM

By default the first disk is set as SCSI disk

When you switch it to SATA, it automaticalty set it to SATA0:1

image.png.ed9bdbda9e0d8880c07956ba1a2b35a9.png

 

and of course if you set SataPortMap=1 with SATA0:1 value, disk is not detected...

Setting it back to SATA0:0 make it works again.

 

But still, always at first position disk 1

 

Edited by Orphée
  • Like 1
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.