
fafner
Members-
Content Count
25 -
Joined
-
Last visited
Community Reputation
0 NeutralAbout fafner
-
Rank
Junior Member
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
RedPill - the new loader for 6.2.4 - Discussion
fafner replied to ThorGroup's topic in Developer Discussion Room
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 -
RedPill - the new loader for 6.2.4 - Discussion
fafner replied to ThorGroup's topic in Developer Discussion Room
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.
-
I have passed through the LSI-Adapter to the XPEnology VM so it has direct access to the HDs. Great performance.
-
Great, guys. Thanks for the work. It's back again! At first my WS2K12R2 didn't see the drive although it was connected and everything looked fine. I then deletet and recreated the iSCSI-target (not the LUN of course) and then it was like before.
-
Yes. Damn. Didn't see this thread before upgrading and now I'm stuck. iSCSI Targets are offline and can't connect to the LUNs. Does one know if it worked with 5.2-5565.1 without Update-1 and if one can downgrade to that?