Bug 25466 - Installer rescue shell miss LVM tools symlinks
Summary: Installer rescue shell miss LVM tools symlinks
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal enhancement
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-23 17:19 CEST by Morgan Leijström
Modified: 2020-02-18 12:01 CET (History)
3 users (show)

See Also:
Source RPM: drakx-installer-rescue
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Morgan Leijström 2019-09-23 17:19:19 CEST 
Description of problem:
Impossible to rescue a LVM based install (all mine are...)

On the good side i can using the installer rescue shell use a loks encrypted partititon as "cryptsetup luksOpen" works, but inside that i have a LVM system so i have to use "vgscan", which is not found.
Comment 1 Lewis Smith 2019-09-23 20:52:51 CEST 
See alsq bug 22795, whose *title* is in the same area, but which talks more about Grub. These may be duplicates, but I cannot judge.

Assigning to tv for 'drakx-installer-rescue', CC'ing ISO team for info.

Assignee: bugsquad => thierry.vignaud
CC: (none) => isobuild

Comment 2 Thomas Backlund 2019-09-23 20:57:29 CEST 
Actually the lvm tools are there, just not all the symlinks (vgscan & co)

if you use lvm command directly it can do all you want..

But I guess we should add the symlinks

CC: (none) => tmb
Severity: major => enhancement
Source RPM: (none) => drakx-installer-rescue

Comment 3 Morgan Leijström 2019-09-24 11:42:27 CEST 
Ah, yes symlinks would be great.
Us casual home admins like me did not even know vgscan was a symlink...
Morgan Leijström 2019-09-24 17:57:38 CEST

Summary: Installer rescue shell miss LVM tools => Installer rescue shell miss LVM tools symlinks

Comment 4 Thierry Vignaud 2020-02-18 12:01:05 CET 
Fixed in git

Resolution: (none) => FIXED
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.