qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Snow <jsnow@redhat.com>
To: Alexander Marx <copymaster@howtolinux.de>, qemu-devel@nongnu.org
Cc: Qemu-block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] Please help corrupt filesystem image
Date: Mon, 18 Feb 2019 15:54:58 -0500	[thread overview]
Message-ID: <2c817163-f940-98f9-ad6e-5da1f70baf99@redhat.com> (raw)
In-Reply-To: <d5dc1bda-6b43-cbd6-3faa-69bb0ae45af4@howtolinux.de>



On 2/16/19 10:54 PM, Alexander Marx wrote:
> Dear List!
> 
> I have a big problem and hope you can help me.
> I built a new windows 2016 domain with virtual servers. 2 dc and 9 rds
> hosts.
> I was nearly finished with the setup and ready to migrate the users from
> old to new domain.
> 
> Then i had to restart the physical servers. Unfortunately 1 dc and 2 rds
> hosts could not be startet anymore.
> Error says:
> 
> qemu-img: Could not open 'vm-150-disk-0.qcow2': Could not read qcow2
> header: Input/output error
> 
> Even worst, a qemu-img check  also gave that error. and i was not able
> to do anything i found in the internet to fix it.
> always that error or the qemu-img could not determine the format.
> 
> Is there a chance to fix these images? What can i do?
> 
> I have no backup because the domain was not fully configured. But if i
> have to rebuild the whole domain, i will need several weeks for it.
> Any help is appreciated.
> 
> Thank you
> 
> Alex
> 

What versions of QEMU were you running?
What filesystem were these images stored on?
What happened at the time of the corruption, is there some detail that
might help explain the nature of the corruption? Did you shut down the
physical host while the VMs were still running?

There may not be a way to recover these images, but we should probably
make sure that your configuration isn't unsafe to prevent this kind of
problem in the future.

  reply	other threads:[~2019-02-18 21:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-17  3:54 [Qemu-devel] Please help corrupt filesystem image Alexander Marx
2019-02-18 20:54 ` John Snow [this message]
2019-02-19  4:05   ` Alexander Marx
  -- strict thread matches above, loose matches on Subject: below --
2019-02-17  4:13 Alexander Marx
2019-02-18  9:51 ` Kevin Wolf
2019-02-18 10:31   ` Alexander Marx

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2c817163-f940-98f9-ad6e-5da1f70baf99@redhat.com \
    --to=jsnow@redhat.com \
    --cc=copymaster@howtolinux.de \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).