Changes between Version 6 and Version 7 of FAQ
- Timestamp:
- Jan 5, 2007, 7:58:33 PM (17 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FAQ
v6 v7 55 55 ''Answer reported by Klaus Ade Johnstad <klaus_at_skolelinux.no>.'' 56 56 Short answer is Yes. 57 Now if you encounter a problem with it, it might be due to the fact that mondorescue doesn't support correctly yetthe usage of58 /dev/mapper/vg*. So you need to adapt your /etc/fstab in order to make mondorescue happy, as here:57 Now if you encounter a problem with it, it might be due to the fact that older versions of mondorescue didn't support correctly the usage of 58 /dev/mapper/vg*. So you needed to adapt your /etc/fstab in order to make mondorescue happy, as here: 59 59 60 60 Original /etc/fstab: … … 79 79 80 80 == Q9/ Can I manually restore a Linux server with an mdadm-created RAID1? == 81 82 Note that with mondo > 2.2.1 this should not be required. 83 81 84 ''Solution provided by Christian von Stebut <christian_at_von.stebut.org>'' 82 85 While the steps worked for me, please keep in mind that I'm not a guru. So if you have any suggestions for improvement, please tell me. … … 258 261 259 262 == Q10/ Does mondo work with SuSE distributions? == 260 Yes, but you may need help from mike. Look for his site [http://www.mikenjane.net/~mike/]263 Yes, but you may need help from mike. Look at DistributionPackaging 261 264 262 265 == Q11/ Does mondo work with Debian distributions? == 263 Yes, your best bet are the official Debian packages. Andree, the Debian maintainer, is usually also on the mailing list. 264 265 == Q12/ Why doesn't my LVM based system re-boot correc lty after restore? ==266 It may be due to the fact that grub has not been restored correctly. Use the hint of Q9 for grub re-instalation. In short:266 Yes, your best bet are the official Debian packages. Andree, the Debian maintainer, is usually also on the mailing list. Look at DistributionPackaging 267 268 == Q12/ Why doesn't my LVM based system re-boot correctly after restore? == 269 On older version (pre-2.2.1) It may be due to the fact that grub has not been restored correctly. Use the hint of Q9 for grub re-instalation. In short: 267 270 {{{ 268 271 grub --batch … … 271 274 }}} 272 275 273 == Q13/ After restore my Windows installation on NTFS is not bootable. I get an error saying "A disk read error occurred. Press Xtrl+Alt+Del to restart.". How do I get my windows back? ==276 == Q13/ After restore my Windows installation on NTFS is not bootable. I get an error saying "A disk read error occurred. Press Ctrl+Alt+Del to restart.". How do I get my windows back? == 274 277 The solution for this is to use gparted (and possibly qtparted) to make the NTFS filesystem slightly smaller and then extend it to the 275 278 partition size :again. The underlying issue is apparently that fdisk is writing incorrect :partition information. A proper fix is being … … 285 288 286 289 Before SVN revision 381 (branches) and 382 (trunk),respectively, mindi would delete 1440kb floppy images right after creation. So, this 287 will be fixed in mindi 1.0.7, but is available from SVN now. Secondly, mindi may need to be forced to create 1440kb boot and root floppies.290 is fixed in mindi 1.0.7. Secondly, mindi may need to be forced to create 1440kb boot and root floppies. 288 291 For this purpose, 'FORCE_DUAL_FLOPPIES=no' needs to be changed to 'FORCE_DUAL_FLOPPIES=yes' in mindi (around line 73 or so). 289 292 … … 301 304 302 305 == Q18/ Why does mindi seg fault on Ubuntu? == 303 There is a bug in the coreutils pack que in Ubuntu see [https://launchpad.net/distros/ubuntu/+source/coreutils/+bug/42264] and306 There is a bug in the coreutils package in Ubuntu see [https://launchpad.net/distros/ubuntu/+source/coreutils/+bug/42264] and 304 307 [https://launchpad.net/distros/ubuntu/+source/coreutils/+bug/36036] 305 308 … … 314 317 315 318 == Q20/ I get error messages like size 4096, block-18446744071562067968, b_blocknr=2147483648 what is the problem ? == 316 You may be using a tdefault minimum blocksize for RAM disks of 4k (Fedora kernel 2.6.18* e.g., RHEL5, ...) so try to add ramdisk_blocksize=1024 to your boot command at boot prompt319 You may be using a default minimum blocksize for RAM disks of 4k (Fedora kernel 2.6.18* e.g., RHEL5, ...) so try to add ramdisk_blocksize=1024 to your boot command at boot prompt 317 320 318 321 ''Solution provided by Kathy Durkin'' … … 323 326 324 327 ''Solution provided by James D. Robinson'' 328 329 == Q22/ Why doesn't mondorestore work correctly on OpenSuSE 10.2 ? == 330 It seems that OpenSUSE 10.2 packaged mondo and mindi but did not include the now required mindi-busybox. Get it from ftp://ftp.mondorescue.org/suse/10.2