12-02-2010
I think it just means no SDD devices were found.
Check your storage and SAN zoning.
10 More Discussions You Might Find Interesting
1. Solaris
I just installed IBMsddsun64_........... on my sun server. I untarred it (tar xvf) & I tried to install the paxkage. When I did pkgadd -d ./IBMsdd..... I get a message Error, no packages were found.
Any idea
Thanks, (1 Reply)
Discussion started by: Remi
1 Replies
2. AIX
Hi all,
Sorry if this is in the wrong place but needed to make sure lots of people saw this so that hopefully someone will be able to help.
Basically i've upgraded a test server from 4.3 to 5.3 TL04.
The server has hdisk0 and 1 as rootvg locally but then has another vg setup on our ESS... (5 Replies)
Discussion started by: djdavies
5 Replies
3. UNIX for Advanced & Expert Users
Hi all,
Sorry if this is in the wrong place but needed to make sure lots of people saw this so that hopefully someone will be able to help.
Basically i've upgraded a test server from 4.3 to 5.3 TL04.
The server has hdisk0 and 1 as rootvg locally but then has another vg setup on our ESS... (1 Reply)
Discussion started by: djdavies
1 Replies
4. Filesystems, Disks and Memory
Hello Unix Admins:
Has any one in this distribution list implemented SVC (SAN Volume Contoller - A solution from IBM) in your environment? If you have, do you have any do's / don'ts? Anything which you like sharing would be really appreciated.
For example, my inputs:
I tried implementing... (1 Reply)
Discussion started by: kdossjojo
1 Replies
5. AIX
Can anyone recommend me some reading material surrounding how AIX handles LUNs:
- with and without MPIO installed
- with and without SDD or SDDPCM installed
Where does lspath sit in all of this (MPIO layer?). Can a system be built with just MPIO software? Is MPIO software even needed?
I guess... (0 Replies)
Discussion started by: apra143
0 Replies
6. Red Hat
I was wondering if there is a way of auto-detecting a new vpath, using IBM's SDD driver, on a Linux platform.
ON AIX it is a simple as running cfgmgr.
Alan (0 Replies)
Discussion started by: alanp
0 Replies
7. AIX
Hi folks.
We want to move a "physical" AIX box to a VIOed LPAR. The physical box is running SDD with disks from a DS8300. I want to be able to reattach those LUNs from the DS8300 to my VIO server which is running SDDPCM and then assigned them back to my AIX LPAR. Any thoughts about this?
I... (1 Reply)
Discussion started by: Stephan
1 Replies
8. Red Hat
Dear Guru,
IHAC who is using Redhat Linux 5 on DELL M910.
When system bootup, it show "Buffer I/O error on device sdd" error message. Below is the "dmesg" output.
The scenario is:
If more external FC SAN disk LUN add, the device would change other name. So it will impact the raw device... (7 Replies)
Discussion started by: devyfong
7 Replies
9. AIX
hi all
we recently upgraded our san switches. after that, i found i got many hdisks showing in lsdev with status "Defined" and "Available". the number of "Defined" is equal to "Available". the time stamp shows all "Available" disks created at our downtime night.
"datapath query device"... (0 Replies)
Discussion started by: rs6000er
0 Replies
10. AIX
This is getting very confusing for me, and appreciate if someone can help.
Platform: Power VM ( Virtual I/O Server)
ioslevel 2.1.3.10-FP23
# oslevel -s
6100-05-00-0000
Storage: IBM DS4300
Two HBAs - Dual Port Fibre Adapter Channels
Each card has two ports , so a total of 4 ports going... (3 Replies)
Discussion started by: filosophizer
3 Replies
HY(4) Kernel Interfaces Manual HY(4)
NAME
hy - Network Systems Hyperchannel interface
SYNOPSIS
/sys/conf/SYSTEM:
NHY hy_controllers # Hyperchannel
DESCRIPTION
The hy interface provides access to a Network Systems Corporation Hyperchannel Adapter.
The network to which the interface is attached is specified at boot time with an SIOCSIFADDR ioctl. The host's address is discovered by
reading the adapter status register. The interface will not transmit or receive packets until the network number is known.
DIAGNOSTICS
hy%d: unit number 0x%x port %d type %x microcode level 0x%x. Identifies the device during autoconfiguration.
hy%d: can't handle af%d. The interface was handed a message with addresses formatted in an unsuitable address family; the packet was
dropped.
hy%d: can't initialize. The interface was unable to allocate UNIBUS resources. This is usually due to having too many network devices on
an 11/750 where there are only 3 buffered data paths.
hy%d: NEX - Non Existent Memory. Non existent memory error returned from hardware.
hy%d: BAR overflow. Bus address register overflow error returned from hardware.
hy%d: Power Off bit set, trying to reset. Adapter has lost power, driver will reset the bit and see if power is still out in the adapter.
hy%d: Power Off Error, network shutdown. Power was really off in the adapter, network connections are dropped. Software does not shut
down the network unless power has been off for a while.
hy%d: RECVD MP > MPSIZE (%d). A message proper was received that is too big. Probable a driver bug. Shouldn't happen.
hy%d: xmit error - len > hy_olen [%d > %d]. Probable driver error. Shouldn't happen.
hy%d: DRIVER BUG - INVALID STATE %d. The driver state machine reached a non-existent state. Definite driver bug.
hy%d: watchdog timer expired. A command in the adapter has taken too long to complete. Driver will abort and retry the command.
hy%d: adapter power restored. Software was able to reset the power off bit, indicating that the power has been restored.
SEE ALSO
intro(4N), inet(4F)
BUGS
If the adapter does not respond to the status command issued during autoconfigure, the adapter is assumed down. A reboot is required to
recognize it.
The adapter power fail interrupt seems to occur sporadically when power has, in fact, not failed. The driver will believe that power has
failed only if it can not reset the power fail latch after a ``reasonable'' time interval. These seem to appear about 2-4 times a day on
some machines. There seems to be no correlation with adapter rev level, number of ports used etc. and whether a machine will get these
``bogus powerfails''. They don't seem to cause any real problems so they have been ignored.
3rd Berkeley Distribution August 20, 1987 HY(4)