18.02.2014 Views

string

string

string

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

fd0: unformatted diskette or no<br />

diskette in the drive<br />

Cause<br />

This message appears on the system console to indicate that the floppy driver fd(4)<br />

could not read the label on a diskette. Usually this is either because a new diskette<br />

has not yet been formatted, or a formatted diskette has become corrupted. This<br />

message often appears along with "read failed" and "bad format" messages after<br />

volcheck(1) is run.<br />

Action<br />

If you are certain that the diskette contains no data, run fdformat -d to format the<br />

diskette in DOS format. (You can also format a diskette in UFS format if you like,<br />

although then it cannot be transported to most other systems.) When the diskette is<br />

formatted, you can write on it, if it was not corrupted beyond repair.<br />

File descriptor in bad state<br />

Cause<br />

Either a file descriptor refers to no open file or a read request was made to a file that<br />

is open only for writing.<br />

Technical Notes<br />

The symbolic name for this error is EBADFD, errno=81.<br />

File exists<br />

Cause<br />

The name of an existing file was mentioned in an inappropriate context. For<br />

example, establishing a link to an existing file, or overwriting an existing file are not<br />

allowed when the csh(1) noclobber option is set.<br />

68 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!