RE [ILUG] Last block on Disk bad

[gerodonoghue at sigma-sl.ie]

Kenn
Got the same results last blocks showing as bad

Using dumpe2fs /dev/hdaXX  |  more will give us the following information
block count and block size

If we then use
badblocks -b <Block_Size> /dev/hdaXX <Block_count>
it will only test the blocks used by the filesystem not the actual partition
size. Got no failures with this method.
The File System with + at end indicates there is free blocks which are not
used by the filesystem on that device because there was not enough space to
make a block when making the FS.
Maybe badblocks program cannot test blocks with no filesystem on them.
Also there is no data on these blocks so if they are bad (which i doubt) there
is no data loss at this time. However it may be adviseable to try and scan the
physical media for bad sectors just to clear any doubt.

Regards Ger

Kenn Humborg wrote:

> On Thu, Sep 28, 2000 at 10:19:41AM +0100, gerodonoghue at sigma-sl.ie wrote:
> > > Is this hypothesis correct, or do I really have a failing disk
> > > (and it's just pure chance that the bad blocks are exactly at the
> > > ends of partitions)?
> ...
> > The plus at the end indicates that the there is 249007.5 blocks in the
> > partition hda2 i.e. 31*255*63/2.
> > What did you use to check your disk as it may read blocks in groups of 4
> > rather then 1 ??
> >
> > I have the same senario on a 12 GB Drive with + at end of some
> > partitions. And could try and verify this as well.
>
> First I do fdisk -s /dev/hdaX to get the size of the parition.  Then I do
>
> # badblocks /dev/hdaX <size>
>
> Maybe there is a way to use tune2fs or e2fsck to get the size of the
> _filesystem_ in the partition, rather than the size of the partition
> itself.
>
> Must investigate later...
>
> Later,
> Kenn