Well, the loader actually looks at hd0 and the system was able to boot
with a modified fstab, but then disklabel shows info for incorrect
drives and I am not able to mount the new drive. I will try boot -c
and your suggestions and let you know what happens
On 6/18/07, Marco S Hyman <[EMAIL PROTECTED]> wrote:
"Bruce Bauer" writes:
> You nailed it down!
> After boot>-s, examining the dmesg shows the SATA drive is wd0 and the
> former wd0 is wd1 and the former wd1 is wd2. Now if my thinking is
> correct, all I should have to do is edit fstab to reflect the changed
> drive positions and the system should be happy.
If the loader is looking to wd0 for the kernel changing the fstab
will do nothing. I have a custom kernel to set the sata as wd0
# IDE hard drives
wd1 at pciide? flags 0x0000
wd0 at pciide? flags 0x0000
wd* at pciide? flags 0x0000
but you can do the same thing with a GENERIC kernel by playing with
config -e or boot -c
neko[GENERIC]$ config -e bsd
OpenBSD 4.1-current (GENERIC) #34: Sun May 27 15:11:12 PDT 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/amd64/compile/GENERIC
warning: no output file specified
Enter 'help' for information
ukc> find wd
42 wd* at wdc*|pciide* channel -1 flags 0x0
ukc> add wd1
Clone Device (DevNo, 'q' or '?') ? 42
Insert before Device (DevNo, 'q' or '?') ? 42
42 wd1 at wdc*|pciide* channel -1 flags 0x0
ukc> add wd0
Clone Device (DevNo, 'q' or '?') ? 43
Insert before Device (DevNo, 'q' or '?') ? 43
43 wd0 at wdc*|pciide* channel -1 flags 0x0
ukc> find wd
42 wd1 at wdc*|pciide* channel -1 flags 0x0
43 wd0 at wdc*|pciide* channel -1 flags 0x0
44 wd* at wdc*|pciide* channel -1 flags 0x0
ukc>
// marc
