• Content Count

  • Joined

  • Last visited

  • Days Won


mr9v9 last won the day on November 3 2018

mr9v9 had the most liked content!

Community Reputation

7 Neutral

About mr9v9

  • Rank
    Junior Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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!
  2. 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.
  3. 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: 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 the
  4. 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?
  5. Thanks for the insight! I will try it this weekend and post some results.
  6. 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?
  7. 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.
  8. 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 a
  9. 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?
  10. 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?
  11. 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.
  12. mr9v9

    DSM 6.2 Loader

    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?
  13. mr9v9

    DSM 6.2 Loader

    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.
  14. 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.