From: Ricflomag <ricflomag@gmail.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] openLuks failing - semaphore weird bug involved ?
Date: Thu, 15 Sep 2011 12:15:14 -0400 [thread overview]
Message-ID: <4E722492.8020501@gmail.com> (raw)
In-Reply-To: <20110915160644.GA5473@tansi.org>
>> I have run a "badblocks -nvs
>> /dev/sdb3<https://one.ubuntu.com/dev/sdb3>",
>> it did not find any error... And after this, SMART still reports 4 pending
>> sectors.
> Meaning the pending sectors are someplae else.
>
>> Any clue about how investigating further ?
> badblocks on /dev/sdb.
>
> Arno
That would tell me where the pending sectors are, outside of the luks
partition. But it would not help to know why the luks partition fails to
open, would it ?
next prev parent reply other threads:[~2011-09-15 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 18:30 [dm-crypt] openLuks failing - semaphore weird bug involved ? Ric Flomag
2011-09-07 22:31 ` Arno Wagner
2011-09-08 15:46 ` Ric Flomag
2011-09-08 18:11 ` Arno Wagner
2011-09-08 21:53 ` Claudio Moretti
2011-09-08 22:21 ` Karl O. Pinc
2011-09-09 16:19 ` Arno Wagner
[not found] ` <1315506605.6590.0@mofo>
2011-09-15 15:54 ` Ric Flomag
2011-09-15 16:06 ` Arno Wagner
2011-09-15 16:15 ` Ricflomag [this message]
2011-09-15 23:07 ` Arno Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E722492.8020501@gmail.com \
--to=ricflomag@gmail.com \
--cc=dm-crypt@saout.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.