Retrieving Data from VHD File (Virtual Machine Harddrive)


 
Thread Tools Search this Thread
Operating Systems Linux Retrieving Data from VHD File (Virtual Machine Harddrive)
# 1  
Old 01-19-2012
Retrieving Data from VHD File (Virtual Machine Harddrive)

Hello,

I had Gentoo installed on a Microsoft Windows Hyper-V virtual machine. The system shutdown properly but the RAID array on the drive it was on failed. We had a backup that was poorly configured and as such we didn't back up all of the data we needed.

Therefore, after getting the RAID array back to a degraded state I was able to get the VHD files (virtual machine harddrives) off of the RAID array but the tools I would use to mount them do not work as they say the file could be corrupted. I cannot use the Windows-based utilities as they only recognize NTFS formatted partitions and as such I cannot recover any files with those tools.

Does anyone know or have experience with recovering or accessing VHD files in Linux?

The ideal scenario would be if I can somehow mount these drives in a Gentoo or other Linux-based OS which I could then try and recover files with. Even if the files don't mount is there a tool that can scan drives mounted in Linux for recoverable files?

Thank you for your time.
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Providing virtual machine priority in kvm based virtual machines

Hi All, Is there any way I can prioritize my VMs when there is resource crunch in host machine so that some VMs will be allocated more vcpu, more memory than other VMs in kvm/qemu hypervisor based virtual machines? Lets say in my cloud environment my Ubuntu 16 compute hosts are running some... (0 Replies)
Discussion started by: SanjayK
0 Replies

2. AIX

IBM Virtual Machine OS on intel x86 and x64? IBM AIX OS on IBM Virtual Machine?

Hi There, I have zero information and zero knowledge for IBM virtual machine except Amazon cloud and VMware ESXi (Only Linux OS available). Anyone could provide me the following answer - Can IBM VM been deploy on X86 and X64 (Intel Chip)? If answer is yes any chance to deploy AIX OS... (13 Replies)
Discussion started by: chenyung
13 Replies

3. Shell Programming and Scripting

Retrieving sequence data from other file

Hello experts :cool:, I am new to programming and will need your help.. I have 2 very large files with the following format: FILE1: >MLP1019 PL4 >MLP7456 PL3 >MLP9268 PL9 >MLP6245 PL1 FILE2: >MLP1019 STNAPLQTSNTWVSYQPSMMMSLQ >MLP7456 PPYWYWNSAVMIFYVQPLSLLAVLLA >MLP9268... (2 Replies)
Discussion started by: narachaid
2 Replies

4. Red Hat

My RHEL virtual Machine Does not have Virtual Machine Manager Desktop Tool

My RHEL virtual Machine Does not have Virtual Machine Manager Desktop Tool Hi, I don't seem to have the Virtual Machine Manager Desktop tool set up on my RHEL6 Machine. The Linux machine runs off VMWare player and I'm not sure whether it is a VMWare software issue or a problem with the RHEL6... (2 Replies)
Discussion started by: accipiter1
2 Replies

5. Solaris

Change hostID of Solaris 10 virtual/guest machine installed by Virtual Box 4.1.12 on Windows-XP host

Trying to set or modify the randomly set hostID of a Solaris 10 virtual/guest machine that I installed on a Windows-XP host machine (using Virtual Box 4.1.12). I was able to set/modify the hostname of the Solaris 10 virtual/guest machine during installation as well as via the Virtual Box... (4 Replies)
Discussion started by: Matt_VB
4 Replies

6. Red Hat

deleted a virtual machine with critical data under CentOS

Hi all, I'm in a pretty messed-up situation, hope you can give me a hand. I deleted by accident a folder containing a VMware server virtual machine, that contains most critical information. The host OS is CentOS 5.5, which I believe by default uses Ext3. I shut down the PC intermediately... (2 Replies)
Discussion started by: starriol
2 Replies

7. UNIX and Linux Applications

Retrieving data from a database and store to a file

Hi I'm using and Oracle 10g Database. I want to write a script to retrieve data from the database and store it toa file. I'm using simple sql statements such as Select * from celltable I don't know how to specify the database name etc. I have this but it doesn't work ... (1 Reply)
Discussion started by: ladyAnne
1 Replies

8. Solaris

Is there any Virtual data center as we have Virtual Machine?

Do we have any Virtual Data Center software as we have Virtual Machine? I want to practice everything of Solaris practically but i don't have resources like data center which includes Servers, Data storages, switches, and other things. (2 Replies)
Discussion started by: karman0931
2 Replies

9. Shell Programming and Scripting

Using loop reading a file,retrieving data from data base.

Hi All, I am having trouble through, I am reading the input from tab delimited file containing several records, e.g. line1 field1 field2 field3 so on.. line2 field1 field2 field3 so on.. .. .. on the basis of certain fields for each record in input file, I have to retrieve... (1 Reply)
Discussion started by: Sonu4lov
1 Replies
Login or Register to Ask a Question
sautil(1M)																sautil(1M)

NAME
sautil - support utility for the HP SmartArray RAID controller family SYNOPSIS
device_file [-N] device_file [-s] device_file fw_image device_file fw_image physical_drive_id device_file fw_image encl_physical_drive_id device_file device_file device_file device_file logical_drive_number device_file rate device_file device_file device_file device_file [-raw] device_file device_file physical_drive_id [-raw] device_file device_file device_file DESCRIPTION
The command is a support tool for the HP SmartArray RAID Controller Family. This command allows the system administrator to perform tasks such as: 1) Retrieving RAID configuration and status information for the controller, logical drive, physical disk, cache, etc.; 2) Retrieving RAID driver information (driver state, trace log, statistics, etc.); 3) Downloading new revisions of controller or disk firmware; 4) Sending instructions to the firmware (reset controller, scan SCSI bus, etc.); and 5) Recreating the controller device file(s). Prerequisites Some of the options are intended for use by HP support personnel and require detailed knowledge of the RAID SA driver or firmware to inter- pret the output. Security Restrictions requires either the superuser privilege or and privileges. See privileges(5) for more information about privileged access on systems that support fine-grained privileges. Options recognizes the following options and parameters as indicated in the section above. Keyword options are order-dependent, but are not case- sensitive. device_file Most options require a device file parameter, e.g., The device file for a specific RAID SA controller can be determined from the output. When the device file parameter is specified without any options, will display information such as the RAID SA driver state, controller hardware path, firmware revision, capacity expansion and rebuild priority settings, cache status and settings, logical drive configuration and physical drive properties. When the optional argument is specified, persistent device files (see intro(7)) are displayed for logical drives. When the optional argument is specified, a subset of the information is displayed. This option downloads the specified firmware image file (fw_image) to the controller. The image file name is case-sensitive. The firmware download process usually completes within one minute, but could theoretically take up to eight minutes. All I/O to the controller are temporarily halted dur- ing this time. This option downloads the specified firmware image file (fw_image) to physical disk specified by the (physical_drive_id). The image file name is case-sensitive. physical_drive_id To specify the SCSI physical disk. It can be represented as such as: 4:12. Valid channel numbers are between 1 and 4. Valid target numbers are between 0 and 15. To specify the SAS/SATA physical disk. It can be represented as either such as: 2I:1:10 or (wwid), such as: 0x500000e010f16432. This option downloads the specified firmware image file (fw_image) to the storage enclosure processor. This option is supported on SAS Smart Array HBAs only. The image file name is case-sensitive. The firmware download process takes ten to fifteen minutes. All I/O to the controller are temporarily halted during this time. encl_physical_drive_id To specify the storage enclosure processor. It can be represented as either such as: 1E:1:0 or (wwid), such as: 0x500000e010f16432. This option resets the controller. Some situations that may require a controller reset are: 1) OLR was performed and the logical drives on the replacement controller are not detected; 2) a disk enclosure with an existing RAID configuration was hot-added and the logical drives on that enclosure are not detected. This option tells the controller to rescan all SCSI buses. A situation that may require a scan is when a physical disk is hot-inserted into the system's internal drive bay. This option tells the controller to start rebuilding any logical drives that are in state. All logical drives in this state will eventually transition to Heavy I/O to the controller may delay this transition. There is no adverse impact if this option is invoked when no logical drives are in state. This option grants permission to the controller to set the state of the specified failed logical drive (logical_drive_number) to "OK" and to set the states of all failed physical disks that have been replaced via hot-plug exchanges to "OK". WARNING: While this option preserves the RAID configuration (logical drive configurations, controller settings, etc.), data on the failed logical drive may have already been compromised. If more disks have failed than the RAID level can accommo- date, you will need to restore your data from backup media. This option tells the controller to set the SCSI transfer rate to a lower speed than it would normally allow. Valid arguments for the rate field are (and ultra-160 for controllers that support Ultra-320). This option displays statistics counters maintained by the RAID SA "ciss" driver. This option clears the statistics counters maintained by the RAID SA "ciss" driver. This option displays the trace buffer of the RAID SA "ciss" driver. This option displays the firmware error log of the RAID SA controller. When the optional argument is specified, the raw data (in bytes) are displayed. This option clears the firmware error log of the RAID160 SA controller. It is not available for SmartArray 640x controllers. This option displays the error log for the physical disk specified by the (physical_drive_id). When the optional argument is specified, the raw data (in bytes) are displayed. This option displays the RAID SA controller's PCI configuration header. This option allows interactive reading of the RAID SA controller's registers. WARNING: Reading an invalid register may cause a system crash. This option is only available for SAS/SATA. Vital Product Data contains Product Description, Part Number, Engineering Date Code, Serial Number, Miscellaneous Informa- tion, Manufacturing Date Code, EFI Version, Asset Tag, HBA Firmware Version, and WWN. This option runs the RAID SA startup script to recreate the device files (/dev/cissX). Logical Drive State Definitions All physical disks in the logical drive are operational. Some possible causes: 1) Multiple physical disks in a fault-tolerant (RAID 1, 1+0, 5, ADG) logical drive have failed. 2) One or more disks in a RAID 0 logical drive have failed. 3) Cache data loss has occurred. 4) Array expansion was aborted. 5) The logical drive is temporarily disabled because another logical drive on the controller had a missing disk at power-up. Also known as "degraded" state. A physical disk in a fault tolerant logical drive has failed. For RAID 1, 1+0 or 5, data loss may result if a second disk should fail. For RAID ADG, data loss may result if two additional disks should fail. A replacement disk is present, but rebuild hasn't started yet (another logical drive may be currently rebuilding). The logical drive will also return to this state if the rebuild had been aborted due to unrecoverable read errors from another disk. One or more physical disks in this logical drive are being rebuilt. While the logical drive was in a degraded state, the system was powered off and a disk other than the failed disk was replaced. Shut off the system and replace the correct (failed) disk. While the system was off, one or more disks were removed. Note: the other logical drives are held in a temporary "failed" state when this occurs. The data in the logical drive is being reorganized because: 1) Physical disks have been added to the array (capacity expansion). 2) The stripe size is being changed (stripe-size migration). 3) The RAID level is being changed (RAID-level migration). A capacity expansion operation is in progress (or is queued up) that will make room on the disks for this new logical drive. Until room has been made on the physical disks, this newly configured logical drive cannot be read or written. The logical drive is waiting to undergo data reorganization (see above). Possible causes for the delay are a rebuild or expansion operation may already be in progress. Physical Disk State Definitions The physical disk is configured in one or more logical drives and is operational. The physical disk is configured as a spare disk. The physical disk has not been configured in any logical drives. The configured physical disk has failed. RETURN VALUE
returns the following values: Successful completion. Command line syntax error. Incompatible CISS driver API. Failure opening a file. Other error. EXAMPLES
Display RAID subsystem information for the controller Update the firmware on the controller using the firmware image file Update the firmware on the physical disk (SCSI ID "13") connected to channel "2" of controller using the firmware image file located in the current directory: Recreate the device files for all RAID SA controllers in the system: AUTHOR
was developed by HP. FILES
Executable file. Device files. SEE ALSO
saconfig(1M), privileges(5), intro(7). sautil(1M)