rider799
February 19th, 2010, 01:25 PM
Hello!
I can't recover Ubuntu after installing WinXp. Now i already know that Xp overwrites the MBR file and boots only itself.
I was trying to recover by this strategy(recomended) https://help.ubuntu.com/community/RecoveringUbuntuAfterInstallingWindows with LiveCD.
I use Ubuntu 9.10 Karmic Koala - Grub2
I got stuck on this .. it shows that file /grub/core.img is unreachable
ubuntu@ubuntu:~$ mount | tail -1
/dev/sda5 on /media/79056c34-6519-47f1-96ea-7a83ca531ccf type ext4 (rw,nosuid,nodev,uhelper=devkit)
ubuntu@ubuntu:~$ ls /media/79056c34-6519-47f1-96ea-7a83ca531ccf/boot
abi-2.6.31-14-generic memtest86+.bin
abi-2.6.31-17-generic System.map-2.6.31-14-generic
abi-2.6.31-19-generic System.map-2.6.31-17-generic
config-2.6.31-14-generic System.map-2.6.31-19-generic
config-2.6.31-17-generic vmcoreinfo-2.6.31-14-generic
config-2.6.31-19-generic vmcoreinfo-2.6.31-17-generic
grub vmcoreinfo-2.6.31-19-generic
initrd.img-2.6.31-14-generic vmlinuz-2.6.31-14-generic
initrd.img-2.6.31-17-generic vmlinuz-2.6.31-17-generic
initrd.img-2.6.31-19-generic vmlinuz-2.6.31-19-generic
ubuntu@ubuntu:~$ sudo grub-install --root-directory=/media/79056c34-6519-47f1-96ea-7a83ca531ccf /dev/sda5
grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD idea.
grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and its use is discouraged.
grub-setup: error: Cannot read `/grub/core.img' correctly
ubuntu@ubuntu:~$ sudo grub-install --root-directory=/media/79056c34-6519-47f1-96ea-7a83ca531ccf /dev/sda5 --recheck
grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD idea.
grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and its use is discouraged.
grub-setup: error: Cannot read `/grub/core.img' correctly
ubuntu@ubuntu:~$ sudo fdisk -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xba10ba10
Device Boot Start End Blocks Id System
/dev/sda1 * 1 6502 52227283+ 7 HPFS/NTFS
/dev/sda2 6503 25860 155493135 7 HPFS/NTFS
/dev/sda3 25861 38913 104848222+ 5 Extended
/dev/sda5 25861 38539 101844036 83 Linux
/dev/sda6 38540 38913 3004123+ 82 Linux swap /Solaris
Also when i checked the files on dev/sda5 on live session with LiveCD - the folders "root" and "lost+found" are unavailable "The folder contents could not be displayed. You do not have the permissions necessary to view contents of .."
maybe that's why there is not the line lost+found after command "ls /media/79056c34-6519-47f1-96ea-7a83ca531ccf/boot"
Has someone expierenced the same?
I don't get it where is problem? I am beginner in Ubuntu and linux systems :)
On previous Ubuntu (before installing WinXp) i had a password - does it make some selfdefense when i try to install new MBR?
I would like to have dual-boot afterwards.
I will aprreciate every help! :)
I can't recover Ubuntu after installing WinXp. Now i already know that Xp overwrites the MBR file and boots only itself.
I was trying to recover by this strategy(recomended) https://help.ubuntu.com/community/RecoveringUbuntuAfterInstallingWindows with LiveCD.
I use Ubuntu 9.10 Karmic Koala - Grub2
I got stuck on this .. it shows that file /grub/core.img is unreachable
ubuntu@ubuntu:~$ mount | tail -1
/dev/sda5 on /media/79056c34-6519-47f1-96ea-7a83ca531ccf type ext4 (rw,nosuid,nodev,uhelper=devkit)
ubuntu@ubuntu:~$ ls /media/79056c34-6519-47f1-96ea-7a83ca531ccf/boot
abi-2.6.31-14-generic memtest86+.bin
abi-2.6.31-17-generic System.map-2.6.31-14-generic
abi-2.6.31-19-generic System.map-2.6.31-17-generic
config-2.6.31-14-generic System.map-2.6.31-19-generic
config-2.6.31-17-generic vmcoreinfo-2.6.31-14-generic
config-2.6.31-19-generic vmcoreinfo-2.6.31-17-generic
grub vmcoreinfo-2.6.31-19-generic
initrd.img-2.6.31-14-generic vmlinuz-2.6.31-14-generic
initrd.img-2.6.31-17-generic vmlinuz-2.6.31-17-generic
initrd.img-2.6.31-19-generic vmlinuz-2.6.31-19-generic
ubuntu@ubuntu:~$ sudo grub-install --root-directory=/media/79056c34-6519-47f1-96ea-7a83ca531ccf /dev/sda5
grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD idea.
grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and its use is discouraged.
grub-setup: error: Cannot read `/grub/core.img' correctly
ubuntu@ubuntu:~$ sudo grub-install --root-directory=/media/79056c34-6519-47f1-96ea-7a83ca531ccf /dev/sda5 --recheck
grub-setup: warn: Attempting to install GRUB to a partition instead of the MBR. This is a BAD idea.
grub-setup: warn: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and its use is discouraged.
grub-setup: error: Cannot read `/grub/core.img' correctly
ubuntu@ubuntu:~$ sudo fdisk -l
Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xba10ba10
Device Boot Start End Blocks Id System
/dev/sda1 * 1 6502 52227283+ 7 HPFS/NTFS
/dev/sda2 6503 25860 155493135 7 HPFS/NTFS
/dev/sda3 25861 38913 104848222+ 5 Extended
/dev/sda5 25861 38539 101844036 83 Linux
/dev/sda6 38540 38913 3004123+ 82 Linux swap /Solaris
Also when i checked the files on dev/sda5 on live session with LiveCD - the folders "root" and "lost+found" are unavailable "The folder contents could not be displayed. You do not have the permissions necessary to view contents of .."
maybe that's why there is not the line lost+found after command "ls /media/79056c34-6519-47f1-96ea-7a83ca531ccf/boot"
Has someone expierenced the same?
I don't get it where is problem? I am beginner in Ubuntu and linux systems :)
On previous Ubuntu (before installing WinXp) i had a password - does it make some selfdefense when i try to install new MBR?
I would like to have dual-boot afterwards.
I will aprreciate every help! :)