Your system seems to be complaining about a couple of network interfaces which are either really faulty or have been flagged as faulty in error.
In the service processor (SP>) try clearfault and clearasrdb commands.
Then try booting.
If that fails try shutting the system down completely (unplug power) and then reconnect. Watch the SP start up and whether it marks these devices as bad (error messages). If they are marked bad:
then try boot.
I've seen this work despite the devices being marked bad during SP boot. If this works the most likely cause is a daughterboard containing these interfaces needs reseating (poor electrical contact issue).
Hope that helps.
---------- Post updated at 10:40 PM ---------- Previous update was at 10:21 PM ----------
Hi, i was installing solaris 8 on sunfire v250 and the power fails :mad: , now it does not boot from cd rom and get the next msg:
ð
Sun Fire V120 (UltraSPARC-IIe 648MHz), No Keyboard
OpenBoot 4.0, 512 MB memory installed, Serial #56338483.
Ethernet address 0:3:ba:5b:a8:33, Host ID: 835ba833.
... (1 Reply)
I have a machine running HP-UX 11.23 (PARISC) and APA startup fails on boot. This is found in /etc/rc.log:
Configure Auto-Port Aggregation(LAN Monitor) interfaces
Output from "/sbin/rc2.d/S343hplm start":
----------------------------
get_start_dlpi_version: failed, errno is 22
ERROR: ... (1 Reply)
Hi,
I am trying to setup a server for a diskless boot of a computer class (with ubuntu)
I followed the guidelines in https://help.ubuntu.com/community/DisklessUbuntuHowto
I have two computers: one is the server I installed and the other is my macbook on which I run a virtual machine... (8 Replies)
I have three Sun Oracle Netra T5220s. I am trying to just get the processor information psrinfo or prtdiag -v from the # prompt in single user mode.
I am needing to know the commands to get to boot the CD/DVD of the Solaris OS. I am using it via Serial Port Management.
Tinkering around I... (4 Replies)
I have a T2000 enterprise SPARC server that's no longer on contract with Oracle. It's on old firmware (6.3.x). After a power-down this weekend, it won't boot normally. Boot snapshot at the bottom of the post.
It can boot to cdrom, and it'll boot to failsafe mode, but it won't do a regular... (9 Replies)
I have an m5000 that Is down.
I have access to XSCF>
and was able to get to the ok prompt.
However, on
>ok boot
it failed to boot.
erred with :
svc.startd: svc:/system/device/fc-fabric:default: Method "/lib/svc/method/fc-fabric" failed due to signal KILL.
Nov 29... (3 Replies)
My OS solarius 5.10 Generic_147148-2 i86
Error: please review new boots environments using options
1. Solution - show me the commands
Partition is full, try to remove some unneeded files,
then try to compress some other unneeded files.
man command creates a temp file under... (0 Replies)
My system suddenly crash and when it rebooted there was an error:
/dev/rdsk/c1t0d0s3 is logging
svc.startd: svc:/network/nis/client:default: Method "/method/yp" failed with status 96.
The system completes booting however when I log in a user account / directory is not longer... (1 Reply)
Hi,
I want to install Solaris-11 on T5220. I created USB from sol-11_4-text-sparc.usb by usbcopy on another Solaris-11 servers, which looks like a good one.
I tried did "reset-all" and still same issue. Can I get some help on this.
{0} ok reset-all
Sun Netra T5220, No Keyboard
Copyright... (8 Replies)
hi:)
i can't boot my sun server by iso solaris 10 sparc dvd that i did download from oracle site.
my hardware is sun T5220.
i receive these after running boot cdrom -s :
can't read disk lable
can't open disk lable package
ERROR: boot-read fail
whould u help me?
Please use CODE... (1 Reply)
Discussion started by: Arefdel
1 Replies
LEARN ABOUT BSD
bad144
BAD144(8) System Manager's Manual BAD144(8)NAME
bad144 - read/write DEC standard 144 bad sector information
SYNOPSIS
bad144 disktype disk [ sno [ bad ... ] ]
DESCRIPTION
Bad144 can be used to inspect the information stored on a disk that is used by the disk drivers to implement bad sector forwarding. The
format of the information is specified by DEC standard 144, as follows.
The bad sector information is located in the first 5 even numbered sectors of the last track of the disk pack. There are five identical
copies of the information, described by the dkbad structure. Only the first of these copies is used.
Replacement sectors are allocated starting with the first sector before the bad sector information and working backwards towards the begin-
ning of the disk. A maximum of 126 bad sectors can be supported. The position of the bad sector in the bad sector table determines which
replacement sector it corresponds to.
The bad sector information and replacement sectors are conventionally only accessible through the ``h'' file system partition of the disk.
If that partition is used for a file system, the user is responsible for making sure that it does not overlap the bad sector information or
any replacement sectors.
The bad sector structure is as follows:
struct dkbad {
long bt_csn; /* cartridge serial number */
u_short bt_mbz; /* unused; should be 0 */
u_short bt_flag; /* -1 => alignment cartridge */
struct bt_bad {
u_short bt_cyl; /* cylinder number of bad sector */
u_short bt_trksec; /* track and sector number */
} bt_bad[MAXBAD];
};
Unused slots in the bt_bad array are filled with all bits set, a putatively illegal value. MAXBAD (in <sys/dkbad.h>) may be tuned locally
to reduce the space required to hold the bad-sector file in memory. It may not be greater than 126, which uses the whole disk sector. Bad
sectors past MAXBAD may be included by the formatter, but replacement sectors will not be used until MAXBAD is increased.
Bad144 is invoked by giving a device type (e.g. rk07, rm03, rm05, etc.), and a device name (e.g. hk0, hp1, etc.). It reads the first sec-
tor of the last track of the corresponding disk and prints out the bad sector information. It may also be invoked giving a serial number
for the pack and a list of bad sectors, and will then write the supplied information onto the same location. Note, however, that bad144
does not arrange for the specified sectors to be marked bad in this case. This option should only be used to restore known bad sector
information which was destroyed.
New bad sectors can be added by running the standard DEC formatter in section ``bad.''
SEE ALSO badsect(8)BUGS
Not all drivers support bad-sector forwarding on the PDP-11.
It should be possible to both format disks on-line under UNIX and to change the bad sector information, marking new bad sectors, without
running a standalone program.
The bootstrap drivers used to boot the system do not understand bad sectors or handle ECC errors. This means that none of these errors can
occur when reading the file /unix to boot. Sector 0 of the disk drive and the file /boot in the root file system of that drive must also
not have any of these errors in it.
The drivers that write a system core image on disk after a crash do not handle errors; thus the crash dump area must be free of errors and
bad sectors.
3rd Berkeley DistributionBAD144(8)