Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Here I am facing a problem with GRUB. The problem is that when i boot up my machine, grub hangs saying as "GRUB". It does not come up showing the boot loader. Then I found that the problem lies with the parition table. I went with the rescue mode and found that my partition table has become odd.. Following is the output of my fdisk command..Can somebody tell me how resolv this problem..??
Device Boot Start End Blocks Id System
/dev/hda1 * 1 26 102406 83 Linux
Partition 1 has different physical/logical endings:
phys=(12, 191, 63) logical=(25, 51, 63)
Partition 1 does not end on cylinder boundary.
phys=(12, 191, 63) should be (12, 127, 63)
/dev/hda2 26 156 524317+ 82 Linux swap
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(12, 192, 1) logical=(25, 52, 1)
Partition 2 has different physical/logical endings:
phys=(78, 6, 63) logical=(155, 56, 63)
Partition 2 does not end on cylinder boundary.
phys=(78, 6, 63) should be (78, 127, 63)
/dev/hda3 156 508 1421343 83 Linux
Partition 3 has different physical/logical beginnings (non-Linux?):
phys=(78, 7, 1) logical=(155, 57, 1)
Partition 3 has different physical/logical endings:
phys=(254, 248, 63) logical=(507, 122, 63)
Partition 3 does not end on cylinder boundary.
YES! That happened to me! I installed FreeBSD 6.0 and it messed up my partitions, thing is, every partition and GRUB works, but I have the "Partition 1 does not end on cylinder boundary" error. I do not want to repartition my system incase I lose all my data.
Does not seem like a GRUB issue....I would infer that GRUB hangs because it cannot get to the files it needs---that in turn is (maybe) because there is an issue with the partition tables.
First, do not do ANYTHING to this disk that might overwrite you data. The data may well be recoverable.
Please describe your actions leading up to this---ie what did you do that might have mucked up the partition table(s)
yep there are lots of partition table issues some important and others not.
1 boot a live cd and see if you can click on your partitions after loading kanotix or knoppix etc if you can no problemo
then if ONE is ok..... no harm is done by re-installing grub into mbr and mbr is only a separate 512 byte file at beginning of hard drive that contains a bootloader and does not change your partition table.....using kanotix or knoppix open a terminal and its your commands
root (hdX,y) as per my tut...where is /boot partition
if 1 fails then you may need to rescue your partition table
2....not sure what distro cd you used for rescue mode......they are often just a bunch of tools....some even allow ntldr back into mbr
3 Next time consider backing up your partition table using the dd command or partimage....assuming 1 was ok
then if ONE is ok..... no harm is done by re-installing grub into mbr and mbr is only a separate 512 byte file at beginning of hard drive that contains a bootloader and does not change your partition table.....
This is an acknowledged nitpick:
the mbr is 446 bytes
partition table 64 bytes
"signature" 2 bytes
Depending on the method for putting grub in the mbr, you can wipe out the partition table. (eg the misuse of "dd")
This happens on my Virtual Machine which is a migrated or cloned from another. The source VM is installed with RHEL (min packages) which works fine and the partition table is perfect. This VM is migrated to another virtualization layer and then the migrated Virtual machine gets this problem.
This does not happen if the migrated VM is migrated from the source with default packages. And so probably, the package which handle the partitioning is missing there in the above case.
One possible way of solution is by rebuilding the partition table or find the correct rpms required for this..Anybody can help me out in this??
then you have to troubleshoot and decide if it was a grub error or some other error.
pretending you are committed to this scheme that you want perfectly aligned boundaries....consider that if you do use a tool to correct it (if it needed it) then you will have to re-install your stuff or use images to put on to the new partitions.
plse advise if you have done my request and used a live cd or not....if you wish to ignore me thats fine with me.
Vampirite.. I think you can use fdisk in your case. How is your disk partitioned? Is your first partition, a boot partition? If yes, then you can resolv this..
Make a backup of /boot. Then type fdisk -l /dev/hda. Mention the correct parameter to delete the partition. Create a new one with correct CHS. Asssign a Bootable Flag if it is /boot. Format it using mkfs. Restore back your backup. Hope this works..It did worked for me..
Ok, it was actually partition 2, which is my extended partition and which contains my data partitions (and linux one).
Today, I tried to resolve this, in cfdisk I had some free space between the extended and primary, thinking this might be a problem, I created a partition and formatted it as ext2 but it didn't make a difference.
I haven't had time to read all the things mentioned before so this mightn't help, but i had the same problem last week when i re-set my laptop to dual boot and i solved it by reinstalling grub (this allowed me to boot into Linux)! and then ran the dd command (so that i could boot into windows as well):