Jump to content
XPEnology Community

Mokai

Transition Member
 View Profile  See their activity

  • Posts

    14

  • Joined

  • Last visited

 Content Type 

Posts posted by Mokai

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    17 hours ago, Peter Suh said:

     

    Let's assume you are in a baremetal environment.

     

    The last log in dmesg says your e1000e is linked up.

    [ 46.445091] e1000e 0000:00:19.0 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx

     

    However, after that, something seems to have caused this e1000e to stop working.
    I suspect there is a conflict with the nic driver.
    There are no logs to pinpoint exactly.

     

    In the junior mode, which is the installation stage of DSM,
    You should analyze the log file /var/log/linuxrc.syno.log.
    You should collect this log file after ttyd or telnet connection through the spare nic.
    Another way you can do without a nic is through a serial port.

     

    For now, the former seems to be the easiest.

     

    Following your mention to the junior mode, I took a new look at the troubleshooting section of https://xpenology.com/forum/topic/62221-tutorial-installmigrate-to-dsm-7x-with-tinycore-redpill-tcrp-loader/ and considered building the loader for another model: by choosing the DS3622xs+ I no longer got that NIC issue and have even been able to upgrade to 7.1.1! so far so good.

    Although I am a little bit frustrated to not understand why it works now, I am really happy to have been able to complete that challenge! :)

    • Like 1
    • Thanks 1

    TinyCore RedPill Loader (TCRP)

    in Loaders

    Posted

    Hello DSM & TCRP experts,

    I need your help after spending days stuck in upgrading my DSM 6.2 setup with Jun's loader to the 7.0.1 with TCRP, here are the details:

     

    The starting point is:

    • Synology Model DS3615xs
    • DSM version: DSM 6.2.3-25426 Update 2
    • A SAS LSI Megaraid card with 6 Sata disks
    • 2 Sata SSD I was using for caching (I removed this cache before the installation)

    The procedure to create the loader I am following is:

    1. ./rploader.sh update now
    2. ./rploader.sh fullupgrade now
    3. ./rploader.sh serialgen DS3615xs realmac (I after update the serial in user_config.json to set the current 6.2.3 serial)
    4. ./rploader.sh identifyusb now
    5. ./rploader.sh satamap now -> override the number of sata disks to 2
    6. ./rploader.sh ext ds3615xs-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/megaraid_sas/rpext-index.json
    7. ./rploader.sh build ds3615xs-7.0.1-42218

    You can find attached:

    • The output of the dmesg command executed from the tinycore shell
    • The output of the ./rploader.sh satamap where you can see the errors "lspci: -s: Invalid slot number"
    • The output of the build
    • The user_config.json that I later slightly customized through my multiple tries to support the SHR1 I have currently and do not have HD compatibility issues wit DSM

    After reboot, the loader seems to load correctly up to the "Booting the Kernel" message on the screen but after:

    • The DSM is not connecting to the network, not visible from synology assistant, etc...
    • The link led of the ethernet port stops blinking, it becomes off!

    What can be wrong I could investigate further?

     

    Thanks.

    dmesg.txt satamap.log build.log user_config.json

    Troubleshooting log of XPenology boot loader?

    in The Noob Lounge

    Posted · Edited by Mokai

    Hello,

     

    I am unable to get access to DSM from the network with the following Baremetal config:

    Intel DH77DF motherboard

    Processor intel core i5 2500K

    RAM ddr3 balistix 1600mhz, 2x8G

    with a LSI MegaRaid 9260-8i card.

     

    The DSM info is:

    • DSM file: DSM_DS3615xs_25426.pat
    • Loader: jun v1.03b ds3615xs

     

    There is no error displayed in the console (I have the usual text mentioning "Happy hacking"), I am pretty sure I am not facing a cid/vid or mac issue, considering the number of tests and checks done. 

    When booting from Jun's loader, my machine is not accessible, no IP address has been granted by the DHCP, although the network card link light is blinking.

    It is really like the onboard network card is basically not recognized...

     

    I have tried:

    • Testing access from Synology Assistant or find.synology.com
    • 2 different USB keys on various USB ports
    • Various versions of Jun's loaders available, for different DSM versions
    • Updating the drivers (extra.lzma) with various versions of packages available
    • Playing with BIOS boot options (Legacy, UEFI)

     

    If I boot Ubuntu or ESXi from an USB on the same machine, the network works fine.

     

    I need to get logs to better understand what could be wrong.

     

    In such context, how can I access to the dmesg output?

    Some posts are referring to the serial, but I have no serial port but an usual screen :)

    I have tried to play with the loglevel kernel option in the grub.cfg, without any change.

     

    FYI: I already used ESXi on that system to run DSM: no network problem.

     

    Thank you

    ESXi vs bare metal

    in The Noob Lounge

    Posted

    One question for ESXi experts in the course of this thread: I finally opted to an ESXi DSM installation to workaround XPenology installation problems in Baremetal mode (I have an Intel DH77DF motherboard with a LSI MegaRaid 9260-8i card) but I am facing an issue:

    I have only one VM hosted under ESXi and I can't allocate it the 16 GB of RAM available, I am limited to around 12 GB. Posts on the net didn't help me much, because they were rather dealing with general resource reservation questions and vSphere, not useful for this case.

    Is there any hint or resource to properly grant all hardware resources to the VM running DSM?

    Clavier francais sous Nanoboot?

    in Archives

    Posted

    Hello,

     

    Est-ce que quelqu'un sait comment configurer le keyboard layout pour le passer en Francais avec Nanoboot (pour la console)?

    Cela me permettrait d'utiliser la console avec un clavier Azerty.

     

    En effet, j'ai régulièrement des problèmes de DHCP et pour le moment le seul moyen de rebooter le boitier est de le rallumer violemment.

    Le mode console me donnerai plus de possibilités.

     

    Ma config:

    N54L

    DSM 5.0 4493 Update 3

    XPEnology DSM 5.0-4493 Discussion / Bootloaders

    in Readers News & Rumours

    Posted

    Hello,

     

    I successfully updated by N54L DSM-5.0 4493 Nanoboot based from Update 3 to Update 4 by:

    • Downloading the update
    • Executing the usual commands
      sed 's/flashupdateDeb/flashupdateDeb1/' /autoupd@te.info > /autoupd@te.info1
mv /autoupd@te.info1 /autoupd@te.info


    • Installing the update

     

    Although I am able to access to the Synology web interface, the Synology assistant is stating that my NAS is not configured, starting the configuration wizard after each discovery!

     

    What should I do?

    How can I set it to the regular "configured" state without breaking my working setup?

     

    Thanx

×
×
  • Create New...