Re: [SOLVED] lilo config is busted, need help fixing it
On Sat, 02 Oct 2010 13:54:11 -0400 (EDT), email@example.com wrote:
> Stephen Powell wrote:
>> Right now, it's only a working setup for one kernel: 2.6.32-5-amd64.
>> If you're not going to make these changes, you might as well
>> de-install the other kernels. They will not boot, so what good are
>> they? What 2.6.32-5-amd64 calls /dev/sda is a PATA disk, which will be
>> treated as /dev/hda by all the other kernels.
> I got rid of the unused images because I really don't need them.
> I put in all the UUID and dev/by-id changes and much to my relief the
> system still boots !
Good! Don't forget to re-run lilo after making the changes, if you
haven't already done so. The change to the root specification requires
that lilo be re-run.
>> # /etc/fstab: static file system information.
>> # <file system> <mount point> <type> <options> <dump> <pass>
>> proc /proc proc defaults 0 0
>> UUID=a948d6b6-8395-49a1-9f0f-21a10ceee9c2 / ext3 defaults,errors=remount-ro 0 1
>> # /dev/sda2 / ext3 defaults,errors=remount-ro 0 1
>> UUID=4b764501-da53-4323-a751-3da37d7e2a91 /home ext3 defaults 0 2
>> # /dev/sda3 /home ext3 defaults 0 2
>> UUID=558d7790-5914-494d-938f-3387296eed45 none swap sw 0 0
>> # /dev/sda4 none swap sw 0 0
> ok, I put this in too. Is there any way to validate the fstab file so
> that I know it's right ?? I mean other than umount and mount...
There are a couple of ways. One way is to use the blkid command.
will return the uuid of /dev/sda2. The other way is to issue
ls -Al /dev/disk/by-uuid/
which will list all the udev-created symbolic links that have a uuid
in them and what they are links to. I prefer the second method because
it lists them all with a single command and also because it makes
sure that udev (at least this portion of it) is working properly.
> p.s. again, thank you.
You're welcome. I'm glad I could help.
.''`. Stephen Powell
: :' :