ESX SD Card?

KB ID 0001785

Problem

For a while it’s been common knowledge that running ESX 7.x from a server that boots with an SD-Card is a no no. VMware themselves said (originally) that they would not support it. Then they said they would ‘sort of‘ support it, if there was additional persistent storage. Then in the past week they’ve said,

VMware will continue supporting USB/SD card as a boot device through the vSphere next product release, including the update releases. Both installs and upgrades will be supported on USB/SD cards.

But, it’s not a complete ‘Back peddle’ because they also say;

The upgrade or install workflows for vSphere will ensure that the OSData partition is relocated away from USB/SD card into a persistent device. There will be an automatic fallback to use a VMFS datastore, or a RAMDisk if such a device is not available. Preferably, the SD cards should be replaced with an SSD or another local persistent device as the standalone boot option.

Reference

ESX SD Card 

So best to err on the side of caution and NOT install anything (or upgrade to anything) newer than 7.0 on an SD Card. I’ve got a client running 6.7 looking to upgrade so I needed to find out if their hosts (a mix of Dells and IBMs) were on the HCL, and more importantly were they booting from SD-Cards?

A quick Google search revealed someone had written PowerCLI Script to do this, problem was the clients management server would need a reboot to get the PowerCLI installed (with the management agents). So I had to grow a ginger pony tail, don my socks and sandals, and do some Linux.

Connect to your EXIi via SSH, First ascertain where you’re booting from (bootbank)

[box]

ls -la /bootbank

[/box]

As you can see in the example below, this will return the VFMS volume tat we need (in this case /vmfs/volumes/dcb33778-ff2797db-9624-0bfeb9391a11) change your command to match the name of yours.

[box]

vmkfstools -P /vmfs/volumes/dcb33778-ff2797db-9624-0bfeb9391a11

[/box]

This time look for Partitions spanned (on “disks”) in the example below, mine’s called naa.600605b00a6913d01e22c30c056436ac (Note: ignore any colons ‘:’ and anything to the right of them).

Then use the disk name in the following command.

[box]

esxcli storage core device list |grep -A27 ^naa.600605b00a6913d01e22c30c056436ac

[/box]

From the output you should be able to tell what the boot device is, for example my client IBM servers gave me this (so I knew they were booting from internal disks).

But the Dell servers, although on the VMware HCL for version 7, were booting from SD Cards (see the following output).

Knowing the servers concerned (Dell R630 PowerEdges) I know they need a particular RAID card (yes I know you can get a cheap 330 model, but not for production hosts!) Then, a specific cable, and the the cost of the drives, to get them for a server this old, Dell will try to charge me a fortune, it’s probably easier to replace those hosts.

Get ESX SD Card Boot Info From PowerCLI

I mentioned earlier that this avenue was not open to me, so I gave it a shot on my test network.

SD-Card-Check is what I used (Note: I do not claim credit for this, Credit to Ivo Bereens.)

Related Articles, References, Credits, or External Links

NA

VMware ESXi Syslog Errors – ‘System logs on host {host-name} are stored on non-persistent storage.’

KB ID 0000456 

Problem

Syslog Error Seen on ESXi 6.0 and 6.5

System logs on host {host-name} are stored on non-persistent storage.

Syslog Error Seen on ESXi 5.1

Error Configuration Issues System logs on host {host-name} are stored on non-persistent storage.

Syslog Error Seen on ESXi 5

Error Configuration Issues System logging is not configured on host {host-name}.

Syslog Error Seen on ESXi 4

Error Configuration Issues Issue detected on {host-name}: Warning: Syslog not configured. Please check Syslog options under Configuration.Software.Advanced Settings.

Solution

Seen on ESXi hosts that boot from an internal SD card, (or USB Drive.)  ESXi likes to have some persistent storage to keep its logs on.

To stop this error you need to give it a location for the logs. That location is setup as follows;

ESXi (Post Version 6) Setting a Syslog Location

First, create a folder on some shared storage to save you logs into, below you can see my datastore name is [iSCSI-RAID5-SAS], and Ive created a folder called ‘Logs’

Select the host with the error > Configure > Advanced System Settings > Type ‘Global’ in the search criteria > Locate Syslog.Global.LogDir > Select it > Edit.

Once again, search for Global and change the location to [DATASTORE-NAME]Logs\HOST-NAME > OK.

The error should cease immediately, without the need to restart anything.

ESXi (Pre Version 6) Setting a Syslog Location

With an ESXi host selected, Configuration > Advanced Settings > Syslog > Syslog.global.logDir.

Here you have two options,

Option 1 Store the Syslogs on the SD Card

Note: If you have built the ESXi Server from a manufacturers ESXi DVD (the HP build for example) there may not be enough room on the SD card for the logs.

In the example below, I’ve got an ESXi host, that’s running ESXi from an SD card (4GB) and I’ve put the syslog on there by using the default entry of;

[box][]/scratch/log[/box]

Click OK > After a couple of seconds the alert will disappear (without the need to reboot).

Option 2 Store the Syslogs on Local or Shared Storage.

ESXi 5 Putting the syslog onto a DataStore

With an ESXi host selected, Configuration > Storage > On a datastore, right click > Browse Datastore > Select the new folder icon > call the folder LOGS > OK.

Note: In this example I’m storing the syslog on local storage (on the ESXi host) if you have shared storage , i.e. a SAN or NAS, I suggest you create a sub-folder for each ESXi host within the LOGS directory and set the path on each host accordingly. This will take effect without a reboot and the error should cease.

ESXi 4 Putting the syslog onto a DataStore

In this case I created a syslog area on one of the shared data stores.

With an ESX host selected, Configuration > Storage > On a datastore, right click > Browse Datastore > Select the new folder icon > call the folder syslog > OK.

Then select Advanced Settings > Syslog > Enter a value in the following format:

[datastore]/syslog/hostname.log

i.e. [Volume 3]/syslog/esx2.log

3. Click OK, you should not need to reboot, the error should cease straight away.

Related Articles, References, Credits, or External Links

Original Article Written 22/11/12

Audi – MMI v3 – Showing Album Art With Mp3 Files

KB ID 0001116 

Problem

A few weeks ago I changed cars, I was pleased to see that the entertainment system in my new car could play music from SD card. These are cheap and can hold a Lot of songs, so rather than have my iPod in the car, I could simply drop music onto an SD card.

Which I did but, annoyingly non of the ‘album artwork’ was displayed, even though the music played fine. I did some Googling and read a few Audi forums, and finally got it to work.

Solution

Theres a lot of conflicting information in forums on how to get this to work, so I will just tell you how I got mine working.

  • Car: Audi A6 (2013)
  • MMI Version 3

SD Card Size: Has to be 32GB or less  – This is because it has to be formatted at FAT32, it’s a limitation of the storage system not Audi or the SD Cards (Yes you can have more than 32GB FAT32 drives, thats a different argument).

To Check;

Mac OSX (right click > Get Info).

Windows (Right Click > Properties).

Why is there a problem displaying Album art?

Well, (and I’m making the assumption your mp3 files actually have album art embedded within them, (thats in the mp3 file, not in a different folder, if not get that sorted first!) The Audi will only display art if;

  • It’s less than 500×500 pixels in size.
  • It’s less than 254kb in file size (the image not the track!)

For example, below Im using the excellent, (and free) Mp3tag to look at this songs details, see the album art is 2000×2000 pixels, and is 409Kb in size. Try to play this in the car and the music will play but you will just see a generic ‘musical note’ instead of the album art.

Well that’s OK, but manually resizing all your album art could take along time, (I’ve got a large music collection). To do that requires another brilliant free piece of software called Bliss, (download here). I’m using Mac but theres a Windows version as well.

Windows Alternative

If I’m in Windows I use Sense Mp3 Art Sizer;

Back to my mac..

Install and run the software, at this point it appears nothing has happened but you should see a large blue ‘bl’ at the top of the screen. Right click that, and it will open. Go to Settings.

Change the music location, so that it points to your SD card.

Under the cover art section click ‘more’.

You now have the option to set the maximum size, set it to 500×500, and then set the maximum size to 256KB. Click Apply Rules an it should rattle its way though all the songs on the SD card. Depending on how many you have, this can take a while.

Notice once complete, when looking at the album art it has been resized, and should now show correctly in the car.

Additional Steps For Mac OSX Users.

Mac OSX has a habit of dropping some folders on the drive, and their names start with a full stop (or period if you’re over the pond). Normally that is not a problem, but your Audi will not like this, (typically is scrolls through all the songs and does nothing).

My Mac is set to show hidden folders, so you probably wont even be able to see them, to remove them open a terminal window. Execute the following two commands;

[box]

cd /volumes

ls

[/box]

What this does, is shows you the names of the mounted volumes, mines got a simple enough name because I called it PETES-AUDI, yours might be something else, take note of what it’s being called.

Then, change into the volume name for the card, change to match the name of yours, then issue three rm commands as shown below(rm is simply a remove command).

[box]

cd PETES-AUDI

rm -rf .f*

rm -rf .S*

rm -rf .T*

[/box]

Then you can eject the SD card, and play it in the car.

Related Articles, References, Credits, or External Links

Original Article Written 17/12/15

ESXi Error “HA agent must have userworld swap enabled”.

KB ID 0000045

Problem

Seen on diskless ESXi Servers, this happens because, to perform HA, the server needs some swap space, and a diskless server has none.

Solution

1. Using your VI client log into your Virtual Center Server.
2. Select the first ESXi host > Configuration > Advanced Settings
3. Select ScratchConfig > Type in a directory with at least 1GB of free storage e.g

/vmfs/volumes/SAS1_V1/Scratch/ESXi1

Note: I’ve read various posts that say – all hosts can use the same folder, but I’ve seen that not work, create a folder for each ESXi host.
Note2: You can create folders using the datastore browser.

4. Tick the Box that says “ScratchConfig.ConfiguredSwapState”
5. Reboot the ESXi host.

On reboot you may notice that the path has changed to something like “/vmfs/volumes/4b689385-77e74be9-dc10-002581e88ad4/Scratch/ESXi1” this is normal.

6. Right click each ESXi host and select “Reconfigure for HA”.

 

Related Articles, References, Credits, or External Links

NA

Cannot Format a SDHC Card to NTFS

KB ID 0000187 

Problem

I had a 16 GB SDHC card, and windows would format it to FAT but not NTFS, this is how to cure the problem.

Solution

Option 1

Download this and use it to format the drive.

Option 2

1. Click Start > In the Search/Run Box type devmgmt.msc > Device Manager will open

2. Navigate to your SC Card reader > Right Click > Properties > Policies > Select Better Performance > OK > Reboot the PC > Try again.

To format your card to FAT32 Quickly use this application.

 

Related Articles, References, Credits, or External Links

NA