Jump to content
XPEnology Community

The_Mole

Rookie
  • Posts

    3
  • Joined

  • Last visited

Everything posted by The_Mole

  1. Hi, I've been trying to add a Mellanox MCX311A to the system, and at least in TC, all looks good: lspci -v 07:00.0 Ethernet controller: Mellanox Technologies MT27500 Family [ConnectX-3] Subsystem: Mellanox Technologies Device 0055 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f7900000 (64-bit, non-prefetchable) [size=1M] Memory at fbf000000 (64-bit, prefetchable) [size=8M] Expansion ROM at f7800000 [disabled] [size=1M] Capabilities: [40] Power Management version 3 Capabilities: [48] Vital Product Data Capabilities: [9c] MSI-X: Enable+ Count=128 Masked- Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [c0] Vendor Specific Information: Len=18 <?> Capabilities: [100] Alternative Routing-ID Interpretation (ARI) Capabilities: [148] Device Serial Number e4-1d-2d-03-00-dc-39-70 Capabilities: [154] Advanced Error Reporting Capabilities: [18c] #19 Kernel driver in use: mlx4_core dmesg |grep mlx [ 1.539474] mlx4_core: Mellanox ConnectX core driver v4.0-0 [ 1.539498] mlx4_core: Initializing 0000:07:00.0 [ 8.793114] mlx4_core 0000:07:00.0: DMFS high rate steer mode is: disabled performance optimized steering [ 8.793495] mlx4_core 0000:07:00.0: 16.000 Gb/s available PCIe bandwidth, limited by 5.0 GT/s PCIe x4 link at 0000:00:1c.4 (capable of 31.504 Gb/s with 8.0 GT/s PCIe x4 link) [ 8.838848] mlx4_en: Mellanox ConnectX HCA Ethernet driver v4.0-0 [ 8.839075] mlx4_en 0000:07:00.0: Activating port:1 [ 8.841547] mlx4_en: 0000:07:00.0: Port 1: Using 8 TX rings [ 8.841549] mlx4_en: 0000:07:00.0: Port 1: Using 8 RX rings [ 8.842023] mlx4_en: 0000:07:00.0: Port 1: Initializing port [ 8.842589] mlx4_en 0000:07:00.0: registered PHC clock [ 30.145433] mlx4_en: eth4: Steering Mode 1 ifconfig eth4 Link encap:Ethernet HWaddr E4:1D:2D:DC:39:70 inet addr:192.168.11.51 Bcast:192.168.11.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:328 errors:0 dropped:102 overruns:0 frame:0 TX packets:2 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:34448 (33.6 KiB) TX bytes:684 (684.0 B) God's in his heaven — All's right with the world. However, after I build the loader and boot into DSM, it looks like this: lspci -v 0000:07:00.0 Class 0200: Device 15b3:1003 Subsystem: Device 15b3:0055 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f7900000 (64-bit, non-prefetchable) [size=1M] Memory at fbf000000 (64-bit, prefetchable) [size=8M] Expansion ROM at f7800000 [disabled] [size=1M] Capabilities: [40] Power Management version 3 Capabilities: [48] Vital Product Data Capabilities: [9c] MSI-X: Enable+ Count=128 Masked- Capabilities: [60] Express Endpoint, MSI 00 Capabilities: [c0] Vendor Specific Information: Len=18 <?> Capabilities: [100] Alternative Routing-ID Interpretation (ARI) Capabilities: [148] Device Serial Number e4-1d-2d-03-00-dc-39-70 Capabilities: [154] Advanced Error Reporting Capabilities: [18c] Secondary PCI Express Kernel driver in use: mlx4_core dmesg | grep mlx [ 8.244251] mlx4_core: Mellanox ConnectX core driver v2.2-1 (Feb, 2014) [ 8.244454] mlx4_core: Initializing 0000:07:00.0 [ 15.451927] mlx4_core 0000:07:00.0: PCIe BW is different than device's capability [ 15.452082] mlx4_core 0000:07:00.0: PCIe link speed is 5.0GT/s, device supports 8.0GT/s [ 15.452234] mlx4_core 0000:07:00.0: PCIe link width is x4, device supports x4 Seems like DSM doesn't load mlx4_en and I'm a bit stuck, here. Can anyone help me out?
  2. Hi there, you guys might be able to save me some time, figuring this out: System is a Fujitsu Esprimo P720 E90, running on a Xeon E3-1275L V3 (Haswell based). There are 13 disks in the system - 5 attached to the mainboard, 8 attached to a Fujitsu D2607-A21 SAS controller (LSI SAS2008), crossflashed to 9211-8i in IT Mode. Another one of those controllers is sitting there empty until I need to add more space. Currently, I'm running my install as DS3615xs on 6.2.3-25426 with Jun's loader 1.03b. I tried upgrading to Redpill as DS918+ on 7.1.0-42661 to enable video encoding but I only get the 5 disks on the mainboard to show up. The ones on the SAS controller that are working with mpt2sas-driver on 6.2.3 do not appear on 7.1.0, even if I add the driver to Redpill. Latest approach was: ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh serialgen DS918+ ./rploader.sh identifyusb now ./rploader.sh satamap now tce-load -wi nano #because I hate vi nano user_config.json #edited to hardware MAC, a different 918+ serial and set maxdisks to 24 ./rploader.sh ext apollolake-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt2sas/rpext-index.json ./rploader.sh build apollolake-7.0.1-42218 ./rploader.sh clean now ./rploader.sh ext apollolake-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/mpt2sas/rpext-index.json ./rploader.sh build apollolake-7.1.0-42661 ./rploader.sh clean now; rm -rf /mnt/sdb3/auxfiles; rm -rf /home/tc/custom-module; ./rploader.sh backup now; sudo reboot Output from lspci -k (on 6.2.3) - Kernel driver won't show up on 7.1.0: 0000:01:00.0 Class 0104: Device 1000:0072 (rev 02) Subsystem: Device 1734:1177 Kernel driver in use: mpt2sas 0000:03:00.0 Class 0104: Device 1000:0072 (rev 03) Subsystem: Device 1734:1177 Kernel driver in use: mpt2sas Output from ll /sys/block (on 6.2.3) - only sda-sde appear on 7.1.0: lrwxrwxrwx 1 root root 0 Jun 17 14:47 sda -> ../devices/pci0000:00/0000:00:1f.2/ata1/host0/target0:0:0/0:0:0:0/block/sda lrwxrwxrwx 1 root root 0 Jun 17 14:47 sdb -> ../devices/pci0000:00/0000:00:1f.2/ata2/host1/target1:0:0/1:0:0:0/block/sdb lrwxrwxrwx 1 root root 0 Jun 17 14:47 sdc -> ../devices/pci0000:00/0000:00:1f.2/ata3/host2/target2:0:0/2:0:0:0/block/sdc lrwxrwxrwx 1 root root 0 Jun 17 14:47 sdd -> ../devices/pci0000:00/0000:00:1f.2/ata4/host3/target3:0:0/3:0:0:0/block/sdd lrwxrwxrwx 1 root root 0 Jun 17 14:47 sde -> ../devices/pci0000:00/0000:00:1f.2/ata5/host4/target4:0:0/4:0:0:0/block/sde lrwxrwxrwx 1 root root 0 Jun 17 14:47 sdh -> ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host7/port-7:0/end_device-:0/target7:0:0/7:0:0:0/block/sdh lrwxrwxrwx 1 root root 0 Jun 17 14:47 sdi -> ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host7/port-7:1/end_device-:1/target7:0:1/7:0:1:0/block/sdi lrwxrwxrwx 1 root root 0 Jun 17 14:47 sdj -> ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host7/port-7:2/end_device-:2/target7:0:2/7:0:2:0/block/sdj lrwxrwxrwx 1 root root 0 Jun 17 14:47 sdk -> ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host7/port-7:3/end_device-:3/target7:0:3/7:0:3:0/block/sdk lrwxrwxrwx 1 root root 0 Jun 17 14:47 sdl -> ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host7/port-7:4/end_device-:4/target7:0:4/7:0:4:0/block/sdl lrwxrwxrwx 1 root root 0 Jun 17 14:47 sdm -> ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host7/port-7:5/end_device-:5/target7:0:5/7:0:5:0/block/sdm lrwxrwxrwx 1 root root 0 Jun 17 14:47 sdn -> ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host7/port-7:6/end_device-:6/target7:0:6/7:0:6:0/block/sdn lrwxrwxrwx 1 root root 0 Jun 17 14:47 sdo -> ../devices/pci0000:00/0000:00:1c.4/0000:03:00.0/host7/port-7:7/end_device-:7/target7:0:7/7:0:7:0/block/sdo I'd appreciate any ideas on how to get those disks on the SAS controller to show up on 7.1.0. Thanks for your time.
  3. Hey there, this has been asked a couple of times but the only answers (if someone answered at all) were like, "Why bother? It works." In the picture above, both installations work. My inner monk (as well as my boss) prefer the right cabinet, however. In the following example I'll refer to a 10-bay system, if your setup is different, you can easily edit the numbers. I assume, you have successfully installed XPEnology on your box, following Polanskiman's tutorial. If you encountered any problems with drives not being recognized, or displayed as eSATA, etc. you checked Hedii's guide, as well. Still, your drives show up like this, maybe because your chipset would support 6 drives but your mainboard only offers 4 connectors. Drives 1,3,5,6 are connected to the mainboard, drives 7-10 to an additional 4-port controller, drives 11 and 12 to another 2-port controller. Drives 2 and 4 look like this in your dmesg: [ 1.835796] ata1: SATA max UDMA/133 abar m2048@0xfe525000 port 0xfe525100 irq 47 [ 1.835802] ata2: DUMMY [ 1.835806] ata3: SATA max UDMA/133 abar m2048@0xfe525000 port 0xfe525200 irq 47 [ 1.835807] ata4: DUMMY [ 1.835812] ata5: SATA max UDMA/133 abar m2048@0xfe525000 port 0xfe525300 irq 47 [ 1.835813] ata6: SATA max UDMA/133 abar m2048@0xfe525000 port 0xfe525400 irq 47 Playing around with internalportcfg (Hedii's guide) did not help you, getting rid of these "DUMMY" ports. Luckily Jun's loader has a feature called "sata_remap", mentioned here and here, that - well - does what it says. To fill the gaps, you can remap the drives from your 2-port controller. Reboot and press "C" in the GRUB menu. (See Polanskiman's guide "Step 7" and "Note 4" if you need help). At the command line enter: append "sata_remap=10>1:11>3:1>10:3>11" Be aware, that counting starts at 0, here. 10>1 will remap drive 11 to 2, 11>3 will remap drive 12 to 4, etc. After the next reboot, it will look like this: As you can see, the drives are now numbered sequentially from 1 to 10 with the two DUMMYs on ports 11 and 12. Now it's easy to hide them. Like in Hedii's guide open an SSH connection to your NAS and edit as follows: # first file to modify vi /etc/synoinfo.conf # second file to modify vi /etc.defaults/synoinfo.conf # In each file look for the line maxdisks="12" # and change it to maxdisks="10" Reboot and you finally have a 10-bay box displaying 10 sequentially numbered drives: Hope, this will help one or the other. Best Regards, The_Mole
×
×
  • Create New...