Re: New hard drive problem
On Wed, Aug 15, 2007 at 00:04:43 -0400, William Walter wrote:
> >On Sun, Aug 12, 2007 at 13:56:21 -0400, William Walter wrote:
> > The problem resurfaced again today. The same error message came up and
> > Debian Etch refuse to boot up.
> > I used UUID of all the hard drives. Still no luck in fixing this problem.
> Is
> > there anything else I should
> > do?
> >
> >>Florian Kulzer wrote:
> >> Where did you put the UUIDs? Both into /etc/fstab and into
> >> /boot/grub/menu.lst?
>
> Okay. Now i've changed the entry in menu.lst to use UUID.
> There's no sign of booting problem for now. Thanks for
> pointing that out.
>
> >> Did you update your initrd after making the
> >> changes?
>
> How can I do that?
If you are using a stock Debian kernel or a self-compiled kernel built
with make_kpkg then you can simply run "dpkg-reconfigure" on your kernel
image, i.e.
dpkg-reconfigure linux-image-$(uname -r)
This will take care of the initrd automatically. (The "$(uname -r)" part
expands into the version string of your currently running kernel.)
You can also call the initrd generator directly, "mkinitrd" or "yaird";
see the manpages for details. (The default for Debian is to use
mkinitrd, I think.)
Right now it looks like you don't have to do anything to the initrd. I
just mentioned it for the sake of completeness: If boot problems persist
even after fixing /etc/fstab and /boot/grub/menu.lst then the initrd is
the next thing to check since it also contains information about the
location of the root partition.
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Reply to: