Hi everyone
When UCS starts the following error appears
Begin: Mouting root file system ...
Begin: Ruinning / scripts / local-top ... "disk / by-uuid / faaaeee8-03b0-4848-aeb8-e9d2beff0f87": Invalid path for Logical Volume.
The curious thing is that it starts normally and the root volume is not LVM.
What can I do to correct this error at startup?
OBS, checking / etc / fstab I notice that the reference is correct.
Best Regards,
Michael Voigt
Hey,
try searching for that UUID:
grep -r -i faaaeee8-03b0-4848-aeb8-e9d2beff0f87 /etc
ucr search --value faaaeee8-03b0-4848-aeb8-e9d2beff0f87
Maybe that’ll shed some light.
Kind regards
mosu
Hey,
in /etc/fstab it is present
it is pointing correctly to root partition
It happens that root partition is not lvm
Look…
root @ server: ~ # lsblk
NAME MAJ: MIN RM SIZE RO TYPE MOUNTPOINT
sda 8: 0 0 1.8T 0 disk
├─sda1 8: 1 0 953M 0 part /boot
├─sda2 8: 2 0 1K 0 part
├─sda5 8: 5 0 14.9G 0 part [SWAP]
├─sda6 8: 6 0 139.7G 0 part /
└─sda7 8: 7 0 1.7T 0 part
└─vg_engel-lv_home 254: 0 0 1.7T 0 lvm /home
sr0 11: 0 1 1024M 0 rom
What do you think?
Best regards,
Michael Voigt
Hi,
please post
lvdisplay -v
cat /etc/fstab
root@servidor:~# lsblk -o +uuid
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT UUID
sda 8:0 0 1.8T 0 disk
├─sda1 8:1 0 953M 0 part /boot 1ea08d39-136d-4e7e-b70c-5f052a99485b
├─sda2 8:2 0 1K 0 part
├─sda5 8:5 0 14.9G 0 part [SWAP] c5bc1c74-17df-4d38-a5a4-0343101175c3
├─sda6 8:6 0 139.7G 0 part / faaaeee8-03b0-4848-aeb8-e9d2beff0f87
└─sda7 8:7 0 1.7T 0 part 0sx16Q-VYeN-ht4l-UoAO-IZBl-uQU1-zfp2Ma
└─vg_engel-lv_home 254:0 0 1.7T 0 lvm /home e16edd23-c6e9-41a4-bd51-b40a346f7e51
sr0 11:0 1 1024M 0 rom
root@servidor:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda6 during installation
UUID=faaaeee8-03b0-4848-aeb8-e9d2beff0f87 / ext4 errors=remount-ro,user_xattr 0 1
# /boot was on /dev/sda1 during installation
UUID=1ea08d39-136d-4e7e-b70c-5f052a99485b /boot ext4 defaults,user_xattr 0 2
/dev/mapper/vg_engel-lv_home /home ext4 defaults,user_xattr 0 2
# swap was on /dev/sda5 during installation
UUID=c5bc1c74-17df-4d38-a5a4-0343101175c3 none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
root@servidor:~# lvdisplay -v
--- Logical volume ---
LV Path /dev/vg_engel/lv_home
LV Name lv_home
VG Name vg_engel
LV UUID 9PuLgm-6r5g-T6cd-JLml-PWsu-XKZi-EaVp6X
LV Write Access read/write
LV Creation host, time unassigned-hostname, 2018-09-18 15:41:32 -0300
LV Status available
# open 1
LV Size 1.67 TiB
Current LE 436854
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0
Hi
see the error at the beginning
Best Regards,
Michael Voigt
Hi,
A few days ago I installed on a server identical to this one and I did not have that problem.
Now I decided to reinstall and changed the partition scheme
In the new scenario, it looks like this:
root@servidor:~# lvdisplay -v
--- Logical volume ---
LV Path /dev/vg_engel/lv_swap
LV Name lv_swap
VG Name vg_engel
LV UUID vzciva-jScI-Zn9P-y2Zs-ioDX-4Eck-UyNsvO
LV Write Access read/write
LV Creation host, time unassigned-hostname, 2018-09-20 17:37:48 -0300
LV Status available
# open 2
LV Size 14.90 GiB
Current LE 3814
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:0
--- Logical volume ---
LV Path /dev/vg_engel/lv_root
LV Name lv_root
VG Name vg_engel
LV UUID vZNSv2-LZ7a-hU0h-TpHO-EUm8-NKL0-7M2aDy
LV Write Access read/write
LV Creation host, time unassigned-hostname, 2018-09-20 17:39:17 -0300
LV Status available
# open 1
LV Size 93.13 GiB
Current LE 23841
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:1
--- Logical volume ---
LV Path /dev/vg_engel/lv_home
LV Name lv_home
VG Name vg_engel
LV UUID CCQNfL-i1to-CcuC-WGAr-xpZm-pzjf-zrWsIq
LV Write Access read/write
LV Creation host, time unassigned-hostname, 2018-09-20 17:39:29 -0300
LV Status available
# open 1
LV Size 1.71 TiB
Current LE 448777
Segments 1
Allocation inherit
Read ahead sectors auto
- currently set to 256
Block device 254:2
root@servidor:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/vg_engel-lv_root / ext4 errors=remount-ro,user_xattr 0 1
# /boot was on /dev/sda1 during installation
UUID=536e0a8e-93e9-44d5-ae14-12859a793ee9 /boot ext2 defaults,user_xattr 0 2
/dev/mapper/vg_engel-lv_home /home ext4 defaults,user_xattr 0 2
/dev/mapper/vg_engel-lv_swap none swap sw 0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
The error still persists, as /var/log/boot.log
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
WARNING: Failed to connect to lvmetad. Falling back to device scanning.
/dev/mapper/vg_engel-lv_root: recovering journal
/dev/mapper/vg_engel-lv_root: clean, 167801/12218000 files, 1787936/24412160 blocks
[ 8.146139] quota-initial-check.sh[840]: Checking quotas...done.
[ OK ] Stopped LSB: Univention iptables --wait configuration.
Starting LSB: Univention iptables --wait configuration...
[ OK ] Started LSB: Univention S4 Connector.
[ OK ] Started LSB: Univention Management Console Web Server.
Starting The Apache HTTP Server...
[ OK ] Started BIND Domain Name Server with samba4 backend.
[ OK ] Reached target Host and Network Name Lookups.
Starting LSB: DHCP server...
Starting Postfix Mail Transport Agent (instance -)...
[ OK ] Started Nagios Remote Plugin Executor.
Starting LSB: nagios host/service/network monitoring and management system...
Starting LSB: DHCP server...
[ OK ] Started LSB: DHCP server.
[ OK ] Started The Apache HTTP Server.
Starting Starting univention-welcome screen...
[ OK ] Started Starting univention-welcome screen.
Starting Terminate Plymouth Boot Screen...
Despite the error, it works fine, but this unexpected error is strange because I have not had it on another identical server.
The equipment is Dell T330 with PERC controller in Raid10
What do you think?
Best regards,
Michael Voigt
This is a totally different message now.
For the first one I assume the root-device is somehow coded in the Grub entries and therefore not found. I guess there might have been changes for some reason.
Anyways, the second is, as written there, just a WARNING, not an ERROR. So it is totally fine. Just ignore them.
/CV
Hi,
After reading a lot on the subject, I see that this warning appears in several distributions and is related to a conflict of lvmetad with udev
Anyway, it is not really relevant, but this has already been addressed and there is update of lvm2 to correct this behavior.
In case, if possible, please update the package of lvm2, because besides that I saw that there are other corrections that can bring benefit to the UCS.
Best regards,
Michael Voigt