From: Kai Hendry <hendry@iki.fi>
To: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>,
Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: USB upgrade fun
Date: Fri, 13 Oct 2017 09:42:54 +0800 [thread overview]
Message-ID: <1507858974.1236555.1137202920.267B449B@webmail.messagingengine.com> (raw)
In-Reply-To: <0a3e71f7-1a8e-9a4f-7470-4c5cc2fb11a0@gmail.com>
Thank you Austin & Chris for your replies!
On Fri, 13 Oct 2017, at 01:19 AM, Austin S. Hemmelgarn wrote:
> Same here on a pair of 3 year old NUC's. Based on the traces and the
> other information, I'd be willing to bet this is probably the root cause
> of the issues.
It probably is... since when I remove my new 4TB USB disk from the
front, I am at least able to mount my two 2x2TB in degraded mode and see
my data!
So I am not quite sure what to do now.
I don't trust USB hubs.
On a different NUC I've noticed I can't charge my iPhone anymore!
https://mail-archive.com/linux-usb@vger.kernel.org/msg95231.html So...
is there any end in sight for the "USB power" problem? Does USB-C /
Thunderbolt address this issue? :(
Try return my new 4TB to Amazon and find an externally powered one
> > merely the Btrfs signature is wiped from the deleted device(s). So you
> > could restore that signature and the device would be valid again;
Wonder how would you do that, in order to have a working snapshot that I
can put in cold storage?
Nonetheless I hope the btrfs developers can make it possible to remove a
RAID1 drive, to put in cold storage use case, without any pfaffing.
I ran that debug info: https://s.natalian.org/2017-10-13/btrfs-reply.txt
To summarise:
* sdb - new 4TB disk that makes my raid1 unmountable atm when connected
* sd{c,d} - old 2tb
Here's the accompanying dmesg.txt
https://s.natalian.org/2017-10-13/dmesg.txt sorry, it might be difficult
to follow since I was moving the 4TB between the front ports and such.
Kind regards,
next prev parent reply other threads:[~2017-10-13 1:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-08 9:58 USB upgrade fun Kai Hendry
2017-10-10 2:06 ` Satoru Takeuchi
2017-10-11 4:18 ` Kai Hendry
2017-10-12 2:27 ` Kai Hendry
2017-10-12 17:19 ` Chris Murphy
2017-10-12 16:57 ` Chris Murphy
2017-10-12 17:19 ` Austin S. Hemmelgarn
2017-10-13 1:42 ` Kai Hendry [this message]
2017-10-13 11:22 ` Austin S. Hemmelgarn
2017-10-13 18:28 ` Chris Murphy
2017-10-28 7:03 ` Kai Hendry
2017-10-28 7:58 ` Qu Wenruo
2017-10-29 3:20 ` Kai Hendry
2017-10-29 10:02 ` Qu Wenruo
2017-10-30 11:12 ` Kai Hendry
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=1507858974.1236555.1137202920.267B449B@webmail.messagingengine.com \
--to=hendry@iki.fi \
--cc=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).