Transition Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About wimsan

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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?
  2. 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> Calli
  3. 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 ?
  4. 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
  5. does anyone have a DS1621+ working with 7.1?
  6. Thanks. so far that worked out. Just doesn't see any disks yet
  7. I performed the update but still same result
  8. 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://sourcefo
  9. 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?
  10. 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
  11. 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-mast
  12. 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?
  13. 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?
  14. 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.
  15. 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?