14 Replies Latest reply on Aug 29, 2019 5:26 PM by insearchof

    Unable to add Disk LUNS for Datastore

    insearchof Enthusiast

      VMWare 6.5

       

      Just upgrade my entire Data Center to using Dell PowerEdge Gen 13 R430 All my ESXI hosts have same hard ware configuration except for Disk drives.

       

      Each host has 4 bays for drives.

       

      In Bay 1 I have and SSD drive all ESXI hosts see that drive.

       

      The other 3 bays as Sata drives of various size from 1 TB to 3 TB

       

      Some of the hosts see all the drives in the bays and some do not.   that problem I am working on with the Hardware group.

       

      On the Hosts that I see all the drives I am unable to create a new data store because they to not show in the list.

       

      I ssh;d to one of the hosts and ran

       

      esxcfg-volume --list    and it was blank line returned did not show any volumes.

       

      How do I get the drives to show up?

       

      Thank you

       

      Tom

        • 1. Re: Unable to add Disk LUNS for Datastore
          AlessandroRomeo68 Hot Shot

          Hi,

           

          Could be this case, you can check:

           

          Increase Datastore Capacity - LUN not showing

           

          Best regards,

          Alessandro Romeo

          • 2. Re: Unable to add Disk LUNS for Datastore
            a.p. Guru
            User ModeratorsCommunity WarriorsvExpert

            How are these drives connected, i.e. presented to ESXi? SATA ports, RAID controller, ...?

            Please read https://kb.vmware.com/s/article/2091600 which explains some limitations for vSphere versions prior to 6.7.

             

            André

            • 3. Re: Unable to add Disk LUNS for Datastore
              insearchof Enthusiast

              Why

              a.p.

               

              the servers have a raid controller card and all devices are connected to that raid controller

               

              I do not have any raid configuration using all drives as individual.

               

              Maybe I need to validate the raid controller configuration

               

              Foreign drives have issues I think

               

               

              Still does not explain why on the hosts I do see all the drives that I can not see them when I try to create a new datastore

               

               

              I looked at the storage  adapters and the number of devices matches what I see on the storage devices

               

              why does  esxcfg-volume -l   not show anything  any other commands I can run to try

               

              Thanks

              • 4. Re: Unable to add Disk LUNS for Datastore
                insearchof Enthusiast

                Alessandro

                 

                 

                His problem was similar but he was trying to add space to existing datastores

                 

                I do not have a data store to add space too.

                 

                The Storage adapters shows the same number of drives I see on the Storage devices display.

                 

                Are there and command besides  esxcfg-volume -l    to try ?

                 

                Thanks

                • 5. Re: Unable to add Disk LUNS for Datastore
                  insearchof Enthusiast

                  The ESXi Shell can be disabled by an administrative user. See the

                  vSphere Security documentation for more information.

                  [root@TGCSESXI-12:~] cd /dev/disks

                  [root@TGCSESXI-12:/dev/disks] ls -l

                  total 6699018919

                  -rw-------    1 root     root     120034123776 Aug 19 00:51 mpx.vmhba0:C0:T0:L0

                  -rw-------    1 root     root       2097152 Aug 19 00:51 mpx.vmhba0:C0:T0:L0:1

                  -rw-------    1 root     root     120030961152 Aug 19 00:51 mpx.vmhba0:C0:T0:L0:                                                                                                              2

                  -rw-------    1 root     root     15483273216 Aug 19 00:51 mpx.vmhba32:C0:T0:L0

                  -rw-------    1 root     root       4161536 Aug 19 00:51 mpx.vmhba32:C0:T0:L0:1

                  -rw-------    1 root     root     262127616 Aug 19 00:51 mpx.vmhba32:C0:T0:L0:5

                  -rw-------    1 root     root     262127616 Aug 19 00:51 mpx.vmhba32:C0:T0:L0:6

                  -rw-------    1 root     root     115326976 Aug 19 00:51 mpx.vmhba32:C0:T0:L0:7

                  -rw-------    1 root     root     299876352 Aug 19 00:51 mpx.vmhba32:C0:T0:L0:8

                  -rw-------    1 root     root     2684354560 Aug 19 00:51 mpx.vmhba32:C0:T0:L0:9

                  -rw-------    1 root     root     300000000000 Aug 19 00:51 naa.5000c50012daec7b

                  -rw------- 1 root root 299432044544 Aug 19 00:51 naa.5000c50012daec7b :1

                  -rw-------    1 root     root     3000592982016 Aug 19 00:51 naa.50014ee20bd195a                                                                                                              f

                  -rw-------    1 root     root       2097152 Aug 19 00:51 naa.50014ee20bd195af:1

                  -rw------- 1 root root 3000589819392 Aug 19 00:51 naa.50014ee20bd195a f:2

                  lrwxrwxrwx    1 root     root            20 Aug 19 00:51 vml.0000000000766d68626                                                                                                              133323a303a30 -> mpx.vmhba32:C0:T0:L0

                  lrwxrwxrwx    1 root     root            22 Aug 19 00:51 vml.0000000000766d68626                                                                                                              133323a303a30:1 -> mpx.vmhba32:C0:T0:L0:1

                  lrwxrwxrwx    1 root     root            22 Aug 19 00:51 vml.0000000000766d68626                                                                                                              133323a303a30:5 -> mpx.vmhba32:C0:T0:L0:5

                  lrwxrwxrwx    1 root     root            22 Aug 19 00:51 vml.0000000000766d68626                                                                                                              133323a303a30:6 -> mpx.vmhba32:C0:T0:L0:6

                  lrwxrwxrwx    1 root     root            22 Aug 19 00:51 vml.0000000000766d68626                                                                                                              133323a303a30:7 -> mpx.vmhba32:C0:T0:L0:7

                  lrwxrwxrwx    1 root     root            22 Aug 19 00:51 vml.0000000000766d68626                                                                                                              133323a303a30:8 -> mpx.vmhba32:C0:T0:L0:8

                  lrwxrwxrwx    1 root     root            22 Aug 19 00:51 vml.0000000000766d68626                                                                                                              133323a303a30:9 -> mpx.vmhba32:C0:T0:L0:9

                  lrwxrwxrwx    1 root     root            19 Aug 19 00:51 vml.0200000000200000000                                                                                                              0000000435431323042 -> mpx.vmhba0:C0:T0:L0

                  lrwxrwxrwx    1 root     root            21 Aug 19 00:51 vml.0200000000200000000                                                                                                              0000000435431323042:1 -> mpx.vmhba0:C0:T0:L0:1

                  lrwxrwxrwx    1 root     root            21 Aug 19 00:51 vml.0200000000200000000                                                                                                              0000000435431323042:2 -> mpx.vmhba0:C0:T0:L0:2

                  lrwxrwxrwx    1 root     root            20 Aug 19 00:51 vml.02000000005000c5001                                                                                                              2daec7b535433333030 -> naa.5000c50012daec7b

                  lrwxrwxrwx    1 root     root            22 Aug 19 00:51 vml.02000000005000c5001                                                                                                              2daec7b535433333030:1 -> naa.5000c50012daec7b:1

                  lrwxrwxrwx    1 root     root            20 Aug 19 00:51 vml.020000000050014ee20                                                                                                              bd195af574443205744 -> naa.50014ee20bd195af

                  lrwxrwxrwx    1 root     root            22 Aug 19 00:51 vml.020000000050014ee20                                                                                                              bd195af574443205744:1 -> naa.50014ee20bd195af:1

                  lrwxrwxrwx    1 root     root            22 Aug 19 00:51 vml.020000000050014ee20                                                                                                              bd195af574443205744:2 -> naa.50014ee20bd195af:2

                  [root@TGCSESXI-12:/dev/disks]

                   

                  This is a host that shows 3 drives but I do not see them when I try to add a new data store

                  • 6. Re: Unable to add Disk LUNS for Datastore
                    insearchof Enthusiast

                    [root@TGCSESXI-11:~] cd /dev/disks

                    [root@TGCSESXI-11:/dev/disks] ls -l

                    total 253138752

                    -rw-------    1 root     root     120034123776 Aug 19 02:09 mpx.vmhba0:C0:T0:L0

                    -rw-------    1 root     root       2097152 Aug 19 02:09 mpx.vmhba0:C0:T0:L0:1

                    -rw-------    1 root     root     120030961152 Aug 19 02:09 mpx.vmhba0:C0:T0:L0:                                                                                                              2

                    -rw-------    1 root     root     15518924800 Aug 19 02:09 mpx.vmhba32:C0:T0:L0

                    -rw-------    1 root     root       4161536 Aug 19 02:09 mpx.vmhba32:C0:T0:L0:1

                    -rw-------    1 root     root     262127616 Aug 19 02:09 mpx.vmhba32:C0:T0:L0:5

                    -rw-------    1 root     root     262127616 Aug 19 02:09 mpx.vmhba32:C0:T0:L0:6

                    -rw-------    1 root     root     115326976 Aug 19 02:09 mpx.vmhba32:C0:T0:L0:7

                    -rw-------    1 root     root     299876352 Aug 19 02:09 mpx.vmhba32:C0:T0:L0:8

                    -rw-------    1 root     root     2684354560 Aug 19 02:09 mpx.vmhba32:C0:T0:L0:9

                    lrwxrwxrwx    1 root     root            20 Aug 19 02:09 vml.0000000000766d68626                                                                                                              133323a303a30 -> mpx.vmhba32:C0:T0:L0

                    lrwxrwxrwx    1 root     root            22 Aug 19 02:09 vml.0000000000766d68626                                                                                                              133323a303a30:1 -> mpx.vmhba32:C0:T0:L0:1

                    lrwxrwxrwx    1 root     root            22 Aug 19 02:09 vml.0000000000766d68626                                                                                                              133323a303a30:5 -> mpx.vmhba32:C0:T0:L0:5

                    lrwxrwxrwx    1 root     root            22 Aug 19 02:09 vml.0000000000766d68626                                                                                                              133323a303a30:6 -> mpx.vmhba32:C0:T0:L0:6

                    lrwxrwxrwx    1 root     root            22 Aug 19 02:09 vml.0000000000766d68626                                                                                                              133323a303a30:7 -> mpx.vmhba32:C0:T0:L0:7

                    lrwxrwxrwx    1 root     root            22 Aug 19 02:09 vml.0000000000766d68626                                                                                                              133323a303a30:8 -> mpx.vmhba32:C0:T0:L0:8

                    lrwxrwxrwx    1 root     root            22 Aug 19 02:09 vml.0000000000766d68626                                                                                                              133323a303a30:9 -> mpx.vmhba32:C0:T0:L0:9

                    lrwxrwxrwx    1 root     root            19 Aug 19 02:09 vml.0200000000200000000                                                                                                              0000000435431323042 -> mpx.vmhba0:C0:T0:L0

                    lrwxrwxrwx    1 root     root            21 Aug 19 02:09 vml.0200000000200000000                                                                                                              0000000435431323042:1 -> mpx.vmhba0:C0:T0:L0:1

                    lrwxrwxrwx    1 root     root            21 Aug 19 02:09 vml.0200000000200000000                                                                                                              0000000435431323042:2 -> mpx.vmhba0:C0:T0:L0:2

                    [root@TGCSESXI-11:/dev/disks]

                     

                    This host only the SAS drive shows

                    • 7. Re: Unable to add Disk LUNS for Datastore
                      a.p. Guru
                      vExpertCommunity WarriorsUser Moderators

                      Just to clarify. Is this a new setup, or did it work before you upgraded the systems?

                       

                      The output that you've posted shows 1 additional disk for ESXi-11, and 3 additional disks for ESXi-12. However some of them show up with two partitions, so it seems that they were in use before, which means that the partition table on these disks needs to be cleared, before they can be formatted as VMFS datastores. The Embedded Host Client's GUI offers an otion to do this (Caution: This action is destructive!)

                      To find out what type of partitions the disks currently contain, you may run partedUtil getptbl /dev/disks/<device-name> fore each of the devices (i.e. the results without a partition number ":#" at the end).

                      For ESX-11 - if it has more than one HDD attached - you may need to check the RAID contriller's configuration, and make sure that the disks are presented to the operating system.


                      André

                      • 8. Re: Unable to add Disk LUNS for Datastore
                        insearchof Enthusiast

                        a.p.

                         

                        Thank for the heads up

                         

                         

                        On TGCSESXI-12

                         

                        [root@TGCSESXI-12:/dev/disks] partedUtil getptbl /dev/disks/vml.02000000002000000000000000435431323042

                        gpt

                        14593 255 63 234441648

                        1 2048 6143 381CFCCC728811E092EE000C2911D0B2 vsan 0

                        2 6144 234441614 77719A0CA4A011E3A47E000C29745A24 virsto 0

                        [root@TGCSESXI-12:/dev/disks]

                         

                        [root@TGCSESXI-12:/dev/disks] partedUtil getptbl /dev/disks/vml.02000000002000000000000000435431323042

                        gpt

                        14593 255 63 234441648

                        1 2048 6143 381CFCCC728811E092EE000C2911D0B2 vsan 0

                        2 6144 234441614 77719A0CA4A011E3A47E000C29745A24 virsto 0

                        [root@TGCSESXI-12:/dev/disks] partedUtil delete /dev/disks/vml.02000000002000000000000000435431323042 2

                        [root@TGCSESXI-12:/dev/disks] partedUtil delete /dev/disks/vml.02000000002000000000000000435431323042 1

                        [root@TGCSESXI-12:/dev/disks] ls -l

                        total 6581799136

                        -rw-------    1 root     root     120034123776 Aug 19 23:19 mpx.vmhba0:C0:T0:L0

                        -rw-------    1 root     root     15483273216 Aug 19 23:19 mpx.vmhba32:C0:T0:L0

                        -rw-------    1 root     root       4161536 Aug 19 23:19 mpx.vmhba32:C0:T0:L0:1

                        -rw-------    1 root     root     262127616 Aug 19 23:19 mpx.vmhba32:C0:T0:L0:5

                        -rw-------    1 root     root     262127616 Aug 19 23:19 mpx.vmhba32:C0:T0:L0:6

                        -rw-------    1 root     root     115326976 Aug 19 23:19 mpx.vmhba32:C0:T0:L0:7

                        -rw-------    1 root     root     299876352 Aug 19 23:19 mpx.vmhba32:C0:T0:L0:8

                        -rw-------    1 root     root     2684354560 Aug 19 23:19 mpx.vmhba32:C0:T0:L0:9

                        -rw-------    1 root     root     300000000000 Aug 19 23:19 naa.5000c50012daec7b

                        -rw-------    1 root     root     299432044544 Aug 19 23:19 naa.5000c50012daec7b:1

                        -rw-------    1 root     root     3000592982016 Aug 19 23:19 naa.50014ee20bd195af

                        -rw-------    1 root     root       2097152 Aug 19 23:19 naa.50014ee20bd195af:1

                        -rw-------    1 root     root     3000589819392 Aug 19 23:19 naa.50014ee20bd195af:2

                        lrwxrwxrwx    1 root     root            20 Aug 19 23:19 vml.0000000000766d68626133323a303a30 -> mpx.vmhba32:C0:T0:L0

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:19 vml.0000000000766d68626133323a303a30:1 -> mpx.vmhba32:C0:T0:L0:1

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:19 vml.0000000000766d68626133323a303a30:5 -> mpx.vmhba32:C0:T0:L0:5

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:19 vml.0000000000766d68626133323a303a30:6 -> mpx.vmhba32:C0:T0:L0:6

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:19 vml.0000000000766d68626133323a303a30:7 -> mpx.vmhba32:C0:T0:L0:7

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:19 vml.0000000000766d68626133323a303a30:8 -> mpx.vmhba32:C0:T0:L0:8

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:19 vml.0000000000766d68626133323a303a30:9 -> mpx.vmhba32:C0:T0:L0:9

                        lrwxrwxrwx    1 root     root            19 Aug 19 23:19 vml.02000000002000000000000000435431323042 -> mpx.vmhba0:C0:T0:L0

                        lrwxrwxrwx    1 root     root            20 Aug 19 23:19 vml.02000000005000c50012daec7b535433333030 -> naa.5000c50012daec7b

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:19 vml.02000000005000c50012daec7b535433333030:1 -> naa.5000c50012daec7b:1

                        lrwxrwxrwx    1 root     root            20 Aug 19 23:19 vml.020000000050014ee20bd195af574443205744 -> naa.50014ee20bd195af

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:19 vml.020000000050014ee20bd195af574443205744:1 -> naa.50014ee20bd195af:1

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:19 vml.020000000050014ee20bd195af574443205744:2 -> naa.50014ee20bd195af:2

                        [root@TGCSESXI-12:/dev/disks] partedUtil getptbl /dev/disks/vml.02000000005000c50012daec7b535433333030

                        Error: The backup GPT table is not at the end of the disk, as it should be.  This might mean that another operating system believes the disk is smaller.  Fix, by moving the backup to the end (and removing the old backup)?

                        Warning: Not all of the space available to /dev/disks/naa.5000c50012daec7b appears to be used, you can fix the GPT to use all of the space (an extra 1094236 blocks) or continue with the current setting? This will also move the backup table at the end if is is not at the end already. diskSize (585937500) AlternateLBA (584843263) LastUsableLBA (584843230) NewLastUsableLBA (585937466)

                        gpt

                        36472 255 63 585937500

                        1 2048 584830259 AA31E02A400F11DB9590000C2911D1B8 vmfs 0

                        [root@TGCSESXI-12:/dev/disks] partedUtil getptbl /dev/disks/vml.020000000050014ee20bd195af574443205744

                        gpt

                        364801 255 63 5860533168

                        1 2048 6143 381CFCCC728811E092EE000C2911D0B2 vsan 0

                        2 6144 5860533134 77719A0CA4A011E3A47E000C29745A24 virsto 0

                        [root@TGCSESXI-12:/dev/disks] partedUtil delete /dev/disks/vml.020000000050014ee20bd195af574443205744 2

                        [root@TGCSESXI-12:/dev/disks] partedUtil delete /dev/disks/vml.020000000050014ee20bd195af574443205744 1

                        [root@TGCSESXI-12:/dev/disks] ls -l

                        total 3651533592

                        -rw-------    1 root     root     120034123776 Aug 19 23:26 mpx.vmhba0:C0:T0:L0

                        -rw-------    1 root     root     15483273216 Aug 19 23:26 mpx.vmhba32:C0:T0:L0

                        -rw-------    1 root     root       4161536 Aug 19 23:26 mpx.vmhba32:C0:T0:L0:1

                        -rw-------    1 root     root     262127616 Aug 19 23:26 mpx.vmhba32:C0:T0:L0:5

                        -rw-------    1 root     root     262127616 Aug 19 23:26 mpx.vmhba32:C0:T0:L0:6

                        -rw-------    1 root     root     115326976 Aug 19 23:26 mpx.vmhba32:C0:T0:L0:7

                        -rw-------    1 root     root     299876352 Aug 19 23:26 mpx.vmhba32:C0:T0:L0:8

                        -rw-------    1 root     root     2684354560 Aug 19 23:26 mpx.vmhba32:C0:T0:L0:9

                        -rw-------    1 root     root     300000000000 Aug 19 23:26 naa.5000c50012daec7b

                        -rw-------    1 root     root     299432044544 Aug 19 23:26 naa.5000c50012daec7b:1

                        -rw-------    1 root     root     3000592982016 Aug 19 23:26 naa.50014ee20bd195af

                        lrwxrwxrwx    1 root     root            20 Aug 19 23:26 vml.0000000000766d68626133323a303a30 -> mpx.vmhba32:C0:T0:L0

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:26 vml.0000000000766d68626133323a303a30:1 -> mpx.vmhba32:C0:T0:L0:1

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:26 vml.0000000000766d68626133323a303a30:5 -> mpx.vmhba32:C0:T0:L0:5

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:26 vml.0000000000766d68626133323a303a30:6 -> mpx.vmhba32:C0:T0:L0:6

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:26 vml.0000000000766d68626133323a303a30:7 -> mpx.vmhba32:C0:T0:L0:7

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:26 vml.0000000000766d68626133323a303a30:8 -> mpx.vmhba32:C0:T0:L0:8

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:26 vml.0000000000766d68626133323a303a30:9 -> mpx.vmhba32:C0:T0:L0:9

                        lrwxrwxrwx    1 root     root            19 Aug 19 23:26 vml.02000000002000000000000000435431323042 -> mpx.vmhba0:C0:T0:L0

                        lrwxrwxrwx    1 root     root            20 Aug 19 23:26 vml.02000000005000c50012daec7b535433333030 -> naa.5000c50012daec7b

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:26 vml.02000000005000c50012daec7b535433333030:1 -> naa.5000c50012daec7b:1

                        lrwxrwxrwx    1 root     root            20 Aug 19 23:26 vml.020000000050014ee20bd195af574443205744 -> naa.50014ee20bd195af

                        [root@TGCSESXI-12:/dev/disks] partedUtil delete /dev/disks/vml.02000000005000c50012daec7b535433333030 1

                        Error: The backup GPT table is not at the end of the disk, as it should be.  This might mean that another operating system believes the disk is smaller.  Fix, by moving the backup to the end (and removing the old backup)?

                        Warning: Not all of the space available to /dev/disks/naa.5000c50012daec7b appears to be used, you can fix the GPT to use all of the space (an extra 1094236 blocks) or continue with the current setting? This will also move the backup table at the end if is is not at the end already. diskSize (585937500) AlternateLBA (584843263) LastUsableLBA (584843230) NewLastUsableLBA (585937466)

                        [root@TGCSESXI-12:/dev/disks]

                         

                        One disk I can not delete the partition.

                         

                        The other two I was able to delete partition 1 and 2

                         

                        How do I format them to vmfs?

                         

                         

                        A fresh

                         

                        [root@TGCSESXI-12:/dev/disks] ls -l

                        total 3359119486

                        -rw-------    1 root     root     120034123776 Aug 19 23:38 mpx.vmhba0:C0:T0:L0

                        -rw-------    1 root     root     15483273216 Aug 19 23:38 mpx.vmhba32:C0:T0:L0

                        -rw-------    1 root     root       4161536 Aug 19 23:38 mpx.vmhba32:C0:T0:L0:1

                        -rw-------    1 root     root     262127616 Aug 19 23:38 mpx.vmhba32:C0:T0:L0:5

                        -rw-------    1 root     root     262127616 Aug 19 23:38 mpx.vmhba32:C0:T0:L0:6

                        -rw-------    1 root     root     115326976 Aug 19 23:38 mpx.vmhba32:C0:T0:L0:7

                        -rw-------    1 root     root     299876352 Aug 19 23:38 mpx.vmhba32:C0:T0:L0:8

                        -rw------- 1 root root 2684354560 Aug 19 23:38 mpx.vmhba32:C0:T0:L0:9

                        -rw-------    1 root     root     300000000000 Aug 19 23:38 naa.5000c50012daec7b

                        -rw------- 1 root root 3000592982016 Aug 19 23:38 naa.50014ee20bd195af

                        lrwxrwxrwx    1 root     root            20 Aug 19 23:38 vml.0000000000766d68626133323a303a30 -> mpx.vmhba32:C0:T0:L0

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:38 vml.0000000000766d68626133323a303a30:1 -> mpx.vmhba32:C0:T0:L0:1

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:38 vml.0000000000766d68626133323a303a30:5 -> mpx.vmhba32:C0:T0:L0:5

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:38 vml.0000000000766d68626133323a303a30:6 -> mpx.vmhba32:C0:T0:L0:6

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:38 vml.0000000000766d68626133323a303a30:7 -> mpx.vmhba32:C0:T0:L0:7

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:38 vml.0000000000766d68626133323a303a30:8 -> mpx.vmhba32:C0:T0:L0:8

                        lrwxrwxrwx    1 root     root            22 Aug 19 23:38 vml.0000000000766d68626133323a303a30:9 -> mpx.vmhba32:C0:T0:L0:9

                        lrwxrwxrwx    1 root     root            19 Aug 19 23:38 vml.02000000002000000000000000435431323042 -> mpx.vmhba0:C0:T0:L0

                        lrwxrwxrwx    1 root     root            20 Aug 19 23:38 vml.02000000005000c50012daec7b535433333030 -> naa.5000c50012daec7b

                        lrwxrwxrwx    1 root     root            20 Aug 19 23:38 vml.020000000050014ee20bd195af574443205744 -> naa.50014ee20bd195af

                        [root@TGCSESXI-12:/dev/disks]

                         

                        No partitions now

                        • 9. Re: Unable to add Disk LUNS for Datastore
                          insearchof Enthusiast

                          Also on TGCSESXI-12

                           

                          My SSD drive had several partitions.

                           

                          [root@TGCSESXI-12:/dev/disks] ls -l

                          total 3359119486

                          -rw-------    1 root     root     120034123776 Aug 19 23:38 mpx.vmhba0:C0:T0:L0

                          -rw-------    1 root     root     15483273216 Aug 19 23:38 mpx.vmhba32:C0:T0:L0

                          -rw-------    1 root     root       4161536 Aug 19 23:38 mpx.vmhba32:C0:T0:L0:1

                          -rw-------    1 root     root     262127616 Aug 19 23:38 mpx.vmhba32:C0:T0:L0:5

                          -rw-------    1 root     root     262127616 Aug 19 23:38 mpx.vmhba32:C0:T0:L0:6

                          -rw-------    1 root     root     115326976 Aug 19 23:38 mpx.vmhba32:C0:T0:L0:7

                          -rw-------    1 root     root     299876352 Aug 19 23:38 mpx.vmhba32:C0:T0:L0:8

                          -rw------- 1 root root 2684354560 Aug 19 23:38 mpx.vmhba32:C0:T0:L0:9

                          -rw-------    1 root     root     300000000000 Aug 19 23:38 naa.5000c50012daec7b

                          -rw------- 1 root root 3000592982016 Aug 19 23:38 naa.50014ee20bd195af

                          lrwxrwxrwx    1 root     root            20 Aug 19 23:38 vml.0000000000766d68626133323a303a30 -> mpx.vmhba32:C0:T0:L0

                          lrwxrwxrwx    1 root     root            22 Aug 19 23:38 vml.0000000000766d68626133323a303a30:1 -> mpx.vmhba32:C0:T0:L0:1

                          lrwxrwxrwx    1 root     root            22 Aug 19 23:38 vml.0000000000766d68626133323a303a30:5 -> mpx.vmhba32:C0:T0:L0:5

                          lrwxrwxrwx    1 root     root            22 Aug 19 23:38 vml.0000000000766d68626133323a303a30:6 -> mpx.vmhba32:C0:T0:L0:6

                          lrwxrwxrwx    1 root     root            22 Aug 19 23:38 vml.0000000000766d68626133323a303a30:7 -> mpx.vmhba32:C0:T0:L0:7

                          lrwxrwxrwx    1 root     root            22 Aug 19 23:38 vml.0000000000766d68626133323a303a30:8 -> mpx.vmhba32:C0:T0:L0:8

                          lrwxrwxrwx    1 root     root            22 Aug 19 23:38 vml.0000000000766d68626133323a303a30:9 -> mpx.vmhba32:C0:T0:L0:9

                          lrwxrwxrwx    1 root     root            19 Aug 19 23:38 vml.02000000002000000000000000435431323042 -> mpx.vmhba0:C0:T0:L0

                          lrwxrwxrwx    1 root     root            20 Aug 19 23:38 vml.02000000005000c50012daec7b535433333030 -> naa.5000c50012daec7b

                          lrwxrwxrwx    1 root     root            20 Aug 19 23:38 vml.020000000050014ee20bd195af574443205744 -> naa.50014ee20bd195af

                          [root@TGCSESXI-12:/dev/disks] partedUtil getptbl /dev/disks/vml.0000000000766d68626133323a303a30

                          gpt

                          1882 255 63 30240768

                          1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128

                          5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

                          6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

                          7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0

                          8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0

                          9 1843200 7086079 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0

                          [root@TGCSESXI-12:/dev/disks] partedUtil delete /dev/disks/vml.0000000000766d68626133323a303a30 9

                          Error: Read-only file system during write on /dev/disks/mpx.vmhba32:C0:T0:L0

                          Unable to delete partition 9 from device /dev/disks/vml.0000000000766d68626133323a303a30

                            

                          [root@TGCSESXI-12:/dev/disks] partedUtil delete /dev/disks/vml.0000000000766d68626133323a303a30 8

                          [root@TGCSESXI-12:/dev/disks] partedUtil delete /dev/disks/vml.0000000000766d68626133323a303a30 7

                          [root@TGCSESXI-12:/dev/disks] partedUtil delete /dev/disks/vml.0000000000766d68626133323a303a30 6

                          [root@TGCSESXI-12:/dev/disks] partedUtil delete /dev/disks/vml.0000000000766d68626133323a303a30 5

                          [root@TGCSESXI-12:/dev/disks] partedUtil delete /dev/disks/vml.0000000000766d68626133323a303a30 1

                          [root@TGCSESXI-12:/dev/disks] ls -l

                          total 3358197982

                          -rw-------    1 root     root     120034123776 Aug 19 23:54 mpx.vmhba0:C0:T0:L0

                          -rw-------    1 root     root     15483273216 Aug 19 23:54 mpx.vmhba32:C0:T0:L0

                          -rw-------    1 root     root     2684354560 Aug 19 23:54 mpx.vmhba32:C0:T0:L0:9

                          -rw-------    1 root     root     300000000000 Aug 19 23:54 naa.5000c50012daec7b

                          -rw-------    1 root     root     3000592982016 Aug 19 23:54 naa.50014ee20bd195af

                          lrwxrwxrwx    1 root     root            20 Aug 19 23:54 vml.0000000000766d68626133323a303a30 -> mpx.vmhba32:C0:T0:L0

                          lrwxrwxrwx    1 root     root            22 Aug 19 23:54 vml.0000000000766d68626133323a303a30:9 -> mpx.vmhba32:C0:T0:L0:9

                          lrwxrwxrwx    1 root     root            19 Aug 19 23:54 vml.02000000002000000000000000435431323042 -> mpx.vmhba0:C0:T0:L0

                          lrwxrwxrwx    1 root     root            20 Aug 19 23:54 vml.02000000005000c50012daec7b535433333030 -> naa.5000c50012daec7b

                          lrwxrwxrwx    1 root     root            20 Aug 19 23:54 vml.020000000050014ee20bd195af574443205744 -> naa.50014ee20bd195af

                          [root@TGCSESXI-12:/dev/disks]

                           

                           

                          Unable to delete 9

                          • 10. Re: Unable to add Disk LUNS for Datastore
                            a.p. Guru
                            User ModeratorsCommunity WarriorsvExpert

                            My SSD drive had several partitions.

                            In case this is (was) the ESXi installation, the partitions are (were) as expected. The discussion so far was about the additional HDDs, so there was no need to delete the partitions on the SSDs. You may now have to reinstall ESXi on the hosts.

                            Btw. as mentioned earlier, cleaning up partition tables (i.e. deleting all partiions on a disk) can be done from the GUI. Simply select the device in Storage -> Devices, and then use "Clean Partition Table" from the available "Actions".


                            André

                            • 11. Re: Unable to add Disk LUNS for Datastore
                              insearchof Enthusiast

                              Andre

                               

                              Sorry I should have given you a little more back ground on this.

                               

                              I had 9 ESXI hosts running ESXI 6.5 on various Dell PowerEdge Servers. after trying to get VSAN to work I found that the Dell Power Edge Servers I had did not support ESXI 6.5

                               

                              So last month  upgraded my entire infrastructure to Dell PowerEdge R430 GEN 13  and installed Dell's VMware ESXI 6.5 U2

                               

                              I took all the drives out of my original ESXI hosts and placed them into my new ESXI Hosts.

                               

                               

                              I built all the esxi host without any drives installed I added them hot after I switched out the old esxi hosts. I installed esxi on a usb drive

                               

                              All the drives were a data store and some were a vsan data store   the SSD drives were part of the VSAN configuration.

                               

                               

                              any ideas

                              • 12. Re: Unable to add Disk LUNS for Datastore
                                a.p. Guru
                                Community WarriorsUser ModeratorsvExpert

                                Ok that explains it.

                                What I would probably do now, is to boot the hosts using the gParted Live CD/ISO, and clean all the disks' partition tables.

                                What may also be worth doing, is to check the RAID controller configuration to see whether all the disks are configured/presented as expected.

                                 

                                André

                                • 13. Re: Unable to add Disk LUNS for Datastore
                                  insearchof Enthusiast

                                  Andre

                                   

                                  I setup a cd with gparted Live  put I drive in the server and found it was clean so I added to one of my esxi hosts and it was seen.

                                   

                                  That's good news.

                                   

                                  Now I need to pull out all the drives with the issue and run it thru gparted.

                                   

                                  This will take a few days

                                   

                                  I will post results

                                  • 14. Re: Unable to add Disk LUNS for Datastore
                                    insearchof Enthusiast

                                    All Drives are now data stores

                                     

                                    Had to re configure the raid controllers had foreign drives etc.

                                     

                                    Also had to order some replacement drives.

                                     

                                    All good now.

                                     

                                    This one can be marked as resolved