| 1 | == Q1/ You have problems with tape and mondo? == |
| 2 | Try setting the blocksize |
| 3 | Use -b 8192 with mondoarchive command and then during restore use at the CLI the following: |
| 4 | {{{ |
| 5 | mt -f /dev/st0 setblk 8192 |
| 6 | }}} |
| 7 | Different drives use different default block sizes, so experimentation with the number may be required. |
| 8 | |
| 9 | == Q2/ Why isn't mondorescue working for fedora core 4 and XFS? == |
| 10 | ''Answer provided by Paulius Pazera (ppp_at_glds.com)''[[BR]] |
| 11 | 'strip xfs.ko' causes problems, makes module unloadable. Had to disable StripExecutable in /sbin/mindi to make it work. Most like it's fc4 |
| 12 | issues. |
| 13 | |
| 14 | == Q3/ Can I use mondorestore in a Microsoft Virtual Server environment? == |
| 15 | ''Answer provided by Albert Smith (albert.smith_at_genexservices.com)''[[BR]] |
| 16 | I have had sucess doing a mondo restore into Microsoft Virtual Server using IDE instead of SCSI. Apparently the virtual scsi controller |
| 17 | does not play nice with RHEL3 or 4 using the AIC7XXX or AIC7XXX_OLD it goes into a continual reset. |
| 18 | |
| 19 | Since I was coming from a SCSI enviornment to an IDE enviornment I had to boot via the mondorescue iso and go into Expert mode. |
| 20 | |
| 21 | Build all LVM and non LVM partitions manually including swap devices and format them. Then load mondorestore and choose the interactive |
| 22 | mode. |
| 23 | |
| 24 | Modify the mountpoints to point to the new hard drive in this case hda[[BR]] |
| 25 | DO NOT FORMAT THE MOUNTPOINTS[[BR]] |
| 26 | DO NOT ALLOW MONDO TO PARTITION EITHER |
| 27 | |
| 28 | Then perform the restore it should all work fine. It did for me. |
| 29 | |
| 30 | == Q4/ How do I create my mindi Failsafe kernel? == |
| 31 | First you need to work with a kernel+modules supporting your hardware both at backup and at restore time. Then copy your kernel under |
| 32 | /usr/share/mindi/vmlinuz and create a tar file compressed with bzip2 called lib.tar.bz2 containing all your modules from /lib |
| 33 | Example: |
| 34 | {{{ |
| 35 | # cd /usr/share/mindi |
| 36 | # cp /boot/vmlinuz-x.y.zz vmlinuz |
| 37 | # tar cfj lib.tar.bz2 /lib/modules/x.y.zz |
| 38 | }}} |
| 39 | (where x.y.zz is your kernel version) |
| 40 | |
| 41 | == Q5/ How do I restore my mondorescue set on a new hardware platform? == |
| 42 | First you need to understand that mondoarchive will create your bootable backup set using your running kernel, or the one you precise or a |
| 43 | failsafe kernel. |
| 44 | Then, whatever you choose, that kernel should be able to support during the boot phase of your mondorestore step your new hardware. Which |
| 45 | means either you create a monolithic kernel containing all the drivers needed for that (mainly IDE, SATS, SCSI, RAID controller and/or |
| 46 | network drivers if PXE or NFS restore) or you ensure that the right drivers will be loaded during the restore phase by adding them to your |
| 47 | /etc/modules.conf file or whatever it is for your distribution. |
| 48 | |
| 49 | A detailed documentation describing such a process is available at |
| 50 | [http://mondorescue.berlios.de/docs/HOWTO-_Deploy_Linux_from_SCSI_to_SATA.pdf] |
| 51 | |
| 52 | ''Thanks to Francois-Xavier.Horel_at_hp.com.'' |
| 53 | |
| 54 | == Q6/ Does mondorescue handle LVM2 ? == |
| 55 | ''Answer reported by Klaus Ade Johnstad <klaus_at_skolelinux.no>.'' |
| 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 yet the usage of |
| 58 | /dev/mapper/vg*. So you need to adapt your /etc/fstab in order to make mondorescue happy, as here: |
| 59 | |
| 60 | Original /etc/fstab: |
| 61 | {{{ |
| 62 | /dev/mapper/vg_system-lv_var /usr ext3 defaults 0 2 |
| 63 | /dev/mapper/vg_system-lv_usr /var ext3 defaults 0 2 |
| 64 | }}} |
| 65 | Modified /etc/fstab: |
| 66 | {{{ |
| 67 | /dev/vg_system/lv_usr /usr ext3 defaults 0 2 |
| 68 | /dev/vg_system/lv_var /var ext3 defaults 0 2 |
| 69 | }}} |
| 70 | |
| 71 | == Q7/ Why does mondo 2.10/mindi 1.10 gives an error message ? == |
| 72 | These versions are '''NOT''' maintained anymore and should '''NOT''' be used. Refer to the development paragraph upper. |
| 73 | |
| 74 | == Q8/ Can I restore some folders from an ISO image without burning it and booting from the CD? == |
| 75 | Sure, Run /usr/sbin/mondorestore from the command-line prompt (without booting from the CD) then you should be able to select ISOs as a |
| 76 | source & choose the files to restore. (Answer from Hugo Rabson hugorabson_at_sbcglobal.net) |
| 77 | Sure, Loop mount the iso image, then find the files you need in the afio balls and restore them. (Answer from Mark Nienberg |
| 78 | mark_at_tippingmar.com) |
| 79 | |
| 80 | == Q9/ Can I manually restore a Linux server with an mdadm-created RAID1? == |
| 81 | ''Solution provided by Christian von Stebut <christian_at_von.stebut.org>'' |
| 82 | 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. |
| 83 | You'll find some remarks and todos in the notes, please add, delete and comment to your liking. |
| 84 | |
| 85 | Basically, I add mdadm and some other files to the image and start restoring manually using "expert". Once the RAID has been manually |
| 86 | created, I then continue with an interactive restore, being careful not to partition and format the disks again. At the end follows a |
| 87 | manual grub installation - I haven't gotten it to work automatically. |
| 88 | |
| 89 | Here are the steps: |
| 90 | |
| 91 | Pre-Backup Phase |
| 92 | |
| 93 | Save partition tables |
| 94 | {{{ |
| 95 | t0e1:~# sfdisk -d /dev/sda > /sda_ptable |
| 96 | t0e1:~# sfdisk -d /dev/sdb > /sdb_ptable |
| 97 | }}} |
| 98 | Add Needed Files to mindi Bootimage |
| 99 | |
| 100 | Edit /etc/mindi/deplist.txt |
| 101 | {{{ |
| 102 | 18 #----------------- STUFF ADDED BY THE USER ---------------------------- |
| 103 | 19 #---vvvv vvvv vvvv list your stuff here! vvvv vvvv vvvv |
| 104 | 20 # |
| 105 | 21 mdadm grub grub-install sfdisk /sda_ptable /sdb_ptable |
| 106 | 22 # |
| 107 | 23 #---^^^^ ^^^^ ^^^^ list your stuff here! ^^^^ ^^^^ ^^^^ |
| 108 | 24 #---------------------------------------------------------------------- |
| 109 | }}} |
| 110 | (Not sure about the following. The LVMFILES: without # looked strange, so I added one) |
| 111 | {{{ |
| 112 | 89 #--------- For all you LVM users out there, much love ----------------- |
| 113 | 90 #LVMFILES: |
| 114 | }}} |
| 115 | |
| 116 | Start mondoarchive |
| 117 | {{{ |
| 118 | t0e1:~# mkdir -p /var/backups/mondo/t0e1/051025_2327 |
| 119 | t0e1:~# mondoarchive -9 -Oi -s4500m -S /tmp -T /tmp -F -E "/tmp /mnt /backup /var/backups" -d /backup/t0e1/051025_2327 |
| 120 | }}} |
| 121 | |
| 122 | Restore Phase |
| 123 | Restore Image on Target Server |
| 124 | Boot |
| 125 | "expert" |
| 126 | |
| 127 | Modify /tmp/mountlist.txt |
| 128 | Get rid of "/dev/sda(i) raid raid number" entries |
| 129 | There should only be the /dev/md(i) entries left. |
| 130 | |
| 131 | Create RAID1 Devices |
| 132 | |
| 133 | Zero Superblock |
| 134 | If old disks, which have previously been a member of another array, are used to build the new array, then the superblock present on the |
| 135 | disks has to be deleted. This can be done with mdadm --zero-superblock DEVICE. |
| 136 | On the VM, PATA disks are used, so DEVICE = /dev/hd{a,b}{1,2,3,4} |
| 137 | On a real machine with SATA disks, DEVICE = /dev/sd{a,b}{1,2,3,4} |
| 138 | For example |
| 139 | {{{ |
| 140 | mdadm -zero-superblock /dev/hda1 |
| 141 | }}} |
| 142 | The disks need to be partitioned, with a type of fd (Linux raid). To create the partitions with sfdisk: |
| 143 | {{{ |
| 144 | sfdisk /dev/hda < /sda_ptable |
| 145 | sfdisk /dev/hdb < /sdb_ptable |
| 146 | }}} |
| 147 | |
| 148 | '''!ToDo:''' sfdisk doesn't like the partition and will not create without --force. |
| 149 | If forced, it will grumble about partitions not ending at cylinder boundaries. |
| 150 | How to automate correctly? (Maybe have a look at how mondo does it presently) |
| 151 | |
| 152 | '''Remark:''' sfdisk --no-reread can be used to disregard existing file systems on disks. |
| 153 | |
| 154 | Now the raid devices can be created: |
| 155 | {{{ |
| 156 | mdadm --create --run /dev/md0 --level 1 --raid-devices=2 /dev/sda1 /dev/sdb1 |
| 157 | mdadm --create --run /dev/md1 --level 1 --raid-devices=2 /dev/sda2 /dev/sdb2 |
| 158 | mdadm --create --run /dev/md2 --level 1 --raid-devices=2 /dev/sda3 /dev/sdb3 |
| 159 | mdadm --create --run /dev/md3 --level 1 --raid-devices=2 /dev/sda4 /dev/sdb4 |
| 160 | }}} |
| 161 | '''Remark (excerpt from "mdadm --create --help):''' |
| 162 | Before devices are added, they are checked to see if they already contain raid superblocks or file systems. They are also checked to see |
| 163 | if the variance in device size exceeds 1%. |
| 164 | If any discrepancy is found, the user will be prompted for confirmation before the array is created. The presence of a '--run' can override |
| 165 | this caution |
| 166 | |
| 167 | '''!ToDo:''' This will take some time. If scripted, how does one detect the end of the process? |
| 168 | |
| 169 | '''Remark:''' Resync on t0e1: about 25 min; resync on virtual machine: about 35 min. |
| 170 | |
| 171 | '''Remark:''' Failure due to not enough disk space on VS. If there is not enough space left on the Virtual Server disk to grow the 2nd disk |
| 172 | during resync, the process will fail and the disk in question is marked as failed. |
| 173 | Steps to recover: |
| 174 | 1. Get enough disk space on VS. |
| 175 | 2. Remove failed drive from array with "mdadm --manage /dev/md3 -r /dev/hdb4" |
| 176 | 3. Add drive back to array with "mdadm /dev/md3 -a /dev/hdb4" |
| 177 | |
| 178 | Format RAID1 Devices |
| 179 | {{{ |
| 180 | mkfs.ext2 /dev/md0 |
| 181 | mkswap /dev/md1 |
| 182 | mkfs.ext2 /dev/md2 |
| 183 | mkfs.ext2 /dev/md3 |
| 184 | }}} |
| 185 | |
| 186 | Restore System Interactively |
| 187 | |
| 188 | Start interactive restore |
| 189 | |
| 190 | mondorestore |
| 191 | |
| 192 | 1. Interactive |
| 193 | 2. DVD |
| 194 | 3. Check mountlist, shouldn't need any changes, because it was adjusted in a previous step. The mountlist should just contain /dev/md(i) |
| 195 | entries. Continue with "Yes" |
| 196 | 4. Do NOT partition |
| 197 | 5. Do NOT format |
| 198 | 6. Do copy all data to disk (estimated time: about 32 min) |
| 199 | 7. Do NOT install boot loader (this will be done manually) |
| 200 | 8. Do Label Disks (not sure on this one) |
| 201 | |
| 202 | Install and configure Grub |
| 203 | |
| 204 | Mount the restored devices |
| 205 | |
| 206 | Edit /tmp/mountlist.txt to get rid of everything except the /dev/md(i) entries. |
| 207 | {{{ |
| 208 | pico /tmp/mountlist.txt |
| 209 | }}} |
| 210 | Mount the restored disks |
| 211 | {{{ |
| 212 | /mondo/mount-me |
| 213 | }}} |
| 214 | Prepare chroot |
| 215 | {{{ |
| 216 | mount -t proc proc /mnt/RESTORING/proc |
| 217 | cd /mnt/RESTORING |
| 218 | chroot /mnt/RESTORING |
| 219 | }}} |
| 220 | Install grub with grub |
| 221 | {{{ |
| 222 | grub |
| 223 | root (hd0,0) |
| 224 | setup (hd0) |
| 225 | root(hd1,0) |
| 226 | setup (hd1) |
| 227 | quit |
| 228 | }}} |
| 229 | Check /boot/grub/menu.lst |
| 230 | Check the file just to make sure it contains the entries needed to boot from raid. This should be the case, because the original system |
| 231 | booted off raid. |
| 232 | |
| 233 | Adjust /etc/mdadm/mdadm.conf |
| 234 | Delete all lines except the first in /etc/mdadm/mdadm.conf |
| 235 | First line should be something like |
| 236 | {{{ |
| 237 | DEVICE /dev/sda* /dev/sdb* (or DEVICE /dev/hda* /dev/hdb*) |
| 238 | }}} |
| 239 | {{{ |
| 240 | mdadm -detail -scan >> /etc/mdadm/mdadm.conf |
| 241 | }}} |
| 242 | Reboot |
| 243 | |
| 244 | Remove image disk from machine |
| 245 | |
| 246 | Leave chroot |
| 247 | {{{ |
| 248 | exit |
| 249 | }}} |
| 250 | Unmount restored disks |
| 251 | {{{ |
| 252 | cd / |
| 253 | /mondo/unmount-me |
| 254 | }}} |
| 255 | Restart System |
| 256 | |
| 257 | Exit |
| 258 | |
| 259 | == 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/] |
| 261 | |
| 262 | == 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 correclty 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: |
| 267 | {{{ |
| 268 | grub --batch |
| 269 | root (hd0,0) |
| 270 | setup (hd0) |
| 271 | }}} |
| 272 | |
| 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? == |
| 274 | 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 | partition size :again. The underlying issue is apparently that fdisk is writing incorrect :partion information. A proper fix is being |
| 276 | worked on. |
| 277 | |
| 278 | == Q14/ I am getting the following error when running mondoarchive |
| 279 | "*** glibc detected *** free(): invalid next size (fast): 0x00000000005496a0 ***" (or similar hex value). It hangs after that. What can I do? == |
| 280 | This is a problem that only seems to appear on Debian systems when the newt interface of mondoarchive is used. The workaround is to install |
| 281 | package libfribidi0. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=351367 for more in-depth information. |
| 282 | |
| 283 | == Q15/ I need a pair of 1440kb boot + root floppies but they are not getting created. How can I get them? == |
| 284 | There are in fact two things involved here: A bug in mindi and lack of documentation. |
| 285 | |
| 286 | 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. |
| 288 | For this purpose, 'FORCE_DUAL_FLOPPIES=no' needs to be changed to 'FORCE_DUAL_FLOPPIES=yes' in mindi (around line 73 or so). |
| 289 | |
| 290 | == Q16/ Why does mondoarchive takes so long to backup my system? == |
| 291 | It may be due to a huge sparse /var/log/lastlog file. In order to trim it, do the following (as root): |
| 292 | {{{ |
| 293 | # rm -f /var/log/lastlog |
| 294 | # touch /var/log/lastlog |
| 295 | # chmod 600 /var/log/lastlog |
| 296 | }}} |
| 297 | to avoid that issue in the future you may want to remove the nfsnobody user from /etc/passwd (uid -1) |
| 298 | |
| 299 | == Q17/ Why does mondoarchive fail saying "No space left on device" although df reports heaps of free space? == |
| 300 | You may have run out of inodes on your filesystem. You can check this with "df -i" |
| 301 | |
| 302 | == Q18/ Why does mindi seg fault on Ubuntu? == |
| 303 | There is a bug in the coreutils packque in Ubuntu see [https://launchpad.net/distros/ubuntu/+source/coreutils/+bug/42264] and |
| 304 | [https://launchpad.net/distros/ubuntu/+source/coreutils/+bug/36036] |
| 305 | |
| 306 | Setting LC_ALL=C seem to fix the problem. |
| 307 | |
| 308 | ''Solution provided by Yannick PEDRON.'' |