Partitioner Problems

[Philippe Landau]

hello Richard

> I tried the Kubuntu linux install from last week 11 or 12 March edition.  It 
> began well on my G3 iMac (256 Meg of RAM).... but the partitioner reported an 
> error when it started to format my home partition.  Funnily enough I got a 
> similar error at the same place when I attempted to run the sarge installer 
> for Debian!! In both cases the problem occured 100% of the time ... even 
> after three or four reboots.
> 
> Now before anyone starts talking about my hard disk being 'on the way out' ... 
> I should say that I subsequently completed a YDL 4 install without hiccup ... 
> and am running on it now!!  I can believe that my hard (the original 6 Gig 
> model) is getting tired ... but should there be such a big difference in the 
> results for the debian and YDL partitioners?  Can I run an outside 
> partitioner and jump over this step in my install??
> 
> Ideas please...
> 
> (or must I shell out some money for a replacement hdd??)

you may check your HD for bad blocks.
some partitioners don't handle this ...

kind regards     philippe

--

-c This option causes e2fsck to run the badblocks(8) program to
find any blocks which are bad on the filesystem, and then marks
them as bad by adding them to the bad block inode. If this
option is specified twice, then the bad block scan will be done
using a non-destructive read-write test.

e2fsck  is  used to check a Linux second extended file system (ext2fs).
E2fsck also supports ext2 filesystems countaining a journal,
which  are also sometimes known as ext3 filesystems,
by first applying the journal to the filesystem before
continuing with  normal  e2fsck  processing.
After  the  journal  has  been  applied,
a filesystem will normally be marked as clean.
Hence, for ext3 filesystems, e2fsck will normally run
the  journal  and  exit,  unless  its superblock indicates
that further checking is required.