From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxim Cournoyer Subject: Re: cannot boot with BTRFS in degraded mode Date: Sat, 07 Sep 2019 09:20:53 +0900 Message-ID: <87zhjhufbu.fsf@gmail.com> References: <87lfv4163w.fsf@roquette.mug.biscuolo.net> <87a7bi25fv.fsf@roquette.mug.biscuolo.net> <87d0gexmpq.fsf@gmail.com> <87zhjiym0e.fsf@roquette.mug.biscuolo.net> <87ef0tx55d.fsf@gmail.com> <87tv9pzrhe.fsf@roquette.mug.biscuolo.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:43267) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i6OTO-0002GO-Kh for help-guix@gnu.org; Fri, 06 Sep 2019 20:21:03 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i6OTM-00051r-5M for help-guix@gnu.org; Fri, 06 Sep 2019 20:21:02 -0400 Received: from mail-pg1-x541.google.com ([2607:f8b0:4864:20::541]:43120) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i6OTL-00050P-KL for help-guix@gnu.org; Fri, 06 Sep 2019 20:21:00 -0400 Received: by mail-pg1-x541.google.com with SMTP id u72so4406997pgb.10 for ; Fri, 06 Sep 2019 17:20:59 -0700 (PDT) In-Reply-To: <87tv9pzrhe.fsf@roquette.mug.biscuolo.net> (Giovanni Biscuolo's message of "Fri, 06 Sep 2019 11:47:09 +0200") List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Giovanni Biscuolo Cc: help-guix Hello Giovanni, Giovanni Biscuolo writes: > Hello Maxim, > > Maxim Cournoyer writes: > > [...] > >> Fixing the Grub config (manually or not) is one thing, but not enough, >> as it is the init script (contained within the initrd) > > Yes I was obviously wrong: the initrd must be updated, also! > >> run by the kernel >> that mounts the root partition. This script currently doesn't honor the >> rootflags= argument given to the Linux kernel command line, which means >> that you cannot pass extra options (such as 'degraded') to mount your >> root partition during the early boot process of the system. > > Yes, now I understand, thanks! > >>> Anyway, with the help of a friend, in a few hours we are going to test >>> this solution :-) >> >> Good luck! > > The only viable solution to this problem is to boot a rescue system and > fix the BTRFS array there: I'm doing it now via grml (remotely via ssh > with the help of a friend who "manually" started the network and ssh > daemon) > > For the records, this is what I did: > > 1. btrfs replace start 5 /dev/sde /target (since the missimg one was the > 5th) > > 2. btrfs replace status /target > > it took less then 10 mins to replace a 1TB disk with 76.28GiB used: > > Started on 6.Sep 09:21:44, finished on 6.Sep 09:40:45, 0 write errs, 0 uncorr. read errs Great! It looks like you're all set! Thank you for maintaining a build machine :-). Maxim