|
|
Sponsored Content
Operating Systems
Solaris
bad BPR sig
Post 99660 by eykyn17 on Monday 20th of February 2006 12:28:10 PM
02-20-2006
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Just testing my sig.. if it doesnt work need some more help.. (2 Replies)
Discussion started by: Voodoo Child
2 Replies
2. UNIX for Dummies Questions & Answers
Well i install successfully Solaris on my Second Hard disk, although i had to make it primary Master and my orignal hard disk as pirmary slave, because solaris will not let Windows on primary master.
Anyway after installation when i try to boot from hard disk , it shows message
bad PBR Sig ... (3 Replies)
Discussion started by: abidmalik
3 Replies
3. Post Here to Contact Site Administrators and Moderators
Is there an issue with it? (2 Replies)
Discussion started by: Spetnik
2 Replies
4. UNIX for Dummies Questions & Answers
ok, i recently posted asking for a distro of unix, and someone said to try solaris, so i booted up the dvd iso installer. And after making some kind of mistake in the preperation, I couldnt retry the installer, it repeated the Warning: Bad Geometry. thing, and when i tried to just boot up into... (0 Replies)
Discussion started by: FaoX666
0 Replies
5. UNIX for Advanced & Expert Users
I need to write a script that can find a bad record (for example: there is date field colom but value provided in the file for this field is N/A) then script shoud searches this pattern and then insert the whole record into the bad file.
Example:
File1
Name designation dateOfJoining... (1 Reply)
Discussion started by: shilendrajadon
1 Replies
6. Shell Programming and Scripting
I need to write a script that can find a bad record (for example: there is date field colom but value provided in the file for this field is N/A) then script shoud searches this pattern and then insert the whole record into the bad file.
Example:
File1
Name designation dateOfJoining... (2 Replies)
Discussion started by: shilendrajadon
2 Replies
7. Solaris
After installing Solaris 10 x86 (solaris 5 2009 update 7 ) i've been granted a “Bad PBR sig” error message on boot, making my system unbootable. any one has any solution for this problem (1 Reply)
Discussion started by: maxim42
1 Replies
8. Shell Programming and Scripting
Hello all!
I'm writing a script that will catch when an outside process crashes (SIGHUP, right?) without having to loop into infinity.
With that in mind, I came across the trap utility and thought if could be used to monitor another process other than it's own. But from what I've read, I'm... (1 Reply)
Discussion started by: mashiox
1 Replies
9. Solaris
Hello everyone,
I have a Sun x4600 (Solaris 10 x86) server.During boot up "Bad PBR sig" error comes soon after post (before GRUB). Unless the return key is pressed the server never boots up. Once the return key is pressed the boot process continues without any problem.
Can you please help me... (1 Reply)
Discussion started by: pingmeback
1 Replies
10. Shell Programming and Scripting
Why I get bad replace when using eval?
$ map0=( "0" "0000" "0")
$ i=0
$ eval echo \${map$i}
0000
$ a=`eval echo \${map$i}` !!!error happens!!!
bash: ${map$i}: bad substitution
How to resolve it ?
Thanks! (5 Replies)
Discussion started by: 915086731
5 Replies
LEARN ABOUT SUSE
usoc
usoc(7D) Devices usoc(7D) NAME
usoc - universal serial optical controller for Fibre Channel arbitrated loop (SOC+) device driver DESCRIPTION
The Fibre Channel adapter is an SBus card that implements two full duplex Fibre Channel interfaces. Each interface can connect to a Fibre Channel arbitrated loop (FC-AL). The usoc device driver is a nexus driver and implements portions of the FC-2 and FC-4 layers of FC-AL. FILES
/kernel/drv/usoc 32-bit ELF kernel module /kernel/drv/sparcv9/usoc 64-bit ELF kernel module ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Architecture |SPARC | +-----------------------------+-----------------------------+ |Interface stability |Unknown | +-----------------------------+-----------------------------+ |Availability |SUNWusoc | +-----------------------------+-----------------------------+ SEE ALSO
fctl(7D), sbus(4), fcp(7D), fp(7D), ssd(7D) Writing Device Drivers Fibre Channel Physical and Signaling Interface (FC-PH) ANSI X3.230: 1994 Fibre Channel Arbitrated Loop (FC-AL) ANSI X3.272-1996 Fibre Channel Private Loop SCSI Direct Attach (FC-PLDA) NCITS TR-19:1998 Fabric Channel Loop Attachment (FC-FLA), NCITS TR-20:1998 DIAGNOSTICS
The following messages are logged and may also appear on the system console. On the console these messages are preceded by: usoc%d: where usoc%d: is the per-port instance number of the usoc controller. Fibre Channel is ONLINE The Fibre Channel loop is now online. Fibre Channel Loop is ONLINE The Fibre Channel loop is now online. Fibre Channel Loop is OFFLINE The Fibre Channel loop is now offline. attach failed: device in slave-only slot. Move soc+ card to another slot. attach failed: alloc soft state. Driver did not attach, devices will be inaccessible. attach failed: bad soft state. Driver did not attach, devices will be inaccessible. attach failed: unable to map eeprom Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to map XRAM Driver was unable to map device memory; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to map registers Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to access status register Driver was unable to map device registers; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to install interrupt handler Driver was not able to add the interrupt routine to the kernel. Driver did not attach to device, devices will be inaccessible. attach failed: unable to access host adapter XRAM Driver was unable to access device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: unable to write host adapter XRAM Driver was unable to write device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. attach failed: read/write mismatch in XRAM Driver was unable to verify device RAM; check for bad hardware. Driver did not attach to device, devices will be inaccessible. SunOS 5.10 20 Jul 1999 usoc(7D)