| View previous topic :: View next topic |
| Author |
Message |
Veovis Muaddib
n00b
Joined: 07 Dec 2011
Posts: 1
|
 Posted: Wed Dec 07, 2011 7:36 am Post subject: Sent here by someone on #archlinux for help with UEFI Shell |
 |
|
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: |
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. |
|
| Back to top |
|
 |
tomk
Bodhisattva
Joined: 23 Sep 2003
Posts: 7221
Location: Sat in front of my computer
|
| Posted: Thu Dec 08, 2011 5:37 pm Post subject: |
|
|
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 dewhite's update (and the subsequently added OTW flair, which has been left behind. --pjp, 2018.11.18
_________________
Search | Read | Answer | Report | Strip |
|
| Back to top |
|
|
Veovis Muaddib
n00b
Joined: 07 Dec 2011
Posts: 1
|
| Posted: Thu Dec 08, 2011 10:08 pm Post subject: |
|
|
| 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. |
|
| Back to top |
|
|
dewhite
Tux's lil' helper
Joined: 16 Mar 2003
Posts: 106
Location: Houston, Texas, USA
|
| Posted: Wed Nov 14, 2018 10:18 pm Post subject: |
|
|
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:
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!
_________________
Work FS: R7-5700g | 2x16Gb DDR4 | 500Gb NVMe LUKS root | 2x 8TB RAID1
Home FS: R7-1700x | 2x8Gb DDR4 | 275Gb M.2 SATA LUKS root | 2x 14TB RAID1 |
|
| Back to top |
|
|
|
Unsupported Software
