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

IndieSchmindie said:
The one linked in the thread.

http://blog.davidwarburton.net/2010/10/25/rdm-mapping-of-local-sata-storage-for-esxi/

What I've found so far is.

1) Install windows directly to the micro server, it can see both the 3TB drives.
2) Install ESXi and follow the guide with a 120GB drive as RDM, everything is fine.
3) Install ESXi and follow the guide using the 3TB drives and everything seems fine in ESXi (The drives are correctly identified as 3TB) but when you come to add them in windows, it reads them as 512bytes.

Unless anyone else has managed to achieve this, I'm beginning to think it's just not possible, which is a shame as both the microserver BIOS and ESXi 5 both claim to support drives >2TB.
Click to expand...

Firstly, try creating them with a specific controller. Like;

Code: 
vmkfstools -a lsilogic -z /vmfs/devices/disks/[identifier] yourdisk.vmdk

It's worth naming the disk differently to before to create a new RDM.

Then, can you paste the result of both of the following commands
Code: 
cat yourdisk.vmdk
ls -al
Obviously changing yourdisk.vmdk for whatever you created.
 
Thanks for the suggestions. I'd already tried putting it on a new controller and specifying that with no difference. I'm not sure that is the issue as like I said, it works fine with a drive <3TB.

Hopefully there will be something you can get from the vmdk info :)

Code: 
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=fffffffe
parentCID=ffffffff
isNativeSnapshot="no"
createType="vmfsPassthroughRawDeviceMap"

# Extent description
RW 5860533168 VMFSRDM "3tbdisk1-rdmp.vmdk"

# The Disk Data Base 
#DDB

ddb.virtualHWVersion = "8"
ddb.longContentID = "64f08cb038823ec00c1b22acfffffffe"
ddb.uuid = "60 00 C2 9d 42 51 29 0a-46 ff 04 a6 9b 78 57 e0"
ddb.geometry.cylinders = "364801"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "lsilogic"

And the ls -al so you can see it has allocated the correct size

Code: 
-rw-------    1 root     root      3000592982016 Nov 28 14:23 3tbdisk1-rdmp.vmdk
-rw-------    1 root     root                499 Nov 28 14:23 3tbdisk1.vmdk
 
And finally, so you can see them OK in the datastore.

cca2457f72_screen_shot_2011-11-28_at_14.28.32.png
 
I need to ask again a question about video cards which I posed last week but unfortunately received no responses.

Browsing through this thread, I have found that there are a variety of recommended cards, i.e. MSI GeForce GT 520 810MHz 1GB.

I have a NVIDIA GeForce GT 430 1024MB video card kicking around and wondering whether this would be suitable for my 40L system.

Or a different approach - what should I be looking for when comparing video card specifications?

Thanks
 
Sinbad said:
I need to ask again a question about video cards which I posed last week but unfortunately received no responses.

Browsing through this thread, I have found that there are a variety of recommended cards, i.e. MSI GeForce GT 520 810MHz 1GB.

I have a NVIDIA GeForce GT 430 1024MB video card kicking around and wondering whether this would be suitable for my 40L system.

Or a different approach - what should I be looking for when comparing video card specifications?

Thanks
Click to expand...

Hi, You could try the GT430 the only reason i reccomended a GT520 was because it was a OK card for the game at a good price. I think the GT430 would be fine.
 
IndieSchmindie said:
Thanks for the suggestions. I'd already tried putting it on a new controller and specifying that with no difference. I'm not sure that is the issue as like I said, it works fine with a drive <3TB.

Hopefully there will be something you can get from the vmdk info :)

Code: 
# Disk DescriptorFile
version=1
encoding="UTF-8"
CID=fffffffe
parentCID=ffffffff
isNativeSnapshot="no"
createType="vmfsPassthroughRawDeviceMap"

# Extent description
RW 5860533168 VMFSRDM "3tbdisk1-rdmp.vmdk"

# The Disk Data Base 
#DDB

ddb.virtualHWVersion = "8"
ddb.longContentID = "64f08cb038823ec00c1b22acfffffffe"
ddb.uuid = "60 00 C2 9d 42 51 29 0a-46 ff 04 a6 9b 78 57 e0"
ddb.geometry.cylinders = "364801"
ddb.geometry.heads = "255"
ddb.geometry.sectors = "63"
ddb.adapterType = "lsilogic"

And the ls -al so you can see it has allocated the correct size

Code: 
-rw-------    1 root     root      3000592982016 Nov 28 14:23 3tbdisk1-rdmp.vmdk
-rw-------    1 root     root                499 Nov 28 14:23 3tbdisk1.vmdk
Click to expand...

That all looks fine.

Have you tried setting up the drive as GPT natively somewhere first?
 
Tried email the promotions people - no reply - I have a feeling that this offer might not be extended into December. . . . . . is it too late to order tonight - i.e. 29th - as that will be the invoice date - would I still qualify for the cash back ?
 
I got an email yesterday to say my cheque will be with me in 45 days (or less) ;)

Yes you will still qualify for cashback:-

The closing date for receipt of claim forms is Friday 23 December 2011. No claims will be accepted
after this date.
Click to expand...
 
MehulLakhani said:
The terms state that it has to be delivered before the 30th Nov - how do they know when it is delivered ? Do they check ?
Click to expand...

Delivered? You're right:

Product must have been delivered and invoiced between 1 and 30 November 2011.
Click to expand...

How odd! I was planning on placing a last-minute order for one tomorrow, but I guess I'm too late. But yeah, how are you supposed to know how long a retailer is going to take to deliver the server? "Invoiced on or before", I can understand, but putting a restriction on delivery date is just odd. What if the delivery is delayed? :confused:
 
The invoice I submitted last week just showed the sales completion date not delivery date, which was several days later, and that went through OK :)
 
You must log in or register to reply here.
Back
Top Bottom