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

Groups > linux.debian.user > #187325

Re: Restore backup to KVM

From solitone <solitone@mail.com>
Newsgroups linux.debian.user
Subject Re: Restore backup to KVM
Date 2017-09-27 19:00 +0200
Message-ID <uunQK-5FA-15@gated-at.bofh.it> (permalink)
References (7 earlier) <utW49-42r-7@gated-at.bofh.it> <uu07M-6zu-19@gated-at.bofh.it> <uu41J-zi-43@gated-at.bofh.it> <uueu6-7gi-13@gated-at.bofh.it> <uujk6-2b5-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw

On 27/09/17 14:01, solitone wrote:
> Although mkfs had warned me, I mistakenly formatted the entire file, 
> like this:
> 
> $ sudo mkfs.ext4 restore.img
> 
> Now I've redone it the right way, using a loop device, and I'll see how 
> it goes.

It's a struggle! Now that I partitioned the image file, it sees 
/dev/sda1. There was an inconsistency between the filesystem size and 
the physical size of the device though, that I repaired with resize2fs, 
specifying the physical number of blocks.

Now it finally mounts /dev/sda1, but on /root rather than on /, as it 
did before with the unpartitioned image file (/dev/sda):

======================================================================
Begin: Will now check root file system ... fsck from util-linux 2.29.2
[/sbin/fsck.ext4 (1) -- /dev/sda1] fsck.ext4 -a -C0 /dev/sda1
/dev/sda1: clean, 434181/5898240 files, 15163981/23592711 blocks
done.
[   33.088863] EXT4-fs (sda1): 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.


BusyBox v1.22.1 (Debian 1:1.22.0-19+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) df
Filesystem           1K-blocks      Used Available Use% Mounted on
udev                     46448         0     46448   0% /dev
tmpfs                    11684        60     11624   1% /run
/dev/sda1             92365508  58650588  28980000  67% /root
(initramfs)
======================================================================

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