Ignore:
Timestamp:
Apr 10, 2008, 1:13:58 AM (11 years ago)
Author:
bruno
Message:

merge -r 1842:1889 2.2.5

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/stable/mondo-doc/mondorescue-howto.sgml

    r1693 r1903  
    3131other supported filesystem partitions to/from CD/DVD-+R/RW media, tape,
    3232NFS, ... and Mindi Linux provides the bootable emergency restore
    33 CD set which Mondo uses at boot-time.
     33media which Mondo uses at boot-time.
    3434</para>
    3535</abstract>
     
    445445</entry>
    446446</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 a
    456 tape or NFS user. No, if you are using CD/DVD-R[W]'s and your computer
    457 supports bootable CD's or using PXE.
    458 </entry>
    459 </row>
    460447</tbody></tgroup></informaltable>
    461448
    462449<itemizedlist>
    463450<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.
     452Choose 'Compare Mode' by typing compare at the boot screen.
     453</para>
    466454</listitem>
    467455<listitem>
     
    469457checkout the compatibility of your system. (see
    470458<link linkend="test-mindi">Testing Mindi</link> for more
    471 details). Remove the CD; boot your computer as usual;
     459details). Remove the media; boot your computer as usual;
    472460execute as root</para>
    473461<para></para>
     
    492480<row>
    493481<entry>
    494 
    495482bash# cdrecord dev=0,0,0 speed=4 -eject -v mindi.iso
    496 
     483</entry>
     484</row>
     485<row>
     486<entry>
     487bash# wodim dev=0,0,0 speed=4 -eject -v mindi.iso
    497488</entry>
    498489</row>
     
    504495<row>
    505496<entry>
    506 
    507497bash# cdrecord dev=0,0,0 speed=4 blank=fast -eject -v mindi.iso
    508 
     498</entry>
     499</row>
     500<row>
     501<entry>
     502bash# wodim dev=0,0,0 speed=4 blank=fast -eject -v mindi.iso
    509503</entry>
    510504</row>
     
    580574<entry>
    581575        bash# cdrecord dev=0,0,0 speed=4 -eject -v /var/cache/mindi/mindi.iso
    582 
    583576</entry>
    584577</row>
     
    608601If you find this to be the case for your computer, please use '-L'
    609602to force Mondo to use LILO instead of Syslinux as the boot loader
    610 for its CD. (NB: This has nothing to do with which boot
     603for its media. (NB: This has nothing to do with which boot
    611604loader your hard drive uses.) Also, it is a good habit to specify
    612605your tape streamer with '-d &lt;device&gt;'. You don't usually need
     
    687680<title>Mindi</title>
    688681<para>
    689 Mindi Linux creates a set of boot/root images
     682Mindi Linux creates a set of boot/root media images
    690683that will let you perform basic system maintenance on your Linux
    691684distro. The principal virtues of Mindi's boot disks are the fact
     
    758751command-line options.</para>
    759752</listitem>
    760 <listitem><para>Insert the CD when prompted.
     753<listitem><para>Insert the media when prompted.
    761754                Press &lt;Enter&gt;. Wait a moment.</para></listitem>
    762755<listitem><para>Select a subset of files to restore, e.g. /usr/local/man
     
    770763<itemizedlist>
    771764<listitem>
    772 <para>Boot from CD.</para>
     765<para>Boot from media.</para>
    773766</listitem>
    774767<listitem><para>Select 'Interactive Mode' at boot-time. (Type
     
    918911also</para>
    919912<para>vfat support in the active kernel - mindi needs this when creating
    920 syslinux boot images</para>
     913syslinux boot media</para>
    921914</listitem>
    922915</itemizedlist>
     
    12221215Do you want to use your own kernel to build the boot disk (y/n) ?y
    12231216Would you like to use LILO (instead of syslinux)
    1224 for your boot CD (y/n) ?n
     1217for your boot media (y/n) ?n
    12251218Analyzing dependency requirements                               Done.
    12261219Making complete dependency list                                 Done.
     
    12691262The easiest way to test Mindi is to say
    12701263'y' to the last question, then use the
    1271 separate application cdrecord to make a bootable CD-R or
     1264separate application cdrecord or wodim to make a bootable CD-R or
    12721265CD-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>
    12791271        bash# cd /var/cache/mindi
    12801272</entry>
     
    12831275        <entry>
    12841276        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
    12911287CD writer's node. It is usually '0,0,0'. Choose one of the
    12921288following calls to write the CD, depending on whether the disk in
     
    12991295<row>
    13001296<entry>
    1301 
    13021297bash# 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)
    13041303</entry>
    13051304</row>
     
    13111310<row>
    13121311<entry>
    1313 
    13141312bash# 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)
    13161318</entry>
    13171319</row>
     
    13691371</tbody></tgroup></informaltable>
    13701372
    1371 <para>cdrecord will tell you where your CD recorder lives, in SCSI
     1373<para>cdrecord or wodim will tell you where your CD recorder lives, in SCSI
    13721374terms, which looks like '0,0,0'. The previous call to mondoarchive tells
    13731375Mondo to backup everything to a 4x CD-RW drive that has
     
    15131515isn't a good idea unless you're a Mondo expert because they'll try
    15141516to 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.iso and hit ENTER a few times to restore.</para>
     1517archives 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>
    15171519<para>Those ISO images can also be used for a PXE restore. For this
    15181520        to work, please refer to the file README.pxe provided with
     
    18911893<para>If you find that you cannot make your PC boot from the CD,
    18921894it's mostly because not all the required drivers to support the CD are included.
    1893 </para>
     1895take heart: the first backup media of each set contains disk
     1896images to give you the same functionality as this media (minus the
     1897archives, of course) on other boot media. Remember, your Mondo CD is a
     1898fully functional CD-based mini-distribution as well as a recovery
     1899CD.</para>
    18941900<para>You can choose from the following modes:</para>
    18951901
     
    23342340<para>It is now possible to restore to a live filesystem using
    23352341Mondo. In other words, you do not have to boot your PC from your
    2336 CD in order to restore files. Mondo was originally designed
     2342media in order to restore files. Mondo was originally designed
    23372343for disaster recovery - situations in which you cannot boot your
    23382344PC. If you can boot your PC, it is not really a disaster, is it? :)
     
    23632369Choose your type of backup media. The live restoration process is
    23642370very similar to what you'll experience if you type mondorestore
    2365 with no parameters after booting from a Mondo CD.
     2371with no parameters after booting from a Mondo media.
    23662372</entry>
    23672373</row>
     
    27402746</qandaentry>
    27412747<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?
    27432749It says my kernel is flawed/outdated/ whatever, and when I wrote to
    27442750the ML, they told me the same thing... but I still don't get it. I
     
    27592765<para>A: On the tape. :-) The first 32MB of the tape will be set
    27602766aside for a large tarball containing the data disks, a list of all
     2767<<<<<<< .courant
    27612768files backed up, and other sundries.
    27622769</para>
     
    29462953    </entry>
    29472954</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>
    29502962<para></para>
    29512963<informaltable><tgroup cols="1"><tbody>
     
    31783190<qandaentry>
    31793191<question><para id="SEGF">Q: When I restore after
    3180 booting from the CD, I sometimes get errors like, "Running
     3192booting from the media, I sometimes get errors like, "Running
    31813193out of memory" or "Segmentation fault". What is going on?</para></question>
    31823194<answer><para>A: It sounds as if you are running out of disk
Note: See TracChangeset for help on using the changeset viewer.