----- Original Message ----- From: "Dan Finn" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, June 25, 2004 4:31 PM Subject: can't mount 300G USB drive that's FAT32
> the system sees the disk: > Jun 24 15:37:30 stewie kernel: umass0: Maxtor OneTouch, rev 2.00/2.00, addr 2 > Jun 24 15:37:30 stewie kernel: umass0: Get Max Lun not supported (STALLED) > Jun 24 15:37:31 stewie kernel: GEOM: create disk da0 dp=0xc2d85050 > Jun 24 15:37:31 stewie kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > Jun 24 15:37:31 stewie kernel: da0: <Maxtor OneTouch 0201> Fixed > Direct Access SCSI-0 device > Jun 24 15:37:31 stewie kernel: da0: 1.000MB/s transfers > Jun 24 15:37:31 stewie kernel: da0: 286103MB (585938944 512 byte > sectors: 255H 63S/T 36473C) > > this is a Maxtor 300G USB drive. A backup was written to it via a > linux 2.4 server and now I would like to mount it on my FBSD laptop to > read it and work with the files. > > When trying to mount it using mount_msdos I get the following: > [ root @ stewie : ~] : mount_msdosfs -o rw /dev/da0s1 /mnt/usb1/ > mount_msdosfs: /dev/da0s1: Invalid argument > > and in /var/log/messages I get the following: > Jun 24 15:43:52 stewie kernel: mountmsdosfs(): disk too big, sorry > > when trying to use ntfs to mount it I get : > [ root @ stewie : ~] : mount_ntfs /dev/da0s1 /mnt/usb1/ > mount_ntfs: /dev/da0s1: Invalid argument > and nothing in any log file. > > One of the taks I need to accomplish here is to copy all of the data > on this 300G USB drive onto an identical 300G USB drive. I was going > to mount both and just copy from one to the other. After reading > about the limited writing capabilities in the man page of mount_ntfs > I'm wondering if I would be better off doing this on a linux box. The > linux box that created the origional backup onto the USB drive had no > problem creating the Fat32 filesystem and writing to it. FAT32 = msdosfs. This is totally different than NTFS, so put all ideas of using mount_ntfs out of your mind since it won't help. The FAT32 support in FreeBSD currently doesn't support "large" disks. I don't know the specific value of "large", but there is some comments in the code that point at certain calculations that break for "large" disks. -- Matt Emmerton _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
