• Content Count

  • Joined

  • Last visited

  • Days Won


mr9v9 last won the day on November 3 2018

mr9v9 had the most liked content!

Community Reputation

6 Neutral

About mr9v9

  • Rank
    Junior Member

Recent Profile Visitors

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

  1. Thanks for the insight! I will try it this weekend and post some results.
  2. 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?
  3. 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.
  4. 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.
  5. 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?
  6. 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?
  7. 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.
  8. 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?
  9. 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.
  10. 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.
  11. It pings and request times out. Which means it can't cross the subnet unless I change my ip to match.
  12. 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?
  13. 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.
  14. I am in the process of doing this today. I will post my findings after the process is complete.
  15. 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.