Jump to content
XPEnology Community

Messenger

Member
  • Posts

    70
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Messenger

  1. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: TCRP v0.4.4 DS3615xs DSM 7.0.1-42218
    - Loader version and model: TCRP v0.9.4.3 DS3622xs+ DSM 7.1.1-42962 Update 1
    - Using custom extra.lzma: no
    - Installation type: BAREMETAL HP N54L

    - Additional comments: Had to modify DiskIdxMap=0001 and SataPortMap=9 to get all my 6 HDDs to work.

  2. Hello all,

     

    today migrated my Nas HP n54l

    seems i am losing one HDD maybe the esata one.

    Can someone give me an advice to repair

    Paste here user_config.json

     

    Evtl. das esata Laufwerk

     

    old Version

     

    {
      "extra_cmdline": {
        "pid": "0xa4a5",
        "vid": "0x0525",
        "sn": "xxxx",
        "mac1": "xxxx",
        "SataPortMap": "58",
        "DiskIdxMap": "0A00"
      },
      "synoinfo": {

              "internalportcfg" : "0xffff",
              "maxdisks" : "16"

    },
      "ramdisk_copy": {

        
    }

    }

     

     

     

    new Version

     

    {
      "general": {
        "model": "DS3622xs+",
        "version": "7.1.1-42951",
        "smallfixnumber": "0",
        "zimghash": "",
        "rdhash": "",
        "usb_line": "",
        "sata_line": "",
        "redpillmake" : "",
        "friendautoupd" : "true",
        "hidesensitive" : "false"
      },
      "ipsettings": {
        "ipset": "",
        "ipaddr": "",
        "ipgw": "",
        "ipdns": "",
        "ipproxy": ""
      },
      "extra_cmdline": {
        "pid": "0xa4a5",
        "vid": "0x0525",
        "sn": "",
        "mac1": "",
        "netif_num": "1",
        "SataPortMap": "58",
        "DiskIdxMap": "0A00"
      },
      "synoinfo": {
        "internalportcfg": "0xffff",
        "maxdisks": "16",
        "support_bde_internal_10g": "no",
        "support_disk_compatibility": "no",
        "support_memory_compatibility": "no"
      },
      "ramdisk_copy": {}
    }

    Quote

  3. Evtl. das esata Laufwerk

     

    alte Version

     

    {
      "extra_cmdline": {
        "pid": "0xa4a5",
        "vid": "0x0525",
        "sn": "xxxx",
        "mac1": "xxxx",
        "SataPortMap": "58",
        "DiskIdxMap": "0A00"
      },
      "synoinfo": {

              "internalportcfg" : "0xffff",
              "maxdisks" : "16"

    },
      "ramdisk_copy": {

        
    }

    }

     

     

     

    neue Version

     

    {
      "general": {
        "model": "DS3622xs+",
        "version": "7.1.1-42951",
        "smallfixnumber": "0",
        "zimghash": "",
        "rdhash": "",
        "usb_line": "",
        "sata_line": "",
        "redpillmake" : "",
        "friendautoupd" : "true",
        "hidesensitive" : "false"
      },
      "ipsettings": {
        "ipset": "",
        "ipaddr": "",
        "ipgw": "",
        "ipdns": "",
        "ipproxy": ""
      },
      "extra_cmdline": {
        "pid": "0xa4a5",
        "vid": "0x0525",
        "sn": "",
        "mac1": "",
        "netif_num": "1",
        "SataPortMap": "58",
        "DiskIdxMap": "0A00"
      },
      "synoinfo": {
        "internalportcfg": "0xffff",
        "maxdisks": "16",
        "support_bde_internal_10g": "no",
        "support_disk_compatibility": "no",
        "support_memory_compatibility": "no"
      },
      "ramdisk_copy": {}
    }

  4. Hallo Allerseits,t k

     

    habe heute mein TCRP und Nas N54l upgedated. Leider fehlt mir jetzt ein Laufwerk und das RAID ist kritisch geflagt hat wer eine Idee was ich machen könnte?

    Danke vorab

  5. I saw this in upgrade Thread:

     

    Posted October 9

    - Outcome of the update: SUCCESSFUL
    - DSM version prior update: TCRP v0.4.6 DS3615xs DSM 7.0.1-42218
    - Loader version and model: TCRP v0.9.2.6 DS3622xs+ DSM 7.1.1-42962 Update 1
    - Using custom extra.lzma: no
    - Installation type: BAREMETAL HP N54L

     

     

     

     

    I have a HP N54L based on TCRP 0.44 DS3615xs.

     

    Can i just upgrade in boot and switch to DS3622xs with new generated serial?

    And under find.synology.com the new generated patfile just upload and everything fine?

     

    Thanks in advance.

  6. Hallo Allerseits,

     

    weiss jemand von Euch, wie man das wol script unter DSM 7 wieder zum laufen bekommt. Bis zu der Version konnte man wol mit dem Script an der nativen nic zum laufen bekommen. Ohne script war die wol Funktion nie gegeben.

     

    #!/bin/sh

    case $1 in
    start)

     if [ -f /var/packages/shutdown_script/DSShutdown.sh ]; then
      /var/packages/shutdown_script/DSShutdown.sh &
     fi
        ;;
    stop)

     if [ -f /var/tmp/shut.down ]; then
      rm /var/tmp/shut.down
     fi
     ifconfig eth0 down

        ;;
    *)
        echo "Usage: $0 [start|stop]"
        ;;
    esac

    S99ZZZ_Shutdown.sh

  7. On 6/1/2018 at 6:12 PM, aol said:

    So where are we? It appears that you:

    - identified that your network infrastructure was not the issue because WOL worked on other boxes, and works on the NAS if you do a forced shutdown (remove power vs. menu -> shut down)

    - made sure that eth0_wol_options="g" in root/etc/synoinfo.conf

    - made sure that support_wol="yes" in same file

    - made sure WOL was ticked in DSM GUI

    - added an rc.d startup/shutdown script named root/usr/local/etc/rc.d/S99ZZZ_Shutdown.sh with the contents from that post (this script appears to do two things: on startup, if the /var/packages/shutdown_script/DSShutdown.sh file exists, it runs it, hopefully you don't have this file; on shutdown it executes the command `ifconfig eth0 down`, which is the command to turn off your eth0 network adapter, which is typically your first or only ethernet port)

    - made it executable via `sudo chmod 755 root/usr/local/etc/rc.d/S99ZZZ_Shutdown.sh` which makes it executable by owner, assuming you created it as root, it would be owned by root

     

    My understanding is that the linux OS DSM is built on is designed to automatically execute scripts in the root/usr/local/etc/rc.d directory on startup passing 'start', and on shutdown passing 'stop', in alphanumeric order, hence that name, which should cause it to be executed last of the rc.d scripts.

     

    And now you are at a weird place where the box doesn't come up clean some times and if it comes up your packages aren't running or aren't appearing correctly in the GUI?

     

    Do you have a file called /var/packages/shutdown_script/DSShutdown.sh? If you do, it appears to be being called at startup if I understand the script. I don't know that you really want to do that. Searching for that file name, I found https://sourceforge.net/p/advpowermgr4ds/discussion/bugs/thread/095d53ea/#8356 indicating to me that it's possible someone reused the script from this post, didn't understand what it did, but since they didn't have /var/packages/shutdown_script/DSShutdown.sh it didn't have any adverse effect. That post has references to the files mentioned in the script which confuse me about why they are being referenced at all. The whole post seems to be about hijacking a Syno package called shutdown_script which may be a pre-requisite for that other post.

     

    The right script as far as I can tell (UNTESTED BY ME) would be

    
    #! /bin/sh
    
    case $1 in
    start)
        # No-op
        ;;
    stop)
        ifconfig eth0 down
        exit 0
        ;;
    *)
        echo "Usage: $0 [start|stop]"
        ;;
    esac

    This script assumes that /bin/sh is the right path to the shell interpreter, which it probably is. It doesn't exit with any code during startup, which is probably fine but may result in a log message. It exits successful (0) during shutdown after doing what you want, which is to turn off your eth0. The `*)` means, if run with any other than start or stop, do this, hence usage. 

     

    So back to your problem, if you have a /var/packages/shutdown_script/DSShutdown.sh file it could be causing problems, and I don't understand the changing of eth0_wol_options="d" to "g" to know if that could cause problems. 

     

    EDIT: as far as I can tell, the eth0_wol_options="g" in root/etc/synoinfo.conf attempts to tell the ethernet card to set Wake-On to "g" (rather than "d"). "d" is disabled, "g" is wake on magic packet. Its the same as doing it manually via the ethtool command, e.g., `ethtool -s eth0 wol g`. You could issue the command `ethtool eth0` to see the settings for the ethernet card. If everything is set properly you should see included in the output

     

    Supports Wake-on: pumbg

    Wake-on: g

     

    the Supports line should include g (the other values don't matter, it needs to support wake on magic packet which means it needs to include a g). And the actual Wake-on setting needs to stay g.

     

    any advice to make it working under DSM 7.0?

    • Like 1
  8. On 12/1/2017 at 2:35 PM, CtrlAltDel said:

    Edit root/etc/synoinfo.conf:

     

    Search for eth0 or the lan connection required for WOL.

     

    eth0_wol_options="d" change the "d" to "g" = eth0_wol_options="g" this will set a tick in the WOL for eth0 in the control panel power settings.

     

    Make sure > wol_enabled_options="g" < is set to "g" not "d"

     

    Make sure > support_wol="yes" <

     

    Copy file or create a file called:

    S99ZZZ_Shutdown.sh

     

    to:


    dsm5.x
    root/usr/syno/etc/rc.d

    dsm6.x
    root/usr/local/etc/rc.d

     

    Set execute permission.

     

    Script command (file content):

    
    #!/bin/sh
    
    case $1 in
    start)
    
     if [ -f /var/packages/shutdown_script/DSShutdown.sh ]; then
      /var/packages/shutdown_script/DSShutdown.sh &
     fi
        ;;
    stop)
    
     if [ -f /var/tmp/shut.down ]; then
      rm /var/tmp/shut.down
     fi
     ifconfig eth0 down
    
        ;;
    *)
        echo "Usage: $0 [start|stop]"
        ;;
    esac

    Now set the WOL option in the synology assistant and then shutdown the machine. Use the WOL option in synology assistant to test WOL is functional.
    If you need WOL over a WAN connection your router will need to be able to pass the magic packet on to the LAN devices.

    someone got it working under dsm 7.0?

  9. The wakeonlanscript under /usr/local/etc/rc.d which works since DSM 5 doesnt work anymore. Someone know how to fix it (HP N54l) under DSM 7?

     

    #!/bin/sh

    case $1 in
    start)

     if [ -f /var/packages/shutdown_script/DSShutdown.sh ]; then
      /var/packages/shutdown_script/DSShutdown.sh &
     fi
        ;;
    stop)

     if [ -f /var/tmp/shut.down ]; then
      rm /var/tmp/shut.down
     fi
     ifconfig eth0 down

        ;;
    *)
        echo "Usage: $0 [start|stop]"
        ;;
    esac

    S99ZZZ_Shutdown.sh

  10. - Outcome of the update: SUCCESSFUL

    - DSM version prior update: DSM 6.2.3-25426 Update 3 - Jun's 1.03b bootloader

    - Loader version and model: RedPill DS3615xs v7.0.1-42218 update 2

    - Using custom extra.lzma: NO

    - Installation type: BAREMETAL - HP N54L 

  11. - Outcome of the update:  SUCCESSFUL

    - DSM version prior update: DSM 6.2.3-25426 Update 2

    - Loader version and model: Jun's Loader v1.03b DS3615XS

    - Using custom extra.lzma: No

    - Installation type: BAREMETAL - HP ProLiant MicroServer N54L

    - Additional comment: Reboot required

×
×
  • Create New...