Jump to content
XPEnology Community

filippo333

Member
  • Posts

    156
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by filippo333

  1. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 6.1.5 15254
    - Loader version and model: Jun's Loader v1.02b - DS3615xs
    - Installation type: ASUS H110I-Plus (Skylake)
    - Additional comments: No reboot required,  Power Button Package needs to be reinstalled.

  2. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 6.1.4 15217 U5
    - Loader version and model: Jun's Loader v1.02b - DS3615xs
    - Installation type: ASUS H110I-Plus (Skylake)
    - Additional comments: Requires immediate reboot

    This update resets synoinfo.conf. It appears DSM 6.1.5 handles SHR much nicer on enterprise models by now also populating the RAID Group tab rather than appearing as empty like previous versions:

     

    Capture.thumb.PNG.da9cce92d2a5aec654f85769cc3e845a.PNG

    Capture2.thumb.PNG.a8a28bf294767d3c9e44e545cfd78704.PNG

  3. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 6.1.4 15217 U4
    - Loader version and model: Jun's Loader v1.02b - DS3615xs
    - Installation type: ASUS H110I-Plus (Skylake)
    - Additional comments: Rebooted automatically

    Did not reset synoinfo.conf file like previous U4 update :)

  4. - Outcome of the update: SUCCESSFUL

    - DSM version prior update: DSM 6.1.4 15217 Update 2

    - Loader version and model: Jun's Loader v1.02b - DS3615xs

    - Installation type: Baremetal (ASUS H110I-PLUS Z170)

    - Additional comments:

    -Requires reboot

    -Will revert /etc.defaults/synoinfo.conf back to defaults, the backup I created (synoinfo.conf.backup) is nowhere to be found either. Recommend backing this file up if you have edited any of the settings!

    • Thanks 1
  5. 18 minutes ago, sbv3000 said:

    I think thats what happens if you do not set mac1 mac2 etc in grub, as a default. The other option you can try to find the addresses is to remove any mac number from grub and this usually brings up the real addresses, bit not always as random addresses can be set somehow, you will know if you reboot a few times :)

     

    I think the only way of doing it is finding out what the real values are and setting them statically in grub.cfg. As you said, every time I reboot the MAC addresses change randomly :S

  6. 1 minute ago, Dfds said:

    Boot from a live Linux USB & type "ifconfig -a", look for eth0 & eth1, the number next to hwaddr will be the MAC address. As you already know the MAC for the intel card you should be able to tell which one is which.

     

    Yeah I think at this point this is my only option; it's odd how Xpenology duplicates the same MAC addresses for all cards if there's only a single entry.

  7. Hello,

    Does anyone know how to harvest the real MAC address of a device whilst booted into Xpenology? Basically I'm using an Intel NIC but now plan to use my integrated Realtek one for something. Originally I only changed the MAC address in grub.cfg for the Intel NIC (there is no second entry for the integrated one), running ifconfig from the server shows the second adapter but with the exact same MAC address as my Intel NIC.

     

    Is there an easy way to see what the unspoofed address is?

  8. On 10/11/2017 at 9:04 PM, XPEH said:

    There is no migration path from FreeNAS to DSM. You will have to backup data elsewhere, install DSM with formatting your disks and copy data back from the backup.

     

    You could use Rsync to go between FreeNAS and Synology.

  9. 15 hours ago, denmalley said:

    Fellow noob here.  I just got a Dell t30 that came with 8GB ECC and added another 8GB stick.  Put 4 - 3GB WD Reds in there and followed this guide:

     

    It took me a few read-throughs to really "get" it, but I am also totally linux illiterate and had this up and running within 1/2 hour.  BTW I used a sandisk cruzer mini flash drive (32GB for $12 on amazon) - better to use a known brand name for your flash drive than some scrappy junk drive you have laying around.  And this minis sit flush in the port.

     

    Currently running using jun's 1.02b loader as a synology DS3617XS, DSM version 6.1.3-15152 update 8.  Plex is awesome.  Sonarr is flawless running in docker.  Continuing to work on more addons but this is better than any synology product I could have gotten at twice the price (other than better purpose-built hardware options like hot swappable HD trays of course)

     

     

     

    Agreed, I previously bought a DS1515+ and it just wasn't enough for video transcoding despite Synology marketing its 1080p video transcoding capabilities. I'd rather not spend £1.5k+ for a machine I can build for a third of that price.

     

    I'm glad you took the plunge, congrats on things working out for you :)

  10. On 10/8/2017 at 7:49 PM, IG-88 said:

    beside this if i open the kernel modules in a hex editor there is the following at the and of each module

     

    "...Synology SDG kernel module signing key...~Module signature appended~"

     

    could mean the modules to load have to be signed and i dont expect the signig key to be part of a open source kernel release

    so this might be a additional hurdel for a using dsm with other hardware

     

    Are Synology required to release their kernel modules under the GPL?

  11. 16 hours ago, aol said:

    Interesting. I see that Plex released GPU-based encoding as a Plex Pass feature earlier this year, and initially supported Intel GPUs only, YMMV with other GPUs. On my old xpenology box (a headless server) it used an older Intel CPU without an integrated (or discrete) GPU, but my current build-a-box has a recent Intel CPU with a built-in GPU. I'll have to investigate whether I can take advantage of it.

     

    I've tested GPU trans-coding myself but the quality is always noticeably worse than doing it with the CPU. That may change in the future but right now GPU trans-coding isn't a viable alternative unless you really can't afford a budget CPU made in the last 3 years.

     

    My i3 6100 for example can trans-code high bit-rate blu-ray rips quite easily (though CPU usage is high as you'd expect).

    • Like 1
  12. Hi,
     
    Hardware transcode it's only on DS916+.
    I have a Xpenology (DS3617xs) baremetal server with intel CPU 7700 (kaby lake), no hardware transcode it's possible (no VAAPI drivers are installed) 
    That's not really true, Plex can transcode on any x86 CPU even within a hyper visor in fact (though not very fast). If you're using DS Video on the other hand, then there are a few factors to consider if you want video transcoding.

    Sent from my SM-G935F using Tapatalk

  13. 1 hour ago, thehack2321 said:

    I'd just like to offer a HUGE thank you to Jun and Polanskiman, I've had to hold off on updating past 6.0.2 x8451 because I'm on an AMD setup:

     

    AMD A6 7400K

    MSI A88XI AC v2 FM2+ mITX

    8GB RAM

     

    In a Fractal Design Node 304 box that had been running the original Polanskiman's tutorial. Decided on a whim to see if Jun's 1.0.2B loader would work, load it on a USB stick and voila! The box booted up and Synology Assistant found it right away.

     

    The only "hiccup" I ran into was, when the box booted up the Assistant asked if I want to migrate, and when I tried migrating with 6.0.2 x 8451 it gave me an error. Failed to install the file. The file is probably corrupted. (13)" Double checked the VID and PID and nothing seems to work, even a forced install didn't work. Double checked the .PAT file, re-downloaded, and still no go. Finally gave up and have the DSM migration wizard download "the latest" 6.1.3 and again, VOILA! Box booted up an have been running like a champ.

     

    I was hesitant on letting migration wizard do its thing and install the latest, but assumed that even if it nuked the drive, I can walk it back using the older loader and reinstall 6.0.2 x8451 and copy all the files I backed up before I started. Lucky I didn't have to do that with 2 TB of data over USB.

     

    Just happy to report that loader 1.0.2B seems to work on my AMD box okay.

     

    Well personally I'm still on 6.0.2.x firmware and everything has been rock stable for me for months now. No reason to ever upgrade if you don't need the new shiny features, security patches are nice though :smile:

  14. 2 hours ago, Huberer said:

    if think DSM and OMV use the same kernel

     

    Well yes and no, Synology's kernel is full of backports and feature enhancements from newer kernels. They just like to have very strict control over what goes into their kernel and as a result their implementation is very fragmented and has doesn't have feature parity with your standard Linux distro.

     

    Basically don't trust version numbers when it comes to Synology's kernel :smile:

    • Like 1
×
×
  • Create New...