search for: id_fs_uuid

This patch just includes the repo name in the subject.

...ice=${1-} + local envvar=${2-} + local rootname + + if [[ "$device" =~ "^.*[0-9]?$" ]]; then + rootname="${device:0:${#device}-1}" + fi + local uuid=$( + udevadm info --path=/sys/block/$rootname/$device --query=property | + awk '/ID_FS_UUID=/ { match($0, "ID_FS_UUID=(.*)", data); print data[1]; }' + ) + + eval $envvar="$uuid" +} + #Check for an existing HostVG on any device on the system. # Return 0 if then is a HostVG found, unless only one found is on $1 # Return 1 if no HostVG found or only found o...

This one incorporates feedback from mburns and apevec to ensure that all multipath devices are excluded in the list of available drives. Only drives with an identified bus are included in the list now.

...cally the one below.. + blkid /dev/sr0: UUID="2016-10-28-12-18-36-00" LABEL="CentOS 7 x86_64" TYPE="iso9660" PTTYPE="dos" /dev/sda1: UUID="a620a180-3a8c-4b5f-ad30-804f131a7261" TYPE="xfs" /dev/sda2: PTTYPE="dos" + blkid -o udev ID_FS_UUID=2016-10-28-12-18-36-00 ID_FS_UUID_ENC=2016-10-28-12-18-36-00 ID_FS_LABEL=CentOS_7_x86_64 ID_FS_LABEL_ENC=CentOS\x207\x20x86_64 ID_FS_TYPE=iso9660 ID_PART_TABLE_TYPE=dos To fix the problem, I booted the system from a livecd and used "wipefs" utility to erase the problematic signature &quo...

> Yannis Milios wrote: >>> But, what happens if you let the kernel post install scripts do the >>> work or setting up the initrd things? >> >> Initially, I just rebooted from LiveCD and left Grub,kernel and dracut >> do >> their job with the defaults, but unfortunately, boot process stops at >> initrd (dracut) stage with the following error: