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


Groups > linux.debian.user > #187236

Re: Restore backup to KVM

From solitone <solitone@mail.com>
Newsgroups linux.debian.user
Subject Re: Restore backup to KVM
Date 2017-09-26 13:20 +0200
Message-ID <utW49-42r-7@gated-at.bofh.it> (permalink)
References (4 earlier) <utaVA-6wY-15@gated-at.bofh.it> <utbRE-76z-3@gated-at.bofh.it> <utH58-2b5-7@gated-at.bofh.it> <utRQR-150-5@gated-at.bofh.it> <utVUu-3YA-11@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 26/09/17 13:01, solitone wrote:
> It's strange, since it finds /dev/sda, i.e. the entire disk:
> 
> =========================================================
> [    6.438693] sd 0:0:0:0: [sda] 188743680 512-byte logical blocks: 
> (96.6 GB/90.0 GiB)
> [    6.469182] sd 0:0:0:0: [sda] Write Protect is off
> [    6.482421] sd 0:0:0:0: [sda] Write cache: enabled, read cache: 
> enabled, doesn't support DPO or FUA
> =========================================================
> 
> However, it then complains that /dev/sda1 does not exists

I've found out that if I specify /dev/sda like this:

$ qemu-system-x86_64 -hda alan_restore.img
-kernel /vmlinuz
-initrd /initrd.img
-append "root=/dev/sda ro init=/bin/bash"

then it finds, checks, and mounts the root file system. However now it 
fails because it tries to mount /dev and /run on /root/dev and 
/root/run, rather than simply /dev and /run:

=========================================================
[...]
Gave up waiting for suspend/resume device
done.
Begin: Will now check root file system ... fsck from util-linux 2.29.2
[/sbin/fsck.ext4 (1) -- /dev/sda] fsck.ext4 -a -C0 /dev/sda
/dev/sda: clean, 434616/5898240 files, 15174007/23592960 blocks
done.
[   40.335292] EXT4-fs (sda): mounted filesystem with ordered data mode. 
Opts: (null)
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: opening console: No such file or directory
Target filesystem doesn't have requested /bin/bash.
run-init: opening console: No such file or directory
run-init: opening console: No such file or directory
run-init: opening console: No such file or directory
run-init: opening console: No such file or directory
run-init: opening console: No such file or directory
No init found. Try passing init= bootarg.
=========================================================

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


Thread

Restore backup to KVM solitone <solitone@mail.com> - 2017-09-22 06:50 +0200
  Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-22 08:10 +0200
    Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-22 21:20 +0200
      Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-22 21:40 +0200
        Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-24 11:00 +0200
          Re: Restore backup to KVM <tomas@tuxteam.de> - 2017-09-24 11:20 +0200
          Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-24 12:00 +0200
            Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-25 21:10 +0200
              Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-26 08:50 +0200
            Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-25 21:20 +0200
              Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-26 08:50 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-26 13:10 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-26 13:20 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-26 17:40 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-26 21:20 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-26 21:50 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-27 09:00 +0200
                Re: Restore backup to KVM "Thomas Schmitt" <scdbackup@gmx.net> - 2017-09-27 09:50 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-27 10:40 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-27 14:10 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-27 19:00 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-28 09:00 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-29 06:40 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-29 08:40 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-30 13:10 +0200
                Re: Restore backup to KVM solitone <solitone@mail.com> - 2017-09-30 15:50 +0200
                Re: Restore backup to KVM Reco <recoverym4n@gmail.com> - 2017-09-30 17:00 +0200

csiph-web