A slightly different grub question

[u-noneinc-s]

@leigh:

rpm -qV grub

returns nothing (so presumably the "package" is good). Would you still recommend removing and replacing it?

[leigh123linux]

Originally Posted by u-noneinc-s

@leigh:

rpm -qV grub

returns nothing (so presumably the "package" is good). Would you still recommend removing and replacing it?

Wrong command try

debian:/# rpm -q grub
grub-0.97-13

If it not working yes

I would also backup your grub.conf

su -
cp /boot/grub/grub.conf /root/grub.conf

[u-noneinc-s]

I knew rpm -q grub worked. I did that quite some time ago. And it does return grub-0.97-13.
I used the -V for verification. Is the -V useless in this case? Is -V just to verify package integrity when a compromise is suspected (rkhunter tripwire etc)?

[leigh123linux]

Originally Posted by u-noneinc-s

I knew rpm -q grub worked. I did that quite some time ago. And it does return grub-0.97-13.
I used the -V for verification. Is the -V useless in this case? Is -V just to verify package integrity when a compromise is suspected (rkhunter tripwire etc)?

-V only works with these commands

Verify options (with -V or --verify):
--nomd5 don't verify MD5 digest of files
--nofiles don't verify files in package
--nodeps don't verify package dependencies
--noscript don't execute verify script(s)
-a, --all query/verify all packages
-f, --file query/verify package(s) owning file
-g, --group query/verify package(s) in group
-p, --package query/verify a package file
-W, --ftswalk query/verify package(s) from TOP file tree
walk
--pkgid query/verify package(s) with package
identifier
--hdrid query/verify package(s) with header
identifier
--fileid query/verify package(s) with file identifier
--specfile query a spec file
--triggeredby query the package(s) triggered by the
package
--whatrequires query/verify the package(s) which require a
dependency
--whatprovides query/verify the package(s) which provide a
dependency
--nomanifest do not process non-package files as
manifests

[u-noneinc-s]

OK, I went with Leigh's suggestion. rpm -e --nodeps grub-0.97-13 then yum install grub, and I still get the same error on the grub command.

root@spongie:~# grub
grub: asmstub.c:214: grub_stage2: Assertion `simstack_alloc_base != ((void *) -1)' failed.
Aborted

So I guess I'll go with the upgrade option from the install screen. It's worked before so it should work again.
I'll try some reboots first to see if I really need to. (See what boots or doesn't boot).

[u-noneinc-s]

Everything boot fine. Windows, and both FC6 partitions boot just fine. I don't know why the grub command doesn't work unless it needs to be run from rescue (or init 1 or 3).

Anyway, there doesn't seem to be a problem (except the original) and I think Seve gave the me the answer I was looking for (or at least the one I expected). That grub-install should be done from rescue and not a running system.

Thanks Seve and leigh123*