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

Partition ID's and labels should be unique to the node hosting the disk #674

Open
khers opened this issue Dec 13, 2024 · 3 comments
Open
Assignees

Comments

@khers
Copy link

khers commented Dec 13, 2024

We are attempting to recover files from a dead node by placing its disk in a new node. Unfortunately, the disk controller enumerates it hardware in random order so we cannot guarantee that the disk for this node is the first one present and is booted. This is because the boot partition for both of these disks share a label and a UUID. It won't solve the disk enumeration problem, but having unique UUIDs and labels would at least allow us to easily identify what disk is being used.

@tzumainn
Copy link
Contributor

@hakasapl what's the right way to handle this?

@hakasapl
Copy link
Collaborator

Not sure it's possible to handle this, if the RAID controller had an HBA mode it would probably work better but I'm not sure there do

@khers
Copy link
Author

khers commented Dec 18, 2024

You likely can't fix the disk enumeration problem. However, if you can assign a unique ID or label to the disk and partition then you don't need to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: To do
Development

No branches or pull requests

3 participants