titoum

Members
  • Content Count

    49
  • Joined

  • Last visited

Posts posted by titoum

  1. 6 hours ago, Orphée said:

     

    @titoum
    ok, je dis juste attention, avant de laisser penser qu'on peut migrer... je préfère mettre en garde ceux qui pourraient croire que c'est bon.

     

    J'ai une utilisation sommaire de DSM et les fonction basic semblent fonctionner comme prévu (WOL, hyperbackup, photo sans tag).

     

    mon nas est le plus svt éteint et allumé avec WOL pour sauver mes photos ou lancer plex :-)

    j avoue etre un peu allergique a docker ^^'

     

    sinon ca serait sympa que syno sorte un os reellement fini et pas une RC... :D

  2. l'origine de mon topic était de savoir si certains s'y était tenté.(non/oui content ou pas)

     

    je ne veux pas convaincre les gens d'y passer ou pas :-)

     

    concernant docker, c'est pr ca que je préfère rester sur du baremetal. il y a déjà assez de couche spaghetti que pour y rajouter celle de docker....imo.

  3. 14 hours ago, Orphée said:

    Ce n'est même pas encore une beta.

    Encore des choses non fonctionnelles.

    Pour du test et debug ok... pour de la "prod" non... sauf si tu es prêt a perdre tes données.

    j'ai un cold back et pour le moment 0 soucis.

     

    plusieurs sont déjà passé dessus et semble autant content.

    en parlant de perte de donnée, je n'avais aucun soucis sur l'ancien dsm. en passant au 7.0.1, j ai eu un warning de faire un data scrubbing...celui ci a trouve un fichier problematique dans la corbeille.

     

    comme quoi...plex fonctionne sans soucis ainsi que le WOL donc pour moi c'est suffisant.

     

  4. 16 minutes ago, stigma86 said:

     This is a ,,step by step codex"?
      - Download the loader
      - mount OFSmount and replace the SN (918+) PID and VID
      - Download the latest path file : 918+ => DSM 7.0.1 (Version: 7.0.1-42214)
      - I continue the installation on the web interface and install the 7.01 image, that I'm writing

     

    this is still dev so at your own risk...

     

    you need haydibe docker then building, rufus to your usb and try/error.

    no cookbook so far.

  5. 1 hour ago, Franks4fingers said:

    I used USB Device View from the Xpenology Tool V1.4.2 toolbox.  

    image.thumb.png.709546ccced557255357d233ca8c9dd0.png

     

    I also looked in the properties via my Surface and the only difference I see is that the VID there is all upper case......does that make a difference given USB Device View gives it in lower case?

     

     

    This is my grub.cfg as well that is on the only available partition that Windows can see now the img has been burnt.

     

     

     

     

    On my side : vid=0x11a1 so i put it exactly as being mentioned in the USBDeview.

     

    image is written with rufus.

     

  6. 3 hours ago, Franks4fingers said:

    I am still plagued with the issue of hitting 56% and then the install bombing out with the error message of:

     

    Failed to Install DSM.

    Failed to install the file.  The file is probably corrupted.

     

    which app did you use to get them?

    can you screen that + provide your grub?

     

    for me, i had also to put hdd as hotplug 

     

  7. 33 minutes ago, ct85msi said:

    It seems that it reverts to performance when I reboot.

     

    root@Apollo:/usr/local/etc/rc.d# ls -la S99Powersaving.sh
    -rwxr-xr-x 1 root root 295 Sep  8 15:32 S99Powersaving.sh
     

     

    Thanks

     

    you can create a task from interface to do it every 10'. so you are sure it is done 😜

    or you can do it with crontab.

    Capture.JPG

     

    and dont forget to set it with root user

     

    root.thumb.JPG.92786bc3400e3638e0f54ebcb723ac23.JPG

  8. may be @ThorGroup could enhance first topic with some extra info ?

     

    link to latest version of haydibe docker image ?

     

    how to get ride of the blank info center

    sudo su - root
    
    sed -i 's/supportsystemperature="yes"/supportsystemperature="no"/g' /etc.defaults/synoinfo.conf
    sed -i 's/supportsystempwarning="yes"/supportsystempwarning="no"/g' /etc.defaults/synoinfo.conf

     

    acpi throttle

    sudo su - root
    vi /usr/local/etc/rc.d/S99Powersaving.sh and insert according to number of core
     
    Script-content:
    
    #!/bin/sh
    
    echo powersave > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
    echo powersave > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
    echo powersave > /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor
    echo powersave > /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor
    
    chmod +x /usr/local/etc/rc.d/S99Powersaving.sh
    sh /usr/local/etc/rc.d/S99Powersaving.sh

     

    • Like 4
  9. 26 minutes ago, shibby said:

     

    re-check VID/PID in grub.cfg.

     

    i had this issue many time until i realize that i set vid as pid and pid as vid 🤫 when i seted correct values then instalation goes well.

     

    i checked them couple of time they were correct...except that vendor id and pid where switched :(

     

    installation goes through so i will see if it goes to the end and then align my docker to avoid this later one.

    regarding the double folder for efi/efi. is there a fix to apply or change to avoid doing it every build ?

     

  10. 57 minutes ago, jumkey said:

    mount img and check is there have folder efi/efi/boot/ with file synobootloader.conf

    change /efi/efi/boot/->/efi/boot/

     

    that is so weird !

     

    G:\EFI\EFI\boot then

     

    • SynoBootLoader.conf
    • SynoBootLoader.efi

     

    G:\EFI\BOOT then

     

    • BOOTX64.EFI

     

     

    Do i just merge all into the eif/boot ?

     

     

  11. i wanted to give it a try.

     

    so setup:

     

    [CM] Asus P8H77-I
    [CPU] Intel Core i3 3225

    [NIC] Intel Gigabit ET Dual Port Srvr Adptr Server Adapter PCI-e x4 2x Gigabit Port

     

    loader:

     

    docker script from haydibe in version 7.2

    bromollow / DSM 7.0.1

     

    i had a first issue complaining about hard drive error. i had to switch hot plug support in bios and then it went further.

     

    now, i am hitting the 56% error about file being corrupted. i would guess that it is related that i plugged the spare hdd on sata3 instead of 1 ?

    vid/pid are correct as same used for jun's loader

     

    leave me still some spare time before official stable release will be available :D

     

     

  12. i started the latest docker and great works as usual :-)

     

    wondering why i get this warning:

     

    /opt/redpill-lkm/config/runtime_config.c:168:47: warning: passing argument 2 of 'validate_nets' discards 'const' qualifier from pointer target type
         valid &= validate_nets(config->netif_num, config->macs);
                                                   ^
    /opt/redpill-lkm/config/runtime_config.c:80:20: note: expected 'char (**)[13]' but argument is of type 'char (* const*)[13]'
     static inline bool validate_nets(const unsigned short if_num, mac_address *macs[MAX_NET_IFACES])
                        ^

     

    for the following user_config (obfuscated value of course but i kept the length of it :-) )

     

    Using user_config.json:
    {
      "extra_cmdline": {
        "pid": "XXXXXX",
        "vid": "XXXXXX",
        "sn": "-",
        "mac1": "000000000000",
        "mac2": "000000000000"
      },
      "synoinfo": {},
      "ramdisk_copy": {}
    }