From mboxrd@z Thu Jan 1 00:00:00 1970 From: Giovanni Biscuolo Subject: Re: cannot boot with BTRFS in degraded mode Date: Fri, 06 Sep 2019 11:47:09 +0200 Message-ID: <87tv9pzrhe.fsf@roquette.mug.biscuolo.net> 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> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:39972) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i6Apn-0000Qb-T0 for help-guix@gnu.org; Fri, 06 Sep 2019 05:47:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i6Apm-0003hf-O7 for help-guix@gnu.org; Fri, 06 Sep 2019 05:47:15 -0400 Received: from ns13.heimat.it ([46.4.214.66]:50478) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1i6Apm-0003c3-Eg for help-guix@gnu.org; Fri, 06 Sep 2019 05:47:14 -0400 In-Reply-To: <87ef0tx55d.fsf@gmail.com> 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: Maxim Cournoyer Cc: help-guix --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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=3D 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: =2D-8<---------------cut here---------------start------------->8--- Started on 6.Sep 09:21:44, finished on 6.Sep 09:40:45, 0 write errs, 0 un= corr. read errs =2D-8<---------------cut here---------------end--------------->8--- [...] Thank you again for your support! Gio' =2D-=20 Giovanni Biscuolo Xelera IT Infrastructures --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEERcxjuFJYydVfNLI5030Op87MORIFAl1yKx0ACgkQ030Op87M ORLBbw//ZbMozQ1M9ZC+DyJlNZ6w/iF5gplaJtwrB8iZ6kAHGFsc7Wf2lLYElW/x WF3CT3CNyIwT8c1gPWahUpSr4csBgl+6Yx2cAJ+vqaj78dkhFAP/5PHhpjZqpUBf 7zahS/rgveot5E5Wc3ZmMeQAUQ9UYSTzOLWVg5e5DRQ/PYfYoZ3REvJEFrlPmky5 XESAE9euNtqoVPNKkYn1scp+yfnL3k/NGWbkKs51EBnfL59hUzT9p3fQU8AWH760 +V/Hh70IlSLoIZ/IdObBAwI+NJWtQQNg0VOXRNpx8jVF53Y1RVMwyFULAwYLQq+y 1ZlNZs0NyYrVbDY9lqyMb3HExz+AWeB9VLhUnQ/OgZ92pOCc/y4vj/ULBozHELlQ 9cvTIjUg63eXt4WVBdcE/7MDBPqqpIwAUAX7lRexQdx73EgYPD3oUcXeLiTqqkNR 3O9BJYHFKkInYTJL6iosACDUETyGnbNn9Jlz+kDwu6rG08AoXIbAqUfm7pVSwTh/ 8RKzf9dm6sMpcyR8LuJY/jvxUK6Wyied2dE34SmMtF0YDN3d8g+WZ3/08K1YRAJT 7kwhcffcJiz8/U6Tj0Vn/g2tIVItvCzvxzf5Dp1jEeMfzTgfOSbDahOY/NxRu0x7 Lp8vvB6vrCRjScpQjOsKSzIG/lv5WZpYvdIVwOX54xF2JVtL7bc= =72Jk -----END PGP SIGNATURE----- --=-=-=--