Are disk labels sda/sdb/sdc/… tied to physical ports?
Clash Royale CLAN TAG#URR8PPP
up vote
3
down vote
favorite
I'm wondering if disk labels like sda/sdb/sdc/... are associated with physical ports on the mainboard? For instance, if I have sda/sdb/sdc and remove the first 2 disks, will sdc become sda or will it stay sdc? Is the principle behind assigning disk labels documented somewhere?
disk
add a comment |Â
up vote
3
down vote
favorite
I'm wondering if disk labels like sda/sdb/sdc/... are associated with physical ports on the mainboard? For instance, if I have sda/sdb/sdc and remove the first 2 disks, will sdc become sda or will it stay sdc? Is the principle behind assigning disk labels documented somewhere?
disk
add a comment |Â
up vote
3
down vote
favorite
up vote
3
down vote
favorite
I'm wondering if disk labels like sda/sdb/sdc/... are associated with physical ports on the mainboard? For instance, if I have sda/sdb/sdc and remove the first 2 disks, will sdc become sda or will it stay sdc? Is the principle behind assigning disk labels documented somewhere?
disk
I'm wondering if disk labels like sda/sdb/sdc/... are associated with physical ports on the mainboard? For instance, if I have sda/sdb/sdc and remove the first 2 disks, will sdc become sda or will it stay sdc? Is the principle behind assigning disk labels documented somewhere?
disk
disk
asked 1 hour ago
bluenote10
921819
921819
add a comment |Â
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
3
down vote
No.
udev
drive identifiers are done in multiple ways, but they are allocated dynamically on bootup and therefore they will change if you unplug devices (or even if one just happens to spin up slower one day). Slightly more consistent than this is /dev/by-path
which will give you a path by connection to the machine, e.g. PCI bus -> Card 0 -> Port 2 (so long as the chip maintains consistent numbering, which isn't guaranteed in all cases).
However, if you want almost perfectly consistent devices*, use their UUID by calling blkid
on the partition (like blkid /dev/sda1
) and then use that in your mount options or /etc/fstab
with UUID=
If you did this as a recent installation, then you should already see an example of this in your /etc/fstab
.
*Consistency is not guaranteed if you bitwise-copy (e.g. dd
) an entire device or partition because it copies the UUID as well. You'll have to change the UUID if you want to use both copies in the same machine.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
No.
udev
drive identifiers are done in multiple ways, but they are allocated dynamically on bootup and therefore they will change if you unplug devices (or even if one just happens to spin up slower one day). Slightly more consistent than this is /dev/by-path
which will give you a path by connection to the machine, e.g. PCI bus -> Card 0 -> Port 2 (so long as the chip maintains consistent numbering, which isn't guaranteed in all cases).
However, if you want almost perfectly consistent devices*, use their UUID by calling blkid
on the partition (like blkid /dev/sda1
) and then use that in your mount options or /etc/fstab
with UUID=
If you did this as a recent installation, then you should already see an example of this in your /etc/fstab
.
*Consistency is not guaranteed if you bitwise-copy (e.g. dd
) an entire device or partition because it copies the UUID as well. You'll have to change the UUID if you want to use both copies in the same machine.
add a comment |Â
up vote
3
down vote
No.
udev
drive identifiers are done in multiple ways, but they are allocated dynamically on bootup and therefore they will change if you unplug devices (or even if one just happens to spin up slower one day). Slightly more consistent than this is /dev/by-path
which will give you a path by connection to the machine, e.g. PCI bus -> Card 0 -> Port 2 (so long as the chip maintains consistent numbering, which isn't guaranteed in all cases).
However, if you want almost perfectly consistent devices*, use their UUID by calling blkid
on the partition (like blkid /dev/sda1
) and then use that in your mount options or /etc/fstab
with UUID=
If you did this as a recent installation, then you should already see an example of this in your /etc/fstab
.
*Consistency is not guaranteed if you bitwise-copy (e.g. dd
) an entire device or partition because it copies the UUID as well. You'll have to change the UUID if you want to use both copies in the same machine.
add a comment |Â
up vote
3
down vote
up vote
3
down vote
No.
udev
drive identifiers are done in multiple ways, but they are allocated dynamically on bootup and therefore they will change if you unplug devices (or even if one just happens to spin up slower one day). Slightly more consistent than this is /dev/by-path
which will give you a path by connection to the machine, e.g. PCI bus -> Card 0 -> Port 2 (so long as the chip maintains consistent numbering, which isn't guaranteed in all cases).
However, if you want almost perfectly consistent devices*, use their UUID by calling blkid
on the partition (like blkid /dev/sda1
) and then use that in your mount options or /etc/fstab
with UUID=
If you did this as a recent installation, then you should already see an example of this in your /etc/fstab
.
*Consistency is not guaranteed if you bitwise-copy (e.g. dd
) an entire device or partition because it copies the UUID as well. You'll have to change the UUID if you want to use both copies in the same machine.
No.
udev
drive identifiers are done in multiple ways, but they are allocated dynamically on bootup and therefore they will change if you unplug devices (or even if one just happens to spin up slower one day). Slightly more consistent than this is /dev/by-path
which will give you a path by connection to the machine, e.g. PCI bus -> Card 0 -> Port 2 (so long as the chip maintains consistent numbering, which isn't guaranteed in all cases).
However, if you want almost perfectly consistent devices*, use their UUID by calling blkid
on the partition (like blkid /dev/sda1
) and then use that in your mount options or /etc/fstab
with UUID=
If you did this as a recent installation, then you should already see an example of this in your /etc/fstab
.
*Consistency is not guaranteed if you bitwise-copy (e.g. dd
) an entire device or partition because it copies the UUID as well. You'll have to change the UUID if you want to use both copies in the same machine.
edited 37 mins ago
answered 1 hour ago
tudor
1,63721541
1,63721541
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1083422%2fare-disk-labels-sda-sdb-sdc-tied-to-physical-ports%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password