Bug 11290

Summary: 4_a2: Cannot add dev-disk-by\x2dpartlabel-*.device to initrd.target Invalid argument
Product: Mageia Reporter: Bit Twister <bittwister2>
Component: RPM PackagesAssignee: Colin Guthrie <mageia>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal    
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: systemd-208-1.mga4.src.rpm CVE:
Status comment:
Attachments: rdsosreport.txt

Description Bit Twister 2013-09-26 10:19:53 CEST
Description of problem:
systemd[1]: Cannot add dependency dev-disk-by\x2dpartlabel-*.device to initrd.target, ignoring: Invalid argument

Thinking  glibc-2.18-2.mga4 or some other updated caused the problem.
I installed all updates but the kernel 3.11.1-1 packages on this date.

With new kernel dracut emeregency shell was dead.

Version-Release number of selected component (if applicable):


How reproducible: Always


Steps to Reproduce:
1. Applied updates reboot

Not sure why it fails on 
 DMI: Hewlett-Packard p6610f/2AB1 , BIOS 6.02 07/21/2010
works in my VirtualBox and on my testbed box
 DMI: LENOVO H215/Tilapia CRB, BIOS D2KT21AUS 03/12/2010


Reproducible: 

Steps to Reproduce:
Comment 1 Bit Twister 2013-09-26 10:21:20 CEST
Created attachment 4376 [details]
rdsosreport.txt
Manuel Hiebel 2013-09-27 21:26:42 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => mageia

Comment 2 Colin Guthrie 2013-09-29 13:10:59 CEST
I suspect this is due to systemd being used in initrd by default in newer dracut. I've disabled this for now even if I do intend to turn it back on once I've tested it properly myself.
Comment 3 Bit Twister 2013-09-30 06:19:01 CEST
(In reply to Colin Guthrie from comment #2)
> I suspect this is due to systemd being used in initrd by default in newer
> dracut. I've disabled this for now even if I do intend to turn it back on
> once I've tested it properly myself.

I saw two problems. 
1. dracut prompt was dead and Ctl+Alt+del had no effect.
2. dracut|systemd did not use the kernel cmdline argument root=LABEL=cauldron from menu.lst for mounting / when / had a different UUID than expected.

My WAG, if you fix 2 before 1 you will not see problem 1. :(
Comment 4 Bit Twister 2013-10-15 20:27:05 CEST
Confirmed dracut has a dead keyboard if it cannot find the UUID of the partition of the last dracut -f.

$ uname -r
3.12.0-desktop-0.rc5.1.mga4

$ blkid | grep -m 1 cauldron
/dev/sda4: LABEL="cauldron" UUID="abecf907-e405-4140-b1f5-d514515c2f29" TYPE="ex

$ grep ' / ' /etc/fstab
LABEL=cauldron / ext4 relatime,acl 1 1

# grep -m 1 hd0,3 /boot/grub/menu.lst 
kernel (hd0,3)/boot/vmlinuz BOOT_IMAGE=mga4_64_a3_Cauldron root=LABEL=cauldron nokmsboot vga=794

$ cat /local/bin/fix_uuid
#!/bin/bash
  if [ $# -gt 0 ] ; then   # running a test so change uuid.
    tune2fs  -U "abecf907-e405-4140-b1f5-d514515c2f20" /dev/sda4
  else  # put uuid back
    tune2fs  -U "abecf907-e405-4140-b1f5-d514515c2f29" /dev/sda4
  fi
  blkid /dev/sda4
#*** end fix_uuid *****

Source RPM: systemd-207-2.mga4.src.rpm => systemd-208-1.mga4.src.rpm

Comment 5 Samuel Verschelde 2015-04-23 14:31:54 CEST
(In reply to Bit Twister from comment #3)
> (In reply to Colin Guthrie from comment #2)
> > I suspect this is due to systemd being used in initrd by default in newer
> > dracut. I've disabled this for now even if I do intend to turn it back on
> > once I've tested it properly myself.
> 
> I saw two problems. 
> 1. dracut prompt was dead and Ctl+Alt+del had no effect.
> 2. dracut|systemd did not use the kernel cmdline argument
> root=LABEL=cauldron from menu.lst for mounting / when / had a different UUID
> than expected.
> 
> My WAG, if you fix 2 before 1 you will not see problem 1. :(

Are those problems still present in Mageia 4 and cauldron?

Keywords: (none) => NEEDINFO

Comment 6 Bit Twister 2015-04-23 23:47:18 CEST
(In reply to Samuel VERSCHELDE from comment #5)
 
> Are those problems still present in Mageia 4 and cauldron?

No idea about problem 1, but 2 is fixed in mga4 and 5.

Keywords: NEEDINFO, Triaged => (none)

Comment 7 Samuel Verschelde 2015-04-24 10:05:10 CEST
For the bug report's clarity, I'm closing it since the original issue is fixed. Please open a new bug report for problem 1 if needed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED