Last active
December 17, 2020 03:21
-
-
Save mohamad-supangat/0cccf8a90c480b2d7d06936ae87e0063 to your computer and use it in GitHub Desktop.
Menjalankan physical hardisk di virtualbox
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Fixing disk readonly | |
In summary: | |
To gain full hard drive access in a VBox guest on Win7 host | |
0. close all open programs or documents on any partition on the disk to pass-through | |
1. run DISKPART (command line utility)* | |
2. select hard drive carefully using SELECT DISK. disk numbering starts at zero. you can roughly verify your selection with LIST PARTITION if you know what your partitions should look like or LIST DISK to see disk sizes. | |
3. offline the disk using OFFLINE DISK. all volumes will disappear from windows explorer. | |
4. ATTRIBUTES DISK CLEAR READONLY | |
5. verify with ATTRIBUTES DISK | |
6. create VMDK file as shown in several howtos on the web | |
7. enjoy | |
1. Create vmdk drives that read from real drives | |
To create an image that represents an entire physical hard disk (which will not contain any actual data, as this will all be stored on the physical disk), on a Linux host, use the command | |
VBoxManage internalcommands createrawvmdk \ | |
-filename /path/to/file.vmdk \ | |
-rawdisk /dev/sda | |
You must have read access to the physical disk device file /dev/sda. To accomplish this you can either change the owner and access rights of the device file or run VBoxManage internalcommands createrawvmdk… as root (put sudo before the command). | |
On a Windows host, instead of the above device specification, use e.g. \\.\PhysicalDrive0. On a Mac OS X host, use e.g. /dev/disk1 (and unmount all partitions on disk1). | |
(all on one line) | |
C:\VirtualBoxDrives>"C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" | |
internalcommands createrawvmdk | |
-filename C:\VirtualBoxDrives\raw-0.vmdk | |
-rawdisk \\.\PHYSICALDRIVE0 | |
(output) | |
RAW host disk access VMDK file C:\VirtualBoxDrives\raw-0.vmdk created successf.. | |
2. Assign the vmdk drives to a VM | |
VM -> Settings -> Storage -> add ide / sata -> Choose existing disk -> browse | |
assign | |
3. Set one of the Writethrough modes. | |
File -> Virtual Media Manager -> e.g raw-0.vmdk -> [modify] -> (o) Writethrough | |
repeat for all drives | |
set writethrough | |
3. Reorder boot-priority (semi optional) | |
VM -> Settings -> System -> Boot order | |
[./] Hard Disk | |
[./] CD/DVD | |
[ ] Floppy | |
[ ] Network | |
VM -> Settings -> Storage -> Controller: SATA -> e.g. raw-5.vmdk -> Hard Disk: Sata Port 0 | |
Relevant chapters (manual) | |
Chapter 9. Advanced topics | |
9.9. Advanced storage configuration | |
9.9.1. Using a raw host hard disk from a guest | |
9.9.1.1. Access to entire physical hard disk | |
Chapter 5. Virtual storage | |
5.2. Disk image files (VDI, VMDK, VHD, HDD) | |
5.3. The Virtual Media Manager | |
5.4. Special image write modes | |
Enumerating physical drives in Windows: | |
C:\Users\win7>wmic diskdrive list brief | |
Caption DeviceID Model Partitions Size | |
Samsung SSD 840 EVO 250GB ATA Device \\.\PHYSICALDRIVE3 Samsung SSD 840 EVO 250GB ATA Device 6 250057228288 | |
ST1000DM003-1CH162 ATA Device \\.\PHYSICALDRIVE1 ST1000DM003-1CH162 ATA Device 5 1000202273280 | |
ST1000DM003-1CH162 ATA Device \\.\PHYSICALDRIVE2 ST1000DM003-1CH162 ATA Device 5 1000202273280 | |
ST1000DM003-1CH162 ATA Device \\.\PHYSICALDRIVE0 ST1000DM003-1CH162 ATA Device 5 1000202273280 | |
WDC WD1000DHTZ-04N21V0 ATA Device \\.\PHYSICALDRIVE5 WDC WD1000DHTZ-04N21V0 ATA Device 6 1000202273280 | |
WDC WD1000DHTZ-04N21V0 ATA Device \\.\PHYSICALDRIVE4 WDC WD1000DHTZ-04N21V0 ATA Device 5 1000202273280 | |
ST1000DM 003-1CH162 SCSI Disk Device \\.\PHYSICALDRIVE6 ST1000DM 003-1CH162 SCSI Disk Device 5 1000202273280 | |
You can also get the drive numbers with PowerShell: | |
PS C:\ Get-Disk |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment