Bug 16449 - Installer not properly deletes LVM and can produce corrupted root partition
Summary: Installer not properly deletes LVM and can produce corrupted root partition
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
: High normal
Target Milestone: Mageia 6
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard: MGA5TOO
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-07-23 00:35 CEST by Nikita Krupenko
Modified: 2017-01-17 10:36 CET (History)
4 users (show)

See Also:
Source RPM: drakxtools
CVE:
Status comment:


Attachments
Log from dracut (37.08 KB, text/plain)
2015-07-23 01:29 CEST, Nikita Krupenko
Details

Description Nikita Krupenko 2015-07-23 00:35:46 CEST
Description of problem:
Deleting LVM does not lead to writing changes into disk immediately. If LVM deleted and then another one created, it can produce corrupted partition inside LVM. If root partition inside this new LVM, the system won't boot and even root partition cannot be mounted. Installation produces no errors, all seems fine until system tries to boot.
This also can happen on system reinstall, with deleting LVM and creating new one.

This only happens if new LVM is encrypted.

I tested it in VirtualBox with EFI enabled.

Version-Release number of selected component (if applicable):
Mageia 5 LiveDVD KDE4 x86_64

How reproducible:
Always.

Steps to Reproduce:
1. Start installation, use clean disk.
2. Select custom partitioning.
3. Create ESP partition.
4. Create LVM partition.
5. Click on "Add to LVM".
6. Confirm writing changes into disk (!).
7. Click on "Remove from LVM".
8. Delete LVM partition.
9. Create new _encrypted_ LVM.
10. Confirm writing changes into disk (!).
11. Click on "Add to LVM".
12. Create root partition in vg.
13. Proceed installation.
14. After reboot enter password befor grub and on system start.
15. The boot should fail and drop into dracut debug shell.

There is one workaround available. After step 8 proceed the installation and changes will be written into disk. Then return back and proceed from step 9. The system should boot.

Reproducible: 

Steps to Reproduce:
Comment 1 Nikita Krupenko 2015-07-23 01:29:51 CEST
Created attachment 6862 [details]
Log from dracut
Comment 2 Marja van Waes 2016-07-12 17:46:01 CEST
@ Nikita

Can you still reproduce this issue with 6sta1 or later?
Comment 3 Nikita Krupenko 2016-07-12 17:54:17 CEST
I haven't checked it yet. Is it fixed?
Comment 4 Samuel Verschelde 2016-07-15 11:37:36 CEST
(In reply to Nikita Krupenko from comment #3)
> I haven't checked it yet. Is it fixed?

I can't tell, but your checking it again would be a valuable contribution, if you can find time for it. Thanks!

Note You need to log in before you can comment on or make changes to this bug.