From: Hendrik Friedel <hendrik@friedels.name>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: booting from BTRFS works only with one device in the pool
Date: Tue, 2 Feb 2016 22:59:57 +0100 [thread overview]
Message-ID: <56B126DD.90009@friedels.name> (raw)
In-Reply-To: <CAJCQCtRox+q5u902iwA3YL2yvEP+9_=02HJzpZU6TWZ1R9V+Qg@mail.gmail.com>
Hello Chris,
> That's a bit weird. This is BIOS or UEFI system? On UEFI, the prebaked
> grubx64.efi includes btrfs, so insmod isn't strictly needed. But on
> BIOS it would be.
it is a Virtual-Box-VM. It is a BIOS system
> It might be as simple as manually mounting:
>btrfs dev scan
>btrfs fi show
## hopefully both devices are now associated with the volume
> mount /dev/sdXY /sysroot
> exit
The mount works.
After entering "exit" I get the feedback "logout" and the system hangs.
> If it mounts, you can exit to continue the startup process. And then:
dracut -f That'll rebuild the initramfs.
And dracut then somehow understands that btrfs dev scan is needed?
>> set root='hd0,msdos1'
>> search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1
>> --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 --hint='hd0,msdos1'
>> 4a470ac6-f013-4e7b-a4f3-3a58cc4debc3
>>
>> after removing sda3 from the pool again, the system boots normally.
> That's unexpected. Both devices should now refer to each other, so
> either device missing should fail, it's effectively raid0 except on a
> chunk level.
>
That's way beyond my understanding. I am not sure how this entry is
generated. But it is somehow a default behavior, as it seems (I have not
done this)
Greetings,
Hendrik
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
next prev parent reply other threads:[~2016-02-02 22:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-01 21:31 booting from BTRFS works only with one device in the pool Hendrik Friedel
2016-02-01 22:11 ` Hugo Mills
2016-02-01 23:02 ` Duncan
2016-02-01 23:15 ` Hugo Mills
2016-02-02 22:01 ` Hendrik Friedel
2016-02-02 22:06 ` Chris Murphy
2016-02-03 6:31 ` Hendrik Friedel
2016-02-02 22:09 ` Hugo Mills
2016-02-01 23:29 ` Chris Murphy
2016-02-02 21:59 ` Hendrik Friedel [this message]
2016-02-02 22:04 ` Chris Murphy
2016-02-03 18:14 ` Hendrik Friedel
2016-02-03 20:30 ` Chris Murphy
2016-02-03 22:19 ` Chris Murphy
2016-02-13 14:38 ` Hendrik Friedel
2016-02-13 18:20 ` Chris Murphy
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=56B126DD.90009@friedels.name \
--to=hendrik@friedels.name \
--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 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.