Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When I was back on Mandrake 10, I could get to my ZIP drive (attached through a USB port), now on Slackware 10, it seems to know it's there if I open the Info Center (USB Devices section). However, going into /mnt/fstab doesn't show anything and neither does anywhere else. I need to know how to get it to detect and access it. Any ideas?
Quote:
USB Zip 100
Manufacturer: Iomega
Serial #: 00334BC3E6D60214
Class
0
((Defined at Interface level))
Subclass
0
Protocol
0
USB Version
1.16
Vendor ID
0x59b
(Iomega Corp.)
Product ID
0x33
Revision
3.0
Clear Reset............................................................................................... .................................................................................................... .................................................................................................... .................................................................................................... .................................................................................................... .......;
pci_cor : reg = 0x0 - 609 - 5D7
eth2: Station identity 001f:0006:0001:0003
eth2: Looks like an Intersil firmware version 1.3.6
eth2: Ad-hoc demo mode supported
eth2: IEEE standard IBSS ad-hoc mode supported
eth2: WEP supported, 104-bit key
eth2: MAC address 00:05:5D:F9:D2:D0
eth2: Station name "Prism I"
eth2: ready
hub.c: new USB device 00:10.3-1, assigned address 2
usb.c: USB device 2 (vend/prod 0x58f/0x9360) is not claimed by any active driver.
hub.c: new USB device 00:10.1-2, assigned address 2
usb.c: USB device 2 (vend/prod 0x3f0/0x6204) is not claimed by any active driver.
Initializing USB Mass Storage driver...
usb.c: registered new driver usb-storage
scsi1 : SCSI emulation for USB Mass Storage devices
Vendor: Generic Model: USB SD Reader Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sda at scsi1, channel 0, id 0, lun 0
sda: Unit Not Ready, sense:
Info fld=0x0, Current 00:00: sns = f0 2
ASC=3a ASCQ= 0
Raw sense data:0xf0 0x00 0x02 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00
sda : READ CAPACITY failed.
sda : status = 1, message = 00, host = 0, driver = 08
Info fld=0x0, Current sd00:00: sns = f0 2
ASC=3a ASCQ= 0
Raw sense data:0xf0 0x00 0x02 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x3a 0x00 0x00 0x00 0x00 0x00
sda : block size assumed to be 512 bytes, disk size 1GB.
sda: I/O error: dev 08:00, sector 0
I/O error: dev 08:00, sector 0
unable to read partition table
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
USB Mass Storage support registered.
usb.c: registered new driver usblp
printer.c: usblp0: USB Bidirectional printer dev 2 if 0 alt 0 proto 2 vid 0x03F0 pid 0x6204
printer.c: v0.13: USB Printer Device Class driver
eth1: link down
eth2: New link status: Connected (0001)
eth2: New link status: Disconnected (0002)
eth2: New link status: Connected (0001)
NET4: AppleTalk 0.18a for Linux NET4.0
hub.c: new USB device 00:10.2-2, assigned address 2
scsi2 : SCSI emulation for USB Mass Storage devices
Vendor: IOMEGA Model: ZIP 100 Rev: 27.O
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0
sdb: Unit Not Ready, sense:
Current 00:00: sns = 70 2
ASC= 4 ASCQ= 2
Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x12 0x00 0x00 0x00 0x00 0x04 0x02 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
sdb : READ CAPACITY failed.
sdb : status = 1, message = 00, host = 0, driver = 08
Current sd00:00: sns = 70 2
ASC= 4 ASCQ= 2
Raw sense data:0x70 0x00 0x02 0x00 0x00 0x00 0x00 0x12 0x00 0x00 0x00 0x00 0x04 0x02 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
sdb : block size assumed to be 512 bytes, disk size 1GB.
sdb: I/O error: dev 08:10, sector 0
I/O error: dev 08:10, sector 0
unable to read partition table
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
scsi2 : SCSI emulation for USB Mass Storage devices
Vendor: IOMEGA Model: ZIP 100 Rev: 27.O
Type: Direct-Access ANSI SCSI revision: 02
Attached scsi removable disk sdb at scsi2, channel 0, id 0, lun 0
The device is /dev/sdb4. You can add an entry to the fstab file:
/dev/sdb4 /mnt/zip vfat noauto,umask=000 0 0
I'm getting a pretty funky error from this, first off let me show you how I edited fstab...
Quote:
/dev/sdb4 /mnt/zip vfat noauto,umask= 000 0 0
I've also had it to where it reads
Quote:
/dev/sdb4 /mnt/zip vfat noauto,umask=000 0 0
And yes, I rebooted after editing and saving this file. Now the icon appears on the desktop, but when click on it, it begins
to try to read it from "Source:/mnt/zip" then it gives me the error dialouge containing the message
Quote:
mount: mount point /mnt/zip does not exist
Please check that the disk is entered correctly.
I'm pretty sure it's just something dumb I did in fstab, then again maybe the ZIP drive is being iffy?
Alright, that's solved half of the problem, now it tells me that writing to devices is not supported (I have the same problem with my windows
harddrives).
I was able to read the files that were previously on the ZIP Drive and delete them, however I now cannot write anything to the disk.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.