[SOLVED] Install on vmware ESXI


Recommended Posts

I suppose you rebooted the SYNOLOGY?

yes, i did reboot it.

Rebooting won't do it. You have to RESTART the Virtual Machine in order for it to pick up the changed settings for the RDM controller. Restarting the Synology is still going to use the same VM setup! :ugeek:

Link to post
Share on other sites

I had to wait for a few replication jobs but after restarting the VM still no SMART on my devices.

 

Can't remember what "smartctl -a /dev/sdc" says about Vendor, Product, Revision (VMware, Virtual Disk, 1.0 or something else) but it does not work.

Link to post
Share on other sites

RdmFilter.HbaIsShared setting is still there in esxi 5.5, indeed.

 

But, even after uncheking this then rebooting hypervisor, DSM is unable to gather SMART info (maybe because my RDM storage disks are detected as SSDs, oddly ??)

Link to post
Share on other sites
I had to wait for a few replication jobs but after restarting the VM still no SMART on my devices.

 

Can't remember what "smartctl -a /dev/sdc" says about Vendor, Product, Revision (VMware, Virtual Disk, 1.0 or something else) but it does not work.

 

For interest, I'll give it a go ... shut down Synology ... clear the RDMFilter flag ... restart VM ... synology running ... SSH login ... and we're ready.

 

Let's check my first RDM drive in the array ...

 

[spoiler=smartctl -a /dev/sda]mediacat> smartctl -a /dev/sda

smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.2.30] (local build)

Copyright © 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

 

=== START OF INFORMATION SECTION ===

Device Model: WDC WD20EFRX-68AX9N0

Serial Number: WD-WCC1T0773149

LU WWN Device Id: 5 0014ee 25daf1b94

Firmware Version: 80.00A80

User Capacity: 2,000,398,934,016 bytes [2.00 TB]

Sector Sizes: 512 bytes logical, 4096 bytes physical

Device is: Not in smartctl database [for details use: -P showall]

ATA Version is: 8

ATA Standard is: ACS-2 (revision not indicated)

Local Time is: Fri Jan 31 21:47:24 2014 NZDT

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

 

=== START OF READ SMART DATA SECTION ===

SMART overall-health self-assessment test result: PASSED

 

General SMART Values:

Offline data collection status: (0x00) Offline data collection activity

was never started.

Auto Offline Data Collection: Disabled.

Self-test execution status: ( 0) The previous self-test routine completed

without error or no self-test has ever

been run.

Total time to complete Offline

data collection: (27540) seconds.

Offline data collection

capabilities: (0x7b) SMART execute Offline immediate.

Auto Offline data collection on/off support.

Suspend Offline collection upon new

command.

Offline surface scan supported.

Self-test supported.

Conveyance Self-test supported.

Selective Self-test supported.

SMART capabilities: (0x0003) Saves SMART data before entering

power-saving mode.

Supports SMART auto save timer.

Error logging capability: (0x01) Error logging supported.

General Purpose Logging supported.

Short self-test routine

recommended polling time: ( 2) minutes.

Extended self-test routine

recommended polling time: ( 255) minutes.

Conveyance self-test routine

recommended polling time: ( 5) minutes.

SCT capabilities: (0x70bd) SCT Status supported.

SCT Error Recovery Control supported.

SCT Feature Control supported.

SCT Data Table supported.

 

SMART Attributes Data Structure revision number: 16

Vendor Specific SMART Attributes with Thresholds:

ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE

1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0

3 Spin_Up_Time 0x0027 180 176 021 Pre-fail Always - 5983

4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 73

5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0

7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0

9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1249

10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0

11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0

12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 73

192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 72

193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 0

194 Temperature_Celsius 0x0022 118 114 000 Old_age Always - 32

196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0

197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0

198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0

199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0

200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0

 

SMART Error Log Version: 1

No Errors Logged

 

SMART Self-test log structure revision number 1

No self-tests have been logged. [To run self-tests, use: smartctl -t]

 

 

SMART Selective self-test log data structure revision number 1

SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS

1 0 0 Not_testing

2 0 0 Not_testing

3 0 0 Not_testing

4 0 0 Not_testing

5 0 0 Not_testing

Selective self-test flags (0x0):

After scanning selected spans, do NOT read-scan remainder of disk.

If Selective self-test is pending on power-up, resume after 0 minute delay.

 

 

All good ... no problems at all on DSM 4.2, ESXi 5.1 with RDMFilter flag cleared. The SMART data is not available in the DSM interface though, so there must be something different about the method by which it gathers/collects that data. I might look into it sometime ... after I migrate to 4.3 and ESXi 5.5.

 

Check everything you've done over again (I'm not sure what could have gone wrong - ParaVirtual Controller? Can not be LSI!). It worked first time for me. Survived a reboot too.

 

Regards,

Tuatara.

Link to post
Share on other sites
@Tuatra: what controller do (did) you use to passthrough to DSM?

Paravirtual. Exactly as I'd specified in the "Idiot's Guide" (found earlier in this thread).

 

I boot off the [Datastore] Synology/esxi_synoboot_3202_v2.vmdk

- Configured as IDE (0:0) Hard Disk 1

SCSI Controller 0 - Paravirtual

- No SCSI Bus Sharing

All physical disks are RDM (Mapped Raw LUN) - Compatibility Mode (Physical)

- vmdk files are stored in the VM directory (for example: /dev/sda)

- vml.020000000050014ee25daf1b94574443205744 / [Datastore] Synology/WDC_2.0TB_1.vmdk

- Configured as SCSI (0:0) Hard Disk 2

(8 total drives RDM on a M1015, with additional 5 drives RDM off Intel Motherboard SATA - all WD Reds, and last Intel SATA is an Intel SSD as ESXi DataStore)

All memory locked - as I also use VT-d for USB and PCI-E Hauppauge Card (which I haven't set up yet).

 

Regards,

Tuatara.

Link to post
Share on other sites

8 total drives RDM on a M1015

OK, I thought you passedthrough M1015, I'm curious if this card being recognized by DSM or not.

 

I wasted two evenings trying to install SIL3112 based PCIe-to-SATA card. I either got DOA card or my only PCI slot is broken .. going to ship it back.

Link to post
Share on other sites

8 total drives RDM on a M1015

OK, I thought you passedthrough M1015, I'm curious if this card being recognized by DSM or not.

 

I wasted two evenings trying to install SIL3112 based PCIe-to-SATA card. I either got DOA card or my only PCI slot is broken .. going to ship it back.

I tried passthrough of the M1015 ages back. Right now, I can't remember if I had it working ... I think so, but I probably compiled/added the driver myself. I did put in a number of different manufacturers cards - Sil3114 for certain, and also a JMicron JMB363 - in which I compiled and added the driver to the Synology, and also into ESXi (for fun & profit). I then ran a few tests ... and decided that the performance loss of RDM (less than 1% from my informal tests) wasn't worth it. RDM works well, is very reliable, and the M1015 is supported by ESXi directly. No messing with kernel drivers in the Synology - other than adding the one Paravirtual. With that driver added, I set up all drives as RDM Paravirtual and tested only that one driver to exhaustion (since all other hardware is natively supported in ESXi and from VMWare). Rock solid. I haven't looked back. Works great.

 

Regards,

Tuatara

Link to post
Share on other sites
I had to wait for a few replication jobs but after restarting the VM still no SMART on my devices.

 

Can't remember what "smartctl -a /dev/sdc" says about Vendor, Product, Revision (VMware, Virtual Disk, 1.0 or something else) but it does not work.

 

Just thinking: I suppose that you have SMART option enabled in BIOS... :idea::?::twisted:

Link to post
Share on other sites

I wasted two evenings trying to install SIL3112 based PCIe-to-SATA card. I either got DOA card or my only PCI slot is broken .. going to ship it back.

I tried passthrough of the M1015 ages back. Right now, I can't remember if I had it working ... I think so, but I probably compiled/added the driver myself. I did put in a number of different manufacturers cards - Sil3114 for certain, and also a JMicron JMB363 - in which I compiled and added the driver to the Synology, and also into ESXi (for fun & profit). I then ran a few tests ... and decided that the performance loss of RDM (less than 1% from my informal tests) wasn't worth it. RDM works well, is very reliable, and the M1015 is supported by ESXi directly. No messing with kernel drivers in the Synology - other than adding the one Paravirtual. With that driver added, I set up all drives as RDM Paravirtual and tested only that one driver to exhaustion (since all other hardware is natively supported in ESXi and from VMWare). Rock solid. I haven't looked back. Works great.

Thanks for sharing, I think I'm going to do the same approach and rather focus testing vDSM itself, my setup is even smaller than yours - not more than 5 disks.

 

I want to deploy a build environment to be able to hack on DSM kernel and user space. Do you happen to have a howto for that maybe? Otherwise I'm looking at translating a how in Russian, available here http://xpenology.com/forum/viewtopic.php?f=5&t=13 Don't know though how actual it is.

 

Cheers,

Link to post
Share on other sites
I had to wait for a few replication jobs but after restarting the VM still no SMART on my devices.

 

Can't remember what "smartctl -a /dev/sdc" says about Vendor, Product, Revision (VMware, Virtual Disk, 1.0 or something else) but it does not work.

 

Just thinking: I suppose that you have SMART option enabled in BIOS... :idea::?::twisted:

 

 

 

:cool:

After changing the Compatibility mode of the RDM-disks from virtual to physical I get the SMART information:

 

SYNOLOGY> smartctl -a /dev/sdb

smartctl 5.42 2011-10-20 r3458 [x86_64-linux-3.2.30] (local build)

Copyright © 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

 

=== START OF INFORMATION SECTION ===

Model Family: Western Digital AV-GP

Device Model: WDC WD20EVDS-63T3B0

Serial Number: WD-WCAVY1934485

LU WWN Device Id: 5 0014ee 2593c7b46

Firmware Version: 01.00A01

User Capacity: 2,000,398,934,016 bytes [2.00 TB]

Sector Size: 512 bytes logical/physical

Device is: In smartctl database [for details use: -P show]

ATA Version is: 8

ATA Standard is: Exact ATA specification draft version not indicated

Local Time is: Fri Jan 31 19:56:26 2014 CET

SMART support is: Available - device has SMART capability.

SMART support is: Enabled

Link to post
Share on other sites

I recently moved my ESXI install and datastore over to a PCIe mSATA card, and my test build is running good so far. Later I'll move that card to a system that can passthrough hardware and try to pass through the onboard SATA controller of my motherboard (DQ77KB).

 

In case anyone is looking for a good card that has drivers available for ESXI, here's the one I picked up for ~$25 on ebay. http://www.ebay.com/itm/mSATA-SATA-3-HD ... 1067002021

 

It uses the ASM 1061 chipset, and the drivers can be found here http://vibsdepot.v-front.de/wiki/index.php/Sata-xahci

 

If all goes well with passing through the onboard SATA controller, I also picked up one of these to turn my onboard mSATA slot into a sata port so I can add a 5th disk to my array :smile:

http://www.ebay.com/itm/290955489021?ss ... 1439.l2649

Link to post
Share on other sites

Can somebody also create an idiots guide for converting img to vmdk. I've been pulling my hair out trying to get this accomplish for hours and can't seem to get by that stupid grub error 22. Nobody seems to have a clear cut guide on how to do it in ESXi but I'm able to get it accomplish with VirtualBox and get by the "error 22" by just replacing the mounted VDMK with a backup version but that doesn't seem to work well in ESXi

Link to post
Share on other sites
Can somebody also create an idiots guide for converting img to vmdk. I've been pulling my hair out trying to get this accomplish for hours and can't seem to get by that stupid grub error 22. Nobody seems to have a clear cut guide on how to do it in ESXi but I'm able to get it accomplish with VirtualBox and get by the "error 22" by just replacing the mounted VDMK with a backup version but that doesn't seem to work well in ESXi

 

The idiots guide in this thread works fine, I've followed it for my first esxi VM's. The easiest to way to convert images is to use StarWind Software V2V Image Converter. It's free, you can find mirrors from download sites so you don't have to register at starwind to get it.

 

The alternative to that is using a live linux cd in a VM, with a virtual IDE HD attached to it. Transfer the IMG to the running linux VM and then dd if=name_of_image.img of=/dev/sda (or whatever drive letter the virtual IDE gets assigned. power down linux and move the virtual IDE drive to your synology VM to boot off of.

Link to post
Share on other sites
Can somebody also create an idiots guide for converting img to vmdk. I've been pulling my hair out trying to get this accomplish for hours and can't seem to get by that stupid grub error 22. Nobody seems to have a clear cut guide on how to do it in ESXi but I'm able to get it accomplish with VirtualBox and get by the "error 22" by just replacing the mounted VDMK with a backup version but that doesn't seem to work well in ESXi

 

The idiots guide in this thread works fine, I've followed it for my first esxi VM's. The easiest to way to convert images is to use StarWind Software V2V Image Converter. It's free, you can find mirrors from download sites so you don't have to register at starwind to get it.

 

The alternative to that is using a live linux cd in a VM, with a virtual IDE HD attached to it. Transfer the IMG to the running linux VM and then dd if=name_of_image.img of=/dev/sda (or whatever drive letter the virtual IDE gets assigned. power down linux and move the virtual IDE drive to your synology VM to boot off of.

 

 

The idiots guide listed is for already created VMDK. I've tried the starwind software to create the VMDK and still end up with the same error, even after following the guide. Is there is special procedure to create the VMDK in the Starwind software?

Link to post
Share on other sites

The idiots guide listed is for already created VMDK. I've tried the starwind software to create the VMDK and still end up with the same error, even after following the guide. Is there is special procedure to create the VMDK in the Starwind software?

 

At what point are you getting the error? the first boot, or after trying to install a PAT file? If it's the later, then it's because the install process of the PAT is writing over parts of you boot drive and messing it up. Some people get around this by making a copy of the boot drive before you try to install a PAT, then replace the messed up one by the PAT install with the unbroken copy you made. If it's the initial boot I dunno what to say.

 

I been playing with gnoboot's boot images and they work pretty nice, at least for testing purposes. I haven't testing any of the other boot images on here, but his doesn't get grub errors after installing.

Link to post
Share on other sites

The idiots guide listed is for already created VMDK. I've tried the starwind software to create the VMDK and still end up with the same error, even after following the guide. Is there is special procedure to create the VMDK in the Starwind software?

 

At what point are you getting the error? the first boot, or after trying to install a PAT file? If it's the later, then it's because the install process of the PAT is writing over parts of you boot drive and messing it up. Some people get around this by making a copy of the boot drive before you try to install a PAT, then replace the messed up one by the PAT install with the unbroken copy you made. If it's the initial boot I dunno what to say.

 

I been playing with gnoboot's boot images and they work pretty nice, at least for testing purposes. I haven't testing any of the other boot images on here, but his doesn't get grub errors after installing.

 

It happens after i install the PAT file. Every time I replace the VMDK with the backup it boots up again but when i run Synology Assistant it shows Configuration lost and puts me put me back to where i started with the PAT. Is there i special way to do this in ESXi because in Virtualbox i don't have these issues

Link to post
Share on other sites

It happens after i install the PAT file. Every time I replace the VMDK with the backup it boots up again but when i run Synology Assistant it shows Configuration lost and puts me put me back to where i started with the PAT. Is there i special way to do this in ESXi because in Virtualbox i don't have these issues

 

I dunno what to tell you. I had similar issue a long time ago when I setup DSM 4.2 in ESXI using the idots guide, but eventually got it to work somehow. I haven't messed with new installs until recently w/ gnoboot (which supposedly has fixes to prevent the issues you're having). Try a different boot img, or gnoboot, or maybe someone else has advice for you.

 

edit: to sum up the problem, it's nothing you're doing wrong. An untouched PAT image writes to the boot drive. From what I understand there's two ways around this; either you have patched PAT files, or boot images that prevent it (and also let you use stock PATs right from synology).

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.