All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Debian Bullseye install btrfs raid1
Date: Wed, 4 May 2022 12:27:29 +0300	[thread overview]
Message-ID: <c0a5db9f-2631-9177-929c-9e76a9c67ec5@suse.com> (raw)
In-Reply-To: <20220504112315.71b41977e071f43db945687c@lucassen.org>



On 4.05.22 г. 12:23 ч., richard lucassen wrote:
> Hello list,
> 
> Still new to btrfs, I try to set up a system that is capable of booting
> even if one of the two disks is removed or broken. The BIOS supports this.
> 
> As the Debian installer is not capable of installing btrfs raid1, I
> installed Bullseye using /dev/md0 for /boot (ext2) and a / btrfs on /dev/sda3.
> This works of course. After install I added /dev/sdb3 to the / fs: OK.
> Reboot: works. Proof/pudding/eating: I stopped the system, removed one of the
> disks and started again. It boots, but it refuses to mount the / fs, either
> without sda or sdb.
> 
> Question: is this newbie trying to set up an impossible config or have I
> missed something crucial somewhere?

That's the default behavior, the reasoning is if you are missing one 
device of a raid1 your data is at-risk in case the 2nd device fails. You 
can override this behavior by mounting in degraded mode, that is
mount -odegraded

> 
> R.
> 
> Begin: Running /scripts/init-premount ... done.
> Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
> Begin: Running /scripts/local-premount ... [    6.809309] Btrfs loaded, crc32c=crc32c-generic
> Scanning for Btrfs filesystems
> [    6.849966] random: fast init done
> [    6.884290] BTRFS: device label data devid 1 transid 50 /dev/sda6 scanned by btrfs (171)
> [    6.892822] BTRFS: device fsid 1739f989-05e0-48d8-b99a-67f91c18c892 devid 1 transid 23 /dev/sda5 scanned by btrfs (171)
> [    6.903959] BTRFS: device fsid f9cf579f-d3d9-49b2-ab0d-ba258e9df3d8 devid 1 transid 3971 /dev/sda3 scanned by btrfs (171)
> Begin: Waiting for suspend/resume device ... Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... done.
> Begin: Running /scripts/local-block ... [   27.015660] md/raid1:md0: active with 1 out of 2 mirrors
> [   27.021181] md0: detected capacity change from 0 to 262078464
> [   27.036555] md/raid1:md1: active with 1 out of 2 mirrors
> [   27.042062] md1: detected capacity change from 0 to 4294901760
> done.
> done.
> done.
> Warning: fsck not present, so skipping root file system
> [   27.235880] BTRFS info (device sda3): flagging fs with big metadata feature
> [   27.242984] BTRFS info (device sda3): disk space caching is enabled
> [   27.249314] BTRFS info (device sda3): has skinny extents
> [   27.258259] BTRFS error (device sda3): devid 2 uuid 5b50e238-ae76-426f-bae3-deee5999adbc is missing
> [   27.267448] BTRFS error (device sda3): failed to read the system array: -2
> [   27.275696] BTRFS error (device sda3): open_ctree failed
> mount: mounting /dev/sda3 on /root failed: Invalid argument
> Failed to mount /dev/sda3 as root file system.
> 
> 
> BusyBox v1.30.1 (Debian 1:1.30.1-6+b3) built-in shell (ash)
> Enter 'help' for a list of built-in commands.
> 
> (initramfs)
> 
> 

  reply	other threads:[~2022-05-04  9:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-04  9:23 Debian Bullseye install btrfs raid1 richard lucassen
2022-05-04  9:27 ` Nikolay Borisov [this message]
2022-05-04  9:30   ` richard lucassen
2022-05-04 10:02   ` richard lucassen
2022-05-04 10:07     ` Nikolay Borisov
2022-05-04 10:14       ` richard lucassen
2022-05-04 10:26         ` Andy Smith
2022-05-04 11:16           ` richard lucassen
2022-05-04 18:15         ` Andrei Borzenkov
2022-05-04 19:33           ` richard lucassen
2022-05-05  8:27             ` Nikolay Borisov
2022-05-05 20:30               ` richard lucassen
2022-05-09  6:50             ` Andrei Borzenkov
2022-05-04 12:06 ` Hans van Kranenburg
2022-05-04 12:59   ` richard lucassen

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=c0a5db9f-2631-9177-929c-9e76a9c67ec5@suse.com \
    --to=nborisov@suse.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.