Announcement

Collapse
No announcement yet.

Dual boot with windows 8 - Not able to start kubuntu

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 4
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 4 template Next
    #31
    Originally posted by Monica View Post
    The rest are comments, aren't they?
    Yeah, true. Anyway, the problem isn't here.


    Continuing...here's the portion of your /boot/grub/grub.cfg that's supposed to allow you to boot Windows 8:
    Code:
    ### BEGIN /etc/grub.d/30_os-prober ###
menuentry 'Windows 8 (loader) (a /dev/sda4)' --class windows --class os $menuentry_id_option 'osprober-chain-1E64807664805287' {
	insmod part_gpt
	insmod ntfs
	set root='hd0,gpt4'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt4 --hint-efi=hd0,gpt4 --hint-baremetal=ahci0,gpt4  1E64807664805287
	else
	  search --no-floppy --fs-uuid --set=root 1E64807664805287
	fi
	drivemap -s (hd0) ${root}
	chainloader +1
}
menuentry 'Windows Recovery Environment (loader) (a /dev/sda5)' --class windows --class os $menuentry_id_option 'osprober-chain-84F8D25EF8D24DD4' {
	insmod part_gpt
	insmod ntfs
	set root='hd0,gpt5'
	if [ x$feature_platform_search_hint = xy ]; then
	  search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt5 --hint-efi=hd0,gpt5 --hint-baremetal=ahci0,gpt5  84F8D25EF8D24DD4
	else
	  search --no-floppy --fs-uuid --set=root 84F8D25EF8D24DD4
	fi
	drivemap -s (hd0) ${root}
	chainloader +1
}
### END /etc/grub.d/30_os-prober ###
    But it isn't working. I have an idea for a workaround.


    And here's the mysterious "system setup"!
    Code:
    ### BEGIN /etc/grub.d/30_uefi-firmware ###
menuentry 'System setup' $menuentry_id_option 'uefi-firmware' {
	fwsetup
}
### END /etc/grub.d/30_uefi-firmware ###
    I've figured this out. Every UEFI-equipped machine includes a very basic boot manager, which displays installed operating systems that the UEFI knows about. GRUB is now providing a menu option to start the UEFI boot manager. Huh. Since I don't use GRUB, I hadn't realized it had gained this capability.


    But we still need to fix your GRUB so that it boots Windows. Boot back into Kubuntu and open a console window. Then type:
    Code:
    sudo nano /etc/grub.d/40_custom
    At the bottom of this file add:
    Code:
    menuentry "Windows 8 (alternate boot method)" {
  search --set=root --file /EFI/Microsoft/Boot/bootmgfw.efi
  chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
    Press Ctrl+X to save and exit.

    Now type:
    Code:
    sudo update-grub
    Reboot. In the GRUB menu, select Windows 8 (alternate boot method). Let me know if that works.
    • Top
    • Bottom

    Comment

      #32
      Eh, check this out! https://bugs.launchpad.net/ubuntu/+s...2/+bug/1024383

      Sheesh. Confirmed, critical, yet unassigned. WTFF?

      The bug report contains some interesting ways to fix the problem. Before we examine those, though, please try what I just suggested in the previous post.
      • Top
      • Bottom

      Comment

        #33
        I wasn't at home until now, couldn't try it earlier

        Originally posted by SteveRiley View Post
        Eh, check this out! https://bugs.launchpad.net/ubuntu/+s...2/+bug/1024383
        Yessss, that's exactly that!

        I tried what you said and it worked!!!!!!!!! So now what?

        I'll try to read the forum thread in french and the bug report now too....
        • Top
        • Bottom

        Comment

          #34
          I was still puzzled why windows didn't find the partitions so I tried again and this time i found this:
          http://imgur.com/BG3n0sJ

          that's too much for me.
          i know it's silly but I'm kind of happy that it was a bug (yes, I know it makes no sense that it is
          critical confirmed and unassigned)... it sort of means that I am not completelly hopeless.
          • Top
          • Bottom

          Comment

            #35
            Originally posted by Monica View Post
            I was still puzzled why windows didn't find the partitions so I tried again and this time i found this:
            {...link snipped...}
            Windows now sees all your partitions, finally. I don't understand why it didn't earlier, but hey, let's not worry about that now


            Originally posted by Monica View Post
            I tried what you said and it worked!!!!!!!!! So now what?
            The last thing to do is format that large partition as NTFS and then set up Kubunto to see it. I'd prefer that you do the formatting in Windows. So please boot that, open Disk Management, right-click the 583,94 GB RAW partition, and format it as NTFS. Use "quick format," it's faster and the end result is the same.

            Once that's done, please boot back into Kubuntu. Show me what's in /etc/fstab. I want to see what it looks like now, before we start adding stuff.

            Also, just for good measure, show the output of
            Code:
            sudo gdisk -l /dev/sda
            • Top
            • Bottom

            Comment

              #36
              I didn't find the folder /etc/fstab, only /etc/fstab.d and it's empty.

              I can access the data partition dades both with kubuntu and windows.

              Code:
              monica@antalya:~$ cd /etc
monica@antalya:/etc$ cd fstab
bash: cd: fstab: No és un directori
monica@antalya:/etc$ cd fstab.d
monica@antalya:/etc/fstab.d$ ls

monica@antalya:/etc/fstab.d$ sudo gdisk -l /dev/sda
[sudo] password for monica: 
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): ECF8BE59-B005-429C-A5A5-0450C2979099
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 4292 sectors (2.1 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048         2097151   1023.0 MiB  2700  Basic data partition
   2         2097152         2834431   360.0 MiB   EF00  EFI system partition
   3         2834432         3096575   128.0 MiB   0C01  Microsoft reserved part
   4         3096576       393944232   186.4 GiB   0700  Basic data partition
   5      1929101312      1953523711   11.6 GiB    0700  Basic data partition
   6       393945088       491599871   46.6 GiB    0700  
   7       491599872       686911487   93.1 GiB    0700  
   8       686911488       704489471   8.4 GiB     8200  
   9       704489472      1929101311   583.9 GiB   0700
              Last edited by SteveRiley; Apr 19, 2013, 12:06 PM.
              • Top
              • Bottom

              Comment

                #37
                Originally posted by Monica View Post
                I didn't find the folder /etc/fstab, only /etc/fstab.d and it's empty.
                That's because /etc/fstab is a file. Yeah, I should have been clearer. When I say "let me see what's in foo, if foo is a subdirectory, you'd display the contents with ls -al foo. If foo is a file, you'd display the contents with cat foo.

                Originally posted by Monica View Post
                sudo gdisk -l /dev/sda
                Your partition table looks exactly like it should.

                Originally posted by Monica View Post
                I can access the data partition dades both with kubuntu and windows.
                Hey, I think everything's sorted now! For my own curiousity, I'd still like to see your fstab. So please show the output of
                Code:
                cat /etc/fstab
                • Top
                • Bottom

                Comment

                  #38
                  Oops, no, i should had found it, I was too excited to think, It finally works!!!!! That's really great, I don't know how to thank you...
                  I hate working with windows so much and I had never solved that alone. That's just another reason to love kubuntu, that there's people like you around..

                  Code:
                  # /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda6 during installation
UUID=efa67d15-0bce-445e-b761-ea5b0b34024a /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/sda2 during installation
UUID=2C0A-9AE8  /boot/efi       vfat    defaults        0       1
# /home was on /dev/sda7 during installation
UUID=d21c332d-fe21-496b-9898-8234043a966e /home           ext4    defaults        0       2
# swap was on /dev/sda8 during installation
UUID=95b9f906-af8c-4345-b617-56fbbea52678 none            swap    sw              0       0
                  • Top
                  • Bottom

                  Comment

                    #39
                    Hm, interesting. Your NTFS partition isn't getting mounted via fstab. Something else must be auto-mounting it for you. I don't run dual-boot, so I'm kind of figuring this stuff out as we go along.

                    What's the output of:
                    Code:
                    cat /proc/mounts
                    I'm glad we got everything sorted for you. Even though we're up to 39 posts on this thread, yours has been one of the cleaner UEFI dual-boot scenarios to get going correctly.
                    • Top
                    • Bottom

                    Comment

                      #40
                      Code:
                      monica@antalya:~$ cat /proc/mounts
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=4053536k,nr_inodes=1013384,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,relatime,size=1626492k,mode=755 0 0
/dev/disk/by-uuid/efa67d15-0bce-445e-b761-ea5b0b34024a / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
none /sys/fs/fuse/connections fusectl rw,relatime 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/kernel/security securityfs rw,relatime 0 0
none /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
none /run/shm tmpfs rw,nosuid,nodev,relatime 0 0
none /run/user tmpfs rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755 0 0
/dev/sda7 /home ext4 rw,relatime,data=ordered 0 0
/dev/sda2 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
                      i don't understand any of it...
                      • Top
                      • Bottom

                      Comment

                        #41
                        Well, I understand what's in that output, but I don't understand why we can't seem to discover is exactly how Kubunutu is finding and mounting your NTFS partition! You said you can see it, that's cool. I presume you're using Dolphin to access it?

                        One more bit of investigation, if I may...what's the output of these two commands:
                        Code:
                        ls -al /mnt

ls -al /media
                        • Top
                        • Bottom

                        Comment

                          #42
                          Yes, I'm using Dolphin. You can ask me to run so many commands as you want ;-), I'm not just disappearing because it's solved for me!

                          Code:
                          monica@antalya:~$ ls -al /mnt
total 8
drwxr-xr-x  2 root root 4096 oct  9  2012 .
drwxr-xr-x 25 root root 4096 abr 15 22:02 ..
monica@antalya:~$ ls -al /media
total 12
drwxr-xr-x  3 root   root   4096 abr 19 20:42 .
drwxr-xr-x 25 root   root   4096 abr 15 22:02 ..
drwx------  1 monica monica 4096 abr 19 19:45 dades
lrwxrwxrwx  1 root   root     45 abr 15 21:41 .directory -> /etc/kubuntu-default-settings/directory-media
lrwxrwxrwx  1 root   root     42 abr 15 21:41 .hidden -> /etc/kubuntu-default-settings/hidden-media
                          • Top
                          • Bottom

                          Comment

                            #43
                            Yeah, I suspect Dolphin is automatically mounting it for you, using a technology called FUSE, "File System in User Space." You can see this here:
                            Code:
                            monica@antalya:~$ [B]ls -al /media[/B]
total 12
drwxr-xr-x  3 root   root   4096 abr 19 20:42 .
drwxr-xr-x 25 root   root   4096 abr 15 22:02 ..
[B]drwx------  1 monica monica 4096 abr 19 19:45 dades[/B]
lrwxrwxrwx  1 root   root     45 abr 15 21:41 .directory -> /etc/kubuntu-default-settings/directory-media
lrwxrwxrwx  1 root   root     42 abr 15 21:41 .hidden -> /etc/kubuntu-default-settings/hidden-media
                            Dolphin is automatically mounting it under /media for you.


                            Try this. Open Dolphin, then open a console window. Now show me the outputs of
                            Code:
                            cat /proc/mounts

udisks --enumerate

udisks --enumerate-device-files
                            Sorry to be using you as my lab rat
                            • Top
                            • Bottom

                            Comment

                              #44
                              Code:
                              monica@antalya:~$ cat /proc/mounts
rootfs / rootfs rw 0 0
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,relatime,size=4053536k,nr_inodes=1013384,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,relatime,size=1626492k,mode=755 0 0
/dev/disk/by-uuid/efa67d15-0bce-445e-b761-ea5b0b34024a / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
none /sys/fs/fuse/connections fusectl rw,relatime 0 0
none /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/kernel/security securityfs rw,relatime 0 0
none /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
none /run/shm tmpfs rw,nosuid,nodev,relatime 0 0
none /run/user tmpfs rw,nosuid,nodev,noexec,relatime,size=102400k,mode=755 0 0
/dev/sda7 /home ext4 rw,relatime,data=ordered 0 0
/dev/sda2 /boot/efi vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/sda9 /media/dades fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0

monica@antalya:~$ udisks --enumerate
/org/freedesktop/UDisks/devices/sda1
/org/freedesktop/UDisks/devices/sda2
/org/freedesktop/UDisks/devices/sda3
/org/freedesktop/UDisks/devices/sda4
/org/freedesktop/UDisks/devices/sda
/org/freedesktop/UDisks/devices/sda5
/org/freedesktop/UDisks/devices/sda6
/org/freedesktop/UDisks/devices/sda7
/org/freedesktop/UDisks/devices/sda8
/org/freedesktop/UDisks/devices/sda9
/org/freedesktop/UDisks/devices/sr0
/org/freedesktop/UDisks/devices/sdb

monica@antalya:~$ udisks --enumerate-device-files
/dev/sda1
/dev/disk/by-id/ata-ST1000DM003-1CH162_Z1D3V0G6-part1
/dev/disk/by-id/scsi-SATA_ST1000DM003-1CHZ1D3V0G6-part1
/dev/disk/by-id/wwn-0x5000c50050245c39-part1
/dev/disk/by-uuid/BC76CCCE76CC8B1A
/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part1
/dev/sda2
/dev/disk/by-id/ata-ST1000DM003-1CH162_Z1D3V0G6-part2
/dev/disk/by-id/scsi-SATA_ST1000DM003-1CHZ1D3V0G6-part2
/dev/disk/by-id/wwn-0x5000c50050245c39-part2 
/dev/disk/by-uuid/2C0A-9AE8 
/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part2 
/dev/sda3 
/dev/disk/by-id/ata-ST1000DM003-1CH162_Z1D3V0G6-part3
/dev/disk/by-id/scsi-SATA_ST1000DM003-1CHZ1D3V0G6-part3
/dev/disk/by-id/wwn-0x5000c50050245c39-part3
/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part3
/dev/sda4
/dev/disk/by-id/ata-ST1000DM003-1CH162_Z1D3V0G6-part4
/dev/disk/by-id/scsi-SATA_ST1000DM003-1CHZ1D3V0G6-part4
/dev/disk/by-id/wwn-0x5000c50050245c39-part4
/dev/disk/by-uuid/1E64807664805287
/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part4
/dev/sda
/dev/disk/by-id/ata-ST1000DM003-1CH162_Z1D3V0G6
/dev/disk/by-id/scsi-SATA_ST1000DM003-1CHZ1D3V0G6
/dev/disk/by-id/wwn-0x5000c50050245c39
/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0
/dev/sda5
/dev/disk/by-id/ata-ST1000DM003-1CH162_Z1D3V0G6-part5
/dev/disk/by-id/scsi-SATA_ST1000DM003-1CHZ1D3V0G6-part5
/dev/disk/by-id/wwn-0x5000c50050245c39-part5
/dev/disk/by-uuid/84F8D25EF8D24DD4
/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part5
/dev/sda6
/dev/disk/by-id/ata-ST1000DM003-1CH162_Z1D3V0G6-part6
/dev/disk/by-id/scsi-SATA_ST1000DM003-1CHZ1D3V0G6-part6
/dev/disk/by-id/wwn-0x5000c50050245c39-part6
/dev/disk/by-uuid/efa67d15-0bce-445e-b761-ea5b0b34024a
/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part6
/dev/sda7
/dev/disk/by-id/ata-ST1000DM003-1CH162_Z1D3V0G6-part7
/dev/disk/by-id/scsi-SATA_ST1000DM003-1CHZ1D3V0G6-part7
/dev/disk/by-id/wwn-0x5000c50050245c39-part7
/dev/disk/by-uuid/d21c332d-fe21-496b-9898-8234043a966e
/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part7
/dev/sda8
/dev/disk/by-id/ata-ST1000DM003-1CH162_Z1D3V0G6-part8
/dev/disk/by-id/scsi-SATA_ST1000DM003-1CHZ1D3V0G6-part8
/dev/disk/by-id/wwn-0x5000c50050245c39-part8
/dev/disk/by-uuid/95b9f906-af8c-4345-b617-56fbbea52678
/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part8
/dev/sda9
/dev/disk/by-id/ata-ST1000DM003-1CH162_Z1D3V0G6-part9
/dev/disk/by-id/scsi-SATA_ST1000DM003-1CHZ1D3V0G6-part9
/dev/disk/by-id/wwn-0x5000c50050245c39-part9
/dev/disk/by-uuid/108EA2C58EA2A328
/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0-part9
/dev/sr0
/dev/disk/by-id/ata-hp_DVD_A_DH16ACSHR_3L8301911780
/dev/disk/by-path/pci-0000:00:1f.2-scsi-0:0:0:0
/dev/sdb
/dev/disk/by-id/usb-Multiple_Card_Reader_058F63666433-0:0
/dev/disk/by-path/pci-0000:00:1d.0-usb-0:1.6:1.0-scsi-0:0:0:0
                              it's kind of fun. you're lucky you're so km away while otherwise I would be asking tons of questions ;-), I'm curious.
                              Last edited by SteveRiley; Apr 19, 2013, 01:28 PM.
                              • Top
                              • Bottom

                              Comment

                                #45
                                Yep, it's a FUSE mount created by Dolphin. Notice that we can now see it in /proc/mounts:
                                Code:
                                /dev/sda9 /media/dades fuseblk rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096 0 0
                                The fuseblk type indicator is the clue.

                                I have personally never needed to check into this, since I'm not a fan of dual-booting. So hey -- we both learned some stuff here! Kewl :cool:
                                • Top
                                • Bottom

                                Comment

                                Previous 1 2 3 4 template Next
                                Working...
                                X