Trantor

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:

Share this post


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

Share this post


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

Share this post


Link to post
Share on other sites
thanks trantor

 

The CIFS mount function of file station is not working in ESXi 5.1 with trantor's ESXi v1.1

please, support cifs mout funtion...

I'm also experiencing this.

Seemed like a glitch within the kernel.

Share this post


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

Share this post


Link to post
Share on other sites

For trying out HA ......

 

I tried on 3202, the passive DSM is giving out errors.

 

but with 3810, it seems like the active DSM cannot communicate to the passive at all .........

Share this post


Link to post
Share on other sites

My VM on ESX 5.1 gets stuck on

 

findhost uses obselete (PF_INET,SOCK_PACKET).

 

Where do i copy the files from modules folder inside the VM or on my esx host?

Share this post


Link to post
Share on other sites

I keep getting an error and its locking up the vM.

 

Can someone please send me screen shots or configuration option so i can verify i have it setup correctly.

Share this post


Link to post
Share on other sites

I have a working version for 4.3 update 3 running. How do i import my vmdk's from previous version 4.2 to 4.3? I can add disks to the 4.3 version but how do i get it to see it without FORMATTING or erasing all the data?

Share this post


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.

Share this post


Link to post
Share on other sites

I attached the VMDK's from 4.2 to 4.3 but it doesn't see them it asks me to initialize the drives meaning ERASE them. What am i doing wrong?

Share this post


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

Share this post


Link to post
Share on other sites

so... I boot off the supplied 30meg esxi .vmdk file. I come to a screen that says diskmanager login: but i am unable to enter anything. Am I missing something?

 

Hardware: Lenovo TS140 running ESXI 5.1u

Share this post


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?

Share this post


Link to post
Share on other sites

- Just add the link in first post to Tuatara's how to

 

CIFS mount : I will update modules (compiled with the "esxi" sources) to fix it

Share this post


Link to post
Share on other sites

Hi Trantor,

great to see, that you are back in this thread. A quick question:

Could you give us an idea, what the planned changes in your next version will be? (NFS, CIFS, VM-Tools, Full package,?)

 

Cheers myhtpc

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now