On Fri, Sep 24, 1999 at 04:36:54PM -0400, Brad Chisholm wrote:
>
> D d0 State: up Device /dev/da0e Avail: 0/17366 MB
>(0%)
> D d1 State: up Device /dev/da1e Avail: 0/17366 MB
>(0%)
> D d2 State: up Device /dev/da2e Avail: 0/17366 MB
>(0%)
> D d3 State: up Device /dev/da3e Avail: 0/17366 MB
>(0%)
>
> da0: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C)
> da3: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C)
> da2: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C)
> da1: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C)
>
What disk are you booting from?
Does it only happen on start or do you have problems using read too?
I have one host on which I don't use start, because one removeable drive
(SyQuest SQ5200) missbehaves reading while there is no media inserted - but it
does not panic the host - it only was trying to read from it longer than my finger
needed to reach reset...
--
B.Walter COSMO-Project http://www.cosmo-project.de
[EMAIL PROTECTED] Usergroup [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
