@Rony:
If you could put up your query again in a simple way, point wise, it may get more replies. :)
Well,I tried to give the paramount things,namely what I did before the stuff happened,what happened,what I tried and what is the present situation.I'm sorry if it became unreadable.
This site is usefull too.
https://help.ubuntu.com/community/RecoveringUbuntuAfterInstallingWindows?act...
If you read my original post,you would find that I've already reinstalled Grub from Ubuntu Live CD.The problem is that Grub tells me it cannot mount the partition it itself is on!
@JTD
Have you tried the console method i posted? what was the result.
I tried and the result was posted to the list.I tried some variations too.For your benefit:
"Boot unsuccessful. /dev/hda7(/ for Ubuntu) had vmlinuz as symlink to boot/vmlinuz- 2.6.20-16-generic and a vmlinuz.old as symlink to boot/vmlinuz- 2.6.20-15-generic,both owned by root and 777 permissions. Similarly,initrd.img was symlink to boot/initrd.img-2.6.20-15-generic and initrd.img.old was symlink to boot/initrd.img- 2.6.20-15-generic,again owned by root and 777 permissions. I tried root=/dev/hda7 and root=/dev/hda5 with root (hd0,4).I also deleted the above symlinks in chroot mode because my /boot partition is not automount in my Ubuntu fstab and there's no use of symlinks which point to a file on a partition which is not mounted.Hopefully,that's not wrong. :P"
PS:I was thinking of moving my /var/cache/apt/archives to my
/home partition and fresh install w/o touching the /home partition in case nothing works out.Is that a good idea?
I have yet to see an install which could not be booted with grub.
Here you see one. ;)
Regards, Easwar
On Friday 10 August 2007 17:43, Easwar Hariharan wrote:
@JTD
Have you tried the console method i posted? what was the result.
I tried and the result was posted to the list.I tried some variations too.For your benefit:
Err i seemed to have missed the post.
Here is what i am talking about. Once u press c at the grub menu grub> root (hd0,4) Filesystem type is jfs, partition type 0x83
grub> kernel /vmlinuz root=/dev/hda5 [Linux-bzImage, setup=0x1400, size=0x108a19]
grub>initrd /initrd.img [Linux-initrd @ 0x1debc000, 0x124000 bytes]
grub> boot
Please do the above and post
"Boot unsuccessful. /dev/hda7(/ for Ubuntu) had vmlinuz as symlink to boot/vmlinuz- 2.6.20-16-generic and a vmlinuz.old as symlink to boot/vmlinuz- 2.6.20-15-generic,both owned by root and 777 permissions. Similarly,initrd.img was symlink to
symlinks work with grub as long as they are on the same partition as the grub root (hd0,4) in the abv example. Grub has auto completion like bash. Hitting tab after a command will show what grub wants and or sees. at the grub prompt type root (hd and hit the tab key, grub will list the disks that it sees. next type (hd0 and hit tab grub should give u a list of partitions. next type (hd0,4) and hit enter. Grub should give you a line like Filesystem type is jfs, partition type 0x83 type kernel / and hit tab. Grub will show a list of files.
Here you see one. ;)
just a communication gap methinks.
On 8/13/07, jtd jtd@mtnl.net.in wrote:
Here is what i am talking about. Once u press c at the grub menu grub> root (hd0,4) Filesystem type is jfs, partition type 0x83
We tried this over when he came on IRC. For some reason ubuntu fails to give any information on this. I checked on Debian and Gentoo, it gives right information but Ubuntu gave none, checked it on the Ubuntu install I have on my PC, too.
jtd wrote:
Here is what i am talking about. Once u press c at the grub menu grub> root (hd0,4) Filesystem type is jfs, partition type 0x83
grub> kernel /vmlinuz root=/dev/hda5 [Linux-bzImage, setup=0x1400, size=0x108a19]
grub>initrd /initrd.img [Linux-initrd @ 0x1debc000, 0x124000 bytes]
grub> boot
I tried out the commands given above and actually booted into the system. First time this way. Since its was a long time that I had installed the OSes I used 'find /boot/grub/stage1' to locate all my root partitions. However after that grub never returns any output unless its an error.
Easwar's problem turns out to be a corrupted /boot partition. I am curious to know how he restored all his /boot files after deleting and re-creating the partition. Is it as simple as backing up the files somewhere else and pasting them back or getting them from some new source.
-
Easwar Hariharan -
jtd -
mehul -
Rony