clonezilla-live

[Clonezilla-live] [1.2.6-24-i686] Doesn't update partition ID

[Gilles <cod...@fr...>]

Hello

Using the latest and greatest (1.2.6-24-i686) to build a live USB, I 
noticed this issue when restoring a Windows partition after running 
Linux, either as Beginner or Expert: Clonezilla leaves the partition 
ID to "Linux" instead of updating this to "NTFS/HPFS".

As a result of this, when rebooting, Windows complains with "autochk 
application not found", and just reboots endlessly.

The work-around is to boot with a Linux live CD (Clonezilla or 
equivalent), and run "fdisk" to change the partition ID accordingly.

HTH,
Gilles.

Re: [Clonezilla-live] [1.2.6-24-i686] Doesn't update partition ID

[Steven S. <st...@nc...>]

Hi,
Thanks for the bug report.
Does this problem occur when you do disk to disk cloning, or image 
restoring?
Normally Clonezilla should honor the partition table of source disk, and 
create the same table on the destination disk. No idea why there is 
Could you please run the following commands on the source disk:
1. sudo fdisk -l /dev/sda
2. sudo parted -s /dev/sda print
(Replace /dev/sda as the source disk device name)
then tell us the results?

Thanks.

Steven.

On 2010/9/30 下午 08:00, Gilles wrote:
> Hello
>
> Using the latest and greatest (1.2.6-24-i686) to build a live USB, I
> noticed this issue when restoring a Windows partition after running
> Linux, either as Beginner or Expert: Clonezilla leaves the partition
> ID to "Linux" instead of updating this to "NTFS/HPFS".
>
> As a result of this, when rebooting, Windows complains with "autochk
> application not found", and just reboots endlessly.
>
> The work-around is to boot with a Linux live CD (Clonezilla or
> equivalent), and run "fdisk" to change the partition ID accordingly.
>
> HTH,
> Gilles.
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Clonezilla-live mailing list
> Clo...@li...
> https://lists.sourceforge.net/lists/listinfo/clonezilla-live

-- 
Steven Shiau <steven _at_ nchc org tw> <steven _at_ stevenshiau org>
National Center for High-performance Computing, Taiwan.
http://www.nchc.org.tw
Public Key Server PGP Key ID: 1024D/9762755A
Fingerprint: A2A1 08B7 C22C 3D06 34DB  F4BC 08B3 E3D7 9762 755A

Re: [Clonezilla-live] [1.2.6-24-i686] Doesn't update partition ID

[Gilles <cod...@fr...>]

At 03:00 01/10/2010, Steven Shiau wrote:
>Does this problem occur when you do disk to disk cloning, or image restoring?

When restoring an image from /sda2 to /sda1 on my test host. I only 
use Clonezilla to restore an image into a partition, so as to be able 
to test applications in the different versions of Windows. That's 
also why it was important for me to understand exactly what CZ does 
to the MBR, especially the bootloader part, when restoring just one partition.

>Normally Clonezilla should honor the partition table of source disk, 
>and create the same table on the destination disk. No idea why there is

Does Clonezilla rewrite the partition table in the MBR even when just 
restoring an image in a single partition (instead of restoring the 
image of a whole disk)?

>Could you please run the following commands on the source disk:
>1. sudo fdisk -l /dev/sda
>2. sudo parted -s /dev/sda print
>(Replace /dev/sda as the source disk device name)
>then tell us the results?

Here goes:
//================ fdisk -l /dev/sda
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xa2e3ce9a
    Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1        2550    20482843+   7  HPFS/NTFS
/dev/sda2            2551        7649    40957717+  83  Linux
/dev/sda3           10200       10330     1052257+   5  Extended
/dev/sda5           10200       10330     1052226   82  Linux swap / Solaris

//================ parted -s /dev/sda print
Model: ATA WDC WD1600AAJS-2 (scsi)
Disk /dev/sda: 160GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number  Start   End     Size    Type      File system     Flags
  1      32.3kB  21.0GB  21.0GB  primary   ntfs            boot
  2      21.0GB  62.9GB  41.9GB  primary   ext2
  3      83.9GB  85.0GB  1078MB  extended
  5      83.9GB  85.0GB  1077MB  logical   linux-swap(v1)

I didn't know Base64 could look this cute :-)
http://img705.imageshack.us/img705/1020/clonezillashiaubase64.jpg

Cheers,
Gilles. 

Re: [Clonezilla-live] [1.2.6-24-i686] Doesn't update partition ID

[Steven S. <st...@nc...>]

Hi,

On 2010年10月01日 17:17, Gilles wrote:
> At 03:00 01/10/2010, Steven Shiau wrote:
>    
>> Does this problem occur when you do disk to disk cloning, or image restoring?
>>      
> When restoring an image from /sda2 to /sda1 on my test host. I only
> use Clonezilla to restore an image into a partition, so as to be able
> to test applications in the different versions of Windows. That's
> also why it was important for me to understand exactly what CZ does
> to the MBR, especially the bootloader part, when restoring just one partition.
>    
When you restore a partition image, Clonezilla won't touch MBR by 
default, unless you enter expert mode and check the option to force it 
to do that.
>    
>> Normally Clonezilla should honor the partition table of source disk,
>> and create the same table on the destination disk. No idea why there is
>>      
> Does Clonezilla rewrite the partition table in the MBR even when just
> restoring an image in a single partition (instead of restoring the
> image of a whole disk)?
>    
No. As mentioned in the above.
>    
>> Could you please run the following commands on the source disk:
>> 1. sudo fdisk -l /dev/sda
>> 2. sudo parted -s /dev/sda print
>> (Replace /dev/sda as the source disk device name)
>> then tell us the results?
>>      
> Here goes:
> //================ fdisk -l /dev/sda
> Disk /dev/sda: 160.0 GB, 160041885696 bytes
> 255 heads, 63 sectors/track, 19457 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0xa2e3ce9a
>      Device Boot      Start         End      Blocks   Id  System
> /dev/sda1   *           1        2550    20482843+   7  HPFS/NTFS
> /dev/sda2            2551        7649    40957717+  83  Linux
> /dev/sda3           10200       10330     1052257+   5  Extended
> /dev/sda5           10200       10330     1052226   82  Linux swap / Solaris
>
> //================ parted -s /dev/sda print
> Model: ATA WDC WD1600AAJS-2 (scsi)
> Disk /dev/sda: 160GB
> Sector size (logical/physical): 512B/512B
> Partition Table: msdos
> Number  Start   End     Size    Type      File system     Flags
>    1      32.3kB  21.0GB  21.0GB  primary   ntfs            boot
>    2      21.0GB  62.9GB  41.9GB  primary   ext2
>    3      83.9GB  85.0GB  1078MB  extended
>    5      83.9GB  85.0GB  1077MB  logical   linux-swap(v1)
>    
 From what you have mentioned, I think it's correct. There is an 
existing partition table on the destination disk, and clonezilla does 
not touch it, it just restores the image to the partition without touch 
the partition table. Therefore in this case, you have to tune the 
partition table by yourself, or you can enter expert mode, check the 
option to force clonezilla to recreate the partition table on the 
destination disk.

Steven.
> I didn't know Base64 could look this cute :-)
> http://img705.imageshack.us/img705/1020/clonezillashiaubase64.jpg
>
> Cheers,
> Gilles.
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Clonezilla-live mailing list
> Clo...@li...
> https://lists.sourceforge.net/lists/listinfo/clonezilla-live
>    

-- 
Steven Shiau<steven _at_ nchc org tw>  <steven _at_ stevenshiau org>
National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw
Public Key Server PGP Key ID: 1024D/9762755A
Fingerprint: A2A1 08B7 C22C 3D06 34DB  F4BC 08B3 E3D7 9762 755A

Re: [Clonezilla-live] [1.2.6-24-i686] Doesn't update partition ID

[Gilles <cod...@fr...>]

At 17:46 02/10/2010, Steven Shiau wrote:
>Actually if you check "-t", no MBR will be restored. Here we mean 
>it's 446 bytes (executable code area):
>http://en.wikipedia.org/wiki/Master_boot_record
>This is the default options for beginner mode:

Thanks for the clarification. Depending on the context, "MBR" can 
refer to the whole 512-byte section, ie. both the bootloader + 
partition table, or it can refer only to the bootloader.

I have a couple more questions:

1. I've read that to wipe out the bootloader, I should zero out the 
first 440 bytes: Why did you write 446? Are there extra bytes that I 
can zero out as well?

//This is what I use:
dd if=/dev/zero of=/dev/sda bs=440 count=1

2. In the -t1 option, does "prebuilt MBR" mean "Windows bootloader"? 
When restoring a Windows partition after playing with Linux (ie. GRUB 
as boot loader), I notice that even leaving this option unchecked 
does restore the Windows bootloader anyway. So I guess the -t1 option 
is only needed if, for some reason, the user needs to force 
Clonezilla to restore the Windows bootloader (equivalent to booting 
with Windows CD and running "fixmbr").

I suggest changing the text as follows:

[*] -g Reinstall GRUB bootloader in MBR on target disk (only if GRUB 
config exists in any Linux partition)
[] -t Clonezilla does not restore bootloader in MBR
[] -t1 Clonezilla restores prebuilt bootloader from syslinux (For Windows only)

Thank you. 

Re: [Clonezilla-live] [1.2.6-24-i686] Doesn't update partition ID

[Steven S. <st...@nc...>]

On 10/06/2010 03:30 AM, Gilles wrote:
> At 17:46 02/10/2010, Steven Shiau wrote:
>    
>> Actually if you check "-t", no MBR will be restored. Here we mean
>> it's 446 bytes (executable code area):
>> http://en.wikipedia.org/wiki/Master_boot_record
>> This is the default options for beginner mode:
>>      
> Thanks for the clarification. Depending on the context, "MBR" can
> refer to the whole 512-byte section, ie. both the bootloader +
> partition table, or it can refer only to the bootloader.
>
> I have a couple more questions:
>
> 1. I've read that to wipe out the bootloader, I should zero out the
> first 440 bytes: Why did you write 446? Are there extra bytes that I
> can zero out as well?
>
> //This is what I use:
> dd if=/dev/zero of=/dev/sda bs=440 count=1
>    
 From http://en.wikipedia.org/wiki/Master_boot_record you can tell the 
max is 446.
> 2. In the -t1 option, does "prebuilt MBR" mean "Windows bootloader"?
> When restoring a Windows partition after playing with Linux (ie. GRUB
> as boot loader), I notice that even leaving this option unchecked
> does restore the Windows bootloader anyway. So I guess the -t1 option
> is only needed if, for some reason, the user needs to force
> Clonezilla to restore the Windows bootloader (equivalent to booting
> with Windows CD and running "fixmbr").
>    
Yes.
> I suggest changing the text as follows:
>
> [*] -g Reinstall GRUB bootloader in MBR on target disk (only if GRUB
> config exists in any Linux partition)
> [] -t Clonezilla does not restore bootloader in MBR
> [] -t1 Clonezilla restores prebuilt bootloader from syslinux (For Windows only)
>    
That's true. Sometimes it's very confusing to use "MBR"...
It will be fixed in the next release.
Thanks.

Steven.
> Thank you.
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2&  L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Clonezilla-live mailing list
> Clo...@li...
> https://lists.sourceforge.net/lists/listinfo/clonez
>    

-- 
Steven Shiau<steven _at_ nchc org tw>  <steven _at_ stevenshiau org>
National Center for High-performance Computing, Taiwan.
http://www.nchc.org.tw
Public Key Server PGP Key ID: 1024D/9762755A
Fingerprint: A2A1 08B7 C22C 3D06 34DB  F4BC 08B3 E3D7 9762 755A

Re: [Clonezilla-live] [1.2.6-24-i686] Doesn't update partition ID

[Gilles <cod...@fr...>]

Hello

At 15:46 12/10/2010, Steven Shiau wrote:
> > //This is what I use:
> > dd if=/dev/zero of=/dev/sda bs=440 count=1
> >
>  From http://en.wikipedia.org/wiki/Master_boot_record you can tell the
>max is 446.

Right, so I was wondering if I should zero out the first 446 bytes? 
The reason I ask, is the command above that I read on the web. So can 
you/someone confirm that zeroing out the 446 bytes is the right thing 
to do, or are there side-effects I should know about?

Thank you. 

Re: [Clonezilla-live] [1.2.6-24-i686] Doesn't update partition ID

[Steven S. <st...@nc...>]

On 2010年10月12日 21:57, Gilles wrote:
> Hello
>
> At 15:46 12/10/2010, Steven Shiau wrote:
>    
>>> //This is what I use:
>>> dd if=/dev/zero of=/dev/sda bs=440 count=1
>>>
>>>        
>>    From http://en.wikipedia.org/wiki/Master_boot_record you can tell the
>> max is 446.
>>      
> Right, so I was wondering if I should zero out the first 446 bytes?
> The reason I ask, is the command above that I read on the web. So can
> you/someone confirm that zeroing out the 446 bytes is the right thing
> to do, or are there side-effects I should know about?
>    
Not very sure. Here we always use 446. So far no issue

Steven.
> Thank you.
>
>
> ------------------------------------------------------------------------------
> Beautiful is writing same markup. Internet Explorer 9 supports
> standards for HTML5, CSS3, SVG 1.1,  ECMAScript5, and DOM L2&  L3.
> Spend less time writing and  rewriting code and more time creating great
> experiences on the web. Be a part of the beta today.
> http://p.sf.net/sfu/beautyoftheweb
> _______________________________________________
> Clonezilla-live mailing list
> Clo...@li...
> https://lists.sourceforge.net/lists/listinfo/clonezilla-live
>    

-- 
Steven Shiau<steven _at_ nchc org tw>  <steven _at_ stevenshiau org>
National Center for High-performance Computing, Taiwan. http://www.nchc.org.tw
Public Key Server PGP Key ID: 1024D/9762755A
Fingerprint: A2A1 08B7 C22C 3D06 34DB  F4BC 08B3 E3D7 9762 755A

Re: [Clonezilla-live] [1.2.6-24-i686] Doesn't update partition ID

[Gilles <cod...@fr...>]

At 05:47 14/10/2010, Steven Shiau wrote:
>Not very sure. Here we always use 446. So far no issue

Thanks for the tip. I'll wipe out the first 446 bytes then instead of 440.