hard drive issues

[w bugar]

Hi, Looking for advice on how best to proceed with
possible disk crash. (running FC4) Recently the boot
stops at Checking Filesystems and drops me into a
shell.
I saw the following in /var/log/messages:
(from a good boot)
Aug  3 20:37:53 localhost kernel: hdd: max request
size: 128KiB
Aug  3 20:37:53 localhost kernel: hdd: 156301488
sectors (80026 MB) w/8192KiB Cache, CHS=65535/16/63,
UDMA(33)
Aug  3 20:37:53 localhost kernel: hdd: cache flushes
supported
Aug  3 20:37:53 localhost kernel:  hdd: hdd1

(bad boot)
Aug  3 21:32:28 localhost kernel: hdd: status error:
status=0x7f { DriveReady DeviceFault SeekComplete
DataRequest CorrectedError Index Error }
Aug  3 21:32:28 localhost kernel: hdd: status error:
error=0x7f { DriveStatusError UncorrectableError
SectorIdNotFound TrackZeroNotFound AddrMarkNotFound },
LBAsect=260013951, sector=3687
Aug  3 21:32:28 localhost kernel: ide: failed opcode
was: unknown
Aug  3 21:32:28 localhost kernel: hdc: DMA disabled
Aug  3 21:32:28 localhost kernel: hdd: DMA disabled
Aug  3 21:32:28 localhost kernel: hdd: drive not ready
for command
Aug  3 21:32:59 localhost kernel: ide1: reset
timed-out, status=0x80
Aug  3 21:32:59 localhost kernel: hdd: status error:
status=0x7f { DriveReady DeviceFault SeekComplete
DataRequest CorrectedError Index Error }
Aug  3 21:32:59 localhost kernel: hdd: status error:
error=0x7f { DriveStatusError UncorrectableError
SectorIdNotFound TrackZeroNotFound AddrMarkNotFound },
LBAsect=260013951, sector=3687
Aug  3 21:32:59 localhost kernel: ide: failed opcode
was: unknown
Aug  3 21:32:59 localhost kernel: hdd: drive not ready
for command
Aug  3 21:33:30 localhost kernel: ide1: reset
timed-out, status=0x80
Aug  3 21:33:30 localhost kernel: end_request: I/O
error, dev hdd, sector 3687
Aug  3 21:33:30 localhost kernel: end_request: I/O
error, dev hdd, sector 3695
Aug  3 21:33:31 localhost kernel: end_request: I/O
error, dev hdd, sector 3703
Aug  3 21:33:31 localhost kernel: end_request: I/O
error, dev hdd, sector 3711
Aug  3 21:33:31 localhost kernel: end_request: I/O
error, dev hdd, sector 3719
Aug  3 21:33:31 localhost kernel: Buffer I/O error on
device hdd1, logical block 457
Aug  3 21:33:31 localhost kernel: lost page write due
to I/O error on hdd1
Aug  3 21:33:31 localhost kernel: Aborting journal on
device hdd1.
Aug  3 21:33:31 localhost kernel: ext3_abort called.
Aug  3 21:33:31 localhost kernel: EXT3-fs error
(device hdd1): ext3_journal_start_sb: Detected aborted
journal
Aug  3 21:33:31 localhost kernel: Remounting
filesystem read-only
Aug  3 21:33:39 localhost kernel: end_request: I/O
error, dev hdd, sector 141810583
Aug  3 21:33:39 localhost kernel: end_request: I/O
error, dev hdd, sector 141810591
Aug  3 21:33:39 localhost kernel: end_request: I/O
error, dev hdd, sector 141810599
Aug  3 21:33:39 localhost kernel: end_request: I/O
error, dev hdd, sector 141810607
Aug  3 21:33:39 localhost kernel: end_request: I/O
error, dev hdd, sector 141810615
:
: (lots more)
:
Aug  3 21:34:05 localhost kernel: end_request: I/O
error, dev hdd, sector 136644367
Aug  3 21:34:05 localhost kernel: end_request: I/O
error, dev hdd, sector 136644311
Aug  3 21:34:06 localhost kernel: end_request: I/O
error, dev hdd, sector 141557887
Aug  3 21:34:06 localhost kernel: Buffer I/O error on
device hdd1, logical block 17694728
Aug  3 21:34:06 localhost kernel: lost page write due
to I/O error on hdd1
Aug  3 21:34:06 localhost kernel: end_request: I/O
error, dev hdd, sector 141557935
Aug  3 21:34:06 localhost kernel: Buffer I/O error on
device hdd1, logical block 17694734
Aug  3 21:34:06 localhost kernel: lost page write due
to I/O error on hdd1
Aug  3 21:34:06 localhost kernel: end_request: I/O
error, dev hdd, sector 127
Aug  3 21:34:06 localhost kernel: Buffer I/O error on
device hdd1, logical block 8
Aug  3 21:34:06 localhost kernel: lost page write due
to I/O error on hdd1
Aug  3 21:34:45 localhost kernel: end_request: I/O
error, dev hdd, sector 135738943
Aug  3 21:34:45 localhost kernel: end_request: I/O
error, dev hdd, sector 135738951
Aug  3 21:34:45 localhost kernel: end_request: I/O
error, dev hdd, sector 135738959
Aug  3 21:34:45 localhost kernel: end_request: I/O
error, dev hdd, sector 135738967
Aug  3 21:34:45 localhost kernel: end_request: I/O
error, dev hdd, sector 135738975
:
: (lots more)
:
Aug  3 21:36:06 localhost kernel: end_request: I/O
error, dev hdd, sector 136766647
Aug  3 21:36:06 localhost kernel: end_request: I/O
error, dev hdd, sector 136766823
Aug  3 21:36:06 localhost kernel: end_request: I/O
error, dev hdd, sector 136766831
Aug  3 21:36:06 localhost kernel: end_request: I/O
error, dev hdd, sector 136766839
Aug  3 21:36:06 localhost kernel: end_request: I/O
error, dev hdd, sector 136766847
Aug  3 21:36:06 localhost kernel: end_request: I/O
error, dev hdd, sector 136766623
Aug  3 21:36:57 localhost kernel: end_request: I/O
error, dev hdd, sector 62963775
Aug  3 21:37:02 localhost kernel: end_request: I/O
error, dev hdd, sector 16613439
Aug  3 21:37:02 localhost kernel: end_request: I/O
error, dev hdd, sector 431
Aug  3 21:37:02 localhost kernel: EXT3-fs error
(device hdd1): ext3_readdir: directory #11 contains a
hole at offset 0
Aug  3 21:37:02 localhost kernel: end_request: I/O
error, dev hdd, sector 439
Aug  3 21:37:02 localhost kernel: EXT3-fs error
(device hdd1): ext3_readdir: directory #11 contains a
hole at offset 4096
Aug  3 21:37:02 localhost kernel: end_request: I/O
error, dev hdd, sector 447
Aug  3 21:37:02 localhost kernel: EXT3-fs error
(device hdd1): ext3_readdir: directory #11 contains a
hole at offset 8192
Aug  3 21:37:02 localhost kernel: end_request: I/O
error, dev hdd, sector 455
Aug  3 21:37:02 localhost kernel: EXT3-fs error
(device hdd1): ext3_readdir: directory #11 contains a
hole at offset 12288
Aug  3 21:37:08 localhost kernel: end_request: I/O
error, dev hdd, sector 62963775

So, is hdd kaput? 
(hardware problem, not sofware?)
Can I run e2fsck to try to "save" this disk?
(had alot of files on it, the disk is only a few
months old)
I removed power from it and rebooted, got the same
problem at Checking Filesystems (impossible?), with
complaints about not finding the superblock. I ran
`e2fsck -c` on hdb - output seemed ok, same command on
hda - it finished right away, only found about 13
files!
So, is hda wiped out? How did this happen?
Should I run e2fsck on hdd followed by reloading FC4
onto hda? (ouch)
Thanks,
Bill
ps. sorry for the long post


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com