- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- SCSI: Async write error
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
06-16-2004 01:34 PM
06-16-2004 01:34 PM
SCSI: Async write error
Jun 3 02:20:05 enaladm vmunix: LVM: vg[2]: pvnum=0 (dev_t=0x1f060200) is POWERFAILED
Jun 3 02:20:05 enaladm vmunix: LVM: Path (device 0x1f070400) to PV 0 in VG 4 Failed!
Jun 3 02:20:05 enaladm vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004c0c7040), from raw device 0x1f070400 (with priority: 0, and current flags: 0x40) to raw device 0x1f060400 (with priority: 1, and current flags: 0x0).
Jun 3 02:20:05 enaladm vmunix: LVM: vg[4]: pvnum=0 (dev_t=0x1f060400) is POWERFAILED
Jun 3 02:20:06 enaladm EMS [2502]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/1_0_2_0_0.8.0.0.0.0.2" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 163971086 -r /storage/events/disks/default/1_0_2_0_0.8.0.0.0.0.2 -n 163971126 -a
Jun 3 02:20:06 enaladm EMS [2502]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/1_0_2_0_0.8.0.0.0.0.4" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 163971092 -r /storage/events/disks/default/1_0_2_0_0.8.0.0.0.0.4 -n 163971127 -a
Jun 3 02:20:10 enaladm vmunix: LVM: Recovered Path (device 0x1f060100) to PV 0 in VG 1.
Jun 3 02:20:10 enaladm vmunix: LVM: Recovered Path (device 0x1f060300) to PV 0 in VG 3.
Jun 3 02:20:10 enaladm vmunix: LVM: Restored PV 0 to VG 1.
Jun 3 02:20:11 enaladm EMS [2502]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/1_0_2_0_0.8.0.0.0.0.2" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 163971086 -r /storage/events/disks/default/1_0_2_0_0.8.0.0.0.0.2 -n 163971128 -a
Jun 3 02:20:11 enaladm vmunix: LVM: Restored PV 0 to VG 3.
Jun 3 02:20:11 enaladm EMS [2502]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/storage/events/disks/default/1_0_2_0_0.8.0.0.0.0.4" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 163971092 -r /storage/events/disks/default/1_0_2_0_0.8.0.0.0.0.4 -n 163971129 -a
Jun 3 02:21:11 enaladm vmunix: LVM: Recovered Path (device 0x1f070300) to PV 0 in VG 3.
Jun 3 02:21:11 enaladm vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004c34e040), from raw device 0x1f060300 (with priority: 1, and current flags: 0x0) to raw device 0x1f070300 (with priority: 0, and current flags: 0x80).
Jun 3 02:21:11 enaladm vmunix: LVM: Recovered Path (device 0x1f070400) to PV 0 in VG 4.
Jun 3 02:21:11 enaladm vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004c0c7040), from raw device 0x1f060400 (with priority: 1, and current flags: 0x0) to raw device 0x1f070400 (with priority: 0, and current flags: 0x80).
Jun 3 02:21:11 enaladm vmunix: LVM: Recovered Path (device 0x1f070200) to PV 0 in VG 2.
Jun 3 02:21:11 enaladm vmunix: LVM: Recovered Path (device 0x1f070100) to PV 0 in VG 1.
Jun 3 02:21:11 enaladm vmunix: LVM: Performed a switch for Lun ID = 0 (pv = 0x000000004c04d080), from raw device 0x1f060100 (with priority: 1, and current flags: 0x0) to raw device 0x1f070100 (with priority: 0, and current flags: 0x80).
on )
.......
....
SCSI: Async write error -- dev: b 31 0x070300, errno: 126, resid: 1024,
Jun 3 14:16:41 enaladm vmunix: blkno: 110102823, sectno: 220205646, offset: 1076141056, bcount: 1024.
Jun 3 14:16:41 enaladm vmunix: SCSI: Async write error -- dev: b 31 0x070300, errno: 126, resid: 8192,
Jun 3 14:16:41 enaladm vmunix: blkno: 110103848, sectno: 220207696, offset: 1077190656, bcount: 8192.
Jun 3 14:16:41 enaladm vmunix: blkno: 108793784, sectno: 217587568, offset: -264314880, bcount: 8192.
Jun 3 14:16:41 enaladm vmunix: blkno: 108813288, sectno: 217626576, offset: -244342784, bcount: 8192.
Jun 3 14:16:41 enaladm vmunix: blkno: 108763816, sectno: 217527632, offset: -295002112, bcount: 8192.
Jun 3 14:16:41 enaladm vmunix: blkno: 108788776, sectno: 217577552, offset: -269443072, bcount: 8192.
Jun 3 14:16:41 enaladm vmunix: blkno: 108676488, sectno: 217352976, offset: -384425984, bcount: 8192.
Jun 3 14:16:41 enaladm vmunix: blkno: 108499824, sectno: 216999648, offset: -565329920, bcount: 8192.
=======================================
please..help me..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2004 01:44 PM
06-16-2004 01:44 PM
Re: SCSI: Async write error
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2004 01:48 PM
06-16-2004 01:48 PM
Re: SCSI: Async write error
Your disks powerfailed and recovered. Its probably a good idea to restart your system and figure out why your disks powerfailed and recovered.
Powerfail warning also occurs if scsi connectivity is lost say to your fiber/fabric network.
Again, you should be able to recover your database and whatever files were on the logical volumes.
Some additional symptoms would be helpful, but a reboot should clear the messages.
Do figure out why it happened and take corrective actions.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-16-2004 01:51 PM
06-16-2004 01:51 PM
Re: SCSI: Async write error
Looks like there is an issue with either the storage system or the adapter. First thing you need to do is to run
ioscan -f > /tmp/ioscan.out
Look at the file to see if any NO_HW entries appear for the disks.
Find out the disks that got affected. Cut off 0x1f from the device id in the POWERFAILED messages and grep from /dev/dsk output. For ex.,
Jun 3 02:20:05 enaladm vmunix: LVM: vg[2]: pvnum=0 (dev_t=0x1f060200) is POWERFAILED
ll /dev/dsk |grep 060200
Run 'vgdisplay -v |grep unavailable' and see if there are any PVs that are in unavailable state.
If everything is looking good, do
vgchange -a y vgxx
for each Volume group to refresh the VGs.
-Sri
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-17-2004 04:02 PM
06-17-2004 04:02 PM
Re: SCSI: Async write error
In this case first you have restart the m/c.then
# ioscan -fnC disk
hard disks are finding go ahead for further check.
# vgscan -a
this will find all pysical volumes , lv also
now this will crate or update the /etc/lvmtab file.
#vgimport -v /dev/vgxx /dev/dsk/cxtxdx
it will import your exisiting lv from hardisk.
# vgchange -a y /dev/vgxx for activate.
it 'll do for you .
with cheers,
shankar