/[clonezilla-sysresccd]/trunk/www/onepage.html
ViewVC logotype

Diff of /trunk/www/onepage.html

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 72 by sng, Mon May 31 19:35:50 2010 UTC revision 102 by sng, Wed Aug 18 09:06:52 2010 UTC
# Line 72  Line 72 
72  <H2>Clonezilla-SysRescCD</H2>  <H2>Clonezilla-SysRescCD</H2>
73  <H3>Wellcome</H3>  <H3>Wellcome</H3>
74    <div style="margin:0; padding: 3px; width: 980; position relative;">    <div style="margin:0; padding: 3px; width: 980; position relative;">
75      <div style="position: absolute; left: 0px;"><H4>25/05/2010 - v 3.1.0</H4></div>      <div style="position: absolute; left: 0px;"><H4>10/08/2010 - v 3.1.0</H4></div>
76      <div style="position: absolute; right: 0px;"><H4>Last update: 31/05/2010</H4></div>      <div style="position: absolute; right: 0px;"><H4>Last update: 18/08/2010</H4></div>
77    </div>    </div>
78  </div>  </div>
79  <div id="linkline">  <div id="linkline">
80    <a class="here" href="index.html">Home</a>    <a class="here" href="index.html">Home</a>
81    <a href="news.php">News</a>    <a href="news.php">News</a>
82    <a href="doc.html">Documentation</a>    <a href="doc.html">Documentation</a>
83    <a href="index.html#download">Download</a>    <a href="download.html">Download</a>
84    <a href="screenshots.html">Screenshots</a>    <a href="screenshots.html">Screenshots</a>
85    <a href="index.html#credits">Credits</a>    <a href="index.html#credits">Credits</a>
86    <a href="help.html">Help</a>    <a href="help.html">Help</a>
# Line 131  Well, I started this project because I w Line 131  Well, I started this project because I w
131  <tr><td class="bordertable"  colspan="4"><b>Release table</b></td></tr>  <tr><td class="bordertable"  colspan="4"><b>Release table</b></td></tr>
132  <tr><td class="bordertable"  valign="top"><b>Date</b></td><td class="bordertable"  valign="top"><b>Version</b></td>  <tr><td class="bordertable"  valign="top"><b>Date</b></td><td class="bordertable"  valign="top"><b>Version</b></td>
133  <td class="bordertable"  valign="top"><b>Clonezilla Live Version</b></td><td class="bordertable"  valign="top"><b>SystemRescueCD Version</b></td></tr>  <td class="bordertable"  valign="top"><b>Clonezilla Live Version</b></td><td class="bordertable"  valign="top"><b>SystemRescueCD Version</b></td></tr>
134  <tr><td  class="bordertable" >25/05/10</td><td  class="bordertable" >3.1.0</td><td  class="bordertable" >1.2.5-17&nbsp;(mod)</td><td  class="bordertable" >1.5.4&nbsp;(mod)</td>  <tr><td  class="bordertable" >25/08/10</td><td  class="bordertable" >3.1.0</td><td  class="bordertable" >1.2.5-35&nbsp;(mod)</td><td  class="bordertable" >1.5.8</td>
135  </tr>  </tr>
136  <tr><td  class="bordertable" >02/07/08</td><td  class="bordertable" >2.6.0</td><td  class="bordertable" >1.1.0-8&nbsp;(mod)</td><td  class="bordertable" >1.0.4&nbsp;(mod)</td>  <tr><td  class="bordertable" >02/07/08</td><td  class="bordertable" >2.6.0</td><td  class="bordertable" >1.1.0-8&nbsp;(mod)</td><td  class="bordertable" >1.0.4&nbsp;(mod)</td>
137  </tr>  </tr>
# Line 162  Well, I started this project because I w Line 162  Well, I started this project because I w
162  <table class="bordertable"  cellpadding="5">  <table class="bordertable"  cellpadding="5">
163  <tr><td class="bordertable" width="10"><b>Version</b></td><td  class="bordertable" width="10"><b>Package/CD</b></td><td class="bordertable"><b>Comments</b></td></tr>  <tr><td class="bordertable" width="10"><b>Version</b></td><td  class="bordertable" width="10"><b>Package/CD</b></td><td class="bordertable"><b>Comments</b></td></tr>
164  <tr><td class="bordertable" width="10" valign="top"><a name="3.1.0"></a>3.1.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">  <tr><td class="bordertable" width="10" valign="top"><a name="3.1.0"></a>3.1.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">
165  -&nbsp;<b>Clonezilla Live</b> updated to version 1.2.5-17-686<br>  -&nbsp;<b>Clonezilla Live</b> updated to version 1.2.5-35<br>
166  -&nbsp;<b>SystemRescueCD</b> updated to version 1.5.3<br>  -&nbsp;<b>SystemRescueCD</b> updated to version 1.5.8<br>
167  -&nbsp;<b>Super Grub Disk</b> updated to version 0.9799<br>  -&nbsp;<b>Super Grub Disk</b> updated to version 0.9799<br>
168  -&nbsp;Added <b>Super Grub Disk 2</b> version 1.30<br>  -&nbsp;Added <b>Super Grub Disk 2</b> version 1.98s<br>
169  -&nbsp;Most operations are now executed through the TUI (Text User Interface)<br>  -&nbsp;Most operations are now executed through the TUI (Text User Interface)<br>
170  -&nbsp;Major site / documentation update (thanks to Jyrki Vesterinen)  -&nbsp;Major site / documentation update (thanks to Jyrki Vesterinen)
171  </td></tr>  </td></tr>
# Line 298  More info: <a href="reloc-img.html">Rest Line 298  More info: <a href="reloc-img.html">Rest
298  </td></tr>  </td></tr>
299  <tr><td class="bordertable" width="10">0.1</td><td class="bordertable" width="10"></td><td class="bordertable">-&nbsp;Initial release</td></tr>  <tr><td class="bordertable" width="10">0.1</td><td class="bordertable" width="10"></td><td class="bordertable">-&nbsp;Initial release</td></tr>
300  </table>  </table>
301    <!--
302  <H2><a name="download"></a>Download <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="download"></a>Download <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>
303  <p>  <p>
304  Installation package: <a href="http://clonezilla-sysresccd.hellug.gr/create-clonezilla-sysresccd-3.1.0".tar.gz" target="_blank">create-clonezilla-sysresccd-3.1.0.tar.gz</a> [~ B]<br>  <!--Whenever possible I will provide a link to the CD created using profile 0 (full CD)<br><br>
305  ISO file: <a href="http://clonezilla-sysresccd.hellug.gr/clonezilla-sysresccd-full-mod-3.1.0.iso" target="_blank">clonezilla-sysresccd-full-mod-3.1.0.iso</a> [~ B]<br>  Installation package: <a href="http://clonezilla-sysresccd.hellug.gr/create-clonezilla-sysresccd-3.1.0".tar.gz" target="_blank">create-clonezilla-sysresccd-3.1.0.tar.gz</a> [~ 6.2 MB]<br>
306    <!--Torrent: <a href="http://thepiratebay.org/tor/4272742" target="_blank">The Pirate Bay</a> | <a href="http://linuxtracker.org/index.php?page=torrent-details&id=4b0f13a25440e3d34fb700cc0ff884c28a73fadf" target="_blank">Linux Tracker</a><br>
307    ISO file: <a href="http://clonezilla-sysresccd.hellug.gr/clonezilla-sysresccd-full-mod-3.1.0.iso" target="_blank">clonezilla-sysresccd-full-mod-3.1.0.iso</a> [~ ISO_SIZEB]<br>
308  md5sum file: <a href="http://clonezilla-sysresccd.hellug.gr/md5sum.txt" target="_blank">md5sum.txt</a><br><br>  md5sum file: <a href="http://clonezilla-sysresccd.hellug.gr/md5sum.txt" target="_blank">md5sum.txt</a><br><br>
309  ISO file md5sum: <b><i></i></b></p>  ISO file md5sum: <b><i>"MD5SUM"</i></b></p>
310    -->
311  <H2><a name="user-help"></a>Can I help? <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="user-help"></a>Can I help? <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>
312  <p>Yes, of course you can. If you have:</p>  <p>Yes, of course you can. If you have:</p>
313  <ul style="margin-right: 30pt;">  <ul style="margin-right: 30pt;">
# Line 350  The ISO 9660 filesystem is encapsulated Line 354  The ISO 9660 filesystem is encapsulated
354  Incorrect use of any raw disk writing tool could cause your<br> operating system (GNU/Linux / Windows) <b>not to boot</b>.<br><br> Confirm the command before you run it.<br></td></tr></table></div>  Incorrect use of any raw disk writing tool could cause your<br> operating system (GNU/Linux / Windows) <b>not to boot</b>.<br><br> Confirm the command before you run it.<br></td></tr></table></div>
355  <p>So, from any linux box, assuming <b>Clonezilla-SysRescCD</b> iso file is in your home directory, and your USB device name is <b><font color="Green">sdc4</font></b>, you just execute the commands:</p>  <p>So, from any linux box, assuming <b>Clonezilla-SysRescCD</b> iso file is in your home directory, and your USB device name is <b><font color="Green">sdc4</font></b>, you just execute the commands:</p>
356  <p class="newcode">umount /dev/<font color="Green">sdc4</font><br>  <p class="newcode">umount /dev/<font color="Green">sdc4</font><br>
357  dd if=~/clonezilla-sysresccd-full-mod-3.1.0.iso of=/dev/<font color="Green">sdc4</font> bs=512</p>  dd if=~/clonezilla-sysresccd-full-mod-3.1.0.iso of=/dev/<font color="Green">sdc</font> bs=512</p>
358  <p>And that's it. Your usb device is ready to boot!!!</p>  <p>And that's it. Your usb device is ready to boot!!!</p>
359    <H3><a name="usb-free-space"></a>Using the extra space <span class="hideprint">[<a href="#usb-top" title="go to top of the page">^</a>]</span></H3>
360    <p>
361    If your usb device is more than 400MB in size, the above command will leave the remaining space unused. To verify it, execute the command:
362    </p>
363    <p class="newcode" style="margin-left: 0;">fdisk -l /dev/<font color="Green">sdc</font></p>
364    <p style="margin-left: 0;">You should get something similar to this:</p>
365    <p class="newcode">
366    Disk /dev/sdc: 1048 MB, 1048576000 bytes<br>
367    64 heads, 32 sectors/track, 1000 cylinders, total 2048000 sectors<br>
368    Units = sectors of 1 * 512 = 512 bytes<br>
369    Sector size (logical/physical): 512 bytes / 512 bytes<br>
370    I/O size (minimum/optimal): 512 bytes / 512 bytes<br>
371    Disk identifier: 0x77a5188f<br>
372    <br>
373    &nbsp;&nbsp;&nbsp;Device&nbsp;Boot&nbsp;&nbsp;Start&nbsp;&nbsp;End&nbsp;&nbsp;Blocks&nbsp;&nbsp;Id&nbsp;&nbsp;System
374    /dev/sdc1&nbsp;&nbsp;&nbsp;&nbsp;*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1&nbsp;&nbsp;384&nbsp;&nbsp;393216&nbsp;&nbsp;17&nbsp;&nbsp;Hidden&nbsp;HPFS/NTFS
375    </p>
376    <p>
377    As you can see, we are currently using 348 out of 1000 cylinders of the disk. The remaining disk space (~600MB) can still be used, executing the following commands:
378    </p>
379    <p class="newcode">
380    fdisk /dev/<font color="green">sdc</font><br>
381    command (m for help): <font color="magenta">n</font> <font color="#990000">(create new partition)</font><br>
382    command action<br>
383       e   extended<br>
384       p   primary partition (1-4)<br>
385    <font color="magenta">p</font><br>
386    partition number (1-4): <font color="magenta">4</font> <font color="#990000">(create partition sdc4)</font><br>
387    first cylinder (385-1000, default 385): <br>
388    using default value 385<br>
389    last cylinder, +cylinders or +size{k,m,g} (385-1000, default 1000): <br>
390    using default value 1000<br>
391    <br>
392    command (m for help): <font color="magenta">p</font> <font color="#990000">(display partition table)</font><br>
393    <br>
394    disk /dev/sdc: 1048 mb, 1048576000 bytes<br>
395    64 heads, 32 sectors/track, 1000 cylinders<br>
396    units = cylinders of 2048 * 512 = 1048576 bytes<br>
397    sector size (logical/physical): 512 bytes / 512 bytes<br>
398    i/o size (minimum/optimal): 512 bytes / 512 bytes<br>
399    disk identifier: 0x77a5188f<br>
400    <br>
401    &nbsp;&nbsp;&nbsp;device&nbsp;boot&nbsp;&nbsp;start&nbsp;&nbsp;&nbsp;end&nbsp;&nbsp;blocks&nbsp;&nbsp;&nbsp;id&nbsp;&nbsp;system<br>
402    /dev/sdc1&nbsp;&nbsp;&nbsp;*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1&nbsp;&nbsp;&nbsp;384&nbsp;&nbsp;393216&nbsp;&nbsp;&nbsp;17&nbsp;&nbsp;hidden&nbsp;hpfs/ntfs<br>
403    /dev/sdc4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;385&nbsp;&nbsp;1000&nbsp;&nbsp;630784&nbsp;&nbsp;&nbsp;83&nbsp;&nbsp;linux<br>
404    <br>
405    <br>
406    command (m for help): <font color="magenta">t</font> <font color="#990000">(change partition type)</font><br>
407    partition number (1-4): <font color="magenta">4</font><br>
408    hex code (type l to list codes): <font color="magenta">b</font><br>
409    changed system type of partition 4 to b (w95 fat32)<br>
410    <br>
411    command (m for help): <font color="magenta">p</font> <font color="#990000">(display partition table)</font><br>
412    <br>
413    disk /dev/sdc: 1048 mb, 1048576000 bytes<br>
414    64 heads, 32 sectors/track, 1000 cylinders<br>
415    units = cylinders of 2048 * 512 = 1048576 bytes<br>
416    sector size (logical/physical): 512 bytes / 512 bytes<br>
417    i/o size (minimum/optimal): 512 bytes / 512 bytes<br>
418    disk identifier: 0x77a5188f<br>
419    <br>
420    &nbsp;&nbsp;&nbsp;device&nbsp;boot&nbsp;&nbsp;start&nbsp;&nbsp;&nbsp;end&nbsp;&nbsp;blocks&nbsp;&nbsp;&nbsp;id&nbsp;&nbsp;system<br>
421    /dev/sdc1&nbsp;&nbsp;&nbsp;*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1&nbsp;&nbsp;&nbsp;384&nbsp;&nbsp;393216&nbsp;&nbsp;&nbsp;17&nbsp;&nbsp;hidden&nbsp;hpfs/ntfs<br>
422    /dev/sdc4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;385&nbsp;&nbsp;1000&nbsp;&nbsp;630784&nbsp;&nbsp;&nbsp;&nbsp;b&nbsp;&nbsp;w95&nbsp;fat32<br>
423    <br>
424    command (m for help): <font color="magenta">w</font> <font color="#990000">(write partition table to disk and exit)</font><br>
425    The partition table has been altered!<br>
426    <br>
427    Calling ioctl() to re-read partition table.<br>
428    <br>
429    WARNING: Re-reading the partition table failed with error 16: Device or resource busy.<br>
430    The kernel still uses the old table. The new table will be used at<br>
431    the next reboot or after you run partprobe(8) or kpartx(8)<br>
432    Syncing disks.
433    </p>
434    <p>
435    At this point you should disconnect and reconnect your usb device. When it's recognised, you can format the partition you've just created
436     </p>
437    <p class="newcode">
438    mkdosfs -F 32 /dev/<font color="Green">sdc4</font>
439    </p>
440    <p>
441    The partition is now ready for use!!!
442    </p>
443  <H2><a name="usb-hard"></a>Installing the "hard" way <span class="hideprint">[<a href="#usb-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="usb-hard"></a>Installing the "hard" way <span class="hideprint">[<a href="#usb-top" title="go to top of the page">^</a>]</span></H2>
444  <p>If the "easy" way does not work there is an alternative; you will use the <b>Clonezilla-SysRescCD</b> ISO file (or CD) to copy and modify a couple of files on the USB disk, and finally make it bootable, using <a href="http://syslinux.zytor.com" target="_blank">syslinux</a> and its configuration file <b>syslinux.cfg</b>.</p>  <p>If the "easy" way does not work there is an alternative; you will use the <b>Clonezilla-SysRescCD</b> ISO file (or CD) to copy and modify a couple of files on the USB disk, and finally make it bootable, using <a href="http://syslinux.zytor.com" target="_blank">syslinux</a> and its configuration file <b>syslinux.cfg</b>.</p>
445  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>
# Line 433  The first thing you should do is double Line 521  The first thing you should do is double
521  If you are on linux, check that the partition on the USB disk is active (bootable), executing:</p>  If you are on linux, check that the partition on the USB disk is active (bootable), executing:</p>
522  <p class="newcode" style="margin-left: 0;">fdisk -l /dev/<font color="Green">sdc</font></p>  <p class="newcode" style="margin-left: 0;">fdisk -l /dev/<font color="Green">sdc</font></p>
523  <p style="margin-left: 0;">You should get something similar to this:</p>  <p style="margin-left: 0;">You should get something similar to this:</p>
524  <table class="newcode" style="margin-left: 0pt;" border="0" width="100%">  <p class="newcode">
525  <tr><td colspan="7">Disk /dev/<font color="Green">sdc</font>: 1031 MB, 1031798272 bytes</td></tr>  Disk /dev/<font color="Green">sdc</font>: 1031 MB, 1031798272 bytes<br>
526  <tr><td colspan="7">64 heads, 32 sectors/track, 983 cylinders</td></tr>  64 heads, 32 sectors/track, 983 cylinders<br>
527  <tr><td colspan="7">Units = cylinders of 2048 * 512 = 1048576 bytes</td></tr>  Units = cylinders of 2048 * 512 = 1048576 bytes<br>
528  <tr><td>&nbsp;</td></tr>  <br>
529  <tr>  &nbsp;&nbsp;&nbsp;Device&nbsp;&nbsp;<font color="Red">Boot</font>&nbsp;&nbsp;Start&nbsp;&nbsp;End&nbsp;&nbsp;&nbsp;Blocks&nbsp;&nbsp;Id&nbsp;&nbsp;System<br>
530  <td align="right">Device&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td><td align="right"><font color="Red">Boot</font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td><td align="right">Start&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td><td align="right">End&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td><td align="right">Blocks&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td><td align="right">Id&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td><td align="right">System&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td><td width="99%"></td></tr>  /dev/<font color="Green">sdc4</font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<font color="Red">*</font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1&nbsp;&nbsp;983&nbsp;&nbsp;1006576&nbsp;&nbsp;&nbsp;6&nbsp;&nbsp;FAT16<br>
531  <tr><td align="right">/dev/<font color="Green">sdc4</font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td><td align="right"><font color="Red">*</font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td><td align="right">1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td><td align="right">983&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td><td align="right">1006576&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td><td align="right">6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td><td align="right">FAT16&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</td><td width="99%"></td>  </p>
 </tr>  
 </table>  
532  <p style="margin-left: 0;"><br>If the partition is not active (no astrisk), execute:</p>  <p style="margin-left: 0;"><br>If the partition is not active (no astrisk), execute:</p>
533  <p class="newcode" style="margin-left: 0;">fdisk /dev/<font color="Green">sdc</font></p>  <p class="newcode" style="margin-left: 0;">fdisk /dev/<font color="Green">sdc</font></p>
534  <p style="margin-left: 0;">and issue "Command: " <b>a</b> (toggle a bootable flag) and "Partition number:" <b><font color="Green">4</font></b> (for <b>/dev/<font color="Green">sdc4</font></b>).<br><br>  <p style="margin-left: 0;">and issue "Command: " <b>a</b> (toggle a bootable flag) and "Partition number:" <b><font color="Green">4</font></b> (for <b>/dev/<font color="Green">sdc4</font></b>).<br><br>
# Line 526  While in the splash screen of <b>Clonezi Line 612  While in the splash screen of <b>Clonezi
612  </p>  </p>
613  <H2><a name="sysresccd"></a>SystemRescueCD boot parameters <span class="hideprint">[<a href="#boot-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="sysresccd"></a>SystemRescueCD boot parameters <span class="hideprint">[<a href="#boot-top" title="go to top of the page">^</a>]</span></H2>
614  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>
615  The following info applies to <b>SystemRescueCD v. 1.5.4</b>. In case<br>  The following info applies to <b>SystemRescueCD v. 1.5.5</b>. In case<br>
616   you need to get info for a more recent version of <b>SystemRescueCD</b><br>   you need to get info for a more recent version of <b>SystemRescueCD</b><br>
617  please see the page "<a href="http://www.sysresccd.org/Sysresccd-manual-en_Booting_the_CD-ROM" target="_blank">Sysresccd-manual-en Booting the CD-ROM</a>"  please see the page "<a href="http://www.sysresccd.org/Sysresccd-manual-en_Booting_the_CD-ROM" target="_blank">Sysresccd-manual-en Booting the CD-ROM</a>"
618  </td></tr></table></div>  </td></tr></table></div>
# Line 545  Available kernels (boot images):</p> Line 631  Available kernels (boot images):</p>
631  <p><br>The boot parameters you can use are:</p>  <p><br>The boot parameters you can use are:</p>
632  <div class="otherpage">  <div class="otherpage">
633  <a name="General_boot_options" id="General_boot_options"></a><p><b> General boot options</b></p>  <a name="General_boot_options" id="General_boot_options"></a><p><b> General boot options</b></p>
634  <p>Press &lt;TAB&gt; to add additional options.  <p>Press &lt;TAB&gt; to add additional options (in SystemRescueCd-1.5 and more recent)
635  </p>  </p>
636  <ul><li><b>docache</b>: causes the CD-ROM will be fully loaded into memory. A slower start but once complete, programs start faster and the CD drive will be released allowing normal access to other CDs.   This requires 400MB of memory to cache everything (including the <code>bootdisks</code> and <code>isolinux</code> directories). Add <code>lowmem</code> if you have less that 400MB of memory of to prevent these directories to be copied.  <ul><li><b>docache</b>: causes the CD-ROM will be fully loaded into memory. A slower start but once complete, programs start faster and the CD drive will be released allowing normal access to other CDs.   This requires 400MB of memory to cache everything (including the <code>bootdisks</code> and <code>isolinux</code> directories). Add <code>lowmem</code> if you have less that 400MB of memory of to prevent these directories to be copied.
637  </li></ul>  </li><li><b>setkmap=kk</b>:  which defines the keymap to load  where <code>kk</code>  (example: <code>setkmap=de</code> for German keyboards). This way you won't be prompted for the keyboard configuration during the boot.
 <p>During boot you will be prompted for the keyboard configuration, avoid this by using  
 </p>  
 <ul><li><b>setkmap=kk</b>:  which defines the keymap to load  where <code>kk</code>  (example: <code>setkmap=de</code> for German keyboards)  
638  </li><li><b>root=/dev/xdnp</b>: the <a target="_blank" href="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" class="external text" title="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" rel="nofollow">root=&lt;device&gt; option</a>  boots an existing linux system. For example, if you have linux Gentoo installed on <code>/dev/sda6</code>,  use <code>rescuecd root=/dev/sda6</code> to start it. Keep in mind that you must use a 64bit kernel if your system is made of 64bit programs. This option works with LVM volumes. Use <code>rescuecd root=/dev/VolGroup00/LogVol00</code>. Support is also provided for <code>root=auto</code>, which scans all the block devices tfor a linux system. The first linux system found will be started. So with <code>root=auto</code> let you start the system installed from the CD-ROM in case you have problem with your boot loader or kernel. It's also possible to specify a partition using its <code>filesystem label</code> or <code>filesystem uuid</code>. If the label of the partition where linux is installed is <code>mylinux</code>, then boot it using <code>rescuecd root=LABEL=mylinux</code>. Similarly <code>root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7</code>. See <a target="_blank" href="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" class="external text" title="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" rel="nofollow">more details</a>.  </li><li><b>root=/dev/xdnp</b>: the <a target="_blank" href="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" class="external text" title="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" rel="nofollow">root=&lt;device&gt; option</a>  boots an existing linux system. For example, if you have linux Gentoo installed on <code>/dev/sda6</code>,  use <code>rescuecd root=/dev/sda6</code> to start it. Keep in mind that you must use a 64bit kernel if your system is made of 64bit programs. This option works with LVM volumes. Use <code>rescuecd root=/dev/VolGroup00/LogVol00</code>. Support is also provided for <code>root=auto</code>, which scans all the block devices tfor a linux system. The first linux system found will be started. So with <code>root=auto</code> let you start the system installed from the CD-ROM in case you have problem with your boot loader or kernel. It's also possible to specify a partition using its <code>filesystem label</code> or <code>filesystem uuid</code>. If the label of the partition where linux is installed is <code>mylinux</code>, then boot it using <code>rescuecd root=LABEL=mylinux</code>. Similarly <code>root=UUID=b3d3bec5-997a-413e-8449-0d0ec41ccba7</code>. See <a target="_blank" href="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" class="external text" title="http://www.sysresccd.org/news/2008/06/05/use-systemrescuecd-to-boot-a-linux-os-from-the-hard-disk/" rel="nofollow">more details</a>.
639  </li><li><b>initscript=service:action</b>: This options allows start/stop a service at boot time. For instance if you need the samba service to be started, you can boot with: <code>initscript=samba:start</code>. This does the same thing as <code>/etc/init.d/samba start</code>. Use this option multiple times for different services. All the actions that are supported by an initscript can be used.  </li><li><b>initscript=service:action</b>: This options allows start/stop a service at boot time. For instance if you need the samba service to be started, you can boot with: <code>initscript=samba:start</code>. This does the same thing as <code>/etc/init.d/samba start</code>. Use this option multiple times for different services. All the actions that are supported by an initscript can be used.
640  </li><li><b>backstore=xxx</b>: SystemRescueCd comes with support for the <a target="_blank" href="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" class="external text" title="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" rel="nofollow">backing-stores</a>. A backing-store  saves all the changes you can make. so that you keep these changes the next time you boot it. By default, sysresccd automatically scan removable devices (eg: USB sticks) at boot time and uses the first backing-store it finds. A backing-store is not mandatory and it the scan fails it will store the files which change in memory. To disable the disks scan at boot time specify <code>backstore=off</code> on the boot command line. If you want to save your backing-store file on an harddisk,  boot with <code>backstore=alldev</code> to scan all devices (not just removable devices). The default location for backing-stores file is any file named <code>sysrcd.bs</code> located at the root of a disk which is often an USB stick. Change the path by using  <code>backstore=/sysrcd/mybackstore.bs</code>. See <a target="_blank" href="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" class="external text" title="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" rel="nofollow">backing-stores</a>.  </li><li><b>backstore=xxx</b>: SystemRescueCd comes with support for the <a target="_blank" href="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" class="external text" title="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" rel="nofollow">backing-stores</a>. A backing-store  saves all the changes you can make. so that you keep these changes the next time you boot it. By default, sysresccd automatically scan removable devices (eg: USB sticks) at boot time and uses the first backing-store it finds. A backing-store is not mandatory and it the scan fails it will store the files which change in memory. To disable the disks scan at boot time specify <code>backstore=off</code> on the boot command line. If you want to save your backing-store file on an harddisk,  boot with <code>backstore=alldev</code> to scan all devices (not just removable devices). The default location for backing-stores file is any file named <code>sysrcd.bs</code> located at the root of a disk which is often an USB stick. Change the path by using  <code>backstore=/sysrcd/mybackstore.bs</code>. See <a target="_blank" href="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" class="external text" title="http://www.sysresccd.org/news/2008/06/29/creating-a-backing-store-to-keep-your-modifications-in-sysresccd/" rel="nofollow">backing-stores</a>.
# Line 560  Available kernels (boot images):</p> Line 643  Available kernels (boot images):</p>
643  <a name="Hardware.2C_drivers_and_troubleshooting_options" id="Hardware.2C_drivers_and_troubleshooting_options"></a><p><b><br> Hardware, drivers and troubleshooting options</b></p>  <a name="Hardware.2C_drivers_and_troubleshooting_options" id="Hardware.2C_drivers_and_troubleshooting_options"></a><p><b><br> Hardware, drivers and troubleshooting options</b></p>
644  <ul><li><b>dodebug</b>: Enables verbose messages in linuxrc  <ul><li><b>dodebug</b>: Enables verbose messages in linuxrc
645  </li></ul>  </li></ul>
646  <ul><li><b>doload=xxx</b>: loads needed modules, multiple occurrences are permitted (example: <code>doload=3c59x</code>)  <ul><li><b>doload=xxx</b>: loads needed kernel modules, multiple comma separated occurrences are permitted (example: <code>doload=3c59x,e1000</code>)
647  </li><li><b>noload=xxx</b>: prevents loading modules, multiple occurrences are permitted (example: <code>noload=3c59x</code>). Use this option if you have a problem when the system loads a particular module.  </li><li><b>noload=xxx</b>: prevents loading kernel modules, multiple comma separated occurrences are permitted (example: <code>noload=3c59x,e1000</code>). Use this option if you have a problem when the system loads a particular module.
648  </li><li><b>nonet</b>: this will disable the network auto detection at startup  </li><li><b>nonet</b>: this will disable the network auto detection at startup
649  </li></ul>  </li></ul>
650  <ul><li><b>scandelay=x</b>: pauses x seconds during the startup to allow slow devices to initialize. This is required when you boot an USB device. A delay of only few seconds should be enough.  <ul><li><b>scandelay=x</b>: pauses x seconds during the startup to allow slow devices to initialize. This is required when you boot an USB device. A delay of only few seconds should be enough.
# Line 584  Available kernels (boot images):</p> Line 667  Available kernels (boot images):</p>
667  <ul><li><b>skipmount=/dev/xxx</b>: The system mounts all the storage devices at boot time to find the sysrcd.dat file.  If your hard disk is broken it should be mounted. Boot with <code>skipmount=/dev/sda1 skipmount=/dev/sda2</code> to ignore these two partitions.  <ul><li><b>skipmount=/dev/xxx</b>: The system mounts all the storage devices at boot time to find the sysrcd.dat file.  If your hard disk is broken it should be mounted. Boot with <code>skipmount=/dev/sda1 skipmount=/dev/sda2</code> to ignore these two partitions.
668  </li></ul>  </li></ul>
669  <a name="Network_configuration_and_remote_access" id="Network_configuration_and_remote_access"></a><p><b><br> Network configuration and remote access</b></p>  <a name="Network_configuration_and_remote_access" id="Network_configuration_and_remote_access"></a><p><b><br> Network configuration and remote access</b></p>
670  <ul><li><b>dodhcp</b>:  to request a DHCP server provide network attributes including an IP address, gateway... .  otherwise,  <ul><li><b>nonm</b>: to disable the Network-Manager service that conflicts with the standard network command line tools such as <code>ifconfig</code> and <code>ip</code>. You can use this option if you want to configure the network using these commands. This option is not necessary when SystemRescueCd is booting from the network since the service is automatically stopped in that case. This option requires SystemRescueCd-1.5.5 or more recent.
671    </li><li><b>dodhcp</b>: to request a DHCP server provide network attributes including an IP address, gateway...
672    </li><li><b>nodhcp</b>: never run the dhcp client in the initramfs boot script. May be useful if you use PXE boot on a computer with several ethernet interfaces. Support for this option is available in SystemRescueCd-1.5.5-beta2 and more recent
673  </li><li><b>ethx=ipaddr/cidr</b>: Sets the static IP address of all the ethernet interfaces on the system. The <code>/cidr</code> extension is optional. For instance, if you use option <code>ethx=192.168.0.1</code> on a machine with two ethernet adapters, both <code>eth0</code> and <code>eth1</code> will be configured with <code>192.168.0.1</code>. You can use the format <code>ethx=10.0.0.1/24</code> (using the cidr notation) if you don't use the default netmask.  </li><li><b>ethx=ipaddr/cidr</b>: Sets the static IP address of all the ethernet interfaces on the system. The <code>/cidr</code> extension is optional. For instance, if you use option <code>ethx=192.168.0.1</code> on a machine with two ethernet adapters, both <code>eth0</code> and <code>eth1</code> will be configured with <code>192.168.0.1</code>. You can use the format <code>ethx=10.0.0.1/24</code> (using the cidr notation) if you don't use the default netmask.
674  </li><li><b>eth0=ipaddr/cidr</b>: This option is similar to <code>ethx=ipaddr/cidr</code> but it configures only one interface at a time.  To configure the network on a server that has two interfaces, use: <code>eth0=192.168.10.1/24 eth1=192.168.20.1</code>.  </li><li><b>eth0=ipaddr/cidr</b>: This option is similar to <code>ethx=ipaddr/cidr</code> but it configures only one interface at a time.  To configure the network on a server that has two interfaces, use: <code>eth0=192.168.10.1/24 eth1=192.168.20.1</code>.
675  </li><li><b>dns=ipaddr</b>: Sets the static IP address of the DNS nameserver you want to use to resolve the names. For instance <code>dns=192.168.0.254</code> means that you want to use <code>192.168.0.254</code> as the DNS server.  </li><li><b>dns=ipaddr</b>: Sets the static IP address of the DNS nameserver you want to use to resolve the names. For instance <code>dns=192.168.0.254</code> means that you want to use <code>192.168.0.254</code> as the DNS server.
# Line 592  Available kernels (boot images):</p> Line 677  Available kernels (boot images):</p>
677  </li><li><b>dhcphostname=myhost</b>: Sets the hostname that the DHCP client will send to the DHCP server. This may be required if the default hostname cannot be used with your DHCP configuration. This option has been introduced in SystemRescueCd-1.3.5.  </li><li><b>dhcphostname=myhost</b>: Sets the hostname that the DHCP client will send to the DHCP server. This may be required if the default hostname cannot be used with your DHCP configuration. This option has been introduced in SystemRescueCd-1.3.5.
678  </li><li><b>rootpass=123456</b>: Sets the root password of the system running on the livecd to <code>1234</code>. That way you can connect from the network and ssh on the livecd and give <code>123456</code> password as the root password.  </li><li><b>rootpass=123456</b>: Sets the root password of the system running on the livecd to <code>1234</code>. That way you can connect from the network and ssh on the livecd and give <code>123456</code> password as the root password.
679  </li><li><b>vncserver=x:123456</b>: The <a target="_blank" href="http://www.sysresccd.org/news/2008/04/12/use-systemrescuecd-remotely-with-vnc-server/" class="external text" title="http://www.sysresccd.org/news/2008/04/12/use-systemrescuecd-remotely-with-vnc-server/" rel="nofollow">vncserver boot option</a> has been introduced in SystemRescueCd-1.0.2. This options forces the system to configure the VNC-server and to start it automatically at boot time. You have to replace <code>x</code> with the number of displays you want, and <code>123456</code> with your password The password must be between 5 and 8 characters, else the boot option will be ignored. In other words the <code>vncserver=2:MyPaSsWd</code> option will give you access to two displays (display=1 on tcp/5901 and display=2 on tcp/5902). Display 0 is reserved for X.Org since SystemRescueCd-1.1.0.  </li><li><b>vncserver=x:123456</b>: The <a target="_blank" href="http://www.sysresccd.org/news/2008/04/12/use-systemrescuecd-remotely-with-vnc-server/" class="external text" title="http://www.sysresccd.org/news/2008/04/12/use-systemrescuecd-remotely-with-vnc-server/" rel="nofollow">vncserver boot option</a> has been introduced in SystemRescueCd-1.0.2. This options forces the system to configure the VNC-server and to start it automatically at boot time. You have to replace <code>x</code> with the number of displays you want, and <code>123456</code> with your password The password must be between 5 and 8 characters, else the boot option will be ignored. In other words the <code>vncserver=2:MyPaSsWd</code> option will give you access to two displays (display=1 on tcp/5901 and display=2 on tcp/5902). Display 0 is reserved for X.Org since SystemRescueCd-1.1.0.
680  </li><li><b>nameif=xxx</b>: You can can <a target="_blank" href="http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/" class="external text" title="http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/" rel="nofollow">specify what interface name to give</a> to a particular interface using the mac address. You need SystemRescueCd-1.1.0 or newer to do that. Here is how you can specify which interface is using which mac address on a machine with two network interfaces: <code>nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64</code>. Be careful, you have to respect the separator (comma between the interfaces and exclamation marks between the name and the mac address).  </li><li><b>nameif=xxx</b>: You can can <a target="_blank" href="http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/" class="external text" title="http://www.sysresccd.org/news/2008/06/28/option-to-define-the-name-of-a-network-interface-using-the-mac-address/" rel="nofollow">specify what interface name to give</a> to a particular interface using the mac address. You need SystemRescueCd-1.1.0 or newer to do that. Here is how you can specify which interface is using which mac address on a machine with two network interfaces: <code>nameif=eth0!00:0C:29:57:D0:6E,eth1!00:0C:29:57:D0:64</code>. Be careful, you have to respect the separator (comma between the interfaces and exclamation marks between the name and the mac address). You can also use the magic keyword <a target="_blank" href="http://www.sysresccd.org/forums/viewtopic.php?f=7&amp;t=2538&amp;start=0" class="external text" title="http://www.sysresccd.org/forums/viewtopic.php?f=7&amp;t=2538&amp;start=0" rel="nofollow">BOOTIF</a> with SystemRescueCd-1.5.4 and more recent when you boot from pxelinux. The pxeboot loader will set BOOTIF to the name of the interface used to boot. You can then use something like <code>nameif=eth0!BOOTIF</code> if you want the boot interface to be called <code>eth0</code> on a computer with several Ethernet interfaces.
681  </li></ul>  </li></ul>
682  <a name="Network_boot_using_PXE" id="Network_boot_using_PXE"></a><p><b><br> Network boot using PXE</b></p>  <a name="Network_boot_using_PXE" id="Network_boot_using_PXE"></a><p><b><br> Network boot using PXE</b></p>
683  <p>SystemRescueCd provides several options for booting from the network using PXE.  <p>SystemRescueCd provides several options for booting from the network using PXE.
# Line 1187  ocs-live</p> Line 1272  ocs-live</p>
1272  </ul>  </ul>
1273  <a name="backup-top"></a>  <a name="backup-top"></a>
1274  <H2 style="font-size: 2em;"><a name="backup-intro"></a>Getting backups <span class="hideprint">[<a href="#backup-top" title="go to top of the page">^</a>]</span></H2>  <H2 style="font-size: 2em;"><a name="backup-intro"></a>Getting backups <span class="hideprint">[<a href="#backup-top" title="go to top of the page">^</a>]</span></H2>
1275  <p>In this page I will demonstrate the creation of an image file by getting a backup of a virtual partition (<b>/dev/<font color="Red">hdb1</font></b>). The image file will be saved in another virtual partition (<b>/dev/<font color="Red">hda1</font></b>).<br></p>  <p>In this page I will demonstrate the creation of an image file by getting a backup of a virtual partition (<b>/dev/<font color="Red">sdb1</font></b>). The image file will be saved in another virtual partition (<b>/dev/<font color="Red">sda1</font></b>).<br></p>
1276  <p>  <p>
1277  The first thing you do when you want to get a backup of a disk/partition, is make sure both the souce (to be backed up) and target (to hold the image file) partitions are in excellent condition (error free). This is the logical thing to do, cause I wouldn't want to backup a corrupt partition, or end up with a corrupt image file.<br>  The first thing you do when you want to get a backup of a disk/partition, is make sure both the souce (to be backed up) and target (to hold the image file) partitions are in excellent condition (error free). This is the logical thing to do, cause I wouldn't want to backup a corrupt partition, or end up with a corrupt image file.<br>
1278  <br>  <br>
# Line 1197  Having done all of the above, I am ready Line 1282  Having done all of the above, I am ready
1282  <br>  <br>
1283  </p>  </p>
1284  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>
1285  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.3-27</b>  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.5-35</b>
1286  </td></tr></table></div>  </td></tr></table></div>
1287  <H2><a name="backup"></a>Getting the backup <span class="hideprint">[<a href="#backup-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="backup"></a>Getting the backup <span class="hideprint">[<a href="#backup-top" title="go to top of the page">^</a>]</span></H2>
1288  <H3><a name="bck-0"></a>Clonezilla-SysRescCD starting screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-0"></a>Clonezilla-SysRescCD starting screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
# Line 1241  I select "<font color="Red"><b>local_dev Line 1326  I select "<font color="Red"><b>local_dev
1326  <H3><a name="bck-7"></a>Next screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-7"></a>Next screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1327  <p>This is where I choose the location of the image file. It will be saved at the root directory of the selected partition.<br><br>  <p>This is where I choose the location of the image file. It will be saved at the root directory of the selected partition.<br><br>
1328  <img src="images/backup-06.png"><br>  <img src="images/backup-06.png"><br>
1329  I select partition <font color="Red"><b>hda1</b></font> and press ENTER.<br>  I select partition <font color="Red"><b>sda1</b></font> and press ENTER.<br>
1330  <br>  <br>
1331  <img src="images/backup-07.png"><br>  <img src="images/backup-07.png"><br>
1332  and then ENTER again.</p>  and then ENTER again.</p>
1333  <p><img src="images/backup-08.png"><br>  <p><img src="images/backup-08.png"><br>
1334  This screen displays the mounting result.<br>  This screen displays the mounting result.<br>
1335  As we can see, <font color="Red"><b>/dev/hda1</b></font> has been successfully mounted under <b>/tmp/local-dev</b>.</p>  As we can see, <font color="Red"><b>/dev/sda1</b></font> has been successfully mounted under <b>/tmp/local-dev</b>.</p>
1336  <H3><a name="bck-7a"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-7a"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1337  <p><img src="images/backup-09.png">  <p><img src="images/backup-09.png">
1338  <br>I select <font color="Red"><b>Beginer mode</b></font> to accept the default backup options. If you select <font color="Red"><b>Expert mode</b></font>, you can choose the options yourself. More details can be found <a href="clonezilla.html#backup-options" target="_blank">here</a>.</p>  <br>I select <font color="Red"><b>Beginer mode</b></font> to accept the default backup options. If you select <font color="Red"><b>Expert mode</b></font>, you can choose the options yourself. More details can be found <a href="clonezilla.html#backup-options" target="_blank">here</a>.</p>
# Line 1259  I select "<font color="Red"><b>savedisk< Line 1344  I select "<font color="Red"><b>savedisk<
1344  <H3><a name="bck-9"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-9"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1345  <p><img src="images/backup-11.png"><br>  <p><img src="images/backup-11.png"><br>
1346  In this screen I select the image name.<br>  In this screen I select the image name.<br>
1347  I type "Backup_5-2010_hdb", which in my opinion is more informative name than the default.  I type "Backup_32-2010_sdb", which in my opinion is more informative name than the default.
1348  </p>  </p>
1349  <H3><a name="bck-10"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-10"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1350  <p><img src="images/backup-12.png"><br>  <p><img src="images/backup-12.png"><br>
# Line 1285  reboot<br><br></p> Line 1370  reboot<br><br></p>
1370  <H2 style="font-size: 2em;"><a name="backup-smb-intro"></a>Getting backups on Samba <span class="hideprint">[<a href="#backup-smb-top" title="go to top of the page">^</a>]</span></H2>  <H2 style="font-size: 2em;"><a name="backup-smb-intro"></a>Getting backups on Samba <span class="hideprint">[<a href="#backup-smb-top" title="go to top of the page">^</a>]</span></H2>
1371  <p>What if you don't have a spare local disk or partition or a USB disk? How will you be able to get a backup of your system? Well, if your PC is on the same LAN with another PC running Windows (or linux), you can use <b>Samba</b> to save your image file on that remote PC (which we will call <b>Samba server</b> from now on).<br><br>  <p>What if you don't have a spare local disk or partition or a USB disk? How will you be able to get a backup of your system? Well, if your PC is on the same LAN with another PC running Windows (or linux), you can use <b>Samba</b> to save your image file on that remote PC (which we will call <b>Samba server</b> from now on).<br><br>
1372  Using <b>Samba</b> you will be able to mount a Windows share resource (or Samba share resource), from within <b>Clonezilla Live</b>, and save the image file there. Then you can boot that PC using <b>SystemRescueCD</b> and create a restore DVD.<br><br>  Using <b>Samba</b> you will be able to mount a Windows share resource (or Samba share resource), from within <b>Clonezilla Live</b>, and save the image file there. Then you can boot that PC using <b>SystemRescueCD</b> and create a restore DVD.<br><br>
1373  In this page I will demonstrate the creation of an image file by getting a backup of my second disk (<b>/dev/<font color="Red">hdb</font></b>). The image file will be save in my Samba server which is my laptop (ip: <b><font color="Red">10.0.0.3</font></b>, Windows share resource name: <b><font color="Red">all_my_images</font></b>).  In this page I will demonstrate the creation of an image file by getting a backup of my second disk (<b>/dev/<font color="Red">sdb</font></b>). The image file will be save in my Samba server which is my laptop (ip: <b><font color="Red">10.0.0.3</font></b>, Windows share resource name: <b><font color="Red">all_my_images</font></b>).
1374  </p>  </p>
1375  <H3><a name="what-is"></a>What is Samba? [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>  <H3><a name="what-is"></a>What is Samba? [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1376  <p>We read at <a href="http://us1.samba.org/samba/" target="_blank">http://us1.samba.org/samba/</a>:</p>  <p>We read at <a href="http://us1.samba.org/samba/" target="_blank">http://us1.samba.org/samba/</a>:</p>
# Line 1337  I type "<font color="Red"><b>spiros</b>< Line 1422  I type "<font color="Red"><b>spiros</b><
1422  <H3><a name="bck-smb-7"></a>Screen "Mount Samba Server" (fourth time) [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-smb-7"></a>Screen "Mount Samba Server" (fourth time) [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1423  <p>This is where I have to enter the directory name on my Samba server, in which the image file will be saved.<br><br> I type "<font color="Red"><b>/all_my_images</b></font>" and press ENTER.<br><br>  <p>This is where I have to enter the directory name on my Samba server, in which the image file will be saved.<br><br> I type "<font color="Red"><b>/all_my_images</b></font>" and press ENTER.<br><br>
1424  <img src="images/backup-smb-09.png"><br>  <img src="images/backup-smb-09.png"><br>
1425  At this point I informed I will be asked for the password for user <b><font color="Red"><b>spiros</b></font></b>.<br><br>  At this point I'm informed I'm going to be asked for the password for user <b><font color="Red"><b>spiros</b></font></b>.<br><br>
1426  <img src="images/backup-smb-10.png"><br>  <img src="images/backup-smb-10.png"><br>
1427  I will be able to continue only after entering it correctly.<br><br>  I will be able to continue only after entering it correctly.<br><br>
1428  <img src="images/backup-smb-11.png"></p>  <img src="images/backup-smb-11.png"></p>
# Line 1352  I select "<font color="Red"><b>savedisk< Line 1437  I select "<font color="Red"><b>savedisk<
1437  <H3><a name="bck-smb-9"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-smb-9"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1438  <p><img src="images/backup-11.png"><br>  <p><img src="images/backup-11.png"><br>
1439  In this screen I select the image name.<br>  In this screen I select the image name.<br>
1440  I type "Backup_5-2010_hdb", which in my opinion is more informative name than the default.  I type "Backup_32-2010_sdb", which in my opinion is more informative name than the default.
1441  </p>  </p>
1442  <H3><a name="bck-smb-10"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>  <H3><a name="bck-smb-10"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1443  <p><img src="images/backup-12.png"><br>  <p><img src="images/backup-12.png"><br>
# Line 1374  cd<br> Line 1459  cd<br>
1459  umount -a<br>  umount -a<br>
1460  reboot<br><br></p>  reboot<br><br></p>
1461  <p>to reboot the system.</p>  <p>to reboot the system.</p>
1462  <a name="restore-top"></a>  <a name="restore-top"></a>
1463    <H2 style="font-size: 2em;"><a name="restore-intro"></a>Restoring data <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>
1464    <p>Image files are always created for one purpose: restoring the data they contain. Images can be, for example, a backup solution: as long as hardware works, the computer can be restored to the state it was when creating the image. Another usage scenario is changing the hard drive: files can be copy-pasted from the old drive to the new, but that method doesn't make the new drive bootable. Disk images do.</p>
1465    <p>This page contains a demonstration of the latter case. On the <a href="backup.html">Getting backups</a> page, a 500 MB virtual disk containing 160 megabytes of data was copied to a 2 GB virtual disk which was empty. Now the 500 MB disk is changed to an empty 2 GB disk (still virtual) and I'll restore the data to that disk.</p>
1466  <H2 style="font-size: 2em;"><a name="restore-intro"></a>Restoring data <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>  <p>When creating a disk image, one needs to check that both the source and target partitions are error free. That's not required when the image is restored, because restoration process can't damage the disk image. Note, however, that restoring an image erases all the data in the target disk/partition.</p>
1467    <p>You also need to check the BIOS settings to be able to boot from <b>Clonezilla-SysRescCD</b>. Some BIOSes contain a boot menu, others require editing settings pernamently. Details can be found on the manual of the motherboard or laptop.</p>
1468  <p>Image files are always created for one purpose: restoring the data they contain. Images can be, for example, a backup solution: as long as hardware works, the computer can be restored to the state it was when creating the image. Another usage scenario is changing the hard drive: files can be copy-pasted from the old drive to the new, but that method doesn't make the new drive bootable. Disk images do.</p>  <p>Now let's boot.</p>
1469    <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>
1470  <p>This page contains a demonstration of the latter case. On the <a href="backup.html">Getting backups</a> page, a 500 MB virtual disk containing 160 megabytes of data was copied to a 2 GB virtual disk which was empty. Now the 500 MB disk is changed to an empty 2 GB disk (still virtual) and I'll restore the data to that disk.</p>  Restore process erases all the data on the target disk/partition.<br><br>Before restoring make sure you have backup of all the data<br> on the target disk/partition, even if the filesystem is corrupted.
1471    </td></tr></table></div>
1472  <p>When creating a disk image, one needs to check that both the source and target partitions are error free. That's not required when the image is restored, because restoration process can't damage the disk image. Note, however, that restoring an image erases all the data in the target disk/partition.</p>  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>
1473    The following pressentation has been made using<br><b>Clonezilla Live v 1.2.5-35</b>
1474  <p>You also need to check the BIOS settings to be able to boot from <b>Clonezilla-SysRescCD</b>. Some BIOSes contain a boot menu, others require editing settings pernamently. Details can be found on the manual of the motherboard or laptop.</p>  </td></tr></table></div>
1475    <H2><a name="restore"></a>Restoring data <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>
1476  <p>Now let's boot.</p>  <H3><a name="res-0"></a>Clonezilla-SysRescCD starting screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1477    <p>If you're fine with US keymap and English language (available languages are English, Spanish, French, Italian, Japanese and Chinese [both simplified and traditional]) or don't mind editing the boot parameters, just select <b>Clonezilla Live</b> at the starting screen and press ENTER. When the system comes up, it will load the program that will preform the backup. After that continue from <a href="#res-4">this step</a>.</p>
1478  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>  <p>If you need to change these settings, select one of the available <b>Clonezilla Live</b> menu entries, and press <font color="Green"><b>TAB</b></font>. The current boot parameters will be displayed.</p>
1479  Restore process erases all the data on the target disk/partition.<br><br>Before restoring make sure you have backup of all the data<br> on the target disk/partition, even if the filesystem is corrupted.  <p>The default parameters for booting <b>Clonezilla Live</b> on a 1024x768 screen, are the following:</p>
1480  </td></tr></table></div>  <p class="newcode">append initrd=/live/initrd1.img boot=live union=aufs<br>
1481  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>  &nbsp;&nbsp;ocs_live_run="ocs-live-general" ocs_live_extra_param=""<br>
1482  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.3-27</b>  &nbsp;&nbsp;ocs_prerun="/live/image/restorecd/prerun.normal" ocs_live_batch="no"<br>
1483  </td></tr></table></div>  &nbsp;&nbsp;ocs_lang="<font color="Red">en_US.UTF-8</font>" ocs_live_keymap="<font color="Red">NONE</font>" vga=791 nolocales</p>
1484    <p>By deleting the words in red, you instruct <b>Clonezilla Live</b> to ask you the values of these parameters. When the appropriate changes have been done (as shown bellow), just press <font color="Green"><b>ENTER</b></font> to boot.</p>
1485    <p class="newcode">append initrd=/live/initrd1.img boot=live union=aufs<br>
1486  <H2><a name="restore"></a>Restoring data <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>  &nbsp;&nbsp;ocs_live_run="ocs-live-general" ocs_live_extra_param=""<br>
1487    &nbsp;&nbsp;ocs_prerun="/live/image/restorecd/prerun.normal" ocs_live_batch="no"<br>
1488  <H3><a name="res-0"></a>Clonezilla-SysRescCD starting screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  &nbsp;&nbsp;ocs_lang="" ocs_live_keymap="" vga=791 nolocales</p>
1489    </p>
1490  <p>If you're fine with US keymap and English language (available languages are English, Spanish, French, Italian, Japanese and Chinese [both simplified and traditional]) or don't mind editing the boot parameters, just select <b>Clonezilla Live</b> at the starting screen and press ENTER. When the system comes up, it will load the program that will preform the backup. After that continue from <a href="#res-4">this step</a>.</p>  <H3><a name="res-1"></a>Screen "Choose Language" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
   
 <p>If you need to change these settings, select one of the available <b>Clonezilla Live</b> menu entries, and press <font color="Green"><b>TAB</b></font>. The current boot parameters will be displayed.</p>  
   
 <p>The default parameters for booting <b>Clonezilla Live</b> on a 1024x768 screen, are the following:</p>  
   
 <p class="newcode">append initrd=/live/initrd1.img boot=live union=aufs<br>  
 &nbsp;&nbsp;ocs_live_run="ocs-live-general" ocs_live_extra_param=""<br>  
 &nbsp;&nbsp;ocs_prerun="/live/image/restorecd/prerun.normal" ocs_live_batch="no"<br>  
 &nbsp;&nbsp;ocs_lang="<font color="Red">en_US.UTF-8</font>" ocs_live_keymap="<font color="Red">NONE</font>" vga=791 nolocales</p>  
   
 <p>By deleting the words in red, you instruct <b>Clonezilla Live</b> to ask you the values of these parameters. When the appropriate changes have been done (as shown bellow), just press <font color="Green"><b>ENTER</b></font> to boot.</p>  
   
 <p class="newcode">append initrd=/live/initrd1.img boot=live union=aufs<br>  
 &nbsp;&nbsp;ocs_live_run="ocs-live-general" ocs_live_extra_param=""<br>  
 &nbsp;&nbsp;ocs_prerun="/live/image/restorecd/prerun.normal" ocs_live_batch="no"<br>  
 &nbsp;&nbsp;ocs_lang="" ocs_live_keymap="" vga=791 nolocales</p>  
 </p>  
   
 <H3><a name="res-1"></a>Screen "Choose Language" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1491  <p><img src="images/backup-00.png"><br>  <p><img src="images/backup-00.png"><br>
1492  I select "<font color="Red"><b>en_US.UTF-8 English</b></font>" and press ENTER.</p>  I select "<font color="Red"><b>en_US.UTF-8 English</b></font>" and press ENTER.</p>
1493    <H3><a name="res-2"></a>Screen "Configuring console-data" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="res-2"></a>Screen "Configuring console-data" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1494  <p><img src="images/backup-01.png"><br>  <p><img src="images/backup-01.png"><br>
1495  I select "<font color="Red"><b>Select keymap from full list</b></font>" and press ENTER. If you're using US keymap, the default option "<font color="Red"><b>Don't touch keymap</b></font>" is a better choice.</p>  I select "<font color="Red"><b>Select keymap from full list</b></font>" and press ENTER. If you're using US keymap, the default option "<font color="Red"><b>Don't touch keymap</b></font>" is a better choice.</p>
1496    <H3><a name="res-3"></a>Screen "Configuring console-data" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="res-3"></a>Screen "Configuring console-data" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1497  <p><img src="images/backup-02.png"><br>  <p><img src="images/backup-02.png"><br>
1498  Because I haven't changed my keyboard, I select "<font color="Red"><b>pc / qwerty / Finnish / Standard / Standard</b></font>". Because you most likely use a different keyboard, choose the one you use.</p>  Because I haven't changed my keyboard, I select "<font color="Red"><b>pc / qwerty / Finnish / Standard / Standard</b></font>". Because you most likely use a different keyboard, choose the one you use.</p>
1499    <H3><a name="res-4"></a>Screen "Start Clonezilla" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="res-4"></a>Screen "Start Clonezilla" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1500  <p><img src="images/backup-03.png"><br>  <p><img src="images/backup-03.png"><br>
1501  I select "<font color="Red"><b>Start Clonezilla</b></font>" and press ENTER.  I select "<font color="Red"><b>Start Clonezilla</b></font>" and press ENTER.
1502  </p>  </p>
1503    <H3><a name="res-5"></a>Screen "Clonezilla" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="res-5"></a>Screen "Clonezilla" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1504  <p><img src="images/backup-04.png"><br>  <p><img src="images/backup-04.png"><br>
1505  I select "<font color="Red"><b>device-image</b></font>" and press ENTER.<br> <br>  I select "<font color="Red"><b>device-image</b></font>" and press ENTER.<br> <br>
1506  </p>  </p>
1507    <H3><a name="res-6"></a>Screen "Mount clonezilla image directory" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1508  <H3><a name="res-6"></a>Screen "Mount clonezilla image directory" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  <p>In this screen I can select the way the image file directory has been saved.
1509    Available options are local directory, remote directory through <b>ssh</b>, <b>samba</b> or <b>nfs</b> and <b>skip</b>, to use the previously used directory. More info about the image file can be found at section "<a href="clonezilla.html#about">About the Image file</a>".<br>
1510  <p>In this screen I can select the way the image file directory has been saved.  <br>
 Available options are local directory, remote directory through <b>ssh</b>, <b>samba</b> or <b>nfs</b> and <b>skip</b>, to use the previously used directory. More info about the image file can be found at section "<a href="clonezilla.html#about">About the Image file</a>".<br>  
 <br>  
1511  <img src="images/backup-05.png"><br>  <img src="images/backup-05.png"><br>
1512  I select "<font color="Red"><b>local_dev</b></font>" and press ENTER.  I select "<font color="Red"><b>local_dev</b></font>" and press ENTER.
1513  </p>  </p>
1514    <H3><a name="res-7"></a>Next screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1515  <H3><a name="res-7"></a>Next screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  <p>This is where I choose the location of the image file.<br><br>
   
 <p>This is where I choose the location of the image file.<br><br>  
1516  <img src="images/restoration-06.png"><br>  <img src="images/restoration-06.png"><br>
1517  I select partition <font color="Red"><b>hda1</b></font> and press ENTER.<br>  I select partition <font color="Red"><b>sda1</b></font> and press ENTER.<br>
1518  <br>  <br>
1519  <img src="images/backup-07.png"><br>and then ENTER again.</p>  <img src="images/backup-07.png"><br>and then ENTER again.</p>
   
1520  <p><img src="images/restoration-08.png"><br>  <p><img src="images/restoration-08.png"><br>
1521  This screen displays the mounting result.<br>  This screen displays the mounting result.<br>
1522  As we can see, <font color="Red"><b>/dev/hda1</b></font> has been successfully mounted under <b>/tmp/local-dev</b>.</p>  As we can see, <font color="Red"><b>/dev/sda1</b></font> has been successfully mounted under <b>/tmp/local-dev</b>.</p>
1523    <H3><a name="res-7a"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="res-7a"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1524  <p><img src="images/backup-09.png"><br>  <p><img src="images/backup-09.png"><br>
1525  I select <font color="Red"><b>Beginer mode</b></font> to accept the default restore options. If you select <font color="Red"><b>Expert mode</b></font>, you can choose the options yourself. More details can be found <a href="clonezilla.html#restore-options" target="_blank">here</a>.</p>  I select <font color="Red"><b>Beginer mode</b></font> to accept the default restore options. If you select <font color="Red"><b>Expert mode</b></font>, you can choose the options yourself. More details can be found <a href="clonezilla.html#restore-options" target="_blank">here</a>.</p>
1526    <H3><a name="res-8"></a>Screen "Select mode" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1527  <H3><a name="res-8"></a>Screen "Select mode" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  <p>Here I can select the desired operation.<br>
1528    <br>
 <p>Here I can select the desired operation.<br>  
 <br>  
1529  <img src="images/restoration-10.png"><br>  <img src="images/restoration-10.png"><br>
1530  I select "<font color="Red"><b>restoredisk</b></font>" and press ENTER.<br> <br></p>  I select "<font color="Red"><b>restoredisk</b></font>" and press ENTER.<br> <br></p>
1531    <H3><a name="res-9"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="res-9"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1532  <p><img src="images/restoration-11.png"><br>  <p><img src="images/restoration-11.png"><br>
1533  In this screen I select the image folder. This partition contains only one image.</p>  In this screen I select the image folder. This partition contains only one image.</p>
1534    <H3><a name="res-10"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="res-10"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1535  <p><img src="images/restoration-12.png"><br>  <p><img src="images/restoration-12.png"><br>
1536  Finally I am asked to select which partition the image will be restored to. After double-checking the disk doesn't contain anything important, I press ENTER.</p>  Finally I am asked to select which partition the image will be restored to. After double-checking the disk doesn't contain anything important, I press ENTER.</p>
1537    <H3><a name="res-11"></a>Starting the restoration [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="res-11"></a>Starting the restoration [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1538  <p><img src="images/restoration-13.png"><br>  <p><img src="images/restoration-13.png"><br>
1539  Then the program will display the command that will be executed and will ask me to press ENTER. <br>  Then the program will display the command that will be executed and will ask me to press ENTER. <br>
1540  Then I will be asked to confirm the operation by pressing <font color="Red"><b>y</b></font> and ENTER.<br>  Then I will be asked to confirm the operation by pressing <font color="Red"><b>y</b></font> and ENTER.<br>
1541  <img src="images/restoration-14.png"><br>  <img src="images/restoration-14.png"><br>
1542    <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>
1543  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>  <b>This is the last confirmation Clonezilla Live asks.<br>After this step there is no coming back.</b><br></td></tr></table></div>
1544  <b>This is the last confirmation Clonezilla Live asks.<br>After this step there is no coming back.</b><br></td></tr></table></div>  Then my confirmation is asked one last time. After checking one more time the disk doesn't contain any important data, I press <font color="Red"><b>y</b></font> and ENTER.<br>
1545  Then my confirmation is asked one last time. After checking one more time the disk doesn't contain any important data, I press <font color="Red"><b>y</b></font> and ENTER.<br>  <br>
 <br>  
1546  <img src="images/restoration-15.png"><br>  <img src="images/restoration-15.png"><br>
1547  After that, the restore process begins  After that, the restore process begins
1548  <br>  <br>
1549  <br>  <br>
1550  <img src="images/restoration-16.png"><br>  <img src="images/restoration-16.png"><br>
1551  and when it's successfully completed, I will be able to reboot the system by pressing <font color="Red"><b>1</b></font> and ENTER.  and when it's successfully completed, I press ENTER to get to the shell. Then, I execute the commands:</p>
1552  </p>  <p class="newcode">sudo su -<br>
1553    cd<br>
1554    umount -a<br>
1555  <a name="restore-top"></a>  reboot<br><br></p>
1556    <p>to reboot the system.</p>
1557  <H2 style="font-size: 2em;"><a name="restore-intro"></a>Creating a Restore DVD - Part 1 <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>  <a name="restore-top"></a>
1558  <p>Assuming you have used <b>Clonezilla Live</b> to make a backup of your Windows XP system (partition <b>/dev/<font color="Red">hda1</font></b>), which you have saved as <font color="Green"><b>win_img</b></font>, you will probably be wondering what to do with it now. Well, one option would be to keep it to the disk you used to save it in, store the disk, and use it whenever you need it. Another option would be to create a DVD you can use to restore this image.<br><br>  <H2 style="font-size: 2em;"><a name="restore-intro"></a>Creating a Restore DVD - Part 1 <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>
1559    <p>Assuming you have used <b>Clonezilla Live</b> to make a backup of your Windows XP system (partition <b>/dev/<font color="Red">sda1</font></b>), you will probably be wondering what to do with it now. Well, one option would be to keep it to the disk you used to save it in, store the disk, and use it whenever you need it. Another option would be to create a DVD you can use to restore this image.<br><br>
1560  Before, up to <b>Clonezilla-SysRescCD 2.6.0</b>, the process to create an automated restore DVD required entering command line prompt and writing some commands, that can be uncomfortable or even difficult for many people.<br><br>  Before, up to <b>Clonezilla-SysRescCD 2.6.0</b>, the process to create an automated restore DVD required entering command line prompt and writing some commands, that can be uncomfortable or even difficult for many people.<br><br>
1561    Later, a TUI option to create an automated recovery disc was added to <b>Clonezilla Live</b>, and <b>ocs-iso</b> script included in <b>Clonezilla-SysRescCD 3.1.0</b> and newer has a TUI too. Old command-line options are no longer supported. This page walks you through the creation of an automated restore DVD via TUI.<br><br>
1562  Later, a TUI option to create an automated recovery disc was added to <b>Clonezilla Live</b>, and <b>ocs-iso</b> script included in <b>Clonezilla-SysRescCD 3.1.0</b> and newer has a TUI too. Old command-line options are no longer supported. This page walks you through the creation of an automated restore DVD via TUI.<br><br>  You have to boot <b>Clonezilla Live</b>, using <b>Clonezilla-SysRescCD</b>.</p>
1563    <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>
1564  Assuming you have saved your image file <font color="Green"><b>win_img</b></font> in partition <font color="Green"><b>hdb4</b></font>, you have to boot <b>Clonezilla Live</b>, using <b>Clonezilla-SysRescCD</b>.</p>  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.5-17</b>
1565    </td></tr></table></div>
1566  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>  <H2><a name="dvd"></a>Creating the disk image <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>
1567  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.3-27</b>  <H3><a name="rui-0"></a>Clonezilla-SysRescCD starting screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1568  </td></tr></table></div>  <p>If you're fine with US keymap and English language (available languages are English, Spanish, French, Italian, Japanese and Chinese [both simplified and traditional]) or don't mind editing the boot parameters, just select <b>Clonezilla Live</b> at the starting screen and press ENTER. When the system comes up, it will load the program that will preform the backup. After that continue from <a href="#rui-4">this step</a>.</p>
1569    <p>If you need to change these settings, select one of the available <b>Clonezilla Live</b> menu entries, and press <font color="Green"><b>TAB</b></font>. The current boot parameters will be displayed.</p>
1570    <p>The default parameters for booting <b>Clonezilla Live</b> on a 1024x768 screen, are the following:</p>
1571    <p class="newcode">append initrd=/live/initrd1.img boot=live union=aufs<br>
1572    &nbsp;&nbsp;ocs_live_run="ocs-live-general" ocs_live_extra_param=""<br>
1573    &nbsp;&nbsp;ocs_prerun="/live/image/restorecd/prerun.normal" ocs_live_batch="no"<br>
1574  <H2><a name="dvd"></a>Creating the disk image <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>  &nbsp;&nbsp;ocs_lang="<font color="Red">en_US.UTF-8</font>" ocs_live_keymap="<font color="Red">NONE</font>" vga=791 nolocales</p>
1575    <p>By deleting the words in red, you instruct <b>Clonezilla Live</b> to ask you the values of these parameters. When the appropriate changes have been done (as shown bellow), just press <font color="Green"><b>ENTER</b></font> to boot.</p>
1576  <H3><a name="rui-0"></a>Clonezilla-SysRescCD starting screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  <p class="newcode">append initrd=/live/initrd1.img boot=live union=aufs<br>
1577    &nbsp;&nbsp;ocs_live_run="ocs-live-general" ocs_live_extra_param=""<br>
1578  <p>If you're fine with US keymap and English language (available languages are English, Spanish, French, Italian, Japanese and Chinese [both simplified and traditional]) or don't mind editing the boot parameters, just select <b>Clonezilla Live</b> at the starting screen and press ENTER. When the system comes up, it will load the program that will preform the backup. After that continue from <a href="#rui-4">this step</a>.</p>  &nbsp;&nbsp;ocs_prerun="/live/image/restorecd/prerun.normal" ocs_live_batch="no"<br>
1579    &nbsp;&nbsp;ocs_lang="" ocs_live_keymap="" vga=791 nolocales</p>
1580  <p>If you need to change these settings, select one of the available <b>Clonezilla Live</b> menu entries, and press <font color="Green"><b>TAB</b></font>. The current boot parameters will be displayed.</p>  </p>
1581    <H3><a name="rui-1"></a>Screen "Choose Language" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <p>The default parameters for booting <b>Clonezilla Live</b> on a 1024x768 screen, are the following:</p>  
   
 <p class="newcode">append initrd=/live/initrd1.img boot=live union=aufs<br>  
 &nbsp;&nbsp;ocs_live_run="ocs-live-general" ocs_live_extra_param=""<br>  
 &nbsp;&nbsp;ocs_prerun="/live/image/restorecd/prerun.normal" ocs_live_batch="no"<br>  
 &nbsp;&nbsp;ocs_lang="<font color="Red">en_US.UTF-8</font>" ocs_live_keymap="<font color="Red">NONE</font>" vga=791 nolocales</p>  
   
 <p>By deleting the words in red, you instruct <b>Clonezilla Live</b> to ask you the values of these parameters. When the appropriate changes have been done (as shown bellow), just press <font color="Green"><b>ENTER</b></font> to boot.</p>  
   
 <p class="newcode">append initrd=/live/initrd1.img boot=live union=aufs<br>  
 &nbsp;&nbsp;ocs_live_run="ocs-live-general" ocs_live_extra_param=""<br>  
 &nbsp;&nbsp;ocs_prerun="/live/image/restorecd/prerun.normal" ocs_live_batch="no"<br>  
 &nbsp;&nbsp;ocs_lang="" ocs_live_keymap="" vga=791 nolocales</p>  
 </p>  
   
 <H3><a name="rui-1"></a>Screen "Choose Language" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1582  <p><img src="images/backup-00.png"><br>  <p><img src="images/backup-00.png"><br>
1583  I select "<font color="Red"><b>en_US.UTF-8 English</b></font>" and press ENTER.</p>  I select "<font color="Red"><b>en_US.UTF-8 English</b></font>" and press ENTER.</p>
1584    <H3><a name="rui-2"></a>Screen "Configuring console-data" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-2"></a>Screen "Configuring console-data" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1585  <p><img src="images/backup-01.png"><br>  <p><img src="images/backup-01.png"><br>
1586  I select "<font color="Red"><b>Select keymap from full list</b></font>" and press ENTER. If you're using US keymap, the default option "<font color="Red"><b>Don't touch keymap</b></font>" is a better choice.</p>  I select "<font color="Red"><b>Select keymap from full list</b></font>" and press ENTER. If you're using US keymap, the default option "<font color="Red"><b>Don't touch keymap</b></font>" is a better choice.</p>
1587    <H3><a name="rui-3"></a>Screen "Configuring console-data" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-3"></a>Screen "Configuring console-data" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1588  <p><img src="images/backup-02.png"><br>  <p><img src="images/backup-02.png"><br>
1589  Because I haven't changed my keyboard, I select "<font color="Red"><b>pc / qwerty / Finnish / Standard / Standard</b></font>". Because you most likely use a different keyboard, choose the one you use.</p>  Because I haven't changed my keyboard, I select "<font color="Red"><b>pc / qwerty / Finnish / Standard / Standard</b></font>". Because you most likely use a different keyboard, choose the one you use.</p>
1590    <H3><a name="rui-4"></a>Screen "Start Clonezilla" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-4"></a>Screen "Start Clonezilla" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1591  <p><img src="images/backup-03.png"><br>  <p><img src="images/backup-03.png"><br>
1592  I select "<font color="Red"><b>Start Clonezilla</b></font>" and press ENTER.  I select "<font color="Red"><b>Start Clonezilla</b></font>" and press ENTER.
1593  </p>  </p>
1594    <H3><a name="rui-5"></a>Screen "Clonezilla" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-5"></a>Screen "Clonezilla" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1595  <p><img src="images/backup-04.png"><br>  <p><img src="images/backup-04.png"><br>
1596  I select "<font color="Red"><b>device-image</b></font>" and press ENTER.<br> <br>  I select "<font color="Red"><b>device-image</b></font>" and press ENTER.<br> <br>
1597  </p>  </p>
1598    <H3><a name="rui-6"></a>Screen "Mount clonezilla image directory" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1599  <H3><a name="rui-6"></a>Screen "Mount clonezilla image directory" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  <p>In this screen I can select the way the image file directory has been saved.
1600    Available options are local directory, remote directory through <b>ssh</b>, <b>samba</b> or <b>nfs</b> and <b>skip</b>, to use the previously used directory. More info about the image file can be found at section "<a href="clonezilla.html#about">About the Image file</a>".<br>
1601  <p>In this screen I can select the way the image file directory has been saved.  <br>
 Available options are local directory, remote directory through <b>ssh</b>, <b>samba</b> or <b>nfs</b> and <b>skip</b>, to use the previously used directory. More info about the image file can be found at section "<a href="clonezilla.html#about">About the Image file</a>".<br>  
 <br>  
1602  <img src="images/backup-05.png"><br>  <img src="images/backup-05.png"><br>
1603  I select "<font color="Red"><b>local_dev</b></font>" and press ENTER.  I select "<font color="Red"><b>local_dev</b></font>" and press ENTER.
1604  </p>  </p>
1605    <H3><a name="rui-7"></a>Next screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1606  <H3><a name="rui-7"></a>Next screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  <p>This is where I choose the location of the image file.<br><br>
   
 <p>This is where I choose the location of the image file.<br><br>  
1607  <img src="images/restore-06.png"><br>  <img src="images/restore-06.png"><br>
1608  I select partition <font color="Red"><b>hda1</b></font> and press ENTER.<br>  I select partition <font color="Red"><b>sda1</b></font> and press ENTER.<br>
1609  <br>  <br>
1610  <img src="images/backup-07.png"><br>  <img src="images/backup-07.png"><br>
1611  and then ENTER again.</p>  and then ENTER again.</p>
   
1612  <p><img src="images/restore-08.png"><br>  <p><img src="images/restore-08.png"><br>
1613  This screen displays the mounting result.<br>  This screen displays the mounting result.<br>
1614  As we can see, <font color="Red"><b>/dev/hda1</b></font> has been successfully mounted under <b>/tmp/local-dev</b>.</p>  As we can see, <font color="Red"><b>/dev/sda1</b></font> has been successfully mounted under <b>/tmp/local-dev</b>.</p>
1615    <H3><a name="rui-7a"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-7a"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1616  <p><img src="images/backup-09.png"><br>  <p><img src="images/backup-09.png"><br>
1617  I select <font color="Red"><b>Beginer mode</b></font> to accept the default restore options, which are used if the recovery disk is ever used. If you select <font color="Red"><b>Expert mode</b></font>, you can choose the options yourself. More details can be found <a href="clonezilla.html#restore-options" target="_blank">here</a>.</p>  I select <font color="Red"><b>Beginer mode</b></font> to accept the default restore options, which are used if the recovery disk is ever used. If you select <font color="Red"><b>Expert mode</b></font>, you can choose the options yourself. More details can be found <a href="clonezilla.html#restore-options" target="_blank">here</a>.</p>
1618    <H3><a name="rui-8"></a>Screen "Clonezilla: Select mode" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1619  <H3><a name="rui-8"></a>Screen "Clonezilla: Select mode" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  <p>Here I can select the desired operation.<br>
1620    <br>
 <p>Here I can select the desired operation.<br>  
 <br>  
1621  <img src="images/restore-10.png"><br>  <img src="images/restore-10.png"><br>
1622  I select "<font color="Red"><b>recovery-iso-zip</b></font>" and press ENTER.<br> <br></p>  I select "<font color="Red"><b>recovery-iso-zip</b></font>" and press ENTER.<br> <br></p>
1623    <H3><a name="rui-9"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-9"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1624  <p><img src="images/restore-11.png"><br>  <p><img src="images/restore-11.png"><br>
1625  In this screen I select the image folder. This partition contains only one image.</p>  In this screen I select the image folder. This partition contains only one image.</p>
1626    <H3><a name="rui-10"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-10"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1627  <p><img src="images/restore-12.png"><br>  <p><img src="images/restore-12.png"><br>
1628  Now I am asked to select which disk the image will be restored to, if the recovery disc is used. Because this image is a backup, I choose the same disk where the original data resides. If you're upgrading your hard drive, choose the new drive.</p>  Now I am asked to select which disk the image will be restored to, if the recovery disc is used. Because this image is a backup, I choose the same disk where the original data resides. If you're upgrading your hard drive, choose the new drive.</p>
1629    <H3><a name="rui-11"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-11"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1630  <p><img src="images/restore-13.png"><br>  <p><img src="images/restore-13.png"><br>
1631  In this screen I can select the language that the recovery disc uses. I choose "<font color="Red"><b>en_US.UTF-8</b></font>".</p>  In this screen I can select the language that the recovery disc uses. I choose "<font color="Red"><b>en_US.UTF-8</b></font>".</p>
1632    <H3><a name="rui-12"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-12"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1633  <p><img src="images/restore-14.png"><br>  <p><img src="images/restore-14.png"><br>
1634  This screen allows me to select the keymap that the recovery disc uses. Unfortunately, changing the keymap requires knowing where the keymap file resides in Debian GNU/Linux. Because I don't know it, I just press ENTER to accept US keymap.</p>  This screen allows me to select the keymap that the recovery disc uses. Unfortunately, changing the keymap requires knowing where the keymap file resides in Debian GNU/Linux. Because I don't know it, I just press ENTER to accept US keymap.</p>
1635    <H3><a name="rui-13"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-13"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1636  <p><img src="images/restore-15.png"><br>  <p><img src="images/restore-15.png"><br>
1637  I select "<font color="Red"><b>iso</b></font>" to create a CD/DVD disk image which I can burn to a recordable CD/DVD disc. The good thing about recordable discs is that overwriting the backup by accident is impossible. The "<font color="Red"><b>zip</b></font>" option creates a ZIP file which can be used to create a bootable pendrive or external hard drive.</p>  I select "<font color="Red"><b>iso</b></font>" to create a CD/DVD disk image which I can burn to a recordable CD/DVD disc. The good thing about recordable discs is that overwriting the backup by accident is impossible. The "<font color="Red"><b>zip</b></font>" option creates a ZIP file which can be used to create a bootable pendrive or external hard drive.</p>
   
1638  <p><img src="images/restore-16.png"><br>  <p><img src="images/restore-16.png"><br>
1639  Then the program will display the command that will be executed and will ask me to press ENTER.</p>  Then the program will display the command that will be executed and will ask me to press ENTER.</p>
1640    <H3><a name="rui-13a"></a>Screen "Excessive Image Size" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1641  <p><a name="dl-dvd"></a><img src="images/cust-menu-01.png"><br>  <p><img src="images/restore-16a.png"><br>
1642  Due to limitations of <b>mkisofs</b>, the script can't create a ISO file which is over 4,5 gigabytes in size. It causes problems if the size of your image is over 4,4 gigabytes. <b>Clonezilla-SysRescCD</b> contains a workaround that creates a ISO file that contains no image, so you can add the image manually later. This dialog asks if you want to do so. Note that if you see this dialog, you most likely need a dual layer DVD+R or Blu-ray disc to burn the image. <b>Growisofs</b> doesn't support multisession burning on dual layer DVD-R discs, so such disc can't be used either.</p>  You will see this screen if the image file you're about to create is larger than a single layer DVD. The screen warns that <b>mkisofs</b> or <b>genisoimage</b> (the programs which actually create the image) might be unable to process a disk image that big. However, even bigger problem is that you need a dual layer DVD or Blu-ray disc to burn the image.</p>
1643    <H3><a name="rui-14"></a>Screen "Customization section" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-14"></a>Screen "Customization section" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1644  <p><img src="images/cust-menu-02.png"><br>  <p><img src="images/cust-menu-02.png"><br>
1645  Now I am asked if I want to customize the boot menu of the disc. I answer "<font color="Red"><b>Yes</b></font>". If you don't want to customize the menu, continue from <a href="#rui-22">this step</a>.</p>  Now I am asked if I want to customize the boot menu of the disc. I answer "<font color="Red"><b>Yes</b></font>". If you don't want to customize the menu, continue from <a href="#rui-22">this step</a>.</p>
1646    <H3><a name="rui-15"></a>Screen "DVD Title" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-15"></a>Screen "DVD Title" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1647  <p><img src="images/cust-menu-03.png"><br>  <p><img src="images/cust-menu-03.png"><br>
1648  In this screen I select the title of the boot menu. I type "Home PC Restore DVD".</p>  In this screen I select the title of the boot menu. I type "Home PC Restore DVD".</p>
1649    <H3><a name="rui-16"></a>Screen "Menu Items Caption" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-16"></a>Screen "Menu Items Caption" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1650  <p><img src="images/cust-menu-04.png"><br>  <p><img src="images/cust-menu-04.png"><br>
1651  This screen allows me to select the caption for all menu items. I enter "Restore Win XP".</p>  This screen allows me to select the caption for all menu items. I enter "Restore Win XP".</p>
1652    <H3><a name="rui-17"></a>Screen "Boot delay" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-17"></a>Screen "Boot delay" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1653  <p><img src="images/cust-menu-05.png"><br>  <p><img src="images/cust-menu-05.png"><br>
1654  I press ENTER to accept the default delay of 30 seconds. It means that when a computer is booted from the restore disc, it waits 30 seconds before choosing the default option automatically. You may want to reduce this delay if, for example, your keyboard doesn't work in boot menu and you must wait until the delay ends.</p>  I press ENTER to accept the default delay of 30 seconds. It means that when a computer is booted from the restore disc, it waits 30 seconds before choosing the default option automatically. You may want to reduce this delay if, for example, your keyboard doesn't work in boot menu and you must wait until the delay ends.</p>
1655    <H3><a name="rui-18"></a>Screen "Default Boot Item" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-18"></a>Screen "Default Boot Item" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1656  <p><img src="images/cust-menu-06.png"><br>  <p><img src="images/cust-menu-06.png"><br>
1657  In this screen I can select the default option of the menu. Selecting one of the options that restore the image makes using the disc even easier, but also raises the risk that the image is restored accidentally. Another reason to select such option may be that your keyboard doesn't work in boot menu, preventing you from choosing any non-default option. I select the first option that restores the image using pixel dimensions of 1024*768.</p>  In this screen I can select the default option of the menu. Selecting one of the options that restore the image makes using the disc even easier, but also raises the risk that the image is restored accidentally. Another reason to select such option may be that your keyboard doesn't work in boot menu, preventing you from choosing any non-default option. I select the first option that restores the image using pixel dimensions of 1024*768.</p>
1658    <H3><a name="rui-19"></a>Screen "Boot Screen Image" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-19"></a>Screen "Boot Screen Image" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1659  <p><img src="images/cust-menu-07.png"><br>  <p><img src="images/cust-menu-07.png"><br>
1660  This screen allows me to select the background picture of the menu. Note that the picture must be in the same partition that contains the disk image, if you don't mind entering command line and mounting the right partition manually. I choose picture <b><font color="Green">mysplash.png</font></b> in the root of the partition. Because the partition has been mounted in <b>/home/partimag</b>, the full path of the picture is <b>/home/partimag/<font color="Green">mysplash.png</font></b>.</p>  This screen allows me to select the background picture of the menu. Note that the picture must be in the same partition that contains the disk image, if you don't mind entering command line and mounting the right partition manually. I choose picture <b><font color="Green">mysplash.png</font></b> in the root of the partition. Because the partition has been mounted in <b>/home/partimag</b>, the full path of the picture is <b>/home/partimag/<font color="Green">mysplash.png</font></b>.</p>
1661    <H3><a name="rui-20"></a>Screen "ISO Label" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-20"></a>Screen "ISO Label" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1662  <p><img src="images/cust-menu-08.png"><br>  <p><img src="images/cust-menu-08.png"><br>
1663  In this screen I can select the volume label of the disc. Volume label is the name of the disc you may see in various situations, for example in the notification you see when you insert the disc into your DVD writer. I type "Backup_52-2009_hdb".</p>  In this screen I can select the volume label of the disc. Volume label is the name of the disc you may see in various situations, for example in the notification you see when you insert the disc into your DVD writer. I type "Backup_52-2009_hdb".</p>
1664    <H3><a name="rui-21"></a>Screen "Publisher ID" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-21"></a>Screen "Publisher ID" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1665  <p><img src="images/cust-menu-09.png"><br>  <p><img src="images/cust-menu-09.png"><br>
1666  This is where I choose the publisher ID of the ISO file and the disc. Publisher ID means the person or company who created the disc. However, at least in GNU/Linux reading the publisher ID is, strictly speaking, a challenge. <a href="http://www.cyberciti.biz/faq/getting-volume-information-from-cds-iso-images/" target="_blank">Here</a> are instructions to read the publisher ID of a ISO file. I didn't find any working instructions to read the ID from the disc.</p>  This is where I choose the publisher ID of the ISO file and the disc. Publisher ID means the person or company who created the disc. However, at least in GNU/Linux reading the publisher ID is, strictly speaking, a challenge. <a href="http://www.cyberciti.biz/faq/getting-volume-information-from-cds-iso-images/" target="_blank">Here</a> are instructions to read the publisher ID of a ISO file. I didn't find any working instructions to read the ID from the disc.</p>
1667    <H3><a name="rui-22"></a>Starting the creation of the disk image [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
 <H3><a name="rui-22"></a>Starting the creation of the disk image [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  
   
1668  <p><img src="images/restore-17.png"><br>  <p><img src="images/restore-17.png"><br>
1669  After that, creation of the disk image begins. Note that no confirmation is asked it the disk image is small enough to fit to a CD.  After that, creation of the disk image begins. Note that no confirmation is asked it the disk image is small enough to fit to a CD.
1670  <br>  <br>
1671  <br>  <br>
1672  <img src="images/cust-menu-10.png">  <img src="images/restore-18.png"><br>
1673  <br>  When the disk image is successfully created, I must reboot in order to burn the disc because my DVD burner is still in use. <b>Clonezilla Live</b> can be loaded into computer memory during boot in order to be able to burn disc(s) within it. However, due to a known bug, the disk image can't be created if <b>Clonezilla Live</b> has been loaded into memory. (<a href="http://free.nchc.org.tw/clonezilla-live/stable/Known-issues-Clonezilla-live.txt" target="_blank">source</a>) Thus, I press <font color="Red"><b>1</b></font> and ENTER to reboot to another operating system and burn the image using graphical burning program. Follow <a href="restore-burn.html">this link</a> for instructions. If you've created a ZIP file, follow <a href="restore-burn.html#zip">this one</a> instead.</p>
 If you have <a href="#dl-dvd">above</a> enabled the workaround to create a ISO file without any image, you get the info screen, which explains the actions to be taken in order to burn the ISO file and add the iamge file to the DVD. A script file is also saved as <b>/tmp/burnISO</b>.<br>  
 <br>  
 <img src="images/restore-18.png"><br>  
 When the disk image is successfully created, I must reboot in order to burn the disc because my DVD burner is still in use. <b>Clonezilla Live</b> can be loaded into computer memory during boot in order to be able to burn disc(s) within it. However, due to a known bug, the disk image can't be created if <b>Clonezilla Live</b> has been loaded into memory. (<a href="http://free.nchc.org.tw/clonezilla-live/stable/Known-issues-Clonezilla-live.txt" target="_blank">source</a>) Thus, I press <font color="Red"><b>1</b></font> and ENTER to reboot to another operating system and burn the image using graphical burning program. For instructions, follow one of these links:<br>  
 <br>  
 <a href="restore-burn.html">If the ISO file contains the disk image</a><br>  
 <a href="restore-burn.html#dvd-noimage">If the ISO file contains no image</a><br>  
 <a href="restore-burn.html#zip">If you've created a ZIP file</a></p>  
   
   
   
1674  <a name="restore-burn-top"></a>  <a name="restore-burn-top"></a>
1675  <H2 style="font-size: 2em;"><a name="restore-burn-intro"></a>What to do with the disk image <span class="hideprint">[<a href="#restore-burn-top" title="go to top of the page">^</a>]</span></H2>  <H2 style="font-size: 2em;"><a name="restore-burn-intro"></a>What to do with the disk image <span class="hideprint">[<a href="#restore-burn-top" title="go to top of the page">^</a>]</span></H2>
1676  <p>The <a href="restore.html">previous page</a> contains partial instructions to create an automated recovery DVD. They're partial because they only tell how the disk image can be created, not what one should do with the image. Of course, partial instructions are not enough, but don't worry - this page is the other part.<br><br>  <p>The <a href="restore.html">previous page</a> contains partial instructions to create an automated recovery DVD. They're partial because they only tell how the disk image can be created, not what one should do with the image. Of course, partial instructions are not enough, but don't worry - this page is the other part.<br><br>
# Line 1712  This page walks through burning the disc Line 1679  This page walks through burning the disc
1679  In addition to a DVD, bootable pendrive or external hard drive can be created as well. If you want to do so, follow instructions <a href="#zip">below</a>.<br><br>  In addition to a DVD, bootable pendrive or external hard drive can be created as well. If you want to do so, follow instructions <a href="#zip">below</a>.<br><br>
1680  Before following these instructions, insert a writable DVD or Blu-ray disc to your burner.</p>  Before following these instructions, insert a writable DVD or Blu-ray disc to your burner.</p>
1681  <H2><a name="dvd"></a>Burning the disc <span class="hideprint">[<a href="#restore-burn-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="dvd"></a>Burning the disc <span class="hideprint">[<a href="#restore-burn-top" title="go to top of the page">^</a>]</span></H2>
1682  <H3><a name="dvd-image"></a>If the ISO file contains the disk image [<a href="#restore-burn-top" title="go to top of the page">^</a>]</H3>  <H3><a name="dvd-imgburn"></a>Using ImgBurn [<a href="#restore-burn-top" title="go to top of the page">^</a>]</H3>
 <H4><a name="dvd-imgburn"></a>Using ImgBurn [<a href="#restore-burn-top" title="go to top of the page">^</a>]</H4>  
1683  <p><a href="http://www.imgburn.com/" target="_blank">ImgBurn</a> is a lightweight but very feature-rich disc burning program. It only requires about two megabytes disk space and contains <a href="http://cynthia.ownit.nu/ImgBurn/guide_settings/settings01a.png" target="_blank">a lot of settings</a>. <b>ImgBurn</b> is closed-source freeware and - unfortunately - Windows-only software. I (Jyrki) personally use <b>ImgBurn</b> when burning discs within Windows.<br><br>  <p><a href="http://www.imgburn.com/" target="_blank">ImgBurn</a> is a lightweight but very feature-rich disc burning program. It only requires about two megabytes disk space and contains <a href="http://cynthia.ownit.nu/ImgBurn/guide_settings/settings01a.png" target="_blank">a lot of settings</a>. <b>ImgBurn</b> is closed-source freeware and - unfortunately - Windows-only software. I (Jyrki) personally use <b>ImgBurn</b> when burning discs within Windows.<br><br>
1684  Launch <b>ImgBurn</b> and press <b>Write image file to disc</b>. Select the disk image you just created.<br><br>  Launch <b>ImgBurn</b> and press <b>Write image file to disc</b>. Select the disk image you just created.<br><br>
1685  At the settings window, keep <b>Test Mode</b> disabled. I also recommend keeping the <b>Verify</b> option enabled. Verifying the integrity of the disc after burning requires time and doesn't prevent the disc from becoming a so-called coaster, but it allows you to know immediately if the burning attempt failed, so you can try burning the disc again.<br><br>  At the settings window, keep <b>Test Mode</b> disabled. I also recommend keeping the <b>Verify</b> option enabled. Verifying the integrity of the disc after burning requires time and doesn't prevent the disc from becoming a so-called coaster, but it allows you to know immediately if the burning attempt failed, so you can try burning the disc again.<br><br>
1686  Keep the number of copies as 1 (or increase it, if you really want multiple copies of the disc). Use your best judgment while choosing the burning speed: according to <a href="http://club.myce.com/f33/high-speed-vs-low-speed-burning-69698/" target="_blank">this forum thread</a> lowering the burning speed gives very mixed results in quality. I personally use ¾ of the maximum speed of the disc, for example 12x on a disc rated 16x.<br><br>  Keep the number of copies as 1 (or increase it, if you really want multiple copies of the disc). Use your best judgment while choosing the burning speed: according to <a href="http://club.myce.com/f33/high-speed-vs-low-speed-burning-69698/" target="_blank">this forum thread</a> lowering the burning speed gives very mixed results in quality. I personally use ¾ of the maximum speed of the disc, for example 12x on a disc rated 16x.<br><br>
1687  After choosing the settings, press the big picture at the bottom-left of the window. Don't do anything that requires much computer resources while burning, because doing so increases the likelihood of burning failure.<br><br>  After choosing the settings, press the big picture at the bottom-left of the window. Don't do anything that requires much computer resources while burning, because doing so increases the likelihood of burning failure.<br><br>
1688  That's it. You own now an automated recovery disc.</p>  That's it. You own now an automated recovery disc.</p>
1689  <H4><a name="dvd-k3b"></a>Using K3b [<a href="#restore-burn-top" title="go to top of the page">^</a>]</H4>  <H3><a name="dvd-k3b"></a>Using K3b [<a href="#restore-burn-top" title="go to top of the page">^</a>]</H3>
1690  <p><a href="http://k3b.plainblack.com/" target="_blank">K3b</a> (KDE Burn Baby Burn) is the disc burning program included in KDE Software Compilation. It comes with most, if not all, KDE-based GNU/Linux distributions. It can also be installed on other distributions, but I recommend <i>against</i> doing so - <b>K3b</b> requires KDE base packages to be installed, and it doesn't make much sense to install KDE base only for <b>K3b</b>.<br><br>  <p><a href="http://k3b.plainblack.com/" target="_blank">K3b</a> (KDE Burn Baby Burn) is the disc burning program included in KDE Software Compilation. It comes with most, if not all, KDE-based GNU/Linux distributions. It can also be installed on other distributions, but I recommend <i>against</i> doing so - <b>K3b</b> requires KDE base packages to be installed, and it doesn't make much sense to install KDE base only for <b>K3b</b>.<br><br>
1691  <img src="images/k3b-00.png"><br>  <img src="images/k3b-00.png"><br>
1692  I launch <b>K3b</b> and navigate to the folder where the disk image resides.<br><br>  I launch <b>K3b</b> and navigate to the folder where the disk image resides.<br><br>
# Line 1735  I click <b>Start</b> and the burning pro Line 1701  I click <b>Start</b> and the burning pro
1701  Because I enabled the <b>Verify written data</b> option, <b>K3b</b> starts verifying the integrity of the disc right after burning.<br><br>  Because I enabled the <b>Verify written data</b> option, <b>K3b</b> starts verifying the integrity of the disc right after burning.<br><br>
1702  <img src="images/k3b-05.png"><br>  <img src="images/k3b-05.png"><br>
1703  The burning attempt succeeded.<br><br>  The burning attempt succeeded.<br><br>
1704  <H3><a name="dvd-noimage"></a>If the ISO file contains no image [<a href="#restore-burn-top" title="go to top of the page">^</a>]</H3>  <img src="images/restore-20.png"><br>
1705  <p>If you have enabled the workaround to create a ISO file that contains no disk image (required if the size of the image is over 4,4 gigabytes), things become much more problematic. The ISO file and the image can't be burned to the disc simultaneously, they must be written one-by-one. That requires two burning sessions: the first for writing the ISO file to the disc and the second for adding the disk image. Many burning programs don't even support multisession burning at all. About the programs I've mentioned in this page: <b>K3b</b> supports multisession burning, <b>ImgBurn</b> doesn't.<br><br>  Here we can see the boot menu of the disc.</p>
 I didn't find any instructions for adding an additional file to a spesific directory by using <b>K3b</b>. Actually, I don't even know if that's possible at all. Thus, I recommend using <b>growisofs</b> for burning the disc if the workaround has been enabled, because <b>growisofs</b> allows adding any file to any directory. However, there's one more limitation: <b>growisofs</b> doesn't support multisession burning on dual layer DVD-R discs, so you must use dual layer DVD+R or Blu-ray disc. (<a href="http://fy.chalmers.se/~appro/linux/DVD+RW/-RW/#nomultisess" target="_blank">source</a>)<br><br>  
 <b>Growisofs</b> is a command-line program and a part of <b>dvd+rw-tools</b> that is installed on most GNU/Linux distributions. <b>Dvd+rw-tools</b> is Linux-only software, so if you use a competing operating system, you must boot into <b>SystemRescueCD</b> (graphical mode is not needed) in order to burn the disc.<br><br>  
 Open terminal and mount the partition that contains the image. The commands below must be run as root.</p>  
 <p class="newcode">mkdir /media/usb<br>  
 mount /dev/<font color="Green">sdc1</font> /media/usb</p>  
 <p><b>Note:</b> How a command can be run as root depends on the GNU/Linux distribution you use.  If it's Ubuntu or a distro based on it, simply put "<b>sudo</b>" above the command. For example, the latter of the above commands can be executed by typing "<b>sudo mount /dev/<font color="Green">sdc1</font> /media/usb</b>". If you're using <b>SystemRescueCD</b>, all commands are run as root, so you don't need to add any prefix to the commands.</p>  
 <p><b>Note:</b> In the command replace <b>/dev/<font color="Green">sdc1</font></b> with the partition where the disk image resides. It's the same partition you mounted as <b>/home/partimag</b> when creating the image.</p>  
 <p>Go to root of the partition:</p>  
 <p class="newcode">cd /media/usb</p>  
 <p>Burn the ISO file to the disc:</p>  
 <p class="newcode">growisofs -Z /dev/dvd=clonezilla-live-<font color="Green">Backup_5-2010_hdb</font>.iso</p>  
 <p><b>Note:</b> In the last command I have assumed your ISO file is <b>clonezilla-live-<font color="Green">Backup_5-2010_hdb</font>.iso</b>. You will have to replace this with the actual name of the file.</p>  
 <p><b>Note:</b> If your computer has multiple DVD drives, replace <b>/dev/dvd</b> with the name of your DVD writer.</p>  
 <p>The disc must be ejected because it's the only known way to force the drive to reread the disc. Do it:</p>  
 <p class="newcode">eject /dev/dvd</p>  
 <p><b>Note:</b> If your drive can't reload the disc, insert the disc back right after ejecting it.</p>  
 <p>Finally, add the image file to the disc:</p>  
 <p class="newcode">growisofs -M /dev/dvd -R -J -V "<font color="Green">Backup_5-2010_hdb</font>" --publisher "<font color="Green">Your Name</font>" -graft-points /<font color="Green">Backup_5-2010_hdb</font>/=/media/usb/<font color="Green">Backup_5-2010_hdb</font></p>  
 <p><b>Note:</b> In the command replace <b><font color="Green">Your Name</font></b> with anything you want to be the publisher ID of the disc. If you don't want the disc to have any publisher ID, run this command instead:</p>  
 <p class="newcode">growisofs -M /dev/dvd -R -J -V "<font color="Green">Backup_5-2010_hdb</font>" -graft-points /<font color="Green">Backup_5-2010_hdb</font>/=/media/usb/<font color="Green">Backup_5-2010_hdb</font></p>  
 <p><img src="images/restore-20.png"><br>Here we can see the boot menu of the disc.</p>  
1706  <H2><a name="zip"></a>ZIP file instructions <span class="hideprint">[<a href="#restore-burn-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="zip"></a>ZIP file instructions <span class="hideprint">[<a href="#restore-burn-top" title="go to top of the page">^</a>]</span></H2>
1707  <p>Often the image file is way too big to fit to even 8 GB DVD. Some people may also want to be able to overwrite the backup when it becomes outdated. In addition, netbooks don't have optical drives at all.</p>  <p>Often the image file is way too big to fit to even 8 GB DVD. Some people may also want to be able to overwrite the backup when it becomes outdated. In addition, netbooks don't have optical drives at all.</p>
1708  <p>One option is using recovery thumb drive or external hard drive instead of DVD. If the external HD is big enough, the disk image can be even over a terabyte in size. Recovery USB drive can also be used on netbooks and overwritten at will.</p>  <p>One option is using recovery thumb drive or external hard drive instead of DVD. If the external HD is big enough, the disk image can be even over a terabyte in size. Recovery USB drive can also be used on netbooks and overwritten at will.</p>
# Line 1765  mount /dev/<font color="Green">sdc1</fon Line 1710  mount /dev/<font color="Green">sdc1</fon
1710  <p>Before creating the disk image, make sure it is split to pieces of four gigabytes or less. It is split automatically if you use <font color="Red"><b>Beginner mode</b></font>, and if you use <font color="Red"><b>Expert mode</b></font>, you should already know how the splitting setting can be changed.</p>  <p>Before creating the disk image, make sure it is split to pieces of four gigabytes or less. It is split automatically if you use <font color="Red"><b>Beginner mode</b></font>, and if you use <font color="Red"><b>Expert mode</b></font>, you should already know how the splitting setting can be changed.</p>
1711  <H3><a name="zip-linux"></a>Using GNU/Linux [<a href="#restore-burn-top" title="go to top of the page">^</a>]</H3>  <H3><a name="zip-linux"></a>Using GNU/Linux [<a href="#restore-burn-top" title="go to top of the page">^</a>]</H3>
1712  <p>After creating the disk image and booting into GNU/Linux, make sure that the filesystem of the partition where you plan to put the disk image is FAT32. If you don't know the filesystem, open terminal and run this command as root:</p>  <p>After creating the disk image and booting into GNU/Linux, make sure that the filesystem of the partition where you plan to put the disk image is FAT32. If you don't know the filesystem, open terminal and run this command as root:</p>
1713  <p class="newcode">fdisk -l /dev/<font color="Green">sdc</font></p>  <p class="newcode">parted -l</p>
1714  <p><b>Note:</b> How a command can be run as root depends on the GNU/Linux distribution you use.  If it's Ubuntu or a distro based on it, simply put "<b>sudo</b>" above the command. For example, the above command can be executed by typing "<b>sudo fdisk -l /dev/<font color="Green">sdc</font></b>"</p>  <p><b>Note:</b> How a command can be run as root depends on the GNU/Linux distribution you use.  If it's Ubuntu or a distro based on it, simply put "<b>sudo</b>" above the command. For example, the above command can be executed by typing "<b>sudo parted -l</b>"</p>
 <p><b>Note:</b> In the command replace <b>/dev/<font color="Green">sdc</font></b> with the name of your USB disk.</p>  
1715  <p><b>Note:</b> The l in parameter <b>-l</b> is lowercase L, not number 1.</p>  <p><b>Note:</b> The l in parameter <b>-l</b> is lowercase L, not number 1.</p>
1716  <p>If your disk doesn't contain any FAT32 partition, but it contains a partition which is big enough and doesn't contain any important data, format the partition as FAT32. The command below needs root access too.</p>  <p>If your disk doesn't contain any FAT32 partition, but it contains a partition which is big enough and doesn't contain any important data, format the partition as FAT32. The command below needs root access too.</p>
1717  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>
1718  The command below erases all the data on the target partition.<br><br>Make sure you don't format a wrong partition by accident.  The command below erases all the data on the target partition.<br><br>Make sure you don't format a wrong partition by accident.
1719  </td></tr></table></div>  </td></tr></table></div>
1720  <p class="newcode">mkfs.vfat -F 32 /dev/<font color="Green">sdc1</font></p>  <p class="newcode">mkfs.vfat -F 32 /dev/<font color="Green">sdc1</font></p>
1721    <p><b>Note:</b> In the command replace <b>/dev/<font color="Green">sdc1</font></b> with the partition you wish to format.</p>
1722  <p>After formatting the partition or noticing that it was already FAT32, extract the ZIP archive to the root of the partition. Also these commands need root rights.</p>  <p>After formatting the partition or noticing that it was already FAT32, extract the ZIP archive to the root of the partition. Also these commands need root rights.</p>
1723  <p class="newcode">mount /dev/<font color="Green">sdc1</font> /media/usb<br>  <p class="newcode">mount /dev/<font color="Green">sdc1</font> /media/usb<br>
1724  unzip clonezilla-live-<font color="Green">Backup_5-2010_hdb</font>.zip -d /media/usb/</p>  unzip clonezilla-live-<font color="Green">Backup_5-2010_hdb</font>.zip -d /media/usb/</p>
# Line 1788  The latter of the commands below replace Line 1733  The latter of the commands below replace
1733  <H3><a name="zip-windows"></a>Using Windows [<a href="#restore-burn-top" title="go to top of the page">^</a>]</H3>  <H3><a name="zip-windows"></a>Using Windows [<a href="#restore-burn-top" title="go to top of the page">^</a>]</H3>
1734  <p>If the Windows version you use is not Vista or 7, you need to be logged in as administrator. If you're not, but you have access to an admin account, log out and then log again in as admin.</p>  <p>If the Windows version you use is not Vista or 7, you need to be logged in as administrator. If you're not, but you have access to an admin account, log out and then log again in as admin.</p>
1735  <p>If you don't have admin rights at all, boot into <b>SystemRescueCD</b> (you don't need graphical mode this time) and follow <a href="#zip-linux">the instructions for GNU/Linux</a>. In <b>SystemRescueCD</b> all commands are run as root, so you don't need to add any prefix to the commands.</p>  <p>If you don't have admin rights at all, boot into <b>SystemRescueCD</b> (you don't need graphical mode this time) and follow <a href="#zip-linux">the instructions for GNU/Linux</a>. In <b>SystemRescueCD</b> all commands are run as root, so you don't need to add any prefix to the commands.</p>
 <p>If you normally use Windows, you maybe don't know the name of your USB disk in GNU/Linux. If that's the case, don't specify any disk in the first command. It causes <b>fdisk</b> to tell about all disks in the computer and you should be able to identify both the right disk and the right partition.</p>  
1736  <p>After creating the disk image and booting into Windows, make sure that the filesystem of the partition where you plan to put the disk image is FAT32. If you don't know the filesystem, open <b>My Computer</b>, right-click the partition and select <b>Properties</b>. Then read the "File system" column. If there reads anything but FAT32, check other partitions of the disk too, if the disk contains multiple partitions. If you have a suitable FAT32 partition, continue from <a href="#extract">this step</a>.</p>  <p>After creating the disk image and booting into Windows, make sure that the filesystem of the partition where you plan to put the disk image is FAT32. If you don't know the filesystem, open <b>My Computer</b>, right-click the partition and select <b>Properties</b>. Then read the "File system" column. If there reads anything but FAT32, check other partitions of the disk too, if the disk contains multiple partitions. If you have a suitable FAT32 partition, continue from <a href="#extract">this step</a>.</p>
1737  <p>If your disk doesn't contain any FAT32 partition, but it contains a partition which is big enough and doesn't contain any important data, format the partition as FAT32.</p>  <p>If your disk doesn't contain any FAT32 partition, but it contains a partition which is big enough and doesn't contain any important data, format the partition as FAT32.</p>
1738  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>
# Line 2366  In the table, I have marked the options Line 2310  In the table, I have marked the options
2310  <H3><a name="boot-column"></a>Choosing the column <span class="hideprint">[<a href="#sysresccd-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="boot-column"></a>Choosing the column <span class="hideprint">[<a href="#sysresccd-top" title="go to top of the page">^</a>]</span></H3>
2311  <p>If you're accustomed to graphical environment, choose <b>Graphical Environment</b>. In <b>Graphical Environment</b> you're able to use graphical programs, like <b>GParted</b> and <b>Mozilla Firefox</b>. Terminals are also available, so using <b>Graphical Environment</b> doesn't prevent using command line. The only negative thing of <b>Graphical Environment</b> is that it slows booting process down a bit - and it's often just plain unneeded.<br>  <p>If you're accustomed to graphical environment, choose <b>Graphical Environment</b>. In <b>Graphical Environment</b> you're able to use graphical programs, like <b>GParted</b> and <b>Mozilla Firefox</b>. Terminals are also available, so using <b>Graphical Environment</b> doesn't prevent using command line. The only negative thing of <b>Graphical Environment</b> is that it slows booting process down a bit - and it's often just plain unneeded.<br>
2312  <br>  <br>
2313  Try <b>VESA</b>, if normal <b>Graphical Environment</b> doesn't work. <b>VESA</b> uses <b>Xvesa</b> graphical environment instead of <b>X.Org</b> that sometimes doesn't work. The drawbacks of <b>Xvesa</b> compared to <b>X.Org</b> are that <b>Xvesa</b> isn't optimized to any hardware (which means poorer performance) and <b>Xvesa</b> requires 32-bit kernel. Thus, if you use this option, do NOT choose 64-bit kernel, the combination leaves you at command line.<br>  Try <b>VESA</b>, if normal <b>Graphical Environment</b> doesn't work. <b>VESA</b> uses <b>Xvesa</b> graphical environment instead of <b>X.Org</b> that sometimes doesn't work. The drawback of <b>Xvesa</b> compared to <b>X.Org</b> is that <b>Xvesa</b> isn't optimized to any hardware, which means poorer performance.<br>
2314  <br>  <br>
2315  If you're accustomed to command line and know already that you're not going to use any graphical program, choose one of the normal options (just below "System Rescue CD Menu"). Booting to command line is a bit faster process than booting to graphical environment, and you can start X manually later.<br>  If you're accustomed to command line and know already that you're not going to use any graphical program, choose one of the normal options (just below "System Rescue CD Menu"). Booting to command line is a bit faster process than booting to graphical environment, and you can start X manually later.<br>
2316  <br>  <br>
# Line 2376  You need the option <b>To RAM</b> if you Line 2320  You need the option <b>To RAM</b> if you
2320  <H3><a name="boot-row"></a>Choosing the row (kernel) <span class="hideprint">[<a href="#sysresccd-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="boot-row"></a>Choosing the row (kernel) <span class="hideprint">[<a href="#sysresccd-top" title="go to top of the page">^</a>]</span></H3>
2321  <p>After having chosen the column of the above table, you still have three options. Now you need to choose the kernel.<br>  <p>After having chosen the column of the above table, you still have three options. Now you need to choose the kernel.<br>
2322  <br>  <br>
2323  The optimal kernel depends on the processor of your computer. If it's an IA-32 processor, like Intel Pentium 4 or AMD Athlon XP, you should choose <b>32-bit kernel</b>, because <b>64-bit kernel</b> doesn't work at all. If you have a x86-64 processor, like AMD Athlon 64 or Intel Core 2, you can choose any kernel - the processor can run all of them. <b>64-bit kernel</b> should be preferred, because it allows chrooting on an existing GNU/Linux partition containing 64-bit programs. Note, though, that you can't use <b>64-bit kernel</b> with <b>VESA</b> option.</br>  The optimal kernel depends on the processor of your computer. If it's an IA-32 processor, like Intel Pentium 4 or AMD Athlon XP, you should choose <b>32-bit kernel</b>, because <b>64-bit kernel</b> doesn't work at all. If you have a x86-64 processor, like AMD Athlon 64 or Intel Core 2, you can choose any kernel - the processor can run all of them. <b>64-bit kernel</b> should be preferred, because it allows chrooting on an existing GNU/Linux partition containing 64-bit programs.</br>
2324  <br>  <br>
2325  If you don't know your processor architecture, try <b>64-bit kernel</b>. If your processor architecture is IA-32, you'll see the following error message:</p>  If you don't know your processor architecture, try <b>64-bit kernel</b>. If your processor architecture is IA-32, you'll see the following error message:</p>
2326  <p class="newcode">This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot - please use a kernel appropriate for your CPU.</p>  <p class="newcode">This kernel requires an x86-64 CPU, but only detected an i686 CPU. Unable to boot - please use a kernel appropriate for your CPU.</p>
# Line 2430  This page contains some theory about par Line 2374  This page contains some theory about par
2374  While partitioning, an user error or a bug can damage your partitions.<br><br>Creating a disk image of the disk to be<br>partitioned beforehand is highly recommended.  While partitioning, an user error or a bug can damage your partitions.<br><br>Creating a disk image of the disk to be<br>partitioned beforehand is highly recommended.
2375  </td></tr></table></div>  </td></tr></table></div>
2376  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>
2377  The following pressentation has been made using<br><b>SystemRescueCD v 1.4.0</b>  The following pressentation has been made using<br><b>SystemRescueCD v 1.5.8</b>
2378  </td></tr></table></div>  </td></tr></table></div>
2379  <H2><a name="theory"></a>Some theory <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="theory"></a>Some theory <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H2>
2380  <H3><a name="partitions-partition"></a>What is a partition? <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="partitions-partition"></a>What is a partition? <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>
# Line 2438  The following pressentation has been mad Line 2382  The following pressentation has been mad
2382  <p>In Windows, a one-partition hard disk is labelled the "C:" drive ("A:" and "B:" are typically reserved for diskette drives). A two-partition hard drive would typically contain "C:" and "D:" drives. (CD-ROM drives typically are assigned the last letter in whatever sequence of letters have been used as a result of hard disk formatting, or typically with a two-partition, the "E:" drive.).</p>  <p>In Windows, a one-partition hard disk is labelled the "C:" drive ("A:" and "B:" are typically reserved for diskette drives). A two-partition hard drive would typically contain "C:" and "D:" drives. (CD-ROM drives typically are assigned the last letter in whatever sequence of letters have been used as a result of hard disk formatting, or typically with a two-partition, the "E:" drive.).</p>
2383  <p>In UNIX-based systems, a partition is used to host the / (root) file system, and optionally the /opt, /usr and /home file systems. There may also be a swap partition, which doesn't host any file system.</p>  <p>In UNIX-based systems, a partition is used to host the / (root) file system, and optionally the /opt, /usr and /home file systems. There may also be a swap partition, which doesn't host any file system.</p>
2384  <p>Each operatin system provides some kind of tool to create and manage partitions. Examples of such tools are <b>fdisk</b> in DOS/Windows, <b>fdisk</b>, <b>sfdisk</b> and <b>parted</b> in Linux, etc.</p>  <p>Each operatin system provides some kind of tool to create and manage partitions. Examples of such tools are <b>fdisk</b> in DOS/Windows, <b>fdisk</b>, <b>sfdisk</b> and <b>parted</b> in Linux, etc.</p>
2385  <H3><a name="partitions-extended"></a>What is the difference between primary, extended and logical partitions? <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H2>  <H3><a name="partitions-extended"></a>What is the difference between primary, extended and logical partitions? <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>
2386  <p>Information about partitions is saved in so-called partition table in Master Boot Record. MBR itself is only 512 bytes in size, and only 64 bytes are reserved for partition table. That's not enough, and there are many workarounds to bypass limitations caused by the size, for example <a href="http://en.wikipedia.org/wiki/Logical_block_addressing#LBA.2C_ATA_devices_and_Enhanced_BIOS" target="_blank">logical block addressing</a>. Extended partitions are another workaround.</p>  <p>Information about partitions is saved in so-called partition table in Master Boot Record. MBR itself is only 512 bytes in size, and only 64 bytes are reserved for partition table. That's not enough, and there are many workarounds to bypass limitations caused by the size, for example <a href="http://en.wikipedia.org/wiki/Logical_block_addressing#LBA.2C_ATA_devices_and_Enhanced_BIOS" target="_blank">logical block addressing</a>. Extended partitions are another workaround.</p>
2387  <p>Partition table can only store information about four partitions. If one has, for example, two GNU/Linux distributions on the same disk, both of them having separate root partitions, shared /home and shared swap, the partition number limit has been hit already.</p>  <p>Partition table can only store information about four partitions. If one has, for example, two GNU/Linux distributions on the same disk, both of them having separate root partitions, shared /home and shared swap, the partition number limit has been hit already.</p>
2388  <p>A partition that is mentioned in the partition table is called primary partition. Because of the limit, one disk can only contain 1-4 primary partitions.</p>  <p>A partition that is mentioned in the partition table is called primary partition. Because of the limit, one disk can only contain 1-4 primary partitions.</p>
2389  <p>An extended partition fixes the problem simply by containing more boot records, called Extended Boot Records (EBR). Each EBR contains information about one logical partition and, if the extended partition contains multiple logical partitions, link to the next EBR. Thus, an extended partition can contain unlimited amount of logical partitions.</p>  <p>An extended partition fixes the problem simply by containing more boot records, called Extended Boot Records (EBR). Each EBR contains information about one logical partition and, if the extended partition contains multiple logical partitions, link to the next EBR. Thus, an extended partition can contain unlimited amount of logical partitions.</p>
2390  <p>Extended partition contains only EBRs and logical partitions (and maybe unallocated space). Extended partition doesn't contain any filesystem and files can't be stored in it. Of course, logical partition can contain any filesystem (or be unformatted).</p>  <p>Extended partition contains only EBRs and logical partitions (and maybe unallocated space). Extended partition doesn't contain any filesystem and files can't be stored in it. Of course, logical partition can contain any filesystem (or be unformatted).</p>
2391  <p>Extended partition itself must be primary partition: an extended partition can't be within another extended partition. In addition, a disk can contain only one extended partition.</p>  <p>Logical partitions can always be used for storing data: any operating system can see logical partitions. GNU/Linux supports both multiple primary extended partitions and extended partitions within each other, while Windows supports only the latter. GNU/Linux distributions can be installed to logical partitions as well, but Windows requires a lot of tweaking. See <a href="http://www.goodells.net/multiboot/index.htm" target="_blank">this outdated guide</a>.</p>
 <p>Logical partitions can always be used for storing data: any operating system can see logical partitions. GNU/Linux distributions can be installed to logical partitions as well, but Windows requires a lot of tweaking. See <a href="http://www.goodells.net/multiboot/index.htm" target="_blank">this outdated guide</a>.</p>  
2392  <H3><a name="partitions-lvm"></a>What is LVM? <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="partitions-lvm"></a>What is LVM? <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>
2393  <p>LVM means "Logical Volume Manager". It allows creating volume groups on top of hard drives and logical volumes within volume groups. Logical volumes are NOT the same thing as logical partitions!</p>  <p>LVM means "Logical Volume Manager". It allows creating volume groups on top of hard drives and logical volumes within volume groups. Logical volumes are NOT the same thing as logical partitions!</p>
2394  <p>Volume groups can be created very flexibly: a volume group can allocate, for example, the first half of the first hard drive and the second half of the third drive. One can even create a massive volume group containing all storage he/she has.</p>  <p>Volume groups can be created very flexibly: a volume group can allocate, for example, the first half of the first hard drive and the second half of the third drive. One can even create a massive volume group containing all storage he/she has.</p>
# Line 2462  The following pressentation has been mad Line 2405  The following pressentation has been mad
2405  <H3><a name="partitions-journaling"></a>What is journaling? <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="partitions-journaling"></a>What is journaling? <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>
2406  <p>Ideally, data in a partition never corrupts. But, in the real world, there are power failures and operating system freezes. And if a computer is forcefully shut down while something is written to the drive, the write operation can't be finished. That can damage the filesystem and destroy any files in the partition.</p>  <p>Ideally, data in a partition never corrupts. But, in the real world, there are power failures and operating system freezes. And if a computer is forcefully shut down while something is written to the drive, the write operation can't be finished. That can damage the filesystem and destroy any files in the partition.</p>
2407  <p>Journaling partially fixes that problem by writing most changes to the disk twice: first to a special area called journal and, after that, to the filesystem itself. If power is lost while writing to the journal was in progress, the partial change is just ignored and never committed to the filesystem itself. If power failure or OS freeze happened while writing to filesystem itself, the write operation is finished by using the information in journal.</p>  <p>Journaling partially fixes that problem by writing most changes to the disk twice: first to a special area called journal and, after that, to the filesystem itself. If power is lost while writing to the journal was in progress, the partial change is just ignored and never committed to the filesystem itself. If power failure or OS freeze happened while writing to filesystem itself, the write operation is finished by using the information in journal.</p>
2408  <p>Journaling helps most of the time when the computer has been forcefully shut down, but not always. Due to performance reasons, only some write operations are written to the journal, mostly the biggest operations. Of course, journaling doesn't help if that particular operation that was in progress while power was lost didn't go through the journal. Journaling also doesn't protect from everything: for example, using ext4 filesystem in conjuction with programs that write a lot of files in a short time can result in <a href="http://www.h-online.com/open/news/item/Possible-data-loss-in-Ext4-740467.html" target="_blank">massive data loss</a>, regardless if journaling is enabled or not.</p>  <p>Journaling is always a trade-off between reliability and performance. In fact, the ext3 and ext4 filesystems support multiple journaling modes in order to allow the user to choose the optimal compromise. The most popular choices are <b>ordered</b> and <b>writeback</b>.</p>
2409  <p>In addition, journaling reduces performance. It causes more writes to the disk. That's not a big problem on mechanical hard drives, but on SSDs (Solid State Drives) and thumb drives write speed is much slower than read speed. They also have a limited number of writing cycles, so journaling reduces their lifetime. I (Jyrki) actually use ext2 and FAT32 filesystems on my external SSD drive because they do NOT support journaling at all.</p>  <p>Both modes only write metadata changes to the journal before committing them: data itself is written directly to the main filesystem. The difference between the modes is that <b>ordered</b> mode guarantees that the data is written before the change is marked as committed. The difference may sound small, but in some cases <b>ordered</b> mode causes horrible performance. In Linux 2.6.30, the default journaling mode was changed to <b>writeback</b> - and it was quickly found out that <b>writeback</b> mode may cause massive data loss. See <a href="http://forums.raiden.net/viewtopic.php?p=155912#155912" target="_blank">this forum post</a> for details. Most GNU/Linux distributions are now using <b>ordered</b> mode as the default again.</p>
2410    <p>In addition, on SSDs (Solid State Drives) and thumb drives write speed is much slower than read speed. They also have a limited number of writing cycles, so journaling reduces their lifetime. Thus, I (Jyrki) recommend against using journaling fileystems on such drives.</p>
2411  <H3><a name="partitions-filesystems"></a>What are the differences between most popular filesystems? <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="partitions-filesystems"></a>What are the differences between most popular filesystems? <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>
2412  <p>The following table quickly describes the most important differences between them.</p>  <p>The following table quickly describes the most important differences between them.</p>
2413  <table border="1">  <table border="1">
# Line 2516  The following pressentation has been mad Line 2460  The following pressentation has been mad
2460    </tr>    </tr>
2461      <tr>      <tr>
2462      <th>ext4</th>      <th>ext4</th>
2463      <td style="background-color: rgb(255,0,0)">No</td>      <td style="background-color: rgb(255,0,0)">No***</td>
2464          <td style="background-color: rgb(0,255,0)">Native</td>          <td style="background-color: rgb(0,255,0)">Native</td>
2465          <td style="background-color: rgb(255,127,0)">16 GB-16 TB*</td>          <td style="background-color: rgb(255,127,0)">16 GB-16 TB*</td>
2466          <td style="background-color: rgb(0,255,0)">Yes</td>          <td style="background-color: rgb(0,255,0)">Yes</td>
# Line 2524  The following pressentation has been mad Line 2468  The following pressentation has been mad
2468    </tr>    </tr>
2469      <tr>      <tr>
2470      <th>exFAT</th>      <th>exFAT</th>
2471      <td style="background-color: rgb(127,255,0)">Native (Vista/7)**</td>      <td style="background-color: rgb(127,255,0)">Built-in (Vista/7)**</td>
2472          <td style="background-color: rgb(255,0,0)">No</td>          <td style="background-color: rgb(255,127,0)">3rd party driver</td>
2473          <td style="background-color: rgb(0,255,0)">64 ZB</td>          <td style="background-color: rgb(0,255,0)">64 ZB</td>
2474          <td style="background-color: rgb(255,0,0)">No</td>          <td style="background-color: rgb(255,0,0)">No</td>
2475          <td style="background-color: rgb(0,255,0)">Yes</td>          <td style="background-color: rgb(0,255,0)">Yes</td>
2476    </tr>    </tr>
2477  </table>  </table>
2478  <p>* Depends on cluster size<br>  <p>* Depends on cluster size<br>
2479  ** <a href="http://support.microsoft.com/kb/955704" target="_blank">This update</a> adds exFAT support to Windows XP</p>  ** <a href="http://support.microsoft.com/kb/955704" target="_blank">This update</a> adds exFAT support to Windows XP<br>
2480    *** <a href="http://ext2read.blogspot.com/" target="_blank">Ext2read</a> makes accessing ext4 partitions possible, but it's not a driver and the access is read-only</p>
2481  <p>Operating system support:</p>  <p>Operating system support:</p>
2482  <ul>  <ul>
2483  <li>"Native" means that the kernel supports the filesystem and the OS can boot from a partition using that FS.</li>  <li>"Native" means that the kernel supports the filesystem and the OS can boot from a partition using that FS.</li>
2484  <li>"Built-in" means that the kernel supports the filesystem, but booting from a partition containing such FS is very difficult.</li>  <li>"Built-in" means that the kernel supports the filesystem, but booting from a partition containing such FS is very difficult.</li>
2485  <li>"Driver included" means that ntfs-3g (the driver that adds NTFS support to Linux) comes with most GNU/Linux distributions.</li>  <li>"Driver included" means that ntfs-3g (the driver that adds NTFS support to Linux) comes with most GNU/Linux distributions.</li>
2486  <li>"3rd party driver" means that drivers to add filesystem support are available, but must be downloaded and installed separately. The drivers are <a href="http://www.fs-driver.org" target="_blank">Ext2 IFS</a> and <a href="http://www.ext2fsd.com" target="_blank">Ext2fsd</a>.</li>  <li>"3rd party driver" means that drivers to add filesystem support are available, but must be downloaded and installed separately. The ext2/3 drivers are <a href="http://www.fs-driver.org" target="_blank">Ext2 IFS</a> and <a href="http://www.ext2fsd.com" target="_blank">Ext2fsd</a> and the exFAT driver is <a href="http://code.google.com/p/exfat/" target="_blank">exfat</a>.</li>
2487  <li>"No" means that there is no way to use the filesystem within the operating system.</li>  <li>"No" means that there is no way to get read-write filesystem support.</li>
2488  </ul>  </ul>
2489  <H2><a name="filesystems"></a>Filesystems <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="filesystems"></a>Filesystems <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H2>
2490  <p>This section contains more information about most popular filesystems.</p>  <p>This section contains more information about most popular filesystems.</p>
# Line 2547  The following pressentation has been mad Line 2492  The following pressentation has been mad
2492  <p>The initial version of FAT (File Allocation Table), now referred as FAT12, was designed for floppy disks. A FAT12 partition can only be up to 32 megabytes in size. After that, PCs equipped with hard drives were introcuded by IBM and the sizes of hard drives began growing. Microsoft answered the need by developing first initial FAT16 and then final FAT16.</p>  <p>The initial version of FAT (File Allocation Table), now referred as FAT12, was designed for floppy disks. A FAT12 partition can only be up to 32 megabytes in size. After that, PCs equipped with hard drives were introcuded by IBM and the sizes of hard drives began growing. Microsoft answered the need by developing first initial FAT16 and then final FAT16.</p>
2493  <p>FAT16 partition can be up to two gigabytes in size. In the middle of 1990s, that limit was becoming a problem. Microsoft pushed the limit up by updating FAT again.</p>  <p>FAT16 partition can be up to two gigabytes in size. In the middle of 1990s, that limit was becoming a problem. Microsoft pushed the limit up by updating FAT again.</p>
2494  <p>FAT32 was first introduced with Windows 95 OSR2. Windows 98, Windows Me, Windows 2000 and newer support FAT32 too. Linux kernel has supported FAT32 almost as long as Windows, but booting GNU/Linux from FAT32 partition is difficult and actually requires DOS to be installed in the partition as well. (<a href="http://en.wikipedia.org/wiki/FAT_filesystem_and_Linux#Installing_Linux_on_and_booting_it_from_FAT_volumes_using_umsdos" target="_blank">more information</a>)</p>  <p>FAT32 was first introduced with Windows 95 OSR2. Windows 98, Windows Me, Windows 2000 and newer support FAT32 too. Linux kernel has supported FAT32 almost as long as Windows, but booting GNU/Linux from FAT32 partition is difficult and actually requires DOS to be installed in the partition as well. (<a href="http://en.wikipedia.org/wiki/FAT_filesystem_and_Linux#Installing_Linux_on_and_booting_it_from_FAT_volumes_using_umsdos" target="_blank">more information</a>)</p>
2495  <p>FAT32 partition can be up to two terabytes in size. As of now (March 2010), there are hard drives that hit the limit, but don't exceed it. A single file within FAT32 partition can be up to four gigabytes in size.</p>  <p>FAT32 partition can be up to two terabytes in size. As of now (July 2010), there are hard drives that hit the limit, but don't exceed it. A single file within FAT32 partition can be up to four gigabytes in size.</p>
2496  <p>Because FAT32 is, in the end, based on FAT12, it has very few features. It doesn't support file permissions, hard/symbolic links, encryption, compression, alternative data streams, journaling... It lacks support for nearly anything that defines a modern filesystem. However, due to very few features, FAT32 is very fast filesystem if it's not fragmented or on a Flash-based drive. Mind you, FAT32 fragments very fast.</p>  <p>Because FAT32 is, in the end, based on FAT12, it has very few features. It doesn't support file permissions, hard/symbolic links, encryption, compression, alternative data streams, journaling... It lacks support for nearly anything that defines a modern filesystem. However, due to very few features, FAT32 is very fast filesystem if it's not fragmented or on a Flash-based drive. Mind you, FAT32 fragments very fast.</p>
2497  <p>Due to excellent operating system support, I recommend FAT32 for storing files which should be accessible in both Windows and GNU/Linux. FAT32 is also a good filesystem on Solid State Drives and thumb drives due to its performance.</p>  <p>Due to excellent operating system support, I recommend FAT32 for storing files which should be accessible in both Windows and GNU/Linux. FAT32 is also a good filesystem on Solid State Drives and thumb drives due to its performance.</p>
2498  <H3><a name="partitions-ext2"></a>ext2 <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="partitions-ext2"></a>ext2 <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>
# Line 2557  The following pressentation has been mad Line 2502  The following pressentation has been mad
2502  <p>The best property of ext2 is extensibility. The superblock contains information about which version the filesystem is (ext2, ext3 or ext4) and which extensions and features are in use. By using these pieces of information, the operating system or driver can decide whether or not mounting the partition is safe. That's the most important reason why most GNU/Linux distributions still use successors of ext2 as default filesystems.</p>  <p>The best property of ext2 is extensibility. The superblock contains information about which version the filesystem is (ext2, ext3 or ext4) and which extensions and features are in use. By using these pieces of information, the operating system or driver can decide whether or not mounting the partition is safe. That's the most important reason why most GNU/Linux distributions still use successors of ext2 as default filesystems.</p>
2503  <p>Depending on cluster size, ext2 partition can be up to 2-32 terabytes in size. File size limit is 16 GB-2 TB.</p>  <p>Depending on cluster size, ext2 partition can be up to 2-32 terabytes in size. File size limit is 16 GB-2 TB.</p>
2504  <p>Ext2 supports file permissions, both hard and symbolic links and extended file attributes. Encryption, compression and journaling are unsupported.</p>  <p>Ext2 supports file permissions, both hard and symbolic links and extended file attributes. Encryption, compression and journaling are unsupported.</p>
2505  <p>Due to lack of journaling support and existence of Windows drivers, I recommend using ext2 if you're going to install GNU/Linux on a SSD drive and want to be able to access files within Windows too. In fact, that's exactly the setup I have.</p>  <p>Due to lack of journaling support and existence of Windows drivers, I recommend using ext2 if you're going to install GNU/Linux on a SSD drive and want to be able to access files within Windows too.</p>
2506  <p>However, lack of journaling support is the worst limitation of ext2. And what was done in order to get rid of the limitation?</p>  <p>However, lack of journaling support is the worst limitation of ext2. And what was done in order to get rid of the limitation?</p>
2507  <H3><a name="partitions-ext3"></a>ext3 <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="partitions-ext3"></a>ext3 <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>
2508  <p>Ext3, the successor of ext2, was introduced in Linux kernel on November 2001. It supports journaling, can be grown online and indexes large directories.</p>  <p>Ext3, the successor of ext2, was introduced in Linux kernel on November 2001. It supports journaling, can be grown online and optionally indexes large directories.</p>
2509  <p>Ext2 IFS and Ext2fsd can mount ext3 partition as ext2 if the journal is empty. (If it's not, something is wrong - journal is always emptied when the partition is unmounted or the computer is shut down.) Thus, ext3 support under Windows is just as good/bad as ext2 support.</p>  <p>Ext2 IFS and Ext2fsd can mount ext3 partition as ext2 if the journal is empty. (If it's not, something is wrong - journal is always emptied when the partition is unmounted or the computer is shut down.) Thus, ext3 support under Windows is just as good/bad as ext2 support.</p>
2510  <p>Partition and file size limits are the same as in ext2: partition size limit is 2-32 TB and file size limit 16 GB-2 TB, depending on cluster size.</p>  <p>Partition and file size limits are the same as in ext2: partition size limit is 2-32 TB and file size limit 16 GB-2 TB, depending on cluster size.</p>
2511  <p>Due to journaling support and existence of Windows drivers, ext3 is a good choice if you're going to install GNU/Linux on a mechanical hard drive and want to be able to access files within Windows.</p>  <p>Due to journaling support and existence of Windows drivers, ext3 is a good choice if you're going to install GNU/Linux on a mechanical hard drive and want to be able to access files within Windows.</p>
# Line 2568  The following pressentation has been mad Line 2513  The following pressentation has been mad
2513  <p>Linux kernel support for ext4, the successor of ext3, was marked stable code on October 2008. Ext4 contains multiple performance and stability improvements over ext3.</p>  <p>Linux kernel support for ext4, the successor of ext3, was marked stable code on October 2008. Ext4 contains multiple performance and stability improvements over ext3.</p>
2514  <p>The most important new feature is extents. An extent is a contiguous area of storage that has been reserved for a file. When a process starts to write to a file, the whole extent is allocated even before the write operation begins. The idea is that even if the file is larger than expected, it doesn't fragment if it doesn't exceed the size of the extent.</p>  <p>The most important new feature is extents. An extent is a contiguous area of storage that has been reserved for a file. When a process starts to write to a file, the whole extent is allocated even before the write operation begins. The idea is that even if the file is larger than expected, it doesn't fragment if it doesn't exceed the size of the extent.</p>
2515  <p>Another important improvement is larger partition size limit: an ext4 partition can be even one exabyte in size. (An exabyte is a million terabytes.) In addition, a directory within an ext4 partition can contain up to 64 000 subdirectories (instead of 32 000, as in ext2/3) and timestamps are much more accurate. The file size limit is 16 GB-16 TB, depending on cluster size.</p>  <p>Another important improvement is larger partition size limit: an ext4 partition can be even one exabyte in size. (An exabyte is a million terabytes.) In addition, a directory within an ext4 partition can contain up to 64 000 subdirectories (instead of 32 000, as in ext2/3) and timestamps are much more accurate. The file size limit is 16 GB-16 TB, depending on cluster size.</p>
2516  <p>Unfortunately, Ext2 IFS and Ext2Fsd don't support ext4 and are unable to mount ext4 partition if extents are enabled. They can be disabled, but other improvements of ext4 aren't that important for most people - using ext2 or ext3 is just easier.</p>  <p>Unfortunately, Ext2 IFS and Ext2Fsd don't support ext4 and are unable to mount ext4 partition if extents are enabled. They can be disabled, but other improvements of ext4 aren't that important for most people - using ext2 or ext3 is just easier. It is also possible to keep extents enabled and browse the partition using <a href="http://ext2read.blogspot.com/" target="_blank">Ext2read</a>, but Ext2read doesn't allow the user to write to the partition.</p>
2517  <p>Due to its features, ext4 is a good filesystem on computers that only have GNU/Linux installed. Because journaling can be disabled, it is suitable for Solid State Drives and thumb drives too.</p>  <p>Due to its features, ext4 is a good filesystem on computers that only have GNU/Linux installed. Because journaling can be disabled, it is suitable for Solid State Drives and thumb drives too.</p>
2518  <H3><a name="partitions-ntfs"></a>NTFS <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="partitions-ntfs"></a>NTFS <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>
2519  <p>At the end of 1980s, IBM and Microsoft were developing OS/2 operating system. Both companies expected OS/2 1.1, released on 1988, to be the first popular operating system having a GUI, Presentation Manager. Even though it didn't become too popular during its first years, Microsoft didn't complain: Windows 2 didn't sell any better.</p>  <p>At the end of 1980s, IBM and Microsoft were developing OS/2 operating system. Both companies expected OS/2 1.1, released on 1988, to be the first popular operating system having a GUI, Presentation Manager. Even though it didn't become too popular during its first years, Microsoft didn't complain: Windows 2 didn't sell any better.</p>
# Line 2581  The following pressentation has been mad Line 2526  The following pressentation has been mad
2526  <H3><a name="partitions-exfat"></a>exFAT <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="partitions-exfat"></a>exFAT <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H3>
2527  <p>NTFS is a great filesystem, but due to its complexity and journaling, it's not suitable for Flash-based drives. Even Microsoft itself has recommended using FAT32 on removable Flash media.</p>  <p>NTFS is a great filesystem, but due to its complexity and journaling, it's not suitable for Flash-based drives. Even Microsoft itself has recommended using FAT32 on removable Flash media.</p>
2528  <p>However, FAT32 only allows files up to four gigabytes in size. The limit is already becoming too small, for example a DVD disc image can exceed that limit. In addition, FAT32 lacks file permission support. In order to get rid of these limitations, Microsoft took FAT from its grave and updated it one more time.</p>  <p>However, FAT32 only allows files up to four gigabytes in size. The limit is already becoming too small, for example a DVD disc image can exceed that limit. In addition, FAT32 lacks file permission support. In order to get rid of these limitations, Microsoft took FAT from its grave and updated it one more time.</p>
2529  <p>ExFAT (extended FAT), also known as FAT64, was introduced with Windows CE 6.0, on November 2006. Windows Vista SP1, Windows 7 and newer support exFAT too, and by installing <a href="http://support.microsoft.com/kb/955704" target="_blank">this update</a> Windows XP can be extended to support exFAT as well. Unfortunately, the only read-write exFAT driver for GNU/Linux (<a href="http://www.tuxera.com/products/exfat-for-embedded-systems/" target="_blank">Tuxera exFAT for Embedded Systems</a>) is payware.</p>  <p>ExFAT (extended FAT), also known as FAT64, was introduced with Windows CE 6.0, on November 2006. Windows Vista SP1, Windows 7 and newer support exFAT too, and by installing <a href="http://support.microsoft.com/kb/955704" target="_blank">this update</a> Windows XP can be extended to support exFAT as well. GNU/Linux drivers are available too, but currently none of them are both stable and free. The best option seems to be <a href="http://code.google.com/p/exfat/" target="_blank">exfat</a>, an open-source driver in beta stage.</p>
2530  <p>The partition and file size limits of exFAT are the same: 64 zettabytes. Another important improvement is file permission support that, oddly, is lacking in Windows Vista. In addition, a directory within an exFAT partition can contain up to 2 796 202 files (instead of 65 536, as in FAT32) and timestamps have become more accurate.</p>  <p>The partition and file size limits of exFAT are the same: 64 zettabytes. Another important improvement is file permission support that, oddly, is lacking in Windows Vista. In addition, a directory within an exFAT partition can contain up to 2 796 202 files (instead of 65 536, as in FAT32) and timestamps have become more accurate.</p>
2531  <p>No operating system can be installed to an exFAT partition, so such partitions can only be used for data storage. Due to lack of journaling and support for huge files, exFAT is a good filesystem on Solid State Drives and thumb drives that are only used within Windows Vista and/or 7.</p>  <p>No operating system can be installed to an exFAT partition, so such partitions can only be used for data storage. Due to lack of journaling and support for huge files, exFAT is a good filesystem on Solid State Drives and thumb drives that are only used within Windows Vista and/or 7.</p>
2532  <H3><a name="annex-b-list"></a>Partition list <span class="hideprint">[<a href="#annex-b-top" title="go to top of the page">^</a>]</span></H3>  <H3><a name="annex-b-list"></a>Partition list <span class="hideprint">[<a href="#annex-b-top" title="go to top of the page">^</a>]</span></H3>
2533  <p>The following table presents known partition types along with their IDs:</p>  <p>The following table presents known partition types along with their IDs:</p>
2534  <p class="newcode" style="margin-right: 0;">&nbsp;0&nbsp;&nbsp;Empty&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;80&nbsp;&nbsp;Old&nbsp;Minix<br>  <p class="newcode" style="margin-right: 0;">&nbsp;0&nbsp;&nbsp;Empty&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;80&nbsp;&nbsp;Old&nbsp;Minix<br>
2535  &nbsp;1&nbsp;&nbsp;FAT12&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;81&nbsp;&nbsp;Minix&nbsp;/&nbsp;old&nbsp;Linux<br>  &nbsp;1&nbsp;&nbsp;FAT12&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;81&nbsp;&nbsp;Minix&nbsp;/&nbsp;old&nbsp;Linux<br>
2536  &nbsp;2&nbsp;&nbsp;XENIX&nbsp;root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<font color="Red">82&nbsp;&nbsp;Linux&nbsp;swap&nbsp;/&nbsp;Solaris</font><br>  &nbsp;2&nbsp;&nbsp;XENIX&nbsp;root&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<font color="Green">82&nbsp;&nbsp;Linux&nbsp;swap&nbsp;/&nbsp;Solaris</font><br>
2537  &nbsp;3&nbsp;&nbsp;XENIX&nbsp;usr&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<font color="Green">83&nbsp;&nbsp;Linux</font><br>  &nbsp;3&nbsp;&nbsp;XENIX&nbsp;usr&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<font color="Red">83&nbsp;&nbsp;Linux</font><br>
2538  &nbsp;4&nbsp;&nbsp;FAT16&nbsp;&lt;32M&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;84&nbsp;&nbsp;OS/2&nbsp;hidden&nbsp;C:&nbsp;drive<br>  &nbsp;4&nbsp;&nbsp;FAT16&nbsp;&lt;32M&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;84&nbsp;&nbsp;OS/2&nbsp;hidden&nbsp;C:&nbsp;drive<br>
2539  &nbsp;5&nbsp;&nbsp;Extended&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;85&nbsp;&nbsp;Linux&nbsp;extended<br>  &nbsp;<font color="Red">5&nbsp;&nbsp;Extended</font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;85&nbsp;&nbsp;Linux&nbsp;extended<br>
2540  &nbsp;<font color="Red">6&nbsp;&nbsp;FAT16</font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;86&nbsp;&nbsp;NTFS&nbsp;volume&nbsp;set<br>  &nbsp;6&nbsp;&nbsp;FAT16&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;86&nbsp;&nbsp;NTFS&nbsp;volume&nbsp;set<br>
2541  &nbsp;<font color="Green">7&nbsp;&nbsp;HPFS/NTFS</font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;87&nbsp;&nbsp;NTFS&nbsp;volume&nbsp;set<br>  &nbsp;<font color="Green">7&nbsp;&nbsp;HPFS/NTFS</font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;87&nbsp;&nbsp;NTFS&nbsp;volume&nbsp;set<br>
2542  &nbsp;8&nbsp;&nbsp;AIX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;88&nbsp;&nbsp;Linux&nbsp;plaintext<br>  &nbsp;8&nbsp;&nbsp;AIX&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;88&nbsp;&nbsp;Linux&nbsp;plaintext<br>
2543  &nbsp;9&nbsp;&nbsp;AIX&nbsp;bootable&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;8e&nbsp;&nbsp;Linux&nbsp;LVM<br>  &nbsp;9&nbsp;&nbsp;AIX&nbsp;bootable&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;8e&nbsp;&nbsp;Linux&nbsp;LVM<br>
# Line 2636  The following pressentation has been mad Line 2581  The following pressentation has been mad
2581  75&nbsp;&nbsp;PC/IX</p>  75&nbsp;&nbsp;PC/IX</p>
2582  <p>The partitions you are most likely to see in use, are:</p>  <p>The partitions you are most likely to see in use, are:</p>
2583  <ul>  <ul>
 <li><b><font color="Red">FAT16 (ID = 6)  </font></b><br>  
 This is the old DOS partition type<br>  
 You may still find it in pure DOS installations, like vendor diagnostics tool partitions, and small USB sticks (128 - 250 MB)</li>  
2584  <li><b><font color="Green">HPFS/NTFS (ID = 7)</font></b><br>  <li><b><font color="Green">HPFS/NTFS (ID = 7)</font></b><br>
2585  This is the <b>Windows XP</b> partition, also known as <b>NTFS</b></li>  This is the <b>Windows XP</b> partition, also known as <b>NTFS</b></li>
2586  <li><b><font color="Red">W95 FAT32 (LBA) (ID = c)</font></b><br>  <li><b><font color="Red">W95 FAT32 (LBA) (ID = c)</font></b><br>
2587  This is the <b>Windows 95 - 98</b> partition<br>  This is the <b>Windows 95 - 98</b> partition<br>
2588  It is used in any kind of disk and large USB devices (1 GB and more)</li>  It is used in any kind of disk and large USB devices (1 GB and more)</li>
2589  <li><b><font color="Green">W95 Ext'd (LBA) (ID = f)</font></b><br>  <li><b><font color="Green">W95 Ext'd (LBA) (ID = f)</font></b><br>
2590  Extended partition. It acts as a container for other partitions<br>  Extended partition. It acts as a container for other partitions</li>
2591  There is one more extended partition type (ID = 5), but it does not seem to be in use as much</li>  <li><b><font color="Red">Extended (ID = 5)</font></b><br>
2592  <li><b><font color="Red">Linux swap / Solaris (ID = 82)</font></b><br>  Another extended partition type. It acts as a container for other partitions<br>
2593    There is one more extended partition type (ID = 85), but Windows doesn't recognise it</li>
2594    <li><b><font color="Green">Linux swap / Solaris (ID = 82)</font></b><br>
2595  Swap partition, acting as <b>Virtual Memory</b><br>  Swap partition, acting as <b>Virtual Memory</b><br>
2596  Modern computers with 1 - 2 GB of memory may not use it at all</li>  Modern computers with 1 - 2 GB of memory may not use it at all</li>
2597  <li><b><font color="Green">Linux (ID = 83)</font></b><br>  <li><b><font color="Red">Linux (ID = 83)</font></b><br>
2598  Linux partitions, such as <b>ext2</b>, <b>ext3</b> and <b>reiserfs</b></li>  Linux partitions, such as <b>ext2</b>, <b>ext3</b> and <b>reiserfs</b></li>
2599  </ul>  </ul>
2600  <H2><a name="example"></a>Partitioning example <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="example"></a>Partitioning example <span class="hideprint">[<a href="#partitions-top" title="go to top of the page">^</a>]</span></H2>
# Line 2685  Disk identifier: 0x00058a4a<br> Line 2629  Disk identifier: 0x00058a4a<br>
2629  <img src="images/gparted-04.png">  <img src="images/gparted-04.png">
2630  <p>I right-click the unallocated area and select <b>New</b>.</p>  <p>I right-click the unallocated area and select <b>New</b>.</p>
2631  <img src="images/gparted-05.png">  <img src="images/gparted-05.png">
2632  <p>I select <b>Extended Partition</b> as the partition type. The size was already 998 megabytes (the maximum) and as said, an extended partition doesn't contain any filesystem. I click <b>Add</b>.</p>  <p>I select <b>Extended Partition</b> as the partition type. The size was already 1000 megabytes (the maximum) and as said, an extended partition doesn't contain any filesystem. I click <b>Add</b>.</p>
2633  <img src="images/gparted-06.png">  <img src="images/gparted-06.png">
2634  <p>I right-click the unallocated area within the extended partition and select <b>New</b>.</p>  <p>I right-click the unallocated area within the extended partition and select <b>New</b>.</p>
2635  <img src="images/gparted-07.png">  <img src="images/gparted-07.png">
2636  <p>I choose the ext4 filesystem and enter 798 MB as the partition size. After that, I click first the <b>Free Space Following (MiB)</b> combo box and then <b>Add</b>.</p>  <p>I choose the ext4 filesystem and enter 799 MB as the partition size. After that, I click first the <b>Free Space Following (MiB)</b> combo box and then <b>Add</b>.</p>
2637  <img src="images/gparted-08.png">  <img src="images/gparted-08.png">
2638  <p>I right-click the remaining unallocated space and select <b>New</b> one more time.</p>  <p>I right-click the remaining unallocated space and select <b>New</b> one more time.</p>
2639  <img src="images/gparted-09.png">  <img src="images/gparted-09.png">
2640  <p>I choose the ext4 filesystem again. The partition size setting was already 201 megabytes (the whole available space), so I just press <b>Add</b>.</p>  <p>I choose the ext4 filesystem again. The partition size setting was already 200 megabytes (the whole available space), so I just press <b>Add</b>.</p>
2641  <img src="images/gparted-10.png">  <img src="images/gparted-10.png">
2642  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>  <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>
2643  The next step is to commit the changes.<br><br>After that some operations, for example<br>partition deletion, can no longer be undone.  The next step is to commit the changes.<br><br>After that some operations, for example<br>partition deletion, can no longer be undone.
# Line 2715  mkdir /mnt/sda6</p> Line 2659  mkdir /mnt/sda6</p>
2659  <p>Then I mount the partitions:</p>  <p>Then I mount the partitions:</p>
2660  <p class="newcode">mount /dev/sda1 /mnt/sda1<br>  <p class="newcode">mount /dev/sda1 /mnt/sda1<br>
2661  mount /dev/sda6 /mnt/sda6</p>  mount /dev/sda6 /mnt/sda6</p>
2662  <p>I move the directory:</p>  <p>I copy the directory to the new partition:</p>
2663  <p class="newcode">mv /mnt/sda1/home/* /mnt/sda6/</p>  <p class="newcode">cd /mnt/sda1<br>
2664    rsync -aAPSX home/ /mnt/sda6</p>
2665    <p>I move the original directory out of my way and create a new directory in place of it:</p>
2666    <p class="newcode">mv home home-old<br>
2667    mkdir home</p>
2668  <p>After that, I unmount /dev/sda6, because it no longer needs to be mounted:</p>  <p>After that, I unmount /dev/sda6, because it no longer needs to be mounted:</p>
2669  <p class="newcode">sync<br>  <p class="newcode">umount /dev/sda6</p>
 umount /dev/sda6</p>  
2670  <img src="images/terminal.png">  <img src="images/terminal.png">
 <p>As you can see, under Linux it's perfectly normal that the terminal doesn't answer to the commands. Don't worry - they are really executed.</p>  
2671  <p>Now I close <b>Terminal</b> and launch <b>Geany</b> by pressing the fourth icon in the bottom pane.</p>  <p>Now I close <b>Terminal</b> and launch <b>Geany</b> by pressing the fourth icon in the bottom pane.</p>
2672  <img src="images/geany-00.png">  <img src="images/geany-00.png">
2673  <p>I select <b>File</b> -> <b>Open</b>.</p>  <p>I select <b>File</b> -> <b>Open</b>.</p>
# Line 2734  umount /dev/sda6</p> Line 2680  umount /dev/sda6</p>
2680  <p class="newcode">/dev/sda6&nbsp;/home&nbsp;ext4&nbsp;defaults&nbsp;0&nbsp;2</p>  <p class="newcode">/dev/sda6&nbsp;/home&nbsp;ext4&nbsp;defaults&nbsp;0&nbsp;2</p>
2681  <p>Finally, I select <b>File</b> -> <b>Save</b>.</p>  <p>Finally, I select <b>File</b> -> <b>Save</b>.</p>
2682  <img src="images/geany-04.png">  <img src="images/geany-04.png">
2683  <p>It's a good idea to reboot the computer now and check if the distribution in <b>/dev/sda1</b> still works. Anyway, the disk should now be ready for the new distro.</p>  <p>It's a good idea to reboot the computer now and check if the distribution in <b>/dev/sda1</b> still works. If yes, the /home-old directory can be removed and the disk is ready for the new distro.</p>
2684  <a name="recover-top"></a>  <a name="recover-top"></a>
2685  <H2 style="font-size: 2em;"><a name="recover-intro"></a>Data Recovery <span class="hideprint">[<a href="#help-top" title="go to top of the page">^</a>]</span></H2>  <H2 style="font-size: 2em;"><a name="recover-intro"></a>Data Recovery <span class="hideprint">[<a href="#help-top" title="go to top of the page">^</a>]</span></H2>
2686  <p>Deleted or "lost" files can be recovered from failed or formatted drives and partitions, cdroms and memory cards using the  software available in <b>SystemRescueCD</b>.  <p>Deleted or "lost" files can be recovered from failed or formatted drives and partitions, cdroms and memory cards using the  software available in <b>SystemRescueCD</b>.

Legend:
Removed from v.72  
changed lines
  Added in v.102

webmaster@linux.gr
ViewVC Help
Powered by ViewVC 1.1.26