[SOLVED] harddisk order wrong, when crossflashed controller is plugged in

LBM · 03-21-2019, 03:37 PM

Hi,

I've just added an crossflashed LSI controller to an system. Harddisk added to this, are now starting from bottom, /dev/sda , /dev/sdb etc.

It gives me some issues, regarding my setup, scripts, configuration and all that. since without this controller, first device is /dev/sda and so forth, and it has been like that for quite some time.

Is it somehow possible to change it, so the onboard first device is still /dev/sda, sdb.. etc, and then the secondary controller, will be /dev/sdX and so on ?.

berndbausch · 03-21-2019, 04:47 PM

Don’t use /dev/sda etc. These file names are called non-persistent device file names for precisely this reason.
Instead, use UUIDs, filesystem labels or symbolic links in /dev/disk. These names are persistent.

Here is an article in the Archlinux wiki. It largely applies to Debian as well: https://wiki.archlinux.org/index.php..._device_naming.

syg00 · 03-21-2019, 08:29 PM

That relates to entities that have a UUID. Device nodes don't - the OP could use by-id, but that would quickly get ugly.
Depends if the scripts really do need to access the device node itself - maybe they can be generalised to take advantage of UUID or LABEL. Else check the BIOS/EFI firmware to see if you can change the order - Linux, and just as importantly, the boot-loader see the devices as enumerated by the firmware. Does the system boot with the card in ?.

LBM · 03-22-2019, 05:37 AM

Yes, WMM,UUID,ID/by-id is defiantly an way to go. Unfortunately, I cannot just change this easily, for which, the other would be easier for me to start with.

Yes, the controller, is there upon boot.