compiling chrooted kernel makes drive unbootable
infofarmer at gmail.com
Sat Oct 29 15:48:29 PDT 2005
On 10/30/05, Dave <dmehler26 at woh.rr.com> wrote:
> I've got a box that has died. The data on it is rather important and a
> reinstall is not feasible. I put the hard drive in a test box, mounted all
> the partitions of the previous drive under /mnt then did a chroot /mnt and
> compiled a generic kernel. The processor on this board is different so i
> felt i had to. The compilation and installation of the chrooted kernel went
> fine, putting the drive in the new system yields an unbootable drive. I've
> checked the data and kernel are there. Any ideas why this procedure didn't
> give me a bootable drive?
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
Any more info, please?
What exactly has died? Has any data been lost?
Why did you have to recompile the kernel? Did you
recompile the world, too? How different are the
processors on the dead system, the one you've
recompiled on and the new one?
You can always run a fresh install without
formatting your drives and thus losing only some
system configuration files.
More information about the freebsd-questions