Jump to content
XPEnology Community

maxime

Member
  • Posts

    151
  • Joined

  • Last visited

Posts posted by maxime

  1. 13 minutes ago, pkdick1 said:

    I am not sure I understand what you are proposing: my NAS always stays plugged on the power. Do you mean that after shutdown, "creating" a fake "power disconnection" and reconnection would lead to a startup for the NAS?

     

    Yes! If you need WOL, it means that your system, for any reason, is powered off. If you can't use WOL (f.e. because your NIC doesn't support it), and you have a Smart Plug connect to your server, you can power off and then power on the smart plug. This operation will turn on your server.
    Obviously you must first set your Mainboard's bios for auto-start after a power disconnection. 

  2. 6 minutes ago, Peter Suh said:

     

     

    Unfortunately, the product description does not say that WOL is supported anywhere.

     

    2023-06-1210_42_41.thumb.png.cf15b7c584e043e6667dbeaea763bca5.png

     

     

    Also, check the following settings in DSM once more.

     

    2023-06-1210_40_26.thumb.png.22e55e22fd56852c640d2e8a43120f4e.png

     

    DS923+ supports powersched.
    However, in 7.1.1, rtc-cmos.ko had a compatibility problem reported, and at that time, the test was successful by replacing it with a module of v1000.
    I will test again in an environment where WOL and powersched work well to see if the same phenomenon exists in 7.2.
    But your new 2.5G M.2 type dual nic may not be guaranteed to work.
    Is there no nic to replace this nic?


    I hope you will solve your WOL problem, but if you can't, you could use this workaround: using a Smart Plug (like this https://a.co/d/cO3gecV), you can switch on your server remotely, and you can have consumption statistics, too. I know it's a last and not professional possibility, but it can be considered.

  3. 42 minutes ago, Peter Suh said:

     

    first:
    -> TCRP ( same for ARPL ) Always use full size DSM PAT files when building loaders.
    For DS3622+ or DS918+, 7.1.1-42962 U1 (with update 1)
    Corresponds to the final version with full size.

    In particular, in the case of DS923+ / DS723+ / RS4021xs+, 7.1.1-42962 U5 exists in full size.

    If you go to the path below, PAT files that exceed approximately 300M are such files.
    https://archive.synology.com/download/Os/DSM

     

    After that, you need to additionally install the required SMALL Update version.
    After the Small Update version is installed, FRIEND proceeds with RD automatic patching.

     

    second:
    -> You don't have to use the UEFI version of IMG to boot into UEFI.
    Legacy versions are also compatible with UEFI.
    If you have problems with the legacy version of IMG, I know that the workaround is to use the UEFI version of IMG.
    This part borrows the image produced by pocopico as it is in M SHELL, so I don't know exactly how it works.

     

    And is there any benefit to using DS923+ instead of DS918+? Should I change the version to DS923+? I'm watching your signature and I see you used two different kind of loader in your servers: one use Jot and another one use Jun. Why you choose that? Isn't June a newer (and than better) kind of loader?

  4. 6 minutes ago, Peter Suh said:

     

    first:
    -> TCRP ( same for ARPL ) Always use full size DSM PAT files when building loaders.
    For DS3622+ or DS918+, 7.1.1-42962 U1 (with update 1)
    Corresponds to the final version with full size.

    In particular, in the case of DS923+ / DS723+ / RS4021xs+, 7.1.1-42962 U5 exists in full size.

    If you go to the path below, PAT files that exceed approximately 300M are such files.
    https://archive.synology.com/download/Os/DSM

     

    After that, you need to additionally install the required SMALL Update version.
    After the Small Update version is installed, FRIEND proceeds with RD automatic patching.

     

    second:
    -> You don't have to use the UEFI version of IMG to boot into UEFI.
    Legacy versions are also compatible with UEFI.
    If you have problems with the legacy version of IMG, I know that the workaround is to use the UEFI version of IMG.
    This part borrows the image produced by pocopico as it is in M SHELL, so I don't know exactly how it works.

     

    FIRST: OK, then is possible that on test hardware, after the installation (7.1.1-42962 U1), the system automatically updated to Update 5 without me realizing it... 
    when you say "you need to additionally install the required SMALL Update version", you mean to install PAT files using manual installation from Synology Web Interface, right?

     

    SECOND: It seems clear. thanks!

  5. Hi! I've a couple of question:

    FIRST: 
    I tried to install XPEnology DS3622xs+ on a test hardware (I7-3770) using the Tiny Core RedPill M-Shell v0.9.4.3-2; it perfectly works and installed by default DSM 7.1.1-42962 Update 5.
    Now I tried to change the loader of my XPE DS918+(see my signature), using Tiny Core RedPill M-Shell v0.9.4.3-2, too. In this case the system installed DSM 7.1.1-42962 Update 2. Why? Did the System check something of my hardware that is not compatible with Update 5? Can I try to manually upgrade my system to Update 5, or do I risk to break the System?

    SECOND:
    If I try to use the UEFI version of Tiny Core RedPill M-Shell, Synology Assistant can't find my server; I have to use the NON UEFI version of Tiny Core RedPill M-Shell to make my XPE server working. What are the differences to use the UEFi version compared to the NON EUFI one?

     

    I attached the screenshot when I try to start my server with UEFI version: 

    Thank you very much for your support!

    UEFI.jpg

  6. On 4/15/2023 at 5:24 AM, Peter Suh said:

     

    I don't know if you are using my M SHELL for TCRP FRIEND or pocopico's.

     

    My M SHELL has a function to easily add MAC2 on the menu.

     

    If it is pocopico's TCRP, you can add more M SHELL functions with the command below.

     

    If you execute the command below, ./menu.sh is automatically executed and the M SHELL menu appears.

     

    curl -k -L "https://raw.githubusercontent.com/PeterSuh-Q3/tinycore-redpill/master/my.sh.gz" -O; tar -zxvf my.sh.gz ; ./rploader.sh backup; ./menu.sh

     

    In this menu, select MAC ADDRESS 2 to finish adding mac2.

     

    Then, rebuild with the FREIND loader.

     

    1270515129_2023-04-1512_19_07.png.8bf8b34de494efcea77bb4f2fcdac7be.png

    Thanks a lot Peter; I installed M-Shell (what incredible work, you did!) and add a second NIC... it works like a charm!
    Many thanks for what you do in this community

    • Like 1
  7. On 3/25/2023 at 3:18 PM, Peter Suh said:

    [NOTICE]

     

    Multilingual support for M SHELL for TCRP menu.


    Currently, nine languages are supported: Korean/Chinese/Japanese/Russian/French/German/Spanish/Italian/Brazilian.


    English is included as standard.


    Because of this, the version has been raised to 0.9.4.3-1 .


    This is a pre-built version of the Tinycore Unicode package for multilingual support.


    https://github.com/PeterSuh-Q3/tinycore-redpill/releases/tag/v0.9.4.3-1

     

     

     

     

     Hi! How to change language? It starts in Korean language (I suppose), and I can't understand... 😅

×
×
  • Create New...