Jump to content
XPEnology Community

Disable/Hide 50MB VMware Virtual Disk?


tret

Recommended Posts

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

Link to comment
Share on other sites

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

Link to comment
Share on other sites

  • 2 months later...
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...

Link to comment
Share on other sites

  • 9 months later...
  • 2 weeks later...

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.

 

Link to comment
Share on other sites

  • 2 months later...
  • 3 weeks later...

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 by Kanedo
Link to comment
Share on other sites

  • 2 years later...
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

Link to comment
Share on other sites

  • 1 month later...
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

Link to comment
Share on other sites

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.

  • Like 1
Link to comment
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.

×
×
  • Create New...