Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I actually know most of the answer to my question, but I am stuck on one point.
If grub.conf is corrupt a server will boot to 'grub>'. To boot the server you need to build the root, kernal and initrd lines which would normally appear in grub.conf. I know how to figure out everything excpet the dev device for the boot partition which is needed for the 'root=' parameter on the kernel directive.
I can find and cat /etc/fstab but I'm on Centos6 and it only lists the UUIDs of the partitions.
I could try each dev device one by one until I eventually select the right one but I was hoping there is a more sensible approach. Sadly I've search online but not found a solution to this yet.
Thanks. I forgot you could do that. Is there no way of translating it though as I seem to mistype the UUID frequently when performing these recovery tests.
I don't think so, but not for sure, someone on here with more brains(of course it don't take a whole lot to pass me up in brain power LOL) then me might know that answer.
I concluded there's no way to translate a UUID to device in grub. Whilst tune2fs and blkid offer this, it's obviously not available whilst you're in grub. Therefore the realistic options are:
1. Use the UUID for / in 'cat (hd0,X)/etc/fstab'
2. Trial and error until you hit the correct disk
3. Keep a record of important configuration info of your servers off the system which incudes the UUID maping, which can be used in such emergencies.
From a support perspective I think option 3 would be good practice but may rarely get done.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.