- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: Serious problem with VA7400
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
тАО01-28-2002 09:50 AM
тАО01-28-2002 09:50 AM
Two times, during restore of 50-70 GB of data from an Ultrium tape to VA7400 disks, machine hung and I needed to hit power button!
OLDsyslog.log is full of these messages:
Jan 28 18:43:45 prod1 vmunix: SCSI: Async write error -- dev: b 31 0x110500, errno: 126, resid: 32768,
Jan 28 18:43:45 prod1 vmunix: blkno: 72993600, sectno: 145987200, offset: 1731002368, bcount: 32768.
Jan 28 18:43:46 prod1 vmunix: SCSI: Async write error -- dev: b 31 0x110500, errno: 126, resid: 24576,
Jan 28 18:43:46 prod1 vmunix: blkno: 72993536, sectno: 1...
Jan 28 18:43:46 prod1 vmunix: LVM: Recovered Path (device 0x1f110500) to PV 0 in VG 5.
Jan 28 18:43:46 prod1 vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x0000000042b7a800), from raw device 0x1f130500 (with priority: 1, and current flags: 0x40) to raw device 0x1f110500 (with priority: 0, and current flags: 0x0).
Jan 28 18:43:46 prod1 vmunix:
Jan 28 18:43:46 prod1 above message repeats 221 times
Jan 28 18:43:46 prod1 vmunix: LVM: vg[5]: pvnum=0 (dev_t=0x1f110500) is POWERFAILED
Jan 28 18:43:46 prod1 vmunix: LVM: Restored PV 0 to VG 5.
Jan 28 18:43:46 prod1 vmunix: LVM: Recovered Path (device 0x1f130500) to PV 0 in VG 5.
Last week, a LUN from the same array disappeared.
It seems a serious issue.
I'm waiting for HP support but I'd like to hear a suggestion form you.
Thanks in advance
Domenico Viggiani
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2002 10:28 AM
тАО01-29-2002 10:28 AM
Re: Serious problem with VA7400
LVM: vg[5]: pvnum=0 (dev_t=0x1f110500) is POWERFAILED
it shows that the device on c10t5d0 is giving you the problem. If you run an # ioscan -fnkC disk you should see what physical device it is referring to. You could post the results from ioscan if you like.
-Bob
Was this helpful? Like this post by giving me a thumbs up below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-30-2002 01:31 AM
тАО01-30-2002 01:31 AM
Re: Serious problem with VA7400
c10t5d0 is a DLT drive and it is unrelated to this problem. I think.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-30-2002 03:50 PM
тАО01-30-2002 03:50 PM
Re: Serious problem with VA7400
1f11050
1f coverted to dec. = 31 which is major # for sdisk.
11 = bus #
0 = target #
5 = LUN
so...c11t0d5. Does that make more sense??
-Bob
Was this helpful? Like this post by giving me a thumbs up below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2002 12:25 AM
тАО01-31-2002 12:25 AM
Re: Serious problem with VA7400
Thanks anyway.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2002 04:00 AM
тАО01-31-2002 04:00 AM
Solutionwe had similar problems.
During Backup the VA hanged up and also with the armdsp command we did receive die VA7400. We needed to remove one controller from the va and put it back into.
HP support presented us a workaround which was definining the Resilency Mode "HighPerformance" for the VA. But it solved not really the problem. The solution was to make an FirmwareUpgrade of the VA to HP14.
But we were told that with the next fw version are again some performance issues. So we will also install this fw.
But with HP14 and "HighPerformance" mode the VA runs ok.
Please take care of the reduced data protection you have with "highPerformance" mode.
Regards
Stephan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2002 10:39 AM
тАО01-31-2002 10:39 AM
Re: Serious problem with VA7400
Array log is filled with following messages (since days of problems):
FRU Location = M/C1.H1
Event Number ---------------- = 17,602
Sequence Number ------------- = 1,269
Time ------------------------ = Jan 31, 2002 7:35 PM
Device Name ----------------- = HP SureStore Virtual Array 7400
Device Unique Name ---------- = 50060b000008aa33
Device Type ----------------- = DiskArray
Event Code ------------------ = 348
Event Description = FRONTEND_FC_ABTS_EVENT_EH This error code indicates that the Host sent
a Fibre Channel ABTS (Abort Sequence) BLS frame to the abort an IO. The array will log thi
s event for informational and debug purposes only. It does not necessarily indicate a prob
lem with the array.
Event Unique Data :
Ckpt 0x470097: 0x00000004
frontend: osIOCompleted: osIOAbortABTS
NPortID=0x011000,OX_ID=0x00fe,LUN=0x4001
CDB=0x2a000566e6a000001000000000000000
ElapsedTime=31.1 ioHWM=0x0023 jstate=0x05
controller tick : 1492421663479
serialNum/moduleId/processId : 00PR0301V566/0x47/0xffffffff
enclosureId/slot : 0x00/0x00
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-20-2002 02:43 AM
тАО02-20-2002 02:43 AM
Re: Serious problem with VA7400
the dev_t is hexadecimal all over.
So the 11 would also need to be converted to decimal, in this case would be c17t0d5.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-21-2002 12:44 AM
тАО02-21-2002 12:44 AM
Re: Serious problem with VA7400
Thanks to all
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-19-2005 12:24 AM
тАО05-19-2005 12:24 AM
Re: Serious problem with VA7400
We have a same problem with VA7410. We also face lun switch problem in our servers. Can you tell me in detail how this problem was resolved and exactly which setting resolved this issue.
Regards