XPEnology DS3612xs DSM 4.3 build 3827 (ESXi v1.2)


Recommended Posts

Yes I'm aware of this two issues (cifs and iscsi) in both standard and esxi build.

I spent last few days fixing issues with SCSI/SAS controllers, this is the next step :wink:

 

 

thank you very much for the effort, happy new year! :grin:

Link to post
Share on other sites

I downloaded the VMDF file from ESXi datastore onto PC, then I use a hex editor to change the MAC address and serial number in the vmdk.

then I uploaded back to the datastore, and I bootup the VM.

 

I can see from the Synology assistant that my VM has the modified serial number and MAC address modified.

 

but when I check inside the VM by bring out the system info, I have a blank serial number, do I need any more edit ?

Edited by Guest
Link to post
Share on other sites

If you have access to a linux machine you can mount the .vmdk an pull the vender file and edited using the vender patcher tool, unmount the .vmdk and all is good

 

that's how i did it and it worked ok.

 

i do have 4 internal nics and i'm passing thru one to the xpenology machine

Link to post
Share on other sites
If you have access to a linux machine you can mount the .vmdk an pull the vender file and edited using the vender patcher tool, unmount the .vmdk and all is good

 

that's how i did it and it worked ok.

 

i do have 4 internal nics and i'm passing thru one to the xpenology machine

 

I did the same today, it is working fine with my 2 N54L machines with ESXi, but I still cannot get HA working.

 

I am suspecting the problem comes from the NIC MAC, it might need to be the real NIC MAC.

but N54L might not be able to pass thru the real NIC MAC all the way to the VM.

 

I don't know how to do that. ....... :cry:

Edited by Guest
Link to post
Share on other sites

Adding existing VMDKs to a new, working, VM does not erase data on those disks.

 

If all VMDKs are in 4.2 VM directory, you should at least move them to new 4.3 VM location to keep things logical.

Also, depending on their size VS your storage pool, you may consider copying those VMDK files in same folder as 4.3 VM, before attaching them.

Link to post
Share on other sites

Bootstrap is not included in this version?

 

Like in DSM 4.2 build 3211++ (repack v1.2):

"- Include bootstrap ipkg setup script (/root.profile is already modified) : after setup just log to ssh and type :

sh syno-i686-bootstrap_1.2-7_i686.xsh

reboot, log again to ssh and type

ipkg update

ipkg upgrade"

 

 

Edit: No, it's not included, I've applied Tuatara's info from here: viewtopic.php?f=2&t=558&start=280#p9968 :ugeek:

Edited by Guest
Link to post
Share on other sites

I successfuly install v1.1 on my ESXi 5.5 box.

 

How can I update to 3810 update 4?

It's available for download, downloading the update is no problem but when installing I get the following error screen.

(see screenshot)

 

j2yj.png

 

Does anyone know what I'm doing wrong?

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.