PV ID set to none

[john22471]

I have 43P-150. Recently, I encountered a problem with one of my scsi hdisk(internal). I tried to do fsck but it doesn't work. I tried to unmount the volument and export then import it again then do varyonvg but I got an error. I also noticed that the failing hardisk keeps on blinking. I do lspv hdiskx and I found out that the PV ID is set to none. I do chdev -l hdiskx -a pv=yes but it doesnt work.

Is there any way I can recover the data inside this volume?

 

[ogniemi]

"lsdev -Cc disk" shows the disk available or missing?
What says errpt about the disk? Any errors?
The disk was the only member of the VG?
What errors during importvg?

Try remove the disk and configure it again:
rmdev -dl hdiskx
cfgmgr

 

[john22471]

when I do lsdev -Cc hdisk is shows that it is available. I tried to remove it using rmdev -l hdiskx -d and do cfgmgr but still when I do lspv hdisk to check the PVID its set to none.

 

[comtec17]

post your errpt from when you first encountered the issue.

 

[john22471]

Here are part of the error report generated :

#errpt
A6688F553 1208193303 P H Hdisk3 DISK OPERATING ERROR
A6688F553 1208193303 P H Hdisk3 DISK OPERATING ERROR
A6688F553 1208193303 P H Hdisk3 DISK OPERATING ERROR
A6688F553 1208193303 P H Hdisk3 DISK OPERATING ERROR
A6688F553 1208193303 P H Hdisk3 DISK OPERATING ERROR
A6688F553 1208193303 P H Hdisk3 DISK OPERATING ERROR
A6688F553 1208193303 P H Hdisk3 DISK OPERATING ERROR
A6688F553 1208193303 P H Hdisk3 DISK OPERATING ERROR
A6688F553 1208193303 P H Hdisk3 DISK OPERATING ERROR
A6688F553 1208193303 P H Hdisk3 DISK OPERATING ERROR
613EF5F38 1208193203 P H LVDD I/O ERROR DETECTED BY LVM
A6688F553 1208193303 P H Hdisk3 DISK OPERATING ERROR
A39F8A49 1208193203 T S syserrlg Error logging buffer overflow
A6688F553 1208193303 P H Hdisk3 DISK OPERATING ERROR
613E5F38 1208193203 P H LVDD I/O ERROR DETECTED BY LVM
A39F8A49 1208193203 T S syserrlg Error logging buffer overflow
A6688F553 1208193303 P H Hdisk3 DISK OPERATING ERROR
613E5F38 1208193203 P H LVDD I/O ERROR DETECTED BY LVM
A6688F553 1208193303 P H Hdisk3 DISK OPERATING ERROR
613E5F38 1208193203 P H LVDD I/O ERROR DETECTED BY LVM
A6688F553 1208193303 P H Hdisk3 DISK OPERATING ERROR
613E5F38 1208193203 P H LVDD I/O ERROR DETECTED BY LVM

 

[MoshiachNow]

Looks like this disk is "GONE".
I would better replace it.

"Long live king Moshiach !"

http://www.7for70.com/

 

[comtec17]

You hdisk3 looks like it has gone bad. Have you done a vgbackup or mksysb on that VG?

 

[john22471]

No, I havent done any vgbackup? Can I still recover the data on this volume?

What does "syserrlg Error logging buffer overflow" mean??

 

[ogniemi]

I think your disk is to be replaced.

syserrlg buffer overflow means that error event were sent so quickly that not all of them could be logged by errdaemon because of "buffer overflow".

The buffer size can be increased (and it is recommended action linked to the error) but I am sure the error disappeare when you exchange/remove borken disk.

regards, m.

And here is the switch of errdaemon which lets increase the buffer:

-B BufferSize Uses the number of bytes specified by the BufferSize parameter for the error log device driver's in-memory buffer. The specified buffer size is saved in the error log configuration database. If the BufferSize parameter is larger than the buffer size currently in use, the in-memory buffer is immediately increased. If the BufferSize parameter is smaller than the buffer size currently in use, the new size is put into effect the next time the error logging daemon is started after the system is rebooted. The buffer cannot be made smaller than the hard-coded default of 8KB.
If this parameter is not specified, the error logging daemon uses the buffer size from the error log configuration database.

The size you specify is rounded up to the next integral multiple of the memory page size (4KB). The memory used for the error log device driver's in-memory buffer is not available for use by other processes. (The buffer is pinned). Be careful not to impact your system's performance by making the buffer excessively large. On the other hand, if you make the buffer too small, the buffer can become full if error entries arrive faster than they can be read from the buffer and put into the log file. When the buffer is full, new entries are discarded until space becomes available in the buffer. When this situation occurs, the error logging daemon creates an error log entry to inform you of the problem. You can correct the problem by enlarging the buffer.

 

[john22471]

Hi,

Thanks for the info. I believed the disk already gone. I had it replaced and its ok.

Regards,

JQ

 

[bi]

Just a couple of suggestions for the future:

start doing regular backups so if you have a disk failure, you can recover most, if not all, of the data on the disk.

if you have the disk space, start mirroring your logical volumes. That way, if one disk fails, you will still have the data on another disk.

Also, if you want to be warned by email when there is a new error logged in errpt, check out FAQ faq52-2445.

 

[john22471]

Thanks and Best Regards,

JQ

 

[john22471]

Hi Bi,

I have some little question regarding the email notification as what you have published.

The question is where to send the email. How to set it up??? I am interested about this scripts...

Thanks and best Regards,

JQ