Author: Emerson .

LVM – Disk removed and appears message read failed after 0 of 4096 at 4096 or similar

In this server when I ran pvs it was showing a lot of input/output errors

root@linux:~ # pvs
/dev/sdq: read failed after 0 of 4096 at 0: Input/output error
/dev/sdq1: read failed after 0 of 2048 at 0: Input/output error
/dev/mpath/disk2: read failed after 0 of 4096 at 80530571264: Input/output error
/dev/mpath/disk2: read failed after 0 of 4096 at 80530628608: Input/output error
/dev/mpath/disk2: read failed after 0 of 4096 at 0: Input/output error
/dev/mpath/disk2: read failed after 0 of 4096 at 4096: Input/output error
/dev/mpath/disk2p1: read failed after 0 of 512 at 80525328384: Input/output error
/dev/mpath/disk2p1: read failed after 0 of 512 at 80525447168: Input/output error
/dev/mpath/disk2p1: read failed after 0 of 512 at 0: Input/output error
/dev/mpath/disk2p1: read failed after 0 of 512 at 4096: Input/output error
/dev/mpath/disk2p1: read failed after 0 of 2048 at 0: Input/output error
/dev/devvg/u01lv: read failed after 0 of 4096 at 21474770944: Input/output error
/dev/devvg/u01lv: read failed after 0 of 4096 at 21474828288: Input/output error
/dev/devvg/u01lv: read failed after 0 of 4096 at 0: Input/output error
/dev/devvg/u01lv: read failed after 0 of 4096 at 4096: Input/output error
/dev/sde: read failed after 0 of 4096 at 0: Input/output error
/dev/sde1: read failed after 0 of 2048 at 0: Input/output error
/dev/sdw: read failed after 0 of 4096 at 0: Input/output error
/dev/sdw1: read failed after 0 of 2048 at 0: Input/output error
/dev/sdk: read failed after 0 of 4096 at 0: Input/output error

A disk was removed and it was not removed cleanly

root@linux:~ # multipath -ll disk2
sde: checker msg is “tur checker reports path is down”
sdk: checker msg is “tur checker reports path is down”
sdq: checker msg is “tur checker reports path is down”
sdw: checker msg is “tur checker reports path is down”
disk2 (360000000000000000000000000000000) dm-25 HP,P2000 G3 FC
[size=75G][features=0][hwhandler=0][rw]
\_ round-robin 0 [prio=0][enabled]
\_ 1:0:0:5 sde 8:64 [failed][faulty]
\_ 1:0:1:5 sdk 8:160 [failed][faulty]
\_ 2:0:0:5 sdq 65:0 [failed][faulty]
\_ 2:0:1:5 sdw 65:96 [failed][faulty]

Removed the block devices

root@linux:~ # echo 1 > /sys/block/sde/device/delete
root@linux:~ # echo 1 > /sys/block/sdk/device/delete
root@linux:~ # echo 1 > /sys/block/sdq/device/delete
root@linux:~ # echo 1 > /sys/block/sdw/device/delete

I was able to remove the device that device-mapper used but I was not able to remove the device with the partition

root@linux:~ # dmsetup remove disk2
root@linux:~ # dmsetup remove disk2p1
device-mapper: remove ioctl failed: Device or resource busy
Command failed

I had a filesystem using the device /dev/devvg/u01lv so I had to remove it before I was able to remove the device with the partition

root@linux:~ # dmsetup remove devvg-u01lv

root@linux:~ # dmsetup remove disk2p1

The legacy lun path (b 32 – t 13 – l 0) registration failed because it has been re-mapped from its original LUN (default dev 0xb000018) to a different LUN (default dev 0xc0000bd).

Checking /var/adm/syslog/syslog.log I see that lunpath, instance 81 is showing an error message

root@hp-ux:~ # grep vmunix /var/adm/syslog/syslog.log | grep “Nov 9”
Nov 9 04:37:14 hp-ux vmunix: class : lunpath, instance 81
Nov 9 04:37:14 hp-ux vmunix: The legacy lun path (b 32 – t 13 – l 0)
Nov 9 04:37:14 hp-ux vmunix: registration failed because it has been
Nov 9 04:37:14 hp-ux vmunix: re-mapped from its original LUN (default dev 0xb000018)
Nov 9 04:37:14 hp-ux vmunix: to a different LUN (default dev 0xc0000bd).
Nov 9 04:37:14 hp-ux vmunix: The administrator has to close the original LUN and
Nov 9 04:37:14 hp-ux vmunix: then validate this LUN re-mapping using the scsimgr
Nov 9 04:37:14 hp-ux vmunix: command:
Nov 9 04:37:14 hp-ux vmunix: scsimgr [-f] replace_leg_dsf -D /dev/rdsk/cxtydz

(b 32 – t 13 – l 0)
scsimgr [-f] replace_leg_dsf -D /dev/rdsk/c32t13d0

Let’s discover the hardware path for this instance

root@hp-ux:~ # scsimgr -p get_attr -C lunpath -I 81 -a hw_path
0/2/0/0/0/1.0x5001438017928fe6.0x0

Pick the LUN H/W Path

root@hp-ux:~ # ioscan -m hwpath -H 0/2/0/0/0/1.0x5001438017928fe6.0x0
Lun H/W Path Lunpath H/W Path Legacy H/W Path
====================================================================
64000/0xfa00/0xbd
0/2/0/0/0/1.0x5001438017928fe6.0x0

And run the following command

root@hp-ux:~ # scsimgr -f replace_wwid -H 64000/0xfa00/0xbd
scsimgr: Successfully validated binding of LUN paths with new LUN.

In another case, there was a missing disk. I removed the disk

root@hp-ux:~ # ioscan -fnNC disk
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
disk 2 64000/0xfa00/0x0 esdisk CLAIMED DEVICE HP EH0146FARUB
/dev/disk/disk2 /dev/rdisk/disk2
/dev/disk/disk2_p1 /dev/rdisk/disk2_p1
/dev/disk/disk2_p2 /dev/rdisk/disk2_p2
/dev/disk/disk2_p3 /dev/rdisk/disk2_p3
disk 3 64000/0xfa00/0x1 esdisk CLAIMED DEVICE HP EH0146FARUB
/dev/disk/disk3 /dev/rdisk/disk3
/dev/disk/disk3_p1 /dev/rdisk/disk3_p1
/dev/disk/disk3_p2 /dev/rdisk/disk3_p2
/dev/disk/disk3_p3 /dev/rdisk/disk3_p3
disk 5 64000/0xfa00/0x2 esdisk CLAIMED DEVICE TEAC DVD-ROM DW-224EV
/dev/disk/disk5 /dev/rdisk/disk5
disk 14 64000/0xfa00/0xa esdisk CLAIMED DEVICE HP HSV340
/dev/disk/disk14 /dev/rdisk/disk14
disk 19 64000/0xfa00/0x46 esdisk NO_HW DEVICE NETAPP LUN C-Mode
/dev/disk/disk19 /dev/rdisk/disk19

root@hp-ux:~ # rmsf -H 64000/0xfa00/0x46

DMESG-UNCLASSIFIED: to probe existing LUN id 0x0 failed with errno of 6.

Node : hp-ux.setaoffice.com
Node Type : Itanium 64/32(HTTPS)
Severity : major
OM Server Time: 2015-11-06 10:30:53
Message : DMESG-UNCLASSIFIED: to probe existing LUN id 0x0 failed with errno of 6.
Msg Group : OS
Application : HPUX_dmesg
Object : dmesg_UNCLASSIFIED
Event Type :
not_found

Instance Name :
not_found

Instruction : No

Message showing in dmesg and /var/adm/syslog/syslog.log

root@hp-ux:/root # dmesg | grep probe
An attempt to probe existing LUN id 0x0 failed with errno of 22.
An attempt to probe existing LUN id 0x0 failed with errno of 22.

root@hp-ux:/root # grep probe /var/adm/syslog/syslog.log | tail
Nov 4 16:08:31 vlunx012 vmunix: An attempt to probe existing LUN id 0x0 failed with errno of 6.
Nov 4 16:08:31 vlunx012 vmunix: An attempt to probe existing LUN id 0x0 failed with errno of 6.
Nov 4 16:08:33 vlunx012 vmunix: An attempt to probe existing LUN id 0x0 failed with errno of 22.

Scanning the hardware and it is shown that some tapes are in NO_HW status. Removed these tapes

root@hp-ux:/root # ioscan -fnkNC lunpath | grep NO_HW
lunpath 139 0/0/4/0.0xb.0x0 eslpt NO_HW LUN_PATH LUN path for tape95
lunpath 147 0/0/4/0.0×19.0x0 eslpt NO_HW LUN_PATH LUN path for tape99
lunpath 141 0/0/4/0.0x1a.0x0 eslpt NO_HW LUN_PATH LUN path for tape96
lunpath 144 0/0/4/0.0x1c.0x0 eslpt NO_HW LUN_PATH LUN path for tape97
lunpath 155 0/0/4/0.0x1d.0x0 eslpt NO_HW LUN_PATH LUN path for tape115
lunpath 150 0/0/4/0.0x1e.0x0 eslpt NO_HW LUN_PATH LUN path for tape47
lunpath 157 0/0/4/0.0×24.0x0 eslpt NO_HW LUN_PATH LUN path for tape98
lunpath 408 0/0/6/0.0×26.0x0 eslpt NO_HW LUN_PATH LUN path for tape199
lunpath 410 0/0/6/0.0×27.0x0 eslpt NO_HW LUN_PATH LUN path for tape203
lunpath 412 0/0/6/0.0×28.0x0 eslpt NO_HW LUN_PATH LUN path for tape200
lunpath 415 0/0/6/0.0×29.0x0 eslpt NO_HW LUN_PATH LUN path for tape201
lunpath 418 0/0/6/0.0x2a.0x0 eslpt NO_HW LUN_PATH LUN path for tape212
lunpath 423 0/0/6/0.0x2b.0x0 eslpt NO_HW LUN_PATH LUN path for tape204

root@hp-ux:/root # rmsf -H 0/0/4/0.0xb.0x0
root@hp-ux:/root # rmsf -H 0/0/4/0.0×19.0x0
root@hp-ux:/root # rmsf -H 0/0/4/0.0x1a.0x0
root@hp-ux:/root # rmsf -H 0/0/4/0.0x1c.0x0
root@hp-ux:/root # rmsf -H 0/0/4/0.0x1d.0x0
root@hp-ux:/root # rmsf -H 0/0/4/0.0x1e.0x0
root@hp-ux:/root # rmsf -H 0/0/4/0.0×24.0x0
root@hp-ux:/root # rmsf -H 0/0/6/0.0×26.0x0
root@hp-ux:/root # rmsf -H 0/0/6/0.0×27.0x0
root@hp-ux:/root # rmsf -H 0/0/6/0.0×28.0x0
root@hp-ux:/root # rmsf -H 0/0/6/0.0×29.0x0
root@hp-ux:/root # rmsf -H 0/0/6/0.0x2a.0x0
root@hp-ux:/root # rmsf -H 0/0/6/0.0x2b.0x0

root@hp-ux:/root # ioscan -fnkNC lunpath | grep NO_HW
root@hp-ux:/root #

dmesg output
class : lunpath, instance 139
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 147
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 141
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 144
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 155
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 150
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 157
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 408
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 410
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 412
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 415
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 418
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 423
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 139
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 147
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 141
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 144
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 155
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 150
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 157
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 412
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 408
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 410
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 415
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 418
An attempt to probe existing LUN id 0x0 failed with errno of 22.

class : lunpath, instance 423
An attempt to probe existing LUN id 0x0 failed with errno of 22.

DMESG-UNCLASSIFIED: class :Ttggpatha i stlnse tg

Node : hp-ux.setaoffice.com
Node Type : Itanium 64/32(HTTPS)
Severity : major
OM Server Time: 2015-11-05 19:07:46
Message : DMESG-UNCLASSIFIED: class :Ttggpatha i stlnse tg
Msg Group : OS
Application : HPUX_dmesg
Object : dmesg_UNCLASSIFIED
Event Type :
not_found

Instance Name :
not_found

Instruction : No

This is a ticket from HPOM dmesg module.
I added string Ttggpatha to /var/opt/OV/conf/OpC/dmsg_mon.cfg

root@hp-ux:~ # cat /var/opt/OV/conf/OpC/dmsg_mon.cfg
no-rewind
tgtpath
tape, instance
option failed
tgtpath
Ttggpatha

DMESG-UNCLASSIFIED: th, instance 175

Node : hp-ux.setaoffice.com
Node Type : Itanium 64/32(HTTPS)
Severity : major
OM Server Time: 2015-11-06 09:34:49
Message : DMESG-UNCLASSIFIED: th, instance 175
Msg Group : OS
Application : HPUX_dmesg
Object : dmesg_UNCLASSIFIED
Event Type :
not_found

Instance Name :
not_found

Instruction : No

Node : hp-ux.setaoffice.com
Node Type : Itanium 64/32(HTTPS)
Severity : major
OM Server Time: 2015-11-06 09:52:57
Message : DMESG-UNCLASSIFIED: evice id = loop id, for private loop devices
Msg Group : OS
Application : HPUX_dmesg
Object : dmesg_UNCLASSIFIED
Event Type :
not_found

Instance Name :
not_found

Instruction : No

Poor performance on Synology DiskStation’s Proxy Server

Synology released a Proxy Server App.

I’ve been suffering from very poor performance with my NAS.

To solve this problem I set the cache memory size to 256MB. This should be the default setting

Some Fibre Channel HBA models found on HP Proliant running Linux

I was updating some servers and this is a small list that I created to help to update the firmware

Emulex LPe1105 Fibre Channel HBA

root@linux:~ # cat /sys/class/scsi_host/host0/model*name
LPe1105-HP

root@linux:~ # cat /sys/class/scsi_host/host0/model*desc
HP BLc Emulex LPe1105-HP FC Mezz Option Kit

Qlogic QMH2462 Fibre Channel HBA

root@linux:~ # cat /sys/class/scsi_host/host1/model*name
QMH2462

root@linux:~ # cat /sys/class/scsi_host/host1/model*desc
PCI-Express Dual Channel 4Gb Fibre Channel Mezzanine HBA

HP FC2142SR 4Gb 1-port PCIe Fibre Channel Host Bus Adapter

root@linux:~ # cat /sys/class/scsi_host/host3/model*name
A8002A

root@linux:~ # cat /sys/class/scsi_host/host3/model*desc
HP FC2142SR 4Gb PCI-e, SC, Fibre Channel Adapter

HP PCIe Fibre Channel Host Bus Adapter

root@linux:~ # cat /sys/class/scsi_host/host0/model*name
QLE2462

root@linux:~ # cat /sys/class/scsi_host/host0/model*desc

HP 4Gb PCIe Host Bus Adapter

root@linux:~ # cat /sys/class/scsi_host/host0/model*name
QLE2460

root@linux:~ # cat /sys/class/scsi_host/host0/model*desc
PCI-Express Single Channel 4Gb Fibre Channel HBA

Qlogic QMH2462 Fibre Channel HBA

root@linux:~ # cat /sys/class/scsi_host/host2/model*name
QLA2462
root@linux:~ # cat /sys/class/scsi_host/host2/model*desc

Emulex LPe1205 Fibre Channel Host Bus Adapter

root@linux:~ # cat /sys/class/scsi_host/host3/model*name
LPe1205-HP

root@linux:~ # cat /sys/class/scsi_host/host3/model*desc
HP BLc Emulex LPe1205-HP 8Gb FC

HP FC1242SR 4Gb 2-port PCIe Fibre Channel Host Bus Adapter

root@linux:~ # cat /sys/class/scsi_host/host0/model*name
HPAE312A

root@linux:~ # cat /sys/class/scsi_host/host0/model*desc
PCI-Express Dual Port 4Gb Fibre Channel HBA

LP10000

root@linux:~ # cat /sys/class/scsi_host/host0/model*name
LP10000
root@linux:~ # cat /sys/class/scsi_host/host0/model*desc
Emulex LP10000 2Gb PCI-X Fibre Channel Adapter

HP 8Gb 2-port PCIe Fibre Channel Host Bus Adapter

root@linux:~ # cat /sys/class/scsi_host/host3/model*name
AJ763A/AH403A
root@linux:~ # cat /sys/class/scsi_host/host3/model*desc
HP 8Gb Dual Channel PCI-e 2.0 FC HBA

HP LPe1605 16Gb Fibre Channel Host Bus Adapter for BladeSystem c-Class

root@linux:~ # cat /sys/class/scsi_host/host0/model*name
HP-LPe1605
root@linux:~ # cat /sys/class/scsi_host/host0/model*desc
HP LPe1605 16Gb FC HBA

If the links stop working, follow the instruction on Upgrading firmware on an Emulex or QLogic Fibre Channel HBA on HP Proliant to find how to download the correct firmware

Problems updating firmware on QLogic QLE2460, QLE2462 and QMH2462 on HP Proliant

I’m having problems updating the firmware on fibre channel HBA cards QLE2460, QLE2462 QMH2462.

For example, this server has a single channel 4Gb QLE2460 and dual channel 4Gb QLE2462

root@linux01:~ # cat /sys/class/scsi_host/host*/model*name
QLE2462
QLE2462
QLE2460

root@linux01:~ # cat /sys/class/scsi_host/host*/model*desc
PCI-Express Dual Channel 4Gb Fibre Channel HBA
PCI-Express Dual Channel 4Gb Fibre Channel HBA
PCI-Express Single Channel 4Gb Fibre Channel HBA

root@linux01:~ # lspci -k | grep -A2 -i fibre
22:00.0 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 02)
Subsystem: QLogic Corp. Device 0138
Kernel driver in use: qla2xxx
—
22:00.1 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 02)
Subsystem: QLogic Corp. Device 0138
Kernel driver in use: qla2xxx
—
25:00.0 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 03)
Subsystem: QLogic Corp. Device 0137
Kernel driver in use: qla2xxx

Following the instruction on Updating firmware on an Emulex or QLogic Fibre Channel HBA on HP Proliant and downloaded the file CP022840.scexe

root@linux01:~ # ./CP022840.scexe
—————————————————
Loading references…done.
Performing discovery…
WARNING! : No supported adapters found.

Checking the log file, it shows that no adapters found and gives return code 7

root@linux01:~ # cat /var/cpq/Component.log
=================================================================

Installation started: Thu Nov 5 18:12:09 BRST 2015

Installing: CP022840.scexe
Version: 2014.09.01
Description: HP Firmware Flash for QLogic Fibre Channel HBA’s (x86_64)

—————————————————
Loading references…done.
Performing discovery…
WARNING! : No supported adapters found.

Return code: 7

Installation complete: Thu Nov 5 18:12:09 BRST 2015

=================================================================

On this other server I have a QMH2462 and I had the same problem

root@linux02:~ # cat /sys/class/scsi_host/host*/model*name
QMH2462
QMH2462
root@linux02:~ # cat /sys/class/scsi_host/host*/model*desc

root@linux02:~ # lspci -k | grep -A2 -i fibre
09:00.0 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 03)
Subsystem: Hewlett-Packard Company Device 1705
Kernel driver in use: qla2xxx
—
09:00.1 Fibre Channel: QLogic Corp. ISP2432-based 4Gb Fibre Channel to PCI Express HBA (rev 03)
Subsystem: Hewlett-Packard Company Device 1705
Kernel driver in use: qla2xxx

root@linux02:~ # cat /var/cpq/Component.log
=================================================================

Installation started: Fri Oct 9 12:09:36 BRT 2015

Installing: CP022840.scexe
Version: 2014.09.01
Description: HP Firmware Flash for QLogic Fibre Channel HBA’s (x86_64)

—————————————————
Loading references…done.
Performing discovery…
WARNING! : No supported adapters found.

Return code: 7

Installation complete: Fri Oct 9 12:09:36 BRT 2015

=================================================================

I think the solution will be to update the firmware offline using the HP SPP DVD and selecting Firmware update

Resizing filesystem online on HP-UX

Check the volume group and logical volume being used by the filesystem

root@hp-ux:/root # bdf /example
Filesystem kbytes used avail %used Mounted on
/dev/vg01/lvol14 32768 2141 28720 7% /example

This logical volume has 32MB and uses 2 PE

root@hp-ux:/root# lvdisplay /dev/vg01/lvol14
— Logical volumes —
LV Name /dev/vg01/lvol14
VG Name /dev/vg01
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 32
Current LE 2
Allocated PE 2
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default
Each PE has 16MB and there is 1047 available

root@hp-ux:/root# vgdisplay vg01
— Volume groups —
VG Name /dev/vg01
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 16
Open LV 16
Max PV 40
Cur PV 2
Act PV 2
Max PE per PV 50000
VGDA 4
PE Size (Mbytes) 16
Total PE 12796
Alloc PE 11749
Free PE 1047
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
VG Version 1.0
VG Max Size 31250g
VG Max Extents 2000000

Checking if it is possible to resize online the filesystem. In some HP-UX versions, this feature is not available

root@hp-ux:/root# swlist -l product | grep -i jfs
AONLINEJFS B.05.01.02 OnlineJFS 5.0.1 Integration Product
JFS B.11.31 Base VxFS File System 4.1 for HP-UX
OnlineJFS01 5.0.31.6 Online features of the VxFS File System

Extending filesystem to 5120MB

root@hp-ux:/root# lvextend -L 5120 /dev/vg01/lvol14
Logical volume “/dev/vg01/lvol14” has been successfully extended.
Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf

Increased logical volume to 320 PE adn 5120MB

root@hp-ux:/root# lvdisplay /dev/vg01/lvol14
— Logical volumes —
LV Name /dev/vg01/lvol14
VG Name /dev/vg01
LV Permission read/write
LV Status available/syncd
Mirror copies 0
Consistency Recovery MWC
Schedule parallel
LV Size (Mbytes) 5120
Current LE 320
Allocated PE 320
Stripes 0
Stripe Size (Kbytes) 0
Bad block on
Allocation strict
IO Timeout (Seconds) default

Now running fsadm to increase the filesystem

root@hp-ux:/root# fsadm -F vxfs -b 5120m /example
UX:vxfs fsadm: INFO: V-3-25942: /dev/vg01/rlvol14 size increased from 32768 sectors to 5242880 sectors

root@hp-ux:/root# bdf /example
Filesystem kbytes used avail %used Mounted on
/dev/vg01/lvol14 5242880 3417 4912004 0% /example

Server booting correctly but file /boot/grub/grub.conf is missing

I was checking a server that didn’t have the file /boot/grub/grub.conf but it was booting without any issues.

The server is a Proliant Gen9

root@linux:~ # dmidecode –type system
# dmidecode 2.12
# SMBIOS entry point at 0x788fb000
SMBIOS 2.8 present.

Handle 0x0009, DMI type 1, 27 bytes
System Information
Manufacturer: HP
Product Name: ProLiant BL460c Gen9
Version: Not Specified
Serial Number:
UUID:
Wake-up Type: Power Switch
SKU Number: 727021-B21
Family: ProLiant

Handle 0x009E, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected

This server has UEFI instead of BIOS. Checking some servers I found the file on /boot/efi/EFI/redhat

root@linux:/boot/efi/EFI/redhat # ls -l
total 256
-rwx——. 1 root root 1648 Nov 4 13:00 grub.conf
-rwx——. 1 root root 254248 Apr 7 2015 grub.efi

and /boot/efi/efi/redhat

root@linux:/boot/efi/efi/redhat # ls -l
total 264
-rwx——. 1 root root 1666 Nov 4 12:59 grub.conf
-rwx——. 1 root root 254248 Apr 7 2015 grub.efi

UXMON: The OFFSET in one peer is greater than the threshold: 400

Node : linux.setaoffice.com
Node Type : Intel/AMD x64(HTTPS)
Severity : minor
OM Server Time: 2015-10-28 13:01:33
Message : UXMON: The OFFSET in one peer is greater than the threshold: 400
Msg Group : OS
Application : ntpmon
Object : ntp
Event Type :
not_found

Instance Name :
not_found

Instruction : The ntpq -p command shows with one or more peers the
offset in time is greater than the threshold set in the
ntp_mon.cfg.

Please, review the ntp status of your system or increase
the threshold in the ntp_mon if you consider this offset
in time between the clocks of your system and the peer’s clock
is aceptable

Please check /var/opt/OV/log/OpC/ntp_mon.log for more details

Run ntpq -p and then check if the offset is higher than what’s configured on ntp_mon.cfg

root@linux:~ # cat /var/opt/OV/conf/OpC/ntp_mon.cfg
NTP_OFFSET 400
NUM_PEER_FAILS 5

Sync the two ntp servers that you are using and then restart the ntp service on the server

root@linux:~ # ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
ntp1 142.40.238.18 6 u 23 64 377 1.761 -23.727 9.886
ntp2 15.179.90.135 5 u 30 64 377 2.003 -48.137 4.418

Share this:

Share this:

Share this:

Share this:

Share this:

Share this:

Share this:

Share this:

Share this:

Share this: