Jump to content
XPEnology Community

Invaliduser

Transition Member
  • Posts

    18
  • Joined

  • Last visited

Posts posted by Invaliduser

  1. Thank you again Pocopico and everyone else that has contributed to this!
    Quick note for those using proxmox with a DS3622xs+ build and want to get "better" hard drive performance from your SATA drives.
    I've been playing around with drive configs and I'm getting much better performance attaching the storage drives in Proxmox as SCSI rather than SATA.

    This is kind of a duh moment... but I didn't realize the 3622xs+ would recognize a SCSI storage drive and I didn't realized the performance would increase that dramatically. 
    My hardware is a pretty generic gigabyte motherboard with a Ryzen 3 3200G, 2 WD Red 4TB Drives in ZFS connected to the integrated SATA controller.
    I built the Proxmox vm using DS3622xs+, Processor Type = host, Storage Drives initially = SATA.

     

    Running drive stress test as follows on my storage drives attached as SATA:

    dd bs=1M count=2048 if=/dev/zero of=/volume1/downloads/testx conv=fdatasync
    2048+0 records in
    2048+0 records out
    2147483648 bytes (2.1 GB, 2.0 GiB) copied, 40.42 s, 53.1 MB/s

     

    ^^Terrible^^

    I powered off the VM, detached the storage drives, and reattached as SCSI.

     

    New stress test:
    dd bs=1M count=2048 if=/dev/zero of=/volume1/downloads/testx conv=fdatasync
    2048+0 records in
    2048+0 records out
    2147483648 bytes (2.1 GB, 2.0 GiB) copied, 12.7126 s, 169 MB/s

     

    ^^Much better.^^

     

    Note that doing this, your storage drives will show up as drive 13, 14, 15, etc and will not display in the storage manager overview graphic.  I'm assuming this is because the 3266xs+ uses SATA for the front slots disk 1 - 12.

    Note that this is only for your storage drives and not the boot drive.

  2. 19 minutes ago, marigo said:

    I have tried to update my VM on Proxmox from 6.2.3 to 7.0.1 (apollolake-7.0.1-42218) but no IP is given from DHCP.

    My setup is to boot from Juns loader 1.04B and have one bootdisk on SATA0 and a datadisk on SATA1:

     

    • vm-xxx-disk-0.raw <- bootdisk
    • vm-xxx-disk1.qcow2 <- datadisk

    I deleted the bootdisk (detach and remove drive) and added a new (raw) bootdisk with 2GB capacity. Changed the NIC from "E1000" to "Virtio", loaded Tinycore loader on this disk and booted. Everything is looking fine, Update the user_config.json and backup this configuration.

     

    After the reboot (booted in grub menu from SATA) there is no connectivity and no IP address has been given out by DHCP.

    If I stop this VM and detach my datadisk (which was previous om dsm6.2.3) and boot again, I get an IP address from DHCP and find.synology.com finds this "Diskstation".

    But there are no disks found to install DSM.

     

    Am I missing something here? I thought it could be the "satamap" so I applied "./rploader satamap now" and this will find the disks in KVM and added to user_config.json

    But that didn't do the trick.

     

    When I create a new VM with Tinycore loader, I can add a second disk with no problem and install DSM7 normally. So greenfield works, but upgrade not yet.

    Hope someone can point me in the right direction.

     

    Are you generating a new mac address for the 7.0.1 build?  If so, you will need to assign that mac address to the VM's network device.

     

    • Thanks 1
  3. 16 hours ago, CaCO3 said:

    Hi all

     

    I tried to get it working with Virtual Box (without an USB drive), mainly orienting on https://xpenology.club/install-dsm-7-on-baremetal-or-vm/. I seem to be able to configure it correctly with the scripts. When I reboot my virtual machine, I see 2 new entries in grub, one for USB, one for SATA.
    But which ever I boot, it gets stuck on "Booting the kernel.".

    Has anybody a tip for me?

     

    Stopping at "booting the kernel" is normal.  Use find.synology.com to discover the VM on your network.  If additional troubleshooting is needed you will need to setup a serial interface with the VM to check the boot process.

  4. 23 minutes ago, Dvalin21 said:

    Hey, what is the best way to pull the pat file from the cache folder? I've done the build, backed up everything and then placed the usb at another computer to extract it. The cache folder is not there. 

     

    GUI - use Winscp, filezilla, or similar to extract immediately after building.
    Or something like sshfs via command line.

    • Thanks 1
  5. 12 minutes ago, Kaneske said:

    Yes, that helps. I think I got that. pocopico thanks for your Time and Help.

     

    I am stuck. Can’t get find.synology.com show my rig anymore…no chance tried everything…

     

    If you are able to connect via serial, you will see the IP Address being assigned.

  6. 7 hours ago, Franks4fingers said:

    I have upgraded today and am now running Apollolake 7.0.1-42218. I have got Plex MS up and running and have repaired other packages that needed it. Python fails to update but I believe Python is an issue anyway in DSM7.

     

    One thing that has happened is that I have lost the ability to connect to Sonarr, Radarr or NZBGet which I run via Docker.

    (EDIT - I actually see these packages are available via the SynoCommunity repo so would I be better off just to stop the Docker containers and instead install the packages from SC?  I used to them ages ago but they weren't being regularyl updated which is why I decided to give Docker a go)

     

    Has anyone else got these apps running in DSM7 and did you need to do anything specific for them post migration from 6.2.*

     

    Great work pocopico as well, its a pretty seamless migration path when you get your head around it. Well done.

     

    It may be the volume mapping.

    On my install (broadwell 7.0.1-xxxxx) (i'm still testing everything for now) I was able to download the images from the registry and import the container settings from my previous 6.2 install.  All looks to be working fine.

    • Like 2
  7. 5 minutes ago, krisr77 said:

    has somebody had an issue when after successful (i  guess, no errors) build and reboot cannot access dsm loader page ? (no ping, no output on browser, find.synology.com also cannot find new dsm). installation is on VM (vwamre player so card network is E1000). Builder Linux appliance is getting proper ip address an has internet connection without any problem)

     

    Do you have a serial connection on the VM to terminal in and monitor boot progress?

  8. 1 hour ago, pocopico said:


    you need to edit manually redpill-load/include/runtime.sh 

     

    And comment the line by adding a # in front of the line.

     

    #[dpkg]="dpkg --version" # extract flashupdate

     

    That did it!  Thanks pocopico.


    image.thumb.png.acf89e53f67e64d7b06b6d019ffa5fe8.png
     

  9. 12 hours ago, haydibe said:

    bromolow-7.0.1-42218 = DS3615xs

    broadwell-7.0.1-42218 = DS3617xs

     

    Yep, i'm an idiot.  Thanks haydibe!

     

     

    Now building with broadwell, I'm missing tools.  I'v confirmed the toolkit URL is correct and I see an outgoing attempt to get there via firewall.
     

    tc@box:~$ sudo ./rploader.sh build broadwell-7.0.1-42218
    jq: error (at <stdin>:1): Cannot iterate over null (null)
    jq: error (at <stdin>:1): Cannot iterate over null (null)
    Loader source : https://github.com/jimmyGALLAND/redpill-load.git Loader Branch : develop
    Redpill module source : https://github.com/jimmyGALLAND/redpill-lkm.git : Redpill module branch : develop
    Extensions :
    Extensions URL :
    TOOLKIT_URL : https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.broadwell-7.0.dev.txz/download
    TOOLKIT_SHA : e050987fbbab0c246aff2af935b1d8a4140ce490915aa4c92f3c8d163eea970c
    SYNOKERNEL_URL : https://sourceforge.net/projects/dsgpl/files/Synology%20NAS%20GPL%20Source/25426branch/broadwell-source/linux-3.10.x.txz/download
    SYNOKERNEL_SHA : d3e85eb80f16a83244fcae6016ab6783cd8ac55e3af2b4240455261396e1e1be
    COMPILE_METHOD : toolkit_dev
    TARGET_PLATFORM       : broadwell
    TARGET_VERSION    : 7.0.1
    TARGET_REVISION : 42218
    REDPILL_LKM_MAKE_TARGET : dev-v7
    Checking Internet Access -> OK
    Checking if a newer version exists on the repo -> Version is current
    Cloning into 'redpill-lkm'...
    remote: Enumerating objects: 1055, done.
    remote: Counting objects: 100% (1055/1055), done.
    remote: Compressing objects: 100% (502/502), done.
    remote: Total 1055 (delta 727), reused 874 (delta 546), pack-reused 0
    Receiving objects: 100% (1055/1055), 449.38 KiB | 4.36 MiB/s, done.
    Resolving deltas: 100% (727/727), done.
    Cloning into 'redpill-load'...
    remote: Enumerating objects: 463, done.
    remote: Counting objects: 100% (52/52), done.
    remote: Compressing objects: 100% (47/47), done.
    remote: Total 463 (delta 19), reused 27 (delta 3), pack-reused 411
    Receiving objects: 100% (463/463), 6.19 MiB | 6.17 MiB/s, done.
    Resolving deltas: 100% (175/175), done.
    Using static compiled redpill extension
    Looking for redpill for : ds3617xs_42218
    Getting file https://raw.githubusercontent.com/pocopico/rp-ext/master/redpill/releases/redpill-4.4.180plus-broadwell.tgz
    Extracting module
    Got redpill-linux-v4.4.180+.ko
    Testing modules.alias.json -> File OK
    ------------------------------------------------------------------------------------------------
    It looks that you will need the following modules :
    
    
    Found VGA Controller : pciid 1234d00001111  Required Extension : bochs_drm
    bochs_drm
    Searching for matching extension for bochs_drm
    Found SATA Controller : pciid 8086d00002922  Required Extension : ahci
    Searching for matching extension for ahci
    Found SATA Controller : pciid 8086d00002922  Required Extension : ahci
    Searching for matching extension for ahci
    Found Ethernet Interface : pciid 1af4d00001000 Required Extension :
    No matching extension
    ------------------------------------------------------------------------------------------------
    Starting loader creation
    Checking user_config.json : Done
    Cache directory OK
    [#] Checking runtime for required tools...
    [-] Couldn't find dpkg in your $PATH
    [#] Checking runtime for required tools... [ERR]
    [!] Some tools weren't available - install them first
    
    *** Process will exit ***
    FAILED : Loader creation failed check the output for any errors

     

  10. pocopico this is fantastic work!

    So I'm trying to throw 4 cores at this in proxmox.  I've generated a DS3617xs serial using serialgen.
    I'm running the build using the bromolow-7.0.1-42218.  Upon boot she thinks she is a DS3615xs with 2 cores.
    What am I missing to boot as a 3617?

×
×
  • Create New...