[NCLUG] Restore Help?

Bob Proulx bob at proulx.com
Tue Dec 27 12:17:13 MST 2005


Sean Reifschneider wrote:
> Bob Proulx wrote:
> >That seems really strange to me.  I often move hard disks around from
> >computer to computer.  The hardware is often different.  But I
> 
> I imagine that he's going from an AMD CPU to Intel or something.  That can
> be tricky, I recently had to do exactly the same thing for exactly the same
> reason, and switched from an AMD XP to a P4, and the system wouldn't boot
> from the old disc because of the AMD kernel.

Oh, a very good point!  I had neglected to think about that.  Yes,
switching from one architecture to another may cause the trouble.

> >Try booting a live cdrom system such as Knoppix.  Recent systems
> 
> The KRUD FC3 discs are already rescue CDs, and they will do the right thing
> about finding the disc, starting LVM, and bringing up your partitions.

Excellent.

> Worst case then you could chroot into the file-system and start USB or
> networking and copy the data off.

Good plan.

> >reinstall your kernel.  If the problem is that the initrd needs to be

And of course a reinstall of the kernel with the right architecture
would solve things if that is the root of the problem.

I always keep a generic i386 kernel installed as a general
bootstrapping aide.  But normally run the tuned kernel for the actual
micro architecture that I am running.

Rich, if you have a i386 kernel installed then try booting that.

> >updated for your new hardware then installing a new kernel should
> >build a new one for your current hardware.  That should get you back
> 
> As long as you update the /etc/modprobe.conf first, then yes.  Or you can
> just nuke the old initrd file or move it out of the way and run another
> "mkinitrd" with the new drivers specified in modprobe.conf, and it'll build
> the right initrd.

What would need to be updated in the /etc/modprobe.conf?  I don't
understand that comment and was hoping you would enlighten me.  I am
used to running discover, hotplug, udev (now all combined) and just
letting it deal with the hardware detection.  Although in the old days
before automatic hardware detection it used to be necessary to load
modules explicitly in /etc/modules.

Bob



More information about the NCLUG mailing list