Sponsored Content
Full Discussion: Sun Ultra 30 boot problems
Operating Systems Solaris Sun Ultra 30 boot problems Post 303040024 by gull04 on Tuesday 22nd of October 2019 04:33:11 AM
Old 10-22-2019
Hi,

You'll have to check the nvram contents and set them accordingly, a short term fix to get the system back up would be from the ok ptompt. Run the command boot disk or boot disk1this should boot you into the OS.

From there you can reset the contents using the the eeprom command see man eeprom.

Regards

Gull04

Last edited by gull04; 10-22-2019 at 05:35 AM.. Reason: Wrong code tags.
This User Gave Thanks to gull04 For This Post:
 

10 More Discussions You Might Find Interesting

1. Solaris

sun ultra or sun sparkstation

am wonder wich sun computer is better, a sun ultra or sun sparkstation, and what is the difference (7 Replies)
Discussion started by: nobody
7 Replies

2. Solaris

sun ultra

Hi Guys, I have a 2nd hand Sun ultra-5, I wanted to know how to be able to run it as a normal window. I do not have any experience whatsoever with solaris/unix. Does anyone can give me a clue where to start. When I switch it goes to: unix console login: pa$$word: #UNIX sendmail : enable to... (0 Replies)
Discussion started by: lingosa
0 Replies

3. Solaris

Ultra 60 strange disk problems

Hello, I just bought a nice ultra 60 with 2x36gb scsi disks (fujitsu MAJ3364MC, sun partnr 540-4521). If i do a probe-scsi-all in obp the disk anounces itself as SUN36G. In a booted system however, I can only use 9 gb and the disk is seen in format as 9.0 gb. My own wild uneducated... (4 Replies)
Discussion started by: poltergeist
4 Replies

4. Solaris

Ultra 60 won't boot

I just was given an Ultra 60 that I'm trying to get started so that I can re-load the system with Solaris 10. I can't seem to get the system to boot past the initial memory check. I've tried to do an Stop-A to get to the eeprom, but can't do that. My next step is to try to send a break from the... (0 Replies)
Discussion started by: zosojohnny
0 Replies

5. Solaris

ultra 10 boot warning---corrupt label

Hi All, Any idea why i'm having this warning during boot: WARNING: /pci@1f,0/pci@1,1/ide@3/dad@1,0 (dad1): corrupt label - wrong magic number This happens after I added another ide HD and reinstall it from solaris 10 to solaris 8. Thanks in advance. (7 Replies)
Discussion started by: itik
7 Replies

6. Solaris

Sun Sparc Ultra 4 won't boot - disk errors

Hi all. I am seeing in one of our less-used servers that it crashed and now won't restart. I get the message 'continue with normal startup or boot into maintenance mode'. I go into maintenance and run fsck on /usr0 (mentioned in error at restart) it then reboots but goes right back to... (3 Replies)
Discussion started by: jamie_collins
3 Replies

7. UNIX for Dummies Questions & Answers

SUN Ultra 10 won't boot - Help Please

Folks; My SUN Ultra 10 5.9 won't boot. It only stops after counting the memory on the white screen then hangs there with nothing. even the power button won't take it down from there, i had to unplug it then re-plug it again. i inserted a disk with Solaris 9 iso trying to rebuild it but nothing... (1 Reply)
Discussion started by: Katkota
1 Replies

8. Solaris

Ultra 5 will not boot from DVD ROM :(

Hi, I just got a new Ultra 5 and replaced the CD-ROM with an LG DVD-ROM (approved and listed in Sun HCL). Got the DVD-ROM installed to install Solaris 10. Im just learning and new to Solaris installation. When I insert a Solaris 10 DVD I see that it gets mounted and File Manager opens and... (8 Replies)
Discussion started by: greypilgrim
8 Replies

9. Solaris

Ultra 45 Boot Loop

I am trying to get an old Ultra 45 to boot and it is stuck in a loop. I cannot get anything to come up on a monitor, so when I hook up a serial connection to the TTYa interface I see the following output: @(#)OBP 4.21.2 2005/12/22 17:17 Sun Ultra 45 Workstation Clearing TLBs Loading... (0 Replies)
Discussion started by: Madrox72
0 Replies

10. UNIX for Beginners Questions & Answers

Sun ultra 30 boot problem

Hi all, I've got a Sun ultra 30 workstation. the Nvram battery died so I replaced it. I reprogrammed the mac address using the mlpl command all that so it booted without error. But for some reason I was trying to boot via the network. So I did a STOP A and boot disk1 which is the alias for my SCSI... (2 Replies)
Discussion started by: robbo007
2 Replies
EEPROM(8)						    BSD System Manager's Manual 						 EEPROM(8)

NAME
eeprom -- display or modify contents of the EEPROM or openprom SUN 3 SYNOPSIS eeprom [-] [-c] [-f device] [-i] [field[=value] ...] SPARC, SPARC64, MACPPC and PREP SYNOPSIS eeprom [-] [-c] [-f device] [-i] [-v] [field[=value] ...] DESCRIPTION
eeprom provides an interface for displaying and changing the contents of the EEPROM or openprom. The eeprom tool is only installed on sup- ported platforms. Without any arguments, eeprom will list all of the known fields and their corresponding values. When given the name of a specific field, eeprom will display that value or set it if the field name is followed by '=' and a value. Only the super-user may modify the contents of the EEPROM or openprom. The options are as follows: - Commands are taken from stdin and displayed on stdout. -c eeprom will fix incorrect checksum values and exit. This flag is quietly ignored on systems with an openprom. -f device On systems with an EEPROM, use device instead of the default /dev/eeprom. On systems with an openprom, use device instead of the default /dev/openprom. -i If checksum values are incorrect, eeprom will ignore them and continue after displaying a warning. This flag is quietly ignored on systems with an openprom. The following options are valid only on the SPARC and will produce an error when used on a Sun 3: -v On systems with an openprom, be verbose when setting a value. Systems with an EEPROM are always verbose. The -v option is also present on sparc64, macppc, and prep systems. FIELDS AND VALUES
The following fields and values are for systems with an EEPROM: hwupdate A valid date, such as ``7/12/95''. The strings ``today'' and ``now'' are also acceptable. memsize How much memory, in megabytes, is installed in the system. memtest How much memory, in megabytes, is to be tested upon power-up. scrsize The size of the screen. Acceptable values are ``1024x1024'', ``1152x900'', ``1600x1280'', and ``1440x1440''. watchdog_reboot If true, the system will reboot upon reset. Otherwise, the system will fall into the monitor. default_boot If true, the system will use the boot device stored in bootdev. bootdev Specifies the default boot device in the form cc(x,x,x), where 'cc' is a combination of two letters such as 'sd' or 'le' and each 'x' is a hexadecimal number between 0 and ff, less the prepending '0x'. kbdtype This value is ``0'' for all Sun keyboards. console Specifies the console type. Valid values are ``b&w'', ``ttya'', ``ttyb'', ``color'', and ``p4opt''. keyclick If true, the keys click annoyingly. diagdev This is a string very similar to that used by bootdev. It specifies the default boot device when the diagnostic switch is turned on. diagpath A 40-character, NULL-terminated string specifying the kernel or standalone program to load when the diagnostic switch is turned on. columns An 8-bit integer specifying the number of columns on the console. rows An 8-bit integer specifying the number of rows on the console. ttya_use_baud Use the baud rate stored in ttya_baud instead of the default 9600. ttya_baud A 16-bit integer specifying the baud rate to use on ttya. ttya_no_rtsdtr If true, disables RTS/DTR. ttyb_use_baud Similar to ttya_use_baud, but for ttyb. ttyb_baud Similar to ttya_baud, but for ttyb. ttyb_no_rtsdtr Similar to ttya_no_rtsdtr, but for ttyb. banner An 80-character, NULL-terminated string to use at power-up instead of the default Sun banner. Note that the secure, bad_login, and password fields are not currently supported. Since the openprom is designed such that the field names are arbitrary, explaining them here is dubious. Below are field names and values that one is likely to see on a system with an openprom. NOTE: this list may be incomplete or incorrect due to differences between revisions of the openprom. sunmon-compat? If true, the old EEPROM-style interface will be used while in the monitor, rather than the openprom-style interface. selftest-#megs A 32-bit integer specifying the number of megabytes of memory to test upon power-up. oem-logo A 64bitx64bit bitmap in Sun Iconedit format. To set the bitmap, give the pathname of the file containing the image. NOTE: this property is not yet supported. oem-logo? If true, enables the use of the bitmap stored in oem-logo rather than the default Sun logo. oem-banner A string to use at power up, rather than the default Sun banner. oem-banner? If true, enables the use of the banner stored in oem-banner rather than the default Sun banner. ttya-mode A string of five comma separated fields in the format ``9600,8,n,1,-''. The first field is the baud rate. The sec- ond field is the number of data bits. The third field is the parity; acceptable values for parity are 'n' (none), 'e' (even), 'o' (odd), 'm' (mark), and 's' (space). The fourth field is the number of stop bits. The fifth field is the 'handshake' field; acceptable values are '-' (none), 'h' (RTS/CTS), and 's' (Xon/Xoff). ttya-rts-dtr-off If true, the system will ignore RTS/DTR. ttya-ignore-cd If true, the system will ignore carrier detect. ttyb-mode Similar to ttya-mode, but for ttyb. ttyb-rts-dtr-off Similar to ttya-rts-dtr-off, but for ttyb. ttyb-ignore-cd Similar to ttya-ignore-cd, but for ttyb. sbus-probe-list Four digits in the format ``0123'' specifying which order to probe the sbus at power-up. It is unlikely that this value should ever be changed. screen-#columns An 8-bit integer specifying the number of columns on the console. screen-#rows An 8-bit integer specifying the number of rows on the console. auto-boot? If true, the system will boot automatically at power-up. watchdog-reboot? If true, the system will reboot upon reset. Otherwise, system will fall into the monitor. input-device One of the strings ``keyboard'', ``ttya'', or ``ttyb'' specifying the default console input device. output-device One of the strings ``screen'', ``ttya'', or ``ttyb'' specifying the default console output device. keyboard-click? If true, the keys click annoyingly. sd-targets A string in the format ``31204567'' describing the translation of physical to logical target. st-targets Similar to sd-targets, but for tapes. The default translation is ``45670123''. scsi-initiator-id The SCSI ID of the on-board SCSI controller. hardware-revision A 7-character string describing a date, such as ``25May95''. last-hardware-update Similar to hardware-revision, describing when the CPU was last updated. diag-switch? If true, the system will boot and run in diagnostic mode. FILES
/dev/eeprom The EEPROM device on systems with an EEPROM. /dev/openprom The openprom device on systems with an openprom. /dev/nvram The nvram device on PReP systems. SEE ALSO
ofctl(8) BUGS
The fields and their values are not necessarily well defined on systems with an openprom. Your mileage may vary. There are a few fields known to exist in some revisions of the EEPROM and/or openprom that are not yet supported. Most notable are those relating to password protection of the EEPROM or openprom. Avoid gratuitously changing the contents of the EEPROM. It has a limited number of write cycles. The date parser isn't very intelligent. BSD
February 27, 2007 BSD
All times are GMT -4. The time now is 08:29 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy