linux-kernel - Re: SCSI device order changed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.61.0607161751590.3179@yvahk01.tjqt.qr>
Date:	Sun, 16 Jul 2006 17:53:33 +0200 (MEST)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Yuri van Oers <yvanoers@...all.nl>
cc:	linux-kernel@...r.kernel.org
Subject: Re: SCSI device order changed

>
>Hard disks are sda thru sdd, the devices start at sde. That is, up until I
>booted 2.6.17 _with_ the external devices attached. The kernel swapped
>the order of the cards: devices start at sda, and the disks come after,
>which means it can't find / on sda.
>
>I found a related post here: http://lkml.org/lkml/2005/12/3/192
>which suggests this situation arose around 2.6.15. It also says ordering
>can't be guaranteed. If that's the final verdict, I'll simply swap the
>cards on the PCI bus and be done with it.
>
And then, hope it does not change again?

It usually depends on link time order (when compiled in) or module load 
order (with initrd), both of which, esp. the latter, can be fine-tuned to 
the user's needs.

Also note CONFIG_BLK_DEV_OFFBOARD.



Jan Engelhardt
-- 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/