On Thursday, April 12, 2012 10:13:00 AM m.roth@xxxxxxxxx wrote: > Time to use smartctl, if not fsck -c. Another useful fsck variation is fsck -cc which will do a nondestructive 'read-write' to trigger on-drive bad sector remapping. Takes a long time to do, but does the work. It's documented in the man page under the '-c' option's paragraph, last sentence. _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
Re: System hanged - no info in logs.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: CentOS mailing list <centos@xxxxxxxxxx>
- Subject: Re: System hanged - no info in logs.
- From: Lamar Owen <lowen@xxxxxxxx>
- Date: Sat, 14 Apr 2012 15:13:26 -0400
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <84ce1c8c481b94a59c1e211ac83e5ec0.squirrel@mail.5-cent.us>
- Organization: PARI
- User-agent: KMail/1.13.7 (Linux/2.6.35.14-106.fc14.x86_64; KDE/4.6.5; x86_64; ; )
- References:
- System hanged - no info in logs.
- From: Rafał Radecki
- Re: System hanged - no info in logs.
- From: m . roth
- System hanged - no info in logs.
- Prev by Date: Re: Changing Python Version
- Next by Date: Re: Changing Python Version
- Previous by thread: Re: System hanged - no info in logs.
- Next by thread: Re: System hanged - no info in logs.
- Index(es):
 |