On Tue, Feb 08, 2000 at 03:36:43AM +0800, Peter Wemm wrote:
> >
> > Hope this is enough to help, if not, I'll provide more. The two-
> > line errors that repeat for the second and each following drive
> > present seem interesting...
>
> I'm sorry, I'm still not following this, there's far too much missing
> information.
>
> To fix this, we need to know:
> 1: the config file relating to the disks
Sure. In fact, after I transcribed these messages, I went in to look
at the kernel configuration file, made a change to more match what
other people were using/the suggestions in LINT, rebooted, and saw
exactly the same results.
Note that I'm having trouble getting my mouse working right, so I'm
typing this all in.
device ahc
device scbus
device da
device cd
device pass
[and to wire things down: ]
device scbus0 at ahc0 (first boot was without this line, didn't
help booting with it either)
device da0 at scbus0 target 1
> 2: the scsi device configuration
You mean like, IBM 1GB drive at target 0, 4GB drive at target 1,
1GB drive at target 2, CD at target 6, for the test?
Normally, the drive mentioned at target 0 is at target 4, so that
the lowest numbered target then becomes target 1, the root/OS disk.
More about this later.
> 3: the dmesg output showing clearly what isn't working. Don't delete too
> much information, taking out too much data makes it impossible to figure out.
The thing is, it (for me) doesn't show clearly what isn't working.
Apart from those two lines that I find unusual, the only way to know
it's failing is when device da0 does not get wired to target 1 on
scbus0 as I specify above, but instead gets attached to target 0.
> 4: Prefereably an old dmesg showing how it used to work - check older
> /var/log/messages and /var/log/messages.*.gz - it should be in there.
``Used to work?'' Well, I just set up this machine with both -current
and -stable, so it never used to work. It does, however, work under
-stable with only the `device da0 at scbus0 target 1' line, and the
appropriate devices for scbus/ahc. I can send that dmesg output, to
show how -stable works...
> 5: a detailed explanation of what is going wrong, not just hints. Remember,
> we have no idea your respective systems are set up.
Okay, what goes `wrong' is that the disks fail to be wired to the
specified targets, and instead are attached as they would be if I
were not to attempt to wire them. All failures past that point are
what one would expect when disks are not where /etc/fstab expects
to find them.
I'll go over to another login and start collecting the dmesg outputs
from both -stable that works, and -current when the drives exist in
the order they are to be attached -- the times it fails, I would have
to change the fstab info to get the machine past single-user mode.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
