I needed to expand my Windows 2008 R2 server with extra HDD data. I had an ISO available with VIOSTOR drivers (Virtio Storage) and autodetected the drivers. How could I be so stupid.

after reboot: BSOD and BSOD and stupid as I was I was unable to go back to ‘last good known configuration’.

first of all I had to pick the drivers for Windows 2008 from this location: ISO/viostor/2k8/(R2 if you have it)/amd64/viostor.*

To stop the BSOD from happening:

Find the viostor drivers (probably):


Rename Windows/System32/drivers/viostor.sys to System32/drivers/disabled.viostor.sys.disabled;

Similarly renamed both Windows/DriverStore/FileRepository/viostor.inf_amd64_neutral_b5a4b523b42ac3b3/viostor.sysand Windows/DriverStore/FileRepository/viostor.inf_amd64_neutral_e322cb56cfbcc209/viostor.systo disabled.viostor.sys.disabled

Then reboot.

Please be noticed that it can cost you a NEW license if you add this driver. Your hardware can be changed and it could be that Microsoft does not allow your key anymore.


A number of Windows 2008 server installations where designed to have 1 DISK with 100GB deviced in 50GB C and 50GB D. Unfortunately 50GB is too less if you run a server and want to apply all patches. (Previous downloaded patches are kept in a ‘storage’ and cannot be deleted, finally consuming a lot of HDD space.

To solve this: add a DATA DISK to the instance in Cloudstack. Please note: the DATA DISK will not be found / seen or identified automatically by the Windows Server

Through the managment panel within Cloudstack you need to attach an ISO: VIRTIO (Leaseweb does provide this)

Within the Device Manager an SCSI device has been found, but no drivers can be applied, therefore the ISO you need to attach so that the VIRTIO drivers can be applied to your machine.

Now the drive will become available and you can format etc..

To expand the C drive: remove all data from the partitions/drives not needed (D, E etc.) You can also copy the content to the new DATADISK you now have.

By default through the DISK MANAGER (under Server Manager) you  CANNOT expand the root / boot disk. You can try all kinds of freeware stuff: no go, it will all point you to version you have to pay $$ for.

The solution is to use DISKPART. As Administrator open a CMD window and enter:

List Disk <Enter>
Select Disk 0 <Enter> (Assuming that Disk 0 is your boot/root disk)
Detail Disk <Enter>
Information about your disk is given, you see the volumes
Select Volume 1 <Enter> (or 2 depends what is your Volume with C)
Extend Size = 20000 (20000 gives you an expand of 20GB for your C drive).

Repeat some commands if not all storage is given to C ..

Exit <Enter>

upgraded ESXI to 6.5 U1 which is version 6.5.0 build 5969303

You are running HPE Customized Image ESXi 6.5.0 version 650. released on July 2017 and based on ESXi 6.5.0 Vmkernel Release Build 5310538

unfortunately the HP Microserserver Gen8 is than running with: HPE_bootbank_scsi-hpvsa_5.5.0.102-1OEM.550.0.0.1331820

As I was (and still am but as of writing I am in maintenance mode) seeing spikes in my CPU usages. It might be caused by the bad performance

checking with:
cd /vmfs/volumes/datastore1
time dd if=/dev/zero of=tempfile bs=8k count=1000000

It took a very long time to see some output. (Very long time!)

than I tried to downgrade to the hpvsa-5.5.0-88.zip driver


  1. enter maintenance mode
  2. I do a reboot, but you can do it probably without
  3. copy the downloaded driver to /tmp/ and run the following command
  4. esxcli software vib install -d /tmp/hpvsa-5.5.0-88.zip
  5. the old driver will be removed and the 5.5.0-88 driver installed
  6. Now important: if you do reboot this way: you will not see your DataStores anymore, only your NFS datastores (in my situation) this is caused by VMWARE ESXI as it will be using vmw_ahci driver for the datastore.
  7. so disable the usage of this ‘default’ driver: esxcli system module set –enabled=false –module=vmw_ahci
  8. now you can reboot and your device will be using the 5.5.0-88 driver
  9. you can see this by using; cat /proc/driver/hpvsa/hpvsa0

the speed should have been returned.


Wauw ..

yesterday and today I tried to upgrade my HP Microserver Gen8 from VMWARE ESXI 6.0.0 to 6.5
what a trouble ..

shut down all vms (hosts) and enter maintenance mode. If you do this there are a number of online blogs with help to install from online depots but in all my tests it was too slow or I was to impatient to wait to end. But in the end I always ended up with an system with errors:

the transaction is not supported: VIB Hewlett-Packard_bootbank_scsi-hpvsa_5.5.0-88OEM.550.0.0.1331820

Do not try to force the installation. You will end up with an system where it seems that your EXSI is updated to 6.5 but actually is is running in a ramdisk environment. Easy to see cause you have lost your datastores (NFS datastores are still mounted).

If you than reboot: you are back to 6.0.0 .. so how to solve this:

easy: when entering maintenance mode: reboot your machine. In many guidelines this part is not mentioned.

After I rebooted I first tried the online depot installation documentation but ended up waiting and waiting. I got a VMWARE image for update from VMWARE but I got all kinds of different issues again:

“The upgrade contains the following set of conflicting VIB” When using the standard image of VMWARE: many conflicting vibs a no go for me. So I read some blogs and I found out that it is best to keep using your HPE image vmware files. (So in short: if you used the HPE VMWARE ESXI ISO installing Esxi onto your HP Microserver Gen8 keep using the update files with HPE in it and not the plain VMWARE onces. It can give issues !

After I used the HPE image I only got 1 issue: one vib was still complaining. On this blog I read what I needed to do: remove this vib (partner supported, so not native).

After removing this VIB I could upload the various ZIP bundle files like


with the command:
esxcli software vib install -d “/vmfs/volumes/datastore1/patch-directory/VMware-ESXi-6.5.0-5310538-HPE-650.”

I was able to install finally the 6.5 version. Due to issues of Storage driver I immediately updated to the U1 update
with the command:

esxcli software vib update -d “/vmfs/volumes/datastore1/patch-directory/VMware-ESXi-6.5.0-Update1-5969303-HPE-650.U1.”

the blog nxhut showed me some info that with the U1 version the storage speed performance issues should be over.

A simple test downloading a file towards a VM showed me a 18MB/s so the 10MB/s barrier was not seen.

A last reboot and get the machine out of maintenance mode. Finally I have a running 6.5U1.


Yeah .. wierd title

So in my case: I am at location A and I am making a VPN to my local network what is at location B

I can access all my local servers and computers, but one !

“The One” is a server which has a dedicated openvpn connection to location C, when this is active my VPN from location A cannot access “The One” at location B. Only when the OpenVPN connection is terminated

Solution: add a static route on “The One”

check with: ip route show

and add the route like this: ip route add via dev eth0

where is the VPN IP range what your local network is giving VPN users and via is the IP of your gateway (router)

… easy peacy ..

Google zegt dat deze site mogelijk gehacked is ..

en laat dat nu eens niet het geval zijn

Deze site is mogelijk gehackt., zegt Google. Ja maar …. en dan ga je zoeken, testen en je weet me god niet waar je moet zoeken. Want .. tsja je krijgt wel een link, maar als je link naar de weblog sectie van deze site verwijst dan staan daar een x aantal berichten onder met wat ‘technisch’ karakter, maar dat is het dan wel .. heb dus totaal geen idee waar ik moet zoeken of wel stukje code wat ik getikt hebt een trigger is voor Alphabet’s Google ..

Mocht je iets vreemds bemerken, ik hoor het wel, tot die tijd blijven we ons afvragen wat er mis zou zijn .. (Ik heb het theme is al veranderd .. ) dus een theme hack sluit ik even uit


update: Na eerst 1 pagina aan te merken als iets wat niet goed zou zijn, vond Google dat dan de gehele site wel even geïnfecteerd was. Maar echte duiding wat er dan mis is: nope ..

Dus ..

update: diep in de spelonken van dit weblog was wel wat aan de hand met wat gemodificeerde bestanden maar zou niet zo 1-2-3 kunnen zien of dat Google zou signaleren .. maar goed , WordPress maar even waar nodig geheel verwijderd en opnieuw geïnstalleerd zodat er geen ‘historie’ van oude bestanden meer aanwezig was.

Tevens een aantal folders die niet meer gebruikt werden ook verwijderd zodat dat ook geen belemmering zou kunnen geven ..Zie hier . site is weer ok .. zegt Google dan ;)

Nadat ik las dat Schiphol data van vertrekkende en landende vliegtuigen beschikbaar ging maken dacht ik: laat ik eens kijken of ik deze data ook kan verwerken in een website.

Na een paar weken stoeien is tie dan als een soort van 1st release beschikbaar: AroundMyRoom’s Schiphol page

Vooral het het begin lopen te stoeien hoe ik de JSON data kom omzetten in arrays en objecten. Met wat hulp van Tweakers.net kwam ik daar wat verder mee.  Daarna liep ik best wel vast met wat for each loops en daar heeft Peter aka zaph.nl mijn mee kunnen helpen.

Op het laatst ging het bijna mis met de checkin balies, want ik wilde wat meer dan wat de API makkelijk mij kon voorschotelen. Ik maak namelijk een verschil tussen normale checkin-balies en andere soorten. Ik had het op basis van Type kunnen doen, maar ik koos onbewust voor de beschrijving waarbij hier vele verschillende schrijfwijzen voorbij kwam.  Door niet op te geven en door te blijven zoeken kwam ik wat functies tegen die ik kon gebruiken. De code is zeer zeker niet geoptimaliseerd, maar hey, het werkt ..

Wat ik als wens heb ik dat ik data wat sneller van de API zou kunnen krijgen / voorschotelen. Wellicht data tijdelijk in een DB stoppen zodat de data snel gepresenteerd kan worden. ..

Message to self: Important

When you create a userspace alike ODBC connection in Windows 2008 Server (whatever) it is likely that Access does not allow you to use linked tables as it is requiring a password.
Although you have the ability to store passwords in Access when linking tables through ODBC it is not always working when the ODBC connection is set in the field ‘user’ rather than Machine DataSource/System

The trick is to execute as admin the file c:\windows\SysWOW64\odbc32.exe
Then create the System ODBC connection towards the SQL database, return to your Access file and link the tables (and keep in mind to save the password as well when linking)

I tried above multiple times when the ODBC was in userspace or was (probably) not correctly created (32 versus 64 bits??)
Possible it can also be related that the application pool is 32bits rather then 64bits and the ODBC connection needs 32bits as well .. Hell: if this occurs again, you have some tips ;_)