Tag: error

Solaris SVM error when attaching a new disk – metattach I/O Error

I was trying to increase a metadevice with another disk but I was getting an I/O error

root@solaris:~ # metattach d200 /dev/rdsk/emcpower46c
metattach: solaris: /dev/dsk/emcpower46c: I/O error

Nothing strange was appearing in the emcpower disk

root@solaris:~ # powermt display dev=emcpower46
Pseudo name=emcpower46a
Symmetrix ID=000287752010
Logical device ID=01A1
state=alive; policy=SymmOpt; priority=0; queued-IOs=0
==============================================================================
—————- Host ————— – Stor – — I/O Path – — Stats —
### HW Path I/O Paths Interf. Mode State Q-IOs Errors
==============================================================================
3072 pci@8,600000/SUNW,emlxs@1/fp@0,0 c1t5006048449AFD288d18s0 FA 9aA active alive 0 0
3073 pci@8,600000/SUNW,emlxs@2/fp@0,0 c2t5006048449AFD287d18s0 FA 8aA active alive 0 0

A friend here at work asked if the disk has a label. It didn’t have one.

selecting emcpower46e
[disk formatted]
Disk not labeled. Label it now? yes

After that I was able to increase the metadevice.

root@solaris:~ # metattach d200 /dev/rdsk/emcpower46c
d200: component is attached

Unable to find the answer LIBDIR – VMware Server

Does anybody know how to solve this problem?

root@memcached:~ # rpm -ivh –force VMwareTools-1.0.5-80187.i386.rpm
Preparing… ########################################### [100%]
Unable to find the answer LIBDIR in the installer database
(/etc/vmware-tools/locations). You may want to re-install VMware
Tools.\n\nExecution aborted.

error: %pre(VMwareTools-6533-80187.i386) scriptlet failed, exit status 1
error: install: %pre scriptlet failed (2), skipping VMwareTools-6533-80187

I cancelled (CTRL+C) in the middle of the installation of the rpm and now I can’t run the installer or reinstall the rpm.

Received SSH_FXP_NAME packet with zero or multiple records – WinSCP

The problem “Received SSH_FXP_NAME packet with zero or multiple records” was manifested here with AIX and here what I did to solve it.

First I login to the machine with the ssh and use a regular user (root doesn’t count).
I entered the directory where the error is ocurring and listed it using ls -la. Check the current directory and up one level (. and ..). If it appear as ./.. Permission denied, do the following:
1. Umount the filesystem. If necessary, force it (umount -f /filesystem).
2. Check the permissions of the folder used by the mount point.
3. Mount it.
4. Check the permissions of the mount point.
5. List again inside the filesystem (ls -la) and check if the message (./.. Permission denied) appears again.

Try to connect again with WinSCP.

This problem manifested while using WinSCP. FileZilla wasn’t presenting this behavior.