[nycbug-talk] OpenBSD, numbering disks...

George Georgalis george
Fri Jul 22 18:22:52 EDT 2005

On Tue, Jul 19, 2005 at 09:16:48AM -0400, bruno wrote:
>On Tue, Jul 19, 2005 at 09:01:01AM -0400, George Georgalis wrote:
>> On Tue, Jul 19, 2005 at 01:46:46AM -0400, Jesse Callaway wrote:
>> >On Monday 18 July 2005 11:59 pm, George Georgalis says:
>> >> What's the best way to assure my root ata disk doesn't get renumbered,
>> >> when new sata drives are added?
>> >>
>> >
>> >There isn't one. The number will get bumped. Not when you're running, but if 
>> >you reboot. So I'm assuming this is only a problem when rebooting. Maybe you 
>> The thing is, BIOS doesn't number them differently, ata is always
>> first, then sata drives (there is no sata/pata in bios boot order, just
>> hd-0,1,2,3,4...), it is the OS renumbering the drives, so I imagine it
>> could be programmed or configured to do "the thing I expect" -- whether
>> that is right or not.
>> dkcsum: wd0 matched BIOS disk 81
>> dkcsum: wd1 matched BIOS disk 80
>> I think the only thing required is a "configuration" to make BIOS 0x80
>> always map to wd0. 
>You can probably do this with a kernel config file.

I've been looking but can't find anything like this, only go there if
you know exactly what you are doing, type statements.

All I'm really looking to do is not rename my root filesystem device
when I add or remove auxiliary sata disks. As this operation is intended
to happen frequently on an NFS server, I don't really want to require
booting a rescue cd to mount and edit fstab entries.  Besides taking
time, too much room for error. On one occasion the other day, BIOS
booted OpenBSD with its root fs, in readonly; then proceeded to mount
DFLY partitions rw, and run on them. It actually worked long enough to
log in, and do a few commands, before it all locked up.

// George

George Georgalis, systems architect, administrator <IXOYE><
http://galis.org/ cell:646-331-2027 mailto:george at galis.org

More information about the talk mailing list