Badblocs too long...

Hi,

I suspect bad blocs in my Hard disk, so I try the commande:

e2fsck -c /dev/hdb1 (hdb1 not mounted)

it calls badblocks, but it's very very long... after half a day I've checked
only 1/10 of my hard disk (IDE - 20 Go)

1. Is it normal?

2. Can I do something else?

Thanks.
--
Patrick GELIN
rue du Beau-Site, 3
CH-2300 La Chaux-de-Fonds
Tel: +41 (0)32 / 913 41 48
Email: patrick.gelin@free.fr

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Badblocs too long...

Hi Patrick!

On Tue, 20 Jan 2004, Patrick Gelin wrote:

> Hi,
>
> I suspect bad blocs in my Hard disk, so I try the commande:
>
> e2fsck -c /dev/hdb1 (hdb1 not mounted)
>
> it calls badblocks, but it's very very long... after half a day I've checked
> only 1/10 of my hard disk (IDE - 20 Go)
>
> 1. Is it normal?

Don't know for sure, but I guess that kinda depends on the filesystem
error thats being found?!

>
> 2. Can I do something else?

I'd wait for the e2fscking to finish, see whats going on, what kind of problem
turns out with the filesystem and then, in case you get it fixed,
think about migrating to a journaling filesytem.

But first let it finish the e2fsck even though it takes so long.

Any helpful kernel messages?


Axel



____________________________________________________________ ________________
Axel Siebenwirth phone +49 3641 776807 |
Am Birnstiel 3 axel at pearbough dot net |
07745 Jena |
Germany________________________________________________http: //pearbough.net |

I either want less decadence or more chance to participate in it.
____________________________________________________________ ________________
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Badblocs too long...

Try:

badblocks -v -n /dev/hdb1

HTH, Chuck

Patrick Gelin wrote:
>
> Hi,
>
> I suspect bad blocs in my Hard disk, so I try the commande:
>
> e2fsck -c /dev/hdb1 (hdb1 not mounted)
>
> it calls badblocks, but it's very very long... after half a day I've checked
> only 1/10 of my hard disk (IDE - 20 Go)
>
> 1. Is it normal?
>
> 2. Can I do something else?
>
> Thanks.
> --
> Patrick GELIN
> rue du Beau-Site, 3
> CH-2300 La Chaux-de-Fonds
> Tel: +41 (0)32 / 913 41 48
> Email: patrick.gelin@free.fr
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Badblocs too long...

chuck gelm net wrote:

> Try:
>
> badblocks -v -n /dev/hdb1
>
I tried, but it asked me a random patern, I don't know what to do, neither
how to leave...

Moreover, man documentation explein it's longer with -n option...

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Badblocs too long...

Axel Siebenwirth wrote:

>> 2. Can I do something else?
>
> I'd wait for the e2fscking to finish, see whats going on, what kind of
> problem turns out with the filesystem and then, in case you get it fixed,
> think about migrating to a journaling filesytem.
>
Firstly, I was using a journaling file system, but I've got same problems...

> But first let it finish the e2fsck even though it takes so long.

Sorry, but I can't wait for one week...

> Any helpful kernel messages?

I found nothing, but I don't know what to look for...

--
Patrick GELIN
rue du Beau-Site, 3
CH-2300 La Chaux-de-Fonds
Tel: +41 (0)32 / 913 41 48
Email: patrick.gelin@free.fr

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

RE: Badblocs too long...

Please revise your version of e2fsprogs,
The last version is in the http://e2fsprogs.sourceforge.net (1.34)
fixes a problem with a tight loop in fsck.

Regards

byca





-----Mensaje original-----
De: Patrick Gelin [mailto:patrick.gelin@free.fr]=20
Enviado el: Mi=E9rcoles, 21 de Enero de 2004 12:16
Para: linux-admin@vger.kernel.org
Asunto: Re: Badblocs too long...

chuck gelm net wrote:

> Try:
>=20
> badblocks -v -n /dev/hdb1
>=20
I tried, but it asked me a random patern, I don't know what to do, neit=
her
how to leave...

Moreover, man documentation explein it's longer with -n option...

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

RE: Badblocs too long...

Carri=F3n Byron wrote:

>=20
> Please revise your version of e2fsprogs,
> The last version is in the http://e2fsprogs.sourceforge.net (1.34)
> fixes a problem with a tight loop in fsck.

I use Mandrake 9.2, current version for my package e2fsprogs is 1.34
>=20
> Regards
>=20
> byca
>=20
>=20
>=20
>=20
>=20
> -----Mensaje original-----
> De: Patrick Gelin [mailto:patrick.gelin@free.fr]
> Enviado el: Mi=E9rcoles, 21 de Enero de 2004 12:16
> Para: linux-admin@vger.kernel.org
> Asunto: Re: Badblocs too long...
>=20
> chuck gelm net wrote:
>=20
>> Try:
>>=20
>> badblocks -v -n /dev/hdb1
>>=20
> I tried, but it asked me a random patern, I don't know what to do, ne=
ither
> how to leave...
>=20
> Moreover, man documentation explein it's longer with -n option...
>=20
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin=
" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin=
" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html

--=20
Patrick GELIN
rue du Beau-Site, 3
CH-2300 La Chaux-de-Fonds
Tel: +41 (0)32 / 913 41 48
Email: patrick.gelin@free.fr

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: Badblocs too long...

Hi, Patrick:

I tested my badblocks (from E2fsprogs 1.22) on a
Slackware 8.0 distribution using kernel 2.4.19 and when I

'badblocks -v -n /dev/hdb1'

the following three lines appear immediately:
Initializing random test data
Checking for bad blocks in non-destructive read-write mode
>From block 0 to 8225248

A portion of 'man badblocks' returns:

-n Use non-destructive read-write mode. By default
only a non-destructive read-only test is done.
This option must not be combined with the -w
option, as they are mutually exclusive.

-v Verbose mode.

What EXACTLY happens when you do the same?

Perhaps

HTH, Chuck


Patrick Gelin wrote:
>
> chuck gelm net wrote:
>
> > Try:
> >
> > badblocks -v -n /dev/hdb1
> >
> I tried, but it asked me a random patern, I don't know what to do, neither
> how to leave...
>
> Moreover, man documentation explein it's longer with -n option...
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html

-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html