bearcat

@yulyo Do you remember what IP range you used before the move? 192.168.x.y / 10.a.b.c ? What IP range / address are you currently getting on your computer now ? Have you tried using the Synology Assistent? If you remember the old IP range, manually set your computer to be in the same IP range, connect it directly to your NAS and try the Syno Assistent or go directly to the old static IP of your NAS.

Make that 2 I have the same SW/HW setup and the same temp.

What make/model is your NIC (lan card) ?

Just to make sure, you are not able to connect to your NAS locally, in your home? Did you use DHCP or static IP's on your NAS and computers before?

@flyride Of course, don't know where i had my head no need to exclude what's not in there 😏

@morow Are you able to ping the different IP addresses on your 10GB interfaces from your computer? If you did not choose the addresses yourself, they have been "randomly chosen" as self-assigned addresses, and you might be missing a route between them. So, you better assign the addresses yourself, and you may use the format: 10.0.0.xyz to easier differentiate them from your 1 GB net. (or maybe 192.168.10.xyz but then you have to exclude that range from the DHCP scope in your router)

@WDCluB 1 box is not running Perl, (only added package is the Power button 6.1-0004) the other one is running Perl 5.18.4-0023 and LMS in addition to the Power button and so they have been running since I upgraded from DSM 4.3 long time ago, this security msg started to show 11 days after any updates made. btw: what is the newest Perl, and how to install it manually?

In this great toolbox you will find everything you need (for Windows 64) as portable tools. Or, you may get the specific VID/PID tool here

Is your Atom CPU compatible with the 1.04b 8 918+ combo?

How come you use a 169.24.x.y IP adress? Thats a link-local IPv4 address in accordance with RFC 3927 indicating a self-assigned IP adress. Did you choose this address your self? If so, you better use a 10.0.0.x or a 172.16.x.y address if you want to separate it from your 192.168.x.y range

@Jamzor Your 970 EVO is on the "compatible list" for the original 918+ so there might be hope... it might be a driver issue related to your "unknown" mainboard?

@unmesh The symptoms your describing sounds familiar, but I have only seen it on bare-metal and "normally" only after update from 5.x with another bootloader (synoboot).

Bluetooth support do exist in DSM, but AFAIK only for USB dongles, just as DSM supports many USB based WiFi cards. I have yet to try an internally mounted WiFi card, is there any drivers "out of the box" for that and support in DSM? edit: in regards to WiFi, I see Synology are referring to some changes in DSM 6.2.2

I'm hoping you do the changes, before creating/writing the boot stick? When you try to reboot/cold start the computer, exactly where does it stop the boot process?

@hairyhobo It might be that I'm tired and sleepy after a long day at work, but I don't understand why you choose to install DSM 6.2.1, that is not supported, neither with the bootloader or the harrdware and use the 3617 ignore all what I said in my first reply. Maybe I'l "get it" tomorrow after some sleep.

Ok, sounds like a network problem.. What .pat file did you install just before that happened?

@hairyhobo Try the "safe route": 1.02b, 3615, DSM 6.1.x (using manual install of the .pat). Be aware of BIOS settings, like disable C1E.

Let me guess, you updated to 6.2.1?

@dochammoc The IP address you set up in the BIOS, is only valid for your IPMI card (using a Realtek RTL8201N PHY) What you need to use DSM on your mainboard, are drivers for your Intel i350 Dual Port Gigabit Ethernet, and a cable connected to any of those 2 ports.

@Jord226 did you change your vNIC to use the e1000e driver?

Your low ammount of free RAM is due to the 13,6 GB that's currently marked as reserved, leaving you with 2,4 GB with usable RAM. Take a look here, and se if it helps with your other problem as well.

@Benoit Do you plan to run Win 2016 as a virtual server inside baremetal DSM?

As I recall, any size from 64 MB (as in MegaByte) will do for the USB bootstick, since the .img file is about 50MB.

It seems like one of your failed update attempts might have installed 6.2.1 on your HDD's system partition? The "Diskstation can not be found" indicates an unsupported NIC with the bootloader/DSM combo used. If you don't mind moving to the 918+ platform, you might be able to do so, using Jun's 1.04b bootloader. That combo works great on one of my boxes, based on the AsRock Q1900-ITX (it also worked with bootloader 1.03 DS3617xs, DSM up to, and including 6.2 update2, but not 6.2.1) This mainboard uses RTL8111GR as the network chip, so before trying make sure your mb has the same.

@williammar This is a Windows based "tool-box" that can run on any computer running 64 bit Windows. And you only use it to prepare the USB stick that will become your boot-device for your NAS, after that you don't need it.