|
Bugzilla – Full Text Bug Listing |
| Summary: | Having / encrypted under lvm doesn't able to open vg/lv volumes | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 12.2 | Reporter: | Bruno Friedmann <bruno> |
| Component: | Basesystem | Assignee: | Dong Mao Zhang <dmzhang> |
| Status: | VERIFIED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | ||
| Version: | Factory | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 12.2 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Screenshot of the situation | ||
Hi,could you please help to have a look at this?I am not very sure whether it is right to assign it to you.Feel free to reassign it.Thank you:) I close this bug. I've killed now the defect install and install a new one with a fresh factory Beta. |
Created attachment 491670 [details] Screenshot of the situation User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20100101 Firefox/12.0 On a previously working M3 zypper dup to last version of factory (directly picked from download.o.o) with up to date patches from 16-20 May. Whatever initrd you use (even a mkinitrd -A) a problem exist in volume detection, and this lead to a loop vg0 not found after entering the luks passphrase. Reproducible: Always Steps to Reproduce: 1. Install factory (good luck) with the following partition schema sda1 -> ext4 /boot sda2 -> Full pv + encryption (enter your desired passphrase) create vg0 as volume group create at least two logical volume (lvswap for swap) and lvsuse for / (made with btrfs) 2. Installation finish (was the case under M3) 3. reboot 4. See warnings (see screenshot) about /lib/udev/vol_id etc ... 5. Enter you luks passphrase 6. See the loop in vg0 not found 7. Cry a bit ... Actual Results: Factory totally locked down ... Still accessible by other live distribution opening vg + luks and using chroot. So no data are (yet) really lost. I've no idea who's responsible for this mess :-) between mkinitrd, vol_id, udev, etc Expected Results: A working boot process like it should be (especially at this stage now) There's also a defect on plymouth/pango font created by mkinitrd which was working on the proposed submission. Feel free to raise up the severity.