Re: Linux fedora core 4 ... GRUB loading stage2... booting message

• Previous message: Lenard: "Re: Linux fedora core 4 ... GRUB loading stage2... booting message"
• In reply to: Lenard: "Re: Linux fedora core 4 ... GRUB loading stage2... booting message"
• Next in thread: Lenard: "Re: Linux fedora core 4 ... GRUB loading stage2... booting message"
• Reply: Lenard: "Re: Linux fedora core 4 ... GRUB loading stage2... booting message"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Date: 16 Nov 2005 23:42:30 -0800

Lenard wrote:
> Was this a clean install (wipe and load) or did you do an upgrade??

yes it was a clean install, I know it was a stupid idea to keep the
boot sector file but it worked for a while.

by the way I just tried to ghost the boot partition today and I receive
an error, maybe it as something to do with the fact that everything was
working correctly an sudently stoped working.

here's the original message:
----------------------------------------------------------------------------------------------------------------------------------
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

----------------------------------------------------------------------------------------------------------------------------------

• Previous message: Lenard: "Re: Linux fedora core 4 ... GRUB loading stage2... booting message"
• In reply to: Lenard: "Re: Linux fedora core 4 ... GRUB loading stage2... booting message"
• Next in thread: Lenard: "Re: Linux fedora core 4 ... GRUB loading stage2... booting message"
• Reply: Lenard: "Re: Linux fedora core 4 ... GRUB loading stage2... booting message"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]