Moved the mobo, drives, controller and video card , and everything else from one box to another. In other words, the ONLY thing I changed was the case and power supply. The zip 250 worked perfectly in the original box and was identified in fstab as: /dev/hdc4 /zip vfat noauto, user, exec 0 0 and a mount point of /zip. In this new box trying to mount it gives a "mount: /dev/hdc4 is not a valid block device. If I alter /etc/fstab to change the zip identifier to the more common hdd4, I get "mount: /dev/hdd4: can't read superblock" Can anyone give me some advice as to what's going on? dave -- David C. Johanson Linux Counter # 116410 Powered by SuSE Linux 7.1 People who behold a phenomenon will often extend their thinking beyond it; people who merely hear about the phenomenon will not be moved to think at all. -- Goethe
Thanks Carlos - Carlos E. R. wrote:
The Thursday 2004-05-06 at 20:50 -0400, David Johanson wrote:
/dev/hdc4 /zip vfat noauto, user, exec 0 0 and a mount point of /zip.
In this new box trying to mount it gives a "mount: /dev/hdc4 is not a valid block device. If I alter /etc/fstab to change the zip identifier to the more common hdd4, I get "mount: /dev/hdd4: can't read superblock"
Can anyone give me some advice as to what's going on?
fdisk -l
Will list all partitions on all recognised drives.
pcp09513812pcs:~ # fdisk -l Disk /dev/sda: 255 heads, 63 sectors, 8924 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 8924 71681998+ c Win95 FAT32 (LBA) Disk /dev/sdb: 255 heads, 63 sectors, 2231 cylinders Units = cylinders of 16065 * 512 bytes Device Boot Start End Blocks Id System /dev/sdb1 1 3 24066 83 Linux /dev/sdb2 4 20 136552+ 82 Linux swap /dev/sdb3 21 2231 17759857+ 83 Linux pcp09513812pcs:~ # No zip identified here. ;-(
You can also have a look at "/proc/ide/*"
In /proc/ide/ I have ide0 and ide1 files, links to the files hda and hdd, and two files of 0 bytes, "drivers" and "via". The link hdd holds 7 additional files of 0 bytes each; capacity, driver, geometry, identify(locked), media, model, and settings (also locked). What should I be seeing here? dave -- David C. Johanson Linux Counter # 116410 Powered by SuSE Linux 7.1 People who behold a phenomenon will often extend their thinking beyond it; people who merely hear about the phenomenon will not be moved to think at all. -- Goethe
The Thursday 2004-05-06 at 20:50 -0400, David Johanson wrote:
/dev/hdc4 /zip vfat noauto, user, exec 0 0 and a mount point of /zip.
In this new box trying to mount it gives a "mount: /dev/hdc4 is not a valid block device. If I alter /etc/fstab to change the zip identifier to the more common hdd4, I get "mount: /dev/hdd4: can't read superblock"
Can anyone give me some advice as to what's going on?
fdisk -l Will list all partitions on all recognised drives. You can also have a look at "/proc/ide/*" -- Cheers, Carlos Robinson
Fri, 07 Jan 2000 03:38:19 -0500 David Johanson wrote: Mebbe you should consider checking your clock? Your previous posts also came from over 4 years ago.
/dev/hdc4 /zip vfat noauto, user, exec 0 0 and a mount point of /zip.
In this new box trying to mount it gives a "mount: /dev/hdc4 is not a valid block device. If I alter /etc/fstab to change the zip identifier to the more common hdd4, I get "mount: /dev/hdd4: can't read superblock"
Can anyone give me some advice as to what's going on?
/etc/fstab has to match the actual device position on the secondary controller. If the drive is in fact jumpered as a slave and has a master on the cable, then the zip must be /dev/hdd. It would include /dev/hdd4 only if the disk inserted was partitioned, as opposed to being formatted as a large floppy, which is the more usual case with zip disks. If the zip drive is the only device on the cable, then it must be jumpered as a master, and it would then be /dev/hdc. Jumpering as a slave with no master is illegal, and thus can be expected to be trouble unless you are using windoze. Unless you plan to boot from your zip, set the BIOS for it to NONE to minimize potential for grief. There is no good reason for non-bootable devices to be enumerated in the BIOS. -- "Be wise in the way you act toward outsiders; make the most of every opportunity." Colossians 4:5 NIV Team OS/2 ** Reg. Linux User #211409 Felix Miata *** http://members.ij.net/mrmazda/
i received that error after dropping my zip 100. If your drive took any type of hit it may be toast. If its external try it on another box. Test the connector with another device printer usb whatever you have. More than two years and IOMEGA will politely tell you to pound sand. CWSIV On Thu, 2004-05-06 at 17:50, David Johanson wrote:
Moved the mobo, drives, controller and video card , and everything else from one box to another. In other words, the ONLY thing I changed was the case and power supply. The zip 250 worked perfectly in the original box and was identified in fstab as:
/dev/hdc4 /zip vfat noauto, user, exec 0 0 and a mount point of /zip.
In this new box trying to mount it gives a "mount: /dev/hdc4 is not a valid block device. If I alter /etc/fstab to change the zip identifier to the more common hdd4, I get "mount: /dev/hdd4: can't read superblock"
Can anyone give me some advice as to what's going on?
dave -- David C. Johanson Linux Counter # 116410 Powered by SuSE Linux 7.1
People who behold a phenomenon will often extend their thinking beyond it; people who merely hear about the phenomenon will not be moved to think at all. -- Goethe
The Friday 2000-01-07 at 03:38 -0500, David Johanson wrote:
pcp09513812pcs:~ # fdisk -l
Disk /dev/sda: 255 heads, 63 sectors, 8924 cylinders Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System /dev/sda1 * 1 8924 71681998+ c Win95 FAT32 (LBA)
Disk /dev/sdb: 255 heads, 63 sectors, 2231 cylinders Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System /dev/sdb1 1 3 24066 83 Linux /dev/sdb2 4 20 136552+ 82 Linux swap /dev/sdb3 21 2231 17759857+ 83 Linux pcp09513812pcs:~ #
No zip identified here. ;-(
No, certainly there is no mountable ide disk there.
You can also have a look at "/proc/ide/*"
In /proc/ide/ I have ide0 and ide1 files, links to the files hda and hdd, and two files of 0 bytes, "drivers" and "via". The link hdd holds 7 additional files of 0 bytes each; capacity, driver, geometry, identify(locked), media, model, and settings (also locked). What should I be seeing here?
Try to 'cat' them. For example: cer@nimrodel:~> cat /proc/ide/hda/model ST360020A which is the model name of my hda disk. They are "pseudofiles" created by the kernel on the fly when you request to see them. For example, "settings" has a lot of interesting info. The "via" file you mention must be equivalent to my "piix" one, and has info about the ide chipset; mine says what dma/udma I have enabled. I think your ZIP drive is not detected. Probably there will be some info in the /var/log/boot.msg file. I have seen the rest of the messages on this thread, but I have nothing else definite to say. -- Cheers, Carlos Robinson
Felix Miata wrote:
Fri, 07 Jan 2000 03:38:19 -0500 David Johanson wrote:
<snip>
/etc/fstab has to match the actual device position on the secondary controller. If the drive is in fact jumpered as a slave and has a master on the cable, then the zip must be /dev/hdd. It would include /dev/hdd4 only if the disk inserted was partitioned, as opposed to being formatted as a large floppy, which is the more usual case with zip disks. If the zip drive is the only device on the cable, then it must be jumpered as a master, and it would then be /dev/hdc.
Oh how pain meds can clog the brain. Forgot that the drive wasn't jumpered at all. Jumpering it to master and changing the dev identifier to hdc did the trick. Thanks! dave -- David C. Johanson Linux Counter # 116410 Powered by SuSE Linux 7.1 People who behold a phenomenon will often extend their thinking beyond it; people who merely hear about the phenomenon will not be moved to think at all. -- Goethe
participants (4)
-
Carl William Spitzer IV -
Carlos E. R. -
David Johanson -
Felix Miata