2.4.21-rc6-rmap15j possible drive format corruption

James Blanford (jimmybgood@cox.net)
Mon, 2 Jun 2003 13:05:50 -0700 (MST)


Now this could just be a complete coincidence and my hard drive decided
to head south just minutes after the second time I booted
2.4.21-rc6-rmap15j. But it is also quite reminiscent of the
Thanksgiving, 2001 greased-turkey release. This time I have no system
problems or error messages, but got a report of 3 ATA errors (my drive's
first) from a running SMART daemon.

Both smartmontool's smartctl and Seagate's SeaTools Desktop gave an
error that basically meant that the drive self-tests could not be run.
Seagate offered the possibility that a low-level format could correct
the problem. More ominously, upon booting to a system on a different
drive and running badblocks, badblocks hangs testing the beginning of
the partition that my root is mounted on. Everything else is ok
including fsck (without badblocks).

drive: Seagate 340016A, ATA 40GB
board: ECS K7S5A, SiS 735 chipset, SiS 5513 on board IDE
filesystem: ext3 built into kernel
config:

#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
# CONFIG_BLK_DEV_GENERIC is not set
# CONFIG_IDEPCI_SHARE_IRQ is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_BLK_DEV_OFFBOARD is not set
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_PCI_WIP is not set
# CONFIG_BLK_DEV_ADMA100 is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_RZ1000 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
CONFIG_BLK_DEV_SIS5513=y
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_IDEDMA_IVB is not set
# CONFIG_DMA_NONPCI is not set
CONFIG_BLK_DEV_IDE_MODES=y
# CONFIG_BLK_DEV_ATARAID is not set

I normally don't post and know that this could be a hardware problem
only. I decided to post because I (and I imagine anyone else) would
have missed it if I had not been running smartd. Or maybe all this
smart stuff is just bogus?

What, me worry?

- Alfred

PS Not subscribed, but lurking
-
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/