On Sat, May 31, 2008 at 10:27:50AM +0200, Colin Brace wrote: > > On Sat, 31 May 2008 09:29:55 +0200, Roland Smith <[EMAIL PROTECTED]> wrote: > > > Can you show us what is shown in the dmesg output when you plug this > > drive in, which devices are then created and the exact command that you > > used to mount it? > > dmesg: > > [...] > umass0: on uhub1 > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 1.000MB/s transfers > da0: 194481MB (398297088 512 byte sectors: 255H 63S/T 24792C) > > These nodes are created: > > # ls -1 /dev/da* > /dev/da0 > /dev/da0s1 > /dev/da0s1c > > Then: > > # mount /dev/da0s1c /media/disk6 > mount: /dev/da0s1c : Invalid argument
This is caused by the nmount system call returning EINVAL. Quoting from
mount(2):
[EINVAL] The super block for the file system had a bad magic
number or an out of range block size.
After partitioning and labeling the disk, did you make filesystems on
the partitions with newfs?
Roland
--
R.F.Smith http://www.xs4all.nl/~rsmith/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725)
pgpL6c9GBu9gY.pgp
Description: PGP signature
