Re: Mounting USB-stick

2005-04-24 Thread Fridtjof Busse
* Mike Jeays [EMAIL PROTECTED]:
  Now I have /dev/da0, but no /dev/da0s1.
  No matter what I try with camcontrol, I don't get da0s1.
  By accident I found out that after I mount /dev/da0 (which of course
  doesn't give me any files on the stick) and umount it, I get /dev/
  da0s1. What's going on/wrong and how can I fix it? I don't need
  amd, so I'd be happy about a simple solution, if there's any.
  Thanks! :)
 
 Run fdisk on the drive, and see where the partitions are.  I have
 found cases where the fourth partition holds the data, and you can
 mount it with 'mount -t msdos /dev/da0s4 /mnt'.  Running fdisk with
 no parameters won't do any damage - but see below.

 In other cases of trouble, try 'camcontrol devlist' to get a list of
 which device numbers have been assigned.  It isn't always da0.

As I've already written: da0s1 is correct, but it only appears if I run
'mount_msdosfs /dev/da0 /mnt  umount /mnt' before.
Otherwise there's only /dev/da0, nothing else. Then I can mount 
/dev/da0s1. 
I'd just like to know how I can mount da0s1 without having to mount the
device itself first. The partition is there and works fine under Linux
and FreeBSD, but FreeBSD doesn't see it at first. camcontrol lists the
device as soon as I plug it in ('scbus 1 target 0 lun 0 (pass0,da0)'),
but da0s1 won't appear before I use the above workaround.

-- 
Fridtjof Busse
   It's psychosomatic. You need a lobotomy. I'll get a saw.
  -- Calvin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Mounting USB-stick

2005-04-24 Thread Dan Olson

Fridtjof Busse wrote:
* Mike Jeays [EMAIL PROTECTED]:
Now I have /dev/da0, but no /dev/da0s1.
No matter what I try with camcontrol, I don't get da0s1.
By accident I found out that after I mount /dev/da0 (which of course
doesn't give me any files on the stick) and umount it, I get /dev/
da0s1. What's going on/wrong and how can I fix it? I don't need
amd, so I'd be happy about a simple solution, if there's any.
Thanks! :)
Run fdisk on the drive, and see where the partitions are.  I have
found cases where the fourth partition holds the data, and you can
mount it with 'mount -t msdos /dev/da0s4 /mnt'.  Running fdisk with
no parameters won't do any damage - but see below.
In other cases of trouble, try 'camcontrol devlist' to get a list of
which device numbers have been assigned.  It isn't always da0.

As I've already written: da0s1 is correct, but it only appears if I run
'mount_msdosfs /dev/da0 /mnt  umount /mnt' before.
Otherwise there's only /dev/da0, nothing else. Then I can mount 
/dev/da0s1. 
I'd just like to know how I can mount da0s1 without having to mount the
device itself first. The partition is there and works fine under Linux
and FreeBSD, but FreeBSD doesn't see it at first. camcontrol lists the
device as soon as I plug it in ('scbus 1 target 0 lun 0 (pass0,da0)'),
but da0s1 won't appear before I use the above workaround.

For me to get da0s1 to appear I use the command:
cat /dev/null  /dev/da0
I think there is a timing issue with my device, a Kingston Elite.
Dan Olson
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Mounting USB-stick

2005-04-24 Thread Fridtjof Busse
* Dan Olson [EMAIL PROTECTED]:
 For me to get da0s1 to appear I use the command:
 
 cat /dev/null  /dev/da0
 
 I think there is a timing issue with my device, a Kingston Elite.

Great, thanks, that works for me as well.
I also found out it works if the stick is plugged in at boot time.
After all, it looks like a bug to me, at least I never had any problems
with the stick (Dell Memory Key) on Linux.
Is there already a report about this (didn't find anything at a first
glance)? Is it worth a bugreport?

BTW: Changing USB_PORT_POWERUP_DELAY to 1000 in /usr/src/sys/dev/usb/
usb.h didn't help. Maybe something else I could try?

-- 
Fridtjof Busse
printk(MASQUERADE: No route: Rusty's brain broke!\n);
linux-2.4.3/net/ipv4/netfilter/ipt_MASQUERADE.c
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Mounting USB-stick

2005-04-23 Thread Mike Jeays
On Sat, 2005-04-23 at 15:41, Fridtjof Busse wrote:
 Hi
 I've got a problem with mounting a USB-stick on FreeBSD 5.4-RC3 (and
 according to google I'm not the only one, but noone seems to have had
 the problem I have):
 If I plug the stick in, I get lots of
 
 Apr 23 21:26:08 fbsd kernel: (da0:umass-sim0:0:0:0): CAM Status: SCSI
 Status Error
 Apr 23 21:26:08 fbsd kernel: (da0:umass-sim0:0:0:0): SCSI Status:
 Check Condition
 Apr 23 21:26:08 fbsd kernel: (da0:umass-sim0:0:0:0): UNIT ATTENTION
 asc:3a,0 
 Apr 23 21:26:08 fbsd kernel: (da0:umass-sim0:0:0:0): Medium not
 present 
 Apr 23 21:26:08 fbsd kernel: (da0:umass-sim0:0:0:0): Retrying
 Command (per Sen se Data) 
 Apr 23 21:26:08 fbsd kernel: (da0:umass-sim0:0:0:0): READ CAPACITY.
 CDB: 25 0 0 0 0 0 0 0 0 0 
 [...]
 
 It ends with
 
 Apr 23 21:26:08 fbsd kernel: (da0:umass-sim0:0:0:0): Retries Exhausted
 Apr 23 21:26:08 fbsd kernel: Opened disk da0 - 6
 
 Now I have /dev/da0, but no /dev/da0s1.
 No matter what I try with camcontrol, I don't get da0s1.
 By accident I found out that after I mount /dev/da0 (which of course
 doesn't give me any files on the stick) and umount it, I get /dev/da0s1.
 What's going on/wrong and how can I fix it? I don't need amd, so I'd be
 happy about a simple solution, if there's any.
 Thanks! :)

Run fdisk on the drive, and see where the partitions are.  I have found
cases where the fourth partition holds the data, and you can mount it
with 'mount -t msdos /dev/da0s4 /mnt'.  Running fdisk with no parameters
won't do any damage - but see below.

In other cases of trouble, try 'camcontrol devlist' to get a list of
which device numbers have been assigned.  It isn't always da0.

(As a digression, I experimented with recreating partition tables using
fdisk and a configuration file, until the day I forgot to enter the
'da0' as the final parameter, and it wiped the disk partition on my
dual-boot system disk.  Easily the worst case of finger trouble I have
had to date).


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]