Search This Blog
Showing posts with label partition. Show all posts
Showing posts with label partition. Show all posts
Thursday, December 29, 2011
How to resize (increase) main NTFS system partition of your Windows base virtual mashine in VMware Workstation
Problem summary
When we create a VM we specify the various hardware component we want to virtualize. One of them is the HDD. After some time you may find out that the hard drive your VM has is too small.
The VMware Workstation allows you to resize the disk (as long there are not snapshots).
Impact
You can't install any additional software because there is not enough free space.
Problem
Although there are many tools you can use to resize the NTFS file system many of them have some limitation (demo version doesn't write data to the disk) or require a comercial license to bought or can be use on the main partition (diskpart.exe) [2]
Solution
The task can be done with the help of [1]. We don't need license. It can resize the main NTFS partition.
Free EaseUS® Partition Master 9.1 Home Edition
References
[1]
Free EaseUS® Partition Master 9.1 Home Edition
http://www.partition-tool.com/personal.htm
[2]
How to extend a data volume in Windows Server 2003, in Windows XP, in Windows 2000, and in Windows Server 2008
http://support.microsoft.com/kb/325590
Labels:
ntfs,
partition,
virtualisation,
vmware
Sunday, May 1, 2011
Gdisk error message: Caution: invalid main GPT header, but valid backup; regenerating main header from backup!
At some point when experimenting with partitions on your disk you may get the following error message.
As always you have to be very careful depending what you did and what do you want to do as next.
The three options for gdisk gives you the choice what partition tables you will examine. Fortunately for us gpart is not going to write on disk anything until we say so by executing the w (write) command (example bellow). The three options only influences how the data on the disk are going to be interpreted and presented for our review.
At this stage it is save to experiment and have a look how the partition tables look like. Depending on your choise different partitions may be printed ('p') .
REMEMBER to always quit the session with the 'q' (quit) and never with 'w' otherwise your experiments will be permanently saved on the disk.
In my case this error was misleading and confusing only. I could verify that my current partition schema was not GPT at all but the good old MSDOS one [1]. At this stage I knew that 'gdisk' is not the tool I wanted to use and I finished creating new partitions with 'parted'. I didn't have to use gdisk at all.
The reason why I had some parts of GPT data on my disk is unknown. I can only suspect that it was created when I played with the Windows tool 'EasyBCD'.
I could try to delete the GPT data but base on [2] never had to do it.
References
[1] How to find what type of disk partition schema do I use (msdos, gpt)
[2] Wiping Out Old GPT Data
% gdisk /dev/sda GPT fdisk (gdisk) version 0.7.1 Caution: invalid main GPT header, but valid backup; regenerating main header from backup! Caution! After loading partitions, the CRC doesn't check out! Warning! Main partition table CRC mismatch! Loaded backup partition table instead of main partition table! Warning! One or more CRCs don't match. You should repair the disk! Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: damaged Found valid MBR and corrupt GPT. Which do you want to use? (Using the GPT MAY permit recovery of GPT data.) 1 - MBR 2 - GPT 3 - Create blank GPT
As always you have to be very careful depending what you did and what do you want to do as next.
The three options for gdisk gives you the choice what partition tables you will examine. Fortunately for us gpart is not going to write on disk anything until we say so by executing the w (write) command (example bellow). The three options only influences how the data on the disk are going to be interpreted and presented for our review.
# gdisk /dev/sda Command (? for help): h b back up GPT data to a file c change a partition's name d delete a partition i show detailed information on a partition l list known partition types n add a new partition o create a new empty GUID partition table (GPT) p print the partition table q quit without saving changes r recovery and transformation options (experts only) s sort partitions t change a partition's type code v verify disk w write table to disk and exit x extra functionality (experts only) ? print this menu
At this stage it is save to experiment and have a look how the partition tables look like. Depending on your choise different partitions may be printed ('p') .
REMEMBER to always quit the session with the 'q' (quit) and never with 'w' otherwise your experiments will be permanently saved on the disk.
In my case this error was misleading and confusing only. I could verify that my current partition schema was not GPT at all but the good old MSDOS one [1]. At this stage I knew that 'gdisk' is not the tool I wanted to use and I finished creating new partitions with 'parted'. I didn't have to use gdisk at all.
The reason why I had some parts of GPT data on my disk is unknown. I can only suspect that it was created when I played with the Windows tool 'EasyBCD'.
I could try to delete the GPT data but base on [2] never had to do it.
References
[1] How to find what type of disk partition schema do I use (msdos, gpt)
[2] Wiping Out Old GPT Data
Labels:
gdisk,
gpt,
instalation,
parted,
partition,
sysadmin,
troubleshooting,
ubuntu
How to find what type of disk partition schema do I use (msdos, gpt)
There are many disk partition schemes that can be used. Very likely on most x86 base computer the choice is often limited by the operating system we use although.
The list of supported labels (partition schemes) in GNU parted tool can be found here [1]:
To find out what type of partition schema we currently have on your system please run the bellow command and check the value for the 'Partition Table'.
References:
[1]
(parted) mklabel msdos
Others:
Parted User's Manual
GUID Partition Table
Make the most of large drives with GPT and Linux
Fun with GPT partitioning
Linux Creating a Partition Size Larger than 2TB
The list of supported labels (partition schemes) in GNU parted tool can be found here [1]:
label-type must be one of these supported disk labels:
* bsd
* loop (raw disk access)
* gpt
* mac
* msdos
* pc98
* sun
To find out what type of partition schema we currently have on your system please run the bellow command and check the value for the 'Partition Table'.
% parted /dev/sda unit mb print Model: ATA ST2000DL003-9VT1 (scsi) Disk /dev/sda: 2000399MB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 0.03MB 104856MB 104856MB primary ntfs boot 2 104857MB 209714MB 104858MB primary ntfs 3 209714MB 312115MB 102401MB primary root@sysresccd /tmp % parted /dev/sda unit s print Model: ATA ST2000DL003-9VT1 (scsi) Disk /dev/sda: 3907029168s Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 63s 204796619s 204796557s primary ntfs boot 2 204797952s 409597951s 204800000s primary ntfs 3 409597952s 609599487s 200001536s primary
References:
[1]
(parted) mklabel msdos
Others:
Parted User's Manual
GUID Partition Table
Make the most of large drives with GPT and Linux
Fun with GPT partitioning
Linux Creating a Partition Size Larger than 2TB
How to export/backup partition schema for a disk using old style disk partitions format like 'msdos' written into MBR sector
To backup the partition schema of the disk you can execute:
To restore the part.txt you can use:
man sfdisk
Wiping Out Old GPT Data
# sfdisk -d /dev/sda > part.txt # example output can look like # cat part.txt # partition table of /dev/sda unit: sectors /dev/sda1 : start= 63, size=204796557, Id= 7, bootable /dev/sda2 : start=204797952, size=204800000, Id= 7 /dev/sda3 : start=409597952, size=200001536, Id=83 /dev/sda4 : start= 0, size= 0, Id= 0
To restore the part.txt you can use:
# sfdisk /dev/hda < part.txt
References:
man sfdisk
Wiping Out Old GPT Data
Sunday, April 24, 2011
How to clone a partition to a remote NFS server
Problem description.
You formatted and re-partitioned your hard drive.
You have a partition of the size about 100GB that you dedicated to your OS.
The installation of your OS went fine as well as the installation of all your necessary drivers.
After all you would like to have a copy of your partition data that can quickly restore in a case something wrong happens.
Solution:
Download the SystemRescueCd ISO img file [1]
Create bootable USB thumb drive [2]
Boot the system using your USB thumb drive. Once it is fully loaded you will get bash command line access.
Mount your remote NFS site image repository:
Copy and compress the partition while coping it out for backup purposes [3]. Copy the partition schema as well.
At the end unmount the NFS partition and we are ready to reboot the system.
Later on, as a security precaution create md5sums and some level of par2 recovery files if the image should have ever get corrupted.
References:
[1] SystemRescueCd
[2] Sysresccd-manual-en How to install SystemRescueCd on an USB-stick
[3] partclone.dd
man 5 nfs
par2 home page
man par2
You formatted and re-partitioned your hard drive.
You have a partition of the size about 100GB that you dedicated to your OS.
The installation of your OS went fine as well as the installation of all your necessary drivers.
After all you would like to have a copy of your partition data that can quickly restore in a case something wrong happens.
Solution:
Download the SystemRescueCd ISO img file [1]
Create bootable USB thumb drive [2]
Boot the system using your USB thumb drive. Once it is fully loaded you will get bash command line access.
Mount your remote NFS site image repository:
# mkdir /tmp/nfs # mount -t nfs -o nolock 192.168.0.X:/your/path /tmp/nfs
Copy and compress the partition while coping it out for backup purposes [3]. Copy the partition schema as well.
# For test purposes you can shortly run the partclone.dd with '-d' option # it will create a log file in /var/log directory. # But don't run it like that otherwise it will quickly fill your log partition # partclone.dd -c -d -s /dev/sda1 -o - | bzip2 -1 -c > /tmp/nfs/sda1.winXP.32bit.img # Once tested run without -d option # # partclone.dd -c -s /dev/sda1 -o - | bzip2 -1 -c > /tmp/nfs/sda1.winXP.32bit.img # parted -l > /tmp/nfs/log.parted.l.txt # parted -l -m > /tmp/nfs/log.parted.lm.txt # # to backup the partition table from the MBR sector (don't use it on GPT partitioned system) # sfdisk -d > /tmp/nfs/log.sfdisk.d.txt # # umount /tmp/nfs
At the end unmount the NFS partition and we are ready to reboot the system.
Later on, as a security precaution create md5sums and some level of par2 recovery files if the image should have ever get corrupted.
# md5sum -b sda1.winXP.32bit.img > sda1.winXP.32bit.img.md5 # par2create -r3 sda1.winXP.32bit.img
References:
[1] SystemRescueCd
[2] Sysresccd-manual-en How to install SystemRescueCd on an USB-stick
[3] partclone.dd
man 5 nfs
par2 home page
man par2
Subscribe to:
Posts (Atom)