Skip to contentSkip to conversation

Different geometry settings for identical drives

DISCUSSION Petr Vandrovec 2 participants 2 messages May 31, 2003 – Jun 2, 2003

lore
Share & tools
lore
#0 lore raw
Quoted 13 lines · Jeffrey W. Baker
Quoted 12 lines · Petr Vandrovec
Quoted 10 lines · Jeffrey Baker

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)

Quoted 8 lines
Quoted 5 lines
Quoted 5 lines

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

The x86-64.org patch doesn't touch much outside of arch/x86_64. You are right that CONFIG_IDE_STROKE is off:

Ok, after looking at your kernel output more, it seems like that there is something strange with your drive: we asked for sector 232343808 (0xDD94900), but your drive reports SectorIdNotFound on sector 234441583 (0xDF94B6F), which is 2097775 (0x020026F) sectors away from sector we requested... As with LBA largest transfer length is 256 sectors, there is something wrong with your disk firmware... Which points to the dead disk together with some bug in the disk firmware (maybe drive wanted to report bug in sector DD9496F, but got it somehow wrong?). Can you try running Western's drive diagnostics on that drive?
Petr Vandrovec [email protected]

#1 lore raw
Quoted 23 lines · Petr Vandrovec
Quoted 13 lines · Jeffrey W. Baker
Quoted 12 lines · Petr Vandrovec
Quoted 10 lines · Jeffrey Baker

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)

Quoted 8 lines
Quoted 5 lines
Quoted 5 lines

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

The x86-64.org patch doesn't touch much outside of arch/x86_64. You are right that CONFIG_IDE_STROKE is off:

Quoted 9 lines

Ok, after looking at your kernel output more, it seems like that there is something strange with your drive: we asked for sector 232343808 (0xDD94900), but your drive reports SectorIdNotFound on sector 234441583 (0xDF94B6F), which is 2097775 (0x020026F) sectors away from sector we requested... As with LBA largest transfer length is 256 sectors, there is something wrong with your disk firmware... Which points to the dead disk together with some bug in the disk firmware (maybe drive wanted to report bug in sector DD9496F, but got it somehow wrong?). Can you try running Western's drive diagnostics on that drive?

I rebooted with the same drive but added hdc=14589,255,63, and now I can make the filesystem perfectly well. So it does seem to be an issue with the way the disk is addressed. Or I could just be fooling myself.

Later I can try swapping in identical hardware and see if the problem persists. All these disks are brand new and were burned in and qualified by the vendor.

-jwb