Good Cheap Server - HP Proliant Microserver 4 BAY - OWNERS THREAD

tbz_ck said:
RDM mapped drives will sort this.

Check out my article on my website for details:

http://forza-it.co.uk/esxi-5-1-using-raw-device-mappings-rdm-on-an-hp-microserver/
Click to expand...

so i putty'd into the server under SSH, stuck the following in:

vmkfstools -z /vmfs/devices/disks/t10.ATA_____ST3000DM0012D9YN166__________________________________W1F162TT /vmfs/volumes/datastore1/disk/3tb.vmdk


comes up with
Failed to create virtual disk: The system cannot find the file specified (25).
any ideas?

seems the drive name is correct? are my paths??
 
Last edited:
something has gone horribly wrong. thought it was all ok , went into whs2011 to create the disk but couldnt access it and it was showing as -128mb
no matter what i did nothing worked,
took the drive out put it in my normally machone and now its showing as 768mb - i presume the 2tb is a virtual partition somewhere but how can i access and remove it?

all i want to do is get a single partition table back so i can start the process from scratch..
 
Is this a 3Tb drive by any chance? I had exactly the same thing with ESXi and a new Seagate 3Tb drive recently.

Solution:

  1. Take the drive out and attach it to another system (e.g. a workstation)
  2. Delete any partitions and re-initialise it as GPT
  3. Create your partition and format as necessary
  4. Re-attach to ESXi, re-create the raw VMDK, add to VM
It will still show up in a Windows VM (in disk management) as an odd size but it works fine. Not sure why it happens, not sure if there are any long lasting issues either. There's probably an explanation on the VMWare KB somewhere but I'd imagine it's a >2Tb or GPT issue with raw mapped drives.
 
but how can you delete the virtual partitions if windows cant see them? look at this (in a win7 workstation)
in diskpart the drive says:

diskp.png

disk 9 - 746mb incorrect.

so go into disk manager says:
wind.png


good you would think , but if you go delete volume windows says it notices a parition created elsewhere do you want to remove, click yes and the drive changes to 746mb (i presume windows couldnt remove it successfully)
 
Last edited:
Are there any partitions you can delete when it's down to 746gb? It might be at that point you can re-initialise the drive. Apologies, it's a week or so since I had to do this so the details are fuzzy!

I take it the drive was fresh when you first attached it to ESX and attempted to format within a Windows VM?
 
Anyone had any issues with the SATA backplane connector?
I've only unplugged mine a handfull of times and now it looks as if the little metal clasp is stuck inside.

Means I can't get the mobo out :(
 
Shad said:
Are there any partitions you can delete when it's down to 746gb? It might be at that point you can re-initialise the drive. Apologies, it's a week or so since I had to do this so the details are fuzzy!

I take it the drive was fresh when you first attached it to ESX and attempted to format within a Windows VM?
Click to expand...

it just partitions to 746, no matter what i do.
doing a google search i feel its more to do with lack of bios update or something than a vm issue - will do some more playing tonight and see what happens though i tried seagates tools last night and it didnt find it. :mad:

I hear Intel Rapid Storage Tech might be the issue so will update first and see what happens.
 
Last edited:
You can run MS Security Essentials on WHS if you install it with a flag that disables the OS check. However it won't be properly licensed if you do and you should do it only at your own risk!
 
tbz_ck said:
You can run MS Security Essentials on WHS if you install it with a flag that disables the OS check. However it won't be properly licensed if you do and you should do it only at your own risk!
Click to expand...

Ooh would this enable me to install it on SBS2003 or no?

If not are there any decent (free) alternatives to Clamwin?

Thanks,

G
 
Last edited:
Just thought id let everyone know. I ordered another Microserver (I have 2 now) and ordered the 16gb kit CMV16GX3M2A1333C9 and it worked perfectly. ESXI shows 16gb of memory avaliable and its all been fine.
 
iamtheoneneo said:
it just partitions to 746, no matter what i do.
doing a google search i feel its more to do with lack of bios update or something than a vm issue - will do some more playing tonight and see what happens though i tried seagates tools last night and it didnt find it. :mad:

I hear Intel Rapid Storage Tech might be the issue so will update first and see what happens.
Click to expand...

finally got it to work, heres what i did for reference:

* so it seems the IRST update was required so grabbed from the gigabyte website and installed.
* attached the drive to a usb adaptor but windows diska manager said it was there (A start) but couldnt convert.
* stuck it in the workstation as a bios bootup and job done able to format and see all 3tb of it.

such a pain in the ass but glad its sorted ! :p
now in vm of whs2011 i formatted it again (bc it wanted me too after doing the RDM stuff) and it works but comes up as this:

drive.png


is that correct? the at risk bit is kinda worrying lol
 
Last edited:
iamtheoneneo said:
stuck it in the workstation as a bios bootup and job done able to format and see all 3tb of it.
Click to expand...
Sorry I should've said, I had to do that too as my USB adapter didn't recognise it properly either.

That's how mine shows up in the VM too, in terms of the -127MB thing. Dynamic disk though... good luck with that ;) :p

Oh, I don't have a warning next to the disk either.
 
Shad said:
Sorry I should've said, I had to do that too as my USB adapter didn't recognise it properly either.

That's how mine shows up in the VM too, in terms of the -127MB thing. Dynamic disk though... good luck with that ;) :p

Oh, I don't have a warning next to the disk either.
Click to expand...

was urs a dynamic disk too? its the only thing i could select?
I dont know why the health warning is there , the drive is new and apart from some messing around with partitions it should be healthy, to me its windows kinda twigging that somethings a little out of place within the vm.

I need to start filling this up now, It should be safe right? right? ;)
 
No mine is a basic GPT disk. If I were you I'd take it out, zap it and re-init as basic with GPT on your workstation, and re-attach to ESX. The last thing you want is a problem with a 3Tb drive, that's a lot of data to go wrong.

Do it right, do it once!
 
You must log in or register to reply here.
Back
Top Bottom