VMware Cloud Community
yud111
Contributor
Contributor

Error: "Failed to create virtual disk: Invalid argument (1441801)"

Hi,

I know this question has been asked in the past but I have not yet seen a solution.

Can you please advise if there is a solution.

(please be gentle on me - I am new to this stuff...)

My Setup:

* Proliant MicroServer N54L

* Adaptec 2405 RAID card

* 2 x Seagate 1TB HDD's (ST31000524AS) in RAID1 for VM's datastore

* 2 x Seagate 3TB HDD's (ST3000DM001) in RAID 1 for storage datastore

* ESXi 5.5 (1746974-HP-5.72A.3-Jun2014) booting from USB stick

All is functioning and I have 2 x VM's running happily on this setup.

Now I want to add a 3rd VM, which requires adding the storage disks manually.

When I run the vmkfstools -z command I get the error:

"Failed to create virtual disk: Invalid argument (1441801)"

The exact syntax i used is: vmkfstools -z /vmfs/devices/disks/mpx.vmhba2:C0:T1:L0 /vmfs/volumes/VM_Datastore/RDM/NAS_Drive1.vmdk

The disk ID in bold is correct.

I searched the error and found it is common with Adaptec RAID cards.

Given the fact the Adaptec 2405 is on the HCL should I be getting this error? Is there anything I can do to resolve it?

My VMware skills are very basic. I do not have access to vMotion or any enterprise console. This is a standalone ESXi installation.

Will appreciate any help.

Regards,

Y.

0 Kudos
4 Replies
William22
Enthusiast
Enthusiast

Hi

Welcome to communities.

please run this command and share the output  ,

fdisk -l

0 Kudos
yud111
Contributor
Contributor

Thanks for your reply and the welcome...

Here is the output

~ # fdisk -l

***

*** The fdisk command is deprecated: fdisk does not handle GPT partitions.  Please use partedUtil

***

Found valid GPT with protective MBR; using GPT

Disk /dev/disks/mpx.vmhba32:C0:T0:L0: 7826688 sectors, 7643K

Logical sector size: 512

Disk identifier (GUID): e27479b9-6be2-4262-b023-f42d5c68e8bb

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 7826654

Number  Start (sector)    End (sector)  Size       Code  Name

   1              64            8191        8128   0700

   5            8224          520191        499K   0700

   6          520224         1032191        499K   0700

   7         1032224         1257471        219K   0700

   8         1257504         1843199        571K   0700

fdisk: device has more than 2^32 sectors, can't use all of them

Found valid GPT with protective MBR; using GPT

Disk /dev/disks/mpx.vmhba2:C0:T1:L0: 4294967295 sectors, 4095M

Logical sector size: 512

Disk identifier (GUID): 201839cf-6c8b-43e2-8bd0-2179dd04fed4

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 5851033566

Number  Start (sector)    End (sector)  Size       Code  Name

   1            2048      5851033566       5579M   0700

Found valid GPT with protective MBR; using GPT

Disk /dev/disks/mpx.vmhba2:C0:T0:L0: 1952428032 sectors, 1861M

Logical sector size: 512

Disk identifier (GUID): d47cbda3-bb9c-43f4-8515-9e45f94a2566

Partition table holds up to 128 entries

First usable sector is 34, last usable sector is 1952427998

Number  Start (sector)    End (sector)  Size       Code  Name

   1            2048      1952427998       1861M   0700

Please note: since getting the error I wiped the datastore, re-created it and configured it to be used by FreeNAS as a test. This could be the reason for the GPT warning (I'm not sure).

However, I still get the 1441801 error.

Thanks for your help.

Y.

0 Kudos
yud111
Contributor
Contributor

Apologies for bumping this but is there a solution to the error "Failed to create virtual disk: Invalid argument (1441801)" ?

0 Kudos
krish290785
Enthusiast
Enthusiast

You might want to check the below link.

1441801 on creating RDM

-Bala Krishna Gali If the above info is useful, please mark answer as correct or helpful.
0 Kudos