ESXi

 View Only

Raw Device Mapping not working

  • 1.  Raw Device Mapping not working

    Posted Nov 19, 2017 08:53 PM

    Hi,

    I am trying to attach my existing disk with data on my Microserver Gen8 to Esxi 6.5 using RDM.

    [root@localhost:~] ls -l /vmfs/devices/disks

    -rw-------    1 root     root     3000559427584 Nov 19 19:38 naa.600508b1001c9cddfce6b89c5f430aed

    -rw-------    1 root     root     3000591450112 Nov 19 19:38 naa.600508b1001c9cddfce6b89c5f430aed:1

    [root@localhost:~] vmkfstools -z /vmfs/devices/disks/naa.600508b1001c9cddfce6b89c5f430aed /vmfs/volumes/Vmware-SSD/RDM/localrdm1.vmdk

    I added this disk to the Virtual Machine, Ubuntu 16.04.

    dmesg:

    [    1.797072] sd 32:0:1:0: [sdb] 5860467632 512-byte logical blocks: (3.00 TB/2.73 TiB)

    [    1.797077] sd 32:0:1:0: [sdb] 4096-byte physical blocks

    [    1.797991] sd 32:0:1:0: [sdb] Write Protect is off

    [    1.797995] sd 32:0:1:0: [sdb] Mode Sense: 73 00 00 08

    [    1.798386] sd 32:0:1:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA

    [    1.834024] sd 32:0:1:0: [sdb] Attached SCSI disk

    @ubuntu:~$ lsblk

    NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT

    sda      8:0    0 29.5G  0 disk

    ├─sda1   8:1    0 27.8G  0 part /

    ├─sda2   8:2    0    1K  0 part

    └─sda5   8:5    0  1.8G  0 part [SWAP]

    sdb      8:16   0  2.7T  0 disk

    sr0     11:0    1 1024M  0 rom

    OK, it's recognised.

    At this point I tried to mount /dev/sdb1, which is not worked.

    @ubuntu:~$ sudo fsck.ext4 /dev/sdb

    e2fsck 1.42.13 (17-May-2015)

    ext2fs_open2: Bad magic number in super-block

    fsck.ext4: Superblock invalid, trying backup blocks...

    fsck.ext4: Bad magic number in super-block while trying to open /dev/sdb

    The superblock could not be read or does not describe a valid ext2/ext3/ext4

    filesystem.  If the device is valid and it really contains an ext2/ext3/ext4

    filesystem (and not swap or ufs or something else), then the superblock

    is corrupt, and you might try running e2fsck with an alternate superblock:

        e2fsck -b 8193 <device>

    or

        e2fsck -b 32768 <device>

    What the heck?

    @ubuntu:~$ sudo fdisk -l

    Disk /dev/sda: 29.5 GiB, 31679578112 bytes, 61874176 sectors

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 512 bytes

    I/O size (minimum/optimal): 512 bytes / 512 bytes

    Disklabel type: dos

    Disk identifier: 0x69a5863d

    Device     Boot    Start      End  Sectors  Size Id Type

    /dev/sda1  *         128 58202239 58202112 27.8G 83 Linux

    /dev/sda2       58202240 61870335  3668096  1.8G  5 Extended

    /dev/sda5       58202368 61870335  3667968  1.8G 82 Linux swap / Solaris

    Disk /dev/sdb: 2.7 TiB, 3000559427584 bytes, 5860467632 sectors

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 4096 bytes

    I/O size (minimum/optimal): 262144 bytes / 262144 bytes

    Disklabel type: dos

    Disk identifier: 0x0a37a706

    Device     Boot Start        End    Sectors Size Id Type

    /dev/sdb1           1 4294967295 4294967295   2T ee GPT

    Partition 1 does not start on physical sector boundary.

    -------------------------------------------------------------------------------------------

    @ubuntu:~$ sudo gdisk -l /dev/sdb

    GPT fdisk (gdisk) version 1.0.1

    Warning! Disk size is smaller than the main header indicates! Loading

    secondary header from the last sector of the disk! You should use 'v' to

    verify disk integrity, and perhaps options on the experts' menu to repair

    the disk.

    Caution: invalid backup GPT header, but valid main header; regenerating

    backup header from main header.

    Warning! One or more CRCs don't match. You should repair the disk!

    Partition table scan:

      MBR: protective

      BSD: not present

      APM: not present

      GPT: damaged

    ****************************************************************************

    Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk

    verification and recovery are STRONGLY recommended.

    ****************************************************************************

    Disk /dev/sdb: 5860467632 sectors, 2.7 TiB

    Logical sector size: 512 bytes

    Disk identifier (GUID): 6CA438F7-2EEB-4739-9340-6AE82353D246

    Partition table holds up to 128 entries

    First usable sector is 34, last usable sector is 5860533134

    Partitions will be aligned on 2048-sector boundaries

    Total free space is 2925 sectors (1.4 MiB)

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

       1            2048      5860532223   2.7 TiB     8300  primary

    ---------------------------------------------------------------------------------------------------------

    At this moment I placed HDD back to my old machine and it's working instantly:

    @ubuntu:~$ sudo fdisk -l /dev/sdb

    Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors

    Units: sectors of 1 * 512 = 512 bytes

    Sector size (logical/physical): 512 bytes / 4096 bytes

    I/O size (minimum/optimal): 4096 bytes / 4096 bytes

    Disklabel type: gpt

    Disk identifier: 6CA438F7-2EEB-4739-9340-6AE82353D246

    Device     Start        End    Sectors  Size Type

    /dev/sdb1   2048 5860532223 5860530176  2.7T Linux filesystem

    Anybody knows the answer, what can be the problem?