Detecting usb stick in freebsd

UNIX BSD
1

I inserted a 8GB usb stick in a number of machine with FreeBSD 7.1, but the medium was not detected:

$ dmesg | grep MB
usable memory = 4263022592 (4065 MB)
avail memory  = 4082540544 (3893 MB)
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
ad0: 238475MB <WDC WD2500BEVT-00ZCT0 11.01A11> at ata2-master SATA300
da0: 40.000MB/s transfers
cd0: 3.300MB/s transfers
usable memory = 4280356864 (4082 MB)
avail memory  = 4099862528 (3909 MB)
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
ad0: 238475MB <WDC WD2500BEVT-00ZCT0 11.01A11> at ata2-master SATA300
cd0: 3.300MB/s transfers
da0: 40.000MB/s transfers
usable memory = 4280356864 (4082 MB)
avail memory  = 4099862528 (3909 MB)
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
ad0: 238475MB <WDC WD2500BEVT-00ZCT0 11.01A11> at ata2-master SATA300
cd0: 3.300MB/s transfers
da0: 40.000MB/s transfers

Furthermore, the usb stick gets very hot after about 5 minutes, probably well over 50C, which is abnormal. This happens on all machines with FreeBSD. da0s1 is not available, as is da1s1 etc. So even if I could mount the stick, it is unclear where to mount it to. Perhaps someone has a suggestion?

2

Well, overheating is certainly an alarm. Can you mount another USB stick, does it work correctly ?

3

Overheating is a concern indeed, since frying data is not always an option. Is there a way to protect oneself against overheating? Checking with another usb stick, the problem seems to have disappeared.

The more pertinent problem has been why the da0s1/da1s1 etc slices were not available, even when logged in as root?

4

Here is another peculiarity when logged in as root:

# ls -l /dev | grep da
#

Why is there no mount-point?

5

whats the output of:

dmesg | grep usb
6 
# dmesg | grep usb
usb0: OHCI version 1.0, legacy support
usb0: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: <AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
usb1: OHCI version 1.0, legacy support
usb1: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: <AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
usb2: OHCI version 1.0, legacy support
usb2: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci2
usb2: USB revision 1.0
uhub2: <AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
usb3: EHCI version 1.0
usb3: companion controllers, 3 ports each: usb0 usb1 usb2
usb3: <ALi M5239 USB 2.0 controller> on ehci0
usb3: USB revision 2.0
uhub3: <AcerLabs EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb3
usb0: OHCI version 1.0, legacy support
usb0: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: <AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb0
usb1: OHCI version 1.0, legacy support
usb1: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci1
usb1: USB revision 1.0
uhub1: <AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb1
usb2: OHCI version 1.0, legacy support
usb2: <AcerLabs M5237 (Aladdin-V) USB controller> on ohci2
usb2: USB revision 1.0
uhub2: <AcerLabs OHCI root hub, class 9/0, rev 1.00/1.00, addr 1> on usb2
usb3: EHCI version 1.0
usb3: companion controllers, 3 ports each: usb0 usb1 usb2
usb3: <ALi M5239 USB 2.0 controller> on ehci0
usb3: USB revision 2.0
uhub3: <AcerLabs EHCI root hub, class 9/0, rev 2.00/1.00, addr 1> on usb3
7

I have tried several machines and since the overheating problem was confined to only one stick, it seems that the problem was in the stick to begin with. The slice I am connecting alternative sticks to is /dev/da1s1