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

Contents of /trunk/www/onepage.html

Parent Directory Parent Directory | Revision Log Revision Log


Revision 181 - (show annotations)
Wed Jun 22 16:47:21 2011 UTC (10 years, 2 months ago) by sng
File MIME type: text/html
File size: 339092 byte(s)
- updating usb installation instructions
- updating site

1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
2 <html>
3 <head>
4 <link rel="alternate" type="application/rss+xml" title="RSS" href="http://clonezilla-sysresccd.hellug.gr/clonezilla-sysresccd.rss">
5 <link rel="shortcut icon" href="favicon.ico">
6 <title>Clonezilla-SysRescCD - Welcome</title>
7 <style type="text/css">
8 body { font-family: Arial, 'sans serif'; color: black; font-size: 12pt; background : fixed no-repeat; background-color: #333333; padding: 0; margin: 0; margin-top: 5px; margin-bottom: 5px; }
9
10
11 #header {position:relative; display: block; width: 980px; height: 121px;margin: auto; padding: auto; background-color: #D37624; background-image: url('images/header.png');clear:both;}
12 #header h2{ color: #FFE6BC; font-weight: bold; font-size: 2.2em; margin:0; padding:0; padding-left: 10px; padding-top: 7px; text-shadow: #333333 2px 2px 4px;}
13 #header h3{ color: #FFE6BC; font-weight: bold; font-size: 1.8em; margin:0; padding: 0; padding-left: 10px; text-shadow: #333333 2px 2px 4px;}
14 #header h4{ color: #FFE6BC; font-weight: bold; font-size: 1.2em; margin:0; padding: 0; padding-left: 10px; padding-right: 10px; text-shadow: #333333 2px 2px 4px;}
15 #header a {text-decoration:none;}
16 #contarea {display: block; width: 980px; margin: auto; padding: auto; background-color: #FFF2DD; background-image: url(''); background-repeat:repeat-y;clear:both;}
17
18 #linkline { width: 980px; height: 29px;margin: auto; padding: auto; background-color: #D37624; background-image: url('images/linkline.png');clear:both; }
19 #linkline a{float: left; color: #FFE6BC; font-weight: bold; font-size: 0.8em; text-decoration: none; text-shadow: #333333 2px 2px 4px; padding-left: 10px; padding-right: 10px; padding-top: 5px;}
20 #linkline a:visited{color: #FFE6BC;}
21 #linkline a:hover{color: #333333;}
22 #linkline a.here {color: #333333; text-decoration: none;}
23 #lastupdate {float: right; display: block; text-align: right; margin: 0; margin-top: -1.2em; padding: 0; padding-right: 15px;}
24 #rss { float: right; text-align: right; padding-top: 3px;}
25
26 #docline-top { float: right; padding-right: 40px; text-align: right; }
27 #docline-bottom { float: right; padding-right: 40px; text-align: right; font-size: 0.8em; padding-top: 15px; }
28 #docline-bottom a{ padding-left: 10px; padding-right: 10px; }
29
30 #menu { float: right; display: block; width: 170px; margin: auto; padding: 15px; font-size: 0.8em; font-weight: bold; background-color: #FFE6BC;}
31 #menu h1 {color: #990000; font-size: 1.8em;text-shadow: gray 2px 2px 4px;}
32 #menu a,a:visited{ color: black; text-decoration: none; font-weight: normal;}
33 #menu a:hover{ text-decoration: underline;}
34 #menu p{ margin-bottom: 10px;}
35
36 #content { float: left; display: block; width: 950px; margin: auto; padding: 15px;}
37
38
39 #footer {display: block; width: 980px; height: 100px;margin: auto; padding: auto; background-color: #D37624; background-image: url('images/footer.png');clear:both;text-shadow: #333333 2px 2px 4px;}
40 #footer p{color: #FFE6BC; font-weight: bold; padding:15px; padding-left: 10px;}
41 #footer a,a:visited{color: #FFE6BC; font-weight: bold; text-decoration:none;}
42 #footer a:hover{ color: #333333; text-decoration: none;}
43
44
45 #content H1,H2,H3,H4{color: #990000; text-align: left;}
46 #content H2{margin-top: 2em;}
47 #content H3{margin-top: 1.5em}
48 #content H4{margin-top: 1em}
49 #content li { margin-top: 1em;}
50 #content a,a:active,a:visited{text-decoration: none; color: #4075CA; font-weight: normal;}
51 #content a:hover{text-decoration: underline; font-weight: normal;}
52 #content .hidden{ display:none; }
53 #content p,td,table,tr,li { font-family: Arial, 'sans serif'; }
54 #content .nav{margin-left: 0pt;}
55 #content .newcode{font-family : "Courier New", Courier, monospace; font-weight: bold; background-color: #F2F2F2; border: solid 1px #DEDEDE;padding: 20pt;}
56 #content .note{margin-top: 30pt; margin-bottom: 30pt; text-align: left; background-color: #FFEFEF; border: double 3px; border-color: #FFD5D5;}
57 #content hr{color: Black; background-color: Black; height: 1px; border: none;}
58 #content .header-news{margin-top: 2em; margin-left: 25pt; font-weight: bold; color: #990000;}
59 #content .item-news{margin-left: 45pt; margin-right: 45pt;}
60 #content .otherpage{border: solid 1px darkgoldenrod; padding: 20pt; background-color: lemonchiffon;}
61 #content IMG {display: block; margin-left: auto; margin-right: auto; }
62 #content .red{color: white; background-color: Red; font-weight: bold;}
63 #lphp{text-align: right; padding-left: 10px; padding-right: 10px; padding-top: 50px; float: right;}
64 #lphp a{padding-left: 5px;}
65 #warning { margin: 5px; padding: .4em; background-color: Red; color: White; align: center; font-weight: bold; border-width: 2px; border-color: white; border-style: solid; }
66 #warning a { color: white; font-weight: bold; text-decoration: underline; }
67 </style>
68 <link href="warning.css" rel="stylesheet" type="text/css" />
69 <!--
70 The file waring.css exists only in the root of the site
71 and it hides the UNSTABLE warnings. Its contents are
72 #warning { display: none; }
73 -->
74 <META NAME="Keywords" CONTENT="multiboot Multi Boot bootable cd rescue clonezilla sysresccd backup restore samba">
75 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
76 </head>
77 <body>
78 <div id="warning" align="center">
79 WARNING<br>
80 This is the UNSTABLE version of Clonezilla-SysRescCD<br>
81 To access our current stable version, please click <a href="../index.html">here</a>
82 </div>
83 <div id="header">
84 <div id="lphp" style=""><a target="_blank" title="Display all in one long page" href="onepage.html"><img src="images/chain.png" border="0" /></a><a target="_blank" title="Display printable page" href="printable.php"><img src="images/print_it.png" border="0" /></a></div>
85 <H2>Clonezilla-SysRescCD</H2>
86 <H3>Welcome</H3>
87 <div style="margin:0; padding: 3px; width: 980; position relative;">
88 <div style="position: absolute; left: 0px;"><H4>30/06/2011 - v 3.2.0</H4></div>
89 <div style="position: absolute; right: 0px;"><H4>Last update: 22/06/2011</H4></div>
90 </div>
91 </div>
92 <div id="linkline">
93 <a class="here" href="index.html">Home</a>
94 <a href="news.php">News</a>
95 <a href="doc.html">Documentation</a>
96 <a href="download.html">Download</a>
97 <a href="screenshots.html">Screenshots</a>
98 <a href="index.html#credits">Credits</a>
99 <a href="help.html">Help</a>
100
101 <div id="rss">
102 <a href="clonezilla-sysresccd.rss"><img src="images/rss-orange-11.png" width="30" height="14" border="0"/></a>
103 </div>
104
105 </div>
106 <div id="contarea">
107 <div id="content">
108 <a name="index-top"></a>
109 <H2 style="margin-top: 0; font-size: 2em;"><a name="index-what"></a>What is it all about? <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2> <p><b>Clonezilla-SysRescCD</b> is a Linux multi boot backup/restore and rescue CD, combining <a href="http://www.clonezilla.org/" target="_blank">Clonezilla Live</a> and <a href="http://www.sysresccd.org/Main_Page" target="_blank">System Rescue CD</a> in one CD. It is released under the <b>GNU General Public License (GPL)</b>.</p>
110 <p>Why one more Linux live CD? you might ask<br><br>
111 Well, I started this project because I wanted to have a rescue CD that would be as self-contained as possible, using my favorite tools. My goals are to have:</p>
112 <ul>
113 <li><b>A backup/restore system</b><br>I have chosen <a href="http://www.clonezilla.org/" target="_blank">Clonezilla Live</a> for this, as it is flexible enough to fulfill my needs. Furthermore, it makes it possible to create automated restore CDs/DVDs. This way, restoring a system will be fast and easy enough for anyone to perform (even people with minimum technical knowledge).</li>
114 <li><b>A rescue system</b><br>I have chosen <a href="http://www.sysresccd.org/Main_Page" target="_blank">SystemRescueCD</a> for this, as it is generally highly appreciated.<br>
115 <br>
116 <b>SystemRescueCD</b> is a live CD with a GUI, based on <a href="http://www.gentoo.org/" target ="_blank">gentoo</a>, which provides tools like <a href="http://gparted.sourceforge.net/" target ="_blank">GParted</a>, the graphical partition tool, <a href="http://www.gnu.org/software/parted/index.shtml" target ="_blank">GNU-Parted</a>, an excellent text based partitioning tool, <a href="http://www.cgsecurity.org/wiki/TestDisk" target ="_blank">TestDisk</a>, a data recovery tool, <a href="http://www.clamav.net/" target ="_blank">Clam-AntiVirus</a>, a free Anti-Virus sofware, <a href="http://www.partimage.org/Main_Page" target ="_blank">Partimage</a>, <a href="http://www.python.org" target ="_blank">Python</a>, <a href="http://www.perl.org" target ="_blank">Perl</a>, file system, networking and archiving tools, editors etc.
117 </li>
118 <li><b>Both of them in just one disk</b><br>The only way to do this was to create a Multi Boot CD.</li>
119 </ul>
120 <H2><a name="enhanced"></a>Enhanced features <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2> <p>Enhancements to <b>Clonezilla Live</b></p> <ul> <li><a class="void" href="restore.html#auto">Automated restore DVDs</a> can be easily created, so that anybody can perform a system restore operation (even people with minimum technical knowledge). All the necessary files for the creation of the DVD are included in <b>Clonezilla-SysRescCD</b>.</li> <li>A set of <a class="void" href="reloc-img.html">shell scripts</a> make it easier to restore an image file to a location (disk or partition) different than the one originally backed up.</li> </ul> <p>Other enhancements</p> <ul> <li>Part of <b>Clonezilla-SysRescCD's</b> web site is included <a class="void" href="help.html">in the CD</a>, so that help is always available.</li> </ul>
121
122 <H2><a name="versions"></a>Versions <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>
123 <!--<p><b>create-clonezilla-sysresccd's</b> version number has nothing to do with its development status. It has to do with the versions of the original ISO/CDs used at release time. So this is what we have for release:</p>
124 <table style="margin-right:20pt;margin-left: 10pt">
125 <tr>
126 <td valign="top" align="right"><font color="Blue">0.1</font></td>
127 <td width="10"></td>
128 <td> first release of the program</td>
129 </tr>
130 <tr>
131 <td valign="top" align="right"><font color="Blue">0.1</font><font color="Red">.1</font></td>
132 <td width="10"></td>
133 <td> first maintenance release of version 0.1<br> It uses the original ISO files used in release 0.1</td>
134 </tr>
135 <tr><td align="right">...</td></tr>
136 <tr>
137 <td valign="top" align="right"><font color="Blue">0.2</font></td>
138 <td width="10"></td>
139 <td>A new version of one of the original ISO files has been released<br>The program may have not been changed</td>
140 </tr>
141 </table>
142 <p></p>-->
143 <table class="bordertable" cellpadding="5">
144 <tr><td class="bordertable" colspan="4"><b>Release table</b></td></tr>
145 <tr><td class="bordertable" valign="top"><b>Date</b></td><td class="bordertable" valign="top"><b>Version</b></td>
146 <td class="bordertable" valign="top"><b>Clonezilla Live Version</b></td><td class="bordertable" valign="top"><b>SystemRescueCD Version</b></td></tr>
147 <tr><td class="bordertable" >XX/XX/10</td><td class="bordertable" >3.2.0</td><td class="bordertable" >1.2.8-46&nbsp;(mod)</td><td class="bordertable" >2.1.1</td>
148 <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>
149 </tr>
150 <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>
151 </tr>
152 <tr><td class="bordertable" >11/04/08</td><td class="bordertable" >2.5.0</td><td class="bordertable" >1.0.10-8&nbsp;(mod)</td><td class="bordertable" >1.0.1&nbsp;(mod)</td>
153 <tr><td class="bordertable" >24/03/08</td><td class="bordertable" >2.4.0</td><td class="bordertable" >1.0.9-19&nbsp;(mod)</td><td class="bordertable" >1.0.0&nbsp;(mod)</td>
154 </tr>
155 <tr><td class="bordertable" >07/03/08</td><td class="bordertable" >2.3.0</td><td class="bordertable" >1.0.9-10&nbsp;(mod)</td><td class="bordertable" >1.0.0&nbsp;(mod)</td>
156 </tr>
157 <tr><td class="bordertable" >22/02/08</td><td class="bordertable" >2.2.0</td><td class="bordertable" >1.0.9-10&nbsp;(mod)</td><td class="bordertable" >0.4.3&nbsp;(mod)</td>
158 </tr>
159 <tr><td class="bordertable" >22/01/08</td><td class="bordertable" >2.1.0</td><td class="bordertable" >1.0.7-18&nbsp;(mod)</td><td class="bordertable" >0.4.3&nbsp;(mod)</td>
160 </tr>
161 <tr><td class="bordertable" >11/12/07</td><td class="bordertable" >1.4.0</td><td class="bordertable" >1.0.7-18&nbsp;(mod)</td><td class="bordertable" >0.4.2&nbsp;(mod)</td>
162 </tr>
163 <tr><td class="bordertable" >03/11/07</td><td class="bordertable" >1.3.0</td><td class="bordertable" >1.0.5-8&nbsp;(mod)</td><td class="bordertable" >0.4.1&nbsp;(mod)</td>
164 </tr>
165 <tr><td class="bordertable" >07/10/07</td><td class="bordertable" >1.2.0</td><td class="bordertable" >1.0.5-8&nbsp;(mod)</td><td class="bordertable" >0.4.0&nbsp;(mod)</td>
166 </tr>
167 <tr><td class="bordertable" >24/09/07</td><td class="bordertable" >1.1.0</td><td class="bordertable" >1.0.5-7&nbsp;(mod)</td><td class="bordertable" >0.3.8&nbsp;(mod)</td>
168 </tr>
169 <tr><td class="bordertable" >06/09/07</td><td class="bordertable" >1.0.0</td><td class="bordertable" >1.0.3-21&nbsp;(mod)</td><td class="bordertable" >0.3.8&nbsp;(mod)</td>
170 </tr>
171 <tr><td class="bordertable" >12/08/07</td><td class="bordertable" >0.2</td><td class="bordertable" >1.0.3-21&nbsp;(mod)</td><td class="bordertable" >0.3.7&nbsp;(mod)</td></tr>
172 <tr><td class="bordertable" >24/07/07</td><td class="bordertable" >0.1.1</td><td class="bordertable" >1.0.3-18</td><td class="bordertable" >0.3.7</td>
173 <tr><td class="bordertable" >23/07/07</td><td class="bordertable" >0.1</td><td class="bordertable" >1.0.3-18</td><td class="bordertable" >0.3.7</td></tr>
174 </table>
175 <H2><a name="changelog"></a>Changelog <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>
176 <table class="bordertable" cellpadding="5">
177 <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>
178 <tr><td class="bordertable" width="10" valign="top"><a name="3.2.0"></a>3.2.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">
179 -&nbsp;<b>Clonezilla Live</b> updated to version 1.2.8-46<br>
180 -&nbsp;<b>SystemRescueCD</b> updated to version 2.1.1<br>
181 -&nbsp;Fixed the splash image installation bug present in 3.1.0<br>
182 &nbsp;&nbsp;Also, a filename relative to /home/partimag, can now be used<br>
183 -&nbsp;Script imginfo can display extended info (command line parameter -e)<br>
184 &nbsp;&nbsp;Extended info is: image size and disk model<br>
185 </td></tr>
186 <tr><td class="bordertable" width="10" valign="top"></td><td class="bordertable" width="10" valign="top">Package</td><td class="bordertable">
187 -&nbsp;Added -d command parameter to scrpit create-clonezilla-sysresccd<br>
188 &nbsp;&nbsp;This way the temporary and output folder can be specified<br>
189 -&nbsp;Using $HOME instead of /root in scrpit create-clonezilla-sysresccd<br>
190 -&nbsp;Script create-clonezilla-sysrescc can now download the original<br>
191 &nbsp;&nbsp;ISO files (parameter -g), making easier to build Clonezilla-SysRescCD
192 </td></tr>
193 <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">
194 -&nbsp;<b>Clonezilla Live</b> updated to version 1.2.5-35<br>
195 -&nbsp;<b>SystemRescueCD</b> updated to version 1.6.0<br>
196 - Three <b>Clonezilla-SysRescCD</b> flavours are now available,<br>
197 &nbsp;&nbsp;one for each architecture (<a href="download.html#download-file" target="_blank">more information</a>)<br>
198 -&nbsp;<b>Super Grub Disk</b> updated to version 0.9799<br>
199 -&nbsp;Added <b>Super Grub Disk 2</b> version 1.98s<br>
200 -&nbsp;<b>Smart Boot Manager</b> was added to the Tools section<br>
201 -&nbsp;Added restorecd/ and docs/ to the squashfs file of Clonezilla distro.<br>
202 &nbsp;&nbsp;This way all items are always available (even when booting to RAM)<br>
203 -&nbsp;Most operations are now executed through the TUI (Text User Interface)<br>
204 -&nbsp;Major site and documentation update (thanks to Jyrki Vesterinen)
205 </td></tr>
206 <tr><td class="bordertable" width="10" valign="top"></td><td class="bordertable" width="10" valign="top">Package</td><td class="bordertable">
207 -&nbsp;Added auto mode (parameter -a) to script create-clonezilla-sysresccd
208 </td></tr>
209 <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">
210 -&nbsp;<b>Clonezilla Live</b> updated to version 1.1.0-8<br>
211 -&nbsp;<b>SystemRescueCD</b> updated to version 1.0.4<br>
212 -&nbsp;<b>Super Grub Disk</b> updated to version 0.9726
213 </td></tr>
214 <tr><td class="bordertable" width="10" valign="top"><a name="2.5.0"></a>2.5.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">
215 -&nbsp;<b>Clonezilla Live</b> updated to version 1.0.10-8<br>
216 -&nbsp;<b>SystemRescueCD</b> updated to version 1.0.1<br>
217 -&nbsp;<b>Super Grub Disk</b> updated to version 0.9701
218 </td></tr>
219 <tr><td class="bordertable" width="10" valign="top"><a name="2.4.0"></a>2.4.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">
220 -&nbsp;<b>Clonezilla Live</b> updated to version 1.0.9-19<br>
221 </td></tr>
222 <tr><td class="bordertable" width="10" valign="top"><a name="2.3.0"></a>2.3.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">
223 -&nbsp;<b>SystemRescueCD</b> updated to version 1.0.0<br>
224 -&nbsp;Added two command line parameters to <b>ocs-iso</b>, used in auto restore DVD<br>
225 &nbsp;&nbsp;mastering. More info: <a href="restore.html#usbKeyboard">Working with a USB keyboard</a>
226 </td></tr>
227 <tr><td class="bordertable" width="10" valign="top"></td><td class="bordertable" width="10" valign="top">Package</td><td class="bordertable">
228 -&nbsp;Fixed the <b>create-clonezilla-sysresccd</b> installation problem<br>
229 &nbsp;&nbsp;Thanks to Chris Rehder</td></tr>
230 <tr><td class="bordertable" width="10" valign="top"><a name="2.2.0"></a>2.2.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">
231 -&nbsp;<b>Clonezilla Live</b> updated to version 1.0.9-10<br>
232 -&nbsp;Updated script <b>reloc-img</b> to support remote images (through samba and nfs)
233 </td></tr>
234 <tr><td class="bordertable" width="10" valign="top"></td><td class="bordertable" width="10" valign="top">Package</td><td class="bordertable">
235 -&nbsp;Added <b>patch-clonezilla-sysresccd</b>, a script that can be used to<br>
236 &nbsp;&nbsp;customize an existing <b>Clonezilla-SysRescCD</b> ISO file<br>
237 &nbsp;&nbsp;More info: <a href="custom-cd.html#custom-patch">Using patch-clonezilla-sysresccd</a></td></tr>
238 <tr><td class="bordertable" width="10" valign="top"><a name="2.1.0"></a>2.1.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">
239 -&nbsp;<b>SystemRescueCD</b> updated to version 0.4.3<br>
240 -&nbsp;<b>Super Grub Disk</b> updated to version 0.9677
241 </td></tr>
242 <tr><td class="bordertable" width="10" valign="top"><a name="1.4.0"></a>1.4.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">
243 -&nbsp;A script to help relocate a Clonezilla image file during restoration<br>
244 &nbsp;&nbsp;hase been added to Clonezilla Live. The script (called <b>reloc-img</b>) uses<br>
245 &nbsp;&nbsp;a curses like interface, which is similar to Clonezilla's interface<br>
246 <br>
247 More info: <a href="reloc-img.html">Restoring to a different location</a>
248 </td></tr>
249 <tr><td class="bordertable" width="10" valign="top"><a name="1.3.0"></a>1.3.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">
250 -&nbsp;Changed the splash screen tool selection interface<br>
251 &nbsp;&nbsp;A navigation menu scheme has been adopted<br>
252 -&nbsp;Removed <b>ranish.img</b> from the CD<br>
253 &nbsp;&nbsp;The <a href="http://www.ranish.com/part/" target="_blank">Ranish Partition Manager</a> has been integrated into <a href="http://www.freedos.org/" target="_blank">FreeDos</a><br>
254 &nbsp;&nbsp;This is because of the fact that Ranish Partition Manager would not<br>
255 &nbsp;&nbsp;execute as a standalone floppy image<br>
256 -&nbsp;Added <a href="http://www.supergrubdisk.org/" target="_blank">Super Grub Disk</a> to the available tools<br>
257 &nbsp;&nbsp;The floppy image provided by "Super Grub Disk" (english version) <br>
258 &nbsp;&nbsp;has been added to the source tarball<br>
259 -&nbsp;Script <b>continue-multi-cd</b> (SysRescCD) updated to v 2.0.0<br>
260 &nbsp;&nbsp;Use "continue-multi-cd -h" to see the new interface<br>
261 -&nbsp;Fixed a minor bug in script <b>what-cd</b>
262 </td></tr>
263 <tr><td class="bordertable" width="10" valign="top"></td><td class="bordertable" width="10" valign="top">Package</td><td class="bordertable">
264 -&nbsp;All the files needed for CD creation have been included in the<br>
265 &nbsp;&nbsp;source tarball. This way the user will only have to download the<br>
266 &nbsp;&nbsp;debian live ISO file, in order to create Clonezilla-SysRescCD.<br>
267 &nbsp;&nbsp;The debian live ISO file has not been included because of its size<br>
268 &nbsp;&nbsp;(~ 79 MB), which would make the source tarball too big.<br>
269 &nbsp;&nbsp;The files can be fount in <b>/root/.clonezilla-sysresccd/files</b><br>
270 -&nbsp;All cfg files have been moved to <b>/root/.clonezilla-sysresccd/files</b><br>
271 &nbsp;&nbsp;If you are upgrading from a previous version, please delete/move<br>
272 &nbsp;&nbsp;these files, and <u>adjust</u> your configuration files (conf files)<br>
273 -&nbsp;A new variable has been inserted to the configuration files (named<br>
274 &nbsp;&nbsp;<b>DebianLiveFolder</b> in <b>clonezilla-sysresccd.conf</b> and <b>DebianLiveFolderP</b><br>
275 &nbsp;&nbsp;in <b>profiles.conf</b>). This variable should point to the folder where<br>
276 &nbsp;&nbsp;the debian live ISO has been saved. If you are upgrading from a<br>
277 &nbsp;&nbsp;previous version, please <u>adjust</u> your configuration files (conf files)<br>
278 -&nbsp;Added support to script <b>create-clonezilla-sysresccd</b> for compressed<br>
279 &nbsp;&nbsp;(tar.gz) isolinux configuration files, in order to implement menus
280 </td></tr>
281 <tr><td class="bordertable" width="10" valign="top">1.2.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">-&nbsp;Added script <b>continue-multi-cd</b> to <b>SystemRescueCD</b><br>
282 &nbsp;&nbsp;This script makes it easy to continue a multi session CD
283 </td></tr>
284 <tr><td class="bordertable" width="10" valign="top">1.1.0</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">-&nbsp;Minor changes (cfg files)
285 </td></tr>
286 <tr><td class="bordertable" width="10" valign="top">1.0.0</td><td class="bordertable" width="10" valign="top">-</td><td class="bordertable">
287 -&nbsp;Moved to version 1.0.0 in order to eliminate any missunderstanding about<br>
288 &nbsp;&nbsp;the development status of Clonezilla-SysRescCD
289 </td></tr>
290 <tr><td class="bordertable" width="10" valign="top"></td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">
291 -&nbsp;Added the options -A and -W to script ocs-iso (Clonezilla Live).<br>
292 &nbsp;&nbsp;&nbsp;&nbsp; Syntax:<br>
293 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /opt/drbl/sbin/ocs-iso -A "ocs-rs command"<br>
294 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; /opt/drbl/sbin/ocs-iso -W "ocs-rs command" [image file]<br>
295 &nbsp;&nbsp;Both options set up the restore CD/DVD for automatic image restoration.<br>
296 &nbsp;&nbsp;The difference is that when using the -W option the image [image file] is <br>
297 &nbsp;&nbsp;appended in the ISO file (maximum 4.4BG). When -A is used, the image<br>
298 &nbsp;&nbsp;file will be appended to the CD/DVD, after the ISO file created by this<br>
299 &nbsp;&nbsp;command is burnt, using growisofs -M ... (maximum 8GB).<br>
300 -&nbsp;Added the option -O to script ocs-iso (Clonezilla Live).<br>
301 &nbsp;&nbsp;Specifies the ISO file name to use when -A, -W options are used.<br>
302 -&nbsp;Added the options -V and -P to script ocs-iso (Clonezilla Live).<br>
303 &nbsp;&nbsp;The user creating a restore CD/DVD can now specify its Volume ID and<br>
304 &nbsp;&nbsp;Publisher ID, respectively.<br>
305 -&nbsp;Added the option -I to script ocs-iso (Clonezilla Live).<br>
306 &nbsp;&nbsp;Specifies the user selectable menu item title of the main screen of a<br>
307 &nbsp;&nbsp;restore CD/DVD. Applicable only with options -W and -A<br>
308 -&nbsp;Added the script what-cd to sysresccd.<br>
309 &nbsp;&nbsp;This script will identify the CDs present on a pc, and report the<br>
310 &nbsp;&nbsp;device name of the writer (if any)<br>
311 -&nbsp;Added a copy of the Clonezilla-SysRescCD site to the CD. In this way <br>
312 &nbsp;&nbsp;the documentation will be available at all times
313 </td></tr>
314 <tr><td class="bordertable" width="10" valign="top"></td><td class="bordertable" width="10" valign="top">Package</td><td class="bordertable">
315 -&nbsp;Added -x [script] option<br>
316 &nbsp;&nbsp;This way you can write a BASH script that will be executed just<br>
317 &nbsp;&nbsp;before mastering the "Clonezilla-SysRescCD"
318 </td></tr>
319 <tr><td class="bordertable" width="10" valign="top">0.2</td><td class="bordertable" width="10" valign="top">CD</td><td class="bordertable">
320 -&nbsp;clonezilla-sysresccd contains customized versions of the original CDs<br>
321 &nbsp;&nbsp;More info in page <a href="custom-cd.html" title=" How to create the custom CDs ">Custom&nbsp;CDs</a>
322 </td></tr>
323 <tr><td class="bordertable" width="10" valign="top"></td><td class="bordertable" width="10" valign="top">Package</td><td class="bordertable">
324 -&nbsp;Fixed a bug that would appear when option -b would be used without any<br>
325 &nbsp;&nbsp;other options. Then create-clonezilla-sysresccd would not be able to get the <br>
326 &nbsp;&nbsp;ISO file name
327 </td></tr>
328 <tr><td class="bordertable" width="10" valign="top">0.1.1</td><td class="bordertable" width="10" valign="top">Package</td><td class="bordertable">
329 -&nbsp;Build system upgrade<br>
330 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;use <b>./configure</b> to upgrade the program<br>
331 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;use <b>./configure --enable-fullInstall</b> to install it<br>
332 -&nbsp;Fixed a potential script installation bug<br>
333 -&nbsp;Normal user can get help<br>
334 -&nbsp;Minor changes
335 </td></tr>
336 <tr><td class="bordertable" width="10">0.1</td><td class="bordertable" width="10"></td><td class="bordertable">-&nbsp;Initial release</td></tr>
337 </table>
338 <!--
339 <H2><a name="download"></a>Download <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>
340 <p>
341 <!--Whenever possible I will provide a link to the CD created using profile 0 (full CD)<br><br>
342 Installation package: <a href="http://clonezilla-sysresccd.hellug.gr/create-clonezilla-sysresccd-3.2.0".tar.gz" target="_blank">create-clonezilla-sysresccd-3.2.0.tar.gz</a> [~ 6.2 MB]<br>
343 <!--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>
344 ISO file: <a href="http://clonezilla-sysresccd.hellug.gr/clonezilla-sysresccd-full-mod-3.2.0.iso" target="_blank">clonezilla-sysresccd-full-mod-3.2.0.iso</a> [~ ISO_SIZEB]<br>
345 md5sum file: <a href="http://clonezilla-sysresccd.hellug.gr/md5sum.txt" target="_blank">md5sum.txt</a><br><br>
346 ISO file md5sum: <b><i>"MD5SUM"</i></b></p>
347 -->
348 <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>
349 <p>Yes, of course you can. If you have:</p>
350 <ul style="margin-right: 30pt;">
351 <li>a script I can add to <b>Clonezilla Live</b> or <b>SystemRescueCD</b>, don't hesitate to send it to me.<br>
352 You can have a look at "<a href="own-scripts.html">Clonezilla-SysRescCD own scripts</a>" to see what type of scripts might be interesting.</li>
353 <li>used <b>Clonezilla Live</b> nfs mode, or any of the tools provided by <b>SystemRescueCD</b>, you can write a guide.<br>
354 I will add it to the site (and the documentation present on the CD). Please keep in mind that this CD may be used by less experienced users, so make it as detailed as possible.</li>
355 </ul>
356 <H2><a name="contact"></a>Contact us <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>
357 <p>If there's anything you want to say about <b>Clonezilla-SysRescCD</b>, go ahead and <a href="mailto:&#115;&#110;&#103;&#064;&#104;&#101;&#108;&#108;&#117;&#103;&#046;&#103;&#114;?subject=About Clonezilla-SysRescCD v 3.2.0" title="About Clonezilla-SysRescCD">send me (Spiros)</a> a message. If there's anything you have to say about the <b>documentation</b> in particular, you can contact <a href="mailto:&#115;&#097;&#110;&#100;&#103;&#116;&#120;&#064;&#103;&#109;&#097;&#105;&#108;&#046;&#099;&#111;&#109;?subject=About Clonezilla-SysRescCD v 3.2.0 documentation" title="About Clonezilla-SysRescCD Documentation">Jyrki</a> directly.</p>
358 <H2><a name="lists"></a>Mailing lists <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>
359 <p>There are two mailing lists available for <b>Clonezilla-SysRescCD</b>:</p>
360 <ul>
361 <li><a href="http://lists.hellug.gr/mailman/listinfo/clonezilla-sysresccd-announce" target="_blank">Clone-sysresccd-announce</a><br>This is the <b>Clonezilla-SysRescCD</b> new releases announcement list. Please do not post there.</li>
362 <li><a href="http://lists.hellug.gr/mailman/listinfo/clonezilla-sysresccd-general" target="_blank">Clone-sysresccd-general</a><br>This is the general discussion list of <b>Clonezilla-SysRescCD</b>.<br>
363 If you have any questions about Clonezilla Live, please use its <a href="http://sourceforge.net/mail/?group_id=115473" target="_blak">Mailing lists</a> or <a href="http://sourceforge.net/forum/?group_id=115473" target="_blak">Forums</a>.
364 <br>If you have any questions about SystemRescueCD, please use its <a href="http://www.sysresccd.org/forums/" target="_blak">Forums</a>.
365 </li>
366 </ul>
367 <H2><a name="license"></a>License <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>
368 <p>This project is published under the terms of <a href="http://www.gnu.org/licenses/gpl.html" target="_blank">GNU General Public License</a> as published by the <a href="http://www.fsf.org/" target="_blank">Free Software Foundation</a>.</p>
369 <H2><a name="credits"></a>Credits <span class="hideprint">[<a href="#index-top" title="go to top of the page">^</a>]</span></H2>
370 <p>I would like to thank:</p>
371 <ul>
372 <li>The creators of <b>SystemRescueCD</b> and <b>Clonezilla Live</b></li>
373 <li>Eleftherios Kosmas for publishing the v 0.1 torrent</li>
374 <li>George Keramidas and &lt;&lt;V13&gt;&gt; from the <a href="http://lists.hellug.gr/mailman/listinfo/linux-greek-users" target="_blank">linux greek users</a> mailing list, who helped fixing a bug that would make the creation of the 8GB Restore DVD impossible.</li>
375 <li>Chris Rehder for reporting the <b>create-clonezilla-sysresccd</b> installation problem in v 2.2.0 and his overall assistance</li>
376 <li>Manfred Hantl for reporting and fixing the windows USB installation problem of version 2.6.0</li>
377 <li>Everyone who seeds the torrent, as it is not possible for me to be online at all times</li>
378 </ul>
379 <p>Special thanks to</p>
380 <ul>
381 <li><b>Jyrki Vesterinen</b>, documentation contributor.<br>Most of these pages have been updated / written by him.</li>
382 </ul>
383 <a name="usb-top"></a>
384 <H2 style="font-size: 2em;"><a name="usb-intro"></a>Installation to USB made easy <span class="hideprint">[<a href="#usb-top" title="go to top of the page">^</a>]</span></H2>
385 <p>Until recently installing <b>Clonezilla-SysRescCD</b> on a USB disk would not be such a great idea, because of its size. But since USB devices become cheaper and cheaper, it is an interesting alternative.<br><br>
386 Starting with <b>version 3.1.0</b>, <b>Clonezilla-SysRescCD</b> provides an iso file that's ISO-Hybrided. This means (as we read at <a href="http://syslinux.zytor.com/wiki/index.php/Doc/isolinux#HYBRID_CD-ROM.2FHARD_DISK_MODE" target="_blank">the isolynux site</a>) that</p>
387 <p class="otherpage">"the iso file can be booted from either CD-ROM or from a device which BIOS considers a hard disk or ZIP disk, e.g. a USB key or similar. This image can then be copied using any raw disk writing tool (on Unix systems, typically "dd" or "cat") to a USB disk, or written to a CD-ROM using standard CD burning tools.<br>
388 <br>
389 The ISO 9660 filesystem is encapsulated in a partition (which starts at offset zero, which may confuse some systems.) This makes it possible for the operating system, once booted, to use the remainder of the device for persistent storage by creating a second partition."</p>
390 <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>
391 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>
392 <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>
393 <p class="newcode">umount /dev/<font color="Green">sdc4</font><br>
394 dd if=~/clonezilla-sysresccd-full-mod-3.2.0.iso of=/dev/<font color="Green">sdc</font> bs=512</p>
395 <p>And that's it. Your usb device is ready to boot!!!</p>
396 <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>
397 <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>
398 <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>
399 Incorrect use of syslinux could cause your operating system<br> (GNU/Linux / Windows) <b>not to boot</b>.<br><br> Confirm the command before you run it.<br></td></tr></table></div>
400 <p>The only thing that's important is that your USB disk must contain a VFAT (Windows 98 or DOS) file system. If this is not the case, refer to the section "<a href="#trouble">Troubleshooting</a>", to find out how you can format it, before copying files to it.<br><br>
401 The bootable USB disk creation procedure can be performed either from Linux or Windows.</p>
402 <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>
403 If you want to create a bootable USB flash drive for this version<br>
404 or later, remember to use the syslinux command from <b>syslinux<br>
405 3.71 or later</b>. Otherwise the boot menu won't work.</td></tr></table></div>
406 <H3><a name="linux"></a>Installation from Linux <span class="hideprint">[<a href="#usb-top" title="go to top of the page">^</a>]</span></H3>
407 <p>There are two ways you can proceed, if you are going to use Linux to perform the USB installation, either using a running linux box, or using <b>Clonezilla-SysRescCD</b>.<br><br>
408 I will assume that you have saved <b>clonezilla-sysresccd-full-mod-3.1.0.iso</b> in your home directory (<b><font color="Green">~</font></b>).</p>
409 <H3><a name="lin-box"></a>Using a linux box [<a href="#usb-top" title="go to top of the page">^</a>]</H3>
410 <p>If you already have a linux box up and running, you can use it to create your <b>Clonezilla-SysRescCD</b> USB, without even having to burn it to CD beforehand. The only thing here is that you have to have <a href="http://syslinux.zytor.com" target="_blank">syslinux</a> installed.<br><br>
411 I will assume that your CD drive is <b>/dev/<font color="Green">sr0</font></b> and that your USB device is <b>/dev/<font color="Green">sdc4</font></b>. You may have to change any of them to reflect your system configuration.<br><br>
412 Boot into linux, connect your USB device and execute the following commands:</p>
413 <p class="newcode">mkdir /mnt/mycd<br>
414 mount <font color="Green">~</font>/clonezilla-sysresccd-full-mod-3.1.0.iso /mnt/mycd -o loop<br>
415 mkdir /mnt/usbdevice<br>
416 mount /dev/<font color="Green">sdc4</font> /mnt/usbdevice<br>
417 cp -r /mnt/mycd/* /mnt/usbdevice<br>
418 umount /mnt/mycd; rmdir /mnt/mycd<br>
419 cd /mnt/usbdevice<br>
420 cp syslinux/*.cfg isolinux<br>
421 cp syslinux/*.png isolinux<br>
422 rm -rf syslinux<br>
423 mv isolinux syslinux</p>
424 <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>
425 Since you are using any linux box to complete this procedure,<br>you have to use the syslinux installation provided by this linux box.<br><br>Otherwise, you will probably end up with an unbootable device...</td></tr></table></div>
426 <p>First thing you have to do is find where syslinux is installed. The best way to do that is look for a file named <b>vesamenu.c32</b>. You can use locate, find, or any other distribution specific tool for that. In Debian (and its derivatives like Ubuntu, LMDE etc.) this file is under <font color="Green"><b>/usr/lib/syslinux</b></font>, so I'll just use that for the following code.</p>
427 <p class="newcode">cd syslinux<br>
428 for f in *.c32<br>
429 do<br>
430 cp -v <font color="Green"><b>/usr/lib/syslinux</b></font>/$f .<br>
431 cd ..<br>
432 done</p>
433 <p>In either case, unmount the device and delete the mount point (directory).</p>
434 <p class="newcode">cd; umount /dev/<font color="Green">sdc4</font><br>
435 rmdir /mnt/usbdevice</p>
436 <p>Finally make your USB device bootable, by executing</p>
437 <p class="newcode">syslinux /dev/<font color="Green">sdc4</font></p>
438 <p>and you are done.</p>
439 <H4><a name="lin-sys"></a>Using Clonezilla-SysRescCD [<a href="#usb-top" title="go to top of the page">^</a>]</H4>
440 <p>If you already burnt <b>Clonezilla-SysRescCD</b> to CD, you can use it to create your <b>Clonezilla-SysRescCD</b> USB.<br><br>
441 I will assume that your CD drive is <b>/dev/<font color="Green">sr0</font></b> and that your USB device is <b>/dev/<font color="Green">sdc4</font></b>. You may have to change any of them to reflect your system configuration.<br><br>
442 Boot <b>SystemRescueCD </b> using the option <b>To RAM</b>, and when it is fully loaded, execute the following commands:</p>
443 <p class="newcode">mkdir /mnt/mycd<br>
444 mount /dev/<font color="Green">sr0</font> /mnt/mycd <br>
445 mkdir /mnt/usbdevice<br>
446 mount /dev/<font color="Green">sdc4</font> /mnt/usbdevice<br>
447 cp -rv /mnt/mycd/* /mnt/usbdevice<br>
448 umount /mnt/mycd<br>
449 cd /mnt/usbdevice<br>
450 cp syslinux/*.cfg isolinux<br>
451 cp syslinux/*.png isolinux<br>
452 rm -rf syslinux<br>
453 mv isolinux syslinux<br>
454 cd; umount /dev/<font color="Green">sdc4</font></p>
455 <p>Finally make your USB device bootable, by executing</p>
456 <p class="newcode">syslinux /dev/<font color="Green">sdc4</font></p>
457 <p>and you are done.</p>
458 <H3><a name="windows"></a>Installation from Windows <span class="hideprint">[<a href="#usb-top" title="go to top of the page">^</a>]</span></H3>
459 <p>Installing <b>Clonezilla-SysRescCD</b> from Windows is as easy as it is in Linux. You have to burn <b>Clonezilla-SysRescCD</b> to CD or use a CD/DVD ROM emulator software like <a href="http://www.daemon-tools.cc/dtcc/announcements.php" target="_blank">Daemon Tools</a> to mount the ISO file.<br><br>
460 I will assume that your USB device is drive <b><font color="Green">K:</font></b> and your CD drive or mounted ISO file is drive
461 <b><font color="Green">D:</font></b>. You may have to change any of them, in order to reflect your system configuration.<br><br>
462 You will have to</p>
463 <ul>
464 <li>Copy all files from drive <b><font color="Green">D:</font></b> (CD or mounted ISO file) to drive <b><font color="Green">K:</font></b> (USB disk)</li>
465 <li>Copy <b><u>all</u> cfg</b> files from <b><font color="Green">K:\</font>syslinux</b> to <b><font color="Green">K:\</font>isolinux</b></li>
466 <li>Copy <b><u>all</u> png</b> files from <b><font color="Green">K:\</font>syslinux</b> to <b><font color="Green">K:\</font>isolinux</b></li>
467 <li>Delete the folder <b><font color="Green">K:\</font>syslinux</b></li>
468 <li>Rename <b><font color="Green">K:\</font>isolinux</b> to <b><font color="Green">K:\</font>syslinux</b></li>
469 </ul>
470 <p>Now all you have to do is make your USB disk bootable. In order to do that you have to open a DOS window (in Windows XP press "<b>Start / Run </b>" and type <b>cmd</b>). Then type at DOS prompt:</p>
471 <p class="newcode"><font color="Green">K:</font><br>
472 cd utils/bootprog<br>
473 syslinux -ma <font color="Green">K:</font></p>
474 <H3><a name="booting"></a>Booting from USB <span class="hideprint">[<a href="#usb-top" title="go to top of the page">^</a>]</span></H3>
475 <p>Before trying to boot from your USB device, you have to set your boot device at your BIOS. This means you have to reboot having your USB device connected, get into your BIOS (usually pressing DEL) and make the appropriate settings in the BOOT section.<br><br>
476 Booting <b>Clonezilla Live</b> should not be a problem. Just select the desired option and press ENTER to boot.<br><br>
477 Booting <b>SystemRescueCD</b> has been made equally simple with <b>SystemRescueCD v 1.0.0</b>, so you shouldn't have any problem (option <b>cdroot</b> is not required any more).<br><br>
478 If you have any problems here, you may try adding any of these boot parameters:</p>
479 <p class="newcode">usbstick<br>
480 doscsi</p>
481 <H3><a name="trouble"></a>Troubleshooting <span class="hideprint">[<a href="#usb-top" title="go to top of the page">^</a>]</span></H3>
482 <p>Whether you can successfully boot from a USB disk or not, depends mainly on your BIOS. Chances are that you will not be able to boot on an old computer, with an old (and possibly buggy) BIOS. So I would recommend testing your <b>Clonezilla-SysRescCD USB</b> on a new computer.</p>
483 <ul>
484 <li><p style="margin-left: 0;"><b>I can't boot (I don't even see the splash screen)</b><br>
485 or <b>Clonezilla Live does not boot</b><br>
486 The first thing you should do is double check your BIOS settings. Reboot having your USB device connected, get into your BIOS (usually pressing DEL) and make the appropriate settings in the BOOT section.<br><br>
487 If you are on linux, check that the partition on the USB disk is active (bootable), executing:</p>
488 <p class="newcode" style="margin-left: 0;">fdisk -l /dev/<font color="Green">sdc</font></p>
489 <p style="margin-left: 0;">You should get something similar to this:</p>
490 <p class="newcode">
491 Disk <font color="Green">/dev/sdc</font>: 4043 MB, 4043309056 bytes<br>
492 125 heads, 62 sectors/track, 1018 cylinders, total 7897088 sectors<br>
493 Units = sectors of 1 * 512 = 512 bytes<br>
494 Sector size (logical/physical): 512 bytes / 512 bytes<br>
495 I/O size (minimum/optimal): 512 bytes / 512 bytes<br>
496 Disk identifier: 0x596bbd85<br>
497 <br>
498 &nbsp;&nbsp;&nbsp;Device&nbsp;<font color="Red">Boot</font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Start&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;End&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Blocks&nbsp;&nbsp;&nbsp;Id&nbsp;&nbsp;System<br>
499 /dev/sdc1&nbsp;&nbsp;&nbsp;<font color="Red">*</font>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;63&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1461914&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;730926&nbsp;&nbsp;&nbsp;&nbsp;b&nbsp;&nbsp;W95&nbsp;FAT32
500 </p>
501 <p style="margin-left: 0;"><br>If the partition is not active (<b>no asterisk</b>), execute:</p>
502 <p class="newcode" style="margin-left: 0;">fdisk /dev/<font color="Green">sdc</font></p>
503 <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>
504 If you are on Windows, this is taken care of by syslinux (parameters -ma).<br><br>
505 If you still have problems booting, you should try to execute</p>
506 <p class="newcode" style="margin-left: 0;">syslinux -s /dev/<font color="Green">sdc4</font></p>
507 <p style="margin-left: 0;">from Linux, or</p>
508 <p class="newcode" style="margin-left: 0;">syslinux -sma <font color="Green">K:</font></p>
509 <p style="margin-left: 0;">from Windows (from folder <b><font color="Green">K:</font>syslinux</b>).<br><br>
510 syslinux man page reads:</p>
511 <p class="otherpage" style="margin-left: 0px;"><b>(Option) -s</b><br>
512 Install a "safe, slow and stupid" version of syslinux. This version may work <br>
513 on some very buggy BIOSes on which syslinux would otherwise fail. If you find <br>
514 a machine on which the -s option is required to make it boot reliably, please <br>
515 send as much info about your machine as you can, and include the failure mode.</p></li>
516 <li><p style="margin-left: 0;"><b>I still can't boot</b><br>
517 In this case you will have to format your USB disk.<br><br>
518 If you are using linux to perform the installation, execute the command:</p>
519 <p class="newcode" style="margin-left: 0;">mkdosfs -F 16 /dev/<font color="Green">sdc4</font></p>
520 <p style="margin-left: 0;">to create a FAT16 file system, or</p>
521 <p class="newcode" style="margin-left: 0;">mkdosfs -F 32 /dev/<font color="Green">sdc4</font></p>
522 <p style="margin-left: 0;">to create a FAT32 file system.<br><br>
523 When you are done go back to section "<a href="#linux">Installation from Linux</a>".<br><br>
524 If you are on Windows, you should download the <a href="http://h50178.www5.hp.com/local_drivers/17550/SP27608.exe" target="_blank">HP-USB Format tool</a>, install it and format your USB drive using the Fat or Fat32 option. This program can be used to format USB devices that won't boot properly when formatted with Windows format tool.<br><br>
525 When you are done go back to section "<a href="#windows">Installation from Windows</a>".</p></li>
526 <li><b>I still can't boot (after formating)</b><br>
527 Things are getting tough!!! Try to format your USB disk using the option you did not use previously. So, if you have created a FAT32 file system, create a FAT16 file system this time, and recreate <b>Clonezilla-SysRescCD</b> on USB.<br><br>
528 If nothing works, you are out of luck; you will not be able to use <b>Clonezilla-SysRescCD USB</b> on this computer... If you do manage to boot it, please <a href="mailto:&#115;&#110;&#103;&#064;&#104;&#101;&#108;&#108;&#117;&#103;&#046;&#103;&#114;?subject=Success booting Clonezilla-SysRescCD v 3.1.0 USB">send me</a> a message.</li>
529 <li><b>SystemRescueCD does not boot</b><br>
530 Ok, you have managed to get to the splash screen and successfully booted <b>Clonezilla Live</b>. But you still can't boot <b>SystemRescueCD</b>.<br><br>
531 Refer to section <a href="#booting">Booting from USB</a> to find out the boot parameters you can use with <b>SystemRescueCD</b>.
532 </li>
533 </ul>
534 <H3><a name="cfg"></a>Customizing sysresc.cfg <span class="hideprint">[<a href="#usb-top" title="go to top of the page">^</a>]</span></H3>
535 <p>As stated previously, <b>Clonezilla-SysRescCD USB</b> is booted by <b>syslinux</b> through its configuration file <b>syslinux.cfg</b>. This file loads <b>sysresc.cfg</b> in order to boot <b>SystemRescueCD</b>.<br><br>
536 If you have to specify any additional boot parameters for <b>SystemRescueCD</b>, you may want to write these changes to the configuration file, so that you don't have to insert them by hand every time.<br><br>
537 The procedure to do that is the following:<br><br>
538 Boot <b>SystemRescueCD</b> (or if that's not possible yet, boot <b>Clonezilla Live</b> and get to the command line) using the option <b>To RAM</b>, and when it is fully loaded, execute the following commands:</p>
539 <p class="newcode">mkdir /mnt/usbdevice<br>
540 mount /dev/<font color="Green">[device]</font> /mnt/usbdevice <br>
541 cd /mnt/usbdevice<br>
542 cp sysresc.cfg sysresc.bak<br>
543 sed 's|<font color="Red">scandelay=5</font>|<font color="Red">scandelay=<font color="Green">x</font> [additional params]</font>|' \<br>
544 sysresc.cfg &gt; sys.cfg<br>
545 mv sys.cfg sysresc.cfg<br>
546 cd; umount /dev/<font color="Green">[device]</font><br>
547 syslinux /dev/<font color="Green">[device]</font><br>
548 reboot</p>
549 <p>where <b><font color="Green">x</font></b> is a number from 1 to 10.</p>
550 <p>After executing these commands, you will have a new <b>sysresc.cfg</b> file, and a backup file called <b>sysresc.bak</b> (in case things go wrong).<br><br>
551 If, for example, you want to increase the device scan delay to maximum, the above commands would become:</p>
552 <p class="newcode">mkdir /mnt/usbdevice<br>
553 mount /dev/<font color="Green">sdc1</font> /mnt/usbdevice <br>
554 cd /mnt/usbdevice<br>
555 cp sysresc.cfg sysresc.bak<br>
556 sed 's|<font color="Red">scandelay=5</font>|<font color="Red">scandelay=<font color="Green">10</font></font>|' sysresc.cfg &gt; sys.cfg<br>
557 mv sys.cfg sysresc.cfg<br>
558 cd; umount /dev/<font color="Green">sdc1</font><br>
559 syslinux /dev/<font color="Green">sdc1</font><br>
560 reboot</p>
561 <p>If, in addition to that, you had to use the boot parameter <b><font color="Red">usbstick</font></b>, then it would be:</p>
562 <p class="newcode">mkdir /mnt/usbdevice<br>
563 mount /dev/<font color="Green">sdc1</font> /mnt/usbdevice <br>
564 cd /mnt/usbdevice<br>
565 cp sysresc.cfg sysresc.bak<br>
566 sed 's|<font color="Red">scandelay=5</font>|<font color="Red">scandelay=<font color="Green">10</font> usbstick</font>|' sysresc.cfg &gt; sys.cfg<br>
567 mv sys.cfg sysresc.cfg<br>
568 cd; umount /dev/<font color="Green">sdc1</font><br>
569 syslinux /dev/<font color="Green">sdc1</font><br>
570 reboot</p>
571 <p>In case something goes wrong with your new settings, you can always rename <b>sysresc.bak</b> to <b>sysresc.cfg</b>, either from linux or Windows.</p>
572 <H2><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></H2>
573 <p>
574 If your usb device is more than 450MB in size, the above procedure will leave the remaining space unused. To verify it, execute the command:
575 </p>
576 <p class="newcode" style="margin-left: 0;">fdisk -l /dev/<font color="Green">sdc</font></p>
577 <p style="margin-left: 0;">You should get something similar to this:</p>
578 <p class="newcode">
579 Disk /dev/sdc: 4043 MB, 4043309056 bytes<br>
580 125 heads, 62 sectors/track, 1018 cylinders, total 7897088 sectors<br>
581 Units = sectors of 1 * 512 = 512 bytes<br>
582 Sector size (logical/physical): 512 bytes / 512 bytes<br>
583 I/O size (minimum/optimal): 512 bytes / 512 bytes<br>
584 Disk identifier: 0x596bbd85<br>
585 <br>
586 &nbsp;&nbsp;&nbsp;Device&nbsp;Boot&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Start&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;End&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Blocks&nbsp;&nbsp;&nbsp;Id&nbsp;&nbsp;System<br>
587 /dev/sdc1&nbsp;&nbsp;&nbsp;*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;63&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1461914&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;730926&nbsp;&nbsp;&nbsp;&nbsp;b&nbsp;&nbsp;W95&nbsp;FAT32
588 </p>
589 <p>
590 As you can see, we are currently using 1461914 out of 7897088 sectors of the disk. The remaining disk space (~3GB) can still be used, to save backups, for example, executing the following commands:
591 </p>
592 <p class="newcode">
593 # fdisk /dev/<font color="green">sdc</font><br>
594 command (m for help): <font color="magenta">n</font> <font color="#990000">(create new partition)</font><br>
595 command action<br>
596 e extended<br>
597 p primary partition (1-4)<br>
598 <font color="magenta">p</font><br>
599 partition number (1-4): <font color="magenta">4</font> <font color="#990000">(create partition sdc4)</font><br>
600 First sector (1461915-7897087, default 1461915): <br>
601 using default value 1461915<br>
602 Last sector, +sectors or +size{K,M,G} (1461915-7897087, default 7897087): <br>
603 using default value 7897087<br>
604 <br>
605 command (m for help): <font color="magenta">p</font> <font color="#990000">(display partition table)</font><br>
606 <br>
607 Disk /dev/sdd: 4043 MB, 4043309056 bytes<br>
608 125 heads, 62 sectors/track, 1018 cylinders, total 7897088 sectors<br>
609 Units = sectors of 1 * 512 = 512 bytes<br>
610 Sector size (logical/physical): 512 bytes / 512 bytes<br>
611 I/O size (minimum/optimal): 512 bytes / 512 bytes<br>
612 Disk identifier: 0x596bbd85<br>
613 <br>
614 /dev/sdc1&nbsp;&nbsp;&nbsp;*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;63&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1461914&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;730926&nbsp;&nbsp;&nbsp;&nbsp;b&nbsp;&nbsp;W95&nbsp;FAT32
615 /dev/sdc4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1461915&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7897087&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3217586+&nbsp;&nbsp;83&nbsp;&nbsp;Linux
616 <br>
617 <br>
618 command (m for help): <font color="magenta">t</font> <font color="#990000">(change partition type)</font><br>
619 partition number (1-4): <font color="magenta">4</font><br>
620 hex code (type l to list codes): <font color="magenta">b</font><br>
621 changed system type of partition 4 to b (W95 FAT32)<br>
622 <br>
623 command (m for help): <font color="magenta">p</font> <font color="#990000">(display partition table)</font><br>
624 <br>
625 Disk /dev/sdd: 4043 MB, 4043309056 bytes<br>
626 125 heads, 62 sectors/track, 1018 cylinders, total 7897088 sectors<br>
627 Units = sectors of 1 * 512 = 512 bytes<br>
628 Sector size (logical/physical): 512 bytes / 512 bytes<br>
629 I/O size (minimum/optimal): 512 bytes / 512 bytes<br>
630 Disk identifier: 0x596bbd85<br>
631 <br>
632 &nbsp;&nbsp;&nbsp;device&nbsp;boot&nbsp;&nbsp;start&nbsp;&nbsp;&nbsp;end&nbsp;&nbsp;blocks&nbsp;&nbsp;&nbsp;id&nbsp;&nbsp;system<br>
633 /dev/sdc1&nbsp;&nbsp;&nbsp;*&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;63&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1461914&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;730926&nbsp;&nbsp;&nbsp;&nbsp;b&nbsp;&nbsp;W95&nbsp;FAT32
634 /dev/sdc4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;1461915&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;7897087&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;3217586+&nbsp;&nbsp;&nbsp;b&nbsp;&nbsp;W95&nbsp;FAT32<br>
635 <br>
636 command (m for help): <font color="magenta">w</font> <font color="#990000">(write partition table to disk and exit)</font><br>
637 The partition table has been altered!<br>
638 <br>
639 Calling ioctl() to re-read partition table.<br>
640 <br>
641 WARNING: Re-reading the partition table failed with error 16: Device or resource busy.<br>
642 The kernel still uses the old table. The new table will be used at<br>
643 the next reboot or after you run partprobe(8) or kpartx(8)<br>
644 Syncing disks.
645 </p>
646 <p>
647 At this point you should disconnect and reconnect your usb device. When it's recognised, you can format the partition you've just created
648 </p>
649 <p class="newcode">
650 mkdosfs -F 32 /dev/<font color="Green">sdc4</font>
651 </p>
652 <p>
653 The partition is now ready for use!!!
654 </p>
655 <a name="boot-top"></a>
656 <H2 style="font-size: 2em;"><a name="boot-intro"></a>Boot parameters <span class="hideprint">[<a href="#boot-top" title="go to top of the page">^</a>]</span></H2>
657 <p>Booting a linux system means loading a kernel, which is actually the operating system. Well, this is not exactly true, and it is not the only thing that happens during boot up phase, but it is not my intension to explain it here.
658 <br><br>
659 The kernel is loaded by Isolinux (the CD boot manager), which is able to pass a number of parameters to it, through its configuration file <b>isolinux.cfg</b>.
660 <br><br>
661 These parameters, called boot parameters, are documented by the kernel itself, and can differentiate its behavior dramatically. In our case, each CD (SystemRescueCD and Clonezilla Live) accept a different set of parameters, because they are based on <a href="http://www.gentoo.org/" target="_blank">gentoo</a> and <a href="http://www.debian.org/" target="_blank">debian</a>, respectively.
662 <br><br>
663 While in the splash screen of <b>Clonezilla-SysRescCD</b>, you can edit the boot parameters by pressing TAB. They will be presented to you, and you can add or remove what you want. You must be careful not to change or remove the parameters that are dedicated to the CD itself, as altering them will certainty make it unbootable. When you are done, just press ENTER to boot.
664 </p>
665 <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>
666 <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>
667 The following info applies to <b>SystemRescueCD v. 2.1.1</b>. In case<br>
668 you need to get info for a more recent version of <b>SystemRescueCD</b><br>
669 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>"
670 </td></tr></table></div>
671 <p>A typical sysresccd isolinux entry is:</p>
672 <p class="newcode">kernel rescuecd<br>
673 append initrd=initram.igz video=ofonly</p>
674 <p>The kernel used is <b>rescuecd</b>, and anything after the word <b>append</b> is a boot parameter.<br><br>
675 Available kernels (boot images):</p>
676 <ul class="otherpage" style="padding: 0px 10px 20px 40px">
677 <li><b>rescuecd</b> Default for 32bit systems, with Framebuffer disabled, best choice.
678 </li><li><b>rescue64</b> Default 64 bit kernel. Use it if you want to chroot to a 64bit linux system installed on your hard disk, or if you have to run 64 bit programs. This kernel is able to boot with 32bit programs, and it requires a processor with 64bit instructions (amd64 / em64t).
679 </li><li><b>altker32</b> an alternative kernel for 32bit systems. Boot with this kernel if you have problems with <b>rescuecd</b>
680 </li><li><b>altker64</b> an alternative kernel for 64bit systems. Boot with this kernel in case you have problems with <b>rescue64</b>.
681 </li>
682 </ul>
683 <p><br>The boot parameters you can use are:</p>
684 <div class="otherpage">
685 <a name="General_boot_options" id="General_boot_options"></a><p><b> General boot options</b></p>
686 <p>Press &lt;TAB&gt; to add additional options (in SystemRescueCd-1.5 and more recent)
687 </p>
688 <ul><li><b>docache</b>: causes the CD-ROM to 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 from being copied.
689 </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.
690 </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 for a linux system. The first linux system found will be started. So <code>root=auto</code> lets 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>.
691 </li><li><b>initscript=service:action</b>: This option allows one to 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 a multiple of times for different services. All the actions that are supported by an initscript can be used.
692 </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. 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 if the scan fails, it will store the files which have changed 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 a harddisk, boot with <code>backstore=alldev</code> to scan all devices (not just removable devices). The default location for a backing-stores file is any file named <code>sysrcd.bs</code> located at the root of a disk which is often a 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>.
693 </li><li><b>isoloop=xxx</b>: Grub2 (currently in development: grub-1.98) provides a new feature to boot from an ISO image which is stored on the hard disk. If you put a copy of <code>systemrescuecd-x86-x.y.z.iso</code> on a partition that Grub2 can read then you can boot SystemRescueCd directly from the ISO image stored on your hard drive. This is very convenient if you frequently update SystemRescueCd and you want to boot it directly from Grub2. Grub2 knows what an ISO image is and it will load the kernel image (rescuecd/rescue64) and the initramfs (initram.igz) from the ISO into memory. It will then do its normal job and execute the kernel. The SystemRescueCd init script must then be aware that its <code>sysrcd.dat</code> file is in an ISO and not directly on the partition. For that reason, this <code>isoloop=xxx</code> boot option is required so you must use it in your <code>grub.cfg</code>. This option is only supported in SystemRescueCd-1.4.0 and more recent. This option specifies the path of the ISO image in the partition that grub considers as its root partition. It's important to understand that the path of the ISO image may be different from the path on your linux system. If you have a separate boot partition mounted on <code>/boot</code> and if you copy this ISO image to <code>/boot/sysrcd/systemrescuecd-x86-x.y.z.iso</code> then the option has to be <code>isoloop=/sysrcd/systemrescuecd-x86-x.y.z.iso</code>. This is because the boot partition is what Grub2 will consider as its root partition during the boot process. Please read <a target="_blank" href="http://www.sysresccd.org/Sysresccd-manual-en_Easy_install_SystemRescueCd_on_harddisk#Boot_the_ISO_image_from_the_disk_using_Grub2" title="Sysresccd-manual-en Easy install SystemRescueCd on harddisk">the section about isoloop</a> for more details.
694 </li></ul>
695 <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>
696 <ul><li><b>dodebug</b>: Enables verbose messages in linuxrc
697 </li></ul>
698 <ul><li><b>doload=xxx</b>: loads needed kernel modules, multiple comma separated occurrences are permitted (example: <code>doload=3c59x,e1000</code>)
699 </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.
700 </li><li><b>nonet</b>: this will disable the network auto detection at startup
701 </li></ul>
702 <ul><li><b>scandelay=x</b>: pauses x seconds during the startup to allow slow devices to initialize. This is required when you boot a USB device. A delay of only few seconds should be enough.
703 </li></ul>
704 <ul><li><b>doxdetect</b>: Since version 0.3.5 the auto-configuration is done in X.Org itself, mkxf86config is disabled by default. This option forces the system to run the mkxf86config startup script and to run the hardware auto-detection from this script. Use this option if you have problems with the graphical environment configuration. This option replaces the option <code>noxdetect</code> that was useful in previous versions.
705 </li><li><b>nodetect</b>: prevents generic hardware auto-detection. Use this option if you have problems with the hardware auto-detection.
706 </li></ul>
707 <ul><li><b>nomodeset</b>: Do not load the Kernel-Mode-Setting video driver. You can use that option if you are experiencing problems with your screen during the boot process (just after modules are being loaded).
708 </li><li><b>dostartx</b>: load the X.Org graphical environment.
709 </li><li><b>forcevesa</b>: Forces X.Org to use the safe VESA driver instead of the best video driver detected for your video card. Use this option if you cannot get the graphical environment working with the default options.
710 </li><li><b>forcevesa=xxx</b>: The <code>startx</code> command will load the <code>Xvesa</code> server instead of <code>Xorg</code>, and use the screen resolution given as parameter (eg: <code>1024x768</code>, <code>1280x1024x32</code>).
711 </li></ul>
712 <ul><li><b>all-generic-ide</b>: In case of problems related to your hard disk, try to enable this option (eg <code>rescuecd all-generic-ide</code>)
713 </li><li><b>nodmraid</b>: Disable dmraid, for some motherboards with built-in RAID controller.
714 </li><li><b>nomdadm</b>: Disable mdadm, for software RAID.
715 </li></ul>
716 <ul><li><b>acpi-off</b> / <b>noapic</b> / <b>irqpool</b>: use these options if you have problem when the kernel boots: if it hangs on a driver or if it crashes, ...
717 </li></ul>
718 <ul><li><b>lowmem</b>: For systems with smaller memory, some daemons are not started including sshd and nfsd.
719 </li></ul>
720 <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 not be mounted. Boot with <code>skipmount=/dev/sda1 skipmount=/dev/sda2</code> to ignore these two partitions.
721 </li></ul>
722 <a name="Network_configuration_and_remote_access" id="Network_configuration_and_remote_access"></a><p><b><br> Network configuration and remote access</b></p>
723 <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.
724 </li><li><b>dodhcp</b>: to request a DHCP server provide network attributes including an IP address, gateway... If there are multiple interfaces on the computer it will run the dhcp client on all of them by default, when no argument is specified with this option. Thanks to <a target="_blank" href="http://www.sysresccd.org/forums/viewtopic.php?f=5&amp;t=3454" class="external text" title="http://www.sysresccd.org/forums/viewtopic.php?f=5&amp;t=3454" rel="nofollow">emiliano</a> SystemRescueCd-1.7.0-beta009 and more recent allows you to optionally specify which interfaces should be configured with dhcp. This way you can combine static and dynamic addresses in the automatic Ethernet configuration. For example you can now use options like that: <pre>dodhcp=eth0,eth2 eth1=192.168.128.1/24</pre> to use dhcp for eth0 and eth2 and a static address on eth1.
725 </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 and more recent
726 </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.
727 </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, for example: <code>eth0=192.168.10.1/24 eth1=192.168.20.1</code>.
728 </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.
729 </li><li><b>gateway=ipaddr</b>: Sets the static IP address of the default route on your network. For instance <code>gateway=192.168.0.254</code> means that the computer can connect to a computer outside of the local network via <code>192.168.0.254</code>.
730 </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.
731 </li><li><b>rootpass=123456</b>: Sets the root password of the system running on the livecd to <code>123456</code>. That way you can connect from the network and ssh on the livecd and give <code>123456</code> password as the root password.
732 </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 6 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. SystemRescueCd-1.5.7 and more recent accept a password longer than 8 chars (between 5 and 12 chars)
733 </li><li><b>nameif=xxx</b>: You 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.
734 </li></ul>
735 <a name="Network_boot_using_PXE" id="Network_boot_using_PXE"></a><p><b><br> Network boot using PXE</b></p>
736 <p>SystemRescueCd provides several options for booting from the network using PXE.
737 These options can be combined with other network boot options such as <code>ethx</code> (cf previous section). See <a target="_blank" href="http://www.sysresccd.org/Sysresccd-manual-en_PXE_network_booting" class="external text" title="http://www.sysresccd.org/Sysresccd-manual-en_PXE_network_booting" rel="nofollow">PXE network booting</a> to get a global overview of SystemRescueCd and PXE and <a target="_blank" href="http://www.sysresccd.org/Sysresccd-manual-en_Manage_remote_windows_linux_servers_using_SystemRescueCd" class="external text" title="http://www.sysresccd.org/Sysresccd-manual-en_Manage_remote_windows_linux_servers_using_SystemRescueCd" rel="nofollow">Manage remote servers using PXE</a>.
738 </p><p>The second stage downloads the kernel + initramfs using DHCP/TFTP.
739 </p><p>The third stage of the PXE boot process acquires the root files system.
740 </p><p>Several protocols are available.
741 </p>
742 <ul><li><b>netboot=</b>tftp<b>://ip/path/sysrcd.dat</b>: from a TFTP server. The filesystem is loaded into memory. As a consequence computers with less than 400MB of memory won't be able to boot this way. The system will continue to work if the network is disconnected after the boot process.
743 </li><li><b>netboot=</b>http<b>://ip:port/path/sysrcd.dat</b>: from a Web server. The file system is loaded into memory. Computers with smaller memory won't be able to boot this way. The the system continues to work if the network is disconnected after the boot process.
744 </li><li><b>netboot=</b>nfs<b>://ip:/path</b>: mount an NFSv3 directory. The NFS url must be the path of the directory that contains <code>sysrcd.dat</code>. Only NFSv3 can be used, NFSv4 is not supported. NFS allows computers with smaller memory to boot SystemRescueCd from the network. After the boot process, continued network connection is required or you will loose access to the root file system.
745 </li><li><b>netboot=</b>nbd<b>://ip:port</b>: connect to an NBD server configured with <code>sysrcd.dat</code> on ip:port. NBD is easier to configure than NFS (only one TCP port involved) and it allows computers with smaller memory to boot SystemRescueCd from the network. After the boot process, the network connection continues to be required to access the root file system.
746 </li></ul>
747 <p>For information on activating <b>speakup</b>, see the <a target="_blank" href="http://www.sysresccd.org/Speakup-info" title="Speakup-info">speakup info page</a>.
748 </p>
749 <a name="Options_provided_for_autorun" id="Options_provided_for_autorun"></a><p><b><br> Options provided for autorun</b></p>
750 <ul><li><b>ar_source=xxx</b>: place where the autorun are stored. It may be the root directory of a partition (<code>/dev/sda1</code>), an nfs share (<code>nfs://192.168.1.1:/path/to/scripts</code>), a samba share (<code>smb://192.168.1.1/path/to/scripts</code>), or an http directory (<code><a target="_blank" href="http://192.168.1.1/path/to/scripts" class="external free" title="http://192.168.1.1/path/to/scripts" rel="nofollow">http://192.168.1.1/path/to/scripts</a></code>).
751 </li><li><b>autoruns=[0-9]</b>: comma separated list of the autorun scrip to be run. For example <code>autoruns=0,2,7</code> the autorun sc <code>autorun0</code>, <code>autorun2</code>, <code>autorun7</code> are run. Use <code>autoruns=no</code> to disable all the autorun scripts with a number.
752 </li><li><b>ar_ignorefail</b>: continue to execute the scripts chain even if a script failed (returned a non-zero status)
753 </li><li><b>ar_nodel</b>: do not delete the temporary copy of the autorun scripts located in <code>/var/autorun/tmp</code> after execution
754 </li><li><b>ar_disable</b>: completely disable autorun, the simple <code>autorun</code> script will not be executed
755 </li><li><b>ar_nowait</b>: do not wait for a keypress after the autorun script have been executed.
756 </li></ul>
757 </p>
758 </div>
759 <H2><a name="clonezilla"></a>Clonezilla Live boot parameters <span class="hideprint">[<a href="#boot-top" title="go to top of the page">^</a>]</span></H2>
760 <div align="center"><table class="note" border="0" cellpadding="20"><tr valign="top"><td><img src="images/info.png"></td><td>
761 The following info applies to <b>Clonezilla Live v. 1.2.8-46</b><br>
762 In case you need to get info for a more recent version of <b>Clonezilla Live</b><br>
763 please see the page "<a href="http://clonezilla.org/fine-print-live-doc.php?path=clonezilla-live/doc/99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc" target="_blank">The boot parameters for Clonezilla live</a>"
764 </td></tr></table></div>
765 <p>A typical Clonezilla Live isolinux entry is:</p>
766 <p class="newcode"> kernel /live/vmlinuz1<br>
767 append initrd=/live/initrd1.img boot=live union=aufs ocs_live_run="ocs-live-general"<br>
768 ocs_live_extra_param="" ocs_live_keymap="" ocs_live_batch="no" ocs_lang="" vga=791 nolocales</p>
769 <p>The kernel used is <b>vmlinuz</b>, and anything after the word <b>append</b> is a boot parameter.</p>
770 <p>The following info comes from the page titled <a href="http://www.clonezilla.org/clonezilla-live/doc/fine-print.php?path=./99_Misc/00_live-initramfs-manual.doc#00_live-initramfs-manual.doc" target="_blank">The boot parameters for Clonezilla live</a>.</p>
771 <div class="otherpage">Clonezilla live is based on <a target="_blank" href="http://wiki.debian.org/DebianLive/" >Debian live</a> with clonezilla installed. Therefore there are 2 kinds of boot parameters:
772 <ol>
773 <li>Boot parameters from live-initramfs. You can refer to this <a href="#live-initramfs">manual of live-initramfs</a>.
774 <li>Boot parameters specially for Clonezilla. All of them are named as "ocs_*", e.g. ocs_live_run, ocs_live_extra_param, ocs_live_batch, ocs_lang.
775 <ul>
776 <li>ocs_live_run is the main program to run in Clonezilla live to save or restore. or other command. Available program: ocs-live-general, ocs-live-restore or any command you write. Use the Absolute path in Clonezilla live.<br>
777 e.g. ocs_live_run="ocs-live-general"<br>
778 <font color="red">//NOTE// You might have to use "sudo" command inside your own script, or you can assign it like: ocs_live_run="sudo bash /my-clonezilla"</font><br>
779 <li>ocs_live_extra_param will be used only when ocs_live_run=ocs-live-restore (not for ocs-live-general or any other), then it will be passed to ocs-sr. Therefore these parameters are actually those of ocs-sr.<br>
780 e.g. ocs_live_extra_param="--batch -c restoredisk sarge-r5 hda"
781 <li>ocs_live_keymap is for keymap used in Clonezilla live. Man install-keymap for more details.<br>
782 e.g. ocs_live_keymap="NONE" (won't change the default layout)<br>
783 ocs_live_keymap="/usr/share/keymaps/i386/azerty/fr-latin9.kmap.gz" (French keyboard)
784 <li>batch mode or not (yes/no), if no, will run interactively.<br>
785 e.g. ocs_live_batch="no"
786 <li>ocs_lang is the language used in Clonezilla live. Available value: en_US.UTF-8, zh_TW.UTF-8... (see $DRBL_SCRIPT_PATH/lang/bash/)
787 e.g. ocs_lang="en_US.UTF-8"
788 <li>ocs_debug (or ocs-debug) is for you to enter command line prompt before any clonezilla-related action is run. This is easier for you to debug.
789 <li>ocs_daemonon, ocs_daemonoff, ocs_numlk, ocs_capslk.<br>
790 Ex. for the first 2 parameters, ocs_daemonon="ssh", then ssh service will be turned on when booting. For the last 2 parameters, use "on" or "off", e.g. ocs_numlk=on to turn on numberlock when booting.
791 <li>ocs_prerun, ocs_prerun1, ocs_prerun2... is for you to run a command before Clonezilla is started. E.g. ocs_prerun="/live/image/myscript.sh". If you have more commands to run, you can assign them in the order: ocs_prerun=..., ocs_prerun1=..., ocs_prerun2=.... If more than 10 parameters, remember to use ocs_prerun01, ocs_prerun02..., ocs_prerun11 to make it in order.
792 <li>ocs_live_run_tty. This option allows you to specify the tty where $ocs_live_run is run. By default $ocs_live_run is run on /dev/tty1 only. If you want to use ttyS0, for example, add live-getty and console=ttyS0,38400n81 in the boot parameter.<br>
793 <font color=red>//NOTE//</font><br>
794 <ul>
795 <li>If "live-getty console=ttyS0,38400n81" are assigned in the boot parameters, ocs_live_run_tty will honor ttyS0, even other value is assigned to ocs_live_run_tty in boot parameter.
796 <li>It's recommended to assign ocs_lang and ocs_live_keymap in the boot parameters too.
797 </ul>
798 <li>ip, this option allows you to specify the network parameters for network card. In Clonezilla live a patched live-initramfs is used, which is different from the original live-initramfs so that you can assign DNS server, too. Its format is: ip=ethernet port,IP address, netmask, gateway, DNS. E.g. If you want to assing eth0 with IP address 10.0.100.1, netmask 255.255.255.0, gateway 10.0.100.254, DNS server 8.8.8.8, you can assign the following in the boot parameter:<br>
799 ip=eth0:10.0.100.1:255.255.255.0:10.0.100.254:8.8.8.8<br>
800 If more than one network card, you can use "," to separate them, e.g.:<br>
801 ip=eth0:10.0.100.1:255.255.255.0:10.0.100.254:8.8.8.8,eth1:192.168.120.1:255.255.255.0:192.168.120.254::<br>
802 <li>Besides, "live-netdev" (yes, not ocs_live_netdev) can be used when using PXE booting, you can force to assign the network device to get filesystem.squashfs. This is useful when there are two or more NICs are linked. E.g. live-netdev="eth1" allows you to force the live-initramfs to use eth1 to fetch the root file system filesystem.squashfs.
803 </ul>
804 </ol>
805 <hr>
806 With the above options, we have the following examples:
807 <ol>
808 <li>A PXE config example for you to boot Clonezilla live via PXE, and ssh service is on, the password of account "user" is assigned:<br>
809 ----------------------------------------<br>
810 label Clonezilla Live<br>
811 MENU LABEL Clonezilla Live<br>
812 MENU DEFAULT<br>
813 kernel vmlinuz1<br>
814 append initrd=initrd1.img boot=live union=aufs noswap noprompt vga=788 fetch=tftp://192.168.120.254/filesystem.squashfs usercrypted=bkuQxLqLRuDW6 ocs_numlk="on" ocs_daemonon="ssh"<br>
815 ----------------------------------------<br>
816 The usercrypted password is created by:<br>
817 echo YOUR_PASSWORD | mkpasswd -s<br>
818 ("mkpasswd" is from package "whois" in Debian or Ubuntu. Check your GNU/Linux to see which package provides this command if you are not using Debian or Ubuntu. Replace YOUR_PASSWORD with your plain text password, and remember do not put any " in the boot parameters of live-initramfs (while it's ok for those ocs_* boot parameters), i.e. do NOT use something like usercrypted="bkuQxLqLRuDW6").<br>
819 //NOTE// If you do not assign salt to mkpasswd, the encrypted password will not be the same every time you create it.<br>
820 For more about usercrypted discussion, please check the <a href="http://lists.debian.org/debian-live/2008/10/msg00020.html" target=_blank>here</a>.
821 <br><br>
822 <li>How to put your own binary driver in Clonezilla live without modifying /live/filesystem.squashfs:
823 <ul>
824 <li>Boot clonezilla live
825 <li>Become root by running "sudo su -"
826 <li>Copy the dir lsi, which contains a precompiled kernel module matching the running kernel in Clonezilla live and a script to run it, to a working dir, e.g.: <br>
827 cp -r /live/image/lsi /home/partimag
828 <li>cd /home/partimag
829 <li>/opt/drbl/sbin/ocs-live-dev -c -s -i lsi -u lsi -x "ocs_prerun=/live/image/lsi/prep-lsi.sh"
830 <li>/opt/drbl/sbin/ocs-iso -s -i lsi -u lsi -x "ocs_prerun=/live/image/lsi/prep-lsi.sh"
831 <li>///NOTE/// In this example, the 2 files in dir lsi are: megasr.ko (the binary driver) and prep-lsi.sh. The contents of prep-lsi.sh:
832 <pre>
833 ------------------------
834 #!/bin/bash
835 cp -f /live/image/lsi/megasr.ko /lib/modules/`uname -r`/kernel/drivers/block/
836 chown root.root /lib/modules/`uname -r`/kernel/drivers/block/megasr.ko
837 depmod -a modprobe megasr
838 sleep 1
839 ------------------------
840 </pre>
841 </ul>
842 <li>To put your customized script with a PXE version of Clonezilla live (You have to use Clonezilla live version 1.2.2-2 or later):<br>
843 In this example, we assume (1) The IP address of your PXE server is 192.168.120.254, (2) the customized script (custom-ocs-2) is put on your PXE server's tftpd root dir (E.g. On DRBL server, the path is /tftpboot/nbi_img/. It might be different in your case if you are not use DRBL server as a PXE server).<br>
844 Therefor your pxelinux.cfg/default file is like:
845 <p>------------------------<br>
846 label Clonezilla Live<br>
847 MENU DEFAULT<br>
848 # MENU HIDE<br>
849 MENU LABEL Clonezilla Live<br>
850 # MENU PASSWD<br>
851 kernel vmlinuz1<br>
852 append initrd=initrd1.img boot=live union=aufs noswap noprompt vga=788 ip=frommedia fetch=tftp://192.168.120.254/filesystem.squashfs ocs_prerun="busybox tftp -g -b 10240 -r custom-ocs-2 -l /tmp/custom-ocs-2 192.168.120.254" ocs_live_run="bash /tmp/custom-ocs-2" ocs_live_keymap="NONE" ocs_live_batch="no" ocs_lang="en_US.UTF-8" nolocales<br>
853 TEXT HELP<br>
854 Boot Clonezilla live via network<br>
855 ENDTEXT<br>
856 <p>------------------------<br>
857 The content of custom-ocs-2 can be like:
858 <pre>
859 ------------------------
860 #!/bin/bash
861 . /opt/drbl/sbin/drbl-conf-functions
862 . /opt/drbl/sbin/ocs-functions
863 . /etc/ocs/ocs-live.conf
864 # Load language file
865 ask_and_load_lang_set en_US.UTF-8
866 # 1. Mount the clonezilla image home.
867 # Types: local_dev, ssh_server, samba_server, nfs_server
868 prep-ocsroot -t nfs_server
869 # 2. Restore the image
870 if mountpoint /home/partimag/ &>/dev/null; then
871 ocs-sr -l en_US.UTF-8 -c -p choose restoredisk ask_user ask_user
872 else
873 [ "$BOOTUP" = "color" ] && $SETCOLOR_FAILURE
874 echo "Fail to find the Clonezilla image home /home/partimag!"
875 echo "Program terminated!"
876 [ "$BOOTUP" = "color" ] && $SETCOLOR_NORMAL
877 fi
878 ------------------------
879 </pre>
880 </li>
881 </ol>
882 </div>
883 <H3><a name="live-initramfs"></a>live-initramfs manual <span class="hideprint">[<a href="#boot-top" title="go to top of the page">^</a>]</span></H3>
884 <p>This is the manual of <a href="http://www.clonezilla.org/clonezilla-live/live-initramfs-param.php" target=_blank>live-initramfs</a>
885 <BR>
886 </p>
887 <a name="live-initramfs"></a><div class="otherpage" style="overflow: auto;"><pre>
888 live-initramfs(7)
889 =================
890 :man source: 1.157.3
891 :man manual: Debian Live
892 Name
893 ----
894 live-initramfs - Debian Live initramfs hook
895 Synopsis
896 --------
897 BOOT=live
898 as kernel parameter at boot prompt.
899 Description
900 -----------
901 live-initramfs is a hook for the initramfs-tools, used to generate a initramfs
902 capable to boot live systems, such as those created by *live-helper*(7).
903 This includes the Debian Live isos, netboot tarballs, and usb stick images.
904 At boot time it will look for a (read-only) media containing a "/live"
905 directory where a root filesystems (often a compressed filesystem image like
906 squashfs) is stored. If found, it will create a writable environment, using
907 aufs, for Debian like systems to boot from.
908 You probably do not want to install this package onto a non-live system,
909 although it will do no harm.
910 live-initramfs is a fork of <a href="http://packages.ubuntu.com/casper/" target="_blank">casper</a>.
911 casper was originally written by Tollef Fog Heen &amp;lt;tfheen@canonical.com&amp;gt;
912 and Matt Zimmerman &amp;lt;mdz@canonical.com&amp;gt;.
913 Boot options
914 ------------
915 Here is the complete list of recognized boot parameters by live-initramfs.
916 access=*ACCESS*::
917 Set the accessibility level for physically or visually impared users. ACCESS
918 must be one of v1, v2, v3, m1, or m2. v1=lesser visual impairment, v2=moderate
919 visual impairment, v3=blindness, m1=minor motor difficulties, m2=moderate motor
920 difficulties.
921 console=*TTY,SPEED*::
922 Set the default console to be used with the "live-getty" option. Example:
923 "console=ttyS0,115200"
924 debug::
925 Makes initramfs boot process more verbose.
926 fetch=*URL*::
927 Another form of netboot by downloading a squashfs image from a given url,
928 copying to ram and booting it. Due to current limitations in busyboxs wget
929 and DNS resolution, an URL can not contain a hostname but an IP only.
930 Not working: http://example.com/path/to/your_filesystem.squashfs
931 Working: http://1.2.3.4/path/to/your_filesystem.squashfs
932 Also note that therefore it's currently not possible to fetch an image from a
933 namebased virtualhost of an httpd if it is sharing the ip with the main httpd
934 instance.
935 hostname=*HOSTNAME*, username=*USER*, userfullname=*USERFULLNAME*::
936 Those parameters lets you override values read from the config file.
937 ignore_uuid
938 Do not check that any UUID embedded in the initramfs matches the discovered
939 medium. live-initramfs may be told to generate a UUID by setting
940 LIVE_GENERATE_UUID=1 when building the initramfs.
941 integrity-check::
942 If specified, an MD5 sum is calculated on the live media during boot and
943 compared to the value found in md5sum.txt found in the root directory of the
944 live media.
945 ip=**[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:
946 [DEVICE]:[AUTOCONF] [,[CLIENT_IP]:[SERVER_IP]:[GATEWAY_IP]:[NETMASK]:[HOSTNAME]:
947 [DEVICE]:[AUTOCONF]]***::
948 Let you specify the name(s) and the options of the interface(s) that should be
949 configured at boot time. Do not specify this if you want to use dhcp (default).
950 It will be changed in a future release to mimick official kernel boot param
951 specification (e.g. ip=10.0.0.1::10.0.0.254:255.255.255.0::eth0,:::::eth1:dhcp).
952 ip=[**frommedia**]::
953 If this variable is set, dhcp and static configuration are just skipped and the
954 system will use the (must be) media-preconfigured /etc/network/interfaces
955 instead.
956 {keyb|kbd-chooser/method}=**KEYBOARD**, {klayout|console-setup/layoutcode}=**LAYOUT**,
957 {kvariant|console-setup/variantcode}=**VARIANT**, {kmodel|console-setup/modelcode}=
958 **CODE**, koptions=**OPTIONS**::
959 Configure the running keyboard as specified, if this one misses live-initramfs
960 behaves as if "keyb=us" was specified. It will be interfered from "locale=" if
961 locale is only 2 lowecase letters as a special case. You could also specify
962 console layout, variant, code, and options (no defaults).
963 live-getty::
964 This changes the auto-login on virtual terminals to use the (experimental)
965 live-getty code. With this option set the standard kernel argument "console=" is
966 parsed and if a serial console is specified then live-getty is used to autologin
967 on the serial console.
968 {live-media|bootfrom}=**DEVICE**::
969 If you specify one of this two equivalent forms, live-initramfs will first try
970 to find this device for the "/live" directory where the read-only root
971 filesystem should reside. If it did not find something usable, the normal scan
972 for block devices is performed.
973 Instead of specifing an actual device name, the keyword 'removable' can be used
974 to limit the search of acceptable live media to removable type only. Note that
975 if you want to further restrict the media to usb mass storage only, you can use
976 the 'removable-usb' keyword.
977 {live-media-encryption|encryption}=**TYPE**::
978 live-initramfs will mount the encrypted rootfs TYPE, asking the passphrase,
979 useful to build paranoid live systems :-). TYPE supported so far are "aes" for
980 loop-aes encryption type.
981 live-media-offset=**BYTES**::
982 This way you could tell live-initramfs that your image starts at offset BYTES in
983 the above specified or autodiscovered device, this could be useful to hide the
984 Debian Live iso or image inside another iso or image, to create "clean" images.
985 live-media-path=**PATH**::
986 Sets the path to the live filesystem on the medium. By default, it is set to
987 '/live' and you should not change that unless you have customized your media
988 accordingly.
989 live-media-timeout=**SECONDS**::
990 Set the timeout in seconds for the device specified by "live-media=" to become
991 ready before giving up.
992 {locale|debian-installer/locale}=**LOCALE**::
993 Configure the running locale as specified, if not present the live-media rootfs
994 configured locale will be used and if also this one misses live-initramfs behave
995 as "locale=en_US.UTF-8" was specified. If only 2 lowercase letter are specified
996 (like "it"), the "maybe wanted" locale is generated (like en:EN.UTF-8), in this
997 case if also "keyb=" is unspecified is set with those 2 lowercase letters
998 (keyb=us). Beside that facility, only UTF8 locales are supported by
999 live-initramfs.
1000 module=**NAME**::
1001 Instead of using the default optional file "filesystem.module" (see below)
1002 another file could be specified without the extension ".module"; it should be
1003 placed on "/live" directory of the live medium.
1004 netboot[=**nfs**|**cifs**]::
1005 This tells live-initramfs to perform a network mount. The parameter "nfsroot="
1006 (with optional "nfsopts="), should specify where is the location of the root
1007 filesystem. With no args, will try cifs first, and if it fails nfs.
1008 nfsopts=::
1009 This lets you specify custom nfs options.
1010 noautologin::
1011 This parameter disables the automatic terminal login only, not touching gdk/kdm.
1012 noxautologin::
1013 This parameter disables the automatic login of gdm/kdm only, not touching
1014 terminals.
1015 nofastboot::
1016 This parameter disables the default disabling of filesystem checks in
1017 /etc/fstab. If you have static filesystems on your harddisk and you want them to
1018 be checked at boot time, use this parameter, otherwise they are skipped.
1019 nopersistent::
1020 disables the "persistent" feature, useful if the bootloader (like syslinux) has
1021 been installed with persistent enabled.
1022 noprompt
1023 Do not prompt to eject the CD or remove the USB flash drive on reboot.
1024 nosudo::
1025 This parameter disables the automatic configuration of sudo.
1026 swapon::
1027 This parameter enables usage of local swap partitions.
1028 nouser::
1029 This parameter disables the creation of the default user completely.
1030 noxautoconfig::
1031 This parameter disables Xorg auto-reconfiguration at boot time. This is valuable
1032 if you either do the detection on your own, or, if you want to ship a custom,
1033 premade xorg.conf in your live system.
1034 persistent[=nofiles]::
1035 live-initramfs will look for persistent and snapshot partitions or files labeled
1036 "live-rw", "home-rw", and files called "live-sn*", "home-sn*" and will try to,
1037 in order: mount as /cow the first, mount the second in /home, and just copy the
1038 contents of the latter in appropriate locations (snapshots). Snapshots will be
1039 tried to be updated on reboot/shutdown. Look at live-snapshot(1) for more
1040 informations. If "nofiles" is specified, only filesystems with matching labels
1041 will be searched; no filesystems will be traversed looking for archives or image
1042 files. This results in shorter boot times.
1043 persistent-path=PATH
1044 live-initramfs will look for persistency files in the root directory of a partition,
1045 with this parameter, the path can be configured so that you can have multiple
1046 directories on the same partition to store persistency files.
1047 {preseed/file|file}=**FILE**::
1048 A path to a file present on the rootfs could be used to preseed debconf
1049 database.
1050 package/question=**VALUE**::
1051 All debian installed packages could be preseeded from command-line that way,
1052 beware of blanks spaces, they will interfere with parsing, use a preseed file in
1053 this case.
1054 quickreboot::
1055 This option causes live-initramfs to reboot without attempting to eject the
1056 media and without asking the user to remove the boot media.
1057 showmounts::
1058 This parameter will make live-initramfs to show on "/" the ro filesystems
1059 (mostly compressed) on "/live". This is not enabled by default because could
1060 lead to problems by applications like "mono" which store binary paths on
1061 installation.
1062 silent
1063 If you boot with the normal quiet parameter, live-initramfs hides most messages
1064 of its own. When adding silent, it hides all.
1065 textonly
1066 Start up to text-mode shell prompts, disabling the graphical user interface.
1067 timezone=**TIMEZONE**::
1068 By default, timezone is set to UTC. Using the timezone parameter, you can set it
1069 to your local zone, e.g. Europe/Zurich.
1070 todisk=**DEVICE**::
1071 Adding this parameter, live-initramfs will try to copy the entire read-only
1072 media to the specified device before mounting the root filesystem. It probably
1073 needs a lot of free space. Subsequent boots should then skip this step and just
1074 specify the "live-media=DEVICE" boot parameter with the same DEVICE used this
1075 time.
1076 toram::
1077 Adding this parameter, live-initramfs will try to copy the whole read-only media
1078 to the computer's RAM before mounting the root filesystem. This could need a lot
1079 of ram, according to the space used by the read-only media.
1080 union=**aufs**|**unionfs**::
1081 By default, live-initramfs uses aufs. With this parameter, you can switch to
1082 unionfs.
1083 utc=**yes**|**no**::
1084 By default, Debian systems do assume that the hardware clock is set to UTC. You
1085 can change or explicitly set it with this parameter.
1086 xdebconf::
1087 Uses xdebconfigurator, if present on the rootfs, to configure X instead of the
1088 standard procedure (experimental).
1089 xvideomode=**RESOLUTION**::
1090 Doesn't do xorg autodetection, but enforces a given resolution.
1091 Files
1092 -----
1093 /etc/live.conf
1094 Some variables can be configured via this config file (inside the live system).
1095 /live/filesystem.module
1096 This optional file (inside the live media) contains a list of white-space or
1097 carriage-return-separated file names corresponding to disk images in the "/live"
1098 directory. If this file exists, only images listed here will be merged into the
1099 root aufs, and they will be loaded in the order listed here. The first entry
1100 in this file will be the "lowest" point in the aufs, and the last file in
1101 this list will be on the "top" of the aufs, directly below /cow. Without
1102 this file, any images in the "/live" directory are loaded in alphanumeric order.
1103 /etc/live-persistence.binds
1104 This optional file (which resides in the rootfs system, not in the live media)
1105 is used as a list of directories which not need be persistent: ie. their
1106 content does not need to survive reboots when using the persistence features.
1107 This saves expensive writes and speeds up operations on volatile data such as
1108 web caches and temporary files (like e.g. /tmp and .mozilla) which are
1109 regenerated each time. This is achieved by bind mounting each listed directory
1110 with a tmpfs on the original path.
1111 See also
1112 --------
1113 live-snapshot(1), initramfs-tools(8), live-helper(7), live-initscripts(7),
1114 live-webhelper(7)
1115 Bugs
1116 ----
1117 Report bugs against live-initramfs
1118 <a href="http://packages.qa.debian.org/live-initramfs" target="_blank">http://packages.qa.debian.org/live-initramfs</a>.
1119 Homepage
1120 --------
1121 More information about the Debian Live project can be found at
1122 <a href="http://debian-live.alioth.debian.org/" target="_blank">http://debian-live.alioth.debian.org/</a> and
1123 <a href="http://wiki.debian.org/DebianLive/" target="_blank">http://wiki.debian.org/DebianLive/</a>.
1124 Authors
1125 -------
1126 live-initramfs is maintained by Daniel Baumann &amp;lt;daniel@debian.org&amp;gt;
1127 for the Debian project.
1128 live-initramfs is a fork of <a href="http://packages.ubuntu.com/casper/" target="_blank">casper</a>.
1129 casper was originally written by Tollef Fog Heen &amp;lt;tfheen@canonical.com&amp;gt;
1130 and Matt Zimmerman &amp;lt;mdz@canonical.com&amp;gt;.
1131 </pre>
1132 </div>
1133 <a name="clonezilla-top"></a>
1134 <H2 style="font-size: 2em;"><a name="clonezilla-intro"></a>About Clonezilla Live <span class="hideprint">[<a href="#clonezilla-top" title="go to top of the page">^</a>]</span></H2>
1135 <p>The DRBL-based PXEBoot Clonezilla is used to clone many computers simultaneously. It is an extremely useful tool, however, it does have several limitations. In order to use it, you must first prepare a DRBL server AND the machine to be cloned must boot from a network (e.g. PXE/Etherboot).<br><br>
1136 To address these limitations, the Free Software Lab at the NCHC has combined <a href="http://debian-live.alioth.debian.org/" target=_blank>Debian Live</a> with Clonezilla to produce "<b>Clonezilla Live</b>", a new software that can be used to easily clone individual machines.</p>
1137 <p>
1138 <b>Clonezilla Live</b> provides two modes of operation:
1139 </p>
1140 <ul>
1141 <li><b>device-image</b><br>
1142 In this mode of operation, a disk/partition can be saved to an image file. This image file can be used to restore the original disk/partition. With Clonezilla-SysRescCD, it can also be used to create an automated restore CD/DVD. This is the mode of operation we will discuss here.
1143 </li>
1144 <li><b>device-device (cloning)</b><br>
1145 This mode of operation creates an exact copy of the original disk/partition on the fly.</li>
1146 </ul>
1147 <p>When working in <b>device-image</b> mode, you will always have to specify three things:</p>
1148 <ul>
1149 <li>The location of the image file</li>
1150 <li>The working parameters for the operation</li>
1151 <li>The disk/partition that will be saved/restored</li>
1152 </ul>
1153 <p><b>Clonezilla Live</b> provides a user friendly interface in order to insert this data.<br><br>
1154 When <b>Clonezilla Live</b> is booted up, either normally or copied to RAM, the contents of the whole CD/DVD can be found in folder <b>/live/image</b>. This is where you will find any extra files, such as the <b>restorecd</b> and the <b>doc</b> folders.
1155 </p>
1156 <H2><a name="start-stop"></a>Starting and stopping Clonezilla Live <span class="hideprint">[<a href="#clonezilla-top" title="go to top of the page">^</a>]</span></H2>
1157 <p>When you boot into <b>Clonezilla Live</b>, the program (actually a script) starts automatically. There are many places where you can stop it, by selecting <b>Cancel</b> or answering <b>N(o)</b> to a question. When you do that you will probably get the following:</p>
1158 <p class="newcode">Now you can choose to:<br>
1159 (0) Poweroff<br>
1160 (1) Reboot<br>
1161 (2) Enter command line prompt<br>
1162 (3) Start over<br>
1163 [2]</p>
1164 <p>Select Poweroff or Reboot, <b>only</b> if you haven't already mounted a disk partition. I found out by experience, it is not always safe to let any live CD automatically unmount my partitions. So if you have already specified the image partition and/or the partition to save/restore, you should enter command line prompt and type:</p>
1165 <p class="newcode"><a name="umount"></a>sudo su -<br>
1166 mount | grep /dev/[sh]d</p>
1167 <p>and then unmount the partitions shown by the last command. So if the results of this command is for example:</p>
1168 <p class="newcode"><font color="Green">/dev/hda1</font> on /home/partimag type vfat (rw)</p>
1169 <p>just type the command:</p>
1170 <p class="newcode">umount <font color="Green">/dev/hda1</font></p>
1171 <p>and it's now safe to Poweroff of Reboot.<br><br>
1172 If, on the other hand, you just want to restart the program, type:</p>
1173 <p class="newcode">ocs-live</p>
1174 <H2><a name="about"></a>About the Image file <span class="hideprint">[<a href="#clonezilla-top" title="go to top of the page">^</a>]</span></H2>
1175 <p>One thing should be made clear about the image file: it is not a file, it is a <b>folder</b>, containing the actual image file and some data about the disk/partition it is associated with. So when you insert the image file name, you actually insert the folder name where the image will be saved/restored.<br><br>
1176 Before you are able to insert the image file name, a list of partitions will be presented to you, so that you can choose where it should be saved/found. When you select one of them, it will be mounted and a list of folders will be presented to you, so you can select the base image directory (first level directory within the partition), which will then be mounted under <b>/home/partimag</b>. This way you can, for example, create a folder called <b>all_my_images</b> in one of your disk partitions, and move all your image files in there; <b>Clonezilla Live</b> will be able to find them!!!<br><br>
1177 Another thing that should be pointed out is that <b>only unmounted</b> partitions will be included in the above list. This means that if you have stopped the program at some point after specifying the partition where the image file resides, and it has been mounted, it will not be present in the list the next time it is presented to you, and you will not be able to use it.<br><br>
1178 There are two things you can do in this case; either unmount the partition, as stated <a href="#umount">above</a>, or select</p>
1179 <p class="newcode"><font color="Red">skip&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Use existing /home/partimag</font></p>
1180 <p>instead of any other option, when you restart the program. The later of course means that you still want to use the previously specified partition as the image file location.<br><br>
1181 Fianlly I should say that <b>Clonezilla Live</b> is able to use a remote disk/partition as the location of the image file, mounted through <b>ssh</b>, <b>samba</b> or <b>nfs</b>. Using any of these options is a more advanced topic, way beyond the scope of this presentation.</p>
1182 <H2><a name="options"></a>Scripts' options <span class="hideprint">[<a href="#clonezilla-top" title="go to top of the page">^</a>]</span></H2>
1183 <p>This section presents the options which are available at the "<i><b>Clonezilla advanced extra parameters</b></i>" screens, if the "Expert" mode is selected. For other options, see <a href="backup.html">Getting backups</a> and <a href="restoration.html">Restoring data</a>.</p>
1184 <H3><a name="backup-options"></a>Backup options [<a href="#clonezilla-top" title="go to top of the page">^</a>]</H3>
1185 <H4><a name="imaging-program-priority"></a>Imaging program priority [<a href="#clonezilla-top" title="go to top of the page">^</a>]</H4>
1186 <p class="newcode"><a name="q_option"></a><font color="Red">-q2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Priority: partclone > partimage > dd<br>
1187 -q1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Priority: Only dd (supports all filesystem, but inefficient)<br>
1188 -q&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Priority: ntfsclone > partimage > dd<br>
1189 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Priority: partimage > dd (no ntfsclone)</font></p>
1190 <p>This option chooses which imaging programs are preferred. By default, <b>Clonezilla Live</b> uses <b>partclone</b> for nearly all filesystems, including ext2/3/4, NTFS and FAT32. If a filesystem isn't supported by <b>partclone</b>, but is supported by <b>partimage</b> (spesifically: if the filesystem is HFS, HPFS or JFS), it is cloned by <b>partimage</b>. If it isn't supported by either (for example Linux swap, though it doesn't make any sense to clone swap partitions), it is cloned by <b>dd</b>. Unlike <b>partclone</b> or <b>partimage</b>, <b>dd</b> copies all blocks of the partition instead of only used, resulting in slower imaging process and bigger images.</p>
1191 <p>Normally the default option <font color="Red"><b>-q2</b></font> should be preferred. Try another option if you have problems and believe they are caused by the imaging program used.</p>
1192 <H4><a name="various-backup-parameters"></a>Various parameters [<a href="#clonezilla-top" title="go to top of the page">^</a>]</H4>
1193 <p>These options are available at the second "<i><b>Clonezilla advanced extra parameters</b></i>" screen.</p>
1194 <p class="newcode"><a name="backup-confirmation"></a><font color="Red">-c&nbsp;Client waits for confirmation before cloning</font></p>
1195 <p>This option causes <b>Clonezilla Live</b> to ask if you really want to clone the disk/partition just before it starts cloning. It is enabled by default.</p>
1196 <p class="newcode"><a name="backup-hidden-data"></a><font color="Red">-j2&nbsp;Clone the hidden data between MBR and 1st partition</font></p>
1197 <p>If this option is set, the 15 hidden sectors between Master Boot Record and the first partition are copied. This area usually contains some data necessary for booting. The option is enabled by default and should be kept enabled if you are cloning a bootable disk.</p>
1198 <p class="newcode"><a name="backup-nogui"></a><font color="Red">-nogui&nbsp;Use text output only, no TUI/GUI output</font></p>
1199 <p>Causes <b>Clonezilla Live</b> to force the used programs to use only command-line interface even if text-based or graphical user interface is available.</p>
1200 <p class="newcode"><a name="backup-no-dma"></a><font color="Red">-a&nbsp;Do NOT force to turn on HD DMA</font></p>
1201 <p>Prevents <b>Clonezilla Live</b> from using DMA for communicating with hard drives. Slows cloning down but in some conditions cloning without this option can be impossible.</p>
1202 <p class="newcode"><a name="rm-win-swap-hib"></a><font color="Red">-rm-win-swap-hib&nbsp;Remove page and hibernation files in Win if exists</font></p>
1203 <p>This option prevents <b>Clonezilla Live</b> from cloning your page file if you are cloning a partition containing Windows. Often the page file is big and unneeded, and skipping it may speed cloning up without causing any harm. Mind you, this option is disabled by default because sometimes the page file may be necessary.</p>
1204 <p class="newcode"><a name="ntfs-ok"></a><font color="Red">-ntfs-ok&nbsp;Skip checking NTFS integrity, even bad sectors (ntfsclone only)</font></p>
1205 <p>This option works only if you selected the <font color="Red"><b>-q</b></font> option and you're cloning a NTFS partition. It prevents the integrity check of NTFS partitions and speeds the cloning process up a little. However, if the check is disabled, there is a risk that the filesystem is damaged and the image created from it is useless.</p>
1206 <p class="newcode"><a name="rescue"></a><font color="Red">-rescue&nbsp;Continue reading next one when disk blocks read errors</font></p>
1207 <p>If this option is set, <b>Clonezilla Live</b> continues cloning even if a read error occurs. If there is one, the disk image will be corrupted, but failing hard drives can only be cloned with this option enabled.</p>
1208 <p class="newcode"><a name="fsck-src-part"></a><font color="Red">-fsck-src-part&nbsp;Check and repair source file system before saving</font></p>
1209 <p>This option causes <b>Clonezilla Live</b> to check the integrity of the partition(s) to be cloned. If the filesystem of the partition is damaged, <b>Clonezilla Live</b> also attempts to repair it automatically. Enabling this option reduces the risk that the image contains a damaged filesystem. However, the option is disabled by default because the automatic filesystem repair attempt may cause data loss.</p>
1210 <p class="newcode"><a name="gen-md5"></a><font color="Red">-gm&nbsp;Generate image MD5 checksums</font></p>
1211 <p>Causes <b>Clonezilla Live</b> to calculate MD5 checksum(s) of image(s) created. If the image gets corrupted afterwards, the checksum allows to notice the corruption before the image is restored. Mind you, calculating the checksum takes some time and slows the process down a little.</p>
1212 <p class="newcode"><a name="gen-sha1"></a><font color="Red">-gs&nbsp;Generate image SHA1 checksums</font></p>
1213 <p>This option is identical to the above, but creates SHA1 checksum(s) instead of MD5. SHA1 is considered to be more accurate checksum algorithm than MD5, but MD5 is more popular.</p>
1214 <H4><a name="compression-method"></a>Compression method [<a href="#clonezilla-top" title="go to top of the page">^</a>]</H4>
1215 <p class="newcode"><a name="z_option"></a><font color="Red">-z1p&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Use parallel gzip compression (testing), for multicore/CPU<br>
1216 -z1&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;gzip compression (fast with a smaller image)<br>
1217 -z2p&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Use parallel bzip2 compression (testing), for multicore/CPU<br>
1218 -z2&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;bzip2 compression (slowest but smallest image)<br>
1219 -z3&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;lzo compression (faster with image size approx. to that of gzip)(NOTE!!)<br>
1220 -z4&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;lzma_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2)<br>
1221 -z5p&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Use_parallel_xz_compression_(testing),_for_multicore/CPU<br>
1222 -z5&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;xz_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2)<br>
1223 -z6p&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Use_parallel_lzip_compression_(testing),_for_multicore/CPU<br>
1224 -z6&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;lzip_compression_(slowest_but_also_small_image,_faster_decompression_than_bzip2)<br>
1225 -z0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;No compression (fastest but largest image size)</font></p>
1226 <p>This option chooses the method which is used to compress the image while creating it.</p>
1227 <p>If no compression is used at all, there won't be any negative speed impact caused by compression. However, the image file size is the size of all the data backed up - for example, if you clone a 160 GB hard drive containing 60 gigabytes of data, the resulting disk image will be 60 gigabytes in size.</p>
1228 <p><b>Gzip</b> and <b>lzop</b> are fast compression methods. <b>Lzop</b> is many times faster than <b>gzip</b>, but creates slightly larger images. <b>Clonezilla Live</b> warns that <b>lzop</b> requires good-quality RAM, but I (the contributor who wrote this chapter) think other compression methods require good RAM too.</p>
1229 <p><b>Bzip2</b>, <b>lzma</b>, <b>xz</b> and <b>lzip</b> are powerful compression methods. <b>Lzma</b> creates a little smaller images than <b>bzip2</b>, and decompressing lzma-compressed images is faster than decompressing <b>bzip2</b> images. But there is no free lunch: <b>lzma</b> compression method is very slow compared even to <b>bzip2</b>, which isn't fast method either.</p>
1230 <p><b>Lzma</b> method is becoming obsolete, and both <b>xz</b> and <b>lzip</b> are attempting to become its successor. They are a bit less powerful compression methods than <b>lzma</b>, but much faster. The differences between <b>xz</b> and <b>lzip</b> are virtually non-existent.</p>
1231 <p>If you don't use the i486 version of <b>Clonezilla-SysRescCD</b> and your processor contains multiple cores and/or supports Hyper-Threading, parallel <b>gzip</b>, <b>bzip2</b>, <b>xz</b> and <b>lzip</b> compression methods are also available. Parallel compression means that each processor core compresses a different part of the image at a time. Without parallel compression one core compresses everything.</p>
1232 <p>The speed impact caused by parallel compression depends on the number of processor cores available. In addition, Hyper-Threading increases the speed by about 30 % if parallel compression is used. For example, if your processor contains four cores and supports Hyper-Threading, speed with parallel compression is nearly 5,2 times as high as without. However, parallel compression is currently an experimental feature.</p>
1233 <H4><a name="splitting"></a>Splitting [<a href="#clonezilla-top" title="go to top of the page">^</a>]</H4>
1234 <p>This option (command line: <b>-i <font color="Red">[number]</font></b>) decides if the created image files are splitted into smaller pieces, and if yes, how large the pieces are. This setting doesn't usually matter, but some filesystems (most importantly FAT32) don't allow files larger than four gigabytes. If you're saving the disk image to a FAT32 partition, enter 4000 or less. (Value 0 disables splitting, so don't use it in that case.) If the filesystem allows files big enough, enter any value which isn't too small (you don't want to split the image into too many pieces, do you?)</p>
1235 <p><b>Clonezilla Live</b> warns that it is no longer safe to disable splitting because value 0 can confuse init. I (the contributor) don't know what the warning exactly means and haven't been able to reproduce the problem. Anyway, entering a very big value, for example 999999999999, is a safe way to keep the image in one piece.</p>
1236 <H4><a name="backup-postaction"></a>Postaction [<a href="#clonezilla-top" title="go to top of the page">^</a>]</H4>
1237 <p class="newcode"><a name="backup_p_option"></a><font color="Red">-p true&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Do nothing when the clone finishes<br>
1238 -p reboot&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Reboot client when the clone finishes<br>
1239 -p poweroff&nbsp;&nbsp;&nbsp;&nbsp;Shutdown client when the clone finishes</font></p>
1240 <p>In this screen you can decide what <b>Clonezilla Live</b> does when the disk/partition is cloned.</p>
1241 <p>Spiros told <a href="#start-stop">above</a> that he has found out that it's not always safe to allow Live CDs automatically unmount partitions, and I have lost data when trying auto-unmount with a script. So, avoid <font color="Red"><b>-p reboot</b></font> and <font color="Red"><b>-p poweroff</b></font> options if possible. You have been warned.</p>
1242 <H3><a name="restore-options"></a>Restore options (script ocs-sr) [<a href="#clonezilla-top" title="go to top of the page">^</a>]</H3>
1243 <H4><a name="various-restore-parameters"></a>Various parameters [<a href="#clonezilla-top" title="go to top of the page">^</a>]</H4>
1244 <p>These options are available at the first "<i><b>Clonezilla advanced extra parameters</b></i>" screen.</p>
1245 <p class="newcode"><a name="reinstall-grub"></a><font color="Red">-g auto&nbsp;Reinstall grub in client disk MBR (only if grub config exists)</font></p>
1246 <p>Causes <b>Clonezilla Live</b> to reinstall GRUB into the Master Boot Record of the disk if at least one partition contains GRUB config file (/boot/grub/menu.lst). The option is enabled by default and shouldn't cause any harm. However, it should be disabled if you for example have another bootloader in MBR and chainload GRUB with it.</p>
1247 <p class="newcode"><a name="ntfs-geometry"></a><font color="Red">-e1 auto&nbsp;Automatically adjust filesystem geometry for a NTFS boot partition if exists</font></p>
1248 <p>The NTLDR bootloader used by Windows isn't able to determine automatically where the files it needs are stored. It only knows their physical locations, which sometimes change when the disk or partition is copied. If the locations are changed and this option is selected, the location information of the files is changed accordingly. This option is enabled by default and if it's disabled, the cloned Windows will fail to boot.</p>
1249 <p class="newcode"><a name="chs-from-edd"></a><font color="Red">-e2&nbsp;sfdisk uses CHS of hard drive from EDD(for non-grub boot loader)</font></p>
1250 <p>This option requires that the <font color="Red"><b>-e1 auto</b></font> option is selected. It causes <b>Clonezilla Live</b> to use disk read interface named EDD for determining the physical locations of the files when updating the location information used by NTLDR. The option is enabled by default because it reduces the risk that Windows doesn't boot.</p>
1251 <p class="newcode"><a name="change-win-ip-based-host"></a><font color="Red">-hn0 PC&nbsp;Change MS Win hostname (based on IP address) after clone</font></p>
1252 <p>If this option is selected and a partition containing Microsoft Windows is cloned, its IP address -based hostname is changed after cloning. Computers which are on any network simultaneously need to have different hostnames, so this option is needed if a Windows system is cloned to another computer and the original computer is still used in addition to the one where the image was restored to.</p>
1253 <p class="newcode"><a name="change-win-mac-based-host"></a><font color="Red">-hn1 PC&nbsp;Change MS Win hostname (based on MAC address) after clone</font></p>
1254 <p>This option causes the MAC address -based hostname of Windows to change. This option needs also be enabled in the above condition.</p>
1255 <p class="newcode"><a name="verbose"></a><font color="Red">-v&nbsp;Prints verbose messages (especially for udpcast)</font></p>
1256 <p>Causes <b>Clonezilla Live</b> to tell more information of what it does.</p>
1257 <p class="newcode"><a name="restore-nogui"></a><font color="Red">-nogui&nbsp;Use text output only, no TUI/GUI output</font></p>
1258 <p>Causes <b>Clonezilla Live</b> to force the used programs to use only command-line interface even if text-based or graphical user interface is available.</p>
1259 <p class="newcode"><a name="batch"></a><font color="Red">-b&nbsp;Run clone in batch mode (DANGEROUS!)</font></p>
1260 <p>Causes <b>Clonezilla Live</b> to run in batch mode. According to Clonezilla Live reference card, this option is dangerous, though I (the contributor) don't know why.</p>
1261 <p class="newcode"><a name="restore-confirmation"></a><font color="Red">-c&nbsp;Client waits for confirmation before cloning</font></p>
1262 <p>This option causes <b>Clonezilla Live</b> to ask if you really want to clone the disk/partition just before it starts cloning. It is enabled by default.</p>
1263 <p class="newcode"><a name="no-mbr"></a><font color="Red">-t&nbsp;Client does not restore the MBR (Mater Boot Record)</font></p>
1264 <p>Do NOT restore the MBR (Mater Boot Record) when restoring image. If this option is set, you must make sure there is an existing MBR in the current restored harddisk. Default is Yes.</p>
1265 <p class="newcode"><a name="restore-syslinux-mbr"></a><font color="Red">-t1&nbsp;Client restores the prebuilt MBR from syslinux (For Windows only)</font></p>
1266 <p>If this option is set, the MBR is overwritten by prebuilt one which chainloads Windows. Use this option if you have to restore Windows and make it bootable, but don't have the original MBR or backup of it.</p>
1267 <p class="newcode"><a name="resize-fs"></a><font color="Red">-r&nbsp;Try to resize the filesystem to fit partition size</font></p>
1268 <p>This option is useful if you are cloning a small disk to larger one. It tries to resize the restored filesystem to the size of the partition where it was restored to. It allows you to use the whole size of your new disk without resizing the partition afterwards. The option requires that the disk where the image is copied already contains a partition where the image is restored or that the option <font color="Red"><b>-k1</b></font> is enabled.</p>
1269 <p class="newcode"><a name="load-geometry"></a><font color="Red">-e&nbsp;sfdisk uses the CHS value of hard drive from the saved image</font></p>
1270 <p>Force to use the saved CHS (cylinders, heads, sectors) when using sfdisk. Of cource, there is no use of it when using any of <b><font color="Red">-j0</font></b>, <b><font color="Red">-k</font></b> or <b><font color="Red">-k2</font></b> options.</p>
1271 <p class="newcode"><a name="ignore-crc"></a><font color="Red">-icrc&nbsp;Ignore CRC checking of partclone</font></p>
1272 <p>This option causes <b>partclone</b> to skip checking the CRC32 checksums of the image. Enabling this option speeds the restore process up. However, if this option is enabled and the <b><font color="Red">-cm</font></b> and <b><font color="Red">-cs</font></b> options are disabled, there is no way to notice if the image has corrupted.</p>
1273 <p class="newcode"><a name="mbr-again"></a><font color="Red">-j1&nbsp;Write MBR (512 B) again after image is restored. Not OK for partition table diffe</font></p>
1274 <p>When a disk image is restored, the partition table must be updated to reflect the actual partitions in the disk. If you don't want it to happen, enable this option. Then the Master Boot Record (including the partition table) is restored again after restoring the image. Note that using this option can destroy all the data in the target drive.</p>
1275 <p class="newcode"><a name="restore-hidden-data"></a><font color="Red">-j2&nbsp;Clone the hidden data between MBR and 1st partition</font></p>
1276 <p>If this option is set, the 15 hidden sectors between Master Boot Record and the first partition are restored. This area usually contains some data necessary for booting. The option is enabled by default and should be kept enabled if you are cloning a bootable disk.</p>
1277 <p class="newcode"><a name="check-md5"></a><font color="Red">-cm&nbsp;Check image by MD5 checksums</font></p>
1278 <p>If the image folder contains MD5 checksum(s), this option causes <b>Clonezilla Live</b> to check if the image has corrupted by calculating its checksum and comparing it to the precalculated one. Mind you, calculating the checksum takes some time and slows the process down a little.</p>
1279 <p class="newcode"><a name="check-sha1"></a><font color="Red">-cs&nbsp;Check image by SHA1 checksums</font></p>
1280 <p><p>This option is identical to the above, but checks SHA1 checksum(s) instead of MD5.</p>
1281 <p class="newcode"><a name="restore-no-dma"></a><font color="Red">-a&nbsp;Do NOT force to turn on HD DMA</font></p>
1282 <p>Prevents <b>Clonezilla Live</b> from using DMA for communicating with hard drives. Slows cloning down but in some conditions cloning without this option can be impossible.</p>
1283 <p class="newcode"><a name="run-prerun-dir"></a><font color="Red">-o0&nbsp;Run script in $OCS_PRERUN_DIR before clone starts</font></p>
1284 <p>Run the scripts in the directory $OCS_PRERUN_DIR before clone is started. The location of the directory can be determined by editing the file drbl-ocs.conf. By default it is /opt/drbl/share/ocs/prerun.</p>
1285 <p class="newcode"><a name="run-postrun-dir"></a><font color="Red">-o1&nbsp;Run script in $OCS_POSTRUN_DIR as clone finishes</font></p>
1286 <p>Run the scripts in the directory $OCS_POSTRUN_DIR when clone is finished. The location of the directory can be determined by editing the file drbl-ocs.conf. By default it is /opt/drbl/share/ocs/postrun. The command will be run before that assigned in <font color="Red"><b>-p</b></font>.</p>
1287 <p>The scripts will be executed by the program "run-parts". run-parts only accepts that the name of the scripts must consist entirely of upper and lower case letters, digits and underscores. So if your file name has an illegal character ".", run-parts won't run it. You can test which files will be executed by entering the command:</p>
1288 <p class="newcode">run-parts --test /opt/drbl/share/ocs/postrun</p>
1289 <H4><a name="partition-table"></a>Partition table [<a href="#clonezilla-top" title="go to top of the page">^</a>]</H4>
1290 <p>This option decides what is done to the partition table of the target drive.</p>
1291 <p class="newcode"><a name="image-partition-table"></a><font color="Red">&nbsp;Use the partition table from the image</font></p>
1292 <p>This option causes <b>Clonezilla Live</b> to copy the partition table from the image. Use this option if you are cloning a whole disk or somehow know that the partition tables are identical (for example, if you are restoring a partition to the same disk where it was copied from and haven't repartitioned the drive after creating the backup). This is the default option.</p>
1293 <p class="newcode"><a name="no-fdisk"></a><font color="Red">-k&nbsp;Do NOT create a partition table on the target disk</font></p>
1294 <p>Do NOT create partition in target harddisk. If this option is set, you must make sure there is an existing partition table in the current restored harddisk.</p>
1295 <p class="newcode"><a name="sfdisk"></a><font color="Red">-k1&nbsp;Create partition table proportionally (OK for MRB format, not GPT)</font></p>
1296 <p>Causes <b>Clonezilla Live</b> to create the partition table automatically using sfdisk after restoring the images. This option works nearly always, but sometimes cloned Windows don't boot. Note that this option doesn't work if you have GUID Partition Table on your disk. (Most likely you don't have one.)</p>
1297 <p class="newcode"><a name="enter-cmd"></a><font color="Red">-k2&nbsp;Enter command line prompt to create partition manually later</font></p>
1298 <p>Like the <font color="Red"><b>-k</b></font> option, this option doesn't create the partition table automatically. However, after restoring the image you are led to command line prompt where you can create the partition table manually. Don't use this option if you don't know how the partition table can be created.</p>
1299 <p class="newcode"><a name="dd"></a><font color="Red">-j0&nbsp;Use dd to create partition (NOT OK if logical drives exist)</font></p>
1300 <p>Use dd to dump the partition table from saved image instead of sfdisk.<br><br>
1301 We read in <a href="http://drbl.sourceforge.net/faq/fine-print.php?path=./2_System/23_Missing_OS.faq#23_Missing_OS.faq" target="_blank">DRBL FAQ/Q&#038;A</a>:</p>
1302 <p class="otherpage">
1303 When I use clonezilla to clone MS windows, there is no any problem when saving an image from template machine. However, after the image is restored to another machine, it fails to boot, the error message is "Missing Operating System" or just a blinking underscore. What's going on ?<br><br>
1304 Usually this is because GNU/Linux and M$ windows interpret the CHS (cylinder, head, sector) value of harddrive differently. Some possible solutions:<br>
1305 &nbsp;&nbsp;1. Maybe you can change the IDE harddrive setting in BIOS, try to use LBA instead of auto mode.<br>
1306 &nbsp;&nbsp;2. Try to choose both<br>
1307 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>[*] -j0 Use dd to create partition table instead of sfdisk</b><br>
1308 &nbsp;&nbsp;and <br>
1309 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>[*] -t1 Client restores the prebuilt MBR from syslinux</b> (For Windows only)<br>
1310 &nbsp;&nbsp;&nbsp;&nbsp;when you restore the image.<br>
1311 &nbsp;&nbsp;3. Try to choose<br>
1312 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>[*] -t1 Client restores the prebuilt MBR from syslinux</b> (For Windows only)<br>
1313 &nbsp;&nbsp;and *uncheck*<br>
1314 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>[ ] -g auto Reinstall grub in client disk MBR</b> (only if grub config exists)<br>
1315 &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<b>[ ] -r Try to resize the filesystem to fit partition size</b><br>
1316 &nbsp;&nbsp;when you restore the image. You can refer to <a href="http://www.ecs.umass.edu/pipermail/umasslug/2008-August/003380.html" target=_blank>this discussion</a>. Thanks to Alex Mckenzie for posting this on the forum.<br>
1317 &nbsp;&nbsp;4. You can try to boot the machine with MS Windows 9x bootable floppy, and in the DOS command prompt, run: "fdisk /mbr".<br>
1318 &nbsp;&nbsp;5. You can try to boot the machine with MS Windows XP installation CD, enter recovery mode (by pressing F10 key in MS XP, for example), then in the console, run "fixmbr" to fix it. Maybe another command "fixboot" will help, too. For more info, refer to <a href="http://support.microsoft.com/?scid=kb%3Ben-us%3B314058&x=7&y=14" _target=blank>this doc</a><br>
1319 &nbsp;&nbsp;6. Use <a href="http://sourceforge.net/projects/ntfsfixboot/" target=_blank>ntfsfixboot</a> to fix it. This program is included in Clonezila live and its name is partclone.ntfsfixboot, and you can use it to adjust FS geometry on NTFS partitions. By default this should be done by Clonezilla with the option -e1 and -e2 checked. If not, you can force to do that again. For more info, please run "partclone.ntfsfixboot --help" or refer to <a href="http://sourceforge.net/projects/ntfsfixboot/" target=_blank>http://sourceforge.net/projects/ntfsfixboot/</a>.<br>
1320 &nbsp;&nbsp;7. Use ntfsreloc to adjust FS geometry on NTFS partitions. For more info, refer to <a href="http://www.linux-ntfs.org/doku.php?id=contrib:ntfsreloc" target=_blank>http://www.linux-ntfs.org/doku.php?id=contrib:ntfsreloc</a>. //NOTE// ntfsreloc is an older version of partclone.ntfsfixboot.<br>
1321 &nbsp;&nbsp;8. If you get error messages like "0xc0000225, 0xc00000e", and something about Winload.exe, refer to <a href="http://drbl.sourceforge.net/faq/fine-print.php?path=./2_System/94_windows_winload_err.faq#94_windows_winload_err.faq">this</a>.<br>
1322 &nbsp;&nbsp;9. Some more discussions are available <a href="https://sourceforge.net/projects/clonezilla/forums/forum/663168/topic/3748791" target=_blank>here</a>.
1323 </p>
1324 <p>It has been confirmed that activating the <font color="Red"><b>-j0</b></font> option, usually fixes the problem.</p>
1325 <p>This option doesn't work if you use LVM (Logical Volume Manager).</p>
1326 <p class="newcode"><a name="exit"></a><font color="Red">exit&nbsp;Exit</font></p>
1327 <p>This option ends the restore process and enters command line prompt.</p>
1328 <H4><a name="restore-postaction"></a>Postaction [<a href="#clonezilla-top" title="go to top of the page">^</a>]</H4>
1329 <p class="newcode"><a name="restore_p_option"></a><font color="Red">-p true&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Do nothing when the clone finishes<br>
1330 -p reboot&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Reboot client when the clone finishes<br>
1331 -p poweroff&nbsp;&nbsp;&nbsp;&nbsp;Shutdown client when the clone finishes</font></p>
1332 <p>When image restoration finishes, do one of the following: choose action (default), poweroff or reboot.</p>
1333 <H2><a name="ntfs"></a>Saving image files in NTFS partitions <span class="hideprint">[<a href="#clonezilla-top" title="go to top of the page">^</a>]</span></H2>
1334 <p>Although not recomended, you may find yourself having to save your image file in a NTFS (Windows XP) partition. You may never have a problem doing this, but you may get a message like the following one, when the partition gets mounted:</p>
1335 <p class="newcode">Volume is scheduled for check<br>
1336 Please boot into Windows TWICE, or use 'force' mount option"</p>
1337 <p>and the backup procedure fails. There are two things you can do here:</p>
1338 <ul>
1339 <li><p style="margin-left: 0pt;">Exit the program, reboot and use <b>Windows XP Recovery Console</b> to fix the NTFS file system. From Recovery Console
1340 prompt, execute the command:</p>
1341 <p class="newcode" style="margin-left: 0pt;"><font color="Red">chkdsk /f X:</font></p>
1342 <p style="margin-left: 0pt;">where <font color="Red"><b>X:</b></font> is the drive letter of the disk. When done, boot back into <b>Clonezilla Live</b> and repeat the backup procedure.</p>
1343 <p style="margin-left: 0pt;">If the disk/partition you are trying to backup is not the Windows System disk (usually <b>C:</b>), you can boot Windows, and execute the command in a DOS window. To open a DOS window click <b>Start / Run... </b> and at the prompt <b>Open:</b> type <b><font color="Red">cmd</font>.</b></li></p>
1344 <p style="margin-left: 0pt;">If the Windows version you use is not XP and you're trying to backup the Windows System drive, boot into <b>SystemRescueCD</b> (graphical mode is not needed) and run the following command:</p>
1345 <p class="newcode" style="margin-left: 0pt;"><font color="Red">ntfsfix /dev/hda1</font></p>
1346 <p style="margin-left: 0pt;">where <b>/dev/<font color="Red">hda1</font></b> is the partition name in GNU/Linux. When done, boot back into <b>Clonezilla Live</b> and repeat the backup procedure.</p>
1347 <li><p style="margin-left: 0pt;">If <b>Windows XP Recovery Console</b> is not available, you don't have the time to execute the procedure described above, or even if you have executed it but you still get the same message, and you are <b><u>absolutely sure</u></b> that you get this message because the NTFS partition is really scheduled for check, and it's not because Windows crushed or have become corrupt, you can mount the patririon by hand and tell <b>Clonezilla Live</b> to use it. Assuming the partition is <b>/dev/<font color="Red">hda1</font></b>, exit the program and execute the commands:</p>
1348 <p class="newcode" style="margin-left: 0pt;">sudo su -<br>
1349 ntfs-3g -o force /dev/<font color="Red">hda1</font> /home/partimag<br>
1350 ocs-live</p>
1351 <p style="margin-left: 0pt;">and when you get to the screen "<b><i>Mount clonezilla image directory</i></b>", select</p>
1352 <p class="newcode" style="margin-left: 0pt;"><font color="Red">skip&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Use existing /home/partimag</font></p>
1353 </li>
1354 </ul>
1355 <a name="backup-top"></a>
1356 <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>
1357 <p>In this page I will demonstrate the creation of an image file by getting a backup of a virtual disk (<b>/dev/<font color="Red">sdb</font></b>). The image file will be saved in a partition in another virtual disk (<b>/dev/<font color="Red">sda1</font></b>).<br></p>
1358 <p>
1359 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>
1360 <br>
1361 There is one more step I would want to take: I should check that my BIOS boot settings are correct, in order to boot from my CD/DVD drive.<br>
1362 <br>
1363 Having done all of the above, I am ready to boot from <b>Clonezilla-SysRescCD</b>.<br>
1364 <br>
1365 </p>
1366 <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>
1367 The following pressentation has been made using<br><b>Clonezilla Live v 1.2.8-46</b>
1368 </td></tr></table></div>
1369 <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>
1370 <H3><a name="bck-0"></a>Clonezilla-SysRescCD starting screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1371 <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="#bck-4">this step</a>.</p>
1372 <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>
1373 <p>The default parameters for booting <b>Clonezilla Live</b> on a 1024x768 screen, are the following:</p>
1374 <p class="newcode">append initrd=/live/initrd.img boot=live config nomodeset nolocales noprompt<br>
1375 &nbsp;&nbsp;noswap edd=on ocs_live_run="ocs-live-general" ocs_live_extra_param=""<br>
1376 &nbsp;&nbsp;ocs_prerun="/restorecd/prerun.normal" ocs_live_batch="no" <br>
1377 &nbsp;&nbsp;ocs_lang="<font color="Red">en_US.UTF-8"</font> ocs_live_keymap="<font color="Red">NONE</font>" vga=791</p>
1378 <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>
1379 <p class="newcode">append initrd=/live/initrd.img boot=live config nomodeset nolocales noprompt<br>
1380 &nbsp;&nbsp;noswap edd=on ocs_live_run="ocs-live-general" ocs_live_extra_param=""<br>
1381 &nbsp;&nbsp;ocs_prerun="/restorecd/prerun.normal" ocs_live_batch="no" <br>
1382 &nbsp;&nbsp;ocs_lang="" ocs_live_keymap="" vga=791</p>
1383 <H3><a name="bck-1"></a>Screen "Choose Language" [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1384 <p><img src="images/backup-00.png"><br>
1385 I select "<font color="Red"><b>en_US.UTF-8 English</b></font>" and press ENTER.</p>
1386 <H3><a name="bck-2"></a>Screen "Configuring console-data" [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1387 <p><img src="images/backup-01.png"><br>
1388 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>
1389 <H3><a name="bck-3"></a>Screen "Configuring console-data" [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1390 <p><img src="images/backup-02.png"><br>
1391 As I (the contributor who wrote a great deal of this page) use Finnish 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>
1392 <H3><a name="bck-4"></a>Screen "Start Clonezilla" [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1393 <p><img src="images/backup-03.png"><br>
1394 I select "<font color="Red"><b>Start Clonezilla</b></font>" and press ENTER.
1395 </p>
1396 <H3><a name="bck-5"></a>Screen "Clonezilla" [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1397 <p><img src="images/backup-04.png"><br>
1398 I select "<font color="Red"><b>device-image</b></font>" and press ENTER.<br> <br>
1399 </p>
1400 <H3><a name="bck-6"></a>Screen "Mount clonezilla image directory" [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1401 <p>In this screen I can select the way the image file directory will be saved.
1402 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>
1403 <br>
1404 <img src="images/backup-05.png"><br>
1405 I select "<font color="Red"><b>local_dev</b></font>" and press ENTER.
1406 </p>
1407 <H3><a name="bck-7"></a>Next screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1408 <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>
1409 <img src="images/backup-06.png"><br>
1410 I select partition <font color="Red"><b>sda1</b></font> and press ENTER.<br>
1411 <br>
1412 <img src="images/backup-07.png"><br>
1413 and then ENTER again.</p>
1414 <p><img src="images/backup-08.png"><br>
1415 This screen displays the mounting result.<br>
1416 As we can see, <font color="Red"><b>/dev/sda1</b></font> has been successfully mounted under <b>/tmp/local-dev</b>.</p>
1417 <H3><a name="bck-7a"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1418 <p><img src="images/backup-09.png">
1419 <br>I select <font color="Red"><b>Beginner 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>
1420 <H3><a name="bck-8"></a>Screen "Select mode" [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1421 <p>Here I can select the desired operation.<br>
1422 <br>
1423 <img src="images/backup-10.png"><br>
1424 I select "<font color="Red"><b>savedisk</b></font>" and press ENTER.<br> <br></p>
1425 <H3><a name="bck-9"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1426 <p><img src="images/backup-11.png"><br>
1427 In this screen I select the image name.<br>
1428 I type "Backup_32-2011_sdb", which in my opinion is more informative name than the default.
1429 </p>
1430 <H3><a name="bck-10"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1431 <p><img src="images/backup-12.png"><br>
1432 Then I am asked to select the disk to save.<br>
1433 I just press ENTER again.
1434 </p>
1435 <H3><a name="bck-10a"></a>Next screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1436 <p><img src="images/backup-12a.png"><br>
1437 And I press ENTER again to enable image validation.</p>
1438 <H3><a name="bck-11"></a>Starting the backup [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1439 <p><img src="images/backup-13.png"><br>
1440 Then the program will display the command that will be executed and will ask me to press ENTER. <br>
1441 Then I will be asked to confirm the operation by pressing <font color="Red"><b>y</b></font> and ENTER.
1442 <br>
1443 <br><img src="images/backup-14.png"><br>
1444 After that, the backup begins<br>
1445 <br>
1446 <img src="images/backup-15.png"><br>
1447 and when it's successfully completed, I press ENTER to get to the shell. Then, I execute the commands:</p>
1448 <p class="newcode">sudo su -<br>
1449 cd<br>
1450 umount -a<br>
1451 reboot<br><br></p>
1452 <p>to reboot the system.</p>
1453 <a name="backup-smb-top"></a>
1454 <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>
1455 <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>
1456 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>
1457 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>).
1458 </p>
1459 <H3><a name="what-is"></a>What is Samba? [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1460 <p>We read at <a href="http://us1.samba.org/samba/" target="_blank">http://us1.samba.org/samba/</a>:</p>
1461 <p class="otherpage">Samba is an Open Source/Free Software suite that provides seamless file and print services to SMB/CIFS clients. Samba is freely available, unlike other SMB/CIFS implementations, and allows for interoperability between Linux/Unix servers and Windows-based clients.<br><br>
1462 Samba is software that can be run on a platform other than Microsoft Windows, for example, UNIX, Linux, IBM System 390, OpenVMS, and other operating systems. Samba uses the TCP/IP protocol that is installed on the host server. When correctly configured, it allows that host to interact with a Microsoft Windows client or server as if it is a Windows file and print server.
1463 </p>
1464 <H2><a name="info"></a>Gathering info <span class="hideprint">[<a href="#backup-smb-top" title="go to top of the page">^</a>]</span></H2>
1465 <p>Before you can use this approach to get a backup, you have to get some info about the <b>Samba server</b>.<br><br>
1466 The <b>Samba server</b> I have used for this example was my laptop, so I already knew most of the info required. If this is not the case for you, just ask the owner, user or system admin.<br><br>
1467 The info required is:</p>
1468 <ol>
1469 <li>The IP address of the Samba server</li>
1470 <li>The domain on the Samba server<br>
1471 This may exist if your PC is connected to a larger LAN (a corporation network, for example). In my case this is empty.</li>
1472 <li>The user name and password you can use</li>
1473 <li>The directory on the Samba server you can use to save your backup<br>
1474 This is the name of the <b>Windows share resource</b> (Samba share resource) as it is known in the network, which is not necessarily the same as the local directory name. The user whose account will be used to login to the <b>Samba server</b>, must have write permission to this directory.</li>
1475 </ol>
1476 <H2><a name="backup-smb"></a>Getting the backup <span class="hideprint">[<a href="#backup-smb-top" title="go to top of the page">^</a>]</span></H2>
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.
1478 </p>
1479 <p>If you need to change these settings, go to the <a href="backup.html#bck-0" target="_blank">Getting backups</a> page for instructions .</p>
1480 <H3><a name="bck-smb-1"></a>Screen "Start Clonezilla" [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1481 <p><img src="images/backup-03.png"><br>
1482 I select "<font color="Red"><b>Start Clonezilla</b></font>" and press ENTER.
1483 </p>
1484 <H3><a name="bck-smb-2"></a>Screen "Clonezilla" [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1485 <p><img src="images/backup-04.png"><br>
1486 I select "<font color="Red"><b>device-image</b></font>" and press ENTER.<br> <br>
1487 </p>
1488 <H3><a name="bck-smb-3"></a>Screen "Mount clonezilla image directory" [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1489 <p>In this screen I can select the way the image file directory will be saved.
1490 Available options are local directory, remote directory through <b>ssh</b>, <b>samba</b> or <b>nfs</b> and skip, 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>
1491 <br>
1492 <img src="images/backup-smb-05.png"><br>
1493 I select "<font color="Red"><b>samba server</b></font>" and press ENTER.</p>
1494 <H3><a name="bck-smb-4"></a>Screen "Mount Samba Server" [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1495 <p>This is where I have to enter the IP address of my Samba server.<br><br>
1496 <img src="images/backup-smb-06.png"><br>
1497 I type "<font color="Red"><b>10.0.0.3</b></font>" and press ENTER.</p>
1498 <H3><a name="bck-smb-5"></a>Screen "Mount Samba Server" (second time) [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1499 <p>This is where I have to enter the domain name on my Samba server.<br><br>
1500 <img src="images/backup-smb-07.png"><br>
1501 I just press ENTER, as there is no domain in my LAN. If there is a domain in your network, you have to type its name (something like <b>my_company.com</b>) and press ENTER.</p>
1502 <H3><a name="bck-smb-6"></a>Screen "Mount Samba Server" (third time) [<a href="#backup-smb-top" title="go to top of the page">^</a>]</H3>
1503 <p>This is where I have to enter the account (user) name on my Samba server.<br><br>
1504 <img src="images/backup-smb-08.png"><br>
1505 I type "<font color="Red"><b>spiros</b></font>" and press ENTER.</p>
1506 <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>
1507 <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>
1508 <img src="images/backup-smb-09.png"><br>
1509 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>
1510 <img src="images/backup-smb-10.png"><br>
1511 I will be able to continue only after entering it correctly.<br><br>
1512 <img src="images/backup-smb-11.png"></p>
1513 <H3><a name="bck-smb-7a"></a>Screen "Clonezilla - Opensource Clone System (OCS)" [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1514 <p><img src="images/backup-09.png">
1515 <br>I select <font color="Red"><b>Beginner 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>
1516 <H3><a name="bck-smb-8"></a>Screen "Select mode" [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1517 <p>Here I can select the desired operation.<br>
1518 <br>
1519 <img src="images/backup-10.png"><br>
1520 I select "<font color="Red"><b>savedisk</b></font>" and press ENTER.<br> <br></p>
1521 <H3><a name="bck-smb-9"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1522 <p><img src="images/backup-11.png"><br>
1523 In this screen I select the image name.<br>
1524 I type "Backup_32-2011_sdb", which in my opinion is more informative name than the default.
1525 </p>
1526 <H3><a name="bck-smb-10"></a>Next Screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1527 <p><img src="images/backup-12.png"><br>
1528 Finally I am asked to select the disk to save.<br>
1529 I just press ENTER again.
1530 </p>
1531 <H3><a name="bck-10a"></a>Next screen [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1532 <p><img src="images/backup-12a.png"><br>
1533 And I press ENTER again to enable image validation.</p>
1534 <H3><a name="bck-smb-11"></a>Starting the backup [<a href="#backup-top" title="go to top of the page">^</a>]</H3>
1535 <p><img src="images/backup-13.png"><br>
1536 Then the program will display the command that will be executed and will ask me to press ENTER. <br>
1537 Then I will be asked to confirm the operation by pressing <font color="Red"><b>y</b></font> and ENTER.
1538 <br>
1539 <br><img src="images/backup-14.png"><br>
1540 After that, the backup begins<br>
1541 <br>
1542 <img src="images/backup-15.png"><br>
1543 and when it's successfully completed, I press ENTER to get to the shell. Then, I execute the commands:</p>
1544 <p class="newcode">sudo su -<br>
1545 cd<br>
1546 umount -a<br>
1547 reboot<br><br></p>
1548 <p>to reboot the system.</p>
1549 <a name="restore-top"></a>
1550 <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>
1551 <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>
1552 <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>
1553 <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>
1554 <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>
1555 <p>Now let's boot.</p>
1556 <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>
1557 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.
1558 </td></tr></table></div>
1559 <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>
1560 The following pressentation has been made using<br><b>Clonezilla Live v 1.2.8-46</b>
1561 </td></tr></table></div>
1562 <H2><a name="restore"></a>Restoring data <span class="hideprint">[<a href="#restore-top" title="go to top of the page">^</a>]</span></H2>
1563 <H3><a name="res-0"></a>Clonezilla-SysRescCD starting screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1564 <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>
1565 <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>
1566 <p>The default parameters for booting <b>Clonezilla Live</b> on a 1024x768 screen, are the following:</p>
1567 <p class="newcode">append initrd=/live/initrd1.img boot=live union=aufs<br>
1568 &nbsp;&nbsp;ocs_live_run="ocs-live-general" ocs_live_extra_param=""<br>
1569 &nbsp;&nbsp;ocs_prerun="/live/image/restorecd/prerun.normal" ocs_live_batch="no"<br>
1570 &nbsp;&nbsp;ocs_lang="<font color="Red">en_US.UTF-8</font>" ocs_live_keymap="<font color="Red">NONE</font>" vga=791 nolocales</p>
1571 <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>
1572 <p class="newcode">append initrd=/live/initrd1.img boot=live union=aufs<br>
1573 &nbsp;&nbsp;ocs_live_run="ocs-live-general" ocs_live_extra_param=""<br>
1574 &nbsp;&nbsp;ocs_prerun="/live/image/restorecd/prerun.normal" ocs_live_batch="no"<br>
1575 &nbsp;&nbsp;ocs_lang="" ocs_live_keymap="" vga=791 nolocales</p>
1576 </p>
1577 <H3><a name="res-1"></a>Screen "Choose Language" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1578 <p><img src="images/backup-00.png"><br>
1579 I select "<font color="Red"><b>en_US.UTF-8 English</b></font>" and press ENTER.</p>
1580 <H3><a name="res-2"></a>Screen "Configuring console-data" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1581 <p><img src="images/backup-01.png"><br>
1582 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>
1583 <H3><a name="res-3"></a>Screen "Configuring console-data" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1584 <p><img src="images/backup-02.png"><br>
1585 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>
1586 <H3><a name="res-4"></a>Screen "Start Clonezilla" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1587 <p><img src="images/backup-03.png"><br>
1588 I select "<font color="Red"><b>Start Clonezilla</b></font>" and press ENTER.
1589 </p>
1590 <H3><a name="res-5"></a>Screen "Clonezilla" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1591 <p><img src="images/backup-04.png"><br>
1592 I select "<font color="Red"><b>device-image</b></font>" and press ENTER.<br> <br>
1593 </p>
1594 <H3><a name="res-6"></a>Screen "Mount clonezilla image directory" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1595 <p>In this screen I can select the way the image file directory has been saved.
1596 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>
1597 <br>
1598 <img src="images/backup-05.png"><br>
1599 I select "<font color="Red"><b>local_dev</b></font>" and press ENTER.
1600 </p>
1601 <H3><a name="res-7"></a>Next screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1602 <p>This is where I choose the location of the image file.<br><br>
1603 <img src="images/restoration-06.png"><br>
1604 I select partition <font color="Red"><b>sda1</b></font> and press ENTER.<br>
1605 <br>
1606 <img src="images/backup-07.png"><br>and then ENTER again.</p>
1607 <p><img src="images/restoration-08.png"><br>
1608 This screen displays the mounting result.<br>
1609 As we can see, <font color="Red"><b>/dev/sda1</b></font> has been successfully mounted under <b>/tmp/local-dev</b>.</p>
1610 <H3><a name="res-7a"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1611 <p><img src="images/backup-09.png"><br>
1612 I select <font color="Red"><b>Beginner 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>
1613 <H3><a name="res-8"></a>Screen "Select mode" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1614 <p>Here I can select the desired operation.<br>
1615 <br>
1616 <img src="images/restoration-10.png"><br>
1617 I select "<font color="Red"><b>restoredisk</b></font>" and press ENTER.<br> <br></p>
1618 <H3><a name="res-9"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1619 <p><img src="images/restoration-11.png"><br>
1620 In this screen I select the image folder. This partition contains only one image.</p>
1621 <H3><a name="res-10"></a>Next Screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1622 <p><img src="images/restoration-12.png"><br>
1623 Finally I am asked to select which disk the image will be restored to. After double-checking the disk doesn't contain anything important, I press ENTER.</p>
1624 <H3><a name="res-11"></a>Starting the restoration [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1625 <p><img src="images/restoration-13.png"><br>
1626 Then the program will display the command that will be executed and will ask me to press ENTER. <br>
1627 Then I will be asked to confirm the operation by pressing <font color="Red"><b>y</b></font> and ENTER.<br>
1628 <img src="images/restoration-14.png"><br>
1629 <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/important.png"></td><td>
1630 <b>This is the last confirmation Clonezilla Live asks.<br>After this step there is no coming back.</b><br></td></tr></table></div>
1631 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>
1632 <br>
1633 <img src="images/restoration-15.png"><br>
1634 After that, the restore process begins
1635 <br>
1636 <br>
1637 <img src="images/restoration-16.png"><br>
1638 and when it's successfully completed, I press ENTER to get to the shell. Then, I execute the commands:</p>
1639 <p class="newcode">sudo su -<br>
1640 cd<br>
1641 umount -a<br>
1642 reboot<br><br></p>
1643 <p>to reboot the system.</p>
1644 <a name="restore-top"></a>
1645 <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>
1646 <p>Assuming you have used <b>Clonezilla Live</b> to make a backup of your system (disk <b>/dev/<font color="Red">sdb</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>
1647 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, which can be uncomfortable or even difficult for many people.<br><br>
1648 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>
1649 You have to boot <b>Clonezilla Live</b>, using <b>Clonezilla-SysRescCD</b>.</p>
1650 <div align="center"><table class="note" border="0" cellpadding="20"><tr><td valign="top"><img src="images/info.png"></td><td>
1651 The following pressentation has been made using<br><b>Clonezilla Live v 1.2.8-46</b>
1652 </td></tr></table></div>
1653 <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>
1654 <H3><a name="rui-0"></a>Clonezilla-SysRescCD starting screen [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1655 <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>
1656 <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>
1657 <p>The default parameters for booting <b>Clonezilla Live</b> on a 1024x768 screen, are the following:</p>
1658 <p class="newcode">append initrd=/live/initrd1.img boot=live union=aufs<br>
1659 &nbsp;&nbsp;ocs_live_run="ocs-live-general" ocs_live_extra_param=""<br>
1660 &nbsp;&nbsp;ocs_prerun="/live/image/restorecd/prerun.normal" ocs_live_batch="no"<br>
1661 &nbsp;&nbsp;ocs_lang="<font color="Red">en_US.UTF-8</font>" ocs_live_keymap="<font color="Red">NONE</font>" vga=791 nolocales</p>
1662 <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>
1663 <p class="newcode">append initrd=/live/initrd1.img boot=live union=aufs<br>
1664 &nbsp;&nbsp;ocs_live_run="ocs-live-general" ocs_live_extra_param=""<br>
1665 &nbsp;&nbsp;ocs_prerun="/live/image/restorecd/prerun.normal" ocs_live_batch="no"<br>
1666 &nbsp;&nbsp;ocs_lang="" ocs_live_keymap="" vga=791 nolocales</p>
1667 </p>
1668 <H3><a name="rui-1"></a>Screen "Choose Language" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1669 <p><img src="images/backup-00.png"><br>
1670 I select "<font color="Red"><b>en_US.UTF-8 English</b></font>" and press ENTER.</p>
1671 <H3><a name="rui-2"></a>Screen "Configuring console-data" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1672 <p><img src="images/backup-01.png"><br>
1673 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>
1674 <H3><a name="rui-3"></a>Screen "Configuring console-data" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1675 <p><img src="images/backup-02.png"><br>
1676 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>
1677 <H3><a name="rui-4"></a>Screen "Start Clonezilla" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1678 <p><img src="images/backup-03.png"><br>
1679 I select "<font color="Red"><b>Start Clonezilla</b></font>" and press ENTER.
1680 </p>
1681 <H3><a name="rui-5"></a>Screen "Clonezilla" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1682 <p><img src="images/backup-04.png"><br>
1683 I select "<font color="Red"><b>device-image</b></font>" and press ENTER.<br> <br>
1684 </p>
1685 <H3><a name="rui-6"></a>Screen "Mount clonezilla image directory" [<a href="#restore-top" title="go to top of the page">^</a>]</H3>
1686 <p>In this screen I can select the way the image file directory has been saved.
1687 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>
1688 <br>
1689 <img src="images/backup-05.png"><br>
1690 I select "<font color="Red"><b>local_dev</b></font>" and press ENTER.
1691 </