Tiny Core Base > Corepure64

GRUB 2 always starts in command line - can't proceed - EFI Boot

<< < (5/11) > >>

PDP-8:
Ok, can't wait - probably getting waaay too far ahead here.

So I tried to "ls" those paths from grub>

And they all ended up with
error: "unknown filesystem"


--- Code: ---ls hd0,gpt1
ls hd0
.
.
ls hd0,gpt1/EFI/BOOT
ls hd0/EFI/BOOT/grub
.
l
ls /hd0,gpt1/EFI/BOOT
ls /hd0/EFI/BOOT

--- End code ---

Seems like all my attempts to ls results in unknown filesystem.

PDP-8:
Re: the pun

Corny, but I couldn't help myself.

I imagined that one of my idols, Brian Kernighan, would say it this way, whom Doug McIlroy claimed was an "expositor par excellence"..

Heh, us old guys. :)

coreplayer2:

--- Quote from: PDP-8 on July 24, 2019, 03:12:32 PM ---The other question is there some major difference in bootx64.efi between TC and the distro that this replacement came from?

--- End quote ---
Indeed there is and it’s by design.   You see each bootx64.efi boot loader is created by grub-mkimage  which is executed by grub-install with the the personalized parameters provided.  These parameters usually include the path to its configuration file (grub.cfg) known as the prefix and modules required to read file systems etc etc

You may also create an boot image file with all the modules included so that the grub modules folder is not required, but that’s another story





--- Quote ---Seems like all my attempts to ls results in unknown filesystem.

--- End quote ---
Ok,  ls can’t read the file system if root has not been set..


Sent from my iPhone using Tapatalk

PDP-8:

--- Quote ---Ok,  ls can’t read the file system if root has not been set..
--- End quote ---

Well, it is already set as hd0 being baked in when using grub>set to view the variables as delivered from the iso.

So, with root=hd0 already set as the baked in value from the iso, I tried to ls it:


--- Code: ---ls (hd0)
Device hd0: No known filesystem detected - sector size 512B - Total size 152320000KiB
--- End code ---

Hmm.  Ok, looks to be the entire size of my drive.

So lets step through all eleven of the possible HDx options as shown by grub>ls


--- Code: ---set root=(hd0,gpt1)
ls (hd0,gpt1)

Partitions hd0,gpt1: No known filesystem detected - Partition start at 1024KiB - Total Size 15230959.5KiB

--- End code ---

Seems like grub duly recognizes the partitions, but stubbornly refuses to recognize the filesystems.  I tried changing the root, and the ls'ing all of the other 11 HDx options that grub found, but the all report no known fileystem.  Partition sizes DO have different values!

So if it can't recognize the partitions with an ls, there is no point trying to start the kernel or initrd right?

I'll study up, but man this is sooo frustrating.  I appreciate the help.

PDP-8:
Not sure if this helps or if this is noise ...

So I forced the grub commandline from the working puppy bootx64.efi to take a peek with the set command:  Some interesting values

cmdpath=(hd0)/EFI/BOOT
prefix=(memdisk)/boot/grub
root=hd0,gpt1

MEMDISK?


--- Code: ---ls (memdisk)
Filesystem type tarfs
Sector Size 512B Total Size 3070KiB

ls (memdisk)/
boot/ euro.pf2

ls (memdisk)/boot/grub
locale/ x86_64-efi/ grub.cfg

--- End code ---

And I can ls any of the HDx partitions, and their filesystem is recognized and can browse through the systems, *EXCEPT* for hd0.  Yet this system boots.

Fascinating.  Sure beats the typical shade-tree recommendations out there to just put my computer in the fridge, change my boot order, delete my windows partition, run grub2 magic fixer/cleaner distro..... :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page