Custom Query (684 matches)
Results (52 - 54 of 684)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#666 | worksforme | Mondo restore hangs | ||
Description |
Hi, I have started installation of Mondo rescue with upgraded rpms. Mondo archive was completed without aborting. When I tried to restore the ISO in OWP PC( HP 6300MT), while booting it prompt for four command:
I have tried with all the options, after entering the command visual hangs, and there is no interaction between keyboard and monitor. There is no response for any key. And also i am unable to get Mondo restore log as restore process hangs. RPMS installed : afio-2.5-1.rhel6.x86_64.rpm buffer-1.19-4.rhel6.x86_64.rpm mindi-2.1.3-1.rhel6.x86_64.rpm mindi-busybox-1.18.3-1.rhel6.x86_64.rpm mondo-3.0.2-1.rhel6.x86_64.rpm newt-devel-0.52.11-3.el6.x86_64.rpm slang-devel-2.2.1-1.el6.x86_64.rpm Kernel : kernel-2.6.32-279.el6.x86_64 (rhel-workstation-6.3-x86_64-dvd.iso) The backup has been done with the following command: /usr/sbin/mondoarchive and selected DVD option. Please find the attached mondoarchive.log and mindi.log (where i have found a information as “INFO: No Hardware optimized support for your product HP Compaq Pro 6300 MT You may ask your manufacturer to contribute to the mindi project for firmware Disaster Recovery support (harmless) " ) Please help me to solve the issue. |
|||
#223 | fixed | mondo restore hang no floppy present | ||
Description |
On Debian etch with mondo 2.2.4 installed I am seeing a hang during mondo restore while "I'm thinking..." due to my machine having no floppy drive. This appears to be same as ticket#136 which changeset[1496] tries to fix. The fix doesnt work on my machine since the dmesg | grep -i floppy shows a valid device. My machine has a floppy controller but no drive, I think the floppy driver prints a boot message on seeing the controller but doesnt know that no drive is attached. A better test would be to use "getfdprm /dev/fd0u1722" from fdutils - this returns immediately with NO DEVICE. Alternately use low level calls: #include <linux/fd.h> struct floppy_struct fdprms; int ifd, res; ifd = open("/dev/fd0u1722", O_RDONLY); if (ifd > 0) { open OK
} else { skip mount } Of course, same test would apply to /dev/fd0H1440. |
|||
#471 | fixed | calculate EXTRA_SIZE and BOOT_SIZE values before assigning them | ||
Description |
EXTRA_SPACE and BOOT_SIZE variables in /usr/sbin/mindi have fixed values. Sometimes, in some systems, it is necessary to increment them to avoid a crash. If mindi crashes because of this, some messages jump in to the screen, ......Failed to copy /tmp/mindi.HoaDLhll8l/initrd.img to /tmp/mindi.HoaDLhll8l/mountpoint.19653 cat: /tmp/mindi.HoaDLhll8l/mtpt.19653: No such file or directory Please unload some of your modules and try again. Cannot incorporate initrd.img in bootdisk (kernel / modules too big?) FATAL ERROR. Sorry, your kernel is too big for your image and /var/log/mindi.log would get a message like this: copying /tmp/mindi.HoaDLhll8l/initrd.img to /tmp/mindi.HoaDLhll8l/mountpoint.19653/initrd.img... cp: writing «/tmp/mindi.HoaDLhll8l/mountpoint.19653/initrd.img»: No space left on device Failed to copy /tmp/mindi.HoaDLhll8l/initrd.img to /tmp/mindi.HoaDLhll8l/mountpoint.19653 Please unload some of your modules and try again. Cannot incorporate initrd.img in bootdisk (kernel / modules too big?) ...-- Kernel size = 2000 K Ramdisk free = 0 K FATAL ERROR. Sorry, your kernel is too big for your image I think this is not a bug, but for a first time user, this can be a "horror movie". I think an easier approach to implement in a short term, could be adding a message telling the user to try to increment values in those variables editing /usr/sbin/mindi. This can lead to prevent users from repeating the same questions in the mailing list. In a second phase, implement an algorithm that could "guess" which values would be assigned to the variables. This would save the user to undesirable crashes, and would be a better solution in my opinion. |