- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE 3PAR StoreServ Storage
- >
- Re: 3PAR StoreServ IDE File Integrity Check Bad, a...
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
Discussions
Discussions
Forums
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
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-03-2018 05:17 AM
тАО09-03-2018 05:17 AM
Hello. I have:
HP 3PAR 7400c (4 nodes) 3.3.1.410 (MU2) + P30,P32,P34,P35,P36,P38 + Upgrade_Tool_180809.U014
VSP 5.0.3.1-25112.
24.08.18 was installed update OS-4.2.0.18-U013 (180809.U014) 3PAR_SW_Upgrade_Tool_U014_QR482-11351.
01.09.18 I have problem, every 2 hours in the events logs is written:
showeventlog -sev Major
Severity : Major
Type : IDE file integrity check bad
Message : The check for valid files on the internal drive of Node 0 found the following invalid files: /opt/tpd/spn/drive.cfg.
Time : 2018-09-03 13:26:15 +03
Severity : Major
Type : IDE file integrity check bad
Message : The check for valid files on the internal drive of Node 1 found the following invalid files: /opt/tpd/spn/drive.cfg.
Time : 2018-09-03 13:26:15 +03
Severity : Major
Type : IDE file integrity check bad
Message : The check for valid files on the internal drive of Node 2 found the following invalid files: /opt/tpd/spn/drive.cfg.
Time : 2018-09-03 13:26:15 +03
Severity : Major
Type : IDE file integrity check bad
Message : The check for valid files on the internal drive of Node 3 found the following invalid files: /opt/tpd/spn/drive.cfg.
checkhealth -detail
Checking ao
Checking cabling
Checking cage
Checking cert
Checking dar
Checking date
Checking file
Checking fs
Checking host
Checking ld
Checking license
Checking network
Checking node
Checking pd
Checking pdch
Checking port
Checking qos
Checking rc
Checking snmp
Checking task
Checking vlun
Checking vv
Checking sp
System is healthy
On the mailbox comes a letter from VSP
Notification from VSP (SP ID: SPxxxxxxxxx) Realtime Alert Process
Notify time: 2018/09/03 04:07:17.850 (+0300 MSK)
Installed machine: 3PAR STORESERV
Event urgency: alert
Severity: Major
Event count: 4
Event time: 2018/09/03 03:25:03.357 (+0300 MSK)
Event description: 3PAR StoreServ IDE File Integrity Check Bad
-----------------------Event Message------------------------
The check for valid files on the internal drive of Node 3 found the following invalid files: /opt/tpd/spn/drive.cfg.
---------------------Corrective Action----------------------
An event occurred that requires attention. Contact your authorized service provider for assistance.
--------------------------Abstract--------------------------
(Major)NODE3 IDE_FILEINTEGRITY_BAD The check for valid files on the internal dri
----------------------------Text----------------------------
Event ID: 1501524 Node 3 Customer Alert - No, Service Alert - Yes
Severity: Major
Event time: Mon Sep 03 03:25:03 2018
Event type: IDE File Integrity Check Bad
Alert ID: null
Msg ID: 1a003c
Component: Node 3
Event string: The check for valid files on the internal drive of Node 3 found the following invalid files: /opt/tpd/spn/drive.cfg.
Notification key: 0x01a003c
Count: 21, up from 17 reported on Sun Sep 02 19:55:46 2018
Thanks for help!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-03-2018 11:12 AM - edited тАО09-03-2018 11:26 AM
тАО09-03-2018 11:12 AM - edited тАО09-03-2018 11:26 AM
Re: 3PAR StoreServ IDE File Integrity Check Bad, after P35
This is a problem with P35 that HPE Support knows about.
You can ignore it until a replacement patch is issued.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-11-2018 09:46 AM - edited тАО09-11-2018 09:46 AM
тАО09-11-2018 09:46 AM - edited тАО09-11-2018 09:46 AM
Re: 3PAR StoreServ IDE File Integrity Check Bad, after P35
P37 came out which replaced P35.
Still the error continues.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-11-2018 08:09 PM
тАО09-11-2018 08:09 PM
Re: 3PAR StoreServ IDE File Integrity Check Bad, after P35
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-30-2018 09:22 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-16-2023 06:24 AM
тАО02-16-2023 06:24 AM
Re: 3PAR StoreServ IDE File Integrity Check Bad, after P35
Same error on HPE 3PAR 8200 array
Current OS 3.3.2 (MU1) with P04,P08
HPE support resolution:
==========================
Ukit(U052) has been released that will recalculate the debsum. Install the same.
Root Cause:
==========================
This message is due to a deprecated Security Key that is now expired and can safely be ignored. They may see a debsum error message in the event logs, and for these files it can be safely ignored.