- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- LVM: vg[0]: pvnum=0 (dev_t=0x1f006000) is POWERFAI...
Operating System - HP-UX
1752799
Members
6244
Online
108789
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
Discussions
Discussions
Forums
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
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
тАО10-27-2004 06:43 PM
тАО10-27-2004 06:43 PM
Hi Forumers!
I've got some serious messages in my systemlog.
Could anybody please advise what to do?
Oct 28 02:00:23 pacmas02 vmunix: SCSI: Unexpected Disconnect -- lbolt: -593051251, dev: 1f006000, io_id: 90a02d
Oct 28 02:00:23 pacmas02 vmunix: SCSI: Target detected parity error -- lbolt: -593051151, dev: 1f006000
Oct 28 02:00:23 pacmas02 vmunix: SCSI: Target detected parity error -- lbolt: -593051019, dev: 1f006000
Oct 28 02:00:23 pacmas02 vmunix: SCSI: Target detected parity error -- lbolt: -593050953, dev: 1f006000
Oct 28 02:00:23 pacmas02 vmunix: SCSI: Target detected parity error -- lbolt: -593050951, dev: 1f006000
Oct 28 02:00:23 pacmas02 vmunix: SCSI: Target detected parity error -- lbolt: -593051151, dev: 1f006000
Oct 28 02:00:37 pacmas02 vmunix: SCSI: Request Timeout; Abort Tag -- lbolt: -593048191, dev: 1f006000, io_id: 90a02c
Oct 28 02:00:43 pacmas02 vmunix: SCSI: Request Timeout; Abort Tag -- lbolt: -593048091, dev: 1f006000, io_id: 90a030
Oct 28 02:00:43 pacmas02 vmunix:
Oct 28 02:00:43 pacmas02 vmunix: SCSI: Write error -- dev: b 31 0x006000, errno: 126, resid: 8192,
Oct 28 02:00:43 pacmas02 vmunix: ^Iblkno: 2487296, sectno: 4974592, offset: -1747976192, bcount: 8192.
Oct 28 02:00:43 pacmas02 vmunix:
Oct 28 02:00:43 pacmas02 vmunix: SCSI: Read error -- dev: b 31 0x006000, errno: 126, resid: 2048,
Oct 28 02:00:43 pacmas02 vmunix: ^Iblkno: 8, sectno: 16, offset: 8192, bcount: 2048.
Oct 28 02:00:43 pacmas02 vmunix: LVM: vg[0]: pvnum=0 (dev_t=0x1f006000) is POWERFAILED
Oct 28 02:00:43 pacmas02 vmunix: LVM: Recovered Path (device 0x1f006000) to PV 0 in VG 0.
Oct 28 02:00:43 pacmas02 vmunix: LVM: Restored PV 0 to VG 0.
Oct 28 02:16:11 pacmas02 vmunix:
Oct 28 02:16:11 pacmas02 vmunix: SCSI: Read error -- dev: b 31 0x006000, errno: 126, resid: 2048,
Oct 28 02:16:11 pacmas02 vmunix: ^Iblkno: 8, sectno: 16, offset: 8192, bcount: 2048.
Oct 28 02:16:11 pacmas02 vmunix: LVM: vg[0]: pvnum=0 (dev_t=0x1f006000) is POWERFAILED
Oct 28 02:16:16 pacmas02 vmunix: LVM: Recovered Path (device 0x1f006000) to PV 0 in VG 0.
Oct 28 02:16:16 pacmas02 vmunix: LVM: Restored PV 0 to VG 0.
Oct 28 02:24:23 cas020 xntpd[11133]: synchronisation lost
Oct 28 02:24:36 cas107 xntpd[1376]: synchronisation lost
Oct 28 02:26:04 pacmas02 vmunix: LVM: Recovered Path (device 0x1f006000) to PV 0 in VG 0.
Oct 28 02:26:09 pacmas02 vmunix: LVM: Restored PV 0 to VG 0.
Oct 28 02:26:09 pacmas02 vmunix:
Oct 28 02:26:09 pacmas02 vmunix: SCSI: Async write error -- dev: b 31 0x006000, errno: 126, resid: 8192,
Oct 28 02:26:09 pacmas02 vmunix: ^Iblkno: 1391648, sectno: 2783296, offset: 1425047552, bcount: 8192.
Oct 28 02:26:09 pacmas02 vmunix: LVM: Recovered Path (device 0x1f006000) to PV 0 in VG 0.
Oct 28 02:26:09 pacmas02 vmunix: LVM: Restored PV 0 to VG 0.
Oct 28 02:26:25 pacmas02 vmunix:
Thanks a lot!
cl
I've got some serious messages in my systemlog.
Could anybody please advise what to do?
Oct 28 02:00:23 pacmas02 vmunix: SCSI: Unexpected Disconnect -- lbolt: -593051251, dev: 1f006000, io_id: 90a02d
Oct 28 02:00:23 pacmas02 vmunix: SCSI: Target detected parity error -- lbolt: -593051151, dev: 1f006000
Oct 28 02:00:23 pacmas02 vmunix: SCSI: Target detected parity error -- lbolt: -593051019, dev: 1f006000
Oct 28 02:00:23 pacmas02 vmunix: SCSI: Target detected parity error -- lbolt: -593050953, dev: 1f006000
Oct 28 02:00:23 pacmas02 vmunix: SCSI: Target detected parity error -- lbolt: -593050951, dev: 1f006000
Oct 28 02:00:23 pacmas02 vmunix: SCSI: Target detected parity error -- lbolt: -593051151, dev: 1f006000
Oct 28 02:00:37 pacmas02 vmunix: SCSI: Request Timeout; Abort Tag -- lbolt: -593048191, dev: 1f006000, io_id: 90a02c
Oct 28 02:00:43 pacmas02 vmunix: SCSI: Request Timeout; Abort Tag -- lbolt: -593048091, dev: 1f006000, io_id: 90a030
Oct 28 02:00:43 pacmas02 vmunix:
Oct 28 02:00:43 pacmas02 vmunix: SCSI: Write error -- dev: b 31 0x006000, errno: 126, resid: 8192,
Oct 28 02:00:43 pacmas02 vmunix: ^Iblkno: 2487296, sectno: 4974592, offset: -1747976192, bcount: 8192.
Oct 28 02:00:43 pacmas02 vmunix:
Oct 28 02:00:43 pacmas02 vmunix: SCSI: Read error -- dev: b 31 0x006000, errno: 126, resid: 2048,
Oct 28 02:00:43 pacmas02 vmunix: ^Iblkno: 8, sectno: 16, offset: 8192, bcount: 2048.
Oct 28 02:00:43 pacmas02 vmunix: LVM: vg[0]: pvnum=0 (dev_t=0x1f006000) is POWERFAILED
Oct 28 02:00:43 pacmas02 vmunix: LVM: Recovered Path (device 0x1f006000) to PV 0 in VG 0.
Oct 28 02:00:43 pacmas02 vmunix: LVM: Restored PV 0 to VG 0.
Oct 28 02:16:11 pacmas02 vmunix:
Oct 28 02:16:11 pacmas02 vmunix: SCSI: Read error -- dev: b 31 0x006000, errno: 126, resid: 2048,
Oct 28 02:16:11 pacmas02 vmunix: ^Iblkno: 8, sectno: 16, offset: 8192, bcount: 2048.
Oct 28 02:16:11 pacmas02 vmunix: LVM: vg[0]: pvnum=0 (dev_t=0x1f006000) is POWERFAILED
Oct 28 02:16:16 pacmas02 vmunix: LVM: Recovered Path (device 0x1f006000) to PV 0 in VG 0.
Oct 28 02:16:16 pacmas02 vmunix: LVM: Restored PV 0 to VG 0.
Oct 28 02:24:23 cas020 xntpd[11133]: synchronisation lost
Oct 28 02:24:36 cas107 xntpd[1376]: synchronisation lost
Oct 28 02:26:04 pacmas02 vmunix: LVM: Recovered Path (device 0x1f006000) to PV 0 in VG 0.
Oct 28 02:26:09 pacmas02 vmunix: LVM: Restored PV 0 to VG 0.
Oct 28 02:26:09 pacmas02 vmunix:
Oct 28 02:26:09 pacmas02 vmunix: SCSI: Async write error -- dev: b 31 0x006000, errno: 126, resid: 8192,
Oct 28 02:26:09 pacmas02 vmunix: ^Iblkno: 1391648, sectno: 2783296, offset: 1425047552, bcount: 8192.
Oct 28 02:26:09 pacmas02 vmunix: LVM: Recovered Path (device 0x1f006000) to PV 0 in VG 0.
Oct 28 02:26:09 pacmas02 vmunix: LVM: Restored PV 0 to VG 0.
Oct 28 02:26:25 pacmas02 vmunix:
Thanks a lot!
cl
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2004 06:50 PM
тАО10-27-2004 06:50 PM
Solution
Hi,
Looks like your c0t6d0 has been having intermittent issues. Do a 'vgdisplay -v' and see if you see any errors. Run 'ioscan -f' and make sure you don't have NO_HW corresponding to the hardware path of c0t6d0. It looks like your root disk with a mirror. If you keep seeing these messages, you will need to have it replaced. To decode the device, use this formula
0x1f006000
1f=major number for sdisk driver.
00=instance number for this controller
6=target
0=LUN
00=ignore for disk device
Or simply do a 'll /dev/dsk |grep 006000'
Another test is to run a dd on it while watching your syslog.log
tail -f syslog.log
dd if=/dev/rdsk/c0t6d0 of=/dev/null bs=1024k (in another window)
-Sri
Looks like your c0t6d0 has been having intermittent issues. Do a 'vgdisplay -v' and see if you see any errors. Run 'ioscan -f' and make sure you don't have NO_HW corresponding to the hardware path of c0t6d0. It looks like your root disk with a mirror. If you keep seeing these messages, you will need to have it replaced. To decode the device, use this formula
0x1f006000
1f=major number for sdisk driver.
00=instance number for this controller
6=target
0=LUN
00=ignore for disk device
Or simply do a 'll /dev/dsk |grep 006000'
Another test is to run a dd on it while watching your syslog.log
tail -f syslog.log
dd if=/dev/rdsk/c0t6d0 of=/dev/null bs=1024k (in another window)
-Sri
You may be disappointed if you fail, but you are doomed if you don't try
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2004 06:53 PM
тАО10-27-2004 06:53 PM
Re: LVM: vg[0]: pvnum=0 (dev_t=0x1f006000) is POWERFAILED ???
Hi,
your disk c0t6d0 may be dead. Check the disk by this command:
# ioscan -fnC disk
and look for the status for the disk in question. If it say NO_HW - and you know for sure that noone has switched off the power for taht particular disk - call HP and have it replaced.
The disk belongs to vg00. Check which logical volume by this command:
# vgdisplay -v /dev/vg00|more
and see where something is stale. I assume that you use mirroring, and the system is still running omn the remaining disk. But I think you should report the error to HP.
regards,
John K.
your disk c0t6d0 may be dead. Check the disk by this command:
# ioscan -fnC disk
and look for the status for the disk in question. If it say NO_HW - and you know for sure that noone has switched off the power for taht particular disk - call HP and have it replaced.
The disk belongs to vg00. Check which logical volume by this command:
# vgdisplay -v /dev/vg00|more
and see where something is stale. I assume that you use mirroring, and the system is still running omn the remaining disk. But I think you should report the error to HP.
regards,
John K.
it would be nice if you always got a second chance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-27-2004 09:55 PM
тАО10-27-2004 09:55 PM
Re: LVM: vg[0]: pvnum=0 (dev_t=0x1f006000) is POWERFAILED ???
Thanks everybody for help!
There are no mirrors. This is just a single rootdisk.
I've done a vgdisplay -v vg00. No errors
lvdisplay -v on all lvols. no stale blocks
ioscan -fnCdisk. Device claimed.
After reboot no error messages appeared. Everythings seems to alright.
Maybe a harbinger to a hdd crash?
There are no mirrors. This is just a single rootdisk.
I've done a vgdisplay -v vg00. No errors
lvdisplay -v on all lvols. no stale blocks
ioscan -fnCdisk. Device claimed.
After reboot no error messages appeared. Everythings seems to alright.
Maybe a harbinger to a hdd crash?
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.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP