From: "Peter Wächtler" <pwaechtler@loewe-komp.de>
To: Sam Varshavchik <mrsam@courier-mta.com>
Cc: Joseph Cheek <joseph@cheek.com>, linux-kernel@vger.kernel.org
Subject: Re: disregard: Re: ide zip 100 won't mount
Date: Tue, 18 Sep 2001 13:59:08 +0200 [thread overview]
Message-ID: <3BA7370C.E5F9460B@loewe-komp.de> (raw)
In-Reply-To: <courier.3BA68362.00004D02@ny.email-scan.com>
Sam Varshavchik wrote:
>
> Joseph Cheek writes:
>
> > hmm, i went into windows *one more time* just to make sure it was still
> > working, and not a hardware problem. well... looks like it doesn't work
> > in windows either. must be hardware.
> >
> > funny thing it shows up in dmesg and in "My Computer", just can't read
> > from it.
>
> That's pretty much what the sense codes below did indicate - media problem.
> Try a different disk.
>
I had the same problem. The second media works, the first got
screwed up? I can't reproduce the problem now.
The media gets destroyed after partitioning and running mke2fs.
I can't believe it myself - but have no other explanation.
When the media was broken I got:
<7>VFS: Disk change detected on device ide0(3,64)
<6> /dev/ide/host0/bus0/target1/lun0:<7>LDM: DEBUG (ldm.c, 877):
validate_partition_table: Found basic MS-DOS partition, not a dynamic
disk.
<4> p1 p2 p3 p4
<7>VFS: Disk change detected on device ide0(3,65)
<6> /dev/ide/host0/bus0/target1/lun0:<7>LDM: DEBUG (ldm.c, 877):
validate_partition_table: Found basic MS-DOS partition, not a dynamic
disk.
<4> p1 p2 p3 p4
[and so on with funny device numbers up to 3,93]
cat /proc/partitions
3 64 98288 ide/host0/bus0/target1/lun0/disc
3 65 272218546 ide/host0/bus0/target1/lun0/part1
3 66 269488144 ide/host0/bus0/target1/lun0/part2
3 67 699181456 ide/host0/bus0/target1/lun0/part3
3 68 10668 ide/host0/bus0/target1/lun0/part4
Note: a new media has NO partition - it's a floppy.
Now is it possible that the media gets destroyed if the hardware
tries to seek to illegal positions?
> > Joseph Cheek wrote:
> >
> >> i've tried 2.4.7-ac10 and 2.4.9-ac10. same results. at boot i get:
> >>
> >> Sep 17 11:02:48 seattle kernel: ide-floppy driver 0.97.sv
> >> Sep 17 11:02:48 seattle kernel: hdd: No disk in drive
> >> Sep 17 11:02:48 seattle kernel: hdd: 98304kB, 96/64/32 CHS, 4096 kBps,
> >> 512
> >> sector size, 2941 rpm
> >>
> >> looks good, right? but i put a disk in and i get:
> >>
> >> Sep 17 14:36:23 seattle kernel: ide-floppy: hdd: I/O error, pc = 0, key
> >> =
> >> 2, asc = 30, ascq = 0
> >> Sep 17 14:36:23 seattle kernel: ide-floppy: hdd: I/O error, pc = 1b, key
> >> =
> >> 2, asc = 30, ascq = 0
> >> Sep 17 14:36:23 seattle kernel: hdd: No disk in drive
> >>
> >> not hardware, as it works in windows on the same machine.
next prev parent reply other threads:[~2001-09-18 12:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-17 23:12 disregard: Re: ide zip 100 won't mount Sam Varshavchik
2001-09-18 11:59 ` Peter Wächtler [this message]
2001-09-19 17:41 ` Mark H. Wood
[not found] <fa.ia34bav.ijiuqq@ifi.uio.no>
[not found] ` <fa.jbpet1v.q08fo6@ifi.uio.no>
2001-09-19 22:14 ` Sam Varshavchik
-- strict thread matches above, loose matches on Subject: below --
2001-09-17 21:39 Joseph Cheek
2001-09-17 22:52 ` disregard: " Joseph Cheek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BA7370C.E5F9460B@loewe-komp.de \
--to=pwaechtler@loewe-komp.de \
--cc=joseph@cheek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mrsam@courier-mta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox