wvh3

I figured I'd start small and just have the one link between my main workstation and the nas... And keep the existing 1gb nics in place... Avoiding the need for a switch for the moment... Pc is i7 4ghz, 16gb ram, Samsung 850 pro ssd Nas is a stock n54l gen7... 2gb ram and (currently) with 4hdds using shr My biggest concern and what I figured I'd ask someone with more experience here, is that there's something fundamental to this whole 10gbe thing that I'm missing... I've read some stuff re transceivers that makes me wonder if there are some missing parts that I'm not considering given the links to the products I mentioned... Also warnings of compatibility with different cable types, makes, models etc. I'd rather not start down this path and then be told "ohhhh well. You're forgetting you'll also need THESE components ... For another $$$

Okay, so I know that half of the forum will say "But, Why would you need this?!?" I like eliminating bottlenecks when I find them... Right now the bottleneck I'm seeing is to do with my 1gb network... Looked into Bonding/Teaming/Load Balancing etc... looks complicated... might come back to it... But then I see people talking about these "Mellanox" cards... is it really this simple? I'm a tech, so I'm sure I'll handle the networking side fine, but I've never played with "the big boy" hardware before... Is this all I need? 2x Mellanox Connectx-2 PCIe (one in my NAS, one in my Workstation) http://www.ebay.com/itm/671798-001-HP-1 ... 51b840d586 1x 10GBASE SFP+ Copper Twinax Cable SFP-H10M-CU5M http://www.ebay.com/itm/Cisco-5-Meter-1 ... 419a7b9562 plug them into eachother, set them to their own subnet and static IPs... and no more 1gb bottleneck? I should mention my config I suppose... NAS is n54l gen7 running 5.2.5565.2 Workstation is running w10 64b

I just downloaded the manual for your switch... it looks like even out of the box it has configuration necessary... Page 11 of the manual... ftp://ftp2.dlink.com/PRODUCTS/DGS-1100-08/REVA/DGS-1100-08_MANUAL_1.04_EN.PDF So, if your router is set to a different IP Range than the one the switch defaults to... then anything you plug into the switch will definitely yes be on a different network than those plugged into your router..... Until you adjust the switches settings to match the rest of your network.

What switch are we talking about? A Regular "Dumb" switch should just plug in and give you more ports... anything plugged into the switch, (While the switch is plugged into the router) should interact perfectly with anything else on the switch or on the router... but then again a dumb switch couldn't be used in networking bonding or link aggregation (for the most part). A smart or managed switch... can be configured in all kinds of different ways, such that different ports are different speeds, or bonded, or not even on the same network as one another. Link Aggregation gets into kindof advanced networking stuff that might not be the best thing for a networking beginner to get into... Proceed with caution down this path.

http://www.tekrevue.com/tip/edit-hosts-file-mac-os-x/

Yes, your 5 year old linksys does have it... Other routers do not, if you read the link I posted, you'd see the Netgear is specifically excluding the "feature", citing security reasons. I'm glad DDNS is working for you, and it works with my relatively cheap EnGenius router too... and many if not most routers out there. Just not this particular one. Perhaps if you've had the same linksys router for 5 years straight you haven't had as much exposure to different routers out there.

While, you are correct, that is A solution, I'm not sure it is the best solution... Yes, it gets you past the issue of the moment, but... there's something wrong with your system in that it is not recognizing Synology's own products as being trusted. By all means, if you are satisfied, feel free to proceed onward happily... however, please keep this issue in the back of your mind for later on when and if some other issue crops up... as this issue might be related to that future issue

Sorry, but no. NAT Loopback will be required to use a DDNS hostname inside your LAN, this is even stated on the Netgear knowledgebase here: http://kb.netgear.com/app/answers/detail/a_id/13297/~/i-am-unable-to-access-my-web-server-via-host-name

I guess I keep struggling to understand your meaning, perhaps a language barrier... Are you saying that Synology is over charging for their ds415+? Welcome to Capitalism. As for "Quick Connect server is part of Synology"... yes, Synology owns and operates and pays for the servers and the Internet traffic for the Quick Connect service. Thus using THEIR traffic and THEIR servers for your nonSynology product does seem rude to me, yes.

Tough Question... I would feel fairly comfortable saying Most routers support or have an option to support Nat Loopback... Most people I find are pretty confident recommending the ASUS or Buffalo lines of routers, Engenius is an unknown but pretty decent brand as well... as for "playing nice" with DSM, if you mean being listed in the "Router Configuration" list, it's a fairly limited and i think fairly outdated list...

If your issue is that you try using the DDNS hostname (eg, examplehostname.no-ip.com) and it works Outside your LAN, but not within your LAN,... then your router may not have the feature called "NAT Loopback" or might not have it turned on. https://en.wikipedia.org/wiki/Network_address_translation#NAT_loopback

Read this? http://forum.synology.com/enu/viewtopic ... 50&t=92675

I'm not sure i understand what you're trying to say here.... Synology gets what lesson? and Google has What to do with this? and yes QuickConnect is a part of DSM... sure.. but it uses Synology's servers... It just seems a bit... rude?... to use their servers for products that aren't theirs.

afaik, mostly why people are talking changing serial/mac is to use Synology ddns/heartbeat/QuickConnect services... Xpenology consensus is to avoid using these services anyway, so as to not encourage Synology to make life more difficult for Xpenology users. Leave Synology's servers for Genuine Synology products... besides, with a tiny bit of networking knowledge, most, if not all of the services offered by their services can be replicated with 3rd party (and often Free) providers. (That having been said, some people started with actual Synology brand products and have one (or more) collecting dust in their attic, and it's certainly more of a gray area repurposing a Genuine synology products serial/mac for use with an Xpenology build)

while "Technically" the data is spread between the disks, from what I understand it would take a pretty sophisticated recovery process and some intimate knowledge of ext3/4 file system structure to try to recreate data out of a "broken" JBOD. AFAIK you're either gonna have to get a different hard drive for that other computer.. or... backup your JBOD, break it, pull the drive out of it, recreate it with one fewer drive and then put whatever data you can fit back on.... JBOD is basically a terrible system for almost every setup I can think of

There's a lot of information missing from this question.... When you go to Storage MAnager, is the new hard drive listed under HDD/SSD At all? if no you might have a problem with the Hardware recognizing the new hard drive at all. Within Storage manager, select Volume, and expand the Volume you want to add this hard drive to... if it does not already say "Synology Hybrid Raid (SHR)... " you will likely have to Delete it (and thus lose all data on it [Please backup!]) and then create a new Volume with the RAID type you want (presumably SHR with 1 disk data protection)

Look in your Control Panel, just beneath QuickConnect, you'll find External Access... go to DDNS, click Add, and other Service Provider you'll see a list of all the DDNS Service providers synology supports... while you're here, check out the Router Configuration tab beside DDNS,... it can help configure your router for port forwarding, if you need help that is.. There's your alternativeS

Ok, so update... After several reboots and attempts at different fixes, I was able to use the "ifconfig eth0 netmask up" command, along with setting the Version# back, along with Install/Upgrade boot... finally Synology Assistant sees the nas, and attempts to write 5.2.5665 to it... even so it Still doesn't come up with an IP by itself, so once again I manually set it using the ifconfig command... and Im now finally able to log into the DSM. Now, Im looking at doing a Clean Install to fix this mess... I thought I read someone mentioning an ability to perform a clean install while maintaining the Data on the drives, but I can't find that information now. I'm cleaning out my data to prepare for a full backup if Im told that a clean backup is Going to be destructive.... but let me know if Im wrong. Thanks for the help and suggestions ya'll (especially hackerjac and crowpet)

Ok, so update... After several reboots and attempts at different fixes, I was able to use the "ifconfig eth0 netmask up" command, along with setting the Version# back, along with Install/Upgrade boot... finally Synology Assistant sees the nas, and attempts to write 5.2.5665 to it... even so it Still doesn't come up with an IP by itself, so once again I manually set it using the ifconfig command... and Im now finally able to log into the DSM. Now, Im looking at doing a Clean Install to fix this mess... I thought I read someone mentioning an ability to perform a clean install while maintaining the Data on the drives, but I can't find that information now. I'm cleaning out my data to prepare for a full backup if Im told that a clean backup is Going to be destructive.... but let me know if Im wrong. Thanks for the help and suggestions ya'll

Yes, first thing I tried. System is still not accessible after having entered those at the CLI

Yea, that's what I did,.... now mine is inaccessible... and won't show up in Synology Assistant... not sure how I'm going to resolve. Always make sure you back up your data!

i have same VGA output and same issue... no IP, tried setting statically per the CLI then using vi per the above post... I still cannot access the DSM ... either via Synology Assistant or through web interface. Even when I choose to boot in "Upgrade/Install" mode, it's still not found via Synology Assistant. Some previous troubleshooting called for running a Clean Install? I'm not sure how i can even do that at this point. I Love the xpenology project and have been using it on my N54L for the last couple of years successfully... 5.1 ran fine for example, it was just when I tried upgrading to 5.2.1 that everything seemed to go south. Help me Please!