Sent here by someone on #archlinux for help with UEFI Shell

[Veovis Muaddib]

I was wondering if I could have some assistance in booting grub-efi from UEFI shell. It's for Arch Linux, but I was told to come here instead, because you guys seem to have better documentation on using UEFI shell. Running ASUS EeePC 1215b.

Here's what I get upon startup, copied by hand to this machine:

Code: Select all

Device mapping table
fs0           :HardDisk - Alias hd12a1 blk0         [SUSPECTED /DEV/SDA1, MY EFI PARTITION]
                ~Snip~
blk0         :HardDisk - Alias hd12a1 fs0           [DUPLICATE OF FS0?]
                ~Snip~
blk1         :HardDisk - Alias (null)                    [MY /]
                ~Snip~
blk2         :HardDisk - Alias (null)                    [MY SWAP]
                ~Snip~
blk3         :HardDisk - Alias (null)                    [MAIN DISK?]


Shell> mount fs0

Success - Force file system to mount

Shell > ls
ls/dir: Cannot open current directory - No Mapping

Shell  > cd efi             [DIRECTORY GRUB IS IN]
cd: Cannot find mapped device

Shell  > mount blk0

Success - Force file system to mount

Shell > ls
ls/dir: Cannot open current directory - No Mapping

Shell  > cd efi
cd: Cannot find mapped device

Shell  > mount hd12a1

Success - Force file system to mount

Shell > ls
ls/dir: Cannot open current directory - No Mapping

Shell  > cd efi
cd: Cannot find mapped device

Mount doesn't seem to take more than one argument, so I don't know what's going on here.

[tomk]

Moved from Other Things Gentoo to Off the Wall, support for other distributions belongs in OTW.

Moved from Off the Wall to Unsupported Software after [post=8281864]dewhite's update[/post] (and the subsequently added OTW flair, which has been left behind. --pjp, 2018.11.18

[Veovis Muaddib]

I was pretty tired that night, and couldn't find this section. I was looking at the Gentoo sections and scrolled down too fast I think. Thanks, and sorry for the inconvenience.

[dewhite]

I'm aware that this thread is _very_ old. However, I was running into a similar issue today while trying to flash upgraded firmware to an LSI HBA and I think it would have been helpful if an answer had been posted here for other Googlers to find.

In my case - the issue was that the EFI shell hadn't defaulted to one of the multiple filesystems that were mounted at boot. This is likely the same issue this fellow from 2011 was experiencing because his shell prompt read: "Shell >" instead of leading with the disk location.

One simply needs to enter the filesystem location where they expect to find their files at that prompt by typing, for example:

Code: Select all

fs0:

followed by a carriage return.

The prompt will change to fs0:> and commands for "dir" or "ls" or "cd" should work as expected. In my case, 3 filesystems had been automatically mounted at boot (fs0, fs1, and fs2). I eventually found the files I was looking for in fs1. Changing between filesystems is as simple as typing in fsX: and pressing "return" again, where X is a number between 0 and infinity. The shell command "map" (or "map -b" for a paged view) can also be used to list all devices and filesystems for some clues about what all was detected and mounted by the shell at boot.

Good luck all!