Dylan Griffiths wrote:
> I just upgraded my one box with a slightly newer kernel, to have it
> not boot. Why was it not booting? Well, it decided to set all kernels
> in my menu.lst to have a root partition of a really long UUID -- a UUID
> string to an HD that was *NOT* in the machine. The new root one (on the
> SATA drive I put in months ago) was clearly marked in the /etc/fstab,
> with the old one commented out.
It seems the blkid.tab file was polluted and had old and new UUIDs in
it. Running blkid seemed to replace the file with a new one. I don't
know why the kernel image doesn't rerun blkid before picking a value
from a possibly stale config file.
It just goes to show: most programmers aren't paranoid enough in sanity
checking their values.
Received on Thu May 31 00:53:28 2007
This archive was generated by hypermail 2.1.8 : Thu May 31 2007 - 00:53:31 CST