Panozguy

Forgot to mention - I of course tried find.synology.com and the Syno Assistant. No dice on either and again, the normal IP address I have assigned to the unit doesn't show on Advanced IP Scanner either.

Hello - I have had a fully working NAS for many months with no hardware or software changes. I needed to move some things around in my rack, so I shut DSM down properly via the GUI. Moved the hardware where it needed to go, fired it back up. I see the normal GRUB bootloader screen and gives the standard loader info. However, I can now no longer find, ping, or even locate the NAS at all on the network. It's like the network stack is dead. For reference - DSM version is 6.2.3.xxxx (can't recall the exact subversion). Jun's bootloader 1.03b for 3617+ on baremetal Chenbro NR12000 hardware (12 cores, 16GB of RAM). PCI-E NIC ports are Mellanox 10gig which have been working fine for many months. I never update DSM (no need to - it does all I need). No one else has access to the machine, or login information. When running, DSM does also see the NR12000's onboard NIC ports as LAN 3 and 4 IIRC, but I never configured them - why would I when I have 2 x 10gig fiber ports already running, lol? Nevertheless I've tried those 1 gig copper ports in an effort to just see if I can get any type of networking running. Advanced IP scanner doesn't show any IP's being assigned to any of the NICs (fiber or copper). It seems like maybe the bootloader is dying before the network drivers are installed. I don't see any link light on either Mellanox port and I feel like I should be. Normally on a Windows system this means the driver hasn't been loaded yet. How can I troubleshoot the network stack? Don't have a null modem cable but I do have a Cisco console cable and an APC UPS serial cable if that helps I've reseated the Mellanox card multiple times, changed DAC cables, tried new upstream switch ports. I have two more known good identical Mellanox cards I'll try to swap in and see if that makes any difference. The only thing I can think of is that I may have changed the USB port that my boot drive was connected to. Would that have made any difference? It's still bootable from BIOS but would it somehow kill GRUB's ability to load DSM? Thank you - I can try to provide additional info but it's challenging without DSM loading.

I got it worked out, but I’m glad that if someone asks in the future it will be here. I just didn’t want to be the first noob guy who hadn’t even attempted some research. Thank you guys.

Yes, it actually worked fine on the 3617xs as well. Guess I missed the part somewhere where you have to actually make the primary connection with a normal NIC. All good, I learned something. Thanks for the offer!

I think I figured it out. I reconnected the server via the standard gig Ethernet ports and installed as a 3615xs. When it rebooted, it now shows 10 gig ports. Now to go back and try it as a 3617xs instead.

Hi folks - I've done quite a bit of searching but just can't quite seem to find the answer I'm looking for. TL;DR - need a hint on what loader or extras are needed for Connect-X2 10gbe NIC support. Let me get the basics out of the way: 1 - TYAN SS512 motherboard, E3-1230V2 CPU, 16GB ECC, integrated LSI 2008 SAS, integrated 2 x Intel i350 NICs. 2 - I am a current Synology hardware owner (DS918+) so I know my way around DSM. I'm also an IT professional and know my way around hardware and OS's pretty well. 3 - A week ago, I installed Xpenology via a lot of reading here (thank you all!). Used 1.03b loader for DS3617xs which is practically a direct match for my hardware, and the latest 6.2.3.xxx version of DSM. Absolutely zero issues. Installed right away and ran perfectly for a solid week. Then my Mellanox Connect-X2 cards came in from Ebay. I installed one into the rig above and Xpenology/DSM would no longer boot. Removed the card and it boots into DSM just fine again. OK, I think - let me first make sure the card is good, along with the DAC cable, the upstream switch etc. I put the same card back in and installed a fresh copy of Windows 10 on the same exact hardware - works perfectly gets 400 MB/sec of traffic with no tweaks. In short, the card and the upstream infrastructure are fine. This lead me to believe that the 3617xs image and/or Jun's 1.03b loader for 3617 might be missing the driver for the Mellanox. So I did some more reading and saw that the 3615xs loader is perhaps a bit more lenient on hardware or has more imbedded drivers. So I went through the process of building a 3615xs 1.03b, and that version unfortunately won't go any further. It will boot into the loader screen, but I never see link light come up on the Mellanox. I also went into BIOS and disabled the 2 x existing Intel i350 NICs on the motherboard just to make sure they weren't conflicting. This tells me it is driver related as the card itself is proven good in the same hardware chassis. So my questions: 1 - Definitively, does the Mellanox Connect-X2 have a driver in one of Jun's prebuilt loaders, or do I need to go hunt up something in an extras.lzma? I see answers that vary wildly on this, which is why I'm trying to get a definitive answer for myself and others who may be searching in the future. 2 - If I don't need any extra drivers, what loader do I need that contains the Mellanox Connect-X2 driver natively? I don't mind going back to DSM 6.1 if needed. I just want to use my extremely standard 10 gig cards but I suppose I can return them and swap for Intel DA-520 versions if needed. Thank you so much for any help you can offer. I've tried quite a bit on my own but failing. If someone can drop me a hint I'd really appreciate it. Panoz