error SAM

[Eli Daniel]

(server Virtual Machine Guesst)
when I try to see the disk assigned to the LV, the following message:

unexpected exit: procces LANG=C LC_ALL=C /usr/sam/lbin/samx -C -p 5930 -s fs_sa_disk /usr/sam/lib//fs.iu exited with a non-zero exit status
sh: 6053 Memory fault (coredump)

[Johnson Punniyalingam · Accepted solution]

above error, looks like "you may have bad memory "

it would be better to log HW call to "check "Memory from HP Response Centre

[Johnson Punniyalingam]

>>unexpected exit: procces LANG=C LC_ALL=C /usr/sam/lbin/samx -C -p 5930 -s fs_sa_disk /usr/sam/lib//fs.iu exited with a non-zero exit status<<

above looks like earlier some one used the "SAM" got some problem did proper exit from "SAM" also could cause issue .?



btw , what is OS version, what is model of server ..?




uname -a;model

[Eli Daniel]

server rx6600
S.O hp-ux 11.23
Virtual Machine Guesst

[Eli Daniel]

this day in the morning assign a new disk, create LV and VG. (disk from SAN EMC)

[Johnson Punniyalingam]

ok so, you did you SAM -> to create new disk, create LV and VG, ..?

Can we try to create "create new disk, create LV and VG," via command line ?

suspecting "if you have used SAM" to create ..(VG,LV)using SAM, as mentioned earlier, person who used "SAM" earlier didn't properly exit from "SAM" menu.

[Eli Daniel]

the create LV and VG were created command no SAM.

[Johnson Punniyalingam]

>>>the create LV and VG were created command no SAM.<<<<

>>sh: 6053 Memory fault (coredump)<<


so please log "HW" call HP -> Response Centre to check "Memory fault"

[Eli Daniel]

the error affects the system??? is a serious case?

[Dennis Handly]

>/usr/sam/lbin/samx -C -p 5930 -s fs_sa_disk /usr/sam/lib//fs.iu exited with a non-zero exit status
sh: 6053 Memory fault (coredump)

This is a bug in samx, signal 11. Do you have all of your SAM patches?
PHCO_34974 is the recommended one.

>Johnson: looks like "you may have bad memory"
>it would be better to log HW call to "check "Memory from HP Response Centre

Not hardly. This is a software error/bug.

You can use gdb to look at the core file to see if it matches any patches.