mr9v9

Sure can, try this one.

So it was a combination of editing eth2 and eth3 as well as the ovs_ethx files under /etc/sysconfig/network-scripts & /etc.defaults/sysconfig/network-scripts. One important thing that seemed to help was assigning BRIDGE=ovs_ethx to the respective interface as I did not have any configs for these. FYI I am running a DS918+ all is well with onboard NICs!

Just out of curiosity, why would I remove the real MAC's from grub? Wouldn't that preven't me from getting back into DSM if I screw up let's say eth0? I can always mount the boot image on another machine and fix it I suppose.

My grub.cfg file is configured correctly with all the hardware NIC's mapped to their MAC addresses, and set netif_num=4. The other two interfaces would only come up manually issuing a command in terminal originally. I got my other interfaces up by setting maxlanport="2" inside /etc.defaults/synoinfo.conf, but now when the interfaces come up on boot, they get default addresses as if they can't find a DHCP: 169.254.199.178 for example. My router gives these 2 other ports proper IP's from the available pool: 192.168.1.x and I can ping these, but if I try using any of these interfaces they go nowhere for virtual machines for example. I also cannot manually change the IP structure to STATIC under DSM with a warning of 'IP address has been used.' I have tried changing /etc/sysconfig/network-scripts/ifcfg-ethx to match the settings to something like: DEVICE=eth2 BOOTPROTO=static ONBOOT=yes IPADDR=ip address NETMASK=netmask This did nothing. I am running a A1SRi-2758F Atom board, and IMPI in a dedicated LAN mode separate from the NICs. My question is how can I fix this annoying little issue?

I have a question, how do I change the default 169.x.x.x for LAN3 and LAN4 since now they come up using this fix? They are supposed to be DHCP, but neither one takes my 192.x.x.x subnet. Which config file is this under?

Thanks for the insight! I will try it this weekend and post some results.

Thank you for the reply! I was going to give that a try, is there an easy way to filter out which devices are which? I assume is has to be in binary?

I am also wondering about this, I have an EXT4 formatted drive in a cradle with backups from previous Diskstation, but neither can mount USB or E-SATA. My only guess is it has something to do with the grub.cfg arguments, because when I go to Storage and try to add another volume, there my E-Sata shows up as Internal.

I would personally just try and salvage the data using one of the Synology guides out there. The last time I tried to restore data from a BTRFS volume it failed for me even though the data looked like it was indeed recoverable. The rebuild would take hours and in the end was a waste of time. Here is other examples of such an experience. I don't care what Synology says, but IMHO Ext4 is more stable for your MEDIA/DATA pool even with ECC memory. and BTRFS is best used for VMM and multi-user quota access because of snapshots and possible prevention of bitrot. I would not use it as a daily driver because it is still a beta, and not for mission critical operations.

There is a hint of what some of the settings do in earlier posts. The set common args seems pretty self explanatory that it is setting flags for the ds3617 on boot. A 0 representing a negative value of false and a 1 representing a positive value of true. The options themselves come down from the Linux Kernel Boot Parameters, and there are too many to name in one post. You can browse common ones here. Hope that at least points you in a helping direction?

I think somebody already did something similar with php scripts on the Synology forums over here. Maybe it could be modified and used to benefit your particular problem?

If you upgrade your HDD capacity it will be easier to migrate to another box down the road. I started at 4tb on a 2-Bay and added disks as I earned money. The rebuild process was simple, but I always bought a similar capacity for an eSATA dock as a backup just in case. I am up to 8TB and have a 4-bay now, but still use the original 4TB disks as BTRFS for VM's.

Try another browser other than Chrome first? I could not get the default NICs to show up for me on 918 build, can you ping your Gen8 at that IP?

I haven't tested it yet, but in your grub.cfg have you edited this line? set netif_num=5 Set the number of NICs to use.

I think the culprit is Emby, but it gets very strange because it happens when no containers are running. If I stop Docker manually and try pinging again same problem. ipconfig tools with /release /renew /flushdns do nothing, as well as rebooting my PC.

It pings 172.17.0.1 and request times out. Which means it can't cross the subnet unless I change my ip to match.

Has anyone experience UNC path problems to their NAS when running a Docker container? When not in use I can browse to my Diskstation shares on Windows using \\MYNAS just fine. When Docker containers run I can only use \\192.x.x.x on certain devices. Might even be a Windows 10 thing. I can touch my containers files with forward mapped ports to get to them on my local subnet no problem. Docker is set to use the 172.x.x.x subnet and I run containers in bridged network mode. Is there some sort of conflict with the way the Docker container is running? Or is this a bug with Windows 10?

I do want to add that in my case I had a few custom packages that needed to be re-installed to "fix" them. I had a static IP set on the old Diskstation, and had to put it on DHCP so there were no conflicts on migration. Also during the migration I used DSM_DS3617xs_23739.pat file to continue, then applied the update 2 pat file to get me back to where I was. My IP and port rules all applied successfully as if it were the same unit. I did not even use my .dss configuration backup! It did retain my SHR RAID setup as well. Very smooth operation and confirm @Joe Bethersonton that it does work and is simple.

I am in the process of doing this today. I will post my findings after the process is complete.

Sorry @Mathias I did a fresh install on my Server, if you don't care about any data on your current one I would follow this video. The files are buried in this forum if you get stuck let me know and I will post the links for them. You can also search around the posts, I have seen some users successfully upgrade their bootloader and DSM...I personally wouldn't do this from how tricky this already difficult setup is to get working.

So have you tried flashing the latest BIOS on that ION? I know I had to do it kind of weird for my own ZBox CI323. The other thing that may make a difference is the bootloader. I use 1.03b and DSM 6.2 running a DS3617xs, and have heard some people don't use C-states on the older version because it might not work correctly, which in turn could just be an older instruction not getting passed to your motherboard. Without the exact model number of the mobo it's hard to find the manual online to see what options it has specs wise. I gotta be honest I don't think XPEnology has the option for 'Advanced HDD Hibernation' even on the latest bootloader. You can see an example in this video. I don't think it is part of your issue though. I am curious about it now though. Last thought is to try and test another OS and make sure WOL actually functions because some motherboards / network controllers don't support WOL from the cold boot (S5 state, where the power to the system is physically turned off and back on again).

Would you care to list your XPEnology specs including your motherboard model? List your processor too.

Also check my related post with my Gen8 over here, it might be of some value to your problem.

I have some findings after doing a little research and adjusting settings, it looks like I found the sweet spot for power draw and performance, as well as having functioning WOL, lower fan speed, and as an added bonus HDD's going to sleep! I am using the very latest Latest Service Pack 2018.09.0 (P03093_001_spp-Gen8.1-SPPGen81.4.iso) with all firmware updates and current iLO. HPE decided you needed a warranty to get the download, let's not muck about with that: Download here I set the iLO time manually to a time server under Network>iLO Dedicated Network Port>SNTP Propagate NTP time to host. Unchecked use DHCPv4 and DHCPv6. I don't use IPv6 so I have that disabled, and under IPv4 I have ping gateway on startup unchecked. My WINS server is my router, if this is pointing to your XPEnology then there might be a sleep wake problem for hibernation of disks (more on that later.) I also don't have a shared network port enabled under iLO. The iLO network tweaks are probably not required but it improved my configuration. Third thing you may want to double check after firmware is that your BIOS settings are set correctly including the correct time: System Options> Embedded NICs: Network boot disabled for both (unless you PXE boot from the Network) USB Options>Removable Flash Media Boot Sequence: Internal DriveKeys First (that is where XPEnology lives) SATA Controller Options>Embedded SATA Configuration: Enable SATA AHCI Support SATA Controller Options>Drive Write Cache: Disabled Power Management Options> HP Power Profile: Set to Custom HP Power Regulator: OS Control Mode Power Management Options>Advanced Power Management Options: Intel QPI Link Power Management: Enabled Minimum Processor Idle Power Core State: C1E State Minimum Processor Idle Power Package State: Package C6 (retention) State Maximum Memory Bus Frequency: I set mine to 1333MHz (This depends on your RAM) Memory Interleaving: Full Interleaving PCI-E Gen 3 Control: I disabled mine because I have no use for it, helps with power draw. If you have something plugged in don't disable. Dynamic Power Savings Mode Response: Fast Collaborative Power Control: Enabled DIMM Voltage Preference: Optimized for Power, again this depends on your RAM Server Availability> Wake-On LAN: Enabled Thermal Shutdown: Enabled Power Button: Enabled Automatic Power-On: Restore Last Power State Advanced Options>Advanced System ROM Options> MPS Table Mode: Full Table APIC Power-On Logo: Disabled, it speeds up the bootup time and still has a prompt for F9 to get into BIOS. Leave everything else alone or set to your specific preferences if you know what you are doing, double check the BIOS date and time and then save your settings to get back into DSM. DSM settings: There are a lot of things that can affect your overall power draw and performance to keep your drives from properly going to sleep, read this page to understand the implications of certain packages. Control Panel> Regional Options>Time: Set the correct time zone, and click update now. Don't worry about NTP Service unless you use Surveillance Station. Performance: Uncheck Memory Compression. Will trigger a reboot. Hardware & Power> General: Everything is ticked, except the Fan Speed Mode. Power Schedule: Leave this alone for now. HDD Hibernation: I do 10 Minutes on both and enable Hibernation logs. Not checking Enable auto poweroff for now. Info Center> Service: Double check you don't have anything running that could affect sleep and wake, for example SMB is the only service running but it could act as a Master Browser which would affect the hibernation so I have it disabled. Another thing I prefer to do on my box is completely remove Universal Search: SSH into the NAS and run these commands: sudo -s synopkg uninstall SynoFinder I don't have any media indexing going on but that may be a factor as well. Other thoughts: Splitting up your hard drive disk groups could have an effect on what your hibernation looks like, check the logs, about half your drives may hibernate while others won't, it depends on the services running and many other factors that are far too much to name here. If you want the unit to go into a complete power off/on state try a package called Advanced Power Manager. I swear by this package and confirmed that it works on both my DS216+II, and XPEnology bare metal Gen8. There are many advanced functions that you can tweak that affect how your NAS "Sleeps" so explore it. Wake-on-LAN works if I have the unit go into an auto-poweroff state, but I use my Router to send a wake request to get it back up to where it was. I am using BTRFS but have not noticed any overworked HDD's crunching data into the night, everything remains stable and quiet and my fan speeds have gone down to 19% and idle is sitting well below 39w. Did I mention time is a factor to your hibernation? Make sure that your BIOS time and Synology DSM times are in sync, otherwise your 10 minute hibernation will never happen. I hope I helped somebody in these forums, and answered my own question at the same time.

Check my post over here. Not a complete solution but a step in the right direction.