Prev: Error in Yum
Next: MP3 player on USB
From: someone92 on 17 Nov 2005 02:27
I'm trying to ghost my ext3 linux fedora core 4 boot partition using
ghost (2003 I think) and I receive this error:
--------------------------------------------------------------------------------------------------------------------------------
Error Number: (29004)
Message: Read sector failure, result = 1, drive = 0, sectors -340954973
to -340954971
--------------------------------------------------------------------------------------------------------------------------------
(If you think that sending the complete error log file would help let
me know and I'll post it)

My root partition can be ghosted without problems by the way. And I was
able to ghost the boot partition not long ago.

I have scanned the partion's surface using ranish partition manager
with a negative result, no bad sectors were found.

the I thought it was a bad blocks problem so I used linux's:
e2fsck -c /dev/hdb6

with this result:
------------------------------------------------------------------------------------------------
WARNING!!! Running e2fsck on a mounted filesystem may cause
SEVERE filesystem damage.

Do you really want to continue (y/n)? yes

/boot: recovering journal
Checking for bad blocks (read-only test): done
388
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/boot: ***** FILE SYSTEM WAS MODIFIED *****
/boot: 40/26104 files (22.5% non-contiguous), 16184/104388 blocks
-------------------------------------------------------------------------------------------------
I choose to scan the drive even if it was mounted because I was so
desperate, was it a bad idea?

To me this seems like there were no error found, I'm I right?

so I ran ghost again and received the same error. What is the problem
if there's no bad sectors or bad blocks (or they were fixed). What's
the difference between bad blocks and bad sectors by the way?

One thing I think is strange is the numbers of the sectors (-340954973
to -340954971). Isn't it unusual?

Do you have any suggestions or scanning tools you think I should use to
scan the drive? I tried western digital's HD test utility but it
crashes the system. Maybe because I have 2 other WD drives mounted in a
RAID0 array or the version is too old. Anyway any idea or hints will be
welcome

Thanks in advance

From: someone92 on 17 Nov 2005 03:23
By the way, here's the error I get if I try the western digital data
lifeguard diagnostic tool (I don't know the version but it should be
recent):

SELECTED OPTION - "OTHER OPTION"
SELECTED DRIVE -
Model :
S/N :
Firmware :
C H S :
Capacity :
Drive :
RESULTS - "COMMAND ERROR"
ERROR/STATUS CODE = 0132

I have 2 other WD drives mounted in raid on a HPT370A controller (on an
abit KT7A-RAID motherboard), so I'm thinking that the problems could be
caused when the diagnostic tool tries to send a command to these
drives, could it be so? When I tried to reboot (CTRL-ALT-DEL not cold
reboot) the raid array didn't work anymore, so I freaked out. But
shuting down the computer fixed everything and all HD are find. My BIOS
do not support SMART reports could it cause the problem with the
diagnostic tool.

Any hints on this error will be welcome, should I stop using
manufacturer diagnostic tools on HD mounted in raid?

Thanks

From: someone92 on 17 Nov 2005 03:40
Sorry for this other posting but I realized that in my last posting I
forgot to mention that I tried ghost with the following options to test
other modes of access and to skip bad sectors:
ghost -FNI
ghost -FFX FNI
ghost -FRO
without any succes it still sends me the error or crashes. Just in case
because I saw in other threads that it's very often the solution given.

I also verified and my WD diagnostic tools are the lastest versions

 | 
Pages: 1
Prev: Error in Yum
Next: MP3 player on USB