Jay Y

Members
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Jay Y

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yup, all in IT mode. Sorry, I wrote that wrong; not sure what I was thinking then! Its 16 ports and the others have 8 ports each. In addition the board has 10 SATA ports of which I used 4.
  2. Ultimately this turned out to be a problem bigger than the others! I tried some combinations of disk counts but the system was just not stable and would occasionally lose all config and start setup on reboot. That risk was not acceptable so I gave up on using Xpenology for this box and went with FreeNAS instead. I did build out one 24 bay Xpenology device next. Did that initially with the 918+ loader but that kept having issues as well so I switched to DS3617 and that runs wonderfully. I've used the 3617 in the past as well and now just trust it to work stably long term. Thanks for the help. Hopefully a fix will be found by someone creating a loader for the more pro syno devices out there.
  3. I turned off hyper threading on the CPU. On command line cores was 8, in DSM it was 4 if I recall right
  4. I've been using Xpenology boxes for a few years now and decided to build a new, bigger box. So now I'm building a 36 Bay unit, plus another 24 bay and 12 bay on the way next. This is the problem: I started to plug in drives on my NAS and realized that HDD numbers start from 11 and go on sequentially, irrespective of which bay I put the next drive in. To be clear, I put my first drive in Bay 1 and that gets recorded as disk 11. Now, if I put the next drive in Bay 10 that is still shown as disk 12 in storage manager. This is where it gets worse: I then put 10 drives in from Bay 1 through Bay 10, and disk numbers went up sequentially. If I then remove a drive from Bay 5, (Disk 15) and add a new drive in Bay 11 that shows up as disk 15 in storage manager. If I then go back and put a drive in Bay 5, that now shows as disk 16! I have searched through this forum and attempted lots of google-fu to figure this out with combinations of SataPortMap, DiskIdxMap, SasIdxMap and Sata_remap. I've restarted, re-configured and rebuilt this box over a dozen times in the last 4 days. For the sake of completeness I will include a list of forum posts, at this end of this post, that I've referenced in trying to solve this. I started with setting this up as a 918+ box but couldn't get that to install so switched over to 3617xs. I am asking for help with these two things: Consistent, predictable drive numbers (Preferably starting at disk 1): I know there are lots of posts about not caring for sequence numbers and that's what I did in the past with smaller boxes. However, this is a large NAS and I want to build it for uptime and need the ability to be able to identify correct drives to be able to pull out, replace or add new drives as needed without bringing the machine down. At minimum, I need consistent drive numbers (So disk 15 remains disk 15 and does not become disk 16, etc). I worry a lot about pulling the wrong drive out since the sequence numbers have a lot of potential to get jumbled up. Finally, I will obviously run out of disk numbers as I keep adding disks! Setting up the boot loader with defaults for 36 bays: Right now I am editing config files (/etc/synoinfo.conf and /etc.defaults/synoinfo.conf) to convert this to a 36 Bay unit after DSM has installed. Is it possible to configure the boot loader so it gets configured as a 36 Bay unit from the start? I found this post for doing exactly this for a 918+:Can I somehow use the same approach with my DS3617XS? I opened up the extra.lzma but that does not have synoinfo_override.conf and jun.patch also does not have the relevant data. My config: DSM Version: DSM 6.2.2-24922 Update 4 Loader: 1.03b for DS3617xs CPU: Intel Xeon E5-2630L V3 RAM: 128 GB, DDR4 Motherboard: Supermicro X10SRH-CF HBAs: LSI 3008 (Built into motherboard - 8 SAS Ports) LSI 3224 (LSI 9305-16i) (Add on with 64 SAS Ports) LSI 3008 (Dell H330 HBA) (Add on with 8 SAS Ports) Motherboard also has 10 SATA ports (Only 4 used in my config) Backplanes: Supermicro BPN-SAS-846A and BPN-SAS-826A Relevant outputs from lspci -v 0000:00:11.4 SATA controller: Intel Corporation C610/X99 series chipset sSATA Controller [AHCI mode] (rev 05) (prog-if 01) Subsystem: Super Micro Computer Inc Device 0838 Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 65 I/O ports at f110 [size=8] I/O ports at f100 [size=4] I/O ports at f0f0 [size=8] I/O ports at f0e0 [size=4] I/O ports at f020 [size=32] Memory at fbd38000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [70] Power Management version 3 Capabilities: [a8] SATA HBA v1.0 Kernel driver in use: ahci 0000:00:1f.2 SATA controller: Intel Corporation C610/X99 series chipset 6-Port SATA Controller [AHCI mode] (rev 05) (prog-if 01) Subsystem: Super Micro Computer Inc Device 0838 Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 66 I/O ports at f070 [size=8] I/O ports at f060 [size=4] I/O ports at f050 [size=8] I/O ports at f040 [size=4] I/O ports at f000 [size=32] Memory at fbd32000 (32-bit, non-prefetchable) [size=2K] Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [70] Power Management version 3 Capabilities: [a8] SATA HBA v1.0 Kernel driver in use: ahci 0000:01:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02) Subsystem: Super Micro Computer Inc AOC-S3008L-L8e Flags: bus master, fast devsel, latency 0, IRQ 26 I/O ports at e000 [size=256] Memory at fbb40000 (64-bit, non-prefetchable) [size=64K] Memory at fbb00000 (64-bit, non-prefetchable) [size=256K] Expansion ROM at fba00000 [disabled] [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [68] Express Endpoint, MSI 00 Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=96 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [1e0] #19 Capabilities: [1c0] Power Budgeting <?> Capabilities: [190] #16 Capabilities: [148] Alternative Routing-ID Interpretation (ARI) Kernel driver in use: mpt3sas 0000:03:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3224 PCI-Express Fusion-MPT SAS-3 (rev 01) Subsystem: Broadcom / LSI Device 3190 Flags: bus master, fast devsel, latency 0, IRQ 34 I/O ports at d000 [size=256] Memory at fb900000 (64-bit, non-prefetchable) [size=64K] Expansion ROM at fb800000 [disabled] [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [68] Express Endpoint, MSI 00 Capabilities: [d0] Vital Product Data Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=96 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [1e0] #19 Capabilities: [1c0] Power Budgeting <?> Capabilities: [190] #16 Capabilities: [148] Alternative Routing-ID Interpretation (ARI) Kernel driver in use: mpt3sas 0000:04:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS3008 PCI-Express Fusion-MPT SAS-3 (rev 02) Subsystem: Dell HBA330 Adapter Flags: bus master, fast devsel, latency 0, IRQ 40 I/O ports at c000 [size=256] Memory at fb700000 (64-bit, non-prefetchable) [size=64K] Memory at fb600000 (64-bit, non-prefetchable) [size=1M] Expansion ROM at fb500000 [disabled] [size=1M] Capabilities: [50] Power Management version 3 Capabilities: [68] Express Endpoint, MSI 00 Capabilities: [a8] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [c0] MSI-X: Enable+ Count=96 Masked- Capabilities: [100] Advanced Error Reporting Capabilities: [1e0] #19 Capabilities: [1c0] Power Budgeting <?> Capabilities: [190] #16 Capabilities: [150] Single Root I/O Virtualization (SR-IOV) Capabilities: [148] Alternative Routing-ID Interpretation (ARI) Kernel driver in use: mpt3sas 0001:08:00.0 Non-VGA unclassified device: Marvell Technology Group Ltd. 88SE9235 PCIe 2.0 x2 4-port SATA 6 Gb/s Controller (rev ff) (prog-if ff) !!! Unknown header type 7f These are the settings I've tried in grub.cfg ==> Currently in use set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=01 SataPortMap=4' ==> DSM fails and reinstalls when I attempt to increase drive count to 36 set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=0C SataPortMap=2421 SasIdxMap=0' ==> Similar behavior to current state set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=2428 SataPortMap=9 SasIdxMap=0' set sata_args='sata_uid=1 sata_pcislot=5 synoboot_satadom=1 DiskIdxMap=01 SataPortMap=4 SasIdxMap=0xfffffff8 sata_remap=10>0' I also attempted lots of combinations of sata_remap via the grub command line after reading this post: I specifically tried various combinations of this command via grub after DSM had already been installed append "sata_remap=10>0:0>10" These are some of the other posts I've gone through: https://hedichaibi.com/fix-xpenology-problems-viewing-internal-hard-drives-as-esata-hard-drives/ https://gugucomputing.wordpress.com/2018/11/11/experiment-on-sata_args-in-grub-cfg/
  5. Did you ever find out what this initial password is? I used to know it a while back and now I've forgotten!
  6. Partial SUCCESS!! (SMART issues!) Finally Thanks a lot to fa2k for helping along the way. I took driver source from linux kernel 3.11 (idea from fa2k), compared with older driver code and made updates to the code to fix compatibility issues and then it compiled. After that, the driver was still crashing (DMA Read errors) so I had to do more research and found a hint online that disabling intel IOMMU would fix those issues. For that I added a kernel boot parameter (intel_iommu=off) in grub config and now my machine reads the adapter and all disks connected to it. Problem now is that DSM UI doesn't seem to be able to read SMART data from the disks attached to the megaraid adapter. Smart information is available if I query via command line. Console also shows problems with the raid volume I created (md1: Failed to send sync event: (sync type: resync, finish: 0, interrupt: 0)), but no errors are reported in DSM UI (Resolved). Anyone know why this might be happening? I'm going to experiment some more and try and use newer versions of driver code to hopefully fix the above and get more stable drivers (and also try building with IOMMU disabled in build options so grub changes are not needed). Once I find an acceptable (to me) driver I will upload it here for others to use. This should enable all Dell (And other) RAID cards that use the SAS 3008 chipset once they are put in HBA mode (which is just a setting with the newer Dell cards).
  7. I gave this a shot and no dice for me. Build fails for megaraid.c - error: implicit declaration of function ‘pci_alloc_dev’ [-Werror=implicit-function-declaration] However you're making it work, just fix those symbol errors for me
  8. Ignore the request for source. Better to get your thoughts on fixing that issue with missing symbols. I'll get the source for 3.11 and try compiling myself in the meantime.
  9. Still failing with the same errors as before. I put in your version of the vow_pvscsi driver and now that is failing too: [ 2.314830] vmw_pvscsi: Unknown symbol pv_irq_ops (err 0) [ 2.316878] megaraid cmm: 2.20.2.7 (Release Date: Sun Jul 16 00:01:03 EST 2006) [ 2.319068] megaraid: 2.20.5.1 (Release Date: Thu Nov 16 15:32:35 EST 2006) [ 2.321165] megaraid: Unknown symbol pv_cpu_ops (err 0) [ 2.321169] megaraid: Unknown symbol pv_irq_ops (err 0) [ 2.325482] Fusion MPT base driver 3.04.20 [ 2.325483] Copyright (c) 1999-2008 LSI Corporation [ 2.329726] Fusion MPT SPI Host driver 3.04.20 [ 2.331939] Fusion MPT SAS Host driver 3.04.20 [ 2.334126] Fusion MPT misc device (ioctl) driver 3.04.20 [ 2.334170] mptctl: Registered with Fusion MPT base driver [ 2.334172] mptctl: /dev/mptctl @ (major,minor=10,220) [ 2.336292] megaraid_sas: Unknown symbol pv_irq_ops (err 0) I got a hold of the driver from Kernel 3.16.62 a few hours back and was about to run a diff to see what's changed and if are any dependency issues. When you see this, mind sharing the 3.11 source you got? I can try compiling with the environment I have setup on my end and see if the dependencies can be worked out.
  10. I've done this too many times and may be starting to lose track a bit... I took the driver from 4.4.x source and compiled it against current kernel. If I remember right, it doesn't build because of missing dependencies. Went down the rabbit hole of trying to fix those one at a time until I got to missing kernel dependencies and then gave up. I also tried DS918+ with the 1.04b Loader and the image just doesn't come up to even setup. Console shows lots of error messages, loading of drivers and errors appears to be all out of order. Lots of crashes (I think drivers) etc. Don't know what's with that image that does not sit right. Will give it another shot with a clean disk later today and see if I can work through the errors.
  11. Thanks for sharing those notes for your environment. I've tried building against that source already and that driver doesn't recognize my adapter. PCI ID for this adapter is 005f. In the LSI official drivers it is defined in megaraid_sas.h as: #define PCI_DEVICE_ID_LSI_FURY 0x005f I've attempted using the LSI drivers but they are written against newer kernel and so far I've not been able to get them to work (driver crashes on load or doesn't build). Going to try a bit more to search for back ports etc.
  12. Is it possible for you to share where you're getting the linux kernel source to compile these drivers? That way I can try myself. I'm assuming I can reuse the toolchain for bromolow. Are there any other config settings you're using to run make that you may be able to share? I looked into the kernel source here: https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/22259branch/broadwell-source/linux-3.10.x.txz/download Don't know if this is the correct version. Unfortunately, the megaraid driver bundled there is the same old version which does not have PCI IDs for my card....
  13. This time 3 of the drivers failed to load. Dmesg output below: [ 2.322299] megaraid_mbox: Unknown symbol pv_irq_ops (err 0) [ 2.324274] megaraid: Unknown symbol pv_cpu_ops (err 0) [ 2.324278] megaraid: Unknown symbol pv_irq_ops (err 0) [ 2.328565] Fusion MPT base driver 3.04.20 [ 2.328566] Copyright (c) 1999-2008 LSI Corporation [ 2.332837] Fusion MPT SPI Host driver 3.04.20 [ 2.335013] Fusion MPT SAS Host driver 3.04.20 [ 2.337189] Fusion MPT misc device (ioctl) driver 3.04.20 [ 2.337232] mptctl: Registered with Fusion MPT base driver [ 2.337232] mptctl: /dev/mptctl @ (major,minor=10,220) [ 2.339359] megaraid_sas: Unknown symbol pv_irq_ops (err 0) [ 2.343067] mpt2sas version 20.00.00.00 loaded [ 2.347259] mpt3sas version 13.00.00.00 loaded
  14. Should I be getting an updated version of megaraid_mbox as well? Trying the others now
  15. Pulled that machine apart to try something else! Will test new drivers in the next hour and report back. Just to be clear, I am using the megaraid drivers you supplied and NOT using your mpt* drivers (using the default ones in the image) Also looked at that Crossflashing link. The problem still remains that all these instructions call for using a jumper on the card and mine has absolutely no physical jumpers on it.