18.02.2014 Views

string

string

string

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Action<br />

Replace the memory module or chip at the indicated position. Refer to the vendor’s<br />

hardware manual for help finding this location.<br />

Bad request descriptor<br />

Cause<br />

Apparently used only in NIS+ to indicate corrupted or missing tables.<br />

Technical Notes<br />

The symbolic name for this error is EBADR, errno=51.<br />

BAD SUPER BLOCK: <strong>string</strong><br />

Cause<br />

This message from fsck(1M) indicates that a filesystem’s super-block is damaged<br />

beyond repair and must be replaced. At boot time (with the -p option) this message<br />

is prefaced by the filesystem’s device name. After this message comes the actual<br />

damage recognized (see Action). Unfortunately fsck(1M) does not print the<br />

number of the damaged super-block.<br />

Action<br />

The most common cause of this error is overlapping disk partitions. Do not<br />

immediately rerun fsck(1M) as suggested by the lines that display after the error<br />

message. First make sure that you have a recent backup of the filesystem involved; if<br />

not, try to back up the filesystem now using ufsdump(1M). Then run the<br />

format(1M) command, select the disk involved, and print out the partition<br />

information.<br />

# format<br />

: N<br />

> partition<br />

(continued)<br />

24 Solaris Common Messages and Troubleshooting Guide ♦ October, 1998

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!