F5F Stay Refreshed Software Operating Systems Set up two distinct partitions for Ubuntu and Windows on separate storage devices.

Set up two distinct partitions for Ubuntu and Windows on separate storage devices.

Set up two distinct partitions for Ubuntu and Windows on separate storage devices.

G
Gamerking136
Member
58
06-11-2023, 01:07 AM
#1
Hi, I recently set up a new rig and installed windows and ubuntu on separate SSDs. I've been attempting to use gnu grub for OS selection at startup but have encountered issues lately. Specifically, when trying to boot Windows from gnu grub, it reports "no such device" and can't locate the expected files. This problem occurs intermittently. After a reset, I entered command-line mode in gnu grub and successfully launched Windows again. To resolve this, I've tried updating grub with sudo update-grub, which now recognizes the Windows boot loader and adds it to the config. In the grub configuration file, it appears correctly placed. I also reviewed the steps on the provided thread and attempted a similar fix, though the issue reappeared after shutting down and restarting. My current solution is adjusting the boot order in BIOS. Since I'm not very experienced with gnu grub or boot modes (UEFI vs legacy), any guidance would be greatly appreciated. Please let me know if you have additional details that could help. Thank you ahead of time.
G
Gamerking136
06-11-2023, 01:07 AM #1

Hi, I recently set up a new rig and installed windows and ubuntu on separate SSDs. I've been attempting to use gnu grub for OS selection at startup but have encountered issues lately. Specifically, when trying to boot Windows from gnu grub, it reports "no such device" and can't locate the expected files. This problem occurs intermittently. After a reset, I entered command-line mode in gnu grub and successfully launched Windows again. To resolve this, I've tried updating grub with sudo update-grub, which now recognizes the Windows boot loader and adds it to the config. In the grub configuration file, it appears correctly placed. I also reviewed the steps on the provided thread and attempted a similar fix, though the issue reappeared after shutting down and restarting. My current solution is adjusting the boot order in BIOS. Since I'm not very experienced with gnu grub or boot modes (UEFI vs legacy), any guidance would be greatly appreciated. Please let me know if you have additional details that could help. Thank you ahead of time.

T
TorJules
Member
184
06-17-2023, 08:58 PM
#2
On certain boards it's possible to turn off all boot devices, which then displays a menu for selecting a drive to start from during power-on/reset. Another method involves using a "boot selection hotkey" at startup to pick a different boot drive. Managing grub or Windows boot manager can become more complicated when auto-updates are active on a Linux system.
T
TorJules
06-17-2023, 08:58 PM #2

On certain boards it's possible to turn off all boot devices, which then displays a menu for selecting a drive to start from during power-on/reset. Another method involves using a "boot selection hotkey" at startup to pick a different boot drive. Managing grub or Windows boot manager can become more complicated when auto-updates are active on a Linux system.

C
ComboHax
Member
184
06-19-2023, 11:12 PM
#3
Essentially, the only option I have is pressing F12 each time I start or change the operating system to pick the boot drive, followed by disabling GRUB.
C
ComboHax
06-19-2023, 11:12 PM #3

Essentially, the only option I have is pressing F12 each time I start or change the operating system to pick the boot drive, followed by disabling GRUB.

X
XxgamerxX1677
Member
214
06-19-2023, 11:42 PM
#4
Backing up was once easier. Now it appears Microsoft is changing parts of their bootloader without notice to confuse Linux users.
X
XxgamerxX1677
06-19-2023, 11:42 PM #4

Backing up was once easier. Now it appears Microsoft is changing parts of their bootloader without notice to confuse Linux users.

F
foz93
Member
136
06-19-2023, 11:49 PM
#5
Use @= sda1 or whatever GRUB partition is active, though likely sda1 @@= sda or the boot sector where Linux and Windows 10 are installed. Probably mount sda as sudo with /dev/@, then bind dev, pts, proc, and sys accordingly.
F
foz93
06-19-2023, 11:49 PM #5

Use @= sda1 or whatever GRUB partition is active, though likely sda1 @@= sda or the boot sector where Linux and Windows 10 are installed. Probably mount sda as sudo with /dev/@, then bind dev, pts, proc, and sys accordingly.