Re: Restore extremely slow - hdc: lost interrupt

Hi Bruno, I appreciate your help, thank you very much.

I solved the first issue using expert noapic or interactive noapic, etc.
(noapic did the trick).

For the second issue, it works for me using an IDE hard disk but it doesn't
boot. I changed sda for hda in /tmp/mountlist.txt and did an interactive
restore using the default options, including initialize bootloader but
after restarting /dev/hda is not recognized as a valid boot disk and tries
to start from the network.

After that, I can boot using the mondo restore iso again and do a mount-me
and chroot /mnt/RESTORING but doing so, fdisk -l shows no disks, so I can't
try a grub-install '(hd0)'.

I tried to restore in a virtualbox virtual machine using the same /dev/sda
disk, but at the end, I'm getting a kernel panic error, with a mount error
6. I see no errors in /boot/grub/menu.lst.

In both cases (vmware and virtualbox) I was using disks of different sizes.
In vmware, I used a bigger disk  and in virtualbox, a smaller one, but
mondorescue adjust the size of the partitions.

What else could I do?

El mar., 22 de oct. de 2019 a la(s) 12:23, Bruno Cornec (
[email protected]) escribió:

> Hello Pablo,
>
> Pablo Chamorro said on Mon, Oct 21, 2019 at 09:43:24AM -0500:
> >I'm trying to virtualize to vmware an old Fedora 4 server. I created the
> >ISO backup. It has a size of 2 GB. I uploaded the iso file to vmware
> >vsphere 6.5 but the boot proccess takes lilterally hours. What I can see
> is
> >the slowness is due to something related to "hdc: lost interrupt". Please
> >look at this: http://prntscr.com/pma1d1
>
> It's probably linked to the fact that the driver used on the original host
> do not work fine for your target machine.
>
> >zcat /boot/initrd-2.6.17-1.2142_FC4.img  | cpio -itv|grep mpt
> >5339 blocks
> >-rw-r--r--   1 root     root        67136 Apr 27  2007 lib/mptbase.ko
> >-rw-r--r--   1 root     root        21724 Apr 27  2007 lib/mptspi.ko
> >-rw-r--r--   1 root     root        27808 Apr 27  2007 lib/mptscsih.ko
> >
> >And also, in /usr/sbin/mindi I included:
> >
> >FORCE_MODS="mptsas mptspi"
>
> Ok, so these drivers will be forced and loaded at restore time.
>
> >In vmware I tried using a SCSI controller and also a SATA controller, and
> >the hard disk as SCSI or IDE, but always I get the hdc: lost interrupt
> >message that causes that slowness, and also: ide-cd: cmd 0x1e timed out,
> >and also: hdc: DMA interrupt recovery, but mainly: hdc: lost interrupt.
> >Those messages are not registered in mondo-archive.log, only a Hi there
> >message at this moment (the boot process hasn't finished yet).
>
> A possibility woule be to create an empty Fedora 4 VM on VMware to see
> what drivers are used by default, and if it works fine (no lost interrupt),
> then force this driver to used at retsore time (of course, if it's
> different from the one you use currently)
>
> I guess the fdisk you mentionned in another mail is on the restored
> machine, in which case, yes without disk it will be difficult to reinstall.
>
> You need to find which is the right driver for your combination.
>
> Warning: will Fedora 4 work on such an HyperVisor remains to see.
>
> Bruno.
> --
> HPE WW FLOSS Technology Strategist
> http://www.hpe.com/engage/opensource
> Open Source Profession, WW Linux Community Lead
> http://github.com/bcornec
> FLOSS projects:     http://mondorescue.org
> http://project-builder.org
> Musique ancienne?   http://www.musique-ancienne.org
> http://www.medieval.org
>
>
> _______________________________________________
> Mondo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mondo-devel
>

_______________________________________________
Mondo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mondo-devel