Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #261656

Re: using ddrescue on the root partition - boot with / as read-only

From Vincent Lefevre <vincent@vinc17.net>
Newsgroups linux.debian.user
Subject Re: using ddrescue on the root partition - boot with / as read-only
Date 2023-09-14 11:30 +0200
Message-ID <HdQPD-8U1a-1@gated-at.bofh.it> (permalink)
References <HdwQV-8I0j-1@gated-at.bofh.it> <Hdx0C-8I3x-3@gated-at.bofh.it> <Hdyzn-8IPa-3@gated-at.bofh.it> <HdKTT-8Qwq-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 2023-09-13 23:00:27 -0400, Stefan Monnier wrote:
> > Or perhaps I could use /bin/sh as init, so that systemd (and its
> > remount as rw) would be avoided?
> 
> Indeed booting with `init=/bin/bash` can be a handy option I've used in
> the past: you get into the normal root (so you don't have to figure out
> how to find and mount root from the initramfs), mounted read-only.

I've used init=/bin/sh, but bash (or zsh) would have been more
practical (as dash doesn't have completions).

Two other things are needed:
  * The USB drive must be connected before booting so that the device
    is recognized (otherwise lsblk doesn't list it).
  * At some point, I got too many kernel messages in the console, and
    I couldn't stop them (I thought that they were due to disk errors
    because of ddrescue, but Ctrl-C had no effect). The solution
    I found on the web was to set kernel.printk to 3 3 3 3. I did
    that with:
      sysctl kernel.printk="3 3 3 3"
    Then I resumed ddrescue. Still onging...

-- 
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

using ddrescue on the root partition - boot with / as read-only Vincent Lefevre <vincent@vinc17.net> - 2023-09-13 14:10 +0200
  Re: using ddrescue on the root partition - boot with / as read-only <tomas@tuxteam.de> - 2023-09-13 14:20 +0200
    Re: using ddrescue on the root partition - boot with / as read-only tomas@tuxteam.de - 2023-09-13 14:30 +0200
    Re: using ddrescue on the root partition - boot with / as read-only Vincent Lefevre <vincent@vinc17.net> - 2023-09-13 16:00 +0200
      Re: using ddrescue on the root partition - boot with / as read-only Stefan Monnier <monnier@iro.umontreal.ca> - 2023-09-14 05:10 +0200
        Re: using ddrescue on the root partition - boot with / as read-only Vincent Lefevre <vincent@vinc17.net> - 2023-09-14 11:30 +0200
          Re: using ddrescue on the root partition - boot with / as read-only Stefan Monnier <monnier@iro.umontreal.ca> - 2023-09-14 18:10 +0200
  Re: using ddrescue on the root partition - boot with / as read-only David Christensen <dpchrist@holgerdanske.com> - 2023-09-14 06:00 +0200
    Re: using ddrescue on the root partition - boot with / as read-only Vincent Lefevre <vincent@vinc17.net> - 2023-09-14 12:20 +0200
      Re: using ddrescue on the root partition - boot with / as read-only Michael Kjörling <2695bd53d63c@ewoof.net> - 2023-09-14 14:50 +0200
        Re: using ddrescue on the root partition - boot with / as read-only Max Nikulin <manikulin@gmail.com> - 2023-09-14 16:50 +0200
          Re: using ddrescue on the root partition - boot with / as read-only Vincent Lefevre <vincent@vinc17.net> - 2023-09-14 17:40 +0200
      Re: using ddrescue on the root partition - boot with / as read-only David Christensen <dpchrist@holgerdanske.com> - 2023-09-15 07:30 +0200
        Re: using ddrescue on the root partition - boot with / as read-only Vincent Lefevre <vincent@vinc17.net> - 2023-09-15 14:50 +0200
          Re: using ddrescue on the root partition - boot with / as read-only David Christensen <dpchrist@holgerdanske.com> - 2023-09-15 23:00 +0200

csiph-web