> While in that particular instance I solved the problem by booting from a 
> rescue
> CD, mounting the the root, and rebuilding the kernel to include the driver for
> the IDE controller, since you have nothing to lose on /dev/hda2 (I suppose) I
> would second Michael's suggestion for a quick fix - just try the stable 
> variant.
> However, if you are feeling adventurous, boot into rescue mode, mount 
> /dev/hda2,
> and mess around with the kernel.

For a Ubuntu fix to the problem here's my recomendation

Use a live CD
mount root (/dev/hda2?) somewhere like /realroot
mkdir /realroot
mount /dev/hda2 /realroot

mount /dev and /proc in there too
mount -o bind /dev /realroot/dev
mount -t proc proc /realroot/proc

chroot into the root partition
chroot /realroot /bin/bash

edit fstab
vi /etc/fstab

regenerate Ubuntu's initial ram disk (initrd) --  those are back-ticks
arround uname -r
dpkg-reconfigure linux-image-`uname -r`

exit chroot and reboot

exit
reboot

cross your fingers.

--
Michael Moore
-------------------------------
www.stuporglue.org -- Donate your used computer to a student that needs it.

--------------------
BYU Unix Users Group
http://uug.byu.edu/

The opinions expressed in this message are the responsibility of their
author.  They are not endorsed by BYU, the BYU CS Department or BYU-UUG.
___________________________________________________________________
List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list

Reply via email to