Nagging Zip Drive problem--will not mount
Hi folks! I have an old external Zip-100 Parallel Port drive that I cannot get mounted on my 8.0 system (Kernel 2.4.18-4GB). The other night I tried again. YaST2 hardware info shows the drive and gives it a mount point of /dev/sda. I edited fstab to point to /dev/sda and added a pointer to the /mnt directory. When I attempt to mount this (via KDE or bash), I get the following error: "mount: /dev/sda is not a valid block device." The help (more than a little dated, I suspect, since it was written for v6.3) suggests running modprobe for ppa. Here's what happens: /lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o: insmod /lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o failed /lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o: insmod ppa failed Any and all thoughts greatly appreciated. Many thanks! -- Mike McCallister ProTek Writing Services workingwriter@prodigy.net "Translation from the Geek a specialty" Phone: (262) 938-9505 Fax: (248) 282-0532 Notes from the Metaverse: http://radio.weblogs.com/0124049
On Tuesday 03 June 2003 11:44 am, Mike McCallister wrote:
Hi folks!
I have an old external Zip-100 Parallel Port drive that I cannot get mounted on my 8.0 system (Kernel 2.4.18-4GB). The other night I tried again. YaST2 hardware info shows the drive and gives it a mount point of /dev/sda. I edited fstab to point to /dev/sda and added a pointer to the /mnt directory. When I attempt to mount this (via KDE or bash), I get the following error: "mount: /dev/sda is not a valid block device."
The help (more than a little dated, I suspect, since it was written for v6.3) suggests running modprobe for ppa. Here's what happens:
/lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o: insmod /lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o failed /lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o: insmod ppa failed
Any and all thoughts greatly appreciated. Many thanks!
--
What info, about the zip, is in your fstab? Mine uses sda4 for pc zips, but then again mine is a scsi. I forget the logic behind it but i found it in the archives awhile ago. Here's the line from my fstab ... /dev/sda4 /media/zip auto noauto,user 0 0 HTH
I ditched the "sync" item--no change. REverted to "auto" from "msdos" and got "you must specify filesystem type". Feeling like I'm getting close... Mike On Tuesday 03 June 2003 10:53 am, Franklin Maurer wrote:
--
What info, about the zip, is in your fstab? Mine uses sda4 for pc zips, but then again mine is a scsi. I forget the logic behind it but i found it in the archives awhile ago. Here's the line from my fstab ... /dev/sda4 /media/zip auto noauto,user 0 0 HTH
-- Mike McCallister ProTek Writing Services workingwriter@prodigy.net "Translation from the Geek a specialty" Phone: (262) 938-9505 Fax: (248) 282-0532 Notes from the Metaverse: http://radio.weblogs.com/0124049
I am wondering what was changed in SUSE to make this a problem. In 7.3 personal the zip drive was not only recognized but mounts on click in KDE 2 without a problem. I did no direct config file editing. As I intend to continue using the drive I am wondering If I should keep this one setup as is and put 8.2 on the other box. Of course I didnt do a custome install but let the system do what it needed. What config file should I study in 7.3 to see what went right? CWSIV ________________________________________________________________ The best thing to hit the internet in years - Juno SpeedBand! Surf the web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today!
CWSIV, While I can't speak with certainty, I'm thinking you probably have nothing to worry about. I did not have the zip drive attached when I installed 8.0, but I did plug it in later. Have to admit this was one of those times when I missed having Windows go "Oh, there's some new peripheral attached. Do I have a driver?" I've never really had a problem with SuSE not recognizing hardware on install, going back to v5.3. Just afterwards. Mike On Tuesday 03 June 2003 1:30 pm, Carl William Spitzer IV wrote:
I am wondering what was changed in SUSE to make this a problem. In 7.3 personal the zip drive was not only recognized but mounts on click in KDE 2 without a problem. I did no direct config file editing.
As I intend to continue using the drive I am wondering If I should keep this one setup as is and put 8.2 on the other box.
Of course I didnt do a custome install but let the system do what it needed.
What config file should I study in 7.3 to see what went right?
CWSIV
________________________________________________________________ The best thing to hit the internet in years - Juno SpeedBand! Surf the web up to FIVE TIMES FASTER! Only $14.95/ month - visit www.juno.com to sign up today!
-- Mike McCallister ProTek Writing Services workingwriter@prodigy.net "Translation from the Geek a specialty" Phone: (262) 938-9505 Fax: (248) 282-0532 Notes from the Metaverse: http://radio.weblogs.com/0124049
Mike McCallister wrote:
Hi folks!
I have an old external Zip-100 Parallel Port drive that I cannot get mounted on my 8.0 system (Kernel 2.4.18-4GB). The other night I tried again. YaST2 hardware info shows the drive and gives it a mount point of /dev/sda. I edited fstab to point to /dev/sda and added a pointer to the /mnt directory. When I attempt to mount this (via KDE or bash), I get the following error: "mount: /dev/sda is not a valid block device."
The help (more than a little dated, I suspect, since it was written for v6.3) suggests running modprobe for ppa. Here's what happens:
/lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o: insmod /lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o failed /lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o: insmod ppa failed
Try: modprobe imm -Stathis.
Yes, that worked, but now my fstab entry apparently is not right. Here's what I have: /dev/sda /media/zip msdos noauto,user,sync 0 0 Shell now complains: mount: wrong fs type, bad option, bad superblock on /dev/sda, or too many mounted file systems I also tried vfat, but that didn't work either. More hints? Mike On Tuesday 03 June 2003 10:55 am, Rouvas Stathis wrote:
Mike McCallister wrote:
Hi folks!
I have an old external Zip-100 Parallel Port drive that I cannot get mounted on my 8.0 system (Kernel 2.4.18-4GB). The other night I tried again. YaST2 hardware info shows the drive and gives it a mount point of /dev/sda. I edited fstab to point to /dev/sda and added a pointer to the /mnt directory. When I attempt to mount this (via KDE or bash), I get the following error: "mount: /dev/sda is not a valid block device."
The help (more than a little dated, I suspect, since it was written for v6.3) suggests running modprobe for ppa. Here's what happens:
/lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o: insmod /lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o failed /lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o: insmod ppa failed
Try:
modprobe imm
-Stathis.
-- Mike McCallister ProTek Writing Services workingwriter@prodigy.net "Translation from the Geek a specialty" Phone: (262) 938-9505 Fax: (248) 282-0532 Notes from the Metaverse: http://radio.weblogs.com/0124049
Mike McCallister wrote:
Yes, that worked, but now my fstab entry apparently is not right. Here's what I have: /dev/sda /media/zip msdos noauto,user,sync 0 0
Shell now complains: mount: wrong fs type, bad option, bad superblock on /dev/sda, or too many mounted file systems
I also tried vfat, but that didn't work either.
More hints?
"mount /dev/sda4 /mnt", perhaps (as root)? -Stathis
Mike
On Tuesday 03 June 2003 10:55 am, Rouvas Stathis wrote:
Mike McCallister wrote:
Hi folks!
I have an old external Zip-100 Parallel Port drive that I cannot get mounted on my 8.0 system (Kernel 2.4.18-4GB). The other night I tried again. YaST2 hardware info shows the drive and gives it a mount point of /dev/sda. I edited fstab to point to /dev/sda and added a pointer to the /mnt directory. When I attempt to mount this (via KDE or bash), I get the following error: "mount: /dev/sda is not a valid block device."
The help (more than a little dated, I suspect, since it was written for v6.3) suggests running modprobe for ppa. Here's what happens:
/lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o: init_module: No such device Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters /lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o: insmod /lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o failed /lib/modules/2.4.18-4GB/kernel/drivers/scsi/ppa.o: insmod ppa failed
Try:
modprobe imm
-Stathis.
-- Rouvas Stathis rouvas@di.uoa.gr http://www.di.uoa.gr/~rouvas
On Tue, Jun 03, 2003 at 11:15:53AM -0500, Mike McCallister wrote:
Yes, that worked, but now my fstab entry apparently is not right. Here's what I have: /dev/sda /media/zip msdos noauto,user,sync 0 0
You need a partition number. Probably /dev/sda4 unless you specifically changed it yourself... "auto" for the type should work, too...
Thank you Michael, Franklin. and (especially, for the correct modprobe command) Rouvas We are now in business! Mike On Tuesday 03 June 2003 11:56 am, Michael George wrote:
On Tue, Jun 03, 2003 at 11:15:53AM -0500, Mike McCallister wrote:
Yes, that worked, but now my fstab entry apparently is not right. Here's what I have: /dev/sda /media/zip msdos noauto,user,sync 0 0
You need a partition number. Probably /dev/sda4 unless you specifically changed it yourself...
"auto" for the type should work, too...
-- Mike McCallister ProTek Writing Services workingwriter@prodigy.net "Translation from the Geek a specialty" Phone: (262) 938-9505 Fax: (248) 282-0532 Notes from the Metaverse: http://radio.weblogs.com/0124049
On Tuesday 03 June 2003 11:15, Mike McCallister wrote:
Yes, that worked, but now my fstab entry apparently is not right. Here's what I have: /dev/sda /media/zip msdos noauto,user,sync 0 0
Shell now complains: mount: wrong fs type, bad option, bad superblock on /dev/sda, or too many mounted file systems
I also tried vfat, but that didn't work either.
More hints?
IIRC, the DOS partition on Zip disks would be #4, do try sda4. -- JAY VOLLMER JVOLLMER@CONSOLIDATEDLINT.COM TEXT REFS DOUBLEPLUSUNGOOD SELFTHINK VERGING CRIMETHINK IGNORE FULLWISE
On Tuesday 03 June 2003 12:02, Jay Vollmer wrote:
On Tuesday 03 June 2003 11:15, Mike McCallister wrote:
Yes, that worked, but now my fstab entry apparently is not right. Here's what I have: /dev/sda /media/zip msdos noauto,user,sync 0 0
Shell now complains: mount: wrong fs type, bad option, bad superblock on /dev/sda, or too many mounted file systems
I also tried vfat, but that didn't work either.
I get this error sporadically on my Suse 8.0 box when trying to mount CF cards via a Lexar Firewire CF Reader. I have also encountered it with the same reader on Suse 8.2. They tend to mount fine on my Suse 7.1 laptop with a ZIO USB 1.1 CF reader(same card, just seconds after it didn't work in the later OS version!) I've gotten around it my doing this: (Kinda scary, but it works every time and I haven't had any problems yet) sudo fdisk /dev/sdb n # for create a new partition p # create a primary partition 1 # for first partition [enter] # take the entry for first cylinder [enter] # take the entry for last cylinder v # verify w # write and exit next I do a 'mount /cf' and all is fine. NOTE: I do have the filesystem type in the /etc/fstab file set to 'auto' Wait a minute! You have the device set in youir /etc/fstab to /dev/sda. That's not going to mount. Change it to /dev/sda1 and see if it works. -- Brian Jackson, President Action Athletics "Sports Photography for You" http://www.actionathletics.com
The 03.06.03 at 10:44, Mike McCallister wrote:
I have an old external Zip-100 Parallel Port drive that I cannot get mounted on my 8.0 system (Kernel 2.4.18-4GB). The other night I tried again. YaST2
modprobe imm Then, in fstab, I have: /dev/sda1 /media/zip auto defaults,noauto,user,exec /dev/sda4 /media/zip2 auto defaults,noauto,user,exec Partition 4 is for FAT formated zips (as shipped by the maker). Partition 1 I use for ext2. You could use fdisk on /dev/sda to check for the partitions you have: the disk you are trying could be different, or it could be uninitialized. -- Cheers, Carlos Robinson
participants (8)
-
Brian Jackson
-
Carl William Spitzer IV
-
Carlos E. R.
-
Franklin Maurer
-
Jay Vollmer
-
Michael George
-
Mike McCallister
-
Rouvas Stathis