wimsan

Hi all, I successfully installed a DS1621+ in Proxmox. This is with a e1000 network interface. With the e1000 interface I get a network status (1 Gbps full Duplex) If I change the network interface to virtio I do not get a network status in DSM. I would like to go to virtio because it is faster than e1000 but I do need a network status to be able to build a High Availablity pair. I built the 1621 using myv.sh and added several network drivers like e1000, rtl8169 (because my mobo has a realtek LAN interface),v9fs. Is there another virtio driver available for DS1621+ that does give a network status in Proxmox? If so where can I find it?

yes but can that be done with all the "old" settings and extensions?

How would I go about adding a driver to an existing TCRP VM? In particular how to add the e1000 driver?

@john_matrix I now have exactly the same error as you have Protocol spec without prior Class and Subclass spec at line 23281 Downloading dtc binary ########################################################################################################################################### 100.0% No cached dtb file found in /home/tc/custom-module/ds1621p.dtb Found 2 disks and 0 nvme Collecting disk paths Found local disk sda with path 00:1e.0,01.0, adding into internal_slot 1 with portnumber 6 Found local disk sdb with path 00:1e.0,01.0, adding into internal_slot 2 with portnumber 7 NO NVME disks found, returning Patching USB to include your loader. Loader found in 010-2 port Converting dts file : ds1621p.dts to dtb file : >ds1621p.dtb dtb extension is not loaded and its required for DSM to find disks on ds1621p_42661 Copy of the DTB file ds1621p.dtb to was not succesfull. Please remember to replace the dtb extension model file ... execute manually : cp ds1621p.dtb and re-run seems to be something in the new version of the loader

Hi, I have a TCRP DS1621+ running in Proxmox. If I select VirtIO for the network interface it works but Synology cannot/does not get a status from the interface. If I select RTL8139 it gets a status of 100 Mbps Full Duplex even though it runs on 1 Gbps. I built the bootloader as follows: ./rploader.sh update now ./rploader.sh fullupgrade now ./rploader.sh ext v1000-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/v9fs/rpext-index.json ./rploader.sh ext v1000-7.1.0-42661 add https://raw.githubusercontent.com/pocopico/rp-ext/master/r8101/rpext-index.json ./rploader.sh serialgen DS1621+ ./rploader.sh identifyusb now ./rploader.sh satamap now answer: 6 disks controller 1 answer: 6 disks controller 2 SataPortMap=66 DiskIdxMap=0006 ./rploader.sh build v1000-7.1.0-42661 Any ideas on how to get an interface status when using VirtIO?

I have created two identical DS1621+ in Proxmox to "play" with Synology HA. I have tried several ways to build the HA pair but it always ends up with "volume1 on passive server crashed" i.e. not created. Building a pool/volume works fine standalone. Is there a way to build the HA pair from command line so that maybe I get more insight as to what is going wrong. Or does anyone have any other ideas to make this work?

During boot of a DS1621+ bootloader in Proxmox I see the following error: Still waiting for boot device (waited 1 of 30 seconds) [ 5.100543] scsi 12:0:0:0: Direct-Access QEMU QEMU HARDDISK 2.5+ PQ: 0 ANSI: 5 [ 5.101762] <redpill/scsi_notifier.c:65> Probing SCSI device using sd_probe_shim [ 5.102728] <redpill/scsi_notifier.c:77> Triggering SCSI_EVT_DEV_PROBING notifications [ 5.103722] <redpill/boot_shim_base.c:29> scsi_is_boot_dev_target: it's not a SATA disk, ignoring [ 5.104697] <redpill/scsi_notifier.c:87> Calling original sd_probe() [ 5.105691] <redpill/scsi_notifier.c:91> Triggering SCSI_EVT_DEV_PROBED notifications - sd_probe() exit=0 [ 5.107576] sd 12:0:0:0: [usb1] 2097152 512-byte logical blocks: (1.07 GB/1.00 GiB) [ 5.108808] sd 12:0:0:0: [usb1] Write Protect is off [ 5.109522] sd 12:0:0:0: [usb1] Mode Sense: 63 00 00 08 [ 5.110491] sd 12:0:0:0: [usb1] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 5.112845] usb1: p1 p2 p3 [ 5.114160] sd 12:0:0:0: [usb1] Attached SCSI disk Still waiting for boot device (waited 2 of 30 seconds) etc. etc. until boot_wait is timed out and no boot device is found? When I see this behaviour installation of teh PAT file always fails at 55% the proxmox VM is created like this: # set vm id id=xxx # create image directory, download and uncomporess mkdir -p /var/lib/vz/images/${id} curl --location https://github.com/pocopico/tinycore-redpill/raw/main/tinycore-redpill.v0.4.6.img.gz --output /var/lib/vz/images/${id}/tinycore-redpill.img.gz gzip --decompress /var/lib/vz/images/${id}/tinycore-redpill.img.gz --keep # create vm qm create ${id} \ --args "-drive 'if=none,id=synoboot,format=raw,file=/var/lib/vz/images/${id}/tinycore-redpill.img' -device 'qemu-xhci,addr=0x18' -device 'usb-storage,drive=synoboot,bootindex=5'" \ --cores 2 \ --cpu host \ --machine q35 \ --memory 2048 \ --name DSM710 \ --net0 virtio,bridge=vmbr0 \ --numa 0 \ --onboot 0 \ --ostype l26 \ --scsihw virtio-scsi-pci \ --sata0 local-lvm:vm-${id}-disk-0,discard=on,size=10G,ssd=1 \ --sockets 1 \ --serial0 socket \ --tablet 1 # create disk for sata0 pvesm alloc local-lvm ${id} vm-${id}-disk-0 10G Is there anything that I'm missing causing the TC image attached as sata0 is not recognized?

Hi all, I have some questions about building the bootloader for DS1621+ on Proxmox. So booting from sata0. do you build the bootloader with HD or HD's attached to TC? In TC virtio drivers are used but they are not added to the bootloader image so that after starting the VM as DS1621+ there is no network interface. I thought this was supposed to go automatically If I solve the virtio driver problem I still cannot install the pat file (error @ 56% file invalid or corrupt) what can be the problem ?

By mistake I deleted the *.img file that I created for a DS1621+ in Proxmox and now the VM doesn't start anymore. The DS1621+ was running 7.0.1-42218-U3. I have tried several times to rebuild the loader. Last time I did: ./rploader.sh update now ./rploader fullupgrade now ./rploader serialgen DS1621+ (write user_config.json) ./rploader identifusb now (write user_config.json) ./rploader satamap now (write user_config.json) ./rploader build v1000-7.0.1-42218 VM starts, gets an IP address, can be connected to but no disks detected. please advise how to (re)build a DS1621+ in Proxmox? By the way using redpill TC v0.4.6

does anyone have a DS1621+ working with 7.1?

Thanks. so far that worked out. Just doesn't see any disks yet

I performed the update but still same result

Trying to create the bootloader for ds1621p I get this: ************************************************** ./rploader.sh build ds1621p-7.0.1-42218 Loader source : https://github.com/jumkey/redpill-load.git Loader Branch : develop Redpill module source : https://github.com/jumkey/redpill-lkm.git : Redpill module branch : develop Extensions : Extensions URL : TOOLKIT_URL : https://sourceforge.net/projects/dsgpl/files/toolkit/DSM7.0/ds.v1000-7.0.dev.txz/download TOOLKIT_SHA : 6108f9f7b7f0a13ee985314aef9419303375ab7ded4112be991590339b66ecd1 SYNOKERNEL_URL : https://sourceforge.net/projects/dsgpl/files/Synology NAS GPL Source/25426branch/v1000-source/linux-4.4.x.txz/download SYNOKERNEL_SHA : d3e85eb80f16a83244fcae6016ab6783cd8ac55e3af2b4240455261396e1e1be COMPILE_METHOD : toolkit_dev TARGET_PLATFORM : ds1621p TARGET_VERSION : 7.0.1 TARGET_REVISION : 42218 REDPILL_LKM_MAKE_TARGET : dev-v7 KERNEL_MAJOR : MODULE_ALIAS_FILE= Checking Internet Access -> OK Checking if a newer version exists on the repo -> Version is current Redpill sources already downloaded, pulling latest Already up to date. Loader sources already downloaded, pulling latest Already up to date. Using static compiled redpill extension Looking for redpill for : jq - commandline JSON processor [version 1.5-1-g940132e-dirty] Usage: jq [options] <jq filter> [file...] jq is a tool for processing JSON inputs, applying the given filter to its JSON text inputs and producing the filter's results as JSON on standard output. The simplest filter is ., which is the identity filter, copying jq's input to its output unmodified (except for formatting). For more advanced filters see the jq(1) manpage ("man jq") and/or https://stedolan.github.io/jq Some of the options include: -c compact instead of pretty-printed output; -n use `null` as the single input value; -e set the exit status code based on the output; -s read (slurp) all inputs into an array; apply filter to it; -r output raw strings, not JSON texts; -R read raw strings, not JSON texts; -C colorize JSON; -M monochrome (don't colorize JSON); -S sort keys of objects on output; --tab use tabs for indentation; --arg a v set variable $a to value <v>; --argjson a v set variable $a to JSON value <v>; --slurpfile a f set variable $a to an array of JSON texts read from <f>; See the manpage for more options. cp: cannot create regular file '/home/tc/redpill-load/ext/rp-lkm/redpill-linux-v4.4.180+.ko': Permission denied Got redpill-linux-v4.4.180+.ko Testing -> ^C ************************* Any ideas?

hi all, I am successfully running a ds3617xs in proxmox using redpill-tinycore. I am also running a ds3615xs in proxmox. the ds3615 has been upgraded to 7.0.1-42218 update 3 but when I try to update the ds3617 as well it gets stuck in a install loop after the upgrade. Does someone already have a redpill-tinycore ds3617 running update 3 ? If so how have you managed to do the upgrade?

synafoto.log says: 021-11-10T16:04:50+01:00 DSM7 synofoto-task-center[18755]: /source/synofoto/src/lib/io/channel.cpp:107 channel[] failed to send: write: Broken pipe 2021-11-10T16:04:50+01:00 DSM7 synofoto-task-center[18755]: /source/synofoto/src/lib/io/channel.cpp:79 channel[/run/synofoto/face-extraction.socket] construct failed: connect: Connection refused plaese advise

In DSM7.0.1-42218 I see this strange behaviour: sudo ./patch.sh -p Detected DSM version: 7.0.1 42218-0 Patch for DSM Version (7.0.1 42218-0) AVAILABLE! Available binaries to patch/restore: 1) /usr/syno/bin/synocodectool 2) /volume1/@appstore/MediaServer/bin//synocodectool 3) Quit Please choose which binary you want to patch/restore:1 Restored synocodectool and valid backup detected (DSM 7.0.1-42216-0_7.0.1-42218-0) . Patching... Patched successfully Creating spoofed activation.conf.. Spoofed activation.conf created successfully ~/synocodectool-patch-master$ sudo ./patch.sh -r Detected DSM version: 7.0.1 42218-0 Patch for DSM Version (7.0.1 42218-0) AVAILABLE! Available binaries to patch/restore: 1) /usr/syno/bin/synocodectool 2) /volume1/@appstore/MediaServer/bin//synocodectool 3) Quit Please choose which binary you want to patch/restore:1 Detected unpatched original synocodectool. Restoring not neccessary! activation.conf looks like this; sudo cat /usr/syno/etc/codec/activation.conf {"success":true,"activated_codec":["hevc_dec","ac3_dec","h264_dec","h264_enc","aac_dec","aac_enc","mpeg4part2_dec","vc1_dec","vc1_enc"],"token":"123456789987654abc"} in Photos the number of photos to be discovered counts down but in the end there's nothing in the people album

The 'old' disks are created with scsi paravirtual driver. Doesn't the 4.3 VM support scsi paravirtual? If so will it work with LSA Logic as driver?

I am currently running DSM 4.2-3202 with 3 disks (full disk VMDK) in ESXi 5.1. How would I go about upgrading to the 4.3 version in this link viewtopic.php?f=13&t=1737?

the question is not a matter what is moer light or not because system resources are not an issue. I was just wondering if someone knows whether xpenolgy DSM works better with VirtualBox or with ESXi? Also support for more drivers etc. is interesting to know. Ultimately the new system will have to run on a Asrock B75-Pro3-M with Core i5 3470T and 8 GB of RAM.

Hello, I'm in the proces of setting up XPEnology as a virtual machine. What free virtualisation works best with XPEnology builds? and what are the pros and cons?

Does anyone know what MAC address to use for installation in a Proxmox VM? I managed to install 3612XS DSM 4.1 build 2668++ using the information in this link viewtopic.php?f=2&t=733&p=3859&hilit=proxmox#p3859