Page 1 of 3 123 LastLast
Results 1 to 10 of 28

Thread: Ubuntu server 20.04.1 parition errors

  1. #1
    Join Date
    Jun 2015
    Beans
    20

    Unhappy Ubuntu server 20.04.1 parition errors

    HI, I have installed Ubuntu 20.04.1 on VMWare ESXi. It has 2 disks - one HDD of 100 GB and one SSD of 360 GB. I am able to see the SSD correctly.

    However, for the HDD I am able to see the following:
    Code:
    sda                         8:0    0   100G  0 disk
    ├─sda1                      8:1    0   512M  0 part /boot/efi
    ├─sda2                      8:2    0     1G  0 part /boot
    └─sda3                      8:3    0  98.5G  0 part
      └─ubuntu--vg-ubuntu--lv 253:0    0  49.3G  0 lvm  /

    I am also getting following errors in syslog:


    Code:
    Aug  1 09:33:34 hostname multipathd[799]: sdb: failed to get sgio uid: No such file or directory
    Aug  1 09:33:38 hostname multipathd[799]: sda: add missing path
    Aug  1 09:33:38 hostname multipathd[799]: sda: failed to get udev uid: Invalid argument
    Aug  1 09:33:38 hostname multipathd[799]: sda: failed to get sysfs uid: Invalid argument
    Aug  1 09:33:38 hostname multipathd[799]: sda: failed to get sgio uid: No such file or directory
    Aug  1 09:33:39 hostname multipathd[799]: sdb: add missing path
    Aug  1 09:33:39 hostname multipathd[799]: sdb: failed to get udev uid: Invalid argument
    Aug  1 09:33:39 hostname multipathd[799]: sdb: failed to get sysfs uid: Invalid argument
    Aug  1 09:33:39 hostname multipathd[799]: sdb: failed to get sgio uid: No such file or directory
    Aug  1 09:33:43 hostname multipathd[799]: sda: add missing path
    Aug  1 09:33:43 hostname multipathd[799]: sda: failed to get udev uid: Invalid argument
    Aug  1 09:33:43 hostname multipathd[799]: sda: failed to get sysfs uid: Invalid argument
    Aug  1 09:33:43 hostname multipathd[799]: sda: failed to get sgio uid: No such file or directory
    Aug  1 09:33:44 hostname multipathd[799]: sdb: add missing path
    Aug  1 09:33:44 hostname multipathd[799]: sdb: failed to get udev uid: Invalid argument
    Aug  1 09:33:44 hostname multipathd[799]: sdb: failed to get sysfs uid: Invalid argument
    Aug  1 09:33:44 hostname multipathd[799]: sdb: failed to get sgio uid: No such file or directory
    Aug  1 09:33:48 hostname multipathd[799]: sda: add missing path
    Aug  1 09:33:48 hostname multipathd[799]: sda: failed to get udev uid: Invalid argument
    Aug  1 09:33:48 hostname multipathd[799]: sda: failed to get sysfs uid: Invalid argument
    Aug  1 09:33:48 hostname multipathd[799]: sda: failed to get sgio uid: No such file or directory

    What am I doing wrong? How do I resolve this?

    Thank you.
    Last edited by Parth_Maniar; August 5th, 2020 at 10:30 AM.

  2. #2
    Join Date
    Nov 2009
    Location
    Catalunya, Spain
    Beans
    14,447
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Ubuntu server 20.04.1 parition errors

    It looks like it is complaining about multipath setup or paths. I assume this is related to multipath in VMware where you can have redundancy to reach the datastores through different paths and that way allow the VMs to continue working if one path goes down.

    Have you googled those messages from the syslog? Anything interesting in the search results?

    On the HDD partition layout I see nothing strange. I don't know if it is what you expected though. You have a EFI partition and what looks like bios_grub partitions. The rest of the 100GB is one single VG which is normal for a guided setup using LVM.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 18.04 LTS 64bit

  3. #3
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    21,616
    Distro
    Ubuntu Mate 16.04 Xenial Xerus

    Re: Ubuntu server 20.04.1 parition errors

    Which disk controller does the VM present to Ubuntu? For most VMs today, using the virtio controller is the best choice - fastest and with the lowest overhead. Alas, we dropped all ESX stuff around 2011 due to VMware management decisions that we and our clients couldn't take, so my VMware knowledge is dated.

    BTW, would help to make output more readable if enclosed in "code tags" when posting here. Especially the lsblk and df -Th output normally needed to troubleshoot storage stuff.

    I've never used efi booting with any virtual machine. For a long time, efi support wasn't very good, so I just never got into the habit.

    Looks like https://bugs.launchpad.net/ubuntu/+s...s/+bug/1875594 is related and there is a proposed fix in a PPA. Post #17 suggests blacklisting the VMware disk drivers - some issue with the VMware SCSI vdisk stuff.

  4. #4
    Join Date
    Jun 2015
    Beans
    20

    Re: Ubuntu server 20.04.1 parition errors

    Quote Originally Posted by TheFu View Post
    Which disk controller does the VM present to Ubuntu? For most VMs today, using the virtio controller is the best choice - fastest and with the lowest overhead. Alas, we dropped all ESX stuff around 2011 due to VMware management decisions that we and our clients couldn't take, so my VMware knowledge is dated.

    BTW, would help to make output more readable if enclosed in "code tags" when posting here. Especially the lsblk and df -Th output normally needed to troubleshoot storage stuff.

    I've never used efi booting with any virtual machine. For a long time, efi support wasn't very good, so I just never got into the habit.

    Looks like https://bugs.launchpad.net/ubuntu/+s...s/+bug/1875594 is related and there is a proposed fix in a PPA. Post #17 suggests blacklisting the VMware disk drivers - some issue with the VMware SCSI vdisk stuff.
    Hi, thank you very much for your reply.

    Please find the required logs.

    Code:
    NAME                      MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
    loop0                       7:0    0   9.1M  1 loop /snap/canonical-livepatch/95
    loop1                       7:1    0    15M  1 loop /snap/aws-cli/130
    loop2                       7:2    0 118.7M  1 loop /snap/google-cloud-sdk/143
    loop3                       7:3    0  59.6M  1 loop /snap/powershell/137
    loop4                       7:4    0    55M  1 loop /snap/core18/1880
    loop5                       7:5    0  71.3M  1 loop /snap/lxd/16100
    loop6                       7:6    0    97M  1 loop /snap/core/9665
    loop7                       7:7    0   3.5M  1 loop /snap/stress-ng/4462
    loop8                       7:8    0  27.1M  1 loop /snap/snapd/7264
    loop9                       7:9    0    55M  1 loop /snap/core18/1705
    loop10                      7:10   0    69M  1 loop /snap/lxd/14804
    loop11                      7:11   0  29.9M  1 loop /snap/snapd/8542
    sda                         8:0    0   100G  0 disk
    ├─sda1                      8:1    0   512M  0 part /boot/efi
    ├─sda2                      8:2    0     1G  0 part /boot
    └─sda3                      8:3    0  98.5G  0 part
      └─ubuntu--vg-ubuntu--lv 253:0    0  49.3G  0 lvm  /
    sdb                         8:16   0   360G  0 disk /mnt/ssd
    and


    Code:
    Filesystem                        Type      Size  Used Avail Use% Mounted on
    udev                              devtmpfs  2.9G     0  2.9G   0% /dev
    tmpfs                             tmpfs     595M  1.3M  594M   1% /run
    /dev/mapper/ubuntu--vg-ubuntu--lv ext4       49G   11G   36G  22% /
    tmpfs                             tmpfs     3.0G     0  3.0G   0% /dev/shm
    tmpfs                             tmpfs     5.0M     0  5.0M   0% /run/lock
    tmpfs                             tmpfs     3.0G     0  3.0G   0% /sys/fs/cgroup
    /dev/sdb                          ext4      354G  5.4G  330G   2% /mnt/ssd
    /dev/sda2                         ext4      976M  104M  805M  12% /boot
    /dev/loop1                        squashfs   15M   15M     0 100% /snap/aws-cli/130
    /dev/loop2                        squashfs  119M  119M     0 100% /snap/google-cloud-sdk/143
    /dev/loop0                        squashfs  9.2M  9.2M     0 100% /snap/canonical-livepatch/95
    /dev/loop3                        squashfs   60M   60M     0 100% /snap/powershell/137
    /dev/loop4                        squashfs   55M   55M     0 100% /snap/core18/1880
    /dev/loop7                        squashfs  3.7M  3.7M     0 100% /snap/stress-ng/4462
    /dev/loop8                        squashfs   28M   28M     0 100% /snap/snapd/7264
    /dev/loop11                       squashfs   30M   30M     0 100% /snap/snapd/8542
    /dev/sda1                         vfat      511M  7.8M  504M   2% /boot/efi
    /dev/loop5                        squashfs   72M   72M     0 100% /snap/lxd/16100
    /dev/loop9                        squashfs   55M   55M     0 100% /snap/core18/1705
    /dev/loop6                        squashfs   97M   97M     0 100% /snap/core/9665
    /dev/loop10                       squashfs   69M   69M     0 100% /snap/lxd/14804
    tmpfs                             tmpfs     595M     0  595M   0% /run/user/1000

    I hope this helps. I am concerned that the disk provisioned is 100 GB but I am only able to see 49 GB for / . I am unsure where the remaining 50 GB is.
    Last edited by Parth_Maniar; August 5th, 2020 at 10:17 AM.

  5. #5
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    21,616
    Distro
    Ubuntu Mate 16.04 Xenial Xerus

    Re: Ubuntu server 20.04.1 parition errors

    code tags?

    Did you follow that link and do what they say?

  6. #6
    Join Date
    Jun 2015
    Beans
    20

    Re: Ubuntu server 20.04.1 parition errors

    Quote Originally Posted by darkod View Post
    It looks like it is complaining about multipath setup or paths. I assume this is related to multipath in VMware where you can have redundancy to reach the datastores through different paths and that way allow the VMs to continue working if one path goes down.

    Have you googled those messages from the syslog? Anything interesting in the search results?

    On the HDD partition layout I see nothing strange. I don't know if it is what you expected though. You have a EFI partition and what looks like bios_grub partitions. The rest of the 100GB is one single VG which is normal for a guided setup using LVM.

    Hi, thank you very much for you reply.


    I found 4 threads with same error and I have tried their solutions but in my case the error doesn't stop. I am worried about the logs filling up to be honest.

    https://askubuntu.com/questions/1242...-configuration
    https://ubuntuforums.org/showthread.php?t=2441797
    https://www.suse.com/support/kb/doc/?id=000016951
    https://internet-lab.ru/vmware_linux...o_get_udev_uid (russian)



  7. #7
    Join Date
    Jun 2015
    Beans
    20

    Re: Ubuntu server 20.04.1 parition errors

    Quote Originally Posted by TheFu View Post
    code tags?

    Did you follow that link and do what they say?

    Hi, sorry I did not do this yet. Let me do this and reply. Could you tell me how to best deal with expanding the disk size too? In case I need to reboot or take downtime for the VM. Why is the HDD size 50 GB instead of 100 GB?

    Thank you.

  8. #8
    Join Date
    Nov 2009
    Location
    Catalunya, Spain
    Beans
    14,447
    Distro
    Ubuntu 18.04 Bionic Beaver

    Re: Ubuntu server 20.04.1 parition errors

    With LVM you probably have the remaining free space inside the VG but not assigned to any LV yet. If you don't know what LVM is I wouldn't install a production server/VM before reading up on it.

    You can see the VG assigned/free space with:
    Code:
    sudo vgdisplay
    When posting output results please include them inside [code] tags like TheFu mentioned already. It keeps the formatting and makes the output easily readable.
    Last edited by darkod; August 1st, 2020 at 09:51 PM.
    Darko.
    -----------------------------------------------------------------------
    Ubuntu 18.04 LTS 64bit

  9. #9
    Join Date
    Mar 2010
    Location
    Squidbilly-Land
    Beans
    21,616
    Distro
    Ubuntu Mate 16.04 Xenial Xerus

    Re: Ubuntu server 20.04.1 parition errors

    Hopefully, the OP knows all about LVM. The current commands we like are
    Code:
    sudo pvs
    sudo vgs
    sudo lvs
    The output from the older lv/vg/pv-display commands is seldom needed unless there is a deep issue.

    The issue here is at a lower level, well below LVM. Unless the OP tried to resize the LV, the first "root" LV should take up the entire VG and PV. Personally, I think that is a huge mistake and I always resize my root LV to be 25G so it isn't wasted on useless stuff and for security. But everyone is different. For people really new to Linux and LVM and volume management, non-trivial storage setups are usually fine, until they learn more and understand why those are a bad idea.

    IMHO.

  10. #10
    Join Date
    Jun 2015
    Beans
    20

    Re: Ubuntu server 20.04.1 parition errors

    Hi, I apologise for not formatting earlier posts. I have edited the one allowed by the system.

    Code:
      --- Volume group ---
      VG Name               ubuntu-vg
      System ID
      Format                lvm2
      Metadata Areas        1
      Metadata Sequence No  2
      VG Access             read/write
      VG Status             resizable
      MAX LV                0
      Cur LV                1
      Open LV               1
      Max PV                0
      Cur PV                1
      Act PV                1
      VG Size               <98.50 GiB
      PE Size               4.00 MiB
      Total PE              25215
      Alloc PE / Size       12608 / 49.25 GiB
      Free  PE / Size       12607 / <49.25 GiB
      VG UUID               ji4eP9-Wal5-BQRo-Qijk-wIIi-LcHt-pqkDej

    I am not an administrator for Ubuntu and my knowledge is limited when deploying Ubuntu server of ESXi. This is not in production for a company. This is part of my final year project in university where I'm trying to capture logs using ELK stack and map cyberattack patterns around the world.

    I have deployed VMs using VMWare workstation and never faced issue even when thin provisioning a disk.

    Continuous error logs have stopped after following guide here https://www.suse.com/support/kb/doc/?id=000016951 and settings within comments here: https://askubuntu.com/questions/1242...-configuration

    Code:
    after I added "blacklist { devnode "sda" }"  to /etc/multipath.conf the entries in syslog disapeared. I am still  wondering why multipath is enabled by default.
    Reboot of the VM is required.

    Thank you for everyone's assistance.

Page 1 of 3 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •