Custom Query (684 matches)
Results (4 - 6 of 684)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #672 | worksforme | mondo restoration of an iso image which was made on large size machine into smaller size machine | ||
| Description |
1.i have tried to restore an iso image which was made on 500 GB HDD machine installed with RHEL5.9 into 250 GB HDD machine. while mondo restoring i blocked with alert: could not mount devices /dev/VolGroup00/LogVol00 shall i abort? 2.is it possible to restore the image made on 500 GB HDD machine into 250 GB HDD machine? if so kindly guide me the procedure. 3.i have tried to edit the file i-want-my-lvm manually and tried to mount. but it showed /dev/VolGroup00/LogVol00 does not exist with the same result. 4.i have tried to edit the file mountlist.txt available in /tmp. but i got same result. 5.i have used mondo-2.2.4-1 |
|||
| #481 | fixed | Ubuntu keyboard map not saved by mindi | ||
| Description |
Ubuntu (11.04 and 10.10) keyboard map is not saved by mindi. Then, at "mondorescue backup" boot (expert mode), the keyboard is mapped to "us" (QWERTY) and - if keyboard is a non-us one - isn't mapped to the right keyboard (example: to the french "AZERTY" mapping). In mondoarchive.log we get : Line 816: Analyzing your keyboard's configuration. Line 817: Searching for rc.config ...Unknown config detected. Default keyboard map will be used. Line 2890: Analyzing your keyboard's configuration. Line 2891: Unknown config detected. Default keyboard map will be used. Instead, in mondoarchive.log, we should get : Analyzing your keyboard's configuration. Adding the following keyboard mapping tables ... |
|||
| #492 | fixed | mindi 2.0.7.9 rev 2858 doesn't return the kernel. | ||
| Description |
I found a bug in /usr/sbin/mindi 2.0.7.9 rev 2858 The line 2901 of /usr/sbin/mindi should be deleted It contains: "fi", that fi should not exist there. This is the proof:# mindi --findkernel OK, I used my initiative and found that /boot/vmlinuz-2.6.18-128.el5 is probably your kernel. # echo $? 255 It did found the kernel but it did not return it. If i deleted the fi of line 2901, it finds the kernel AND it returns it : # mindi --findkernel OK, I used my initiative and found that /boot/vmlinuz-2.6.18-128.el5 is probably your kernel. /boot/vmlinuz-2.6.18-128.el5 /boot/vmlinuz-2.6.18-128.el5 # echo $? 0 |
|||
