I'm wanting to copy my entire Natty install from /dev/sda to the new disk - /dev/sdc and be able to boot into it.
Yesterday I added a 3 TB USB drive to my system and proceeded to erase the useless software that comes on the drive (Seagate Go Flex), formatted as ext3, then clone a 2 TB internal SATA drive using clonezilla.
This failed so I then tried the dd command (dd if=/dev/sda of=/dev/sdc) as root.
The operation completed after several hours, with no errors and claimed it had copied 2 TB of data to the new disk, so I tried to boot it. The message said something like - insert disk or bootable media..."
What was supposed to happen according to a guide I found, was after the copy was made I was supposed to go into gparted to expand the size of the partition (since I was cloning a smaller drive to a larger one) but gparted reports the entire drive as 'unformatted', and also as being 2.7 TB (100+ GB - 1% reserved for root, since I first formatted as ext3).
The system no longer sees the drive in file manager but is recognized by fdisk, and BIOS (under the cdrom drives section).
fdisk -lu reports:
Disk /dev/sdc: 3000.6 GB, 3000592977920 bytes
255 heads, 63 sectors/track, 45600 cylinders, total 732566645 sectors
Units = sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x000d1faa
Device Boot Start End Blocks Id System
/dev/sdc1 * 2048 59375615 237494272 83 Linux
/dev/sdc2 59377662 3907028991 2505703432 5 Extended
Partition 2 does not start on physical sector boundary.
fdisk /dev/sdc1 returns:
"Note: sector size is 4096 (not 512)
Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0xd01e4e29.
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 partition table 4 will be corrected by w(rite)
WARNING: DOS-compatible mode is deprecated. It's strongly recommended to
switch off the mode (command 'c') and change display units to
sectors (command 'u').
"
Googling on 'invalid flag' I found this http://ubuntuforums.org/showthread.php?t=1192598 on sfdisk but I'm unsure that this is the actual problem.
sfdisk -l reports:
Disk /dev/sdc: 364801 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sdc1 * 0+ 3695- 3696- 29686784 83 Linux
/dev/sdc2 3696+ 243201- 239506- 1923825665 5 Extended
/dev/sdc3 0 - 0 0 0 Empty
/dev/sdc4 0 - 0 0 0 Empty
/dev/sdc5 10504+ 243201- 232698- 1869139968 83 Linux
/dev/sdc6 3696+ 3817- 122- 975872 82 Linux swap / Solaris
/dev/sdc7 3817+ 10504- 6687- 53707776 83 Linux
The drive I attempted to clone is sda - sfdisk says:
Disk /dev/sda: 243201 cylinders, 255 heads, 63 sectors/track
Warning: extended partition does not start at a cylinder boundary.
DOS and Linux will interpret the contents differently.
Units = cylinders of 8225280 bytes, blocks of 1024 bytes, counting from 0
Device Boot Start End #cyls #blocks Id System
/dev/sda1 * 0+ 3695- 3696- 29686784 83 Linux
/dev/sda2 3696+ 243201- 239506- 1923825665 5 Extended
/dev/sda3 0 - 0 0 0 Empty
/dev/sda4 0 - 0 0 0 Empty
/dev/sda5 10504+ 243201- 232698- 1869139968 83 Linux
/dev/sda6 3696+ 3817- 122- 975872 82 Linux swap / Solaris
/dev/sda7 3817+ 10504- 6687- 53707776 83 Linux
Ubuntu's disk utility shows:
and:
With all this:
"Partition 2 does not start on a physical sector boundary"
and:
"Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)" and Note: sector size is 4096 (not 512)"
and:
"Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel
Building a new DOS disklabel with disk identifier 0xd01e4e29.
Changes will remain in memory only, until you decide to write them.
After that, of course, the previous content won't be recoverable."
... I'm unsure what the next step would be if this is even recoverable at all.
Can someone see what the problem might be?
Thanks
Mr. M
Adv Reply
Originally Posted by HavarN
Bookmarks