03-18-2004
FIXED and you'll never guess what it was
wow, never saw this and not sure why it just happened, but the problem was end termination of the scsi chain. The last device had the wrong scsi id AND wasn't terminated. This has worked for over a year so not sure why it happened now, and not sure how those pins got changed, because when it was set up it was correct. but that was it completely. So hope this helps someone else.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Could some one please tell the command used to boot from an external SCSI cdrom drive? from PROM level. (2 Replies)
Discussion started by: fishman2001
2 Replies
2. Solaris
I want to install Solaris 9 on SUN ULTRA 10. The cdrom is attached to an ide controller. The server is currently running Solaris 2.6
I insert Solaris cd 1 of 2 and at the ok prompt I type boot cdrom i get the error below
Boot device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0:f file and args:... (11 Replies)
Discussion started by: Msororaji
11 Replies
3. Solaris
i am having a problem when trying to boot from cdrom. I received the below message
system is not bootable, boot command is disabledfound
how can i fix this.
also what is the key combination on ordinary keyboard for STOP+A. Is it ctrl+break? (2 Replies)
Discussion started by: shabu
2 Replies
4. AIX
Hello:
NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Discussion started by: bbird
11 Replies
5. Solaris
Hi all am trying to boot the system from cdrom in single user mode , however when i am giving command boot cdrom -s i am getting below error
Boot Device: /pci@1f,0/pci@1,1/ide@3/cdrom@2,0: f file and args:
Can't read disk label
Can't open disk label package
can,t open boot device
... (17 Replies)
Discussion started by: kumarmani
17 Replies
6. Solaris
iam traying to install o/s in spark machine it showing error
ok >boot cdrom
is showing error
short disk read
failed to read superblock
the file just loaded does not appear to excutable
how to solve this can u help me (6 Replies)
Discussion started by: tirupathi
6 Replies
7. Solaris
Hi community,
Does anyone can tell me the difference between "boot cdrom" and "boot cdrom - install" ?
Thank you very much:D (3 Replies)
Discussion started by: Sunb3
3 Replies
8. Boot Loaders
Hello,
I have kubuntu on my laptop and now I decided to switch to Windows 7. I made the bios settings properly (first choice is boot from cd\vd) but I see the error
" reboot and select proper Boot device or insert Boot media in select Boot device and press a key "
I have tried CD and... (0 Replies)
Discussion started by: rpf
0 Replies
9. Hardware
I have a server with a scsi raid controller (for hard drives) and a scsi controller (for tape drive and cd-rom). I am trying to boot from the cd-rom but can't. During boot up, bootable media is detected in the cd-rom but the system will not boot from it. BIOS for the raid controller installs but... (1 Reply)
Discussion started by: powwm
1 Replies
10. UNIX for Beginners Questions & Answers
Good Afternoon,
I'm trying to boot from cdrom so I:
bash-2.05# init 0
{1} ok boot cdrom -s and I get:
Rebooting with command: boot cdrom -s
Boot Device: /pci@1e,600000/ide@d/cdrom@2,0:f File and args: -s
Can't read disk label.
Can't open disk label package
Evaluating:
Can't open boot... (13 Replies)
Discussion started by: Stellaman1977
13 Replies
LEARN ABOUT CENTOS
fc_remote_port_add
FC_REMOTE_PORT_ADD(9) SCSI mid layer FC_REMOTE_PORT_ADD(9)
NAME
fc_remote_port_add - notify fc transport of the existence of a remote FC port.
SYNOPSIS
struct fc_rport * fc_remote_port_add(struct Scsi_Host * shost, int channel, struct fc_rport_identifiers * ids);
ARGUMENTS
shost
scsi host the remote port is connected to.
channel
Channel on shost port connected to.
ids
The world wide names, fc address, and FC4 port roles for the remote port.
DESCRIPTION
The LLDD calls this routine to notify the transport of the existence of a remote port. The LLDD provides the unique identifiers (wwpn,wwn)
of the port, it's FC address (port_id), and the FC4 roles that are active for the port.
For ports that are FCP targets (aka scsi targets), the FC transport maintains consistent target id bindings on behalf of the LLDD. A
consistent target id binding is an assignment of a target id to a remote port identifier, which persists while the scsi host is attached.
The remote port can disappear, then later reappear, and it's target id assignment remains the same. This allows for shifts in FC addressing
(if binding by wwpn or wwnn) with no apparent changes to the scsi subsystem which is based on scsi host number and target id values.
Bindings are only valid during the attachment of the scsi host. If the host detaches, then later re-attaches, target id bindings may
change.
This routine is responsible for returning a remote port structure. The routine will search the list of remote ports it maintains internally
on behalf of consistent target id mappings. If found, the remote port structure will be reused. Otherwise, a new remote port structure will
be allocated.
Whenever a remote port is allocated, a new fc_remote_port class device is created.
Should not be called from interrupt context.
NOTES
This routine assumes no locks are held on entry.
AUTHORS
James Bottomley <James.Bottomley@hansenpartnership.com>
Author.
Rob Landley <rob@landley.net>
Author.
COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 FC_REMOTE_PORT_ADD(9)