F5F Stay Refreshed Software Operating Systems Linux startup problems.

Linux startup problems.

Linux startup problems.

Pages (2): 1 2 Next
X
XDarkSlayerX
Junior Member
20
02-29-2016, 08:54 AM
#1
Your ASUS laptop features an HDD with three partitions—one containing Windows and another being a fresh SSD. After installing Linux Mint on the SSD, you booted via GRUB but faced issues with touchpad support, prompting you to uninstall it. You then switched to a live Linux USB, formatted the SSD, and followed similar steps with Windows, formatting it as NTFS. Now the SSD appears as a blank 111GB drive despite being unused. In the boot menu, Ubuntu still appears and launches GRUB when selected. Attempts to remove the boot partition from BIOS were unsuccessful. No Wi-Fi files are present. You’re looking to erase the SSD completely and eliminate the Grub installation.
X
XDarkSlayerX
02-29-2016, 08:54 AM #1

Your ASUS laptop features an HDD with three partitions—one containing Windows and another being a fresh SSD. After installing Linux Mint on the SSD, you booted via GRUB but faced issues with touchpad support, prompting you to uninstall it. You then switched to a live Linux USB, formatted the SSD, and followed similar steps with Windows, formatting it as NTFS. Now the SSD appears as a blank 111GB drive despite being unused. In the boot menu, Ubuntu still appears and launches GRUB when selected. Attempts to remove the boot partition from BIOS were unsuccessful. No Wi-Fi files are present. You’re looking to erase the SSD completely and eliminate the Grub installation.

L
lainey123
Junior Member
8
03-07-2016, 06:38 PM
#2
It looks like your OS is in disarray. I recommend starting with a fresh installation of both Windows and Linux.
L
lainey123
03-07-2016, 06:38 PM #2

It looks like your OS is in disarray. I recommend starting with a fresh installation of both Windows and Linux.

M
MikeDragon159
Senior Member
661
03-07-2016, 10:52 PM
#3
Grub was likely added to the Windows UEFI partition. You'll need a Linux Live installation media booted to the Linux Live Desktop you prefer. Identify a Fat32 partition on the drive with your Windows install. Eliminate any entries that mention Grub, Ubuntu, Linux, or Mint. Open a terminal. efibootmgr will display entries such as "Boot0003* Arch Linux". The final number you need is the one following the sequence, for example 3 in this case. Run efibootmgr -b number_of_entry -B to restart your system.
M
MikeDragon159
03-07-2016, 10:52 PM #3

Grub was likely added to the Windows UEFI partition. You'll need a Linux Live installation media booted to the Linux Live Desktop you prefer. Identify a Fat32 partition on the drive with your Windows install. Eliminate any entries that mention Grub, Ubuntu, Linux, or Mint. Open a terminal. efibootmgr will display entries such as "Boot0003* Arch Linux". The final number you need is the one following the sequence, for example 3 in this case. Run efibootmgr -b number_of_entry -B to restart your system.

L
LeCapoChino
Junior Member
29
03-09-2016, 01:02 AM
#4
Because the issue isn't caused by any mistakes on your end. A Live Installer tends to reuse the same EFI partition even if it's on a different drive. Just remove the files and delete the entry—no need to reinstall anything.
L
LeCapoChino
03-09-2016, 01:02 AM #4

Because the issue isn't caused by any mistakes on your end. A Live Installer tends to reuse the same EFI partition even if it's on a different drive. Just remove the files and delete the entry—no need to reinstall anything.

D
146
03-13-2016, 11:40 PM
#5
Looking for a way to proceed without a live system? I only have a single flash drive, and I'm trying to see if installing Windows on an SSD is possible.
D
D14M0ND_D34THS
03-13-2016, 11:40 PM #5

Looking for a way to proceed without a live system? I only have a single flash drive, and I'm trying to see if installing Windows on an SSD is possible.

F
FoxX_MC
Member
107
03-24-2016, 08:04 PM
#6
I don’t know of any method, but I’m not confident enough with Windows to understand. Your SSD should be okay. The boot entry is saved in the BIOS and the Grub files are on your current Windows EFI partition. Adding something to the SSD won’t help if you’ve formatted it, since it’s already empty.
F
FoxX_MC
03-24-2016, 08:04 PM #6

I don’t know of any method, but I’m not confident enough with Windows to understand. Your SSD should be okay. The boot entry is saved in the BIOS and the Grub files are on your current Windows EFI partition. Adding something to the SSD won’t help if you’ve formatted it, since it’s already empty.

R
Redconfuser
Junior Member
45
03-25-2016, 12:49 AM
#7
Hey everyone, I'm still getting the hang of this. My main goal is to run Windows on an SSD, but Linux doesn't work well with the touchpad. I'm wondering if installing Windows fresh on the SSD will interfere with the boot process. If I do that, can I just keep using the Ubuntu Boot partition? And what about the potential issues with Grub?
R
Redconfuser
03-25-2016, 12:49 AM #7

Hey everyone, I'm still getting the hang of this. My main goal is to run Windows on an SSD, but Linux doesn't work well with the touchpad. I'm wondering if installing Windows fresh on the SSD will interfere with the boot process. If I do that, can I just keep using the Ubuntu Boot partition? And what about the potential issues with Grub?

A
akgdgr8est
Junior Member
2
03-25-2016, 09:12 AM
#8
It shouldn't create any problems. Yes. You might only need to adjust your boot sequence. If you're setting up Windows on an SSD and wiping the old installation, it should remove the GRUB files during that process. GRUB is actually stored in your existing Windows Boot Partition, so leaving it in place won't cause issues. As a tip for smoother starts later, disconnect all other drives except the one you're installing to. After finishing, reconnect them to avoid partition conflicts.
A
akgdgr8est
03-25-2016, 09:12 AM #8

It shouldn't create any problems. Yes. You might only need to adjust your boot sequence. If you're setting up Windows on an SSD and wiping the old installation, it should remove the GRUB files during that process. GRUB is actually stored in your existing Windows Boot Partition, so leaving it in place won't cause issues. As a tip for smoother starts later, disconnect all other drives except the one you're installing to. After finishing, reconnect them to avoid partition conflicts.

D
dasfuss
Member
156
03-26-2016, 03:08 PM
#9
Thank you for your kind words. I currently used diskpart and confirmed there’s an inaccessible 200MB fat32 partition. The Grub area is where it resides. As you mentioned, installing Windows on the new drive should be manageable.
D
dasfuss
03-26-2016, 03:08 PM #9

Thank you for your kind words. I currently used diskpart and confirmed there’s an inaccessible 200MB fat32 partition. The Grub area is where it resides. As you mentioned, installing Windows on the new drive should be manageable.

J
jvdbreemen
Member
191
03-27-2016, 12:07 AM
#10
I experienced the same issue before. Assuming Windows is still running, you can proceed. (Be cautious) From the Admin Command, execute: mountvol U: /s dir /A /S U:\ If a loader.efi file exists: delete /F U:path\loader.efi. If your directory contains an Ubuntu folder, use: RD /S /Q "U:EFI\ubuntu" mountvol U: /D Reboot. I suspect your folder will be labeled as Mint or similar. Let me know! Edited August 22, 2020 by Jurien72 Added clarification details
J
jvdbreemen
03-27-2016, 12:07 AM #10

I experienced the same issue before. Assuming Windows is still running, you can proceed. (Be cautious) From the Admin Command, execute: mountvol U: /s dir /A /S U:\ If a loader.efi file exists: delete /F U:path\loader.efi. If your directory contains an Ubuntu folder, use: RD /S /Q "U:EFI\ubuntu" mountvol U: /D Reboot. I suspect your folder will be labeled as Mint or similar. Let me know! Edited August 22, 2020 by Jurien72 Added clarification details

Pages (2): 1 2 Next