From: chuck gelm <chuck@gelm.net>
To: James Miller <jamtat@mailsnare.net>
Cc: linux-newbie@vger.kernel.org
Subject: Re: dmesg output: impending hardware failure?
Date: Mon, 15 Aug 2005 19:52:39 -0400 [thread overview]
Message-ID: <43012AC7.2000606@gelm.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0508151724430.11640@localhost.localdomain>
Hi, James:
I'll top post because your example is long.
First: Backup your data on /dev/hdb! :-|
Second: I recommend editing /etc/smartd.conf to include
/dev/hdb -a
Then running
smartd
Then
tail -f /var/log/messages
and see whazzzup! ;-)
HTH, Chuck
James Miller wrote:
> I run a Debian unstable system here and recently did a
> dist-upgrade--actually the Synaptic equivalent. In the process, I got a
> new kernel (2.6.12). On reboot, I noticed alot of errors referencing
> /dev/hdb. This is not the oldest of the 3 hard drives I have in this
> machine, but it's also not very new (ca. 4 years old). All drives are on
> the built-in IDE channels. I'm wondering if the output may be telling me
> the hardware is on its way south. I include relevant dmesg output below.
> Any input or advice on this anyone?
>
> NET: Registered protocol family 1
> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
> PIIX4: IDE controller at PCI slot 0000:00:07.1
> PIIX4: chipset revision 1
> PIIX4: not 100% native mode: will probe irqs later
> ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:DMA, hdb:DMA
> ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:DMA, hdd:DMA
> Probing IDE interface ide0...
> hda: ST310215A, ATA DISK drive
> hdb: ST320413A, ATA DISK drive
> ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
> Probing IDE interface ide1...
> hdc: IBM-DPTA-371360, ATA DISK drive
> hdd: CD-RW 32X10X40, ATAPI CD/DVD-ROM drive
> ide1 at 0x170-0x177,0x376 on irq 15
> Probing IDE interface ide2...
> Probing IDE interface ide3...
> Probing IDE interface ide4...
> Probing IDE interface ide5...
> hda: max request size: 128KiB
> hda: 19541088 sectors (10005 MB) w/2048KiB Cache, CHS=19386/16/63, UDMA(33)
> hda: cache flushes not supported
> /dev/ide/host0/bus0/target0/lun0: p1
> hdb: max request size: 128KiB
> hdb: Host Protected Area detected.
> current capacity is 39102336 sectors (20020 MB)
> native capacity is 39102337 sectors (20020 MB)
> hdb: Host Protected Area disabled.
> hdb: 39102337 sectors (20020 MB) w/1024KiB Cache, CHS=38792/16/63, UDMA(33)
> hdb: cache flushes not supported
> /dev/ide/host0/bus0/target1/lun0: p1
> hdc: max request size: 128KiB
> hdc: 26712000 sectors (13676 MB) w/1961KiB Cache, CHS=26500/16/63, UDMA(33)
> hdc: cache flushes not supported
> /dev/ide/host0/bus1/target0/lun0: p1 p2
> kjournald starting. Commit interval 5 seconds
> EXT3-fs: mounted filesystem with ordered data mode.
> hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102336,
> sector=39102336
> ide: failed opcode was: unknown
> hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102336,
> sector=39102336
> ide: failed opcode was: unknown
> hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102336,
> sector=39102336
> ide: failed opcode was: unknown
> hdb: dma_intr: status=0x51 { DriveReady SeekComplete Error }
> hdb: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=39102336,
> sector=39102336
> ide: failed opcode was: unknown
> hda: DMA disabled
> hdb: DMA disabled
> ide0: reset: success
> hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdb: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=39167615,
> sector=39102336
> ide: failed opcode was: unknown
> hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdb: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=39167615,
> sector=39102336
> ide: failed opcode was: unknown
> hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdb: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=39167615,
> sector=39102336
> ide: failed opcode was: unknown
> hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdb: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=39167615,
> sector=39102336
> ide: failed opcode was: unknown
> ide0: reset: success
> hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdb: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=39167615,
> sector=39102336
> ide: failed opcode was: unknown
> end_request: I/O error, dev hdb, sector 39102336
> Buffer I/O error on device hdb, logical block 39102336
> hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdb: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=39167615,
> sector=39102336
> ide: failed opcode was: unknown
> hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdb: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=39167615,
> sector=39102336
> ide: failed opcode was: unknown
> hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdb: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=39167615,
> sector=39102336
> ide: failed opcode was: unknown
> hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdb: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=39167615,
> sector=39102336
> ide: failed opcode was: unknown
> ide0: reset: success
> hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdb: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=39167615,
> sector=39102336
> ide: failed opcode was: unknown
> hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdb: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=39167615,
> sector=39102336
> ide: failed opcode was: unknown
> hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdb: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=39167615,
> sector=39102336
> ide: failed opcode was: unknown
> hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdb: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=39167615,
> sector=39102336
> ide: failed opcode was: unknown
> ide0: reset: success
> hdb: task_in_intr: status=0x59 { DriveReady SeekComplete DataRequest
> Error }
> hdb: task_in_intr: error=0x10 { SectorIdNotFound }, LBAsect=39167615,
> sector=39102336
> ide: failed opcode was: unknown
> end_request: I/O error, dev hdb, sector 39102336
> Buffer I/O error on device hdb, logical block 39102336
>
> Thanks, James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs
next prev parent reply other threads:[~2005-08-15 23:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-15 22:30 dmesg output: impending hardware failure? James Miller
2005-08-15 23:52 ` chuck gelm [this message]
2005-08-16 18:26 ` James Miller
2005-08-17 16:33 ` Ray Olszewski
2005-08-17 16:59 ` James Miller
2005-08-18 0:06 ` Ray Olszewski
2005-08-18 1:41 ` James Miller
2005-08-18 3:06 ` Vikas
2005-08-18 3:10 ` HOW TO HAVE GOOD KERNEL UNDERSTANDING Vikas
2005-08-19 13:07 ` _z33
2005-08-19 13:17 ` osk
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=43012AC7.2000606@gelm.net \
--to=chuck@gelm.net \
--cc=jamtat@mailsnare.net \
--cc=linux-newbie@vger.kernel.org \
/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