fafner

Totally. This is phantastic. Thx a lot. Runs under ESXi 8 like a charm. Upgraded my previous red pill by installing / configuring arpl and then just mounting the disks into new VM. DSM recognized the transfer and allowed "keep settings". Bingo.

This works for Active Backup for Business. But does one know the URL for Active Backup for Google Workspace...? 🤔

I created a docker container from https://registry.hub.docker.com/r/linuxkit/open-vm-tools/ Runs like I've never seen before. Ok, didn't test shut down / restart so far because I always use the Syno web interface for that. But snapshot w/quiescence works soo nice.

Qiescence (Snapshot) does not work. 2022-01-27T12:20:44.657Z In(05) vcpu-2 - [msg.snapshot.quiesce.vmerr] The guest OS has reported an error during quiescing. 2022-01-27T12:20:44.657Z In(05)+ vcpu-2 - The error code was: 3 2022-01-27T12:20:44.657Z In(05)+ vcpu-2 - The error message was: Error when enabling the sync provider. 2022-01-27T12:20:44.657Z In(05) vcpu-2 - ---------------------------------------- 2022-01-27T12:20:44.659Z In(05) vcpu-2 - VigorTransportProcessClientPayload: opID=4501266d-01-32-28e5 seq=8814: Receiving Bootstrap.MessageReply request. 2022-01-27T12:20:44.659Z In(05) vcpu-2 4501266d-01-32-28e5 VigorTransport_ServerSendResponse opID=4501266d-01-32-28e5 seq=8814: Completed Bootstrap request. 2022-01-27T12:20:44.659Z In(05) vcpu-2 - ToolsBackup: changing quiesce state: STARTED -> ERROR_WAIT 2022-01-27T12:20:46.661Z In(05) vcpu-2 - ToolsBackup: changing quiesce state: ERROR_WAIT -> IDLE 2022-01-27T12:20:46.661Z In(05) vcpu-2 - ToolsBackup: changing quiesce state: IDLE -> DONE 2022-01-27T12:20:46.661Z In(05) vcpu-2 - SnapshotVMXTakeSnapshotComplete: Done with snapshot 'VM Snapshot 27.1.2022, 13:20:36': 0 2022-01-27T12:20:46.662Z In(05) vcpu-2 - DISKLIB-CBT :ChangeTrackerESX_DestroyMirror: Destroyed mirror node 126d1cea-4dd2938-cbtmirror. 2022-01-27T12:20:46.727Z In(05) vcpu-2 - DISKLIB-CBT :ChangeTrackerESX_DestroyMirror: Destroyed mirror node 13a31cde-50c2934-cbtmirror. 2022-01-27T12:20:46.729Z In(05) vcpu-2 - SnapshotVMXTakeSnapshotComplete: Snapshot 0 failed: Failed to quiesce the virtual machine (29). 2022-01-27T12:20:46.729Z In(05) vcpu-2 - VVolObjNotifySnapshotDone: isEnabled: 1

Same here. Used to have four real SATA-Disks as RDM via the PVSCSI controller... And thought I have to do so with tinycore-redpill DSM 7. 🤔 Didn't get it done here either. 🙄 BUT... obviously I can use my SATA RDM with vSATA AHCI. Works great so far. 🥳

I get "Invalid file format. Contact developer." 😕 tinycore-redpill ds918p DSM 7.0.1-42218 Update 2 on ESXi 7 Edit: I guess I have to build it myself first... 🙈

- Outcome of the update: SUCCESSFUL - DSM version prior to update: DSM 6.2.1-23824U6 - Loader version and model: Jun v1.04b - DS918+ - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.7u2 on Supermicro X11SPM - Additional comments: Manual update, reboot. Disk as VMDK on VMware Paravirtual SCSI controller.

- Outcome of the update: SUCCESSFUL - DSM version prior to update: DSM 6.2.1-23824U6 - Loader version and model: Jun v1.03b - DS3617xs - Using custom extra.lzma: NO - Installation type: VM - ESXi 6.7u2 on Supermicro X9SRH - Additional comments: Reboot required, all disks as RDM on 2nd SATA controller.

Did anyone get any SCSI Controller to work? I would like to use RDMs. Edit: Forget it. Just noticed that I can attach RDM to SATA controller. Great, really. 👍

Not surprised. Probably no one is working on this. Sticking with iSCSI so far.

iSCSI seems to work here so far...

I've been running the DS412+ for month with NFS-VAAI including 5562U2 before 5592 and it was working all the time. So I am sure XPEnology is broken here.

You think DSM 5.2-5565 has problem, but 5592 doesn't, right ? No. XPEnology is broken. It's not a matter of DSM. I have 5592 on a DS412+ and there it's working.

I can confirm it's broken in XPEnoboot 5.2-5565.2 with vSphere 5.5.

I did and I used it and it said "online" or "ready" or whatever it says when it's working. Also the Server was connected, iSCSI-Initiator in WS said "connected" / "ok" and DSM too. But alas, no drive was showing up. After recreating the target in DSM it looked exactly the same but now the drive was accessible.