Virtualbox disk read error occurred

Your help is appreciated.
  • Reply with quote

A disk read error occurred

Your help is appreciated.

Upon Normal Start to the Oracle VM VirtualBox:-

A Disk read error occurred
Press Ctrl+Alt+Del to restart

With Endless Blessings in the Son of God,
LEUNG, [Ms.]

Iris Leung
 
Posts: 16
Joined: 22. Jan 2018, 14:31

  • Reply with quote

Re: A disk read error occurred

Postby socratis » 12. Mar 2018, 18:50

This is an error from within your guest. Deal with it as a guest problem, not a VirtualBox problem. If this happens when your VM starts, then I suspect a corrupt «disk». You’ll have to use the appropriate tools for your guest to fix it…

PS. I have sent you a Private Message a long time ago, could you please read your messages?

Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the «QUOTE» button, please use the «POST REPLY«, at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.

socratis
Site Moderator
 
Posts: 27689
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

  • Reply with quote

Re: A disk read error occurred

Postby Iris Leung » 13. Mar 2018, 03:03

Dear socratis,

Thank you for your kindest reply, thought we are of different religion(s), myself do truly hope that my Father, the Son of God, does show understanding on you. Nevertheless, myself am thankful for all the help I could obtain from this forum from Oracle Corporation.

«This is an error from within your guest.» <- Can you please do kindly specific this…

«You’ll have to use the appropriate tools for your guest to fix it.» <- Can you please do kindly further and suggest of the appropriate media for fixing this problem.

Your help is truly appreciated.

With Endless and the Holiest Blessings in the Son of God,
LEUNG, [Ms.]

Iris Leung
 
Posts: 16
Joined: 22. Jan 2018, 14:31

  • Reply with quote

Re: A disk read error occurred

Postby socratis » 13. Mar 2018, 11:27

I have deleted your duplicate post, they are not allowed.

Just because an OS/program that runs in the context of VirtualBox has a problem, it doesn’t make it a VirtualBox problem. You’re having an issue that has most probably nothing to do with VirtualBox, so my suggestion would be to treat it as such, as a native problem with the OS or the application of the guest.

PS. Could you please refrain from any religious, political or sports messages in your greetings? Not all of the people share the same beliefs, and this is not the place for such discussions.

Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the «QUOTE» button, please use the «POST REPLY«, at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.

socratis
Site Moderator
 
Posts: 27689
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

  • Reply with quote

Re: A disk read error occurred

Postby andyp73 » 13. Mar 2018, 11:49

Iris Leung wrote:«This is an error from within your guest.»

To simplify what Socratis has said…

In the same way that a physical PC goes through the process of power on, BIOS, boot OS from hard disk the VirtualBox guest does the same thing. In your case, it has completed the first two of these tasks but when it has attempted the third of them it has discovered that the disk is corrupt. With VirtualBox this means that the contents of the .vdi file as the guest sees them are corrupt.

Iris Leung wrote:«You’ll have to use the appropriate tools for your guest to fix it.»

You will need to boot the guest VM from the ISO image you have of the Windows XP installation media, boot into recovery mode and see if it can repair the disk.

If that fails, and you don’t have a backup of your data files, you may need to reinstall Windows XP in a new VM, connect the old .vdi file as a secondary disk and hope you can read your important files from it that way.

All done the same way as if you had hit the same problem with a physical hardware platform and actual disk drives.

-Andy.

My crystal ball is currently broken. If you want assistance you are going to have to give me all of the necessary information.
Please don’t ask me to do your homework for you, I have more than enough of my own things to do.

andyp73
Volunteer
 
Posts: 1642
Joined: 25. May 2010, 23:48
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Assorted Linux, Windows Server 2012, DOS, Windows 10, BIOS/UEFI emulation

  • Reply with quote

Re: A disk read error occurred

Postby mpack » 13. Mar 2018, 12:21

A disk read error reported by the guest could be a problem with the host VDI file, or it could be entirely a guest problem. Without a VM log file we can never know.

mpack
Site Moderator
 
Posts: 37957
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: PUEL
Guest OSses: Mostly XP

  • Reply with quote

Re: A disk read error occurred

Postby Iris Leung » 14. Mar 2018, 09:32

Dear socratis,

May you please do kindly delete this post, I personally opt to post on another board.

Thank you for your time and patience.

With Endless and the Holiest Blessings in the Son of God,
LEUNG, [Ms.]

Iris Leung
 
Posts: 16
Joined: 22. Jan 2018, 14:31

  • Reply with quote

Re: A disk read error occurred

Postby socratis » 14. Mar 2018, 10:14

Iris Leung wrote:I personally opt to post on another board.

Posting a duplicate is not an option that you have I’m afraid. This is the 2nd time that you are posting a duplicate, and the 2nd time that I am forced to delete it. There will not be a 3rd time. I hope that this message is quite clear.

Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the «QUOTE» button, please use the «POST REPLY«, at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.

socratis
Site Moderator
 
Posts: 27689
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

  • Reply with quote

Re: A disk read error occurred

Postby Iris Leung » 14. Mar 2018, 10:22

Dear socratis,

May you please do kindly delete this topic, before I shall move on to post it on to another board.

Thank you for your time and patience.

With Endless and the Holiest Blessings in the Son of God,
LEUNG, [Ms.]

Last edited by socratis on 14. Mar 2018, 10:25, edited 1 time in total.

Reason: Removed URL.

Iris Leung
 
Posts: 16
Joined: 22. Jan 2018, 14:31

  • Reply with quote

Re: A disk read error occurred

Postby socratis » 14. Mar 2018, 10:24

  1. You have a problem with your guest. It is in my opinion that your message belongs in the «Windows Guests» forum. Even if it was posted somewhere else (in another section), I would have moved it here. This is where it should be, this is where it will stay.
  2. I have edited your message to remove a URL to a religious picture. I have asked you both in private and in public to refrain from any religious, political or sports messages in your greetings and your posts. Not only you didn’t refrain, but you now started including URLs to unrelated 3rd party religious images. If this continues, I will be forced to take more drastic action. This is your 3rd warning. You are starting to test the limits of my patience.

Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the «QUOTE» button, please use the «POST REPLY«, at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.

socratis
Site Moderator
 
Posts: 27689
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5

  • Reply with quote

Re: A disk read error occurred

Postby Iris Leung » 14. Mar 2018, 10:29

Dear socratis,

May you please do kindly delete this topic, before I shall move on to post it on to another board with my personal signature.

Thank you for your time and patience, and understanding.

With Endless and the Holiest Blessings in the Son of God,
LEUNG, [Ms.]

Iris Leung
 
Posts: 16
Joined: 22. Jan 2018, 14:31

  • Reply with quote

Re: A disk read error occurred

Postby socratis » 14. Mar 2018, 10:32

Actually I will ban you for a 3-day cooling period. I do not have to deal with 3 copy/paste messages in a row. Other people are also waiting for help.

And if your personal signature continues to ignore the advice given, a more permanent ban might follow.

Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the «QUOTE» button, please use the «POST REPLY«, at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.

socratis
Site Moderator
 
Posts: 27689
Joined: 22. Oct 2010, 11:03
Location: Greece
Primary OS: Mac OS X other
VBox Version: PUEL
Guest OSses: Win(*>98), Linux*, OSX>10.5


Return to Windows Guests

Who is online

Users browsing this forum: Google [Bot] and 21 guests

  • Home
  • Forum
  • The Ubuntu Forum Community
  • Ubuntu Specialised Support
  • Virtualisation
  • [ubuntu] Virtualbox VM says «Disk Read Error. Press CTRL-ALT-DEL to restart»

  1. Virtualbox VM says «Disk Read Error. Press CTRL-ALT-DEL to restart»

    A friend of mine recently did a complete reinstall of Ubuntu and I had him copy all the files (including hidden items) from his Home folder onto a couple external hard drives (with NTFS partitions on them, I think). I’m not exactly sure how he re-added the machines to his inventory, but he did copy his .Virtualbox folder from his external drive back to his new Home folder.

    Anyway, when I tried to start up one of his machines, it spit an error message out similar to this one:

    Failed to power up VM! Error info:
    Medium ‘/home/matt/VMImages/WindowsXPSP3.vdi’ is not accessible. Could not open the hard disk ‘/home/matt/VMImages/WindowsXPSP3.vdi’.

    I went into the Machine settings to check and see what it was using for storage (assuming the path name was incorrect) and re-selected the vdi file for the virtual disk. Also, not too sure what the problem might be, I added the user to the vboxusers group and changed the permissions for everything in the /.Virtualbox folder to be read/write accessible for all users.

    The next time I booted, the VM started but this time in the VM display (virtual screen, if you will) was a box that said «A Disk Read Error Occurred. Press CTRL-ALT-DEL to restart.» (like the attachment).

    So I’m not sure what to do about this. I always thought you could just copy and paste the ~/.Virtualbox folder from one Home folder to another and then install VB, then add the machines back in or they’d already be there…


  2. Re: Virtualbox VM says «Disk Read Error. Press CTRL-ALT-DEL to restart»


  3. Re: Virtualbox VM says «Disk Read Error. Press CTRL-ALT-DEL to restart»

    The error message is accurate.

    Delete and re-add the .vdi to the Virtual Media Manager, and then reassociate the disk with the VM under the ‘Storage’ tab for the VM.


  4. Re: Virtualbox VM says «Disk Read Error. Press CTRL-ALT-DEL to restart»

    Did this work for you? I have a friend having the same issue. There is also an extra .vdi in the Hard Disks folder. I don’t understand where it came from. The vdi I they have been using all along is in the proper folder. Nothing has changed. Does this coincide with what you were experiencing as well?


  5. Re: Virtualbox VM says «Disk Read Error. Press CTRL-ALT-DEL to restart»

    Quote Originally Posted by Nausser
    View Post

    Did this work for you? I have a friend having the same issue. There is also an extra .vdi in the Hard Disks folder. I don’t understand where it came from. The vdi I they have been using all along is in the proper folder. Nothing has changed. Does this coincide with what you were experiencing as well?

    It did work… and one of the weird things I noticed at the time was the vdi files we were trying to load into Virtualbox were truncated in file size. What was supposed to be about 16 gigs was cut off at 4 gigs; in fact all the vdi files were. Fortunately we went back to the external hard drive he originaly backed the machines up on to and re-copied the full size vdi files over. We then, more or less, re-created the machines from scratch. The key here is to make sure that Virtualbox’s little inventory is cleared, or made «unaware», of the old VDI files. It’s kind of like the way it «stores» a small selection of recently used ISO files you’ve mounted to the CD/DVD device for a VM. If you deleted one of those ISO files, you’ll still see the file listed in the inventory, but you’ll likely get an error message that tells you the file is missing, so you have to also delete that iso out of Virtualbox.

    One of the snags I also ran into while removing the old VDI files was that one machine had associated itself with a VDI file that had snapshots saved, but the VDI file was named slightly different, and as a result, the machine didn’t want to delete. I had to open up some Virtualbox configuration file to change the name of the VDI file it wanted to point to for that machine to match up with one that it used to be associated with, and then delete it. Or something like that. It’s been a while since I did this, but the only other alternative was to leave this broken VM in the Virtualbox inventory and rename it to something like «Broken VM, don’t use». But I managed to get rid of it eventually.


Bookmarks

Bookmarks


Posting Permissions

Earlier we published a guide about VirtualBox P2V in Windows 10/11 by VMware converter. In this guide, we will learn more about how to do a VirtualBox P2V with a Microsoft utility called disk2vhd. disk2vhd is an excellent virtual hard disk tool to clone the physical disk partitions of a computer (Physical or virtual). It can output the virtual hard disk in VHD format. This VHD file can be converted to other several virtual disk formats or attached to virtualization software like Hyper-V and VirtualBox.

Even though I successfully converted a physical machine to a virtual one by using the disk2vhd tool, it gave me a few errors when I tried to boot the virtual machine from Oracle VirtualBox. Later, found a few solutions to make it work.

Let us discuss the possible errors and how to solve them with Microsofts’s disk2vhd. disk2vhd tool does work on Microsoft Windows Operating Systems only. Also, the tool should be installed locally on the computer to convert it. We can’t use it remotely to convert a network-connected computer/server.

Disk2vhd Errors image

Migrating a working physical Windows computer to the VirtualBox platform is very easy in this way. Once it has been converted to VHD format, we can use it with VirtualBox which can run on any OS like Linux or macOS. Since VirtualBox supports VHD file format natively, we do not need to convert the VHD to VDI in this case.

In this example, I converted my physical computer that is having two Operating Systems (Windows 7 and Windows XP). I will be converting and moving only Windows 7 to VirtualBox by P2V here.

1) Download the latest version of disk2vhd (2.02 version)

2) Installation is not required, execute the program directly.

3) It will pick up the physical disk partitions from the host OS.

VirtualBox P2V with Disk2vhd

Important Note:

Before going to the next step, let’s understand something clearly!

  • If you want to convert your entire physical disk (for example 500GB with 5 partitions) to VHD, then select all partitions and start the conversion. This will not cause any issues while attaching the VHD to VirtualBox or Hyper-V.
  • If you want to P2V only specific Operating Systems and partitions from a physical computer, then you must do it properly to avoid problems.

In this example, I planned to convert my working Windows 7 to VirtualBox. So, I must convert the System and boot partitions which are usually different in most cases.

Here is my working Windows 7 physical computer.

Working physical computer

Initially, I converted only Windows 7 boot partition (normally the C drive) to save space and time. I know this is not the system partition with the boot recorder, but I thought I can repair it and make it work if it fails to boot later.

No matter how many partitions you select and convert, VirtualBox will detect the VHD as the size of a full physical disk with all partitions. When the boot loader/recorder is not found on any of the partitions, OS will not boot.

So, my first method returned the following error

A disk read error occurred
Press Ctrl+Alt+Del to restart

It’s because of the missing system partition. I tried several methods to write the MBR and do the repair with the Windows installation medium, but all failed for me. Hence, I need to rerun the disk2vhd P2V conversion.

4) So before starting the conversion, go to disk management and check the partition structure.

Partition Manager

Always you must convert the system and boot partitions by disk2vhd to be able to use with Virtualbox or any other platform.

In my above example, the System partition is E and the Boot partition is C. So, I have to select both partitions to convert.

5) Now press Create button and start the process. Make sure that each partition is having enough disk space to create snapshots on the physical computer. It’s highly recommended to do nothing while conversion is happening on the computer.

6) After completed successfully, create a new virtual machine with the correct OS type and attach the converted VHD file.

Once you power on the VM, it should boot and work fine if the partition structure is converted properly.

Here is another problem I encountered. The converted Windows 7 machine kept on restarting in VirtualBox. Do you know why? My physical hard disk is connected via the SATA port on the host computer. So I attached the VHD file to the SATA port on VirtualBox too, but that was wrong.

It started working after I removed the disk and re-attached it to the IDE port of the virtual machine.

Update: This demonstration was done many years ago with the older VirtualBox and Windows OS versions. By the time you read this guide, VirtualBox and Windows OS would have improved the features and auto fix the errors we faced so far.

Try the Following Steps to Solve disk2vhd Errors with VirtualBox

In summary, here are some of the solutions you can try if the virtual machine is not booting after doing P2V with disk2vhd.

  1. Make sure that you are converting system and boot partitions
  2. Remove and attach the converted VHD disk to IDE (if not, SATA) port of the virtual machine
  3. Change the storage type in virtual machine settings
  4. Enable or disable IO APIC and PAE/NX
  5. Insert the Windows installation medium and repair the boot loader and any start-up issues.

Changing disk to IDE from SATA did the trick and I managed to boot on VirtualBox. Here is the successful P2V with disk2vhd.

Converted VM by disk2vhd on VirtualBox

After the migration, install the latest guest additions to get more features and performance boost.

This will be an ideal way to move your working physical computer to VirtualBox or Hyper-V on a different host computer to get maximum portability.

Even though we demonstrated these steps in older versions of products, still, it will work on Windows 10, Windows 11 and the latest versions of Oracle VirtualBox.

Author Sunil katke

Team,

Due to this VM production is down is somebody help me soon.

Waiting for your reply


Was this post helpful?
thumb_up
thumb_down

Author Matt Bergeron

Are the 2 volumes (the one you moved from, and the one you moved to) do they use the same drive controller? SCSI? IDE? If not, make sure the VM has the right driver for the controller installed. 

Have you tried moving the VM storage back to it’s original state?

First rule of troubleshooting, if you get in a pinch with a production system, revert back to the last known working configuration. 


Was this post helpful?
thumb_up
thumb_down

Try booting the VM from installation media and running a repair. http://forums.petri.com/showthread.php?t=22388 Opens a new window


Was this post helpful?
thumb_up
thumb_down

Sunnykatke wrote:

Team,

Due to this VM production is down is somebody help me soon.

Waiting for your reply

You do know that we are volunteers here and do this for fun? If you need immediate support then get a support contract with Microsoft or similar.


Was this post helpful?
thumb_up
thumb_down

Is any of your storage out of disk space?


Was this post helpful?
thumb_up
thumb_down

Author Sunil katke

We have 8 node Cluster in that this VM is Hosted , 

we are using SCSI Controller i have not tried moving back to its Original state. let me try to revert it back.

If u find any other solution pls try to post it here.


Was this post helpful?
thumb_up
thumb_down

Gary D Williams wrote:

Sunnykatke wrote:

Team,

Due to this VM production is down is somebody help me soon.

Waiting for your reply

You do know that we are volunteers here and do this for fun? If you need immediate support then get a support contract with Microsoft or similar.

This.

Also, have a read of Asking Better Questions.

A brief description of the steps you’ve already tried would help. I would hope you’ve already googled the error message and tried the returned results, but you never mention it and so I assume you haven’t. We’re happy to help with tricky problems, but sticking someone else’s error messages into Google gets tiring.


Was this post helpful?
thumb_up
thumb_down

Author Sunil katke

Hi Team,

There was a space issue on Volume 8 so that i have migrated the storage from Volume 8 to Volume 4. back end we are working to reboot the cluster’s.

Due I can’t try multiple things becoz its a production server managing from USA. 

i will try few things which you people suggested like roll back to same storage, Uploading the OS & try to repair it. 

Thank you chamele0n and Joewilliams. I will get back to you after sometime.

Note : I’m a employee of Microsoft.


Was this post helpful?
thumb_up
thumb_down

Sunnykatke wrote:

Note : I’m a employee of Microsoft.

I really don’t wish to sound rude, but surely if you are an employee of Microsoft with a high priority production-down issue with your Microsoft server, you would turn to your highly qualified internal support team rather than a bunch of strangers on the Internet who have to second guess what you’re trying to do and what the problem might be?

What is your position at Microsoft?


Was this post helpful?
thumb_up
thumb_down

Author Sunil katke

I will let you know the exact issue, m working with my seniors on that, once its resolve i will post it. 


Was this post helpful?
thumb_up
thumb_down

JoeWilliams wrote:

Sunnykatke wrote:

Note : I’m a employee of Microsoft.

I really don’t wish to sound rude, but surely if you are an employee of Microsoft with a high priority production-down issue with your Microsoft server, you would turn to your highly qualified internal support team rather than a bunch of strangers on the Internet who have to second guess what you’re trying to do and what the problem might be?

What is your position at Microsoft?

+1. Microsoft have an internal IT team who help with issues like this, plus you have a direct line to the people who wrote the software.

Sunnykatke’s profile says «Home User at Microsoft» which suggests that he is NOT an employee of Microsofts.


Was this post helpful?
thumb_up
thumb_down

Sunnykatke wrote:

I will let you know the exact issue, m working with my seniors on that, once its resolve i will post it. 

Sunnykatke wrote:

There was a space issue on Volume 8 so that i have migrated the storage from Volume 8 to Volume 4. back end we are working to reboot the cluster’s.

Sounds like a space issue to me, exactly what I said a few posts ago.


Was this post helpful?
thumb_up
thumb_down

Gary D Williams wrote:

Sunnykatke wrote:

I will let you know the exact issue, m working with my seniors on that, once its resolve i will post it. 

Sunnykatke wrote:

There was a space issue on Volume 8 so that i have migrated the storage from Volume 8 to Volume 4. back end we are working to reboot the cluster’s.

Sounds like a space issue to me, exactly what I said a few posts ago.

think that volume 8 had the space issue, so he migrated it to volume 4, at which point he got this error. He’ll probably pop back later on and throw out another nugget of information whilst failing to clarify this point.


Was this post helpful?
thumb_up
thumb_down

Sunnykatke wrote:

Hi Team,

There was a space issue on Volume 8 so that i have migrated the storage from Volume 8 to Volume 4. back end we are working to reboot the cluster’s.

Due I can’t try multiple things becoz its a production server managing from USA. 

i will try few things which you people suggested like roll back to same storage, Uploading the OS & try to repair it. 

Thank you chamele0n and Joewilliams. I will get back to you after sometime.

Note : I’m a employee of Microsoft.

I would think Microsoft employees would have better access to support. 


Was this post helpful?
thumb_up
thumb_down

Image: post content

Hmm.

Maybe Microsoft do have a small Service Provider arm in India to which they provide sub-standard support.


Was this post helpful?
thumb_up
thumb_down

Author Sunil katke

HI Team,

Bad luck………….

First thing there was a space issue, so we have migrated to Volume 4. it was not much critical space issue we have 92 GB free space was there….. Capacity of the Volume 8 was 2 TB. After migrating frm 8 to 4 as i said i got error A disk read error occurred press ctrl+alt+del to restart -Virtual Machine 2012R2.

1.Uploaded the OS and tried to repair but it didn’t resolve the issue.

2.Migrated to same volume 8 and restarted the VM but same error.

3.Took export copy of the VM, copied to different cluster and Imported the VHD file but same issue.

4.We hosted a new VM and tried to copy the data from corrupted VHD, attached the VHD to newly hosted VM.

We tried all possibilities to recover the data inside the VHD

but could not recover the data as the VHD is corrupted.

The boot sectors, File Systems along with MBR got corrupted due

to which we are unable to load OS and mount the VHD as well.

If you find any solution pls let me know.

you people r giving more attention on my profile can’t they concentrate there work and give a good support to spiceworks. discussing about others wht they do wht they did in there life its waste of time.

IF I SAY ANY THING WRONG sorry for that…………..

Thank you


Was this post helpful?
thumb_up
thumb_down

Sunnykatke wrote:

We tried all possibilities to recover the data inside the VHD

but could not recover the data as the VHD is corrupted.

Ok, what does Microsoft have to say about it? Don’t they have any internal tools for rebuilding VHD’s?

Can you not restore from backup?

What storage arrays are you using?


Was this post helpful?
thumb_up
thumb_down

If the VHD is corrupted and this is impacting production systems, restore it from backup.


Was this post helpful?
thumb_up
thumb_down

Author Sunil katke

There is no backup for this server. we can’t restore the data from storage as per our policy its not recommended . 

we tried to attache the VHD file to new VM its fails. 

Now its not impacting becoz we have provided new VM for them.

if u have any better solution how to use corrupted VHD and take the backup let me know.


Was this post helpful?
thumb_up
thumb_down

Sunnykatke wrote:

There is no backup for this server. we can’t restore the data from storage as per our policy its not recommended . 

Microsoft have a policy that says to NOT back up Virtual machines?

Sunnykatke wrote:

if u have any better solution how to use corrupted VHD and take the backup let me know.

You allegedly work for Microsoft. If true and they cannot help you, especially as they are the very people who defined the layout of the VHD and VHDX files and as you have a policy of not backing up then I’d say that you are SOL.


Was this post helpful?
thumb_up
thumb_down

Author Nick Kopka

NiKopka


This person is a Verified Professional

This person is a verified professional.

Verify your account
to enable IT peers to see that you are a professional.

ghost chili

Does Microsoft know you supposedly work for them?  Cuz I’m with the Internet Police Squad and will have you arrested for impersonating an M$ employee!


Was this post helpful?
thumb_up
thumb_down

Author Sunil katke

some policies will apply some policies will not. every company and sub companies will have there own policies, that one i don’t wanna discuss it here.

Microsoft never says not to backup. if u need to keep backup u have to pay it for it. its PAID service not free services.

For backup will user DPM tool.

Thanks for your help u can close this discussion thread.

VHD corrupted can’t do anything now.

Nikopka : If u r with internet police squad what should i do with that tell me. i don’t have a problem if u r with them or with ur ministers. I m here for technical discussion not for private discussion.

Thank you.


Was this post helpful?
thumb_up
thumb_down

I’ve got it!

He does work for Microsoft — he’s with that specialist team that call you up when your Windows computer has a virus and helpfully get rid of it for you.

Microsoft never says not to backup. if u need to keep backup u have to pay it for it. its PAID service not free services.

Maybe you should have paid for it then?


Was this post helpful?
thumb_up
thumb_down

Sunnykatke wrote:

Microsoft never says not to backup. if u need to keep backup u have to pay it for it. its PAID service not free services. 

For backup will user DPM tool.

I think that Microsoft can afford to use their own software, it’s not like they have to pay for licensing.


Was this post helpful?
thumb_up
thumb_down

Author Sunil katke

Yes we are using our own software’s for backup. but its depend upon customer, Customer need a backup or not.

If windows crashes due to application or for some other reasons customer will approach us to provide a new VM becoz it crashes due to application’s.

Gray D Williams & Joe Williams Thanks for your kind support.


Was this post helpful?
thumb_up
thumb_down

Понравилась статья? Поделить с друзьями:
  • Virtualbox boot error
  • Virtualbox bios error
  • Virtualbox amd v error
  • Virtualbox 80004005 ошибка
  • Virtualalloc remapping failed тарков ошибка