Sponsored Content
Full Discussion: Cannot boot from scsi cdrom
Special Forums Hardware Cannot boot from scsi cdrom Post 302658121 by frank_rizzo on Monday 18th of June 2012 11:27:17 PM
Old 06-19-2012
it would help to provide hardware details on the system and components you have and what error messages are displayed.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

how do i mount a scsi extrnal cdrom on solaris 2?

ok i have had it i need help i am in 11th grade and i cant figure how to mount the dumb cdrom on the sparcstation 2. i have tried everything i know and it still doesnt see it. by the way this is for school so please help me. Jon aka wixifer (1 Reply)
Discussion started by: wixifer
1 Replies

2. UNIX for Dummies Questions & Answers

boot from external cdrom

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

3. UNIX for Dummies Questions & Answers

boot cdrom error

I'm running a Ultra 60 and having problems booting from the cdrom. This is the error I get, Boot device: /pci@1f,4000/scsi@3/disk@6,0:f File and args: The file just loaded does not appear to be executable. Any know what could be the problem here? I've even tried connecting a 2nd cdrom... (3 Replies)
Discussion started by: merlin
3 Replies

4. UNIX for Dummies Questions & Answers

Cdrom boot problems

Hi Everyone, I have a problem. I'm trying too reinstall sun solaris 8.0 on may Sunfire 280r but solaris 9.0 is all ready installed. I tried to boot from cd rom it keeps telling me that File does not seem executable. I need to get Solaris 8.0 on this system. I have boot all ready in single mode... (4 Replies)
Discussion started by: Peterh
4 Replies

5. Solaris

cannot find boot device and won't boot off cdrom

I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies

6. Solaris

Boot from cdrom

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

7. Solaris

not able to boot from cdrom

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

8. Solaris

can't boot cdrom

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

9. Solaris

Boot cdrom - install

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

10. UNIX for Beginners Questions & Answers

Cannot boot cdrom -s

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
fmtmsg(3C)																fmtmsg(3C)

NAME
fmtmsg() - displays formatted message on standard error and console SYNOPSIS
DESCRIPTION
The routine is intended as a language-independent error message service. Messages are displayed on the system console, standard error, or both, depending on the setting of the class parameter. The format of messages is under the control of the user, who may specify how much of the message is to be displayed on standard error. However, the format of the message displayed to the system console is not under user control. All messages specify a class, which indicates the source and status of the error condition, and where the message should be directed. The class may be functionally excluded by specifying If this is done, no message is produced. The class types are: The display class has allowable values of which directs the message to standard error, which directs the message to the system console, or which directs the message to both. The error type class may be one of indicating a hardware error, indicating a software failure, or which indicates a firmware error. The error source class may be one of indicating an application, indicating an OS utility, or indicating a system error. The recovery status class may be one of indicating recovery from the error is possible, or stating no recovery is possible. The remaining parameters are functionally optional, in that the message produced may exclude any or all of them. Each is discussed in parameter order. The label component states where the error originated. It has the form major:minor, where major is a 10 character field specifying the major system producing the message and minor is a 14 character field specifying the subsystem in error. For example, This component can be excluded by setting it to or The severity component describes the degree of importance of the failure. The predefined severity levels are: No severity is specified and no print string is generated. The message is informational only and the string is generated. The situation might be in error, and should be checked. The string is generated. An error has been detected. The string is generated. An unrecoverable error has been detected. The string is generated. The text component describes the nature of the failure in the most specific terms. It is expected to provide a sufficiently detailed account of the error to remove all doubt about its cause. It may be excluded by setting text to or The action component describes the options available for recovery from the error. As output, it is prefaced with the string It may be dis- abled by setting to or The tag component is intended to direct the user to the appropriate documentation to correct or avoid the error. It may be disabled by setting tag to or EXTERNAL INFLUENCES
The user may control the appearance of the message produced on standard error through the use of two environment variables: and These have no effect on the console message. The environment variable describes the components the user is interested in seeing. The value of is a list of one or more components, sep- arated by colons if more than one is specified. All components with non-NULL values listed in are displayed when is called; all other com- ponents are excluded. Only the component names label, severity, text, action, and tag are valid list elements. Any others (or an empty list) are considered an error in format. If is erroneous or unset, produces the full message. The environment variable gives users control over the text string displayed for the severity component if the severity is other than those described above. The predefined severity levels through cannot be overridden. The value of is a list of one or more level specifiers separated by colons. A level specifier is a three item comma list of the form iden- tifier, level, message. The identifier is not used by and is only included for compatibility. It is not optional, however, as expects it when examining level specifiers for the other two parts. The level is a number greater than four indicating the level defined. The mes- sage is a string to be displayed in the field, in the same manner as and are displayed for the and severities. Level specifiers having more or fewer than three items are invalid, as are null level specifiers. Invalid or null valued lists have no impact on the behavior of RETURN VALUE
The routine returns one of the following values on exit: Success. Failure. Failure to standard error, success to the system console. Success to standard error, failure to the system console. AUTHOR
was developed by OSF and HP. SEE ALSO
printf(3S), thread_safety(5). STANDARDS COMPLIANCE
fmtmsg(3C)
All times are GMT -4. The time now is 10:16 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy