Disable/Hide 50MB VMware Virtual Disk?

[tret]

Hi folks,

 

Here are my build (VM) details

----------------------------------------

Loader: Jun's Loader 1.02b

Model: DS3615xs

Type: VM (ESXi v6.5)

DSM: DSM 6.1.2-15132 Update 1

 

 

Issue: The loader is showing up in slot/disk 1 as a VMware Virtual Disk 50MB SSD. this effectively uses up one of the 12 disk slots. Previously, with Jun's Loader v1.01 and DSM 6.0.2 I was able to avoid this by making the vDisk Independed - Persistent and using the LSI Logic Parallel controller. This doesn't seem to work this time around. Any tips?

 

Thanks,

Rob

[tret]

Solved. 50MB VMware Virtual Disk is no longer showing in the list of available disks in DSM after making the following changes.

 

- Added SATA Controller

- Removed SCSI LSI Logic Parallel Controller

- Changed vDisk to Independent Non-Persistent

[kim82]

On 2017-07-12 at 1:00 AM, tret said:

Solved. 50MB VMware Virtual Disk is no longer showing in the list of available disks in DSM after making the following changes.

 

- Added SATA Controller

- Removed SCSI LSI Logic Parallel Controller

- Changed vDisk to Independent Non-Persistent

Hello!

 

how do I add sata controller in esxi? I dont have that option, when im adding hardware...

[NoFate]

same here , did you ever resolve  , i cant add sata controller either in esxi 6.5

[nero]

Hi , I'm also solving same problem moving boot disk to sata.

I add sata controller simply by editing vm , then I remove disk , convert to sata ( from cli using vmkfstools ) then added back to vm as first and only sata disk.

 

[luchuma]

to enable sata controler change vm machine type for example ubuntu x64

then add sata controller

set synoboot vmdk as sata 0:0

 

machine type maybe diffrent on esxi 6.5 and 6.7

Edited September 9, 2018 by luchuma

[Kanedo]

The proper way to move synoboot to a much higher enumeration is to change DiskIdxMap in grub.cfg

 

On jun's 1.03b, the default is DiskIdxMap=0C

0C = Disk 13

 

Change it to something much higher

DiskIdxMap=1F

1F = Disk 32

 

For more info: https://github.com/evolver56k/xpenology/blob/master/synoconfigs/Kconfig.devices#L245

Edited September 27, 2018 by Kanedo

[aniel]

On 9/27/2018 at 2:55 PM, Kanedo said:

The proper way to move synoboot to a much higher enumeration is to change DiskIdxMap in grub.cfg

 

On jun's 1.03b, the default is DiskIdxMap=0C

0C = Disk 13

 

Change it to something much higher

DiskIdxMap=1F

1F = Disk 32

 

For more info: https://github.com/evolver56k/xpenology/blob/master/synoconfigs/Kconfig.devices#L245

is i use this method then i can not update the system

[yonn]

On 7/12/2017 at 1:00 AM, tret said:

Solved. 50MB VMware Virtual Disk is no longer showing in the list of available disks in DSM after making the following changes.

 

- Added SATA Controller

- Removed SCSI LSI Logic Parallel Controller

- Changed vDisk to Independent Non-Persistent

 

 

Same problem. But if I change synoboot.vmdk to "Independent Non Persistent" Xpenology refuses to boot.

 

synoboot.vmdk on Sata:0:0 xpenology.vmdk on Sata:0:1. vm Esxi 6.7

 

Another solution?

 

Thanks in advance

[flyride]

Your virtual disk (xpenology.vmdk) should be on a second SATA controller SATA 1:0

 

If you are using DS3615xs/3617xs, DiskIdxMap=0C00

If you are using DS918, DiskIdxMap=1000

 

Depending on your version you may need to add FixSynoboot script for updates to work, but the above will hide the boot device.