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.

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

[bug]: Unable to set up due to "Disk Management Error" #1756

Open
1 task done
kn0wmad opened this issue Aug 21, 2022 · 7 comments
Open
1 task done

[bug]: Unable to set up due to "Disk Management Error" #1756

kn0wmad opened this issue Aug 21, 2022 · 7 comments
Assignees
Labels
Bug Something isn't working Ghost Bug reports that haven't been consistently reproducible Needs Diagnosis Send to Needs Triage after bug has been diagnosed Needs Scoping Requirements are not fully defined Needs Triage Needs to be assigned a priority startd Issues pertaining to startd itself

Comments

@kn0wmad
Copy link
Contributor

kn0wmad commented Aug 21, 2022

Prerequisites

EmbassyOS Version

0.3.1.1

Device

Laptop/Desktop

Device OS

Linux

Device OS Version

5.18

Browser

Firefox

Browser Version

102

Current Behavior

Disk Management Error File descriptor 9 (pipe:[14989]) leaked on pvremove invocation. Parent PID 594: /usr/local/bin/embassy-init File descriptor 10 (pipe:[14989]) leaked on pvremove invocation. Parent PID 594: /usr/local/bin/embassy-init WARNING: PV /dev/sda is used by VG EMBASSY_5PDBSFY6A43O5ISBKZYHTMOKXDJRFARE4L6AH5GJGULD2U3N5S5Q. WARNING: Wiping physical volume label from /dev/sda of volume group "EMBASSY_5PDBSFY6A43O5ISBKZYHTMOKXDJRFARE4L6AH5GJGULD2U3N5S5Q". Can't open /dev/sda exclusively. Mounted filesystem? Can't open /dev/sda exclusively. Mounted filesystem? Restart Embassy to try again.

Above error is given, restarts do not change the situation, error persists

Expected Behavior

Setup flow completes

Steps to Reproduce

  1. Attempt setup flow
  2. Get to 'add disk' stage
  3. See error

Anything else?

No response

@kn0wmad kn0wmad added Bug Something isn't working startd Issues pertaining to startd itself Needs Scoping Requirements are not fully defined Needs Triage Needs to be assigned a priority Needs Diagnosis Send to Needs Triage after bug has been diagnosed labels Aug 21, 2022
@MattDHill MattDHill added this to the 0.3.2 milestone Aug 24, 2022
@MattDHill
Copy link
Member

Is this still a thing?

@kn0wmad
Copy link
Contributor Author

kn0wmad commented Sep 25, 2022

To my knowledge it is unsolved

@MattDHill MattDHill modified the milestones: 0.3.2, 0.3.3 Oct 4, 2022
@kn0wmad
Copy link
Contributor Author

kn0wmad commented Nov 3, 2022

I think @dr-bonez has more insight on this one

@dr-bonez
Copy link
Member

dr-bonez commented Nov 3, 2022

For some reason lvm is automounting the disk, but not always. Trying to determine why

@redragonx redragonx assigned redragonx and unassigned dr-bonez Nov 9, 2022
@MattDHill MattDHill removed this from the 0.3.3 milestone Nov 28, 2022
@elvece elvece assigned dr-bonez and unassigned redragonx Dec 14, 2022
@elvece elvece added the Ghost Bug reports that haven't been consistently reproducible label Dec 14, 2022
@MattDHill
Copy link
Member

@dr-bonez status on this?

@dr-bonez
Copy link
Member

Haven't reproduced in a while. It's hard to see what's causing the problem unless it can be reproduced in a lab

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Ghost Bug reports that haven't been consistently reproducible Needs Diagnosis Send to Needs Triage after bug has been diagnosed Needs Scoping Requirements are not fully defined Needs Triage Needs to be assigned a priority startd Issues pertaining to startd itself
Projects
None yet
Development

No branches or pull requests

5 participants