Jump to content
XPEnology Community

merve04

Member
  • Posts

    328
  • Joined

  • Last visited

  • Days Won

    4

Posts posted by merve04

  1. - Outcome of the update: SUCCESSFUL
    - DSM version prior update: DSM 7.1.1-42962 Update 4
    - Loader version and model: TCRP v0.9.4.3-2 w\Friend 0.0.6 (DVA1622)
    - Using custom extra.lzma: NO
    - Installation type: BAREMETAL - Gigabyte B365-DS3H, i5-8400, 8x12TB, 2x4TB
    - Additional comments: Updated via DSM GUI

  2. On 4/12/2023 at 8:21 PM, Peter Suh said:

     

    Are the LEDs on the NIC lit?


    In addition, the ability to check with the Getty console when the NIC is not operating is
    Added to my M SHELL for TCRP FRIEND.
    Please refer to the contents below and create the loader again.

     

     

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

     

     

    Well I used pocopico's tcrp to generate a UBR serial# and inputed it in your build, happy it booted in DSM but just like last time in July '22, it wiped all my personal settings without prompting me if I wanted or not. Its frustrating but i guess the important thing is my data is intact. Thanks for the support.

    • Like 1
  3. I'm not sure why its the menu.sh is all in chinese or something, but i managed to go through the menu by just hitting enter,enter,enter,enter and it started building the key, im concern that the SN is of SJR type. Server got the same error on Friend screen, but i let it boot and synology assistant showed system as migrate-able. I guess before I decide to proceed, how can i adjust the SN so i wont have an issue with surveillance station?

    IMG_5594.jpg

  4. 19 hours ago, Peter Suh said:

     

    Anyway, since nic seems to be working, let's check the log through junior.
    It seems that you are already in junior mode because you haven't installed DSM yet.
    Please check and attach the log through the TTYD web console as shown below.

     

    You must use a web browser.

     

    http://<youripaddr>:7681/

    id : root / pw : ( no password )

     

    cat /var/log/linuxrc.syno.log

     

    ls -l /sys/block

     

    ls -la /sys/class/ata_device

     

    ls -l /dev/syno*

    Here is what I get on the TCRP friend screen.

    Regarding your instructions, when booting my server with the functional USB key, if i enter my ip, http://10.10.1.101:7681/ in my web browser, firefox, I get connection closed.

     

    IMG_5581.jpg

  5. 1 hour ago, Peter Suh said:

     

    Your hardware information is insufficient.

     

    Please attach a screen capture of the monitor where TCRP FRIEND is executed and tell me your H/W specifications.

    (MOBO model, separate use of Sata controller, etc.)

     

    I guess I'll have to check the junior logs if needed.

    I've attached a screenshot of the cat /proc/cmdline

     

    I have a Gigabyte B365M DS3H, Intel i5-8400, 2x 16GB Corsair ram, 2x jmicron jmb585.

     

    My server is currently occupied hosting streams but at my next availability, I can boot the usb key back up and take a picture of when the tcrp friend screen comes on.

     

    It's my understanding I do not need to do "./rploader.sh satamap" due to DVA1622 uses devicetree and sometime ago TCRP had an automated approach in finding the drives.

    IMG_5580.jpeg

  6. 2 hours ago, pocopico said:

     

    Check your cmdline while DSM is up and running (with old loader) by running cat /proc/cmdline and then use these values to recreate your new loader.

     

     

    Thanks for the response, I followed the command as you suggested, I see many lines with values. Which ones should I be paying attention too?

  7. Hi, I’m really hoping someone can point me in the right direction. 
    I’m using a fairly dated version of TCRP 0.9 and dva1622 7.1

    I really want to upgrade to latest TCRP so I can be up to date on DSM. 
     

    Here are the steps I’ve taken this far. 
     

    Download/write latest TCRP to usb drive

    Booted flash drive and performed these commands. 
     

    ./rploader.sh update

    ./rploader.sh fullupgrade

    ./rploader.sh identifyusb

    ./rploader.sh serialgen DVA1622 realmac

    ./rploader.sh build dva1622-7.1.1-42962 withfriend

    exitcheck.sh reboot

     

    when system booted back up, the tcrp friend page came one but no IP detected. 
     

    when I opened synology assistant, machine was discovered but status was not installed. When I open the IP, I get no drives detected.

    i shut down the machine, reinserted my previous usb key and rebooted machine, everything is back now.

     

    what am I not doing correctly here?

    any help is much appreciated. 

     

     

  8. 9 hours ago, phone guy said:

    I personally have not built or used a dva1622 except to test if it would load on my cpu, but taken from the first page of this thread, I have to assume the correct postupdate command to update dsm7.1 to 7.1u4 on a dva1622 is:

    ./rploader.sh postupdate dva1622_42661 

    You might wait until @pocopico or another user confirms this. But I see no reason this would not be the case.  <yourplatform> for dva1622 is dva1622_42661

    Thank you for your input on this, yes I have time to wait for a definitive answer.

  9. 38 minutes ago, phone guy said:

    If you're talking about the 7.1u4 update, it's pretty simple... assuming you are on 7.1, you download the 7.1u4 update for your platform go to synology.com and get the 7.1 update 4 file for your platform (dva1622-7.1u4) which should be around 50mb. Do the manual upgrade inside DSM, on the reboot, at the grub menu, press down arrow on the keyboard to the bottom item which is boot into tinycore, ssh in to your tinycore session and do these commands

    ./rploader.sh backup now
    ./rploader.sh update now
    ./rploader.sh fullupgrade now
    ./rploader.sh postupdate <yourplatform>
    
      reboot and change grub menu back to original loader method

     

    That's pretty much it. Has worked for me on DS918 (apollolake-7.1.0-42661) and DS3622 (broadwellnk-7.1.0-42661) and boom, 7.1u4! ;)

     

    EDIT: I literally just wrote this full guide for a guy trying to upgrade from 7.0 to 7.1u4, its super detailed, so if you need any more guidance, just ask.

    I much appreciate your reply on this, but once again i feel nervous about what to enter in "<yourplatform>", hence why i ask is inputing "geminilake-7.1.0-42661" the correct value for the process?

    Thanks again.

  10. 4 minutes ago, phone guy said:

    I have never used that command (exitcheck.sh) in any of my builds, test builds, etc. Never saw that mentioned before. Thanks for the reply.

    Unfortunately I couldn’t tell y’a what exactly it does, and I’m still in the dark in the correct command procedure for applying an update to DSM. I’ve read if you don’t do it, machine goes in an infinite loop. 

  11. 7 hours ago, phone guy said:

     

    what is exitcheck.sh ?

    Not sure, but I’ve seen this posted several times, I’ve used it myself when building the loader in TC. I guess I figure since dva1622 is based of Geminilake that it would be the command line to use for post update. But I’m really not sure if it’s correct as when building the loader I never used the word “geminilake” in any of the commands. 

  12. Outcome of the update: SUCCESSFUL

    - DSM version prior update: DSM 6.2.3 Update 3 - JUN'S LOADER v1.04b - DS918+

    - Loader version and model: tinycore-redpill.v0.9.0.2 - DVA1622

    - Using custom extra.lzma: NO

    - Installation type: BAREMETAL - Gigabyte B365 DS3H, Intel i5 8400, 32GB DDR4, 2x JMB585 PCI-e 3.0

    - Additional comments: Standard install as per guides made available on this site.

×
×
  • Create New...