Poll: How easy is Linux to install with 2 existing windows installations?
Very easy
Easy
Medium
Hard
Very hard
[Show Results]
 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Install Linux alongside 2 windows installations
#11

Hello Hybrid!

 

I was just in the middle of trying to sudo kate the grub file when I started googling, and thinking maybe this isn't a good idea lol. I will check out the link you posted, and give it a try. Back in a flash.

 

Thanks!

 

EDIT: What am I doing wrong?

 



Code:
sudo mount /dev/sda4
mount: /dev/sda4 already mounted or /media/Linux Root busy
mount: according to mtab, /dev/sda4 is already mounted on /media/Linux Root
ubuntu@ubuntu:~$ sudo mount --bind /dev  /mnt/dev
mount: mount point /mnt/dev does not exist




Reply
#12

Hello again!

 

Okay, i'm still here in the LiveCD. I am getting stuck with Method 3 - Step 6:

 



Code:
ubuntu@ubuntu:~$ sudo mount --bind /dev  /mnt/dev
mount: mount point /mnt/dev does not exist                                        
ubuntu@ubuntu:~$ sudo mount --bind /proc /mnt/proc
mount: mount point /mnt/proc does not exist
ubuntu@ubuntu:~$ sudo mount --bind /sys  /mnt/sys                                          
mount: mount point /mnt/sys does not exist                                                
ubuntu@ubuntu:~$




 

I'm assuming this isn't something I can ignore and continue to step 7?

 

Thanks!

 

EDIT: Okay, I think I sorted that. I had to mkdir them all. I am having trouble with step 7 now:

 



Code:
Chroot into your normal system device:
sudo chroot /mnt




 

When I attempt to do that I get:

 



Code:
ubuntu@ubuntu:~$ sudo chroot /mnt
chroot: cannot run command `/bin/bash': No such file or directory




 

Help? lol

Reply
#13

Try doing this before the instructions:

 



Code:
sudo umount "/media/Linux Root"




 

Once you've done that, the first mount command will work properly and the rest should also work properly.

Reply
#14

Hello Hybrid!

 

No luck my friend..

 



Code:
ubuntu@ubuntu:~$ sudo umount "/media/Linux Root"
ubuntu@ubuntu:~$ sudo chroot /mnt
chroot: cannot run command `/bin/bash': No such file or directory




 

EDIT: I done the umount command, and still no luck. I also tried going to "Dolphin" and rightclick - Unmount. The "Linux Root" keeps re-mounting itself.

 

Does this look correct:

 

[Image: snapshot1h.jpg]

Reply
#15

Quote:Hello Hybrid!

 

No luck my friend..

 



Code:
ubuntu@ubuntu:~$ sudo umount "/media/Linux Root"
ubuntu@ubuntu:~$ sudo chroot /mnt
chroot: cannot run command `/bin/bash': No such file or directory

<div>




</div>
 

OK, you probably need to reboot the live CD now.

 

Once you have done so, run:

 



Code:
sudo umount "/media/Linux Root"




 

and then follow the Ubuntu wiki instructions from the beginning. Sorry about any confusion.

Reply
#16

Hello Hybrid!

 

I have restarted the machine, and am back. I still have the same problem:

 



Code:
ubuntu@ubuntu:~$ sudo umount "/media/Linux Root"
umount: /media/Linux Root: not found
ubuntu@ubuntu:~$ sudo mount /dev/sda3 /mnt
ubuntu@ubuntu:~$ sudo mount --bind /dev  /mnt/dev
ubuntu@ubuntu:~$ sudo mount --bind /proc /mnt/proc
ubuntu@ubuntu:~$ sudo mount --bind /sys  /mnt/sys
ubuntu@ubuntu:~$ sudo chroot /mnt
chroot: cannot run command `/bin/bash': No such file or directory
ubuntu@ubuntu:~$




 

Any ideas?

Reply
#17

There are some signs that your installation of Kubuntu might not have worked properly.

 

It might be quicker and easier to just re-run the Kubuntu install again, just by following my guide above again, choosing to format the same partitions. At very least that should eliminate the possibility that it is just this install that went wrong!

Reply
#18

Hello Hybrid!

 

I have now formatted all Linux related partitions (Root/Home). I also renamed the Labels to Linux_Root (previously Linux Root) and Linux_Home (previously Linux Home).

 

I installed Kubuntu from fresh (as per your instructions), giving that would I be right in assuming we are at Stage 1 again now?

 

I tried to boot, and had the same error about the kernel. Where do I go from here?

 

Thanks!

 

PS: I am currently using the "Try Kubuntu without installing" option.

Reply
#19

OK, we'll have to go down another route still.

 

It is possible it is the zero UUIDs (00000-00000... etc. that you noticed) that are the problem. If you open up the grub.cfg file, do you still see those zero'ed entries?

 

Also, what result do you get from running:

 



Code:
blkid




 

in the Live CD terminal? This command should show you what the partition UUIDs should be.

 

And just to reiterate -- I am stumped as to why the bootloader is failing. It makes no sense to me why the installer didn't set it up properly. The installation process shouldn't normally be this difficult, you understand! :)

Reply
#20

Quote:It is possible it is the zero UUIDs (00000-00000... etc. that you noticed) that are the problem. If you open up the grub.cfg file, do you still see those zero'ed entries?
 

Affirmative, I still see all the 0000's apart from under the Windows 7 Boot Loader menu entry.

 

 

KUBUNTU 10 BOOT LOADER ENTRY



Code:
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Ubuntu, with Linux 2.6.32-21-generic' --class ubuntu --class gnu-linux --class gnu --class os {
recordfail
insmod ext2
set root='(hd0,4)'
search --no-floppy --fs-uuid --set 00000000-0000-0000-0000-000000000000
linux    /boot/vmlinuz-2.6.32-21-generic root=/dev/sda4 ro   quiet splash
initrd    /boot/initrd.img-2.6.32-21-generic




 

WINDOWS 7 BOOT LOADER ENTRY



Code:
### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Windows 7 (loader) (on /dev/sda1)" {
insmod fat
set root='(hd0,1)'
search --no-floppy --fs-uuid --set 9c81-cc68
chainloader +1




 

 

Quote:Also, what result do you get from running:

Code:
blkid

<div>




</div>
 

I ran the blkid using the "Sudo" command and I got the following results:

 



Code:
ubuntu@ubuntu:~$ sudo blkid
/dev/loop0: TYPE="squashfs"
/dev/sda1: LABEL="WINDOWS XP" UUID="9C81-CC68" TYPE="vfat"
/dev/sda3: LABEL="Windows 7" UUID="0608D9FB08D9E9A7" TYPE="ntfs"
/dev/sda4: LABEL="Linux_Root" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda5: LABEL="Linux_Home" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdb1: LABEL="Files" UUID="2C84E01284DFDC80" TYPE="ntfs"
/dev/sdb2: TYPE="swap"




 

Some more information:

 

Also if it helps, my GRUB is v1.98. I read somewhere online that GRUB2 doesn't allow you to edit the grub.cfg file, (even if you try editing it using root). Now I am unsure as whether the 1.98 is behaving/being treated as GRUB2 as I can't edit the grub.cfg.

 

I found a fix for someone elses problem over at launchpad. It seems quite similar but doesn't seem to help if I change the numbers to match my distro.

 

Quote:Try:sudo apt-get clean; sudo apt-get --reinstall install linux-image-2.6.31-20-generic

Should be ok.

 

 

<div class="ipsSpoiler" data-ipsspoiler="">
<div class="ipsSpoiler_header">
https://answers.launchpad.net/ubuntu/+question/104757

</div>
 

 

Thanks in advance for your help!

 

EDIT: I did read somewhere that Windows 7 creates a hidden partition, however that being said I don't think it would get in the way of the installations as all the partitions are labelled correctly as you can see from the blkid.

 

EDIT again: I did notice this...

 



Code:
/dev/sda4: LABEL="Linux_Root" SEC_TYPE="ext2" TYPE="ext3"
/dev/sda5: LABEL="Linux_Home" SEC_TYPE="ext2" TYPE="ext3"




 

Do you think I should reformat the Linux partitions with ext2?

</div>[/quote]
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)