- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: bad internal drive??
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-2011 03:56 PM
тАО01-28-2011 03:56 PM
bad internal drive??
I've been watching syslog for any clues and finally had the info below pop up. Could this mean a struggling internal disk? I have 2 internal disks, are they probably mirrored or probably not mirrored? If one of the drives does need to be replaced, what impact would that have on the system? I do have an active HP support agreement but I'm trying to get an idea what I should be prepared for when I call. I already made an ignite tape, what else should I do before I call?
Here is the entry from syslog and the results of the command it lists:
Jan 28 13:08:09 PRODUX EMS [3949]: ------ EMS Event Notification ------ Value:
"CRITICAL (5)" for Resource: "/storage/events/disks/default/1_0_0_3_0.6.0"
(Threshold: >= " 3") Execute the following command to obtain event details:
/opt/resmon/bin/resdata -R 258801666 -r /storage/events/disks/default/1_0_0_3_
0.6.0 -n 258801665 -a
CURRENT MONITOR DATA:
Event Time..........: Fri Jan 28 13:08:09 2011
Severity............: CRITICAL
Monitor.............: disk_em
Event #.............: 3
System..............: PRODUX.HPM.local
Summary:
Disk at hardware path 1/0/0/3/0.6.0 : Drive is not responding.
Description of Error:
As part of the polling functionality, the monitor periodically requests
data from the device. The monitor's request of Test Unit Ready command
failed.
Probable Cause / Recommended Action:
The I/O request that the monitor made to this device failed because the
device timed-out. Check cables, power supply, ensure the drive is powered
ON, and if needed contact your HP support representative.
Additional Event Data:
System IP Address...: deleted Event Id............: 0x4d43060900000000
Monitor Version.....: B.01.01
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_disk_em.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
None
Additional System Data:
System Model Number.............: 9000/800/rp7420
OS Version......................: B.11.11
STM Version.....................: A.47.00
EMS Version.....................: A.04.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/disk_em.htm#3
v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v
Component Data:
Physical Device Path...: 1/0/0/3/0.6.0
Device Class...........: Disk
Inquiry Vendor ID......: HP 73.4G
Inquiry Product ID.....: ST373453LC
Firmware Version.......: HPC5
Serial Number..........: 3HW2WH210000753292A7
Product/Device Identification Information:
Logger ID.........: disc30; sdisk
Product Identifier: Disk
Product Qualifier.: HP 73.4GST373453LC
SCSI Target ID....: 0x06
SCSI LUN..........: 0x00
SCSI Command Data Block: (not present in log record)
Hardware Status: (not present in log record).
SCSI Sense Data: (not present in log record)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2011 12:49 AM
тАО01-29-2011 12:49 AM
Re: bad internal drive??
run dd if=/dev/rdsk/cxtxdx of=/dev/null bs=1024
count=100
try increasing the count to a higher value if commands succeeds , other wise it fails with error.
Paste the dd output.
Thanks
Manix
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-29-2011 04:28 PM
тАО01-29-2011 04:28 PM
Re: bad internal drive??
It seems that you have EMS running but you haven't been getting the error messages by email. Check root's email -- it is probably huge with all the failure messages. Make sure all your systems have root's email aliased to your sysadmin email address so everyone will see the problems sooner.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2011 07:38 AM
тАО01-31-2011 07:38 AM
Re: bad internal drive??
[PRODUX]:/home/root ->dd if=/dev/rdsk/c1t6d0 of=/dev/null bs=1024 count=100
100+0 records in
100+0 records out
[PRODUX]:/home/root ->dd if=/dev/rdsk/c1t6d0 of=/dev/null bs=1024 count=500
500+0 records in
500+0 records out
[PRODUX]:/home/root ->dd if=/dev/rdsk/c1t6d0 of=/dev/null bs=1024 count=1000
1000+0 records in
1000+0 records out
[PRODUX]:/home/root ->dd if=/dev/rdsk/c1t6d0 of=/dev/null bs=1024 count=10000
10000+0 records in
10000+0 records out
[PRODUX]:/home/root ->
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2011 07:56 AM
тАО01-31-2011 07:56 AM
Re: bad internal drive??
HP recommends; Check cables, power supply, ensure the drive is powered ON, and if needed replace the drive.
you can try this also:
# echo 2400?20X | adb /dev/dsk/cxtydz
to see if there is nonzero counts , except first two counts.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2011 08:00 AM
тАО01-31-2011 08:00 AM
Re: bad internal drive??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2011 08:06 AM
тАО01-31-2011 08:06 AM
Re: bad internal drive??
and check no of disks used by lvols over there.
Then do lvdisplay -v lvolname | more to see if they are mapped over two disks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2011 08:06 AM
тАО01-31-2011 08:06 AM
Re: bad internal drive??
[PRODUX]:/home/root ->echo 2400?20X | adb /dev/dsk/c1t6d0
2400: 44454645 43543031 0 0
0 0 0 0
0 0 0 0
0 0 0 0
0 0 0 0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2011 08:11 AM
тАО01-31-2011 08:11 AM
Re: bad internal drive??
If this is your boot disk,you can check if it is mirrorred using.
#lvlnboot -v
Rgds
Bijeesh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-31-2011 08:12 AM
тАО01-31-2011 08:12 AM
Re: bad internal drive??
[PRODUX]:/home/root ->vgdisplay -v /dev/vg00
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 7
Open LV 7
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 4384
VGDA 4
PE Size (Mbytes) 16
Total PE 8748
Alloc PE 7528
Free PE 1220
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 304
Current LE 19
Allocated PE 38
Used PV 2
LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 256
Allocated PE 512
Used PV 2
LV Name /dev/vg00/lvol3
LV Status available/syncd
LV Size (Mbytes) 512
Current LE 32
Allocated PE 64
Used PV 2
LV Name /dev/vg00/lvol4
LV Status available/syncd
LV Size (Mbytes) 30000
Current LE 1875
Allocated PE 3750
Used PV 2
LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 12000
Current LE 750
Allocated PE 1500
Used PV 2
LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 4400
Current LE 275
Allocated PE 550
Used PV 2
LV Name /dev/vg00/lvol8
LV Status available/syncd
LV Size (Mbytes) 8912
Current LE 557
Allocated PE 1114
Used PV 2
--- Physical volumes ---
PV Name /dev/dsk/c1t6d0
PV Status available
Total PE 4374
Free PE 610
Autoswitch On
Proactive Polling On
PV Name /dev/dsk/c4t6d0
PV Status available
Total PE 4374
Free PE 610
Autoswitch On
Proactive Polling On
[PRODUX]:/home/root ->lvdisplay -v /dev/vg00/lvol1 | more
--- Logical volumes ---
LV Name /dev/vg00/lvol1
VG Name /dev/vg00
LV Permission read/write
LV Status available/syncd
Mirror copies 1
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 304
Current LE 19
Allocated PE 38
Stripes 0
Stripe Size (Kbytes) 0
Bad block off
Allocation strict/contiguous
IO Timeout (Seconds) default
--- Distribution of logical volume ---
PV Name LE on PV PE on PV
/dev/dsk/c1t6d0 19 19
/dev/dsk/c4t6d0 19 19
--- Logical extents ---
LE PV1 PE1 Status 1 PV2 PE2 Status 2
00000 /dev/dsk/c1t6d0 00000 current /dev/dsk/c4t6d0 00000 current
00001 /dev/dsk/c1t6d0 00001 current /dev/dsk/c4t6d0 00001 current
00002 /dev/dsk/c1t6d0 00002 current /dev/dsk/c4t6d0 00002 current
00003 /dev/dsk/c1t6d0 00003 current /dev/dsk/c4t6d0 00003 current
00004 /dev/dsk/c1t6d0 00004 current /dev/dsk/c4t6d0 00004 current
00005 /dev/dsk/c1t6d0 00005 current /dev/dsk/c4t6d0 00005 current
00006 /dev/dsk/c1t6d0 00006 current /dev/dsk/c4t6d0 00006 current
00007 /dev/dsk/c1t6d0 00007 current /dev/dsk/c4t6d0 00007 current
00008 /dev/dsk/c1t6d0 00008 current /dev/dsk/c4t6d0 00008 current
00009 /dev/dsk/c1t6d0 00009 current /dev/dsk/c4t6d0 00009 current
00010 /dev/dsk/c1t6d0 00010 current /dev/dsk/c4t6d0 00010 current
00011 /dev/dsk/c1t6d0 00011 current /dev/dsk/c4t6d0 00011 current
00012 /dev/dsk/c1t6d0 00012 current /dev/dsk/c4t6d0 00012 current
00013 /dev/dsk/c1t6d0 00013 current /dev/dsk/c4t6d0 00013 current
00014 /dev/dsk/c1t6d0 00014 current /dev/dsk/c4t6d0 00014 current
00015 /dev/dsk/c1t6d0 00015 current /dev/dsk/c4t6d0 00015 current
00016 /dev/dsk/c1t6d0 00016 current /dev/dsk/c4t6d0 00016 current
00017 /dev/dsk/c1t6d0 00017 current /dev/dsk/c4t6d0 00017 current
00018 /dev/dsk/c1t6d0 00018 current /dev/dsk/c4t6d0 00018 current
[PRODUX]:/home/root ->