Jump to content
XPEnology Community

Bobwin

Transition Member
  • Posts

    12
  • Joined

  • Last visited

Posts posted by Bobwin

  1. 12 minutes ago, pocopico said:

    You might be able to Use usb loader but again I’ve never tested that


    USB Loader is unfortunately not possible with synology VMM. 
    What I don’t get is that it is possible to install XPE with the Jun loader, but as your probably know that is limited to DSM 6.2.3. 

     

  2. 12 hours ago, pocopico said:

    Hi, do you mean, DSM virtual ? I think you have one DSM virtual license per physical DSM

    Yes that is what I mean. I know about the free license per Synology NAS, I already have used my free license, but I’m in need of another virtual DSM so that is why I thought about trying xpenology.

     I already tried to install xpenology with the RedPill Tinycore loader but I can’t get it to work. It fails when dsm is asking for formatting the disks.

  3. On 8/2/2022 at 3:56 PM, THDJ said:

    Hi all


    Is it possible to developp the loader for work with Virtuals Machines of "Virtual Machine Manager" ?

    @pocopico i have testing multiple configuration for execute the loader in VVM but impossible. Would you have an idea ?

    All the time, when i install DSM 7, i have an error message as  55% with an error reporting that the file is corrupt

     

    I you want @pocopico, contact me in MP to recieve logs and others

     

    Thanks in advance 

     

    BR

     

    THDJ

    Any luck with installing RP on VMM Yet? I’m also looking for a way to install RP on Virtual Machine Manager, until now no success. 
    I did manage to install DSM 6.2.3 with the Jun loader so I guess it should be possible to install RP too if the developers would take a look at it!

  4. I also have tried many times but didn’t succeed. Always get the same error message that file is corrupted. As I have posted earlier somewhere in the forum, I think it has to do with the fact that the two volumes are wiped when installing DSM. So I guess the solution would be to somehow keep the TC partition…but I don’t know how to do that.  
     

    Install DSM 6.2 with the Jun loaders works, I have that running without any problems. So theoretically it should also be possible with TC?!

     

     

  5. 33 minutes ago, Peter Suh said:

    I think Pocopico can tell you more accurately whether boot-wait ext is associated with a 55% error.

    Recently, DS920+ and boot-wait timeout problems were discovered, so I got help to fix the RC script of Pocopico.

    There are many versions of boot-wait ext


    it is not just a boot-wait, the installation just quite because of a error message “the file is probably corrupted..” and than you can’t do anything anymore. 
     

    I guess the problem is related to the fact that the disks are wiped and somehow it losses connection with the bootlader. 
    I’m having the same problem with redpill but the Jun loader works just fine installing DSM 6.2. 
     

    So my guess is that if the bootloader partition could be protected against wiping that it should work, just my simple thoughts..

     

    Installing on VMM 

  6. 3 hours ago, mxmx said:

    Is this something that can be avoided? I've setup both virtual disk 1 (tinycore-redpill.v0.4.6-img) and the virtual disk 2 as SATA disks.

     

    tc@box:~$ ./rploader.sh satamap now

    Machine is VIRTUAL Hypervisor=KVM

    HBA: 00:1a.0 Disks : 6

    HBA: 00:01.1 Disks : 2

    SataPortMap=62

    DiskIdxMap=0002

     

    Using Virtual USB doesn't seem like an option as VMM give option to set USB as boot drive.

    Same here, I also guess it has to do with wiping the disks.

     

    The strange thing is that I do manage to install DSM with the Jun loader, and in doing so it also asks me to erase the disks, but after that the installation goes just fine and I can create my account and log in. I was thus able to successfully install DSM 6.2.3 (DS918+) with the Jun loader.

    So what is the difference?

  7. 3 hours ago, Peter Suh said:

    Why don't we prepare to monitor the flow of the log and watch when that 55% situation appears.


    I also have the same problem...

    Can you explain in a little more detail how to do that, monitoring the log? I'm not very familiar with that.


     

  8. Hi,

    I’m trying to install DSM918+ on a real Synology NAS via VMM (Virtual Machine Manager) with the Redpill loader.

    The bootloader is build just fine and I can find the install page with Synology Assistant, but the installation of DSM just fails every time. After uploading the pat file the installer starts and at 55-56% I get an error message that the file is probably corrupted. I have downloaded the pat file from the Synology site.

    These are my steps to build the loader:

    sudo ./rploader.sh update now
    
    sudo ./rploader.sh fullupgrade now
    
    sudo ./rploader.sh serialgen DS918+ now
    
    sudo ./rploader.sh satamap now
    
    sudo ./rploader.sh ext apollolake-7.0.1-42218 add https://raw.githubusercontent.com/pocopico/rp-ext/master/e1000/rpext-index.json
    
    sudo ./rploader.sh build apollolake-7.0.1-42218 #DS918+
    
    reboot



    When I start the installer I get a message the the disks will be wiped, there is no other choice than accept. Maybe  that has something to do with it?

    Anyone a solution for me how to fix this?

    TIA

  9. On 8/13/2020 at 8:44 AM, leonoxo said:

    Is there a way to use DDSM on another Docker?

    How to solve the network failure after starting another Docker?

     

    The reverse check of the DDSM Container startup command is as follows:

    docker run --name=DDSM --hostname=DDSM --volume=/volume1/DDSM/@synology_dockerdsm_conf/Infostore/:/usr/syno/ddsm/:rw --volume=/volume1/DDSM/Datastore/:/volume1:rw --volume=/volume1/DDSM/@synology_dockerdsm_conf/Confstore/etc:/etc/:rw --volume=/volume1/DDSM/@synology_dockerdsm_conf/Confstore/var:/var/:rw --volume=/volume1/DDSM/@synology_dockerdsm_conf/Confstore/usr.syno.etc:/usr/syno/etc/:rw --volume=/volume1/DDSM/@synology_dockerdsm_conf/Confstore/usr.local:/usr/local:rw --volume=/volume1/DDSM/@synology_dockerdsm_conf/Confstore/root.ssh:/root/.ssh:rw --cap-add=ALL --cap-drop=AUDIT_CONTROL --cap-drop=AUDIT_WRITE --cap-drop=MAC_ADMIN --cap-drop=MAC_OVERRIDE --cap-drop=DAC_READ_SEARCH --cap-drop=LINUX_IMMUTABLE --cap-drop=SYS_ADMIN --cap-drop=SYS_TIME --cap-drop=SYS_BOOT --cap-drop=SYS_MODULE --cap-drop=SYS_RAWIO --cap-drop=SYS_TTY_CONFIG --network=none --label IsSynologyDSM="yes" --log-driver=db --detach=true SynologyDSM:6.1-15284 /sbin/init

     

    --network=none Why is it still connected?

     

    Did you find out if it was possible to install DDSM on another Docker?

    I’m running DDSM on Synology docker, but I would also like to have a version of DDSM running on docker on my Debian VM.

    Anyone know if this is possible and how do a do that?

     

    TIA

×
×
  • Create New...