Changeset 1903 in MondoRescue for branches/stable/mondo-doc/mondorescue-howto.sgml
- Timestamp:
- Apr 10, 2008, 1:13:58 AM (16 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
branches/stable/mondo-doc/mondorescue-howto.sgml
r1693 r1903 31 31 other supported filesystem partitions to/from CD/DVD-+R/RW media, tape, 32 32 NFS, ... and Mindi Linux provides the bootable emergency restore 33 CD setwhich Mondo uses at boot-time.33 media which Mondo uses at boot-time. 34 34 </para> 35 35 </abstract> … … 445 445 </entry> 446 446 </row> 447 <row>448 <entry>449 <ulink url="images/10cd.png"><inlinemediaobject><imageobject>450 <imagedata fileref="images/10cd-mini">451 </imageobject></inlinemediaobject>452 </ulink>453 </entry>454 <entry>455 Do you want to create a boot image at the end? Yes, if you're a456 tape or NFS user. No, if you are using CD/DVD-R[W]'s and your computer457 supports bootable CD's or using PXE.458 </entry>459 </row>460 447 </tbody></tgroup></informaltable> 461 448 462 449 <itemizedlist> 463 450 <listitem> 464 <para>Try to boot from the first CD of the backup. Choose 'Compare Mode' by typing 465 compare at the boot screen.</para> 451 <para>Try to boot from the first media of the backup. 452 Choose 'Compare Mode' by typing compare at the boot screen. 453 </para> 466 454 </listitem> 467 455 <listitem> … … 469 457 checkout the compatibility of your system. (see 470 458 <link linkend="test-mindi">Testing Mindi</link> for more 471 details). Remove the CD; boot your computer as usual;459 details). Remove the media; boot your computer as usual; 472 460 execute as root</para> 473 461 <para></para> … … 492 480 <row> 493 481 <entry> 494 495 482 bash# cdrecord dev=0,0,0 speed=4 -eject -v mindi.iso 496 483 </entry> 484 </row> 485 <row> 486 <entry> 487 bash# wodim dev=0,0,0 speed=4 -eject -v mindi.iso 497 488 </entry> 498 489 </row> … … 504 495 <row> 505 496 <entry> 506 507 497 bash# cdrecord dev=0,0,0 speed=4 blank=fast -eject -v mindi.iso 508 498 </entry> 499 </row> 500 <row> 501 <entry> 502 bash# wodim dev=0,0,0 speed=4 blank=fast -eject -v mindi.iso 509 503 </entry> 510 504 </row> … … 580 574 <entry> 581 575 bash# cdrecord dev=0,0,0 speed=4 -eject -v /var/cache/mindi/mindi.iso 582 583 576 </entry> 584 577 </row> … … 608 601 If you find this to be the case for your computer, please use '-L' 609 602 to force Mondo to use LILO instead of Syslinux as the boot loader 610 for its CD. (NB: This has nothing to do with which boot603 for its media. (NB: This has nothing to do with which boot 611 604 loader your hard drive uses.) Also, it is a good habit to specify 612 605 your tape streamer with '-d <device>'. You don't usually need … … 687 680 <title>Mindi</title> 688 681 <para> 689 Mindi Linux creates a set of boot/root images682 Mindi Linux creates a set of boot/root media images 690 683 that will let you perform basic system maintenance on your Linux 691 684 distro. The principal virtues of Mindi's boot disks are the fact … … 758 751 command-line options.</para> 759 752 </listitem> 760 <listitem><para>Insert the CDwhen prompted.753 <listitem><para>Insert the media when prompted. 761 754 Press <Enter>. Wait a moment.</para></listitem> 762 755 <listitem><para>Select a subset of files to restore, e.g. /usr/local/man … … 770 763 <itemizedlist> 771 764 <listitem> 772 <para>Boot from CD.</para>765 <para>Boot from media.</para> 773 766 </listitem> 774 767 <listitem><para>Select 'Interactive Mode' at boot-time. (Type … … 918 911 also</para> 919 912 <para>vfat support in the active kernel - mindi needs this when creating 920 syslinux boot images</para>913 syslinux boot media</para> 921 914 </listitem> 922 915 </itemizedlist> … … 1222 1215 Do you want to use your own kernel to build the boot disk (y/n) ?y 1223 1216 Would you like to use LILO (instead of syslinux) 1224 for your boot CD(y/n) ?n1217 for your boot media (y/n) ?n 1225 1218 Analyzing dependency requirements Done. 1226 1219 Making complete dependency list Done. … … 1269 1262 The easiest way to test Mindi is to say 1270 1263 'y' to the last question, then use the 1271 separate application cdrecord to make a bootable CD-R or1264 separate application cdrecord or wodim to make a bootable CD-R or 1272 1265 CD-RW.</para> 1273 <para>Use the cdrecord application to write the CD image:</para> 1274 <para></para> 1275 <informaltable><tgroup cols="1"><tbody> 1276 <row> 1277 <entry> 1278 1266 <para>Use the cdrecord or wodim application to write the CD image:</para> 1267 <para></para> 1268 <informaltable><tgroup cols="1"><tbody> 1269 <row> 1270 <entry> 1279 1271 bash# cd /var/cache/mindi 1280 1272 </entry> … … 1283 1275 <entry> 1284 1276 bash# cdrecord -scanbus 1285 1286 </entry> 1287 </row> 1288 </tbody></tgroup></informaltable> 1289 1290 <para>The output of the above call to cdrecord will tell you your 1277 </entry> 1278 </row> 1279 <row> 1280 <entry> 1281 bash# wodim --devices 1282 </entry> 1283 </row> 1284 </tbody></tgroup></informaltable> 1285 1286 <para>The output of the above call will tell you your 1291 1287 CD writer's node. It is usually '0,0,0'. Choose one of the 1292 1288 following calls to write the CD, depending on whether the disk in … … 1299 1295 <row> 1300 1296 <entry> 1301 1302 1297 bash# cdrecord -v blank=fast dev=x,x,x speed=4 mindi.iso (for CD-RW) 1303 1298 </entry> 1299 </row> 1300 <row> 1301 <entry> 1302 bash# wodim -v blank=fast dev=/dev/xxx speed=4 mindi.iso (for CD-RW) 1304 1303 </entry> 1305 1304 </row> … … 1311 1310 <row> 1312 1311 <entry> 1313 1314 1312 bash# cdrecord -v dev=x,x,x speed=4 mindi.iso (for CD-R) 1315 1313 </entry> 1314 </row> 1315 <row> 1316 <entry> 1317 bash# wodim -v dev=/dev/xxx speed=4 mindi.iso (for CD-R) 1316 1318 </entry> 1317 1319 </row> … … 1369 1371 </tbody></tgroup></informaltable> 1370 1372 1371 <para>cdrecord will tell you where your CD recorder lives, in SCSI1373 <para>cdrecord or wodim will tell you where your CD recorder lives, in SCSI 1372 1374 terms, which looks like '0,0,0'. The previous call to mondoarchive tells 1373 1375 Mondo to backup everything to a 4x CD-RW drive that has … … 1513 1515 isn't a good idea unless you're a Mondo expert because they'll try 1514 1516 to restore over a network by default, which is silly because the 1515 archives are on the CD's). Or, you can boot from the Mindi 1516 mondorescue.isoand hit ENTER a few times to restore.</para>1517 archives are on the CD's). Or, you can boot from the Mindi media 1518 (or mondorescue.iso) and hit ENTER a few times to restore.</para> 1517 1519 <para>Those ISO images can also be used for a PXE restore. For this 1518 1520 to work, please refer to the file README.pxe provided with … … 1891 1893 <para>If you find that you cannot make your PC boot from the CD, 1892 1894 it's mostly because not all the required drivers to support the CD are included. 1893 </para> 1895 take heart: the first backup media of each set contains disk 1896 images to give you the same functionality as this media (minus the 1897 archives, of course) on other boot media. Remember, your Mondo CD is a 1898 fully functional CD-based mini-distribution as well as a recovery 1899 CD.</para> 1894 1900 <para>You can choose from the following modes:</para> 1895 1901 … … 2334 2340 <para>It is now possible to restore to a live filesystem using 2335 2341 Mondo. In other words, you do not have to boot your PC from your 2336 CDin order to restore files. Mondo was originally designed2342 media in order to restore files. Mondo was originally designed 2337 2343 for disaster recovery - situations in which you cannot boot your 2338 2344 PC. If you can boot your PC, it is not really a disaster, is it? :) … … 2363 2369 Choose your type of backup media. The live restoration process is 2364 2370 very similar to what you'll experience if you type mondorestore 2365 with no parameters after booting from a Mondo CD.2371 with no parameters after booting from a Mondo media. 2366 2372 </entry> 2367 2373 </row> … … 2740 2746 </qandaentry> 2741 2747 <qandaentry> 2742 <question><para>Q: But why won't Mondo boot from my CD?2748 <question><para>Q: Why won't Mondo boot from my CD? 2743 2749 It says my kernel is flawed/outdated/ whatever, and when I wrote to 2744 2750 the ML, they told me the same thing... but I still don't get it. I … … 2759 2765 <para>A: On the tape. :-) The first 32MB of the tape will be set 2760 2766 aside for a large tarball containing the data disks, a list of all 2767 <<<<<<< .courant 2761 2768 files backed up, and other sundries. 2762 2769 </para> … … 2946 2953 </entry> 2947 2954 </row> 2948 </tbody></tgroup></informaltable> 2949 <para>or for ATAPI type of devices:</para> 2955 <row> 2956 <entry> 2957 bash# wodim --devices 2958 </entry> 2959 </row> 2960 </tbody></tgroup></informaltable> 2961 <para>or for ATAPI type of devices on older kernel versions:</para> 2950 2962 <para></para> 2951 2963 <informaltable><tgroup cols="1"><tbody> … … 3178 3190 <qandaentry> 3179 3191 <question><para id="SEGF">Q: When I restore after 3180 booting from the CD, I sometimes get errors like, "Running3192 booting from the media, I sometimes get errors like, "Running 3181 3193 out of memory" or "Segmentation fault". What is going on?</para></question> 3182 3194 <answer><para>A: It sounds as if you are running out of disk
Note:
See TracChangeset
for help on using the changeset viewer.