Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi,
I've never been able to boot from GRUB to Windows 7, regardless of what method I've tried. osprober doesn't pick up my Windows partition because it's on sda (GRUB is installed on sdb), and the only way to boot into Windows is to select "2.2TB Infinity" as the boot device from BIOS, which in turn boots Windows (booting directly to sda doesn't work).
Has anyone ever dealt with 2.2TB Infinity and getting it to cooperate with GRUB?
osprober doesn't pick up my Windows partition because it's on sda (GRUB is installed on sdb)
It doesn't matter if it is on another drive. If you have both drives attached running os-prober and update-grub should detect a bootloader on whichever partition. There's something else going on here. Run the command again and post the results including the command you use.
It would help if you reveal some or all of your grub configuration. Methods you've tried may not be at all correct. There's no way to know without seeing the configs.
So, I accidently figured out how to get it working. The problem was that I was trying to boot into a particular partition, instead of the hard-drive itself (which 2.2TB requires).
My entry in 40_custom resembled:
Code:
menuentry "Windows 7" {
set root=hd1
chainloader +1
}
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.