All of lore.kernel.org
 help / color / mirror / Atom feed
From: Remi Gauvin <remi@georgianit.com>
To: evan d <forumscollective@gmail.com>, linux-btrfs@vger.kernel.org
Subject: Re: Two partitionless BTRFS drives no longer seen as containing BTRFS filesystem
Date: Sat, 6 Oct 2018 20:32:21 -0400	[thread overview]
Message-ID: <ca47dc8e-a99d-f1b9-d3c1-a79794d6f3ac@georgianit.com> (raw)
In-Reply-To: <CAG__1a5fh+H2WnCp6Ofuic_MD-0YNcjReSngbCs1DQypzxNdyQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 812 bytes --]

On 2018-10-06 07:23 PM, evan d wrote:
> I have two hard drives that were never partitioned, but set up as two
> independent BRTFS filesystems.  Both drives were used in the same
> machine running Arch Linux and the drives contain(ed) largely static
> data.
> 
> I decommissioned the machine they were originally used in and on
> installing in a newer Arch build found that BRTFS reported no
> filesystem on either of the drives.
> 
> uname -a:
> Linux z87i-pro 4.18.9-arch1-1-ARCH #1 SMP PREEMPT Wed Sep 19 21:19:17
> UTC 2018 x86_64 GNU/Linux
> 
> btrfs --version: btrfs-progs v4.17.1
> btrfs fi show: returns no data

Did you try a btrfs device scan  ?

(Normally, that would be done on boot, but depending on how your arch
was configured, or if the devices are available early enough in the boot
process....)

[-- Attachment #2: remi.vcf --]
[-- Type: text/x-vcard, Size: 193 bytes --]

begin:vcard
fn:Remi Gauvin
n:Gauvin;Remi
org:Georgian Infotech
adr:;;3-51 Sykes St. N.;Meaford;ON;N4L 1X3;Canada
email;internet:remi@georgianit.com
tel;work:226-256-1545
version:2.1
end:vcard


  reply	other threads:[~2018-10-07  0:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-06 23:23 Two partitionless BTRFS drives no longer seen as containing BTRFS filesystem evan d
2018-10-07  0:32 ` Remi Gauvin [this message]
2018-10-07  6:08   ` evan d
2018-10-07  0:41 ` Qu Wenruo
2018-10-07  6:10   ` evan d
2018-10-07  6:26     ` Qu Wenruo
2018-10-07  6:47       ` evan d
2018-10-07  7:39         ` Qu Wenruo
2018-10-07  8:09           ` evan d
2018-10-07  8:19             ` Qu Wenruo
2018-10-07  8:28               ` evan d
2018-10-07  9:47                 ` Qu Wenruo
2018-10-07 10:39                   ` evan d
2018-10-07 10:51                     ` Qu Wenruo
2018-10-07 12:25                       ` evan d
2018-10-07 12:26                         ` evan d

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=ca47dc8e-a99d-f1b9-d3c1-a79794d6f3ac@georgianit.com \
    --to=remi@georgianit.com \
    --cc=forumscollective@gmail.com \
    --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.