Transition Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About tfboy

  • Rank

Recent Profile Visitors

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

  1. This is my first attempt at a tutorial here, so please go easy on me. I've spent some time yesterday understanding the process and various issues and common errors we can easily make. This guide is based on 6.2.2-24922 U6. It may work with other versions of DSM, but I've tested it and managed to get it working on this one. First, a few pre-requisites: You need a domain name for which you have administrative access and control. I already had one I could use. I think getting it to work on free dynamic DNS domain names is very difficult due to Let's Encrypt (LE) limi
  2. tfboy

    DSM 6.2 Loader

    @Red100, you have a couple of options depending on how you want to do it. Work on the .img bootloader file before you write to USB. If you want to modiy your original image file use OSFmount. With that app, you can load the .img bootloader file. Mount it, untick the "read only" check box, selecting the first 15MB partition. The app will mount that as a drive letter. You'll then be able to access the files in that partition from Windows Explorer. Edit the file directly on your USB key. For that, you can use the free version of Partition Wizard. That will allow you to mount your USB
  3. Found the issue for me. I hadn't thought that the website you need for the authorisation and verification to work (writes a file to your webspace/.well-known/acme-challenge/) is from the normal web service (nginx or apache2) running via Web Station which of course responds on ports 80 and 443. My initial redirecting and port forwarding from my public WAN to private LAN was forwarding to ports 5000 and 5001 for DSM. Whilst I need this to access DSM remotely, I actually need it to forward to the standard 80 and 443 for the certificate generation.
  4. I'm having issues with getting a LE cert for my domain. It's similar to the ones above, but I get a different error message. I've checked and am using ACME v2 so it's not that. Having been unsuccessful using the DSM interface, I've tried within SSH to get more detailed information. sudo /usr/syno/sbin/syno-letsencrypt new-cert -d -m -s -v The /var/log/messages suggests an invalid response from the ./well-known/acme-challenge url. I've tried that and get
  5. Ooh. A bit more digging and it appears the OS really does have the X553 NICs. I've stripped out some of the non-important data, but the key point is that the onboard X553 NICs are enumerated (eth4 - eth7) but even if they are connected physically to the network, they never come up and never get an IP address from the DHCP server. eth0 is strange, the MAC address starting with 0000b6 is Micro Matic Research - I guess the vendor Synology use so it's a fabricated one by the underlying OS and replaces the MAC burnt into the active NIC (I removed the MAC address from grub.cfg to se
  6. Here are the device IDs, etc: I guess this is the extra HP PCIe card: 0000:04:00.0 Class 0200: Device 8086:10bc (rev 06) Subsystem: Device 103c:704b Kernel driver in use: e1000e 0000:04:00.1 Class 0200: Device 8086:10bc (rev 06) Subsystem: Device 103c:704b Kernel driver in use: e1000e 0000:05:00.0 Class 0200: Device 8086:10bc (rev 06) Subsystem: Device 103c:704b Kernel driver in use: e1000e 0000:05:00.1 Class 0200: Device 8086:10bc (rev 06) Subsystem: Device 103c:704b Kernel driver in use: e1000e And these are the onboard Int
  7. Oh there's an 0.11 on 6.2.3? Interestingly, I was caught out this evening playing with 918+ 0.8 package on 6.2.2. At first, I thought it was working on the Intel X553 NICs as I had that Mac address picked up on my router but then realised that it was using the other HP add-in card. I guess it picked up the Mac addresses within the grub file and as it couldn't work with the X553, it applied those Mac addresses on the HP card.
  8. Thanks. I'm not worried (for me) about intel GPU transcoding, I just want the basic version working but preferably with the X553 onboard NICs rather than having to add a PCIe card. I'm starting from scratch, no real preference on whether a 918+, 3615 or 3617 platform. I did see a table somewhere but can't find it now detailing the differences. For DSM, again, no preference, 6.2.2 would be fine for me. Just to make sure I've understood, does that mean with my config above, it should be working with your extra.lzma ? As I've been running under the 3615 platform, I've tri
  9. I posted in another thread But after some more digging, it really appears my boot issues are purely NIC driver. I have put in an HP NC364T and that boots fine and gets an IP address. It's not clear to me exactly which drivers version I require. The motherboard I want to get working is a Supermicro A2SDi-8C-HLN4F which has 4x Intel 1GbE NICs based on the X553. Now the X55x is a 10GbE capable range of cards, so not sure if this is the problem. Linux drivers are here:
  10. tfboy

    DSM 6.2 Loader

    Hi @Infray I have the same Supermicro motherboard. Searching, I saw you had similar issues getting the onboard Intel X553 drivers to work. Your latest post here: suggests it does or did with an older version. Can I ask where are you with it today and what versions do you have it running on? I've tried 1.03b with both DS3615 and DS3617 bootloaders with no luck. I haven't tried getting my head around including the extra.lzma which might be required for driver support? Thanks!