# Device name changed after reboot jbob disk

**URL:** <https://forums.rockylinux.org/t/device-name-changed-after-reboot-jbob-disk/11789>\
**Category:** Rocky Linux Help & Support\
**Tags:** supermicro, rocky-linux-9\
**Created:** [November 6, 2023, 7:37am UTC](https://forums.rockylinux.org/t/device-name-changed-after-reboot-jbob-disk/11789 "2023-11-06T07:37:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![WatsonChoi](https://avatars.discourse-cdn.com/v4/letter/w/58956e/32.png) [@WatsonChoi](https://forums.rockylinux.org/u/WatsonChoi)\
**Post date:** [November 6, 2023, 7:37am UTC](https://forums.rockylinux.org/t/device-name-changed-after-reboot-jbob-disk/11789/1 "2023-11-06T07:37:43Z")

</div>

Hi, guys

If you reboot after changing the sas disk to Job mode, the device name gets twisted.

This is the spec of the server I’m testing right now.

os= rocky 9.2  
I put the scsi\_mod.scan=sync option in grub in os.

For example, os disk = /dev/sda(reboot -\>) /dev/sdc  
Like this.

I really don’t know what the hell’s wrong with this, guys. Please save me

I want to solve it without uuid or mount or formatting.

Bless everyone who answered

---

<div class="post-metadata">

**Author:** ![iwalker](https://sea2.discourse-cdn.com/flex020/user_avatar/forums.rockylinux.org/iwalker/32/2599_2.png) [@iwalker](https://forums.rockylinux.org/u/iwalker)\
**Post date:** [November 6, 2023, 7:39am UTC](https://forums.rockylinux.org/t/device-name-changed-after-reboot-jbob-disk/11789/2 "2023-11-06T07:39:23Z")

</div>

This is why mounts using the UUID for the partition is the solution to the problem, when mount points or disks change position.

The solution is to use blkid to get the UUID and then use that in /etc/fstab. Why do you **not** want to use this method which is very easy to solve your problem?

---

<div class="post-metadata">

**Author:** ![WatsonChoi](https://avatars.discourse-cdn.com/v4/letter/w/58956e/32.png) [@WatsonChoi](https://forums.rockylinux.org/u/WatsonChoi)\
**Post date:** [November 6, 2023, 8:57am UTC](https://forums.rockylinux.org/t/device-name-changed-after-reboot-jbob-disk/11789/3 "2023-11-06T08:57:04Z")

</div>

thx, iwalker

I want to solve this problem through grub setting.  
Is there only a solution through UUID?

WatsinChoi

---

<div class="post-metadata">

**Author:** ![jlehtone](https://avatars.discourse-cdn.com/v4/letter/j/e9a140/32.png) [@jlehtone](https://forums.rockylinux.org/u/jlehtone)\
**Post date:** [November 6, 2023, 9:54am UTC](https://forums.rockylinux.org/t/device-name-changed-after-reboot-jbob-disk/11789/4 "2023-11-06T09:54:19Z")

</div>

> [@WatsonChoi](#):
>
> Is there only a solution through UUID?

At some point LABEL was also an option. Both UUID and LABEL are metadata stored within filesystem – _inside_ volume – and hence _persistent_, unlike the enumerated `/dev/sd*` names.

* * *

Low level clone of disks and volumes duplicates some of PARTUUID, PARTLABEL, UUID, and LABEL but that is usually a different issue.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/rockylinux/original/1X/91b7219eec10e30013422e4df76c1d898711a5d5.svg) [@system](https://forums.rockylinux.org/u/system)\
**Post date:** [January 5, 2024, 9:55am UTC](https://forums.rockylinux.org/t/device-name-changed-after-reboot-jbob-disk/11789/5 "2024-01-05T09:55:10Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.