Re: zip drive problems...
On Wed, Aug 01, 2001 at 09:49:42AM +0800, Robert Storey wrote: > > > -- Forwarded Message -- > Subject: Re: zip drive problems... > Date: Wed, 1 Aug 2001 07:19:45 +0800 > From: Robert Storey <[EMAIL PROTECTED]> > To: Andy Saxena <[EMAIL PROTECTED]> > > > On Tuesday July 31 2001 04:57, Phillip Deackes wrote: > > On Mon, 30 Jul 2001 13:39:47 -0700 > > > > Sometimes the partition you need to access is /dev/sda1 rather than > > /dev/sda4. Don't know why, but I have several zip disks, some where the > > uabale partition is /dev/sda1 and others where it is /dev/sda4. Maybe it > > has something to do with whether you formatted the zipdisks using Linux > > or Windows? > > By default, Zip disks from the factory are partitioned as /dev/sda4. That's > just Iomega's standard practice, there is no technical reason why it must be > so. By using the Linux fdisk command, you can repartition a Zip disk as > /dev/sda1, /dev/sda2 or /dev/sda3. Actually, I believe this is done so that older versions of MacOS (which uses its own partition map and saves the first three partitions for system use) could use PC zip disks with the msdos fs driver installed on the mac. partition 1: Apple partition map partition 2: Apple disk driver code partition 3: Updated disk driver or free space for such partition 4: first fs partition > If you aren't already familiar with the fdisk command, it wouldn't be a bad > idea to practice with it on a Zip disk (a Zip disk with no important data on > it!). It's much safer to practice using fdisk on a Zip disk than on your hard > drive. Run "fdisk /dev/sda" and have fun playing with the menus. Once you've > changed the partition information, you may have to reformat the disk with > mkfs. Oh, and to throw a spanner into the works, the official spec for the IDE/ATAPI zip drive allows the drive to hide the first track (with the partition) table from the IDE interface and pretend that it's a single msdos fs. So if you use a disk with custom partitioning, be prepared that it might not work in an IDE zip drive. My dualboot system's BIOS sets this, so the custom Debian installer image I was playing with cannot work any longer. -- Ferret I will be switching my email addresses from @ferret.dyndns.org to @mail.aom.geek on or after September 1, 2001, but not until after Debian's servers include support. 'geek' is an OpenNIC TLD. See http://www.opennic.unrated.net for details about adding OpenNIC support to your computer, or ask your provider to add support to their name servers. pgp9gs4POpXDL.pgp Description: PGP signature
Re: zip drive problems...
-- Forwarded Message -- Subject: Re: zip drive problems... Date: Wed, 1 Aug 2001 07:19:45 +0800 From: Robert Storey <[EMAIL PROTECTED]> To: Andy Saxena <[EMAIL PROTECTED]> On Tuesday July 31 2001 04:57, Phillip Deackes wrote: > On Mon, 30 Jul 2001 13:39:47 -0700 > > Sometimes the partition you need to access is /dev/sda1 rather than > /dev/sda4. Don't know why, but I have several zip disks, some where the > uabale partition is /dev/sda1 and others where it is /dev/sda4. Maybe it > has something to do with whether you formatted the zipdisks using Linux > or Windows? By default, Zip disks from the factory are partitioned as /dev/sda4. That's just Iomega's standard practice, there is no technical reason why it must be so. By using the Linux fdisk command, you can repartition a Zip disk as /dev/sda1, /dev/sda2 or /dev/sda3. If you aren't already familiar with the fdisk command, it wouldn't be a bad idea to practice with it on a Zip disk (a Zip disk with no important data on it!). It's much safer to practice using fdisk on a Zip disk than on your hard drive. Run "fdisk /dev/sda" and have fun playing with the menus. Once you've changed the partition information, you may have to reformat the disk with mkfs. - Robert Storey ---
Re: zip drive problems...
On Tue, 31 Jul 2001, Phillip Deackes wrote: PD> Sometimes the partition you need to access is /dev/sda1 rather than PD> /dev/sda4. Don't know why, but I have several zip disks, some where the PD> uabale partition is /dev/sda1 and others where it is /dev/sda4. Maybe it PD> has something to do with whether you formatted the zipdisks using Linux or PD> Windows? factory zip disks come out with extended partition except primary, the reason for this is probably the fact that iomega people didn't wanted the zip to force it self to be second primary partition, which is not much of a problem on linux since it uses root tree filesystem. But in windows and other dos-like filesystems this can be a big problem, for example, let's say that you have 20gb drive, split in 2 partitions that normally show as C and D, on primary ide as a master, and ide zip drive as secondary slave. if you have old machine that doesn't have bios support for ide zip drives, you will be fine since you have to use windows or dos driver to get the machine to see the zip drive. now 2 things can happend if you have machine that has bios which supports zip drives: 1. you leave the zip disk with primary partition in the drive over reboot, your second hard drive partition D will be pushed to E and the zip drive will become D. at this point any windows program that has been installed on your extended hdd partition will quit working because the drive letters changed. 2. you leave zip disk with extended partition in the drive over reboot, because of the fact that the zip drive is plugged in as secondary slave, its extended partition will be the last partition in drive list, thus not pushing any other drive letters around. here is a table how dos/bios normally sorts the partitions: 1st ide master primary 1st ide slave primary 2nd ide master primary 2nd ide slave primary 1st ide master 1st extended . 1st ide master Xth extended 1st ide slave 1st extended . 1st ide slave Xth extended 2nd ide master 1st extended . 2nd ide master Xth extended 2nd ide slave 1st extended . 2nd ide slave Xth extended so the actual problem isn't which system had formatted the disk, but how the disk it self has been partitioned. Dingo. ).|.( '.'___'.' ' '(>~<)' ' -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-ooO-=(_)=-Ooo-=-=-=-=-=-=-=-=-=-=-=-=-=- Petr [Dingo] Dvorak [EMAIL PROTECTED] Coder - Purple Dragon MUD pdragon.org port -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-[ 369D93 ]=-=- Debian version 2.2.18pre21, up 2 days, 8 users, load average: 1.00 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Re: zip drive problems...
Hi! What I should have added, is that I use the USB port. I have built into the kernel usb-storage, usb-core, ide-scsi, sg, and I amalso running hotplug, usbutils, modutils. I have a mount point /zip for the drive, and here is what happens when I start up the system: scsi0 : SCSI host adapter emulation for IDE ATAPI devices scsi : 1 host. usb.c: registered new driver usbdevfs usb.c: registered new driver hub usb.c: registered new driver usb-storage USB Mass Storage support registered. eth0: Initial media type 10baseT. usb-uhci.c: $Revision: 1.237 $ time 23:10:21 Mar 13 2001 usb-uhci.c: High bandwidth mode enabled usb-uhci.c: USB UHCI at I/O 0x1040, IRQ 9 usb-uhci.c: Detected 2 ports usb.c: new USB bus registered, assigned bus number 1 usb.c: USB new device connect, assigned device number 1 hub.c: USB hub found hub.c: 2 ports detected usb.c: USB new device connect, assigned device number 2 usb-uhci.c: interrupt, status 2, frame# 856 usb-uhci.c: interrupt, status 3, frame# 857 scsi1 : SCSI emulation for USB Mass Storage devices scsi : 2 hosts. usb-uhci.c: interrupt, status 2, frame# 866 usb-uhci.c: interrupt, status 3, frame# 891 Vendor: IOMEGAModel: ZIP 100 Rev: 10.V Type: Direct-Access ANSI SCSI revision: 02 Detected scsi removable disk sda at scsi1, channel 0, id 0, lun 0 usb-uhci.c: interrupt, status 2, frame# 905 usb-uhci.c: interrupt, status 3, frame# 937 usb-uhci.c: interrupt, status 3, frame# 943 usb-uhci.c: interrupt, status 3, frame# 949 usb-uhci.c: interrupt, status 3, frame# 955 usb-uhci.c: interrupt, status 3, frame# 961 usb-uhci.c: interrupt, status 3, frame# 985 usb-uhci.c: interrupt, status 3, frame# 1059 usb-uhci.c: interrupt, status 3, frame# 1103 usb-uhci.c: interrupt, status 3, frame# 1180 usb-uhci.c: interrupt, status 3, frame# 1186 usb-uhci.c: interrupt, status 3, frame# 1195 usb-uhci.c: interrupt, status 3, frame# 1201 usb-uhci.c: interrupt, status 3, frame# 1207 usb-uhci.c: interrupt, status 3, frame# 1214 usb-uhci.c: interrupt, status 3, frame# 1220 usb-uhci.c: interrupt, status 3, frame# 1226 usb-uhci.c: interrupt, status 3, frame# 1235 usb-storage: bus_reset() requested but not implemented usb-storage: bus_reset() requested but not implemented usb-storage: host_reset() requested but not implemented usb-uhci.c: interrupt, status 3, frame# 1910 usb-uhci.c: interrupt, status 3, frame# 1916 usb-uhci.c: interrupt, status 3, frame# 1922 usb-uhci.c: interrupt, status 3, frame# 1928 usb-uhci.c: interrupt, status 3, frame# 1934 usb-uhci.c: interrupt, status 3, frame# 1940 usb-uhci.c: interrupt, status 3, frame# 1946 usb-uhci.c: interrupt, status 3, frame# 1952 usb-uhci.c: interrupt, status 3, frame# 1958 usb-uhci.c: interrupt, status 3, frame# 1964 usb-uhci.c: interrupt, status 3, frame# 1970 usb-uhci.c: interrupt, status 3, frame# 1976 usb-uhci.c: interrupt, status 3, frame# 1982 usb-uhci.c: interrupt, status 3, frame# 1988 usb-uhci.c: interrupt, status 3, frame# 1994 usb-uhci.c: interrupt, status 3, frame# 2000 usb-uhci.c: interrupt, status 3, frame# 2006 usb-uhci.c: interrupt, status 3, frame# 2012 usb-storage: bus_reset() requested but not implemented usb-storage: bus_reset() requested but not implemented usb-storage: host_reset() requested but not implemented usb-uhci.c: interrupt, status 3, frame# 627 usb-uhci.c: interrupt, status 3, frame# 633 usb-uhci.c: interrupt, status 3, frame# 639 usb-uhci.c: interrupt, status 3, frame# 645 usb-uhci.c: interrupt, status 3, frame# 651 usb-uhci.c: interrupt, status 3, frame# 657 usb-uhci.c: interrupt, status 3, frame# 663 usb-uhci.c: interrupt, status 3, frame# 669 usb-uhci.c: interrupt, status 3, frame# 675 sda : READ CAPACITY failed. sda : status = 0, message = 00, host = 7, driver = 00 sda : sense not available. sda : block size assumed to be 512 bytes, disk size 1GB. sda:scsidisk 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 The Zip disk is an unused Windows formatted disk. I am lost - where do I go from here.. Thanks! JTLarsen "Gilger.John" wrote: > 1. Do you have a disk installed? > > 2. Did you add ppa or imm and parport_pc support when you compiled your > kernal? Or did you insert (insmod) those modules? > > 3. Does your sysstem recognize the zip drive on boot? > > John Gilger > > -Original Message- > From: Joern T. Larsen [mailto:[EMAIL PROTECTED] > Sent: Monday, July 30, 2001 01:40 PM > To: debian-user@lists.debian.org > Subject: zip drive problems... > > When I try do mount my zip drive > > mount /dev/sda4 /zip > > I get the message > > mount: /dev/sda4 is not a valid block device. > > What am I missing. > > Thanks! > > JTLarsen begin:vcard n:Larsen;Joern T. tel;fax:(510) 486 7797 tel;work:(510) 495 2407 x-mozilla-html:FALSE org:Lawrence Berkeley National Laboratory;ES
Re: zip drive problems...
On Tuesday July 31 2001 04:57, Phillip Deackes wrote: > On Mon, 30 Jul 2001 13:39:47 -0700 > > Sometimes the partition you need to access is /dev/sda1 rather than > /dev/sda4. Don't know why, but I have several zip disks, some where the > uabale partition is /dev/sda1 and others where it is /dev/sda4. Maybe it > has something to do with whether you formatted the zipdisks using Linux or > Windows? And that is correct :). It's a filesystem thing. -Andy
Re: zip drive problems...
On Mon, 30 Jul 2001 13:39:47 -0700 "Joern T. Larsen" <[EMAIL PROTECTED]> wrote: > When I try do mount my zip drive > > mount /dev/sda4 /zip > > I get the message > > mount: /dev/sda4 is not a valid block device. > > What am I missing. Sometimes the partition you need to access is /dev/sda1 rather than /dev/sda4. Don't know why, but I have several zip disks, some where the uabale partition is /dev/sda1 and others where it is /dev/sda4. Maybe it has something to do with whether you formatted the zipdisks using Linux or Windows? -- Phillip Deackes Using Progeny Debian Linux
Re: zip drive problems...
Gilger.John wrote on Mon Jul 30, 2001 at 01:48:34PM: > Joern T. Larsen: >> mount: /dev/sda4 is not a valid block device. > > 2. Did you add ppa or imm and parport_pc support when you compiled your > kernal? Or did you insert (insmod) those modules? ... and you need sd_mod as well ... ppa / imm is for the drive, sd_mod is fro the disk. Matth¡as -- Matthias Richter --+- stud. soz. & inf. -+-- http://www.uni-leipzig.de -->GPG Public Key: http://www.matthias-richter.de/gpg.ascii<-- · Projekt Deutscher Wortschatz: http://wortschatz.uni-leipzig.de> pgpYN1UtKG82l.pgp Description: PGP signature
RE: zip drive problems...
1. Do you have a disk installed? 2. Did you add ppa or imm and parport_pc support when you compiled your kernal? Or did you insert (insmod) those modules? 3. Does your sysstem recognize the zip drive on boot? John Gilger -Original Message- From: Joern T. Larsen [mailto:[EMAIL PROTECTED] Sent: Monday, July 30, 2001 01:40 PM To: debian-user@lists.debian.org Subject: zip drive problems... When I try do mount my zip drive mount /dev/sda4 /zip I get the message mount: /dev/sda4 is not a valid block device. What am I missing. Thanks! JTLarsen
zip drive problems...
When I try do mount my zip drive mount /dev/sda4 /zip I get the message mount: /dev/sda4 is not a valid block device. What am I missing. Thanks! JTLarsen begin:vcard n:Larsen;Joern T. tel;fax:(510) 486 7797 tel;work:(510) 495 2407 x-mozilla-html:FALSE org:Lawrence Berkeley National Laboratory;ESD - Earth Science Division adr:;;1 Cyclotron Road, Bldg 70-114, MS 70-108B;Berkeley;California;CA 94720; version:2.1 email;internet:[EMAIL PROTECTED] title:Research Associate x-mozilla-cpt:;11392 fn:Joern T. Larsen end:vcard
Zip Drive Problems
I had a system crash and after a reinstall Problems with the Zip Drive. The Zip Drive 100 was working before the crash. Now when I try to mount the Zip DriveI get the following: [EMAIL PROTECTED]:~ > mount /zip mount: only root can mount /dev/sda1 on /zip [EMAIL PROTECTED]:/home/clay > mount /zip mount: the kernel does not recognize /dev/sda1 as a block device (maybe `insmod driver'?) What has to be done to get the kernel to recognize the Zip Drive as a block device? The permission for /dev/sda1 was chaged from group disk to users and I am in the users group. This is part of "dmesg": parport0: PC-style at 0x378 (0x778) [SPP,ECP,ECPEPP,ECPPS2] parport_probe: succeeded parport0: Printer, HEWLETT-PACKARD DESKJET 660C ppa: Version 2.03 (for Linux 2.2.x) WARNING - no ppa compatible devices found. As of 31/Aug/1998 Iomega started shipping parallel port ZIP drives with a different interface which is supported by the imm (ZIP Plus) driver. If the cable is marked with "AutoDetect", this is what has happened. lp0: using parport0 (polling). And this is a part of "lsmod ppa": [EMAIL PROTECTED]:/home/clay > lsmod ppa Module Size Used by lp 6020 0 (unused) parport_probe 3492 0 (autoclean) parport_pc 7440 1 (autoclean) parport 7432 1 [lp parport_probe parport_pc]
ZIp drive problems
When I was moving to my new computer, I backed up all my linux data onto a ZIP disk, since I had that working with my old computer. I figured it wouldn't be too hard to set this up for my new computer (formatted the ZIP disk to linux format). Anyhow, I've compiled the Kernel 2.2.5 verision (identical to before) and selected the options necessary for ZIP disk support (SCSI support, scsi disk support, Iomega zip support, and printer support. Kernel compile goes fine, lalalla. I reboot, and then try to connect the ZIP drive. Here's the error messages I get: if I type "mount -t ext2 /dev/sda4 /Zip" I get: The kernel does not recognize /dev/sda4 as a block device (I think that's correct...) if i type "insmod ppa" (other modules load just fine or are built into the kernel) I get: ppa: Version 2.04 (for linux 2.2.x) ppa: parport reports no devices scsi: 0 hosts /lib/modules/2.2.5/scsi/ppa.0 init_module: Device or resource busy I get these error messages no matter what order I toss them in, weither the ZIP drive is conencted on boot, or what not. Being the linux newbie that I am, I'm sort of at a lost. Can anyone help me, so I can get back to a working os?:) Jon
