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


Groups > linux.debian.user > #187423

Re: Restore backup to KVM

From solitone <solitone@mail.com>
Newsgroups linux.debian.user
Subject Re: Restore backup to KVM
Date 2017-09-30 15:50 +0200
Message-ID <uvqjv-4NB-11@gated-at.bofh.it> (permalink)
References (6 earlier) <uujk6-2b5-7@gated-at.bofh.it> <uunQK-5FA-15@gated-at.bofh.it> <uuAXD-5v7-1@gated-at.bofh.it> <uuVfH-1vc-7@gated-at.bofh.it> <uvnOF-3lm-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


This is serious hacking :^)

On 30/09/17 13:04, Reco wrote:
> the next thing I have to suspect is that your backup misses
> /dev directory (possibly /proc and /sys). The contents for those are
> irrelevant. You simply do not have /dev, /proc, /sys in your root
> filesystem.

No, I don't, you're perfectly right! Now I've made /dev, /proc, /sys, as 
well as /run and now it boots right.

I still have several error messages complaining about the floppy disk 
(?), which slow booting, but everything seems to end well. Now I'll try 
to correct grub. Thanks!

===================================================================
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top 
... done.
Begin: Running /scripts/local-premount ... [    1.688631] 
blk_update_request: I/O error, dev fd0, sector 0
[    1.689678] floppy: error -5 while reading block 0
[    1.699913] random: fast init done
[    1.760666] blk_update_request: I/O error, dev fd0, sector 0
[    1.762276] floppy: error -5 while reading block 0
Begin: Waiting for suspend/resume device ... Begin: Running 
/scripts/local-block ... done.
[    2.828592] blk_update_request: I/O error, dev fd0, sector 0
[    2.829812] floppy: error -5 while reading block 0
[    2.888813] blk_update_request: I/O error, dev fd0, sector 0
[    2.890727] floppy: error -5 while reading block 0
Begin: Running /scripts/local-block ... done.
[    3.964558] blk_update_request: I/O error, dev fd0, sector 0
[    3.966112] floppy: error -5 while reading block 0
[    4.024658] blk_update_request: I/O error, dev fd0, sector 0
[    4.027035] floppy: error -5 while reading block 0
[...]
Begin: Running /scripts/local-block ... done.
[   32.404669] blk_update_request: I/O error, dev fd0, sector 0
[   32.406074] floppy: error -5 while reading block 0
[   32.464656] blk_update_request: I/O error, dev fd0, sector 0
[   32.465880] floppy: error -5 while reading block 0
done.
[   32.536758] blk_update_request: I/O error, dev fd0, sector 0
[   32.539140] floppy: error -5 while reading block 0
[   32.600728] blk_update_request: I/O error, dev fd0, sector 0
[   32.603490] floppy: error -5 while reading block 0
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/sda1] fsck.ext4 -a -C0 /dev/sda1
/dev/sda1: clean, 434185/5898240 files, 15163985/23592711 blocks
done.
[   33.183454] EXT4-fs (sda1): mounted filesystem with ordered data 
mode. Opts: (null)
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
bash: cannot set terminal process group (-1): Inappropriate ioctl for device
bash: no job control in this shell
root@(none):/#
===================================================================

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