Jump to content
XPEnology Community

filippo333

Member
  • Posts

    156
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by filippo333

  1. 7 hours ago, medric said:

    Here is the info that i pulled from

     

     

    https://github.com/kref/scripts juns script i can read and understand a bit of it but its a bash script not my strong suite 

    https://xpenology.club/compile-drivers-xpenology-with-windows-10-and-build-in-bash/

    https://github.com/HuxyUK/xpenology-3.x old but still has good info

    http://xpenology.com/wiki/en/building_xpenology old style for building the pat file but again has good place to start

     

    https://help.ubuntu.com/community/Kernel/Compile standard compile for linux

    https://github.com/0xAX/linux-insides/blob/master/Misc/how_kernel_compiled.md sandard compile for linux

     

     

     

     

     

    Looks like a fair amount of assembly is involved in modifying/analysing synobios though most of the compilation is bash.

  2. So one of my HD died today went a picked up a new one same make model and space put. volume is repairing but i cant see any data I had the raid on SHR1


    Is DSM complaining about wanting to also repair the operating system? Have you tried having a look with filestation?

    I know for a fact if DSM crashes it can take down most other services until the OS and RAID show up green as a failsafe.


    Sent from my iPad using Tapatalk
  3. 3 hours ago, R0KH said:

     

    Using the DS3617xs image on my system in the signature below, works fine, however many synocommunity packages aren't available. Not sure if they are on a 3615xs which I used when on DSM 5.2 where these packages were available. So it could be DSM 6.1 or the 'hardware' version you run, not sure...

    Currently I'm using Docker to run apps like Sabnzbd and Sonarr which is working quite well I must say, I might even like this better than running these apps natively on DSM (if it were possible). 

     

    There's some discussion about using hardware transcoding on DSM with apps like Plex. I can only guess that's what you want to use quicksync for, but it's unclear to me whether it works and it depends on the exact hardware configuration, especially with Xeon CPU's. 

     

    Quote

    It must be because Synology does not have Quick Sync compatibility built into the kernel.

     

    Looks like Synology don't officially support Quick Sync anyway.

  4. 55 minutes ago, pwvandeursen said:

    Thanks Filippo333 for the clear answer. So what you say is if I have a SHR, it will retain that configuration, eventhough a fresh system can not select SHR as a RAID option. It used to be an option as I started from scratch on the DS3615xs, and built the SHR on that with 4 drive (2x3tb and 2 x6TB so don't want to go to RAID 5 as that will cost 3TB of storage). Since DSM 6, it can no longer be selected as option in the DS3615xs, possibly still on the more consumer focused units indeed.

     

    Would be great to hear some feedback from others on the update route (5.2->6.1 or 5.2->6.02->6.1)

     

    That's correct SHR normally continues working when migrated to a loader which doesn't officially support it OOTB :smile:

    Obviously I do strongly recommend editing the config file on the DS3615xs loader if you want to continue using SHR.

  5. 1 hour ago, pwvandeursen said:

    Is it possible/wise to update in one go from 5.2 to 6.1. just tested it on a spare drive with 5.2 on it, and all went smooth, however before jumping to production two questions:

     

    1. Will I retain the SHR setup? in the new 6.1 it is no longer possible te select SHR (unless you change the settings through synoinfo.conf

    2. can I jump in one go from 5.2 to 6.1? or is it wise to install 6.02 first?

     

    thanks

     

    on a Q1900 with SHR and 4 HDD's

     

    I believe SHR is only enabled on consumer units by default (like the DS916p). As you said you can enable SHR on enterprise class devices but it's something which has to be done via SSH.

     

    Also others have had success with migrating their existing SHR array to a loader with SHR disabled, it just means you cannot create any more SHR arrays without editing your config first. The worst that will happen is DSM will just not mount your volume, though SHR is only disabled via the GUI not system-level. I tested this myself in VMware a while ago and it worked for me (but I went from 6.0.2 to 6.1.1).

    • Like 1
  6. 1 hour ago, guindous said:

    Hi All,

     

    Sorry for my English.

     

    As I can read, boot loader 1.02b is not compatible with AMD. It means that prolong G7 is deprecated forever?

     

    Regards,

     

    Please search the forum, loader 1.02b is currently not compatible with AMD since it's a beta release. The stable releases should be compatibile with AMD, if you need AMD support right now then stick with Jun's 1.01 loader.

  7. 11 minutes ago, wapoo said:

     

    yes, im on DS3615xs, but there wasnt a problem in dsm 5.2. So is this a problem in 6.0.2?  if so, how can i flash to ds916p?

     

    Look around the forum, it's the same process as changing your loader when upgrading from 6.0.2 to 6.1.x.

  8. 12 minutes ago, wapoo said:

    hi all,

     

    i am currently on v1.01 bootloader, running 6.0.2 on hp n54l amd server baremetal. since upgrade  from dsm 5. i found out that the video station no longer able to play majority of my mkv and avi files, neither on web nor on ios device with ds video app. looks like there is a transcoding problem. does anyone experience the same problem as i do? and any solution?

     

    Correct me if I'm wrong: only the DS916p image contains the necessary modules for hardware trans-coding. I believe the enterprise models (DS3615xs, DS3617xs) do not support transcoding via Synology's media apps. You can always use Plex of course like me :P

  9. On 7/14/2017 at 5:25 AM, epicurean said:

    Thank you @filippo333

    So if my media(eg movies, tv shows) is in volume 2, would my plex files be in volume 1 usually?

    What are the typical folder in 7a?

     

    Would it be better( eg ease of plex clients finding plex media server) if net is bridge or host mode?

     

    thank you 

     

    Bare in mind that this is just for linuxserver/plex, other containers have different requirements.

    Essentially just mount the two required folders when setting up the container. The docker mount points should look like this:

     

    Folder                     Mount Path

    /MyMediaFolder     /data

    /MyPlexConfig       /config

     

    Quote
    • --net=host - Shares host networking with container, required.
    • -v /config - Plex library location. This can grow very large, 50gb+ is likely for a large collection.
    • -v /data/xyz - Media goes here. Add as many as needed e.g. /data/movies, /data/tv, etc.
    • -v /transcode - Path for transcoding folder, optional.
    • -e VERSION=latest - Set whether to update plex or not - see Setting up application section.
    • -e PGID= for for GroupID - see below for explanation
    • -e PUID= for for UserID - see below for explanation
    • -e TZ - for timezone information eg Europe/London, etc

     

    One other thing you may need to do is set your GroupID and UserID to the be same as your Synology user with access to your media. You can do this by typing "cat /etc/passwd" via SSH-ing into your Xpenology box.

     

    For example, if your UserID is 1024 and your GroupID is 100; you'd set the PGID and PUID as Docker environment variables shown in the linuxserver/plex documentation accordingly:

     

    PUID=    1024

    PGID=    100

     

    As for Bridge mode vs Host mode, the default works fine. There is normally not a good reason to change it unless you need a different IP address than your Xpenology system.

  10. 2 hours ago, epicurean said:

    HI Haydibe,

    Can you explain 7a onwards in closer detail please? I do not quite understand. 

     

    much thanks

     

     

    Plex requires two key components to work, the first is your media (videos, music, pictures etc).

    The second is a location for Plex to store its settings such the metadata and database.

     

    With Docker, you must mount data you want access to as by default everything inside the docker environment is volatile. This means whenever you re-create or update the container, all data within is lost forever. Therefore data you want to keep safe must be mounted; after all you don't want all you media and Plex settings lost every time you decide to update the container.

  11. I wonder what the root cause of this Timb Bomb issue is? It seems migrating your data & applications to a new boot loader is the trigger.


    Sent from my iPad using Tapatalk

  12. 3 hours ago, brendann said:

    I'm assuming you want to remove the notification badge from the control panel, The below is supposed to reset the badge but doesn't look like it works to remove the 1. Using -a or -u and then a number increases the badge and then -r returns it back to 1.

    
    /usr/syno/bin/synoappnotify -c SYNO.SDS.AdminCenter.Application -r @administrators

    I have also tried using SYNO.SDS.AdminCenter.Update_Reset.Main as the class but same result

    
    synoappnotify -c SYNO.SDS.AdminCenter.Update_Reset.Main -r @administrators

     

     

    Nice work regardless for finding that out :smile:

  13. 1 hour ago, Thomas126a said:

    Is it possible to backup the Synology partition and all files needed for DSM to run in order to test an update and be safe to always go back to the state in which everything was working just fine by restoring?! Baremetal ofc.

    Was thinking to backup via Linux Live Disk. Is there a way or has anyone ever tried that?

     

    You could probably use Linux's inbuilt dd tool to image a partition/entire disk. Don't ask me for the technical details though, there are likely tons of tutorials if you Google for it :smile:

  14. 22 minutes ago, Polanskiman said:

    Untick: ?

    Screen Shot 2017-06-30 at 6.01.36 PM.jpg

     

    So I want to be able to stop DSM from even attempting to look for updates, just to get rid of the annoying update badge. So far blocking the host file works assuming DSM has never connected to the internet; I'm now thinking it caches whatever the latest version is.

  15. Update: So I managed to successfully block DSM updates by editing the following hosts file /etc/hosts (editing /etc.defaults/hosts doesn't work!) I added the following line:

    Quote

    127.0.0.1 update.synology.com

     

    The problem is the update badge remains, meaning it's still somehow talking to Synology's servers but at least it won't allow you to update via the GUI.

     

    Capture.PNG

  16. 3 hours ago, muaddib81 said:

    +8 for AMD support

     

    I mean AMD support would be nice but people have to remember; Synology DSM doesn't natively run on AMD hardware (I'm not aware of any current gen Synology hardware running on AMD chips). So further patience will be needed to implement the necessary kernel modules for AMD compatibility :smile:

  17. Just now, Polanskiman said:

    I don't see anything being locked.

     

    For Quickconnect: use a custom DDNS. 

    Surveillance Station. There are other alternatives. Even on a real Synology you need to buy licenses over 2 cams.

    Push services. Along with Quickconnect those two have always required a valid pair of SN/MAC.

     

    Nothing new I would say. There is so many other things that one can do with an XPEnology box. If the above is what you need the most then maybe using a real Syno would be the way to go or maybe digging a bit more on google might yield some goodies...

     

    Agreed, I use No-IP and that works a treat! I don't know much about Surveillance station, but I guess that's okay if you need to buy licenses for it.

    Also I had a real Synology for a day or too (DS1515+) and it was just way too underpowered to do my Plex 1080p video transcoding; so I have no choice other than to stick with my i3 6100 system personally. Don't feel like shelling out close to £2500 for a NAS ;)

  18. That is correct. Same goes for the use of QuickConnect, and hacked Surveillance Station. Just so that I am thorough, using these loaders is one thing as it doesn't involve modification of any binaries, yet we are in a grey area. Cracking Synology proprietary software and abusing Synology's servers (QuickConnect or push services) is yet another step and that is something that XPEnology Devs do not support nor do I.


    If this becomes a trend and Synology start locking out all their first party applications... Xpenology becomes much less compelling to many people (including myself) :sad:

    Sent from my SM-G935F using Tapatalk

×
×
  • Create New...