Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Installation to storage with existing LVM or Linux MD metadata may fail #30

Open
serhepopovych opened this issue Sep 28, 2020 · 0 comments
Open

Installation to storage with existing LVM or Linux MD metadata may fail #30

serhepopovych opened this issue Sep 28, 2020 · 0 comments
Assignees
@serhepopovych
Labels
bug Something isn't working
Milestone
first-release

Comments

@serhepopovych
Copy link
Owner

If target storage isn't clean from previous installation and contains MD and/or LVM metadata
partman may fail to update in-kernel representation of new partition layout with EBUSY (Device or resource is busy).

Removing MD and/or LVM signatures from storage before install (e.g. with wipefs(8)) does help. Giving raid=noautodetect
to kernel during install helps only to prevent kernel from automatically assembing MD arrays with 0.9 metadata. Other
array types assembed/activated somewhere in debian-installer or partman.
@serhepopovych serhepopovych added this to the first-release milestone Sep 28, 2020
@serhepopovych serhepopovych self-assigned this Sep 28, 2020
@serhepopovych serhepopovych added the bug Something isn't working label Sep 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@serhepopovych serhepopovych

Labels
bug Something isn't working
Projects
None yet
Milestone
first-release
Development

No branches or pull requests
1 participant
@serhepopovych