1

What happens to data copied after undoing fdisk?

view story
linux-howto

http://unix.stackexchange.com – Suppose I have some drive with a single partition. For some reason I decide to repartition it, using fdisk. I create multiple partitions, then write the partition table, then exit fdisk. At this point the kernel is still not aware of the new partition table : the initial partition is still mounted through NFS, it was only "lazy-unmounted" (umount -l) before fdisk, so it triggered the "device or resource busy" error. Now I change my mind, launch fdisk again, and merge all partitions into a single one, exactly as it was at first. Then again I write the partition table, exit fdisk, and the (HowTos)

Songlist's picture
Submitted by Songlist on 11/07/2012

Stories similar to What happens to data copied after undoing fdisk?

I ran fdisk on the wrong HD. I basically cleared partition table, pressed w and quited fdisk and only then realized that that was my main harddrive...

I got this message:

WARNING: Re-reading the partition table failed with error 16: Device or resource busy. The kernel still uses the old table.

I'm trying to set up an 8GB USB drive a persistent live boot.

The tutorial I am using told me to use fdisk and create two partitions. The first partition is supposed to be just large enough to hold the ISO image I'm using, which in this case is 2.9GB.

I used a whole device as LVM physical partition, just so

sudo pvcreate /dev/xvdg

Unfortunately, while this was in use, I then accidentally overwrote some data (I think), by writing a new partition table:

sudo fdisk /dev/xvdg, add new partition, write partition table, delete partition, write empty partition table

This is where I am currently at.

I recently added a new 3TB hard drive to a headless media server (HP proliant microserver) running Ubuntu server 12.04. I followed this tutorial, which uses fdisk to create a single partition of the maximum sixe reported by fdisk. I have choosen ext4 format. I then copied across all my media, which took some time.

For example:

sam@sam:~$ sudo fdisk /dev/sdb [sudo] password for sam: Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel Building a new DOS disklabel with disk identifier 0xb063e88f. Changes will remain in memory only, until you decide to write them. After that, of course, the previous content won't be recoverable.

Warning: invalid flag 0x0000 of par

I read that fdisk cannot be used to create partitions greater than 2GB. So I use "parted" to create my partition and use fdisk to view them once created and it has NEVER been a problem until now.

I have an infotrend RAID 6 that after I use parted and look at the RAID with "fdisk -l" it reports two partitions;

I have my computer with both W7 and Ubuntu for quite a while now. I had made the Partitions with Easeus Partition Manager and no problem there.

I've grown fond of Ubuntu and wanted to allocate it more space.

hi,

i'm trying to make my imac capable of triple boot.

the software i use are:

mac os x 10.5.8 win vista sp1 linux opensuse 11.2 and, rEFIt GParted

i used the diskutility to create 6 partitions.

1st. is for the EFI 2nd. is for mac 3rd. is for linux 4th. is for windows

fdisk help 6 weeks 6 days ago

I'm concerned that you have damaged your current /dev/sda2 partition. In your original post you showed how you'd used fdisk to create a partition table on /dev/sda2 and then wrote it to d... [by TrevorH]