Bug 14528

Summary: mcc(uninstall old kernels) => system won't boot; goes into dracut
Product: Mageia Reporter: Pierre Fortin <pf>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal    
Version: 4   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: kernel* CVE:
Status comment:

Description Pierre Fortin 2014-11-13 15:55:22 CET
Description of problem:  Tiring of *desktop* kernels on laptop which are chosen by default for boot, via mcc, I removed kernel*desktop* and older kernel-tmb-laptop* and system will no longer boot.

Found that swap UUID changed in this process -- HOW?  
Does this happen when using mcc to remove old/unwanted kernels?

All attempts at correcting still fail to boot; even FAILSAFE. Found and used procedure at 
http://www.mageialinux-online.org/wiki/dracut-warning-could-not-boot to no avail.
BTW, chroot'ing failed due to missing zsh in SystemRescue4.2.0 -- editing files still possible, though more carefully.

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


How reproducible:  dunno. first time this happened. unable to boot mga4.
   Using SystemRescue to report this.


Steps to Reproduce:
1.  on laptop, remove kernel*desktop which are useless for full laptop functionality. Also, remove older kernel-tmb-laptop*.  NOTE: I did NOT remove or alter vmlinuz-3.12.26-tmb-laptop-1.mga4 which I've been using for months -- just tired of desktop default.
2.
3.


FILES:

/etc/dracut.conf.d/51-mageia-resume.conf:
add_device+="UUID=115f7bc9-a6b6-485a-9dac-5ee3f2f9bea2"

/boot/grup/menu.lst:
timeout 10
color black/cyan yellow/cyan
gfxmenu (hd0,4)/boot/gfxmenu
default 4

title linux-nonfb
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux-nonfb root=UUID=115f7bc9-a6b6-485a-9dac-5ee3f2f9bea2 resume=UUID=17e9aabf-bf31-4ea3-9118-4744a10ae28e
root (hd0,4)
initrd /boot/initrd.img

title failsafe
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=failsafe root=UUID=115f7bc9-a6b6-485a-9dac-5ee3f2f9bea2 failsafe
root (hd0,4)
initrd /boot/initrd.img

title windows
root (hd0,2)
makeactive
chainloader +1

title tmb-laptop 3.12.26-1.mga4
kernel (hd0,4)/boot/vmlinuz-3.12.26-tmb-laptop-1.mga4 BOOT_IMAGE=tmb-laptop_3.12.26-1.mga4 root=UUID=115f7bc9-a6b6-485a-9dac-5ee3f2f9bea2 splash quiet resume=UUID=17e9aabf-bf31-4ea3-9118-4744a10ae28e vga=788
root (hd0,4)
initrd /boot/initrd-3.12.26-tmb-laptop-1.mga4.img

title linux
kernel (hd0,4)/boot/vmlinuz BOOT_IMAGE=linux root=UUID=115f7bc9-a6b6-485a-9dac-5ee3f2f9bea2 splash quiet resume=UUID=17e9aabf-bf31-4ea3-9118-4744a10ae28e vga=788
root (hd0,4)
initrd /boot/initrd.img


(sysresccd:/mnt/chroot/boot) # ls -l
total 40868
-rw-r--r-- 1 root root     440 Jul 17 14:22 boot.backup.sda
-rw-r--r-- 1 root root  144684 Aug  6 16:48 config-3.12.26-tmb-laptop-1.mga4
drwxr-xr-x 2 root root    4096 Dec 28  2013 dracut
-rwxr-xr-x 1 root root  535552 Jul 17 14:22 gfxmenu
drwxr-xr-x 2 root root    4096 Nov 13 08:24 grub
-rw------- 1 root root 8670795 Jul 18 03:35 initrd-3.12.13-desktop-2.mga4.img.old
-rw------- 1 root root 8775765 Jul 17 14:16 initrd-3.12.21-desktop-2.mga4.img.old
-rw------- 1 root root 9712705 Sep 15 02:21 initrd-3.12.26-tmb-laptop-1.mga4.img
lrwxrwxrwx 1 root root      36 Nov 13 02:34 initrd.img -> initrd-3.12.26-tmb-laptop-1.mga4.img
-rw------- 1 root root 8671567 Jul 18 03:36 initrd.img.old
lrwxrwxrwx 1 root root      36 Sep 15 02:21 initrd-tmb-laptop.img -> initrd-3.12.26-tmb-laptop-1.mga4.img
-rw-r--r-- 1 root root 1997625 Aug  6 16:48 System.map-3.12.26-tmb-laptop-1.mga4
lrwxrwxrwx 1 root root      33 Nov 13 02:34 vmlinuz -> vmlinuz-3.12.26-tmb-laptop-1.mga4
-rw-r--r-- 1 root root 3311680 Aug  6 16:48 vmlinuz-3.12.26-tmb-laptop-1.mga4
lrwxrwxrwx 1 root root      33 Sep 15 02:21 vmlinuz-tmb-laptop -> vmlinuz-3.12.26-tmb-laptop-1.mga4

What's with the initrd*.old files?


Added "nofail" to non-essential disks in /etc/fstab -- will test shortly after filing this report.

/etc/fstab (after SWAP correction and addition of "nofail"):
# Entry for /dev/sda5 :
UUID=115f7bc9-a6b6-485a-9dac-5ee3f2f9bea2 / ext4 acl,noatime 1 1
# Entry for /dev/sda7 :
UUID=e939f4d6-ae81-427e-8fe2-1fd3eede377d /home ext4 acl,noatime 1 2
# Entry for /dev/sda3 :
UUID=1C0A571C0A56F1EE /media/windows ntfs-3g defaults,nofail,umask=000 0 0
# Entry for /dev/sdc2 :
UUID=877dc6c1-6916-4494-8cb5-8ac3bdc34083 /mnt/hd ext4 noatime,acl,nofail 1 2
none /proc proc defaults 0 0
# Entry for /dev/sda6 :
#UUID=1d2df15b-5c80-43b5-8642-dc0a64cc214f swap swap defaults 0 0
UUID=17e9aabf-bf31-4ea3-9118-4744a10ae28e swap swap defaults,nofail 0 0


Reproducible: 

Steps to Reproduce:
Comment 1 Pierre Fortin 2014-11-13 17:11:03 CET
Boot still fails trying to mount swap by using OLD UUID:

rdsosreport.txt ends with:
[    8.761225] usb 2-1.5: new full-speed USB device number 3 using ehci-pci
[    8.848625] usb 2-1.5: New USB device found, idVendor=8087, idProduct=07dc
[    8.848627] usb 2-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0
### boot stalls here for 30 seconds...
[   38.441133] dracut Warning: Could not boot.
[   38.443890] dracut Warning: /dev/disk/by-uuid/1d2df15b-5c80-43b5-8642-dc0a64cc214f does not exist
+ '[' -f /run/initramfs/init.log ']'

See also https://bugzilla.redhat.com/show_bug.cgi?id=995843

Yet, still unable to find where the old UUID is coming from...
Comment 2 Pierre Fortin 2014-11-13 21:33:06 CET
The old swap UUID is buried in initrd-3.12.26-tmb-laptop-1.mga4.img -- all well and good; but it was a PAIN to get this resolved. Finally solved missing zsh files to be able to chroot and re-install active kernel:

sysresccd# rpm -Uvh /distros/remote/mageia/distrib/4/x86_64/media/core/updates/kernel-tmb-laptop-3.12.26-1.mga4-1-1.mga4.x86_64.rpm 
Preparing...                          ################################# [100%]
	package kernel-tmb-laptop-3.12.26-1.mga4-1-1.mga4.x86_64 is already installed

sysresccd# rpm -Uvh --force /distros/remote/mageia/distrib/4/x86_64/media/core/updates/kernel-tmb-laptop-3.12.26-1.mga4-1-1.mga4.x86_64.rpm
Preparing...                          ################################# [100%]
Updating / installing...
   1:kernel-tmb-laptop-3.12.26-1.mga4-################################# [100%]


All this because after using mcc to remove old kernels, I was left with a new UUID for the swap partition.  :P

Now to reboot to see if this is the final solution....
Comment 3 Samuel Verschelde 2015-09-21 13:18:49 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you are able to reproduce it 
against a later version of Mageia, you are encouraged to click on "Version" and 
change it against that version of Mageia. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 4 Pierre Fortin 2015-09-21 16:37:31 CEST
Will re-open if it occurs again.

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