how to create da* device?

[Peter]

--- "Conrad J. Sabatier" <conrads at cox.net> wrote:

> On Tue, 28 Mar 2006 01:51:41 -0500 (EST)
> Peter <petermatulis at yahoo.ca> wrote:
> 
> > I am still trying to get my USB hard drive to work.  It used to
> work
> > but now when I plug it in all I get is:
> > 
> > kernel: umass0: PI-036 USB2.0 Drive, rev 2.00/0.01, addr 2
> > kernel: umass0: Get Max Lun not supported (STALLED)
> > 
> > I remember such messages before but after them there were some more
> > meesages beginning with "da0".  But now no da* device is created
> under
> > /dev.
> > 
> > I figured maybe this (new) drive has gone bad but it works under
> > Windows 2000.  Any ideas why this has stopped working?  I did not
> > change anything on my system although I just updated my sources and
> > baked a new kernel without success (same results).
> 
> Updating your sources and building *only* a new kernel without also
> building world is never a good idea.  Your kernel and world are most
> likely out of sync right now, perhaps even critically so.
> 
> I just added an external USB/firewire drive myself, which is working
> fine.  The kernel options I added to support the device are:
> 
> device		da
> device		ehci
> device		ohci
> device		pass
> device		ugen
> device		uhci
> device		umass
> device		usb
> 
> Hope this helps.

I heeded your warning on keeping userland and kernel in sync (I have
the kernel options/devices you mention).  Not that I thought that it
would help my predicament but still this drive cannot be mounted.  When
I plug it in after booting it is probed and recognized:

kernel: umass0: PI-036 USB2.0 Drive, rev 2.00/0.01, addr 2
kernel: umass0: Get Max Lun not supported (STALLED)
kernel: da0 at umass-sim0 bus 0 target 0 lun 0
kernel: da0: <WDC WD20 00JB-00KFA0 \0000\0000> Fixed Direct Access
SCSI-0 device 
kernel: da0: 40.000MB/s transfers
kernel: da0: 190782MB (390721968 512 byte sectors: 255H 63S/T 24321C)

I have da0 and da0s1 under /dev.

Now if I do 'sysinstall' I get:

Mar 29 13:25:48 sonata kernel: umass0: BBB reset failed, IOERROR
Mar 29 13:25:48 sonata kernel: umass0: BBB bulk-in clear stall failed,
IOERROR
Mar 29 13:25:48 sonata kernel: umass0: BBB bulk-out clear stall failed,
IOERROR
Mar 29 13:25:48 sonata kernel: umass0: BBB reset failed, IOERROR
Mar 29 13:25:48 sonata kernel: umass0: BBB bulk-in clear stall failed,
IOERROR
Mar 29 13:25:48 sonata kernel: umass0: BBB bulk-out clear stall failed,
IOERROR
Mar 29 13:25:48 sonata kernel: umass0: BBB reset failed, IOERROR
Mar 29 13:25:48 sonata kernel: umass0: BBB bulk-in clear stall failed,
IOERROR
Mar 29 13:25:48 sonata kernel: umass0: BBB bulk-out clear stall failed,
IOERROR
Mar 29 13:25:48 sonata kernel: umass0: BBB reset failed, IOERROR
Mar 29 13:25:48 sonata kernel: umass0: BBB bulk-in clear stall failed,
IOERROR
Mar 29 13:25:48 sonata kernel: umass0: BBB bulk-out clear stall failed,
IOERROR
Mar 29 13:25:48 sonata kernel: umass0: BBB reset failed, IOERROR
Mar 29 13:25:48 sonata kernel: umass0: BBB bulk-in clear stall failed,
IOERROR
Mar 29 13:25:48 sonata kernel: umass0: BBB bulk-out clear stall failed,
IOERROR
Mar 29 13:25:48 sonata kernel: Opened disk da0 -> 5

And there are no more da0* under /dev.

Now!  I boot up with knoppix and the thing is automatically mounted and
I can enter and view its contents.  And as stated in a previous post, I
can also use this drive with Windows 2000.

Any suggestions?

p.s. Is there any chance that having an identical drive can mess up the
works somehow?  Like FreeBSD can get confused?  Because I have the same
model and it worked.  I cannot test again now because it is at another
location.  And at that location this problem drive also ceased to function.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com