Unassigned Devices storage device

[xDayTx]

I did a transplant of my server from one case to another, I did not change any components, and left the hard drives in the same SATA ports as before.

Upon first boot, unassigned devices plugin, shows the above, from sdb to sdf, storage device_0000......9744. I have no idea what caused this.

 

My drives still show up as usual above, just that the drive letters have changed accordingly. Dockers and VM and files are still working and accessible, and a parity check showed no errors.

Is this issue of any worry?

[trurl]

I'm not sure I understand. Is there something you are concerned about other than the fact that the drive "letters" have changed? The drive letters are not expected to stay the same from one boot to another though they often do. Only the serial numbers are used to identify the disks.

[trurl]

Maybe if you had some screenshot or description of how things were before it would help clarify.

[xDayTx]

Nah. It's alright. I'm just worried about the drive letter change that's all. If it's normal, then shouldn't be an issue anymore.

 

I was just curious as to why unassigned devices would list sdb to sdf, as sdb to sdf was the previous drive letters for the drives.

When I click on sdb to sdf disk logs info, this appears:

 

[itimpi]

29 minutes ago, xDayTx said:

I was just curious as to why unassigned devices would list sdb to sdf, as sdb to sdf was the previous drive letters for the drives.

When I click on sdb to sdf disk logs info, this appears:

Linux assigns the sdX type names dynamically in ascending order at the point it first sees a device.  The names are therefore timing dependant on when devices actually first get initialised.

[Vr2Io]

storage device_0000......9744 should be some kind of memory card reader drive mapping.

Edited December 16, 2019 by Benson