- Community Home
- >
- Storage
- >
- Data Protection and Retention
- >
- StoreEver Tape Storage
- >
- Re: MSL2024 Drive Comm.-Err./Code: F1 00
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
09-08-2009 10:40 PM
09-08-2009 10:40 PM
MSL2024 Drive Comm.-Err./Code: F1 00
I have a problem on MSL2024.
The LCD displays message below:
Drive Comm.-Err.
Code: F1 00
At this time, web management interface displays this error message:
09.07.22 02:44:50.44 Library Error - HE: drive communication error
Return status: 0x80 - command failed
Global error code: 0xF1 - hardware error, drive communication
Module error code: 0x01, 1
Task originator: 0x00 - Libctrl task
Extender library specifier: 0x00 - master library
Sub error type: 0x01 - native SDCI error
Data: Sdci return code 20, Error code 01, USART error code 00, number retries 00
Source element type.: 0x04 - tape drive
Element number: 0x01, 1
Any help or advice?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2009 08:08 AM
09-10-2009 08:08 AM
Re: MSL2024 Drive Comm.-Err./Code: F1 00
Pablo Alvarado Siles
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2009 12:32 AM
09-16-2009 12:32 AM
Re: MSL2024 Drive Comm.-Err./Code: F1 00
I pulled out the drive and pushed it back to its slot, but the error was remained.
Any other advices?
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2009 06:22 AM
09-16-2009 06:22 AM
Re: MSL2024 Drive Comm.-Err./Code: F1 00
Pablo Alvarado Siles
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2025 02:53 AM
01-21-2025 02:53 AM
Re: MSL2024 Drive Comm.-Err./Code: F1 00
I had the simmilar problem with CU:
|__ 14:29:23 - 2024/12/07 Crit:0x00A3 HE: drive communication error
|__ Suggested service action: Power-cycle the device and retry the operation.
|__ Re-seat the tape drive to ensure a good connection to the device.
|__ 14:29:23 - 2024/12/07 (Code 0xF1) Crit:0x00a3 HE: drive communication error
||__ Return status: 128 (0x80) command failed
||__ Global error code: 241 (0xF1) HE: drive communication error
||__ Module error code: 1 (0x01)
||__ Task originator: 0 (0x00) Libctrl task
||__ Extender library specifier: 0 (0x00) master library
||__ Source element type.: 4 (0x04) tape drive
||__ Element number: 1 (0x01)
problem has been resolved by re-seating the TD
I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
