Hello,
For the second time in a week time I found my root partition was
so damaged that I couldn't boot up anymore.
At boottime I got this:
<3>ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
<3>ata1.00: BMDMA stat 0x64
<3>ata1.00: cmd c8/00:08:6d:65:14/00:00:00:00:00/ec tag 0 cdb 0x1e data
4096 in <4> res 51/40:00:6f:65:14/00:00:00:00:00/ec Emask 0x9
(media error) <6>ata1.00: configured for UDMA/100
<6>ata1.01: configured for UDMA/44
<6>ata1: EH complete
I got this uncountable times.
At the end I got this:
<6>sd 0:0:0:0: [sda] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE,SUGGEST_OK <6>sd 0:0:0:0: [sda] Sense Key :
Medium Error [current] [descriptor] <4>Descriptor sense data with sense
descriptors (in hex): <6> 72 03 11 04 00 00 00 0c 00 0a 80 00 00
00 00 00 <6> 0c 14 65 6f
<6>sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto
reallocate failed <4>end_request: I/O error, dev sda, sector 202663279
<6>ata1: EH complete
<2>EXT3-fs error (device sda9): ext3_get_inode_loc: unable to read
inode block - inode=877217, block=1769563 <5>sd 0:0:0:0: [sda]
234441648 512-byte hardware sectors (120034 MB) <5>sd 0:0:0:0: [sda]
Write Protect is off <7>sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
<2>EXT3-fs error (device sda9) in ext3_reserve_inode_write: IO failure
<5>sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA <5>sd 0:0:0:0: [sda] 234441648 512-byte hardware
sectors (120034 MB) <5>sd 0:0:0:0: [sda] Write Protect is off
<7>sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
<5>sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't
support DPO or FUA Kernel logging (ksyslog) stopped.
Kernel log daemon terminating.
A fsck of /dec/sda9 resulted in
Error reading block 1769563 (Attempt to read block from filesystem
resulted in short read) while getting next inode from scan. Ignore
error <y>? Yes Force rewrite <y>? Yes
repeated numerous times
At the end lots of files went to the lost+found dir
As result of that I couldn't reboot anymore.
The first time I re-installed OpenSuse 10.3 (as 11.0 failed to install)
and all went fine for a week. But now the same thing happened again.
Is this a hard disk failure?
If not can I resolve these problems without doing a complete
re-installation of OpenSuse 10.3?
TIA,
Martin
--
Martin /Nightowl/ Byttebier