/[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 84 by sng, Thu Jul 15 20:54:27 2010 UTC revision 114 by sng, Wed Sep 15 13:32:14 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>15/09/2010 - v 3.1.0</H4></div>
76      <div style="position: absolute; right: 0px;"><H4>Last update: 13/07/2010</H4></div>      <div style="position: absolute; right: 0px;"><H4>Last update: 15/09/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.8</td>  <tr><td  class="bordertable" >15/09/10</td><td  class="bordertable" >3.1.0</td><td  class="bordertable" >1.2.5-35&nbsp;(mod)</td><td  class="bordertable" >1.6.0</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<br>  -&nbsp;<b>Clonezilla Live</b> updated to version 1.2.5-35<br>
166  -&nbsp;<b>SystemRescueCD</b> updated to version 1.5.8<br>  -&nbsp;<b>SystemRescueCD</b> updated to version 1.6.0<br>
167    - Three <b>Clonezilla-SysRescCD</b> flavours are now available,<br>
168    &nbsp;&nbsp;one for each architecture (i486,i686,amd64)<br>
169  -&nbsp;<b>Super Grub Disk</b> updated to version 0.9799<br>  -&nbsp;<b>Super Grub Disk</b> updated to version 0.9799<br>
170  -&nbsp;Added <b>Super Grub Disk 2</b> version 1.30<br>  -&nbsp;Added <b>Super Grub Disk 2</b> version 1.98s<br>
171    -&nbsp;<b>Smart Boot Manager</b> was added to the Tools section<br>
172    -&nbsp;Added restorecd/ and docs/ to the squashfs file of Clonezilla distro.<br>
173    &nbsp;&nbsp;This way all items are always available (even when booting to RAM)<br>
174  -&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>
175  -&nbsp;Major site / documentation update (thanks to Jyrki Vesterinen)  -&nbsp;Major site and documentation update (thanks to Jyrki Vesterinen)
176    </td></tr>
177    <tr><td class="bordertable" width="10" valign="top"></td><td class="bordertable" width="10" valign="top">Package</td><td class="bordertable">
178    -&nbsp;Added auto mode (parameter -a) to script create-clonezilla-sysresccd
179  </td></tr>  </td></tr>
180  <tr><td class="bordertable" width="10" valign="top"><a name="2.6.0"></a>2.6.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">  <tr><td class="bordertable" width="10" valign="top"><a name="2.6.0"></a>2.6.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">
181  -&nbsp;<b>Clonezilla Live</b> updated to version 1.1.0-8<br>  -&nbsp;<b>Clonezilla Live</b> updated to version 1.1.0-8<br>
# Line 298  More info: <a href="reloc-img.html">Rest Line 306  More info: <a href="reloc-img.html">Rest
306  </td></tr>  </td></tr>
307  <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>
308  </table>  </table>
309    <!--
310  <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>
311  <p>  <p>
312  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>
313  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.3 MB]<br>
314    <!--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>
315    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>
316  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>
317  ISO file md5sum: <b><i></i></b></p>  ISO file md5sum: <b><i>"MD5SUM"</i></b></p>
318    -->
319  <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>
320  <p>Yes, of course you can. If you have:</p>  <p>Yes, of course you can. If you have:</p>
321  <ul style="margin-right: 30pt;">  <ul style="margin-right: 30pt;">
# Line 1278  Having done all of the above, I am ready Line 1290  Having done all of the above, I am ready
1290  <br>  <br>
1291  </p>  </p>
1292  <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>
1293  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.5-17</b>  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.5-35</b>
1294  </td></tr></table></div>  </td></tr></table></div>
1295  <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>
1296  <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 1340  I select "<font color="Red"><b>savedisk< Line 1352  I select "<font color="Red"><b>savedisk<
1352  <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>
1353  <p><img src="images/backup-11.png"><br>  <p><img src="images/backup-11.png"><br>
1354  In this screen I select the image name.<br>  In this screen I select the image name.<br>
1355  I type "Backup_22-2010_sdb", 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.
1356  </p>  </p>
1357  <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>
1358  <p><img src="images/backup-12.png"><br>  <p><img src="images/backup-12.png"><br>
# Line 1433  I select "<font color="Red"><b>savedisk< Line 1445  I select "<font color="Red"><b>savedisk<
1445  <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>
1446  <p><img src="images/backup-11.png"><br>  <p><img src="images/backup-11.png"><br>
1447  In this screen I select the image name.<br>  In this screen I select the image name.<br>
1448  I type "Backup_22-2010_sdb", 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.
1449  </p>  </p>
1450  <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>
1451  <p><img src="images/backup-12.png"><br>  <p><img src="images/backup-12.png"><br>
# Line 1466  reboot<br><br></p> Line 1478  reboot<br><br></p>
1478  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.  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.
1479  </td></tr></table></div>  </td></tr></table></div>
1480  <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>
1481  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.5-17</b>  The following pressentation has been made using<br><b>Clonezilla Live v 1.2.5-35</b>
1482  </td></tr></table></div>  </td></tr></table></div>
1483  <H2><a name="restore"></a>Restoring data <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>  <H2><a name="restore"></a>Restoring data <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>
1484  <H3><a name="res-0"></a>Clonezilla-SysRescCD starting screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>  <H3><a name="res-0"></a>Clonezilla-SysRescCD starting screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
# Line 1633  This screen allows me to select the keym Line 1645  This screen allows me to select the keym
1645  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>
1646  <p><img src="images/restore-16.png"><br>  <p><img src="images/restore-16.png"><br>
1647  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>
1648  <p><a name="dl-dvd"></a><img src="images/cust-menu-01.png"><br>  <H3><a name="rui-13a"></a>Screen "Excessive Image Size" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1649  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>  <p><img src="images/restore-16a.png"><br>
1650    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>
1651  <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>
1652  <p><img src="images/cust-menu-02.png"><br>  <p><img src="images/cust-menu-02.png"><br>
1653  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>
# Line 1664  This is where I choose the publisher ID Line 1677  This is where I choose the publisher ID
1677  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.
1678  <br>  <br>
1679  <br>  <br>
 <img src="images/cust-menu-10.png">  
 <br>  
 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>  
1680  <img src="images/restore-18.png"><br>  <img src="images/restore-18.png"><br>
1681  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>  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>
 <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>  
1682  <a name="restore-burn-top"></a>  <a name="restore-burn-top"></a>
1683  <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>
1684  <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 1682  This page walks through burning the disc Line 1687  This page walks through burning the disc
1687  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>
1688  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>
1689  <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>
1690  <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>  
1691  <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>
1692  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>
1693  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>
1694  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>
1695  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>
1696  That's it. You own now an automated recovery disc.</p>  That's it. You own now an automated recovery disc.</p>
1697  <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>
1698  <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>
1699  <img src="images/k3b-00.png"><br>  <img src="images/k3b-00.png"><br>
1700  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 1705  I click <b>Start</b> and the burning pro Line 1709  I click <b>Start</b> and the burning pro
1709  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>
1710  <img src="images/k3b-05.png"><br>  <img src="images/k3b-05.png"><br>
1711  The burning attempt succeeded.<br><br>  The burning attempt succeeded.<br><br>
1712  <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>
1713  <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>" \<br>  
 --publisher "<font color="Green">Your Name</font>" -graft-points \<br>  
 /<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>" \<br>  
 -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>  
1714  <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>
1715  <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>
1716  <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 1738  mount /dev/<font color="Green">sdc1</fon Line 1718  mount /dev/<font color="Green">sdc1</fon
1718  <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>
1719  <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>
1720  <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>
1721  <p class="newcode">fdisk -l /dev/<font color="Green">sdc</font></p>  <p class="newcode">parted -l</p>
1722  <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>  
1723  <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>
1724  <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>
1725  <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>
1726  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.
1727  </td></tr></table></div>  </td></tr></table></div>
1728  <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>
1729    <p><b>Note:</b> In the command replace <b>/dev/<font color="Green">sdc1</font></b> with the partition you wish to format.</p>
1730  <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>
1731  <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>
1732  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 1761  The latter of the commands below replace Line 1741  The latter of the commands below replace
1741  <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>
1742  <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>
1743  <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>  
1744  <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>
1745  <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>
1746  <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 2403  This page contains some theory about par Line 2382  This page contains some theory about par
2382  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.
2383  </td></tr></table></div>  </td></tr></table></div>
2384  <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>
2385  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>
2386  </td></tr></table></div>  </td></tr></table></div>
2387  <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>
2388  <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 2411  The following pressentation has been mad Line 2390  The following pressentation has been mad
2390  <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>
2391  <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>
2392  <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>
2393  <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>
2394  <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>
2395  <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>
2396  <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>
2397  <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>
2398  <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>
2399  <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>  
2400  <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>
2401  <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>
2402  <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 2435  The following pressentation has been mad Line 2413  The following pressentation has been mad
2413  <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>
2414  <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>
2415  <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>
2416  <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>
2417  <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>
2418    <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>
2419  <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>
2420  <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>
2421  <table border="1">  <table border="1">
# Line 2489  The following pressentation has been mad Line 2468  The following pressentation has been mad
2468    </tr>    </tr>
2469      <tr>      <tr>
2470      <th>ext4</th>      <th>ext4</th>
2471      <td style="background-color: rgb(255,0,0)">No</td>      <td style="background-color: rgb(255,0,0)">No***</td>
2472          <td style="background-color: rgb(0,255,0)">Native</td>          <td style="background-color: rgb(0,255,0)">Native</td>
2473          <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>
2474          <td style="background-color: rgb(0,255,0)">Yes</td>          <td style="background-color: rgb(0,255,0)">Yes</td>
# Line 2497  The following pressentation has been mad Line 2476  The following pressentation has been mad
2476    </tr>    </tr>
2477      <tr>      <tr>
2478      <th>exFAT</th>      <th>exFAT</th>
2479      <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>
2480          <td style="background-color: rgb(255,0,0)">No</td>          <td style="background-color: rgb(255,127,0)">3rd party driver</td>
2481          <td style="background-color: rgb(0,255,0)">64 ZB</td>          <td style="background-color: rgb(0,255,0)">64 ZB</td>
2482          <td style="background-color: rgb(255,0,0)">No</td>          <td style="background-color: rgb(255,0,0)">No</td>
2483          <td style="background-color: rgb(0,255,0)">Yes</td>          <td style="background-color: rgb(0,255,0)">Yes</td>
2484    </tr>    </tr>
2485  </table>  </table>
2486  <p>* Depends on cluster size<br>  <p>* Depends on cluster size<br>
2487  ** <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>
2488    *** <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>
2489  <p>Operating system support:</p>  <p>Operating system support:</p>
2490  <ul>  <ul>
2491  <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>
2492  <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>
2493  <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>
2494  <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>
2495  <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>
2496  </ul>  </ul>
2497  <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>
2498  <p>This section contains more information about most popular filesystems.</p>  <p>This section contains more information about most popular filesystems.</p>
# Line 2520  The following pressentation has been mad Line 2500  The following pressentation has been mad
2500  <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>
2501  <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>
2502  <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>
2503  <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>
2504  <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>
2505  <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>
2506  <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 2530  The following pressentation has been mad Line 2510  The following pressentation has been mad
2510  <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>
2511  <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>
2512  <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>
2513  <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>
2514  <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>
2515  <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>
2516  <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>
2517  <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>
2518  <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>
2519  <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 2541  The following pressentation has been mad Line 2521  The following pressentation has been mad
2521  <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>
2522  <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>
2523  <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>
2524  <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>
2525  <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>
2526  <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>
2527  <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 2554  The following pressentation has been mad Line 2534  The following pressentation has been mad
2534  <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>
2535  <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>
2536  <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>
2537  <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>
2538  <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>
2539  <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>
2540  <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>
2541  <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>
2542  <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>
2543  &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>
2544  &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>
2545  &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>
2546  &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>
2547  &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>
2548  &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>
2549  &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>
2550  &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>
2551  &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 2609  The following pressentation has been mad Line 2589  The following pressentation has been mad
2589  75&nbsp;&nbsp;PC/IX</p>  75&nbsp;&nbsp;PC/IX</p>
2590  <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>
2591  <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>  
2592  <li><b><font color="Green">HPFS/NTFS (ID = 7)</font></b><br>  <li><b><font color="Green">HPFS/NTFS (ID = 7)</font></b><br>
2593  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>
2594  <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>
2595  This is the <b>Windows 95 - 98</b> partition<br>  This is the <b>Windows 95 - 98</b> partition<br>
2596  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>
2597  <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>
2598  Extended partition. It acts as a container for other partitions<br>  Extended partition. It acts as a container for other partitions</li>
2599  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>
2600  <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>
2601    There is one more extended partition type (ID = 85), but Windows doesn't recognise it</li>
2602    <li><b><font color="Green">Linux swap / Solaris (ID = 82)</font></b><br>
2603  Swap partition, acting as <b>Virtual Memory</b><br>  Swap partition, acting as <b>Virtual Memory</b><br>
2604  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>
2605  <li><b><font color="Green">Linux (ID = 83)</font></b><br>  <li><b><font color="Red">Linux (ID = 83)</font></b><br>
2606  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>
2607  </ul>  </ul>
2608  <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 2658  Disk identifier: 0x00058a4a<br> Line 2637  Disk identifier: 0x00058a4a<br>
2637  <img src="images/gparted-04.png">  <img src="images/gparted-04.png">
2638  <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>
2639  <img src="images/gparted-05.png">  <img src="images/gparted-05.png">
2640  <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>
2641  <img src="images/gparted-06.png">  <img src="images/gparted-06.png">
2642  <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>
2643  <img src="images/gparted-07.png">  <img src="images/gparted-07.png">
2644  <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>
2645  <img src="images/gparted-08.png">  <img src="images/gparted-08.png">
2646  <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>
2647  <img src="images/gparted-09.png">  <img src="images/gparted-09.png">
2648  <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>
2649  <img src="images/gparted-10.png">  <img src="images/gparted-10.png">
2650  <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>
2651  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 2688  mkdir /mnt/sda6</p> Line 2667  mkdir /mnt/sda6</p>
2667  <p>Then I mount the partitions:</p>  <p>Then I mount the partitions:</p>
2668  <p class="newcode">mount /dev/sda1 /mnt/sda1<br>  <p class="newcode">mount /dev/sda1 /mnt/sda1<br>
2669  mount /dev/sda6 /mnt/sda6</p>  mount /dev/sda6 /mnt/sda6</p>
2670  <p>I move the directory:</p>  <p>I copy the directory to the new partition:</p>
2671  <p class="newcode">mv /mnt/sda1/home/* /mnt/sda6/</p>  <p class="newcode">cd /mnt/sda1<br>
2672    rsync -aAPSX home/ /mnt/sda6</p>
2673    <p>I move the original directory out of my way and create a new directory in place of it:</p>
2674    <p class="newcode">mv home home-old<br>
2675    mkdir home</p>
2676  <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>
2677  <p class="newcode">sync<br>  <p class="newcode">umount /dev/sda6</p>
 umount /dev/sda6</p>  
2678  <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>  
2679  <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>
2680  <img src="images/geany-00.png">  <img src="images/geany-00.png">
2681  <p>I select <b>File</b> -> <b>Open</b>.</p>  <p>I select <b>File</b> -> <b>Open</b>.</p>
# Line 2707  umount /dev/sda6</p> Line 2688  umount /dev/sda6</p>
2688  <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>
2689  <p>Finally, I select <b>File</b> -> <b>Save</b>.</p>  <p>Finally, I select <b>File</b> -> <b>Save</b>.</p>
2690  <img src="images/geany-04.png">  <img src="images/geany-04.png">
2691  <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>
2692  <a name="recover-top"></a>  <a name="recover-top"></a>
2693  <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>
2694  <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>.
# Line 3172  Can&nbsp;write&nbsp;RAM:&nbsp;&nbsp;&nbs Line 3153  Can&nbsp;write&nbsp;RAM:&nbsp;&nbsp;&nbs
3153  &nbsp;*&nbsp;signifies&nbsp;the&nbsp;current&nbsp;active&nbsp;mode<br>  &nbsp;*&nbsp;signifies&nbsp;the&nbsp;current&nbsp;active&nbsp;mode<br>
3154  <br></p>  <br></p>
3155  <a name="shots-top"></a>  <a name="shots-top"></a>
3156  <p align="center"><img src="images/clonezilla-sysresccd-1.png" border="0" alt="The splash screen of v 2.4.0"><br>  <p align="center"><img src="images/clonezilla-sysresccd-1.png" border="0" alt="The splash screen of v 3.1.0"><br>
3157  The splash screen of v 2.6.0<br><br><img src="images/clonezilla-sysresccd-2.png" border="0" alt="The splash screen of my test Restore DVD (v 2.4.0)"><br>  The splash screen of v 3.1.0 (Clonezilla i686)<br><br><img src="images/clonezilla-sysresccd-2.png" border="0" alt="The splash screen of my test Restore DVD (v 3.1.0)"><br>
3158  The splash screen of my test Restore DVD (v 2.6.0)<br>  The splash screen of my test Restore DVD (v 3.1.0)<br>
3159  As you can see, I have used the option  <i><b>-I "Restore sda (250MB Stick)"</b></i><br>  As you can see both the menu entries text and the default item have been altered</p>
 to master the DVD</p>  
3160  <p>You may also want to see:</p>  <p>You may also want to see:</p>
3161  <p>SystemRescueCD Screenshots - <a href="http://www.sysresccd.org/Screenshots" target="_blank">http://www.sysresccd.org/Screenshots</a><br>  <p>SystemRescueCD Screenshots - <a href="http://www.sysresccd.org/Screenshots" target="_blank">http://www.sysresccd.org/Screenshots</a><br>
3162  Clonezilla Live - <a href="http://www.clonezilla.org/screenshot/" target="_blank">http://www.clonezilla.org/screenshot/</a><br>  Clonezilla Live - <a href="http://www.clonezilla.org/screenshot/" target="_blank">http://www.clonezilla.org/screenshot/</a><br>

Legend:
Removed from v.84  
changed lines
  Added in v.114

webmaster@linux.gr
ViewVC Help
Powered by ViewVC 1.1.26