Go Back   openSUSE Forums > Archives > SF Archives > ARCHIVES - Miscellaneous
Forums FAQ Members List Search Today's Posts Mark Forums Read

ARCHIVES - Miscellaneous Questions about SUSE Linux that don't fit anywhere else

 
Page 1 of 2 1 2
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 07-Jan-2005, 01:49
jrev
Guest
 
Posts: n/a
Post

hi all,
My internal ZIP 100 has been OK with Suse 9.1 & kde 3.2.1...

But suddenly the /dev/hdd4 block disapeared from the dev folder



when I type : # mount /dev/hdd4 I got :
mount: block device /dev/hdd4 is write-protected, mounting read-only
mount: cannot mount block device /dev/hdd4 read-only

this is how this Zip100 reader has been installed :
Configuration : in the /media folder I created a new folder named "zip", this folder belongs to root and has permissions chmod 777 (same as floppy)
I added the following line in /etc/fstab :
/dev/hdd4 /media/zip auto auto,rw,user,uid=1000,umask=000 00
and everything was fine
I created a bash script to mount/umount this reader with one clic on the desktop it has been working for months, and then suddenly there is no more trace of this reader in Yast/hardware /hardware informations
I am very much interested to read your comments
see: http://www.trustonme.net/forum/public/post...at=1&topic=4466

thanks
  #2 (permalink)  
Old 07-Jan-2005, 04:04
giel
Guest
 
Posts: n/a
Default

I remember that I had a similar problem with my internal zipdrive. Probably after an update the zip is assigned to a different device. As far as I remembered I had to change /dev/hdd4 to hdd0 or hdd1. I don't remember exactly. Just try mounting your zip in a terminal. Fiind out which device is linked to your zip
  #3 (permalink)  
Old 07-Jan-2005, 05:43
jrev
Guest
 
Posts: n/a
Post

I think no device is linked and there is no mention of this drive in :
Yast/hardware /hardwareinformations
so how do I start my fault tracing ?
they said : you are not with windows => no need to reinstall everything
so my question :
what am I gone do now ?
  #4 (permalink)  
Old 07-Jan-2005, 07:17
giel
Guest
 
Posts: n/a
Default

unless there is a reason to assume that your zip is broken, it must be possible to mount is. If its an internal ide zipdrive, you should see during booting that bios recognizes the drive.
In a console, try mount -t vfat /dev/hdd0 /media/zip
If that doesn't work, try hdd1, hdd2 and hdd3.
  #5 (permalink)  
Old 07-Jan-2005, 10:47
jrev
Guest
 
Posts: n/a
Post

linux:/home/jean # mount -t vfat /dev/hdd0 /media/zip
mount: special device /dev/hdd0 does not exist
linux:/home/jean # mount -t vfat /dev/hdd1 /media/zip
mount: /dev/hdd1: can't read superblock
linux:/home/jean # mount -t vfat /dev/hdd2 /media/zip
mount: /dev/hdd2: can't read superblock
linux:/home/jean # mount -t vfat /dev/hdd3 /media/zip
mount: /dev/hdd3: can't read superblock
linux:/home/jean # mount -t vfat /dev/hdd4 /media/zip
mount: block device /dev/hdd4 is write-protected, mounting read-only
mount: cannot mount block device /dev/hdd4 read-only
linux:/home/jean # mount -t vfat /dev/hdd5 /media/zip
mount: /dev/hdd5: can't read superblock
linux:/home/jean #

  #6 (permalink)  
Old 07-Jan-2005, 11:13
BigShell
Guest
 
Posts: n/a
Default

Quote:
Originally posted by jrev@Jan 7 2005, 01:49
hi all,
My internal ZIP 100 has been OK with Suse 9.1 & kde 3.2.1...

But suddenly the /dev/hdd4 block disapeared from the dev folder

when I type : # mount /dev/hdd4 I got :
mount: block device /dev/hdd4 is write-protected, mounting read-only
mount: cannot mount block device /dev/hdd4 read-only
You must be using 9.2

Things have changed. Mount /dev/hdd (no partition number).

See this topic: Suse Profess 9.2 Atapi Zip Drive

Have fun!
  #7 (permalink)  
Old 07-Jan-2005, 12:36
jrev
Guest
 
Posts: n/a
Post

you can see in my first post that this zip has been working fine for a long time on suse 9.1
but i cannot find my own way to trace faults on Linux
I am still too new to this OS
  #8 (permalink)  
Old 07-Jan-2005, 13:12
BigShell
Guest
 
Posts: n/a
Default

Quote:
Originally posted by jrev@Jan 7 2005, 12:36
you can see in my first post that this zip has been working fine for a long time on suse 9.1
Sorry, I misread your original post and thought you had moved up to 9.2. This problem appears in 9.2. In SuSE 9.1, mounting /dev/hdd4 (in your case) should work.

In 9.2, /dev/hdd4 (or whaterver hdx4 your zip is on), does not exist and mounting /dev/hdd (no parttition number) works. You might try it just to see.

# mount -t vfat /dev/hdd /media/zip

I that doesn't work, insert a zip disk and try (as root):
fdisk -l (small 'L' not a # 1)
See if that lists anything helpful

Good luck
  #9 (permalink)  
Old 08-Jan-2005, 05:00
jrev
Guest
 
Posts: n/a
Post

linux:/home/jean # mount -t vfat /dev/hdd /media/zip
mount: wrong fs type, bad option, bad superblock on /dev/hdd,
or too many mounted file systems


linux:/home/jean # fdisk -l (small 'L' not a # 1)
bash: syntax error near unexpected token `('

thanks for your help



  #10 (permalink)  
Old 08-Jan-2005, 11:00
mgardner
Guest
 
Posts: n/a
Default

I think he just meant

fdisk -l

The parentheses were a comment.
 
Page 1 of 2 1 2

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

Search Engine Friendly URLs by vBSEO 3.3.0 RC2