LinuxQuestions.org - Ubuntu, Kubuntu, debian based systems can't detect Windows Vista

- Ubuntu (https://www.linuxquestions.org/questions/ubuntu-63/)

- - Ubuntu, Kubuntu, debian based systems can't detect Windows Vista (https://www.linuxquestions.org/questions/ubuntu-63/ubuntu-kubuntu-debian-based-systems-cant-detect-windows-vista-4175465328/)

Ubuntu, Kubuntu, debian based systems can't detect Windows Vista

Hi!

I would like to ask for your help. I have problem with Ubuntu, Kubuntu related to not detecting Windows Vista in grub. I run update-grub or update-grub2 and see that on generated cfg there is Windows Vista, also when i use sudo os-prober the same list is being generated with Windows Vista but as soon as i reboot, see purple grub with available systems to boot, there is no Windows Vista.

I think that it is related to call 30_os-prober in /etc/default/grub or /etc/grub.d/ (im on Windows right now, can't check it). The only way of starting Windows is not from grub but by hitting F8 and selecting hard disk with it.

Could you help me? I tried to find a solution, few have the same problem but running os-prober in my case didn't helped at all.

Thanks.

Here are the outputs of update-grub, update-grub2 and os-prober

Code:

firekage@deusex:~$ sudo os-prober

[sudo] password for firekage:

/dev/sda2:Slackware Linux (Slackware 13.37.0):Slackware:linux

/dev/sdc1:Windows Vista (loader):Windows:chain

/dev/sdd1:Slackware Linux (Slackware 14.0):Slackware1:linux

/dev/sdf1:Ubuntu 12.04.2 LTS (12.04):Ubuntu:linux

and

Code:

firekage@deusex:~$ sudo update-grub

Generating grub.cfg ...

Found linux image: /boot/vmlinuz-3.2.0-24-generic-pae

Found initrd image: /boot/initrd.img-3.2.0-24-generic-pae

Found linux image: /boot/vmlinuz-3.2.0-24-virtual

Found initrd image: /boot/initrd.img-3.2.0-24-virtual

Found linux image: /boot/vmlinuz-3.2.0-24-generic

Found initrd image: /boot/initrd.img-3.2.0-24-generic

Found memtest86+ image: /boot/memtest86+.bin

Found Slackware Linux (Slackware 13.37.0) on /dev/sda2

Found Windows Vista (loader) on /dev/sdc1

Found Slackware Linux (Slackware 14.0) on /dev/sdd1

Found Ubuntu 12.04.2 LTS (12.04) on /dev/sdf1

done

and

Code:

firekage@deusex:~$ sudo update-grub2

Generating grub.cfg ...

Found linux image: /boot/vmlinuz-3.2.0-24-generic-pae

Found initrd image: /boot/initrd.img-3.2.0-24-generic-pae

Found linux image: /boot/vmlinuz-3.2.0-24-virtual

Found initrd image: /boot/initrd.img-3.2.0-24-virtual

Found linux image: /boot/vmlinuz-3.2.0-24-generic

Found initrd image: /boot/initrd.img-3.2.0-24-generic

Found memtest86+ image: /boot/memtest86+.bin

Found Slackware Linux (Slackware 13.37.0) on /dev/sda2

Found Windows Vista (loader) on /dev/sdc1

Found Slackware Linux (Slackware 14.0) on /dev/sdd1

Found Ubuntu 12.04.2 LTS (12.04) on /dev/sdf1

done

firekage@deusex:~$

It is, during reboot on purple grub, it isn't.

Your output above shows windows on sdc1 and windows likes to be on the first drive so you should be able to boot by mapping the drive. Add the following to your windows menuentry in grub.cfg:

set root=(hd2,1)
drivemap -s hd0 hd2

Reboot to test it and if it succeeds, copy the windows entry to /etc/grub.d/40_custom and run update-grub.

Quote:

Originally Posted by yancek (Post 4968352)

Could you explain setting root here? I'm not familiar with this kind of naming devices (i know windows letters naming devices and linux naming devices /dev/sdXY, but here are propably msdos and i dont understand how to use it in future).

Why i need it on the first "disk" - it worked on plain install.

BTW - what "mapping" drive here means?

This is the output from /boot/grub/grub.cfg

Code:

### BEGIN /etc/grub.d/30_os-prober ###

menuentry "Slackware_13.37 (on /dev/sda2)" --class gnu-linux --class gnu --class os {

        insmod part_msdos

        insmod ext2

        set root='(hd0,msdos2)'

        search --no-floppy --fs-uuid --set=root 0a2ebb07-8b93-4938-9bee-7eca19168eee

        linux /boot/vmlinuz root=UUID ro  vt.default_utf8=0 vga = normal append = "resume=UUID=9a4b8b62-9163-4d61-b9af-4d4c75e29fee

}

menuentry "Windows Vista (loader) (on /dev/sdc1)" --class windows --class os {

        insmod part_msdos

        insmod ntfs

        set root='(hd2,msdos1)'

        search --no-floppy --fs-uuid --set=root 20FEB393FEB36028

        chainloader +1

}

menuentry "Slackware_14 (on /dev/sdd1)" --class gnu-linux --class gnu --class os {

        insmod part_msdos

        insmod ext2

        set root='(hd3,msdos1)'

        search --no-floppy --fs-uuid --set=root 340d8335-6690-46fd-8b73-26f68cfb317d

        linux /boot/vmlinuz root=UUID ro  vt.default_utf8=0 vga = normal append = "resume=UUID=9a4b8b62-9163-4d61-b9af-4d4c75e29fee

}

menuentry "Ubuntu, za pomocą systemu Linux 3.2.0-39-generic-pae (on /dev/sdf1)" --class gnu-linux --class gnu --class os {

        insmod part_msdos

        insmod ext2

        set root='(hd5,msdos1)'

        search --no-floppy --fs-uuid --set=root 8ef102e8-b7d4-4c5d-89f7-23cd35c85552

        linux /boot/vmlinuz-3.2.0-39-generic-pae root=UUID=8ef102e8-b7d4-4c5d-89f7-23cd35c85552 ro quiet splash $vt_handoff

        initrd /boot/initrd.img-3.2.0-39-generic-pae

}

menuentry "Ubuntu, za pomocą systemu Linux 3.2.0-39-generic-pae (tryb ratunkowy) (on /dev/sdf1)" --class gnu-linux --class gnu --class os {

        insmod part_msdos

        insmod ext2

        set root='(hd5,msdos1)'

        search --no-floppy --fs-uuid --set=root 8ef102e8-b7d4-4c5d-89f7-23cd35c85552

        linux /boot/vmlinuz-3.2.0-39-generic-pae root=UUID=8ef102e8-b7d4-4c5d-89f7-23cd35c85552 ro recovery nomodeset

        initrd /boot/initrd.img-3.2.0-39-generic-pae

}

menuentry "Ubuntu, za pomocą systemu Linux 3.2.0-37-generic-pae (on /dev/sdf1)" --class gnu-linux --class gnu --class os {

        insmod part_msdos

        insmod ext2

        set root='(hd5,msdos1)'

        search --no-floppy --fs-uuid --set=root 8ef102e8-b7d4-4c5d-89f7-23cd35c85552

        linux /boot/vmlinuz-3.2.0-37-generic-pae root=UUID=8ef102e8-b7d4-4c5d-89f7-23cd35c85552 ro quiet splash $vt_handoff

        initrd /boot/initrd.img-3.2.0-37-generic-pae

}

menuentry "Ubuntu, za pomocą systemu Linux 3.2.0-37-generic-pae (tryb ratunkowy) (on /dev/sdf1)" --class gnu-linux --class gnu --class os {

        insmod part_msdos

        insmod ext2

        set root='(hd5,msdos1)'

        search --no-floppy --fs-uuid --set=root 8ef102e8-b7d4-4c5d-89f7-23cd35c85552

        linux /boot/vmlinuz-3.2.0-37-generic-pae root=UUID=8ef102e8-b7d4-4c5d-89f7-23cd35c85552 ro recovery nomodeset

        initrd /boot/initrd.img-3.2.0-37-generic-pae

}

### END /etc/grub.d/30_os-prober ###

Everything you have posted suggests to me that Ubuntu can see the Windows Vista install just fine and even includes it in your grub.cfg.
When you see the GRUB screen have you tried pressing an arrow key (to stop the timer) then looking for and entry named something like "Other OSs"? Also, does Slackware show up on the GRUB menu you see?

In your first post, you indicate you are seeing a purple screen on boot which means it is Ubuntu. Is the grub.cfg file you posted from Ubuntu? If so, you should see this for windows:

Quote:

"Windows Vista (loader) (on /dev/sdc1)"

Whatever is between double quotes on the menuentry line should show on the boot menu. If you posted the entire grub.cfg file from Ubuntu, your windows entry should be the second entry.

The reference to set root is from the menuentry in grub.cfg. In Grub Legacy, it was: root (hd0,0) or whatever drive/partition. So I would suggest that your change the line in your windows entry by adding this line below the current set root='(hd2, msdos1)': drivemap -s hd0 hd2 so that your entry looks like this:

Code:

menuentry "Windows Vista (loader) (on /dev/sdc1)" --class windows --class os {

        insmod part_msdos

        insmod ntfs

        set root='(hd2,msdos1)'

        drivemap -s hd0 hd2

        search --no-floppy --fs-uuid --set=root 20FEB393FEB36028

        chainloader +1

}

The mapping command is basically to get windows to think it is on the first drive.

Quote:

Why i need it on the first "disk" - it worked on plain install.

Was it on the third drive when you originally installed it? Do you no longer have Kubuntu installed. If the above doesn't work, it may be a good idea to go to the site below and download and run the bootinfoscript and post the output, a results.txt file here to provide more information:

http://sourceforge.net/projects/bootinfoscript/

Quote:

Originally Posted by 273 (Post 4968477)

Yes, i tried this and it doesen't work, and yes, slackware is being seen on purble grub, Vista doesen't appear here.

Quote:

Originally Posted by yancek (Post 4968484)

In your first post, you indicate you are seeing a purple screen on boot which means it is Ubuntu. Is the grub.cfg file you posted from Ubuntu?

Yes, it is from Ubuntu.

Quote:

Code:

menuentry "Windows Vista (loader) (on /dev/sdc1)" --class windows --class os {

        insmod part_msdos

        insmod ntfs

        set root='(hd2,msdos1)'

        drivemap -s hd0 hd2

        search --no-floppy --fs-uuid --set=root 20FEB393FEB36028

        chainloader +1

}

The mapping command is basically to get windows to think it is on the first drive.

Ik, i don't understand this part in "code" but i will do it.

Quote:

I haven't changed anything, it was and it is on the same disk. I just upgraded Ubuntu, and Vista vanished from purple grub. I have still Kubuntu installed.

I'm not sure what you mean in your last post about not understanding the part in code. On each menuentry line, there is a section in double quotes and that part and only that part is what you should see on your boot menu. Reading over your posts, I guess I misread and your problem is not just that you can't boot but that you don't even see the windows entry as an option on boot, is that correct?

The menuentry lines in grub.cfg should show up on the boot menu and in the grub.cfg file you posted, you have two Slackware entries with vista between them and four Ubuntu entries. You should see all of them in that order if the default is set to zero. If you use the down arrow key, you should see all the entries.

The only scenario I can think of that would explain this is that you are running update-grub or editing the grub.cfg file in Kubuntu when you have the Ubuntu Grub in the master boot record - seeing the purple screen would indicate that as with Kubuntu it would be a blue screen.

The only suggestion I would have if you haven't resolve this issue is to go to the link I posted earlier and download and run the bootinfoscript, posting the results here. Read the instructions, there is a link in the Description box on the site.

You could also copy/paste the entry in the grub.cfg file to /etc/grub.d/40_custom if the down button doesn't reveal the entry that should be on your screen menu.

You will need to run update-grub to get that into the grub.cfg file. Will be the last entry on your screen menu.

Quote:

Originally Posted by firekage (Post 4968330)

I would like to ask for your help. I have problem with Ubuntu, Kubuntu related to not detecting Windows Vista in grub. ...

You may want to try the Ubuntu Boot Repair tool: https://help.ubuntu.com/community/Boot-Repair
You can either make a live CD with Boot Repair, or you can install Boot Repair to your working Ubuntu system.
Note that since you can already boot Ubuntu, you do not need to boot from an Ubuntu live CD. You should be able to add that PPA to your Ubuntu system and run Boot Repair from your working Ubuntu install.

Quote:

Originally Posted by yancek (Post 4969150)

Yes. I cant even see Vista on the list.

Quote:

The menuentry lines in grub.cfg should show up on the boot menu and in the grub.cfg file you posted, you have two Slackware entries with vista between them and four Ubuntu entries. You should see all of them in that order if the default is set to zero. If you use the down arrow key, you should see all the entries.

Yes, that's correct exept Vista.

Quote:

The only scenario I can think of that would explain this is that you are running update-grub or editing the grub.cfg file in Kubuntu when you have the Ubuntu Grub in the master boot record - seeing the purple screen would indicate that as with Kubuntu it would be a blue screen.

My mistake. Even on the blue grub from Kubuntu the same thing happens. I don't see it from purple and blue from Ubuntu and Kubuntu.

Quote:

The only suggestion I would have if you haven't resolve this issue is to go to the link I posted earlier and download and run the bootinfoscript, posting the results here. Read the instructions, there is a link in the Description box on the site.

Ok.

---------- Post added 06-11-13 at 03:47 PM ----------

Quote:

Originally Posted by tommcd (Post 4969272)

Did that. Didn't helped.

Quote:

Originally Posted by yancek (Post 4968484)

So I would suggest that your change the line in your windows entry by adding this line below the current set root='(hd2, msdos1)': drivemap -s hd0 hd2 so that your entry looks like this:

Code:

menuentry "Windows Vista (loader) (on /dev/sdc1)" --class windows --class os {

        insmod part_msdos

        insmod ntfs

        set root='(hd2,msdos1)'

        drivemap -s hd0 hd2

        search --no-floppy --fs-uuid --set=root 20FEB393FEB36028

        chainloader +1

}

I did it and it doesen't work. Still no Vista in purple and blue grub.

There is somethinfg more. In this quoted part there is "drivemap -s hd0 hd2" but earlier You suggested me to write something different:

Quote:

set root=(hd2,1)
drivemap -s hd0 hd2

but i don't know which is correct.

BTW - after update-grub with added lines posted above, they dissapear.

Update - either way, it doesen't work. Tried both of them. I will post bootscript.

Here is my boot-repair log, could you check it?

http://paste.ubuntu.com/5767574/

I added also something here;

http://ubuntuforums.org/showthread.p...1#post12692161

Quote:

I have installed ubuntu on my 2 laptops (Acer E531 and AOD 270) and have Vista on them, it is being detected but these laptops have only one disk with few partitions, while my desktop have 6 or 7 disk with more than one partition.

I think you inadvertently mislead us.
You appear to have 3 GRUB installs and one LiLo install. So, which hard drive's MBR is being booted and which instance of GRUB are you seeing?