I have an IDE MO drive, and I usually do not make partitions on MO
disks: I prefer to create filesystems on the "raw" device (i.e., not
having /dev/hdc1 containing the filesystem, but /dev/hdc). But
mounting such disks often produces the errors like the following:
# mount -t vfat /dev/hdc /mnt/mo
hdc:hdc: read_intr: status=0x59 { DriveReady SeekComplete DataRequest Error }
hdc: read_intr: error=0x20 { }
hdc1 hdc2 hdc3 hdc4
hdc: hdc1 hdc2 hdc3 hdc4
This happens not only for vfat, but for the ext2 disks as well. And
it tends to appear only if change the "type" disk: e.g., I first mount
/dev/hdc1, and then /dev/hdc or vice versa. If I mounted /dev/hdc1,
then mounting other partitioned disks do not produce errors; the same
is for unpartitioned disks /dev/hdc.
By errors I mean those kernel messages "hdc: read_intr: status=0x59 ...".
But also attempts to determine the partitions when I'm _explicitly_
mounting /dev/hdc are looking strange. This is probably a bug of
"mount".
Best regards, -- Vladimir.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu