- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- LVM: vg[18]: pvnum=7 (dev_t=0x1f190700) is POWERFA...
-
- Forums
-
Blogs
- Alliances
- Around the Storage Block
- Behind the scenes @ Labs
- HPE Careers
- HPE Storage Tech Insiders
- Infrastructure Insights
- Inspiring Progress
- Internet of Things (IoT)
- My Learning Certification
- OEM Solutions
- Servers: The Right Compute
- Shifting to Software-Defined
- Telecom IQ
- Transforming IT
- Infrastructure Solutions German
- L’Avenir de l’IT
- IT e Trasformazione Digitale
- Enterprise Topics
- ИТ для нового стиля бизнеса
- Blogs
-
Quick Links
- Community
- Getting Started
- FAQ
- Ranking Overview
- Rules of Participation
- Contact
- Email us
- Tell us what you think
- Information Libraries
- Integrated Systems
- Networking
- Servers
- Storage
- Other HPE Sites
- Support Center
- Enterprise.nxt
- Marketplace
- Aruba Airheads Community
-
Forums
-
Blogs
-
InformationEnglish
- 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
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-04-2003 01:34 AM
11-04-2003 01:34 AM
How can I interpret this message, there is nothing wrong on the server? Please reply..
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-04-2003 02:05 AM
11-04-2003 02:05 AM
Solution1f hex = 31 dec
31 = major# of sdisk driver (lsdev 31)
so we know it is a disk...
19 = c19
0 = t0
7 = d7
c19t0d7 is the device... it's recommended to increase the io timeout for disks in an array to 180.
pvdisplay /dev/dsk/c19t0d7
IO Timeout = default
pvchange -t 180 /dev/dsk/c19t0d7
Where there any "SCSI" errors leading upto the LVM POWERFAILED message?
-Denver
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-04-2003 02:19 AM
11-04-2003 02:19 AM
Re: LVM: vg[18]: pvnum=7 (dev_t=0x1f190700) is POWERFAILED
Best answer I received...
Thanks
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-04-2003 06:36 AM
11-04-2003 06:36 AM
Re: LVM: vg[18]: pvnum=7 (dev_t=0x1f190700) is POWERFAILED
The way you mentioned is not the case, however I am seeing that,
$ ls -altrR *dsk*|grep -i 190700
brw-r----- 1 bin sys 31 0x190700 Oct 4 01:15 c25t0d7
crw-r----- 1 bin sys 188 0x190700 Oct 4 01:15 c25t0d7
While C19t0d7 is an other device:
$ls -altrR *dsk*|grep -i c19t0d7
brw-r----- 1 bin sys 31 0x130700 Sep 15 17:21 c19t0d7
crw-r----- 1 bin sys 188 0x130700 Sep 16 16:11 c19t0d7
I am having XP array attached to system, and c19t0d7 & c25t0d7, are alternate device links.
$/usr/sbin/pvdisplay /dev/dsk/c25t0d7
PV Name /dev/dsk/c25t0d7
PV Name /dev/dsk/c19t0d7 Alternate Link
Is there any way of knowing, which path it is giving error for....Or how to know like one of the path has failed...
Please reply..
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-04-2003 08:44 AM
11-04-2003 08:44 AM
Re: LVM: vg[18]: pvnum=7 (dev_t=0x1f190700) is POWERFAILED
Denver was essentially correct, he just forgot to do the hex to decimal conversion for the 19.
19 hex = 25 decimal.
So the correct device path is c25t0d7.
I would look at the PV timeout that Denver recommended first.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-05-2003 12:58 AM
11-05-2003 12:58 AM
Re: LVM: vg[18]: pvnum=7 (dev_t=0x1f190700) is POWERFAILED
thanks to patrick for pointing out my math prob.
-Denver
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
11-05-2003 08:04 PM
11-05-2003 08:04 PM
Re: LVM: vg[18]: pvnum=7 (dev_t=0x1f190700) is POWERFAILED
Just an afterthought.
Instead of math how about just doing.
ll /dev/* | grep 190700
It should come back with character and block device files -- something like this -
"Assuming they were not removed" :)
brw-r----- 1 bin sys 31 0x190700 Oct 27 19:33 c25t0d7
crw-r----- 1 bin sys 188 0x190700 Oct 27 19:33 c25t0d7
Nicest thing about that is it works on any
device file that might be mentioned in
syslog.
Regards,
dbk.
Hewlett Packard Enterprise International
- Communities
- HPE Blogs and Forum
© Copyright 2019 Hewlett Packard Enterprise Development LP