All of lore.kernel.org
 help / color / mirror / Atom feed
From: richard lucassen <mailinglists@lucassen.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: Debian Bullseye install btrfs raid1
Date: Wed, 4 May 2022 13:16:32 +0200	[thread overview]
Message-ID: <20220504131632.00ffbd49c7ec5a7782f0e662@lucassen.org> (raw)
In-Reply-To: <20220504102608.u4oublhjagp5h5hm@bitfolk.com>

On Wed, 4 May 2022 10:26:08 +0000
Andy Smith <andy@strugglers.net> wrote:

> You can pause at the grub menu and edit the current boot selection
> to have the additional kernel command line parameter:
> 
>     rootflags=degraded
> 
> That has the same effect as "Mount -o degraded …" or putting
> "degraded" in the fstab options.

Yes, but apparently I fsck'd up the whole system, even with two disks.
I will first add a single disk / filesystem as rescue (never mind, this
is a test system):

[    5.622734]  sdb: sdb1 sdb2 sdb3 sdb4 < sdb5 sdb6 >
[    5.634754]  sda: sda1 sda2 sda3 sda4 < sda5 sda6 >
[    5.649152] sd 1:0:0:0: [sdb] Attached SCSI disk
[    5.652889] sd 0:0:0:0: [sda] Attached SCSI disk
[    5.724026] random: fast init done
[    5.821439] md/raid1:md0: active with 2 out of 2 mirrors
[    5.827536] md0: detected capacity change from 0 to 262078464
[    5.828427] md/raid1:md1: active with 2 out of 2 mirrors
[    5.839332] md1: detected capacity change from 0 to 4294901760

[..]

Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... [    6.826141] Btrfs loaded, crc32c=crc32c-generic
Scanning for Btrfs filesystems
[    6.868147] random: fast init done
[    6.901066] BTRFS: device label data devid 1 transid 50 /dev/sda6 scanned by btrfs (171)
[    6.909951] BTRFS: device fsid 1739f989-05e0-48d8-b99a-67f91c18c892 devid 1 transid 23 /dev/sda5 scanned by btrfs (171)
[    6.921421] BTRFS: device fsid f9cf579f-d3d9-49b2-ab0d-ba258e9df3d8 devid 1 transid 3994 /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.012381] md/raid1:md0: active with 1 out of 2 mirrors
[   27.017890] md0: detected capacity change from 0 to 262078464
[   27.033248] md/raid1:md1: active with 1 out of 2 mirrors
[   27.038793] md1: detected capacity change from 0 to 4294901760
done.
done.
done.
Warning: fsck not present, so skipping root file system
[   27.229282] BTRFS info (device sda3): flagging fs with big metadata feature
[   27.236375] BTRFS info (device sda3): allowing degraded mounts
[   27.242285] BTRFS info (device sda3): disk space caching is enabled
[   27.248579] BTRFS info (device sda3): has skinny extents
[   27.256813] BTRFS warning (device sda3): devid 2 uuid 5b50e238-ae76-426f-bae3-deee5999adbc is missing
[   27.266833] BTRFS warning (device sda3): devid 2 uuid 5b50e238-ae76-426f-bae3-deee5999adbc is missing
[   27.284235] BTRFS info (device sda3): enabling ssd optimizations
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such file or directory
mount: mounting /dev on /root/dev failed: No such file or directory
done.
mount: mounting /run on /root/run failed: No such file or directory
run-init: can't execute '/sbin/init': No such file or directory
Target filesystem doesn't have requested /sbin/init.
run-init: can't execute '/sbin/init': No such file or directory
run-init: can't execute '/etc/init': No such file or directory
run-init: can't execute '/bin/init': No such file or directory
run-init: can't execute '/bin/sh': No such file or directory
run-init: can't execute '': No such file or directory
No init found. Try passing init= bootarg.


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)


-- 
richard lucassen
https://contact.xaq.nl/

  reply	other threads:[~2022-05-04 11:16 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
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 [this message]
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=20220504131632.00ffbd49c7ec5a7782f0e662@lucassen.org \
    --to=mailinglists@lucassen.org \
    --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.