From: Chris Murphy <lists@colorremedies.com>
To: Nicholas Lee <email@nickle.es>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Question: How can I recover this partition? (unable to find logical $hugenum len 4096)
Date: Thu, 22 Aug 2013 19:26:03 -0600 [thread overview]
Message-ID: <78390B95-F33F-44AC-BF85-ED48D7FF2BFE@colorremedies.com> (raw)
In-Reply-To: <5F161E82-F226-43FB-860F-53AF859E4EFA@nickle.es>
On Aug 22, 2013, at 6:59 PM, Nicholas Lee <email@nickle.es> wrote:
>
> smartctl -x /dev/sdg | grep SCT
The grep filtered the current read/write values, try this:
smartctl -l scterc /dev/sdg
If it's higher than 300(30.0 seconds) then you should change it:
smartctl -l scterc,70,70 /dev/sdX
for all drives. And then I'd filter through dmesg to see if you have any PHY or read errors or ATA reset messages.
Chris Murphy
next prev parent reply other threads:[~2013-08-23 1:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-22 6:47 Question: How can I recover this partition? (unable to find logical $hugenum len 4096) Nicholas Lee
2013-08-22 14:09 ` Mitch Harder
2013-08-22 19:23 ` Nicholas Lee
2013-08-22 19:38 ` Nicholas Lee
2013-08-22 22:58 ` Chris Murphy
2013-08-23 0:58 ` Chris Murphy
[not found] ` <6A12FF1B-5E1A-4F6F-92DA-41E52152E6F2@nickle.es>
2013-08-26 17:26 ` Nicholas Lee
2013-08-26 17:36 ` Chris Murphy
[not found] ` <CAGURm2FS=YTuBpbrg7BV=Un8ZCp9xYZae-WuqhjV29xXA7e0jw@mail.gmail.com>
2013-08-26 19:10 ` Chris Murphy
2013-08-26 19:31 ` Hugo Mills
2013-08-27 3:39 ` Chris Murphy
2013-08-29 17:35 ` Zach Brown
2013-08-29 19:37 ` Chris Murphy
2013-08-29 19:40 ` Hugo Mills
2013-08-29 19:44 ` Chris Murphy
2013-08-29 19:53 ` Hugo Mills
2013-08-29 20:19 ` Chris Murphy
2013-08-29 20:28 ` Chris Murphy
2013-08-30 14:44 ` Eric Sandeen
2013-08-30 14:54 ` Hugo Mills
2013-08-23 0:59 ` Nicholas Lee
2013-08-23 1:26 ` Chris Murphy [this message]
2013-08-22 23:53 ` Duncan
[not found] ` < pan$c2c58$61dbf027$55d0c5a2$71b9b679@cox.net>
2013-08-23 1:47 ` Duncan
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=78390B95-F33F-44AC-BF85-ED48D7FF2BFE@colorremedies.com \
--to=lists@colorremedies.com \
--cc=email@nickle.es \
--cc=linux-btrfs@vger.kernel.org \
/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.