Messages in this thread | | | From | "Petr Vandrovec" <> | Date | Sat, 31 May 2003 01:20:45 +0200 | Subject | Re: Different geometry settings for identical drives |
| |
On 30 May 03 at 15:46, Jeffrey Baker wrote:
> hda: host protected area => 1 > hda: setmax LBA 234441648, native 234375000 > hda: 234375000 sectors (120000 MB) w/8192KiB Cache, CHS=232514/16/63, UDMA(100) > hdc: attached ide-disk driver. > hdc: host protected area => 1 > hdc: setmax LBA 234441648, native 234375000 > hdc: 234375000 sectors (120000 MB) w/8192KiB Cache, CHS=232514/16/63, UDMA(100) > hdd: attached ide-cdrom driver. > hdd: ATAPI 24X CD-ROM drive, 128kB Cache, UDMA(33) > > The result is that hda works fine but hdc doesn't. When I try to mke2fs > on the latter I see: > > hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } > hdc: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=234441583, sector=232343808 > > You can see that LBAsect (234441583) is higher than the "native" sectors > quoted by the kernel (234375000, difference 66583 sectors). Why are > these two disks being addressed differently?
As far as I can tell, it has nothing to do with disk geometry.
Someone just cut couple of sectors at the end from disk, you compiled your kernel without CONFIG_IDEDISK_STROKE, but still kernel for some reason reports block size as if idedisk_set_max_address() was invoked.
I do not see how this could happen with 2.4.21-rc3... Can you recheck that you are using 2.4.21-rc3 without any additional patches? Petr Vandrovec vandrove@vc.cvut.cz
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |