HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Integrity Servers
- >
- EFI Shell
Integrity Servers
1827769
Members
2690
Online
109969
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2007 03:03 AM
02-27-2007 03:03 AM
Red Hat Enterprise Linux 3
In simple prompt I can send the output of a command to a text file (Example: ls -l > output.txt)
How can I do the same in EFI Shell?
In simple prompt I can send the output of a command to a text file (Example: ls -l > output.txt)
How can I do the same in EFI Shell?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2007 03:13 AM
02-27-2007 03:13 AM
Re: EFI Shell
I have tried with following errors.
Shell> errdump mca > errdump_mca.log
Could not open output file errdump_mca.log
Exit status code: Invalid Parameter
Shell> errdump mca > errdump_mca.log
Could not open output file errdump_mca.log
Exit status code: Invalid Parameter
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2007 03:50 AM
02-27-2007 03:50 AM
Solution
You must change to a disk.
You are still in the firmware
Shell>
try
Shell> fs0:
(or another existing disk)
fs0> your_command > output file
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
You are still in the firmware
Shell>
try
Shell> fs0:
(or another existing disk)
fs0> your_command > output file
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-27-2007 03:53 AM
02-27-2007 03:53 AM
Re: EFI Shell
I'm not in a spot where I can look at the EFI shell to verify the following, but here is what Intel claims for EFI I/O redirection syntax:
cmd > unicode.log
cmd >a ascii.log
cmd 1> unitcode.log
cmd 1>a ascii.log
cmd 2> unicode_stder.log
cmd 2>a ascii_stderr.log
cmd >> unicode_append.log
cmd >>a ascii_append.log
cmd 1>> unicode_append.log
cmd 1>>a ascii_append.log
Try a few commands other than errdump, on the off chance that errdump isn't playing by the rules. (It looks like it might not be, based on the error message.)
Most folks tend to capture the error log using a serial-line capture; a capture from the terminal emulator. Or from the error log, if that's available and loading up messages from the EFI level. (But if you're looking at the error log, you also might not be booting.)
Stephen Hoffman
HoffmanLabs
cmd > unicode.log
cmd >a ascii.log
cmd 1> unitcode.log
cmd 1>a ascii.log
cmd 2> unicode_stder.log
cmd 2>a ascii_stderr.log
cmd >> unicode_append.log
cmd >>a ascii_append.log
cmd 1>> unicode_append.log
cmd 1>>a ascii_append.log
Try a few commands other than errdump, on the off chance that errdump isn't playing by the rules. (It looks like it might not be, based on the error message.)
Most folks tend to capture the error log using a serial-line capture; a capture from the terminal emulator. Or from the error log, if that's available and loading up messages from the EFI level. (But if you're looking at the error log, you also might not be booting.)
Stephen Hoffman
HoffmanLabs
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP