Failed to get canonical path of /cow
I am trying to install Ubuntu 12.10 for quite some time, and passing hurdles one by one. Now I am in a situation as follows.
I have got a PC and 10 GB HDD which will be totally dedicated to Ubuntu so no option of Wubi and dual boot.
I was trying to install from DVD, but it is getting stuck at "Out of frequency" error. So I had to adapt for USB boot option. But my PC is USB non bootable, so workaround is "Plop Boot Manager". So I am doing the installation procedure as follows:
- starting from a CD drive which is having plop installed.
- opting for for USB boot in plop options.
- booting begins from USB.
- monitor eventually gives "out of frequency" error
- press Shift+Alt+F1 to get the terminal.
- open the grub with
sudo nano /etc/default/grub
. - do necessary changes.
sudo update-grub
.
Now here I am getting error as follows:
/usr/sbin/grub-probe:error:failed to get canonical path of /cow.
My system is
P4 3.06 GHz, 1 GB ram , 10 GB HDD without an OS, monitor CRT lg StudioWorks (7 years old). Mobo Mercury P4 266a NDMx (865 equivalent). The whole system is perfectly in working condition under XP, but it is USB non bootable, and all other devices working perfectly.
What should I do next?
grub2 usb live-usb usb-creator
|
show 5 more comments
I am trying to install Ubuntu 12.10 for quite some time, and passing hurdles one by one. Now I am in a situation as follows.
I have got a PC and 10 GB HDD which will be totally dedicated to Ubuntu so no option of Wubi and dual boot.
I was trying to install from DVD, but it is getting stuck at "Out of frequency" error. So I had to adapt for USB boot option. But my PC is USB non bootable, so workaround is "Plop Boot Manager". So I am doing the installation procedure as follows:
- starting from a CD drive which is having plop installed.
- opting for for USB boot in plop options.
- booting begins from USB.
- monitor eventually gives "out of frequency" error
- press Shift+Alt+F1 to get the terminal.
- open the grub with
sudo nano /etc/default/grub
. - do necessary changes.
sudo update-grub
.
Now here I am getting error as follows:
/usr/sbin/grub-probe:error:failed to get canonical path of /cow.
My system is
P4 3.06 GHz, 1 GB ram , 10 GB HDD without an OS, monitor CRT lg StudioWorks (7 years old). Mobo Mercury P4 266a NDMx (865 equivalent). The whole system is perfectly in working condition under XP, but it is USB non bootable, and all other devices working perfectly.
What should I do next?
grub2 usb live-usb usb-creator
Does your computer have the Recommended Minimum System Requirements to run Ubuntu? I have had problems installing 12.04 to machines with less than 1GB RAM.
– C.S.Cameron
Feb 14 '13 at 5:49
Yes ,Now I have added my system specification to question.
– ulkaNCST
Feb 14 '13 at 7:56
askubuntu.com/questions/207663/… might be worth a try.
– Rinzwind
Feb 14 '13 at 7:59
5
First mount your hard drive to some folder, say/mnt
and thenchroot
to/mnt
.
– green
Feb 18 '13 at 3:44
3
possible duplicate of How can I repair grub? (How to get Ubuntu back after installing Windows?)
– psusi
Apr 2 '14 at 18:30
|
show 5 more comments
I am trying to install Ubuntu 12.10 for quite some time, and passing hurdles one by one. Now I am in a situation as follows.
I have got a PC and 10 GB HDD which will be totally dedicated to Ubuntu so no option of Wubi and dual boot.
I was trying to install from DVD, but it is getting stuck at "Out of frequency" error. So I had to adapt for USB boot option. But my PC is USB non bootable, so workaround is "Plop Boot Manager". So I am doing the installation procedure as follows:
- starting from a CD drive which is having plop installed.
- opting for for USB boot in plop options.
- booting begins from USB.
- monitor eventually gives "out of frequency" error
- press Shift+Alt+F1 to get the terminal.
- open the grub with
sudo nano /etc/default/grub
. - do necessary changes.
sudo update-grub
.
Now here I am getting error as follows:
/usr/sbin/grub-probe:error:failed to get canonical path of /cow.
My system is
P4 3.06 GHz, 1 GB ram , 10 GB HDD without an OS, monitor CRT lg StudioWorks (7 years old). Mobo Mercury P4 266a NDMx (865 equivalent). The whole system is perfectly in working condition under XP, but it is USB non bootable, and all other devices working perfectly.
What should I do next?
grub2 usb live-usb usb-creator
I am trying to install Ubuntu 12.10 for quite some time, and passing hurdles one by one. Now I am in a situation as follows.
I have got a PC and 10 GB HDD which will be totally dedicated to Ubuntu so no option of Wubi and dual boot.
I was trying to install from DVD, but it is getting stuck at "Out of frequency" error. So I had to adapt for USB boot option. But my PC is USB non bootable, so workaround is "Plop Boot Manager". So I am doing the installation procedure as follows:
- starting from a CD drive which is having plop installed.
- opting for for USB boot in plop options.
- booting begins from USB.
- monitor eventually gives "out of frequency" error
- press Shift+Alt+F1 to get the terminal.
- open the grub with
sudo nano /etc/default/grub
. - do necessary changes.
sudo update-grub
.
Now here I am getting error as follows:
/usr/sbin/grub-probe:error:failed to get canonical path of /cow.
My system is
P4 3.06 GHz, 1 GB ram , 10 GB HDD without an OS, monitor CRT lg StudioWorks (7 years old). Mobo Mercury P4 266a NDMx (865 equivalent). The whole system is perfectly in working condition under XP, but it is USB non bootable, and all other devices working perfectly.
What should I do next?
grub2 usb live-usb usb-creator
grub2 usb live-usb usb-creator
edited Feb 18 '14 at 16:53
Olli
6,91613040
6,91613040
asked Feb 13 '13 at 4:18
ulkaNCSTulkaNCST
316139
316139
Does your computer have the Recommended Minimum System Requirements to run Ubuntu? I have had problems installing 12.04 to machines with less than 1GB RAM.
– C.S.Cameron
Feb 14 '13 at 5:49
Yes ,Now I have added my system specification to question.
– ulkaNCST
Feb 14 '13 at 7:56
askubuntu.com/questions/207663/… might be worth a try.
– Rinzwind
Feb 14 '13 at 7:59
5
First mount your hard drive to some folder, say/mnt
and thenchroot
to/mnt
.
– green
Feb 18 '13 at 3:44
3
possible duplicate of How can I repair grub? (How to get Ubuntu back after installing Windows?)
– psusi
Apr 2 '14 at 18:30
|
show 5 more comments
Does your computer have the Recommended Minimum System Requirements to run Ubuntu? I have had problems installing 12.04 to machines with less than 1GB RAM.
– C.S.Cameron
Feb 14 '13 at 5:49
Yes ,Now I have added my system specification to question.
– ulkaNCST
Feb 14 '13 at 7:56
askubuntu.com/questions/207663/… might be worth a try.
– Rinzwind
Feb 14 '13 at 7:59
5
First mount your hard drive to some folder, say/mnt
and thenchroot
to/mnt
.
– green
Feb 18 '13 at 3:44
3
possible duplicate of How can I repair grub? (How to get Ubuntu back after installing Windows?)
– psusi
Apr 2 '14 at 18:30
Does your computer have the Recommended Minimum System Requirements to run Ubuntu? I have had problems installing 12.04 to machines with less than 1GB RAM.
– C.S.Cameron
Feb 14 '13 at 5:49
Does your computer have the Recommended Minimum System Requirements to run Ubuntu? I have had problems installing 12.04 to machines with less than 1GB RAM.
– C.S.Cameron
Feb 14 '13 at 5:49
Yes ,Now I have added my system specification to question.
– ulkaNCST
Feb 14 '13 at 7:56
Yes ,Now I have added my system specification to question.
– ulkaNCST
Feb 14 '13 at 7:56
askubuntu.com/questions/207663/… might be worth a try.
– Rinzwind
Feb 14 '13 at 7:59
askubuntu.com/questions/207663/… might be worth a try.
– Rinzwind
Feb 14 '13 at 7:59
5
5
First mount your hard drive to some folder, say
/mnt
and then chroot
to /mnt
.– green
Feb 18 '13 at 3:44
First mount your hard drive to some folder, say
/mnt
and then chroot
to /mnt
.– green
Feb 18 '13 at 3:44
3
3
possible duplicate of How can I repair grub? (How to get Ubuntu back after installing Windows?)
– psusi
Apr 2 '14 at 18:30
possible duplicate of How can I repair grub? (How to get Ubuntu back after installing Windows?)
– psusi
Apr 2 '14 at 18:30
|
show 5 more comments
5 Answers
5
active
oldest
votes
After booting from the Ubuntu live CD (Tried 14.04 and 16.04) I was able to work around this problem by running update-grub chroot'ed to the grub partition. (Substitute /dev/sda1
below with whatever partition you installed grub on. All commands as root.)
mkdir /mnt/chrootdir
mount /dev/sda1 /mnt/chrootdir
for dir in proc dev sys etc bin sbin var usr lib lib64 tmp; do
mkdir /mnt/chrootdir/$dir && mount --bind /$dir /mnt/chrootdir/$dir
done
chroot /mnt/chrootdir
update-grub2 # inside chroot
2
Attempting to run mount gives me the error:,NTFS signature is missing.
which is odd, because it should be Ext4, not NTFS...
– Cerin
Apr 13 '15 at 3:01
@Cerin, I emphasize /dev/sda1 was the right partition for me, but evidently not for you, if that volume is NTFS.
– Nathan Kidd
Apr 13 '15 at 15:55
Your solution is confusing. Do you need to run the first part and the second from within the chroot of the first? Or do you throw away everything you did in the first part and only run the second part? Why do you mount both /dev/sda and /dev/sda1?
– Cerin
Apr 15 '15 at 1:18
/dev/sda was a typo, it should be /dev/sda1, sorry. I updated the info. Is it clearer now?
– Nathan Kidd
Apr 15 '15 at 16:13
2
I followed your instructions and ended up with/usr/sbin/grub-probe: error: failed to get canonical path of '/boot'.
I had only my/boot
partition on my boot drive, the rest was elsewhere.
– ArtB
Sep 30 '15 at 1:13
|
show 2 more comments
Find your drive that's supposed to boot with
mount
Or
parted -l
Or
fdisk /dev/sda
And type p to list the partitions, look for type 83.
(If you've got Fedora you might have to use the commands "vgs" and "lvs" and if you've got mdraid you might have to "cat /proc/mdstat" or mdadm -A --scan or insmod raid1 or insmod raid5 and then mdadm -A --scan) and you will use /dev/md0 or /dev/mapper/my-vg instead of /dev/sda
then try mount it
mkdir /mnt
mount /dev/sda1 /mnt
cd /mnt
ls -l
Is this your drive? Cool!
grub-install --recheck --root-directory=/mnt /dev/sda
(Or whichever /dev drive your root is, with it's mounted path)
grub-install --recheck --root-directory=/mnt /dev/sda --force
(Force it if it doesn't like your partitions.)
Now it should boot into grub, and you can use the grub commands to boot up, after rebooting and selecting the right boot drive from the BIOS Setup, or by pressing ESC or F12 depending on your BIOS and whether you are quick enough, then at the Grub prompt - you can use tab completion to find it if it's not (hd0,1) but (hd1,3) or something else instead, but beware, tab completion sometimes hangs for a few seconds if grub can't read the drive.
insmod linux
ls
root=(hd0,1)
linux /boot/vmlinuz root=/dev/sda1
initrd /boot/initrd
boot
Or, hopefully you've still got an intact grub.cfg file... or maybe this will work:
grub-mkconfig -o /mnt/boot/grub/grub.cfg
1
It didn't like my partitions, but-f
wasn't working. I had to use--force
– R.M
Jan 7 at 19:12
add a comment |
Revised solution based on code above
The solution from above will not work totally without problems because it mounts the boot partition into the / (root) of the file system. That makes grub complain that /boot does not exist, of course. This will fix that problem:
mkdir /mnt/chrootdir
mkdir /mnt/chrootdir/boot
mount /dev/sda1 /mnt/chrootdir/boot
for dir in proc dev sys etc bin sbin var usr lib lib64 tmp; do mkdir /mnt/chrootdir/$dir && mount --bind /$dir /mnt/chrootdir/$dir ; done
chroot /mnt/chrootdir
update-grub2 # inside chroot
As you see i also removed the line breaks so that it is easier to execute for everyone.
Another (simpler) solution
If you keep having problems getting it to work you should look to copy the /boot partition onto the / (root) partition. For that start your system with the Ubuntu live boot dvd and open the terminal. Inside it type:
sudo su
fdisk -l
To find out which partitions you have. In my case sda1 is my /boot partition which is about 250MB large and an sda5 which is about 500GB. I use these values in the commands below:
mkdir /mnt/boot/
mount /dev/sda1 /mnt/boot/
mkdir /mnt/root/
mount /dev/sda5 /mnt/root/
cp -R /mnt/boot/ /mnt/root/boot/
Set the bootable flag for the data partition and remove it for the boot partition:
fdisk /dev/sda
b -> 1 (unset the bootable flag for the first partition)
b -> 5 (set the bootable flag for the fifth partition)
w -> write changes to the MBR
Your computer will now look inside the sda5 for the boot files. Time to do the chrooting again, this time with some required folders needed for grub and which are generated by your Ubuntu live disc already:
mkdir /mnt/chrootdir/
mkdir /mnt/chrootdir/dev/
mkdir /mnt/chrootdir/proc/
mkdir /mnt/chrootdir/sys/
mount /dev/sda5 /mnt/chrootdir/
mount --bind /dev/ /mnt/chrootdir/dev/
mount --bind /proc/ /mnt/chrootdir/proc/
mount --bind /sys/ /mnt/chrootdir/sys/
chroot /mnt/chrootdir/
grub-install /dev/sda
Installation finished. No error reported.
If you do not see a message that the grub.cnf file is generated then also run the update command:
update-grub2 /dev/sda
Now you can safely reboot and see the well known boot menu appear again.
This solution was the only one which was working for me after migrating from a physical server to a virtual machine. I hope someone finds this useful!
add a comment |
I know, it's a old problem, but I had the same troubles today with the actual version of mint-linux (ubuntu-based). I found a very simply solution! :-) Take off the internet-connection during the first installation. This stop loading of a non compatible grub2. Make the update of all after installation has finished.
add a comment |
It is the update-grub command which will give you the error when using it from a live cd. I faced with a similar situation when i was doing a grub rescue. The problem you have is that update-grub and grub-install commands do not work directly under live cd (I don't know why). So, you have to go to /usr/sbin where the commands are located and execute them from there (i.e ./update-grub).
No, you have to mount the hard disk and chroot into it, like @green7 said.
– psusi
Apr 2 '14 at 18:27
my method also works. try it. its simpler
– aveemashfaq
Apr 4 '14 at 12:32
1
You don't have a method. /usr/sbin is on the path already so there is no need to cd there. You can't run grub-install and update-grub directly from the live cd ( as you noted ) because it tries to set up grub to boot the current system, which would be the live cd, rather than the os installed on the hard drive.
– psusi
Apr 4 '14 at 14:00
This, of course, doesn't work. You get the "can't get cannonical path of /cow" error. And the stuff about cd-ing to /usr/sbin... oh boy.
– dan3
Apr 13 '14 at 12:37
try it people. it worked for me all the time
– aveemashfaq
Apr 13 '14 at 13:09
|
show 1 more comment
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f254491%2ffailed-to-get-canonical-path-of-cow%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
After booting from the Ubuntu live CD (Tried 14.04 and 16.04) I was able to work around this problem by running update-grub chroot'ed to the grub partition. (Substitute /dev/sda1
below with whatever partition you installed grub on. All commands as root.)
mkdir /mnt/chrootdir
mount /dev/sda1 /mnt/chrootdir
for dir in proc dev sys etc bin sbin var usr lib lib64 tmp; do
mkdir /mnt/chrootdir/$dir && mount --bind /$dir /mnt/chrootdir/$dir
done
chroot /mnt/chrootdir
update-grub2 # inside chroot
2
Attempting to run mount gives me the error:,NTFS signature is missing.
which is odd, because it should be Ext4, not NTFS...
– Cerin
Apr 13 '15 at 3:01
@Cerin, I emphasize /dev/sda1 was the right partition for me, but evidently not for you, if that volume is NTFS.
– Nathan Kidd
Apr 13 '15 at 15:55
Your solution is confusing. Do you need to run the first part and the second from within the chroot of the first? Or do you throw away everything you did in the first part and only run the second part? Why do you mount both /dev/sda and /dev/sda1?
– Cerin
Apr 15 '15 at 1:18
/dev/sda was a typo, it should be /dev/sda1, sorry. I updated the info. Is it clearer now?
– Nathan Kidd
Apr 15 '15 at 16:13
2
I followed your instructions and ended up with/usr/sbin/grub-probe: error: failed to get canonical path of '/boot'.
I had only my/boot
partition on my boot drive, the rest was elsewhere.
– ArtB
Sep 30 '15 at 1:13
|
show 2 more comments
After booting from the Ubuntu live CD (Tried 14.04 and 16.04) I was able to work around this problem by running update-grub chroot'ed to the grub partition. (Substitute /dev/sda1
below with whatever partition you installed grub on. All commands as root.)
mkdir /mnt/chrootdir
mount /dev/sda1 /mnt/chrootdir
for dir in proc dev sys etc bin sbin var usr lib lib64 tmp; do
mkdir /mnt/chrootdir/$dir && mount --bind /$dir /mnt/chrootdir/$dir
done
chroot /mnt/chrootdir
update-grub2 # inside chroot
2
Attempting to run mount gives me the error:,NTFS signature is missing.
which is odd, because it should be Ext4, not NTFS...
– Cerin
Apr 13 '15 at 3:01
@Cerin, I emphasize /dev/sda1 was the right partition for me, but evidently not for you, if that volume is NTFS.
– Nathan Kidd
Apr 13 '15 at 15:55
Your solution is confusing. Do you need to run the first part and the second from within the chroot of the first? Or do you throw away everything you did in the first part and only run the second part? Why do you mount both /dev/sda and /dev/sda1?
– Cerin
Apr 15 '15 at 1:18
/dev/sda was a typo, it should be /dev/sda1, sorry. I updated the info. Is it clearer now?
– Nathan Kidd
Apr 15 '15 at 16:13
2
I followed your instructions and ended up with/usr/sbin/grub-probe: error: failed to get canonical path of '/boot'.
I had only my/boot
partition on my boot drive, the rest was elsewhere.
– ArtB
Sep 30 '15 at 1:13
|
show 2 more comments
After booting from the Ubuntu live CD (Tried 14.04 and 16.04) I was able to work around this problem by running update-grub chroot'ed to the grub partition. (Substitute /dev/sda1
below with whatever partition you installed grub on. All commands as root.)
mkdir /mnt/chrootdir
mount /dev/sda1 /mnt/chrootdir
for dir in proc dev sys etc bin sbin var usr lib lib64 tmp; do
mkdir /mnt/chrootdir/$dir && mount --bind /$dir /mnt/chrootdir/$dir
done
chroot /mnt/chrootdir
update-grub2 # inside chroot
After booting from the Ubuntu live CD (Tried 14.04 and 16.04) I was able to work around this problem by running update-grub chroot'ed to the grub partition. (Substitute /dev/sda1
below with whatever partition you installed grub on. All commands as root.)
mkdir /mnt/chrootdir
mount /dev/sda1 /mnt/chrootdir
for dir in proc dev sys etc bin sbin var usr lib lib64 tmp; do
mkdir /mnt/chrootdir/$dir && mount --bind /$dir /mnt/chrootdir/$dir
done
chroot /mnt/chrootdir
update-grub2 # inside chroot
edited Sep 4 '18 at 14:27
answered Oct 1 '14 at 14:43
Nathan KiddNathan Kidd
64069
64069
2
Attempting to run mount gives me the error:,NTFS signature is missing.
which is odd, because it should be Ext4, not NTFS...
– Cerin
Apr 13 '15 at 3:01
@Cerin, I emphasize /dev/sda1 was the right partition for me, but evidently not for you, if that volume is NTFS.
– Nathan Kidd
Apr 13 '15 at 15:55
Your solution is confusing. Do you need to run the first part and the second from within the chroot of the first? Or do you throw away everything you did in the first part and only run the second part? Why do you mount both /dev/sda and /dev/sda1?
– Cerin
Apr 15 '15 at 1:18
/dev/sda was a typo, it should be /dev/sda1, sorry. I updated the info. Is it clearer now?
– Nathan Kidd
Apr 15 '15 at 16:13
2
I followed your instructions and ended up with/usr/sbin/grub-probe: error: failed to get canonical path of '/boot'.
I had only my/boot
partition on my boot drive, the rest was elsewhere.
– ArtB
Sep 30 '15 at 1:13
|
show 2 more comments
2
Attempting to run mount gives me the error:,NTFS signature is missing.
which is odd, because it should be Ext4, not NTFS...
– Cerin
Apr 13 '15 at 3:01
@Cerin, I emphasize /dev/sda1 was the right partition for me, but evidently not for you, if that volume is NTFS.
– Nathan Kidd
Apr 13 '15 at 15:55
Your solution is confusing. Do you need to run the first part and the second from within the chroot of the first? Or do you throw away everything you did in the first part and only run the second part? Why do you mount both /dev/sda and /dev/sda1?
– Cerin
Apr 15 '15 at 1:18
/dev/sda was a typo, it should be /dev/sda1, sorry. I updated the info. Is it clearer now?
– Nathan Kidd
Apr 15 '15 at 16:13
2
I followed your instructions and ended up with/usr/sbin/grub-probe: error: failed to get canonical path of '/boot'.
I had only my/boot
partition on my boot drive, the rest was elsewhere.
– ArtB
Sep 30 '15 at 1:13
2
2
Attempting to run mount gives me the error:,
NTFS signature is missing.
which is odd, because it should be Ext4, not NTFS...– Cerin
Apr 13 '15 at 3:01
Attempting to run mount gives me the error:,
NTFS signature is missing.
which is odd, because it should be Ext4, not NTFS...– Cerin
Apr 13 '15 at 3:01
@Cerin, I emphasize /dev/sda1 was the right partition for me, but evidently not for you, if that volume is NTFS.
– Nathan Kidd
Apr 13 '15 at 15:55
@Cerin, I emphasize /dev/sda1 was the right partition for me, but evidently not for you, if that volume is NTFS.
– Nathan Kidd
Apr 13 '15 at 15:55
Your solution is confusing. Do you need to run the first part and the second from within the chroot of the first? Or do you throw away everything you did in the first part and only run the second part? Why do you mount both /dev/sda and /dev/sda1?
– Cerin
Apr 15 '15 at 1:18
Your solution is confusing. Do you need to run the first part and the second from within the chroot of the first? Or do you throw away everything you did in the first part and only run the second part? Why do you mount both /dev/sda and /dev/sda1?
– Cerin
Apr 15 '15 at 1:18
/dev/sda was a typo, it should be /dev/sda1, sorry. I updated the info. Is it clearer now?
– Nathan Kidd
Apr 15 '15 at 16:13
/dev/sda was a typo, it should be /dev/sda1, sorry. I updated the info. Is it clearer now?
– Nathan Kidd
Apr 15 '15 at 16:13
2
2
I followed your instructions and ended up with
/usr/sbin/grub-probe: error: failed to get canonical path of '/boot'.
I had only my /boot
partition on my boot drive, the rest was elsewhere.– ArtB
Sep 30 '15 at 1:13
I followed your instructions and ended up with
/usr/sbin/grub-probe: error: failed to get canonical path of '/boot'.
I had only my /boot
partition on my boot drive, the rest was elsewhere.– ArtB
Sep 30 '15 at 1:13
|
show 2 more comments
Find your drive that's supposed to boot with
mount
Or
parted -l
Or
fdisk /dev/sda
And type p to list the partitions, look for type 83.
(If you've got Fedora you might have to use the commands "vgs" and "lvs" and if you've got mdraid you might have to "cat /proc/mdstat" or mdadm -A --scan or insmod raid1 or insmod raid5 and then mdadm -A --scan) and you will use /dev/md0 or /dev/mapper/my-vg instead of /dev/sda
then try mount it
mkdir /mnt
mount /dev/sda1 /mnt
cd /mnt
ls -l
Is this your drive? Cool!
grub-install --recheck --root-directory=/mnt /dev/sda
(Or whichever /dev drive your root is, with it's mounted path)
grub-install --recheck --root-directory=/mnt /dev/sda --force
(Force it if it doesn't like your partitions.)
Now it should boot into grub, and you can use the grub commands to boot up, after rebooting and selecting the right boot drive from the BIOS Setup, or by pressing ESC or F12 depending on your BIOS and whether you are quick enough, then at the Grub prompt - you can use tab completion to find it if it's not (hd0,1) but (hd1,3) or something else instead, but beware, tab completion sometimes hangs for a few seconds if grub can't read the drive.
insmod linux
ls
root=(hd0,1)
linux /boot/vmlinuz root=/dev/sda1
initrd /boot/initrd
boot
Or, hopefully you've still got an intact grub.cfg file... or maybe this will work:
grub-mkconfig -o /mnt/boot/grub/grub.cfg
1
It didn't like my partitions, but-f
wasn't working. I had to use--force
– R.M
Jan 7 at 19:12
add a comment |
Find your drive that's supposed to boot with
mount
Or
parted -l
Or
fdisk /dev/sda
And type p to list the partitions, look for type 83.
(If you've got Fedora you might have to use the commands "vgs" and "lvs" and if you've got mdraid you might have to "cat /proc/mdstat" or mdadm -A --scan or insmod raid1 or insmod raid5 and then mdadm -A --scan) and you will use /dev/md0 or /dev/mapper/my-vg instead of /dev/sda
then try mount it
mkdir /mnt
mount /dev/sda1 /mnt
cd /mnt
ls -l
Is this your drive? Cool!
grub-install --recheck --root-directory=/mnt /dev/sda
(Or whichever /dev drive your root is, with it's mounted path)
grub-install --recheck --root-directory=/mnt /dev/sda --force
(Force it if it doesn't like your partitions.)
Now it should boot into grub, and you can use the grub commands to boot up, after rebooting and selecting the right boot drive from the BIOS Setup, or by pressing ESC or F12 depending on your BIOS and whether you are quick enough, then at the Grub prompt - you can use tab completion to find it if it's not (hd0,1) but (hd1,3) or something else instead, but beware, tab completion sometimes hangs for a few seconds if grub can't read the drive.
insmod linux
ls
root=(hd0,1)
linux /boot/vmlinuz root=/dev/sda1
initrd /boot/initrd
boot
Or, hopefully you've still got an intact grub.cfg file... or maybe this will work:
grub-mkconfig -o /mnt/boot/grub/grub.cfg
1
It didn't like my partitions, but-f
wasn't working. I had to use--force
– R.M
Jan 7 at 19:12
add a comment |
Find your drive that's supposed to boot with
mount
Or
parted -l
Or
fdisk /dev/sda
And type p to list the partitions, look for type 83.
(If you've got Fedora you might have to use the commands "vgs" and "lvs" and if you've got mdraid you might have to "cat /proc/mdstat" or mdadm -A --scan or insmod raid1 or insmod raid5 and then mdadm -A --scan) and you will use /dev/md0 or /dev/mapper/my-vg instead of /dev/sda
then try mount it
mkdir /mnt
mount /dev/sda1 /mnt
cd /mnt
ls -l
Is this your drive? Cool!
grub-install --recheck --root-directory=/mnt /dev/sda
(Or whichever /dev drive your root is, with it's mounted path)
grub-install --recheck --root-directory=/mnt /dev/sda --force
(Force it if it doesn't like your partitions.)
Now it should boot into grub, and you can use the grub commands to boot up, after rebooting and selecting the right boot drive from the BIOS Setup, or by pressing ESC or F12 depending on your BIOS and whether you are quick enough, then at the Grub prompt - you can use tab completion to find it if it's not (hd0,1) but (hd1,3) or something else instead, but beware, tab completion sometimes hangs for a few seconds if grub can't read the drive.
insmod linux
ls
root=(hd0,1)
linux /boot/vmlinuz root=/dev/sda1
initrd /boot/initrd
boot
Or, hopefully you've still got an intact grub.cfg file... or maybe this will work:
grub-mkconfig -o /mnt/boot/grub/grub.cfg
Find your drive that's supposed to boot with
mount
Or
parted -l
Or
fdisk /dev/sda
And type p to list the partitions, look for type 83.
(If you've got Fedora you might have to use the commands "vgs" and "lvs" and if you've got mdraid you might have to "cat /proc/mdstat" or mdadm -A --scan or insmod raid1 or insmod raid5 and then mdadm -A --scan) and you will use /dev/md0 or /dev/mapper/my-vg instead of /dev/sda
then try mount it
mkdir /mnt
mount /dev/sda1 /mnt
cd /mnt
ls -l
Is this your drive? Cool!
grub-install --recheck --root-directory=/mnt /dev/sda
(Or whichever /dev drive your root is, with it's mounted path)
grub-install --recheck --root-directory=/mnt /dev/sda --force
(Force it if it doesn't like your partitions.)
Now it should boot into grub, and you can use the grub commands to boot up, after rebooting and selecting the right boot drive from the BIOS Setup, or by pressing ESC or F12 depending on your BIOS and whether you are quick enough, then at the Grub prompt - you can use tab completion to find it if it's not (hd0,1) but (hd1,3) or something else instead, but beware, tab completion sometimes hangs for a few seconds if grub can't read the drive.
insmod linux
ls
root=(hd0,1)
linux /boot/vmlinuz root=/dev/sda1
initrd /boot/initrd
boot
Or, hopefully you've still got an intact grub.cfg file... or maybe this will work:
grub-mkconfig -o /mnt/boot/grub/grub.cfg
edited Jan 25 at 23:22
answered Apr 13 '16 at 22:15
DagelfDagelf
27146
27146
1
It didn't like my partitions, but-f
wasn't working. I had to use--force
– R.M
Jan 7 at 19:12
add a comment |
1
It didn't like my partitions, but-f
wasn't working. I had to use--force
– R.M
Jan 7 at 19:12
1
1
It didn't like my partitions, but
-f
wasn't working. I had to use --force
– R.M
Jan 7 at 19:12
It didn't like my partitions, but
-f
wasn't working. I had to use --force
– R.M
Jan 7 at 19:12
add a comment |
Revised solution based on code above
The solution from above will not work totally without problems because it mounts the boot partition into the / (root) of the file system. That makes grub complain that /boot does not exist, of course. This will fix that problem:
mkdir /mnt/chrootdir
mkdir /mnt/chrootdir/boot
mount /dev/sda1 /mnt/chrootdir/boot
for dir in proc dev sys etc bin sbin var usr lib lib64 tmp; do mkdir /mnt/chrootdir/$dir && mount --bind /$dir /mnt/chrootdir/$dir ; done
chroot /mnt/chrootdir
update-grub2 # inside chroot
As you see i also removed the line breaks so that it is easier to execute for everyone.
Another (simpler) solution
If you keep having problems getting it to work you should look to copy the /boot partition onto the / (root) partition. For that start your system with the Ubuntu live boot dvd and open the terminal. Inside it type:
sudo su
fdisk -l
To find out which partitions you have. In my case sda1 is my /boot partition which is about 250MB large and an sda5 which is about 500GB. I use these values in the commands below:
mkdir /mnt/boot/
mount /dev/sda1 /mnt/boot/
mkdir /mnt/root/
mount /dev/sda5 /mnt/root/
cp -R /mnt/boot/ /mnt/root/boot/
Set the bootable flag for the data partition and remove it for the boot partition:
fdisk /dev/sda
b -> 1 (unset the bootable flag for the first partition)
b -> 5 (set the bootable flag for the fifth partition)
w -> write changes to the MBR
Your computer will now look inside the sda5 for the boot files. Time to do the chrooting again, this time with some required folders needed for grub and which are generated by your Ubuntu live disc already:
mkdir /mnt/chrootdir/
mkdir /mnt/chrootdir/dev/
mkdir /mnt/chrootdir/proc/
mkdir /mnt/chrootdir/sys/
mount /dev/sda5 /mnt/chrootdir/
mount --bind /dev/ /mnt/chrootdir/dev/
mount --bind /proc/ /mnt/chrootdir/proc/
mount --bind /sys/ /mnt/chrootdir/sys/
chroot /mnt/chrootdir/
grub-install /dev/sda
Installation finished. No error reported.
If you do not see a message that the grub.cnf file is generated then also run the update command:
update-grub2 /dev/sda
Now you can safely reboot and see the well known boot menu appear again.
This solution was the only one which was working for me after migrating from a physical server to a virtual machine. I hope someone finds this useful!
add a comment |
Revised solution based on code above
The solution from above will not work totally without problems because it mounts the boot partition into the / (root) of the file system. That makes grub complain that /boot does not exist, of course. This will fix that problem:
mkdir /mnt/chrootdir
mkdir /mnt/chrootdir/boot
mount /dev/sda1 /mnt/chrootdir/boot
for dir in proc dev sys etc bin sbin var usr lib lib64 tmp; do mkdir /mnt/chrootdir/$dir && mount --bind /$dir /mnt/chrootdir/$dir ; done
chroot /mnt/chrootdir
update-grub2 # inside chroot
As you see i also removed the line breaks so that it is easier to execute for everyone.
Another (simpler) solution
If you keep having problems getting it to work you should look to copy the /boot partition onto the / (root) partition. For that start your system with the Ubuntu live boot dvd and open the terminal. Inside it type:
sudo su
fdisk -l
To find out which partitions you have. In my case sda1 is my /boot partition which is about 250MB large and an sda5 which is about 500GB. I use these values in the commands below:
mkdir /mnt/boot/
mount /dev/sda1 /mnt/boot/
mkdir /mnt/root/
mount /dev/sda5 /mnt/root/
cp -R /mnt/boot/ /mnt/root/boot/
Set the bootable flag for the data partition and remove it for the boot partition:
fdisk /dev/sda
b -> 1 (unset the bootable flag for the first partition)
b -> 5 (set the bootable flag for the fifth partition)
w -> write changes to the MBR
Your computer will now look inside the sda5 for the boot files. Time to do the chrooting again, this time with some required folders needed for grub and which are generated by your Ubuntu live disc already:
mkdir /mnt/chrootdir/
mkdir /mnt/chrootdir/dev/
mkdir /mnt/chrootdir/proc/
mkdir /mnt/chrootdir/sys/
mount /dev/sda5 /mnt/chrootdir/
mount --bind /dev/ /mnt/chrootdir/dev/
mount --bind /proc/ /mnt/chrootdir/proc/
mount --bind /sys/ /mnt/chrootdir/sys/
chroot /mnt/chrootdir/
grub-install /dev/sda
Installation finished. No error reported.
If you do not see a message that the grub.cnf file is generated then also run the update command:
update-grub2 /dev/sda
Now you can safely reboot and see the well known boot menu appear again.
This solution was the only one which was working for me after migrating from a physical server to a virtual machine. I hope someone finds this useful!
add a comment |
Revised solution based on code above
The solution from above will not work totally without problems because it mounts the boot partition into the / (root) of the file system. That makes grub complain that /boot does not exist, of course. This will fix that problem:
mkdir /mnt/chrootdir
mkdir /mnt/chrootdir/boot
mount /dev/sda1 /mnt/chrootdir/boot
for dir in proc dev sys etc bin sbin var usr lib lib64 tmp; do mkdir /mnt/chrootdir/$dir && mount --bind /$dir /mnt/chrootdir/$dir ; done
chroot /mnt/chrootdir
update-grub2 # inside chroot
As you see i also removed the line breaks so that it is easier to execute for everyone.
Another (simpler) solution
If you keep having problems getting it to work you should look to copy the /boot partition onto the / (root) partition. For that start your system with the Ubuntu live boot dvd and open the terminal. Inside it type:
sudo su
fdisk -l
To find out which partitions you have. In my case sda1 is my /boot partition which is about 250MB large and an sda5 which is about 500GB. I use these values in the commands below:
mkdir /mnt/boot/
mount /dev/sda1 /mnt/boot/
mkdir /mnt/root/
mount /dev/sda5 /mnt/root/
cp -R /mnt/boot/ /mnt/root/boot/
Set the bootable flag for the data partition and remove it for the boot partition:
fdisk /dev/sda
b -> 1 (unset the bootable flag for the first partition)
b -> 5 (set the bootable flag for the fifth partition)
w -> write changes to the MBR
Your computer will now look inside the sda5 for the boot files. Time to do the chrooting again, this time with some required folders needed for grub and which are generated by your Ubuntu live disc already:
mkdir /mnt/chrootdir/
mkdir /mnt/chrootdir/dev/
mkdir /mnt/chrootdir/proc/
mkdir /mnt/chrootdir/sys/
mount /dev/sda5 /mnt/chrootdir/
mount --bind /dev/ /mnt/chrootdir/dev/
mount --bind /proc/ /mnt/chrootdir/proc/
mount --bind /sys/ /mnt/chrootdir/sys/
chroot /mnt/chrootdir/
grub-install /dev/sda
Installation finished. No error reported.
If you do not see a message that the grub.cnf file is generated then also run the update command:
update-grub2 /dev/sda
Now you can safely reboot and see the well known boot menu appear again.
This solution was the only one which was working for me after migrating from a physical server to a virtual machine. I hope someone finds this useful!
Revised solution based on code above
The solution from above will not work totally without problems because it mounts the boot partition into the / (root) of the file system. That makes grub complain that /boot does not exist, of course. This will fix that problem:
mkdir /mnt/chrootdir
mkdir /mnt/chrootdir/boot
mount /dev/sda1 /mnt/chrootdir/boot
for dir in proc dev sys etc bin sbin var usr lib lib64 tmp; do mkdir /mnt/chrootdir/$dir && mount --bind /$dir /mnt/chrootdir/$dir ; done
chroot /mnt/chrootdir
update-grub2 # inside chroot
As you see i also removed the line breaks so that it is easier to execute for everyone.
Another (simpler) solution
If you keep having problems getting it to work you should look to copy the /boot partition onto the / (root) partition. For that start your system with the Ubuntu live boot dvd and open the terminal. Inside it type:
sudo su
fdisk -l
To find out which partitions you have. In my case sda1 is my /boot partition which is about 250MB large and an sda5 which is about 500GB. I use these values in the commands below:
mkdir /mnt/boot/
mount /dev/sda1 /mnt/boot/
mkdir /mnt/root/
mount /dev/sda5 /mnt/root/
cp -R /mnt/boot/ /mnt/root/boot/
Set the bootable flag for the data partition and remove it for the boot partition:
fdisk /dev/sda
b -> 1 (unset the bootable flag for the first partition)
b -> 5 (set the bootable flag for the fifth partition)
w -> write changes to the MBR
Your computer will now look inside the sda5 for the boot files. Time to do the chrooting again, this time with some required folders needed for grub and which are generated by your Ubuntu live disc already:
mkdir /mnt/chrootdir/
mkdir /mnt/chrootdir/dev/
mkdir /mnt/chrootdir/proc/
mkdir /mnt/chrootdir/sys/
mount /dev/sda5 /mnt/chrootdir/
mount --bind /dev/ /mnt/chrootdir/dev/
mount --bind /proc/ /mnt/chrootdir/proc/
mount --bind /sys/ /mnt/chrootdir/sys/
chroot /mnt/chrootdir/
grub-install /dev/sda
Installation finished. No error reported.
If you do not see a message that the grub.cnf file is generated then also run the update command:
update-grub2 /dev/sda
Now you can safely reboot and see the well known boot menu appear again.
This solution was the only one which was working for me after migrating from a physical server to a virtual machine. I hope someone finds this useful!
edited May 15 '16 at 21:00
answered May 15 '16 at 18:44
Tim B.Tim B.
4913
4913
add a comment |
add a comment |
I know, it's a old problem, but I had the same troubles today with the actual version of mint-linux (ubuntu-based). I found a very simply solution! :-) Take off the internet-connection during the first installation. This stop loading of a non compatible grub2. Make the update of all after installation has finished.
add a comment |
I know, it's a old problem, but I had the same troubles today with the actual version of mint-linux (ubuntu-based). I found a very simply solution! :-) Take off the internet-connection during the first installation. This stop loading of a non compatible grub2. Make the update of all after installation has finished.
add a comment |
I know, it's a old problem, but I had the same troubles today with the actual version of mint-linux (ubuntu-based). I found a very simply solution! :-) Take off the internet-connection during the first installation. This stop loading of a non compatible grub2. Make the update of all after installation has finished.
I know, it's a old problem, but I had the same troubles today with the actual version of mint-linux (ubuntu-based). I found a very simply solution! :-) Take off the internet-connection during the first installation. This stop loading of a non compatible grub2. Make the update of all after installation has finished.
edited Mar 15 '17 at 18:51
anonymous2
3,31841847
3,31841847
answered Mar 15 '17 at 18:39
ChruegelChruegel
1
1
add a comment |
add a comment |
It is the update-grub command which will give you the error when using it from a live cd. I faced with a similar situation when i was doing a grub rescue. The problem you have is that update-grub and grub-install commands do not work directly under live cd (I don't know why). So, you have to go to /usr/sbin where the commands are located and execute them from there (i.e ./update-grub).
No, you have to mount the hard disk and chroot into it, like @green7 said.
– psusi
Apr 2 '14 at 18:27
my method also works. try it. its simpler
– aveemashfaq
Apr 4 '14 at 12:32
1
You don't have a method. /usr/sbin is on the path already so there is no need to cd there. You can't run grub-install and update-grub directly from the live cd ( as you noted ) because it tries to set up grub to boot the current system, which would be the live cd, rather than the os installed on the hard drive.
– psusi
Apr 4 '14 at 14:00
This, of course, doesn't work. You get the "can't get cannonical path of /cow" error. And the stuff about cd-ing to /usr/sbin... oh boy.
– dan3
Apr 13 '14 at 12:37
try it people. it worked for me all the time
– aveemashfaq
Apr 13 '14 at 13:09
|
show 1 more comment
It is the update-grub command which will give you the error when using it from a live cd. I faced with a similar situation when i was doing a grub rescue. The problem you have is that update-grub and grub-install commands do not work directly under live cd (I don't know why). So, you have to go to /usr/sbin where the commands are located and execute them from there (i.e ./update-grub).
No, you have to mount the hard disk and chroot into it, like @green7 said.
– psusi
Apr 2 '14 at 18:27
my method also works. try it. its simpler
– aveemashfaq
Apr 4 '14 at 12:32
1
You don't have a method. /usr/sbin is on the path already so there is no need to cd there. You can't run grub-install and update-grub directly from the live cd ( as you noted ) because it tries to set up grub to boot the current system, which would be the live cd, rather than the os installed on the hard drive.
– psusi
Apr 4 '14 at 14:00
This, of course, doesn't work. You get the "can't get cannonical path of /cow" error. And the stuff about cd-ing to /usr/sbin... oh boy.
– dan3
Apr 13 '14 at 12:37
try it people. it worked for me all the time
– aveemashfaq
Apr 13 '14 at 13:09
|
show 1 more comment
It is the update-grub command which will give you the error when using it from a live cd. I faced with a similar situation when i was doing a grub rescue. The problem you have is that update-grub and grub-install commands do not work directly under live cd (I don't know why). So, you have to go to /usr/sbin where the commands are located and execute them from there (i.e ./update-grub).
It is the update-grub command which will give you the error when using it from a live cd. I faced with a similar situation when i was doing a grub rescue. The problem you have is that update-grub and grub-install commands do not work directly under live cd (I don't know why). So, you have to go to /usr/sbin where the commands are located and execute them from there (i.e ./update-grub).
answered Apr 2 '14 at 18:06
aveemashfaqaveemashfaq
1495
1495
No, you have to mount the hard disk and chroot into it, like @green7 said.
– psusi
Apr 2 '14 at 18:27
my method also works. try it. its simpler
– aveemashfaq
Apr 4 '14 at 12:32
1
You don't have a method. /usr/sbin is on the path already so there is no need to cd there. You can't run grub-install and update-grub directly from the live cd ( as you noted ) because it tries to set up grub to boot the current system, which would be the live cd, rather than the os installed on the hard drive.
– psusi
Apr 4 '14 at 14:00
This, of course, doesn't work. You get the "can't get cannonical path of /cow" error. And the stuff about cd-ing to /usr/sbin... oh boy.
– dan3
Apr 13 '14 at 12:37
try it people. it worked for me all the time
– aveemashfaq
Apr 13 '14 at 13:09
|
show 1 more comment
No, you have to mount the hard disk and chroot into it, like @green7 said.
– psusi
Apr 2 '14 at 18:27
my method also works. try it. its simpler
– aveemashfaq
Apr 4 '14 at 12:32
1
You don't have a method. /usr/sbin is on the path already so there is no need to cd there. You can't run grub-install and update-grub directly from the live cd ( as you noted ) because it tries to set up grub to boot the current system, which would be the live cd, rather than the os installed on the hard drive.
– psusi
Apr 4 '14 at 14:00
This, of course, doesn't work. You get the "can't get cannonical path of /cow" error. And the stuff about cd-ing to /usr/sbin... oh boy.
– dan3
Apr 13 '14 at 12:37
try it people. it worked for me all the time
– aveemashfaq
Apr 13 '14 at 13:09
No, you have to mount the hard disk and chroot into it, like @green7 said.
– psusi
Apr 2 '14 at 18:27
No, you have to mount the hard disk and chroot into it, like @green7 said.
– psusi
Apr 2 '14 at 18:27
my method also works. try it. its simpler
– aveemashfaq
Apr 4 '14 at 12:32
my method also works. try it. its simpler
– aveemashfaq
Apr 4 '14 at 12:32
1
1
You don't have a method. /usr/sbin is on the path already so there is no need to cd there. You can't run grub-install and update-grub directly from the live cd ( as you noted ) because it tries to set up grub to boot the current system, which would be the live cd, rather than the os installed on the hard drive.
– psusi
Apr 4 '14 at 14:00
You don't have a method. /usr/sbin is on the path already so there is no need to cd there. You can't run grub-install and update-grub directly from the live cd ( as you noted ) because it tries to set up grub to boot the current system, which would be the live cd, rather than the os installed on the hard drive.
– psusi
Apr 4 '14 at 14:00
This, of course, doesn't work. You get the "can't get cannonical path of /cow" error. And the stuff about cd-ing to /usr/sbin... oh boy.
– dan3
Apr 13 '14 at 12:37
This, of course, doesn't work. You get the "can't get cannonical path of /cow" error. And the stuff about cd-ing to /usr/sbin... oh boy.
– dan3
Apr 13 '14 at 12:37
try it people. it worked for me all the time
– aveemashfaq
Apr 13 '14 at 13:09
try it people. it worked for me all the time
– aveemashfaq
Apr 13 '14 at 13:09
|
show 1 more comment
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f254491%2ffailed-to-get-canonical-path-of-cow%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Does your computer have the Recommended Minimum System Requirements to run Ubuntu? I have had problems installing 12.04 to machines with less than 1GB RAM.
– C.S.Cameron
Feb 14 '13 at 5:49
Yes ,Now I have added my system specification to question.
– ulkaNCST
Feb 14 '13 at 7:56
askubuntu.com/questions/207663/… might be worth a try.
– Rinzwind
Feb 14 '13 at 7:59
5
First mount your hard drive to some folder, say
/mnt
and thenchroot
to/mnt
.– green
Feb 18 '13 at 3:44
3
possible duplicate of How can I repair grub? (How to get Ubuntu back after installing Windows?)
– psusi
Apr 2 '14 at 18:30