Barry Bouwsma wrote:
> > > > > > > > It seem hardwiring SCSI devices is broken in -current:
> > > > > dmesg would be useful, otherwise we can't even begin to guess what ha
ppened.
> > > >
> > > I don't have it in /var/log/messages, but I can reboot my machine
> > > (that has this problem) and copy down what I see.
>
> Okay, this may or may not be relevant...
>
> I've re-ID'ed one disk to be at target 0. The kernel config is
> supposed to wire target 1 to be da0. There is another disk at
> target 2 (in my earlier tests, there were only two disks).
>
> Before the `Mounting root' entry I see the following now:
>
> (da0:ahc0:0:0:0): Duplicate Wired Device entry!
> (da0:ahc0:0:0:0): Second device will not be wired
> (da0:ahc0:0:0:0): Duplicate Wired Device entry!
> (da0:ahc0:0:0:0): Second device will not be wired
>
> That's right, twice, with three disks.
> When I only had two disks (that was the error I noted in the /var
> logfiles), there was only a single pair of lines.
>
> Then I see...
> Mounting root from ufs:da1s1a (I don't remember what I did earlier
> to boot cleanly with another disk at target 0, I should try to
> reproduce that in case there is any difference)
> da2 at ahc0 bus 0 target 2 lun 0
> [...]
> cd0 at ahc0 bus 0 target 6 lun 0
> [...]
> da1 at ahc0 bus 0 target 1 lun 0
> [...]
> da0 at ahc0 bus 0 target 0 lun 0
>
>
> Ideally, target 1 should be da1. It finds the fstab file but
> that has da0 as root/swap/etc, not the da1 that the above dmesg
> puts it at. So the problem is that mounting the filesystems
> fails.
>
> Note that I had tried the kernel configuration several times with
> different possibilities to keep `config' quiet, but none of them
> resulted in the desired device being wired, so it is possible that
> this kernel's config file isn't quite as clean as it should be.
> I'll take a look at that and if need be, correct it and try again.
> For this kernel, config did complain about the `0', so I think it
> should be close to what I intended.
>
> 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
2: the scsi device configuration
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.
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.
5: a detailed explanation of what is going wrong, not just hints. Remember,
we have no idea your respective systems are set up.
Cheers,
-Peter
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
