#Issue while installing to hard drive from live usb.

1 messages · Page 1 of 1 (latest)

zenith nimbus
#

i think i've seen this before, and the solution was to re-flash the usb drive with Fedora Media Writer and/or try again

#

are you trying to dual-boot with windows?

#

ah

#

maybe there's a grub partition already

#

do you know what your existing partition layout is?

#

could you send a screenshot of it?

#

ah

#

okay, so you deleted the ext4 /boot and the uefi entries with efibootmgr

#

could you mount the ESP (efi partition, vfat/fat32) and make sure there's nothing GRUB-related in there?

#

if you have Windows installed, open an admin command prompt and enter diskpart, then list disk, select disk <number>, list partition, select partition <number corresponding to esp>, then assign letter=e or something

#

then exit (or quit, whichever it is i can't remember), e:, and then dir to see the files in the esp

#

maybe windows explorer can do it from there idk

#

it should work if you start from a clean slate. you don't have a choice about which bootloader to use with secureblue

#

if you can, let me know if you're able to mount/open the ESP and whether there's anything grub-related in there :)

#

i think some people successfully do it

#

it's not very supported because windows likes to erase the GRUB data from the ESP or UEFI

#

and then you have to reinstall 🙃

#

but that's not secureblue's fault, it's just windows being a bad citizen

#

the other thing to keep in mind is that you'll need to configure Windows to use UTC for the RTC

#

windows likes to set your hardware real-time clock (which keeps track of time while the computer is switched off) to local time, i.e. your normal time zone

#

linux likes to set the hardware rtc to UTC, which is Iceland/UK time (depending on time of year)

#

if you don't get Windows to use UTC for the hardware clock, then the two OSes will fight over the local time and that can break encrypted connections etc.

#

it's just one of those awkward things

#

but it's easy enough to do

#

why not just make sure the ESP is clean (as in, just contains the Windows bootloader) and try to install secureblue again?

#

you want to install Linux after Windows, i think, so i don't think you'd be helping anything by doing that

#

it might be intimidating to think about opening the ESP with Windows, i think that might be the solution though

#

you just need to make sure everything's clean from previous Linux installations

#

or maybe someone else can help who's experienced this specific thing before

#

can you send a screenshot of Disk Management?

#

sure, so does it tell you which is the small fat32 one at the beginning?

#

wait i hope you actually have an ESP and not MBR lol

#

it's a recent computer right? it doesn't use BIOS

#

hmmm

#

send it anyway :))

#

wait you spoke about managing efibootmgr entries, so if that worked then you have UEFI

#

you've selected the wrong disk in diskpart

#

Disk Management shows Disk 0 as having a 512 MB "EFI System Partition" (the ESP)

#

dw

#

just select the other disk, list partitions again, and select the ESP

#

maybe in Disk Management you can right-click the 512 MB ESP and assign it a drive letter? i'm not sure

#

i don't remember Windows well enough, but you might be able to do that instead of using the command line

#

okay, so have a look in there and check to see whether there's any old GRUB

#

i think you need to use Command Prompt, as described above: exit diskpart, and using an elevated command prompt: ```

E:
dir```

zenith nimbus
#

so cd EFI and see what's inside it

#

sorry lol i'm maybe assuming too much familiarity with Windows' janky command line

#

aha

#

so first step is to delete the ubuntu folder, like rmdir /S ubuntu

#

and then dir to make sure it's deleted, and then cd BOOT to look inside there 👀

#

oh, . just means "current directory", .. means "the parent directory of this one"

#

it's the same on Linux

#

cd . does nothing; cd .. goes up a level

#

but you don't need that right now

#

have you deleted the ubuntu folder? what's inside the BOOT folder?

eager agate
#

I think I had a similar issue sometime ago. What fixed it for me was reflashing and setting FAT32 with block/cluster size 8192 (default is 4096) in Rufus. Not sure if it was the same issue, but you can try this ig?

zenith nimbus
#

either way, cleaning up ancient files in the ESP can't hurt

#

(though Rufus is good and probably works if you get the settings right, it's not an equivalent tool unless you run it in dd mode)

#

okay, so dir to make sure it's gone, and cd BOOT to look inside that?

#

definitely delete grubx64.efi, so just del grubx64.efi, but idk about fbx64.efi, let me see

#

it probably won't hurt to leave it in

#

i think it's something shim loads, but it doesn't matter, you can leave it

#

if you want to increase the size of C:\ and decrease the size of the currently unallocated space, you'll have to do that offline (when Windows isn't running) using a tool like gparted

#

but it's kind of a chore, because moving C:\ moves all the big important Windows files

#

you can extend the end of C:, but you can't really "move it back" by extending it at the beginning, i don't think?

eager agate
zenith nimbus
#

so @bold osprey i think you're good to go, please re-flash the USB stick using Fedora Media Writer

#

how did you make it the first time round?

#

hm, so it should be fine then

#

maybe re-flash it just in case on Windows, in case it didn't sync when you flashed it from Linux

#

it's up to you

#

what version of windows are you using?

#

are you using PowerShell as a regular user, or running as administrator?

#

do you have App Installer installed? https://apps.microsoft.com/detail/9nblggh4nns1?hl=en-GB&gl=GB

Microsoft Store - Download apps, games & more for your Windows PC
App Installer - Microsoft Apps

Microsoft App Installer simplifies the installation of Windows applications by allowing users to sideload app packages with a double-click—no need to run PowerShell scripts or command-line tools. It presents key package details such as the app name, publisher, version, display logo, and requested capabilities, streamlining the installation exp...

#

alternatively, maybe you can install GnuPG manually

#

okay, fair

#

GnuPG is to verify the signatures etc.

#

it's not crucial for flashing the ISO, though i can understand why you might want to do that

zenith nimbus
#

i don't know what you mean

#

if you deleted Ubuntu's UEFI entries directly using your firmware, or efibootmgr, then it shouldn't appear in your firmware

#

where is the option appearing?

#

so what is the output of efibootmgr --verbose --unicode?

#

ah well it doesn't matter

#

nw

#

i'm glad it's working