device-mapper: remove ioctl on cryptoroot failed: Device or resource busy

  • Open
  • quality assurance status badge
Details
One participant
  • theamazed74
Owner
unassigned
Submitted by
theamazed74
Severity
normal
T
T
theamazed74 wrote on 4 Oct 2019 07:33
(address . bug-guix@gnu.org)
LqKFXWV--3-1@tutanota.com
# Steps to reproduce:

I start going through the GUI installer and during the install I get these errors:

![memory-leak](https://coinsh.red/u/653Guix-Memory-Leak.jpeg) https://coinsh.red/u/653Guix-Memory-Leak.jpeg

Next I enter and get these:

![crypt-error]( https://coinsh.red/u/Crypt-Error_647_.jpeghttps://coinsh.red/ipfs/QmWkYNpehzGZNeJquZb8ev39SzsQ9crmMfNofAnMKNdz4c https://coinsh.red/ipfs/QmWkYNpehzGZNeJquZb8ev39SzsQ9crmMfNofAnMKNdz4c ) https://coinsh.red/u/Crypt-Error_647_.jpeg

Then after restarting I tried the first couple steps then it halted with these:

![bug(pg1)](https://coinsh.red/u/TheFirst566.jpeg) https://coinsh.red/u/653Guix-Memory-Leak.jpeg

![bug(pg2)]( https://coinsh.red/u/653Guix-Memory-Leak.jpeghttps://coinsh.red/u/TheSECOND56677.jpeg https://coinsh.red/u/TheSECOND566.jpeg )

# What was expected?

I am not certain what these errors mean. I tried to RTFM but wasn't able to find much.
Attachment: file
T
T
theamazed74 wrote on 5 Oct 2019 01:57
Markdown
(address . 37612@debbugs.gnu.org)
LqOCGqV--3-1@tutanota.com
Sorry, for the bad formatting.
I hadn't used the GNU Bug reporting system before and thought it used markdown.
Attachment: file
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 37612@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 37612
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch