Jump to content
XPEnology Community

Jseinfeld

Member
  • Posts

    44
  • Joined

  • Last visited

Posts posted by Jseinfeld

  1. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 7.2-64570 Update 3

    - Loader version and model: arpl-i18n 23.11.10  DS920+
    - Using custom extra.lzma: NO
    - Installation type: BAREMETAL - Asrock J4105

    - Additional comments: Flashed arpl-i8n image onto USB. Booted into USB, went into "Advanced" & "Try to recovery a DSM installed system". This was successful and system booted into DSM

  2. Just now, wjz304 said:

    The current update-check.sh has two functions,

    1. Check whether the environment matches the new version,
    2. Modify the changes.


    It is not recommended to upgrade from i18n to RR due to many factors.

    If you have not done a lot of configuration for booting and the DSM is the latest version, rewriting the bootloader disk and trying to restore booting will not affect the dsm system.

     

    For security reasons, you can also back up the current USB flash drive first, or try changing the USB flash drive.

     

    Because I am just one person, I often cannot think carefully. If the version span is too large, it may be more likely to be incompatible. This is one of the reasons why it is not recommended to directly upgrade from arpl-i18n to RR.

    Thanks, currently on DSM 7.2-64570 Update 3 and on i8n 23.6.4.

     

    I am using basic standard i8n config. No extra modules, no nothing. Very simple home system.

     

    If I create new disk, how to restore booting of DSM system?

  3. 9 hours ago, wjz304 said:

     

    I am on version 23.6.4. I saw the video but there is no "Local Upload" option to select files in the "Update Menu". How do I apply the update.zip file to my install manually? When I try to update, it tries to download 23.11.8 but fails, saying not compatible

     

    So I unzipped the update.zip file. There is update-check.sh and some other files. Do I just replace the files as specified in update-list.yml and then run the update-check.sh file?

  4. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 7.2-64570
    - Loader version and model: arpl-i18n 23.6.4  DS920+
    - Using custom extra.lzma: NO
    - Installation type: BAREMETAL - Asrock J4105
    - Additional comments: Manual update via GUI

  5. So I downloaded the latest 7z binary and the results are even better with it. Looks like my CPU is boosting and everything correctly.

     

    Plus the DSM is updating apps in the background, the Web Interface is open, have 2-3 SSH connections to it, etc. Apart from all the background services that run on it.

     

    ./7zz b -mmt4 -md26
    
    7-Zip (z) 23.01 (x64) : Copyright (c) 1999-2023 Igor Pavlov : 2023-06-20
     64-bit locale=en_US.utf8 Threads:4 OPEN_MAX:1024, ASM
    
     mt4 d26
    Compiler: 9.4.0 GCC 9.4.0: SSE2
    Linux : 4.4.302+ : #64570 SMP Sat Jun 3 00:00:25 CST 2023 : x86_64
    PageSize:4KB hwcap:2
    Intel(R) Celeron(R) J4105 CPU @ 1.50GHz (706A1) 
    
    1T CPU Freq (MHz):  2376  2383  2383  2388  2435  2448  2448
    2T CPU Freq (MHz): 200% 2381   200% 2382  
    
    RAM size:   15645 MB,  # CPU hardware threads:   4
    RAM usage:   1629 MB,  # Benchmark threads:      4
    
                           Compressing  |                  Decompressing
    Dict     Speed Usage    R/U Rating  |      Speed Usage    R/U Rating
             KiB/s     %   MIPS   MIPS  |      KiB/s     %   MIPS   MIPS
    
    22:       9326   344   2639   9073  |     146986   367   3419  12540
    23:       8895   358   2534   9063  |     149042   382   3375  12896
    24:       8465   359   2535   9102  |     137129   365   3296  12034
    25:       8094   356   2596   9242  |     139043   382   3236  12375

     

    • Like 1
  6. Are you using the DS918+ model? I have a J4105 and use the DS920+ model.

     

    My CPU results are almost identical to the results under Windows 10 for you. Which is what I would expect, considering that the DS920+ uses an Intel CPU from the same family. So they should be quite similar.

     

    7z b -mmt4 -md26
    
    7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21
    p7zip Version 16.02 (locale=en_US.utf8,Utf16=on,HugeFiles=on,64 bits,4 CPUs x64)
    
    x64
    CPU Freq: - - - - - - - - -
    
    RAM size:   15645 MB,  # CPU hardware threads:   4
    RAM usage:   1618 MB,  # Benchmark threads:      4
    
                           Compressing  |                  Decompressing
    Dict     Speed Usage    R/U Rating  |      Speed Usage    R/U Rating
             KiB/s     %   MIPS   MIPS  |      KiB/s     %   MIPS   MIPS
    
    22:       7350   348   2056   7150  |     110700   385   2451   9444
    23:       6969   356   1997   7101  |     107489   385   2415   9300
    24:       6653   362   1977   7154  |     105164   388   2381   9232
    25:       6230   361   1970   7113  |     100953   383   2345   8985

     

  7. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 7.1.1-42962 Update 5
    - Loader version and model: arpl-i18n 23.6.4  DS920+
    - Using custom extra.lzma: NO
    - Installation type: BAREMETAL - Asrock J4105
    - Additional comments: Upgraded from arpl 1.11 by flashing arpl-i8n image onto USB. Didn't get prompt to migrate from old install. Had to setup everything again.

  8. On 6/3/2023 at 6:12 PM, bloodilo said:

    How can I change SN+MAC of BAREMETAL ASROCK 5040 ARPL 920+ 7.1 remotely? I mean I'm not physically at the location where the unit is located, but I do have VPN to the network (GUI and SSH access are working). I found several similar posts, even for TCRP or Proxmox, but not really an answer HOW TO. Any tip?

     

    Mount the USB and change the config in the JSON

  9. My system is currently running on ARPL and I have this issue where a lot of spam log messages are being generated. It has been reported here: https://github.com/fbelavenuto/arpl/issues/489#issuecomment-1382693032

     

    Seeing the same messages in the log files as the comment linked. Currently running the DS920+ config on DSM 7.1.1-42962 Update 5

     

    Now I am just wondering if this also happens on TCRP. Do these spam log messages also show up on TCRP installs?

     

     

  10. On 12/10/2022 at 1:29 AM, pleitex said:

    But with what software are the commands executed? With CMD in windows?

    But with what software are the commands executed? With CMD in windows?

     

    amisetupwriter is an EFI Shell executable. 

    To get into the EFI Shell

    1. Format a USB Disk to FAT32
    2. Copy over the EFI folder and amisetupwriter.efi file to the USB
    3. Disconnect all your SATA / other disks, as it will make it easier to mount the USB. Ideally the USB should be the only disk on the system
    4. Reboot from USB
    5. It will boot into a weird text interface, with the prompt as "Shell>"
    6. Here type in the command "map -r"
    7. This will mount all the disks
    8. The USB should be fs0. Select it by typing in "fs0:"
    9. The prompt will change to "fs0:\>"
    10. Now if you run the "dir" command it should display the contents of the USB
    11. Finally you can run the "amisetupwriter"

     

    • Like 1
  11. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 7.1.1-42962 Update 4
    - Loader version and model: Automated Redpill Loader 0.4 alpha 11  DS920+
    - Using custom extra.lzma: NO
    - Installation type: BAREMETAL - Asrock J4105
    - Additional comments: Manually downloaded PAT & installed via Web UI.

  12. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 7.1.1-42962 Update 3
    - Loader version and model: Automated Redpill Loader 0.4 alpha 11  DS920+
    - Using custom extra.lzma: NO
    - Installation type: BAREMETAL - Asrock J4105
    - Additional comments: Manually downloaded PAT & installed via Web UI.

  13. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 7.1.1-42962 Update 2
    - Loader version and model: Automated Redpill Loader 0.4 alpha 11  DS920+
    - Using custom extra.lzma: NO
    - Installation type: BAREMETAL - Asrock J4105
    - Additional comments: Manually downloaded PAT & installed via Web UI. Update completed without need for Reboot. Manual Reboot worked just fine

  14. On 12/19/2022 at 3:11 PM, gericb said:

    I THOUGHT the only way the networking would actually function at all, was the TCRP encoded MAC address HAD to match the ACTUAL hardware MAC address of what your motherboard or add-in ethernet port had.

     

    This is not a requirement on any OS or any device for that matter. It is trivial to fake one's MAC address.

     

    In Linux you can do it with ifconfig. In Windows, there used to be tools for this, but it just a registry thing from what I remember. Some LAN cards even have the option to set a custom MAC in the Hardware Properties page in Device Manger. On iOS & macOS, the OS does it automatically when the option is enabled for privacy reasons.

  15.  

    - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 7.1.1-42962 Update 1
    - Loader version and model: Automated Redpill Loader 0.4 alpha 11  DS920+
    - Using custom extra.lzma: NO
    - Installation type: BAREMETAL - Asrock J4105
    - Additional comments: Auto-update doesn't pick up this, due to the outdated XML file on the ARPL repo. Manually downloaded PAT & installed via Web UI.

  16. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 6.2.3 -25426
    - Loader version and model: Automated Redpill Loader 0.4 alpha 11  DS920+
    - Using custom extra.lzma: NO
    - Installation type: BAREMETAL - Asrock J4105

    - Additional comments: This was a pretty simple upgrade. Here are some tips

     

    • After install, the NAS would boot but would seemed to shutdown mid-way automatically. Ping would work, but HTTP would refuse connections. Turned out to be the i915 module. Rebuild the loader with defaults and it worked great.
    • For some reason 1 of 6 disks was detected as eSATA. Changing the physical port the disk was attached to worked
    • Apart from these, it was a simple process. Everything works great. Even have the /dev/dri folder working
  17. CubeNet is still erroring out in NZBGET after running the script.

     

    It says

     

    "TLS certificate verification failed for secure.europe.thecubenet.com: certificate has expired. For more info visit http://nzbget.net/certificate-verification"

     

    Did the steps they mention and even manually added the chain files to cacert.pem in the NZBGet "bin" folder, but no luck

     

    `openssl s_client -showcerts -connect secure.news.thecubenet.com:80`

     

    This command works perfect on the DSM and says "Verify return code: 0 (ok)". Not sure what nzbget is getting hung up on
     

  18. - Outcome of the update:  SUCCESSFUL

    - DSM version prior update: DSM DSM 6.2.3-25426

    - Loader version and model: Jun's Loader v1.04b DS918+

    - Using custom extra.lzma: Yes, v0.13.3 for 6.2.3 by IG-88 

    - Installation type: BAREMETAL - J4105-ITX + 8GB RAM

    - Additional Notes: With the powerbutton fix installed, didn't encounter any trouble with the reboot. Came up just fine after the update. HW Accel also working on first boot.

×
×
  • Create New...