[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
Contrary to any popular logic i normally have to drop the 1 and just do a "mount -t auto /dev/sdb /mnt/usbpen" (sda is my SATA drive, so it's sdb for me). There was a version of 2.6 kernel where USB mass storage device was hopelessly broken. Not sure which it was but worth bearing in mind. Oops, hang on. 2.6.10 should be fine, it was something like 2.6.3. I know i've used 2.6.9 and 11 with usbpens so it isn't that. If you've nothing much on there to loose would it be worth formatting it from within linux? Never tried that so don't know if it would work out or not... Martin. On Thursday 14 April 2005 22:36, Grant Sewell wrote:
Hi all. I just ordered a loverly 512MB USB 2.0 drive from Ebuyer - a nice Kingston job. Shame I can't get the thing to place nicely! The instructions clearly state that it'll work with Linux 2.4 and above... well, I'm pretty sure that 2.6.10 qualifies as "and above". Here's what happens... I plug in the device (either USB 1.1 or USB 2.0 - doesn't matter which) and the device registers itself apparently nicely: Apr 14 23:13:51 localhost kernel: usb 5-2: new high speed USB device using ehci_hcd and address 2 Apr 14 23:13:53 localhost usb.agent[14913]: usb-storage: already loaded Apr 14 23:13:53 localhost kernel: scsi4 : SCSI emulation for USB Mass Storage devices Apr 14 23:13:58 localhost kernel: Vendor: Kingston Model: DataTraveler 2.0 Rev: 6.00 Apr 14 23:13:58 localhost kernel: Type: Direct-Access ANSI SCSI revision: 02 Apr 14 23:13:58 localhost kernel: SCSI device sda: 1001472 512-byte hdwr sectors (513 MB) Apr 14 23:13:58 localhost kernel: sda: assuming Write Enabled Apr 14 23:13:58 localhost kernel: SCSI device sda: 1001472 512-byte hdwr sectors (513 MB) Apr 14 23:13:58 localhost kernel: sda: assuming Write Enabled Apr 14 23:13:58 localhost kernel: /dev/scsi/host4/bus0/target0/lun0: [CUMANA/ADFS] p1<5>Attached scsi removable disk sda at scsi4, channel 0, id 0, lun 0 Apr 14 23:13:58 localhost kernel: Attached scsi generic sg0 at scsi4, channel 0, id 0, lun 0, type 0 Apr 14 23:13:59 localhost scsi.agent[14950]: disk at /devices/pci0000:00/0000:00:0f.2/usb5/5-2/5-2:1.0/host4/target4:0:0/4:0:0:0 Apr 14 23:15:08 localhost kernel: SCSI device sda: 1001472 512-byte hdwr sectors (513 MB) Apr 14 23:15:08 localhost kernel: sda: assuming Write Enabled Apr 14 23:15:10 localhost kernel: /dev/scsi/host4/bus0/target0/lun0: [CUMANA/ADFS] p1<5>SCSI device sda: 1001472 512-byte hdwr sectors (513 MB) Apr 14 23:15:10 localhost kernel: sda: assuming Write Enabled However... I can't use it. Running "fdisk -l" as root shows the following: Disk /dev/sda: 512 MB, 512753664 bytes 16 heads, 63 sectors/track, 993 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System /dev/sda1 1 993 500440+ e W95 FAT16 (LBA) Disk /dev/sda1: 2082.3 GB, 2082317979648 bytes 16 heads, 63 sectors/track, 4034749 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System /dev/sda1p1 1 993 500440+ e W95 FAT16 (LBA) I have never seen this last entry on a Linux system before, so I'm stumped. I try "# mount -t vfat /dev/sda1 /mnt/pendrive" (pendrive does exist already) and I'm told the following: mount: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or other error In some cases useful info is found in syslog - try dmesg | tail or so And interestingly, when I try that, I get a load more messages in /var/log/messages: Apr 14 23:22:51 localhost kernel: /dev/scsi/host4/bus0/target0/lun0: [CUMANA/ADFS] p1<3>FAT: invalid media value (0xb9) Apr 14 23:22:51 localhost kernel: VFS: Can't find a valid FAT filesystem on dev sda1. /dev/sda1p1 doesn't even exist in the /dev directory, so I can't access that. Any thoughts? Cheers. Grant.
-- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe. FAQ: www.dcglug.org.uk/linux_adm/list-faq.html