koroziv

Here is what I used on esxi 6.5, on a hp gen8 microserver : https://mega.nz/#!Vk40FCDT!r2ertz7Eyoeh ... W2p1GLgzfs It's jun's loader 1.01. Add drive and install. If you want to modify the grub cfg you need to set the boot drive as dependent or persistent before edit. But I see no need for abusing synology services, a free dns is all you need. The vm comes with 2x2 cpu and 4 GB ram, change it to your needs. edit: here is how you can edit grub after dsm6 install (make sure the boot drive is NOT non-persistent for this to work): SSH into dsm and type echo 1 > /proc/sys/kernel/syno_install_flag mount /dev/synoboot1 /mnt /mnt/grub/grub.cfg umount /mnt or for using winscp to edit the file with notepad++ (vi editor is not that hard, but...): 1. Login using putty or any other ssh client with administrator account (usually "admin") 2. You will be asked for a password. Enter the one for the administrator account 3. You will get a command prompt 4. Enter: sudo su - 5. You will be asked for a password. Enter again the one for the administrator account 6. You will get a command prompt root@... 7. Enter command: synouser --setpw root your_new_root_password For "your_new_root_password" please use the desired password for root account. Nou you can do SSH into dsm and type echo 1 > /proc/sys/kernel/syno_install_flag mount /dev/synoboot1 /mnt login using winscp (user root and the password you set before) an go to /mnt/grub/ and edit grub.cfg Save and close editor when finished. Get back to the ssh sesion and do umount /mnt Shut down dsm normally (not from esxi cli or webui) and edit the vm setting - change the boot drive back to non-persistent.

Don't set as boot as non-persistant. This is very important. Sent from my SM-N920T using Tapatalk I installed about 7 times with the non-peristent option on esxi. Zero problems. Now I'm on baremetal setup but I tested again on VMware workstation and it's working just fine. Edit: the only thing is that if you want to use the tool to edit settings (mac, sn, etc) you will not have acces to save the changes. So just finish the setup using the tool, install dsm, and only when finished go to vm settings and set the boot drive to non-persistent.

Stop your vm and edit the settings for it; change the boot drive to non-persistent, nothing else. This will hide the boot drive on xpeno.

For esxi users : here you have an ovf vm export that will make the install easier: https://mega.nz/#!Vk40FCDT!r2ertz7Eyoeh ... W2p1GLgzfs All you need to do after import is to add your drives and edit ram/cpu to your needs (comes with 2x2cpu and 4 Gb ram), then start the vm and continue with the install process. It will start with the vmware boot option automatically, and after the install you will not see the 50mb boot drive. I didn't edit a thing in the cfg (vid or pid) This is the loader on the first page of this topic, latest version, I just made it more easy to use it for esxi users. Here is the process: I had to import the original vm in VMware Workstation Pro (I had errors at import in esxi 6.5), and chage to hw version 10, export to new ovf; imported the new ovf in esxi, edited a few things, start once to retain the vmware boot option, changed the boot drive to non-persistent (it's hidden in xpeno now) and exported again to the ovf in the link for easy future use. I hope it will be useful to others to; if I messed up something let me know, for me and a few others this worked nice. Edit: On my gen8 microserver I don't have and can't add an usb3 controller; this could be a poor choice at vm guest os version, I put "other 3.x or later linux x64", did not tried any other way yet. Edit 2: The usb3 issue is not present on the atached hw 10 ovf(the one in the link), you can add usb3 controller in it; my xpeno install is on a vm with hw 13 and that is why I can't add an usb3 controller.

The problem was with the drive, I changed it to persistent and now the changes remain after boot; I also fixed the root issue as suggested, and I can use winscp with root now. using VI editor it's not that hard, but for noobs like me notepad it's more easy. The vmdk unmount issue (pc restart) it's still present with the persistent drive; I changed back to non-persistent for future use of the vm, I think that's how it is suposed to be used. Thank you all for your help with such minor and elementary linux stuff

winscp is fine, but it maybe not easily be connected as root user. so you need change the above mount line as something like this, to give non-root use full access to the boot partition. mount -o umask=0 /dev/synoboot1 /mnt there are a few possible reasons cause it not got saved: 1. your boot disk is set to non-persistence 2. you did not properly umount the disk after editing. 3. vi is not really beginner friendly. Yes the boot drive is non persistent, I'll change that and try again. I can't get root in winscp, incorect password, just with the admin user I have access but read only. With workstation the pc restarts on disconnect from the program, same as from Explorer. Quickconnect is not important to me, I manage just fine using a free dns, but I wanted to make it work just to pass some time Sent from my SM-G930F using Tapatalk

I tried I'm not familiar with linux but willing to try; I was thinking that I could mount the image and then edit the file from winscp, but can't. I'll look for another editor edit: edited and saved with vi editor, still has the old sn after restarting the vm.

Ummm. Yeah I do.. Unless I'm misinterpreting what you're trying to do! Always a chance! I thought I'd suggested a method (maybe I dreamed it?). ESXi.. You set up your VM in ESXi as you like it.. Shut it down. Go to the datastore on the host. Download the Boot drive VMDK of your VM to a new EMPTY folder on your PC.. You will note that there is more than one file when you download it (this is normal).. Your PC.. You should have Vmware workstation on your machine - this will allow you to Mount VMDK files as drive letters. Map the first VMDK file you downloaded to a Drive letter (NOT the vmdk file that has 'flat' or something in the file name), be sure to untick the 'read only' check box when mapping.. Go to the drive you mapped and edit the grub.cfg file. Save the file. Disconnect the mapped drive (right click on the VMDK file again) on your PC. ESXi again.. Next, go back to your datastore and upload BOTH vmdk files to the same location, one at a time. Close the datastore folder and power on your VM again. Watch how your SN and MAC addresses have changed.. Have a beer.. Yes, I've tested it and it works.. #H My pc restarts (win10) when I try to disconnect the vmdk, nothing saved; VMware® Workstation 12 Pro (12.5.0 build-4352439)

Tried that, can't add rdm to it; this is the error message : "Failed to reconfigure virtual machine DSM-6. Incompatible device backing specified for device '3' Update: my bad, I forgot that the drive I was trying to use for RDM was an old unused datastore; removed the datastore and now I'm able to add it. Also I can use the rdm's that I used on dsm5, but they are ext4 I have no space to backup all the data to migrate to btrfs so I gues I'll use the ext4 for now.

Tried that, can't add rdm to it; this is the error message : "Failed to reconfigure virtual machine DSM-6. Incompatible device backing specified for device '3'

How did you managed to add rdm to the dsm6 vm ? I get errors every single time; can you export and upload an ovf please ? How are you adding them rdm? Assuming that the error is related with space.... If you are doing it via web ui and the rdm disk is bigger than your datastore i can't do it because a bug, you have two options: - use the windows vsphere client - Update the web host client (https://labs.vmware.com/flings/esxi-emb ... ost-client) I use the second method because if you use the first, then i can't edit again the vm using the web ui. Notice however that the updateve version is a from labs... so not so stable like the one from esxi 6u2 I tried both methods, using the latest webui and the windows vsphere. Dsm 6 is installed and working, just can't add my rdm's. Maybe I did a mistake when I created the vm, that's why I ask for an ovf upload if possible. Sent from my SM-G930F using Tapatalk

How did you managed to add rdm to the dsm6 vm ? I get errors every single time; can you export and upload an ovf please ? How are you adding them rdm? Assuming that the error is related with space.... If you are doing it via web ui and the rdm disk is bigger than your datastore i can't do it because a bug, you have two options: - use the windows vsphere client - Update the web host client (https://labs.vmware.com/flings/esxi-emb ... ost-client) I use the second method because if you use the first, then i can't edit again the vm using the web ui. Notice however that the updateve version is a from labs... so not so stable like the one from esxi 6u2 I tried both methods, using the latest webui and the windows vsphere. Dsm 6 is installed and working, just can't add my rdm's. Maybe I did a mistake when I created the vm, that's why I ask for an ovf upload if possible. Sent from my SM-G930F using Tapatalk

How did you managed to add rdm to the dsm6 vm ? I get errors every single time; can you export and upload an ovf please ?

Is anyone using esxi 6 + dsm6 + RDM diaks ? I can't add RDM disks to it; this is my ususal setup on the gen8, only 16gb drive on the datastore for the system and all the storage added via RDM. In dsm 5 works perfect but with dsm 6 I get errors when trying to add the rdm to the vm. I get the pat file from the synology site, i set it up, configure after the first boot, all ok, jus can't add RDM's

I tried the ovf (both v10 and v11) in esxi 6.0u2 on a gen8 microserver; I can install and create volumes but fail to add an existing RDM. I tried using vsphere and the embeded client, error in both. I need to use the RDM's that I have now working in dsm 5. Do I need to do something to get this working or this is it for now ?

Edit: sorry for the double post.

Great. I have no ideea how and what to edit in order to achieve that, care to share for noobs like me ? Sent from my SM-G930F using Tapatalk

You can't add drives using RDM from web ui, a bug probably (not working for dsm 5 either).

It works ok, updated from control panel.

Should work on 5.5 and later but I only tried on 6. Sent from my SM-G930F using Tapatalk

That link was to show you that it's possible to control edit setting of your vm's on esxi from vmware workstation. Don't know man either you are doing something different or your vmware workstation version is not supported. I can definitely connect to esxi and add existing RDM disks. From your workstation: File/Connect to server Fill in the esxi username password and open the settings of your VM on esxi. From there it's self explanatory to add an existing disk and select your RDM disk as SATA and start your VM. That's all, nothing more nothing less. I know how to connect and that it's possible to edit, but from my workstation v12 I can't add RDM for some reason (as seen in that picture). It is the same for dsm5 not only for dsm6. The RDM's are made in command line and added to dsm5 with vsphere; I removed one disk from dsm5 and tried to use the that rdm to dsm6, not working. Then I tried to put it back to my dsm5 vm using workstation, not possible, only with vsphere I was able to do that.

@donmimo How is that link supposed to help ? I tried, it didn't work as is visible in the picture: Please select "use a fisical disk" option. Where is that option? Can't find it. Sent from my SM-G930F using Tapatalk

Actually there is another way which you can try. Install Vmware Workstation 12 and connect to your esxi server from there, there is an option to connect. When you are connected you can edit vm's on esxi and add rdm disks. nope can't find the suggested option

I allready have the latest version, and I can edit settings just fine, only in this case I have issues with RDM. @ omega syslinux.cfg should be on the boot disk, but I can't be sure, I didn't make it; until now it was there (dsm 4-5) @ koalala Thanks for the RDM information. You are right, it doesn't work when you want to add RDM disks. But you can use vcenter to add RDM disks. If you don't have a vcenter setup you can deploy the VCSA, once you add the disks you can delete the appliance if you don't plan to use it since it's a trial version. Thanks; tried some time ago to deploy VCSA, didn't go so well for me I guess I'l wait for a proper xpeno release, but is good to know that there is a solution for RDM at this time.

I allready have the latest version, and I can edit settings just fine, only in this case I have issues with RDM. @ omega syslinux.cfg should be on the boot disk, but I can't be sure, I didn't make it; until now it was there (dsm 4-5) @ koalala Thanks for the RDM information.