SVN : 2455 restore bug
-
It certainly sounds like a bug, but it should work. Maybe grub shouldn’t be trying to locate the boot volume via UUID?
-
[quote=“Tom Elliott, post: 38142, member: 7271”]It certainly sounds like a bug, but it should work. Maybe grub shouldn’t be trying to locate the boot volume via UUID?[/quote]
I’ll modify the grub on the master. Before that update I have upload the image and restore it without problem.
-
I guess I’m not understanding the issue.
The only thing that changed from the d1.partitions setup is instead of making the Chunk and start sector always start at 2048, we’re pulling the start partition directly from the d1.original.partitions file.
The exact command is:
[code]cat $data | grep start | awk -F, '{print $1}' | awk -F 'start=' '{print $2}' | awk '{print $1}' | egrep -v 0$ | sort -n| head -1;[/code]The $data variable is the the d1.original.partitions file. The start get’s the line that says start, the awk only prints the first side of all the data up until the comma. The second Awk prints the data after start=. The third awk removes any extra white space. The egrep command just removes the 0 start sectors from the view. The sort -n just sorts the data from lowest to highest. The head -1 just gives us the first value. If your d1.original.partitions file has /dev/sda1 starting at sector 2048, nothing should be wrong.
I’m not saying there couldn’t be a problem, just trying to figure out what the problem is.
-
[quote=“Tom Elliott, post: 38144, member: 7271”]I guess I’m not understanding the issue.
The only thing that changed from the d1.partitions setup is instead of making the Chunk and start sector always start at 2048, we’re pulling the start partition directly from the d1.original.partitions file.
The exact command is:
[code]cat $data | grep start | awk -F, '{print $1}' | awk -F 'start=' '{print $2}' | awk '{print $1}' | egrep -v 0$ | sort -n| head -1;[/code]The $data variable is the the d1.original.partitions file. The start get’s the line that says start, the awk only prints the first side of all the data up until the comma. The second Awk prints the data after start=. The third awk removes any extra white space. The egrep command just removes the 0 start sectors from the view. The sort -n just sorts the data from lowest to highest. The head -1 just gives us the first value. If your d1.original.partitions file has /dev/sda1 starting at sector 2048, nothing should be wrong.
I’m not saying there couldn’t be a problem, just trying to figure out what the problem is.[/quote]
I’ll try to remove the image from fog server and upload it.
-
Hi,
I use this : [url]http://www.reliableembeddedsystems.com/wiki/index.php?title=Grub2/Ubuntu_remove_UUID_stuff[/url]
It’s now good for me.
Regards,
Ch3i. -
[quote=“ch3i, post: 38261, member: 2513”]Hi,
I use this : [url]http://www.reliableembeddedsystems.com/wiki/index.php?title=Grub2/Ubuntu_remove_UUID_stuff[/url]
[S]It’s now good for me.[/S]
Regards,
Ch3i.[/quote]After a second test, when I restore a computer I have a new partition table :
1 primary partition for the boot windows
1 primary for the windows installation
1 partition with the /boot for grub
1 extend with these partitions- 1 partition (empty)
Below the content of the image folder :
[CODE]-rwxrwxrwx 1 root root 0 oct. 27 15:22 d1.has_grub
-rwxrwxrwx 1 root root 1048576 oct. 27 15:22 d1.mbr
-rwxrwxrwx 1 root root 47 oct. 27 15:58 d1.original.swapuuids
-rwxrwxrwx 1 root root 25363450 oct. 27 15:22 d1p1.img
-rwxrwxrwx 1 root root 75859218715 oct. 27 15:45 d1p2.img
-rwxrwxrwx 1 root root 5225 oct. 27 15:45 d1p3.img
-rwxrwxrwx 1 root root 79517576 oct. 27 15:46 d1p5.img
-rwxrwxrwx 1 root root 39452923097 oct. 27 15:58 d1p6.img
-rwxrwxrwx 1 root root 2459943866 oct. 27 15:59 d1p8.img
-rwxrwxrwx 1 root root 130522435 oct. 27 15:59 d1p9.img
-rwxrwxrwx 1 root root 514 oct. 27 15:22 d1.partitions
[/CODE]And the d1.partitions :
[CODE]/dev/sda1 : start= 2048, size= 204800, Id= 7, bootable
/dev/sda2 : start= 206848, size=204595200, Id= 7
/dev/sda3 : start=204804094, size=771969026, Id= 5
/dev/sda4 : start= 0, size= 0, Id= 0
/dev/sda5 : start=204804096, size= 602112, Id=83
/dev/sda6 : start=205408256, size=194899968, Id=83
/dev/sda7 : start=400310272, size= 15622144, Id=82
/dev/sda8 : start=415934464, size=277053440, Id=83
/dev/sda9 : start=692989952, size=283781120, Id= 7[/CODE]In the image management I have these settings :
- OS : Linux - (50)
- Image Type : Multiple Partition Image - Single Disk (Not Resizable) - (2)
- Partition : Everything - (1)
Any Idea ?
-
I’m confused.
My guess, /dev/sda4 is your extended partition.
-
[quote=“Tom Elliott, post: 38270, member: 7271”]I’m confused.
My guess, /dev/sda4 is your extended partition.[/quote]
The extended is the /dev/sda3, when I check with the disk tools of Ubuntu (or another same installation on debian/windows) I’have not a /dev/sda4.
Below the result of fdisk -l :
[CODE]/dev/sda1 * 2048 206847 102400 7 HPFS/NTFS/exFAT
/dev/sda2 206848 204802047 102297600 7 HPFS/NTFS/exFAT
/dev/sda3 204804094 625141759 210168833 5 Étendue
/dev/sda5 204804096 205623295 409600 83 Linux
/dev/sda6 205625344 410425343 102400000 83 Linux
/dev/sda7 410427392 422715391 6144000 82 partition d’échange Linux / Solaris
/dev/sda8 422717440 523524095 50403328 83 Linux
/dev/sda9 523526144 625141759 50807808 7 HPFS/NTFS/exFAT
[/CODE] -
So it’s not working properly?
-
[quote=“Tom Elliott, post: 38272, member: 7271”]So it’s not working properly?[/quote]
The result of the fdisk -l is on the original computer.
On the new computer when I boot with the Gptarted live I have a popup error at launch : “invalid partition table on /dev/sda – wrong signature 0”.
Gparted show this partition table :
/dev/sda1 - ntfs - System Reserved - boot flag
/dev/sda2 - ntfs - Windows OS
/dev/sda3 - extend
/dev/sda5 - ext4
free space… -
Do you know what revision you were at before the update and breaking?
-
Also, does it go through and image all 9 partitions, or stop imaging on number 5?
-
[quote=“Tom Elliott, post: 38298, member: 7271”]Also, does it go through and image all 9 partitions, or stop imaging on number 5?[/quote]
I’ll test another tomorrow, but I think it restore all partition.
For the sda4 it’s normal that it’s not use by linux if the sda4 it’s not primary or extend.[QUOTE]Do you know what revision you were at before the update and breaking?[/QUOTE]
I’ll check tomorrow.
Regards,
Ch3i. -
This post is deleted! -
[quote=“ch3i, post: 38307, member: 2513”]I’ll test another tomorrow, but I think it restore all partition.
For the sda4 it’s normal that it’s not use by linux if the sda4 it’s not primary or extend.I’ll check tomorrow.
Regards,
Ch3i.[/quote]Partclone restore all partitions.
Before the 2455 I think I use a version older than 1 or 2 days.
Regards,
Ch3i. -
Hi,
I solve my problem by using another partition table :
[CODE]/dev/sda1 – windows boot (ntfs)
/dev/sda2 – windows system (ntfs)
/dev/sda3 – linux / (ext4)
/dev/sda4 – extended (-)
/dev/sda5 – swap (-)
/dev/sda6 – DATA (ntfs)
[/CODE]Regards,
Ch3i.
