Jay Y

  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About Jay Y

  • Rank

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.
  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 f
  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
  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: (Release Date: Sun Jul 16 00:01:03 EST 2006) [ 2.319068] megaraid: (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 Corpor
  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 k
  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
  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 Fu
  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.