fonix232

Members
  • Content Count

    324
  • Joined

  • Last visited

  • Days Won

    1

fonix232 last won the day on June 13 2017

fonix232 had the most liked content!

Community Reputation

5 Neutral

About fonix232

  • Rank
    Super Member

Recent Profile Visitors

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

  1. At that point, why not just use LetsEncrypt? Especially since DSM 6.2.3 now has the capability to request wildcard certificates.
  2. The loader specifically looks for USB devices. An eMMC module installed on the system will NOT show up as a USB device, thus the loader won't work. No, you can't install the loader on the eMMC. Most likely you can't even use the eMMC for storage. Stick with a small USB drive for bootloading, and that's it. I know it's annoying, but hey, what can you do... However when you attach the eMMC to a USB adapter, it will show up as a USB device, thus it will boot. It is that simple.
  3. Jun's loader works fine with RTL8111H.
  4. If you can hack the driver into the installer, sure it will work. However I had other system incompatibilities that ended up taking a week of my time. Proxmox setup took maybe 4 hours, 3 of that was finding a proper way for the USB disk, and testing.
  5. Yes, indeed, virtio drivers are not included, so let's stick with the regular stuff. I did the USB workaround so e.g. updates won't wipe that disk. This way it is exactly the same as booting from an actual USB stick on barebones. Harder to achieve but you don't need to always overwrite the boot disk. Not sure if running a virtualized OS within a virtualized OS is a good idea. ESXi has a VERY limited support for various hardware (e.g. my RTL8111H LAN is not supported, many other hw aspects are not supported), and in my opinion managemen
  6. After fiddling with it for a day, and getting it to work, I thought it would be nice to share the knowledge, especially since "officially" only ESXi is supported, and ESXi is picky about supporting stuff... The main reason for me to move to a hypervisor was because Synology has not yet introduced NVMe support AT ALL. And even with a kernel driver, the Storage Manager will not see it as an SSD, as an HDD, or anything. Synology is silent about this, even though some have requested it on their forums (although they do not have a model with M.2 NVMe connector yet, they have some models
  7. fonix232

    DSM 6.1.x Loader

    Anyone successfully installed this yet on Proxmox? Nvm, done it.
  8. fonix232

    DSM 6.1.x Loader

    Hey guys! I ended up reinstalling my server... And now I'm also getting error 13 when I'm trying to install. Serial and MAC are correct, USB VID and PID too. Has any of you got around this issue? EDIT: Using 1.02a 3615xs works, but no updates show up to 15101. 1.02a2 does not work at all, fails with error 13 even on clean disks. Now to compile the nvme driver to get it to see my SSD...
  9. If you want to back up and/or restore: - Use a Linux live disk. For me, GParted recognized the MDADM arrays and mounted them. - DO NOT make a disk image via dd or any similar block-reading tool - DO use a tool made for backing up files, or simply moving them (rsync or even better, tar it all up) To restore, just erase all files on the initial mdadm array, and extract the TAR file to it. It should restore everything stored on the system partition. However this whole thing is unnecessary since Synology stores little to no "new" things on the system partition - it is instead kept
  10. fonix232

    DSM 6.1.x Loader

    Do you have network connection? If not, it is possible that you ran into the upgrade issue many had, which killed the network drivers.
  11. fonix232

    DSM 6.1.x Loader

    you footer states as board msi b250i, the manual states Realtek RTL8111H, the realtek website states RTL8111B...RTL8118AS Unix (Linux) Apply to RTL8111H(S)/RTL8118/RTL8119i as well. the driver source provided by realtek, LINUX driver for kernel up to 4.7, contains file r8168.*, so it will be r8168.ko took 5 minutes and just reading websites and manual your bigger problem might be that juns loader only provides r8169.ko and that driver is often mentions to be loaded and causing problems with RTL8111H so a r8168.ko driver comiled for dsm 6.1 is the thing you need (and you have to make
  12. fonix232

    DSM 6.1.x Loader

    This is what I have seen others do: try mounting the raid array in live ubuntu usb. Then replace /lib/modules/[yournic].ko with the one in /lib/modules/update/[yournic].ko Let us know if that works. Thanks for the heads-up. I'll try to do so (pity that I have literally no idea which NIC driver I'll need, but I guess I'll just push the whole modules/update folder to modules/, overwriting old files).
  13. fonix232

    DSM 6.1.x Loader

    So for now, no solution for people who accidentally upgraded to 15101? I've tried "reinstalling" (popped 3617xs 1.02a2 loader on my drive, booted it, migration went fine then bam disappeared from the network), to no avail.
  14. fonix232

    DSM 6.1.x Loader

    Have you had any luck fixing it? Booting with mfg forces a reinstall, so I'm not sure if that would work on the long term.
  15. fonix232

    DSM 6.1.x Loader

    Neat! I can probably modify the loader images so that you can include extra modules without replacing the whole extra.lzma (instead you can add another). That way there won't be need to include all the patches Jun made, just the modules. Also, could you please compile a few wireless drivers for wireless USB dongles? The most widespread models (iwl, realtek, atheros) should do fine for a test run.