Ignore:
Timestamp:
Oct 20, 2009, 4:07:00 PM (15 years ago)
Author:
Bruno Cornec
Message:

r3548@localhost: bruno | 2009-10-16 19:18:27 +0200

  • mindi now boots in a QEMU VM without busybox
  • mindi is now noarch as a consequence
  • MINDI_LIB becomes MINDI_DATA for coherency and as a consequence
  • CACHEDIR becomes MINDI_CACHE for coherency and it's a build parameter and not hardcoded anymore in mindi
  • THat variable is also used at restore time for mondorestore.cfg e.g.
  • FAILSAFE kernel is gone. Just use another kernel of your choice. Most std kernels work anyway
  • TurnTgzIntoRdz rewritten and now really computes data disk size and not suppose its size
  • Interface mondo/mindi changed again => incompatible
  • Non-bootable media not supported anymore.
  • Mondorescue adapted to these changes but not tested yet
  • Doc updated as well
File:
1 edited

Legend:

Unmodified
Added
Removed

  • branches/2.2.10/mondo-doc/mondorescue-howto.sgml

    r2445 r2462  
    340340in the 'exclude directories' dialog box. Please put a space in
    341341between each path, e.g. /shared/private /scratch /nfs /windows
    342 </entry>
    343 </row>
    344 <row>
    345 <entry>
    346 <ulink url="images/makernel.png"><inlinemediaobject><imageobject>
    347 <imagedata fileref="images/makernel-mini">
    348 </imageobject></inlinemediaobject>
    349 </ulink>
    350 </entry>
    351 <entry>
    352 Is your kernel sane? Red Hat, Mandrake, SuSE, Debian and Slackware users
    353 should in general say 'yes' because these vendors are good at
    354 producing reliable kernels. If you are using Gentoo or LFS
    355 then your kernel might be non-standard, in which case say 'no' to
    356 use Mondo's failsafe kernel (provided separately).
    357342</entry>
    358343</row>
    … …  
    14111396</tbody></tgroup></informaltable>
    14121397
    1413 </sect2>
    1414 <sect2 id="backup-cmd-failsafe">
    1415         <title>Standard Example With Failsafe kernel</title>
    1416 <para></para>
    1417 <informaltable><tgroup cols="1"><tbody>
    1418 <row>
    1419 <entry>
    1420 
    1421 bash# mondoarchive -k FAILSAFE -Ow 2
    1422 
    1423 </entry>
    1424 </row>
    1425 </tbody></tgroup></informaltable>
    1426 
    1427 <para>If you have problems during the restore phase, due to your kernel
    1428         (which may be the case on some distributions), you may want to explore the Failsafe
    1429         approach, In order for this option to work you'll have to get
    1430         the mindi-kernel tarball or package for your distribution.</para>
    1431 </sect2>
    1432 <sect2 id="backup-cmd-network">
    1433         <title>Standard Example With Network Backup</title>
    1434 <para></para>
    1435 <informaltable><tgroup cols="1"><tbody>
    1436 <row>
    1437 <entry>
    1438 
    1439         bash# mount nfs://192.168.1.3:/home/nfs -t nfs /mnt/nfs
    1440 </entry>
    1441 </row>
    1442 <row>
    1443         <entry>
    1444         bash# mondoarchive -OVn nfs://192.168.1.3:/home/nfs -g -s 200m
    1445 </entry>
    1446 </row>
    1447 <row>
    1448         <entry>
    1449         bash# umount /mnt/nfs
    1450 
    1451 </entry>
    1452 </row>
    1453 </tbody></tgroup></informaltable>
    1454 
    1455 <para>The resultant ISO's can be burned to CD's if you want (which
    1456 isn't a good idea unless you're a Mondo expert because they'll try
    1457 to restore over a network by default, which is silly because the
    1458 archives are on the CD's). Or, you can boot from the Mindi media
    1459 (or mondorescue.iso) and hit ENTER a few times to restore.</para>
    1460 <para>Those ISO images can also be used for a PXE restore. For this
    1461         to work, please refer to the file README.pxe provided with
    1462         your mindi package.
    1463 </para>
    14641398</sect2>
    14651399</sect1>
    … …  
    21562090<para>Mondo (technically, Mindi on behalf of Mondo) creates a file
    21572091called a mountlist. This can be found on the ramdisk at
    2158 /tmp/mountlist.txt; it looks something like this:</para>
     2092/var/cache/mindi/mountlist.txt; it looks something like this:</para>
    21592093<para></para>
    21602094<informaltable><tgroup cols="1"><tbody>
    … …  
    22692203automatically partition and format your disks for you, including
    22702204the RAID devices.</para>
    2271 <para>Once you have finished editing /tmp/mountlist.txt using
     2205<para>Once you have finished editing /var/cache/mindi/mountlist.txt using
    22722206mondorestore's built-in editor then you may choose 'OK'. Please
    22732207note that this will not write anything to your hard disk. You will
    … …  
    26172551<qandaentry>
    26182552<question><para>Q: When I try to boot from the Mondo CD,
    2619 it says, "VFS: Unable to mount root fs." I am using an old Debian
    2620 distro. What do I do?</para></question>
    2621 <answer>
    2622 <para>A: Ask Debian's designers why they, unlike every other distro
    2623 I can find, have included cramfs and other 'goodies' with their
    2624 kernel. In the meantime, please use '-k FAILSAFE' in your command
    2625 line when calling Mondo.</para>
    2626 <para>A: From Sarge onwards, all stock Debian 2.6 kernels should work fine. If
    2627 you are still using stock Debian 2.4 kernels, FAILSAFE is the way to go.
    2628 Of course, if you have compiled your own kernel and experience problems,
    2629 FAILSAFE is the way to go as well, but this is not really
    2630 Debian-specific.</para>
    2631 </answer>
    2632 </qandaentry>
    2633 <qandaentry>
    2634 <question><para>Q: When I try to boot from the Mondo CD,
    2635 it says, "Cannot mount root fs - kernel panic," or something
    2636 similar. What do I do?</para></question>
    2637 <answer>
    2638 <para>A: Recompile your kernel (or use '-k FAILSAFE'). Take a look
    2639 at <link linkend="overview-sysrq-kernelreq">Linux Kernel support</link> to
    2640 see what your kernel must support.</para>
    2641 </answer>
    2642 </qandaentry>
    2643 <qandaentry>
    2644 <question><para>Q: When I try to boot from the Mondo CD,
    26452553                it says, "UPGRADE YOUR RAM". What does that mean?</para></question>
    26462554<answer>
    … …  
    26742582in lilo and speeds up booting, for more info see the lilo man
    26752583page.</para>
    2676 </answer>
    2677 </qandaentry>
    2678 <qandaentry>
    2679 <question><para>Q: I made a Mondo CD using the failsafe
    2680 kernel (i.e. I said 'no' when Mondo asked if I wanted to use my own
    2681 kernel). It still doesn't boot. Help!</para></question>
    2682 <answer>
    2683 <para>A: OK, now that is a bug. :-) I included a kernel with Mondo
    2684 (technically, with Mindi, which Mondo uses) to make sure that users
    2685 could use Mondo despite flaws in their own kernels. If you are
    2686 using Mondo/Mindi's kernel but still cannot boot from your Mondo CD
    2687 then please e-mail the &ML;.</para>
    26882584</answer>
    26892585</qandaentry>
    … …  
    29632859        <para>
    29642860                A: Look at <filename>/var/log/mindi.log</filename> and see what it
    2965 says. Also, try typing 'mindi --makemountlist /tmp/mountlist.txt'
     2861                says. Also, try typing 'mindi --makemountlist /var/cache/mindi/mountlist.txt'
    29662862to see what Mindi says. Send the log to the &ML; if you get stuck.
    29672863</para>
Note: See TracChangeset for help on using the changeset viewer.