05-18-2010
Boot issues Solaris 10 + V440
Hello,
I've a very weird problem with one of the machines. When I try to boot off a working DVD that I used to install another system with it spits out the following message:
Sun Fire V440, No Keyboard
Copyright 2007 Sun Microsystems, Inc. All rights reserved.
OpenBoot 4.22.33, 8192 MB memory installed, Serial #63056041.
Ethernet address 0:3:ba:c2:28:a9, Host ID: 83c228a9.
System is operating in Service Mode.
Rebooting with command: boot cdrom -s
Boot device: /pci@1e,600000/ide@d/cdrom@0,0:f File and args: -s
Bad magic number in disk label
Can't open disk label package
Can't mount root
Evaluating:
The file just loaded does not appear to be executable.
{1} ok
SC Alert: Maximum Boot Failures on Host.
I've tried with 4 different DVDs but still to no avail. I cannog find any useful information on google as well.
Could someone give me a hint on how to solve this problem?
I have to re-install the operating system on the machine.
Thanks!
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
i'm having 2 problems.
1. the system will always look to boot from the net. i've changed the prom settings so that it boots from the disk, by entering "setenv boot-device disk0:3", but the system still seems to want to boot from the net.
2. i replaced my creator3d with an elitem6 and i did... (6 Replies)
Discussion started by: xyyz
6 Replies
2. Solaris
Hi Friends,
My solaris box V440 got stucked. I couldn't accessit from the remote console. Finally i restarted the box.
Can you tell me what are the ways we can find out the issues
and what are the logs we can check other than /var/log/messages.
Thanks
Jinu (1 Reply)
Discussion started by: Jinu
1 Replies
3. Solaris
I have a pentium IV with 512 MB ram and 80 GB HDD.
I first installed windows XP on the first primary partition, then Solaris on the second with 20 GB for the solaris partition, and when rebooted , the grub menu functioned as expected giving me the options to dual boot, so next I wanted to install... (3 Replies)
Discussion started by: saagar
3 Replies
4. Solaris
Hi:
I bougth an used Sun Fire v440, and It have a firmware password. When I turn on the server, it ask for firmware password. (I don 't know what is the correct password). I can access to SC, but when I want to access to OBP, Firmware Password appears again. I remove the battery for two hours,... (1 Reply)
Discussion started by: mguazzardo
1 Replies
5. Solaris
Got a T2000 which has got the 2.5" SAS drives. Want to be able, if I can, to connect to USB caddy and connect to a V440.
Anyone ever tried this? To be honest, having problems even finding a SAS-USB caddy. (0 Replies)
Discussion started by: psychocandy
0 Replies
6. Solaris
Hi,
I have Sun Fire V440. Boot disks are mirrored. system crashed and it's not coming up. Error message is
Insufficient metadevice database replicas located. Use Metadb to delete databases which are broken.
Boot disks are mirrored and other disks are ZFS configuration. Please... (2 Replies)
Discussion started by: samnyc
2 Replies
7. Solaris
Hi,
I have Sun Solaris V440, every two days or so, the system crashes and it's at OK prompt. After that I do the FSCK and clear all the bad sectors. Then system stays up for close to 48 hours. Then it crashes again. I checked the logs and I don't see anything under /var/adm/messages file.
... (1 Reply)
Discussion started by: samnyc
1 Replies
8. Solaris
Hi,
I have a SUN Fire V440 server running Solaris 8. One of the 4 disks do not appear when issued the format command. The "ready to remove" LED is not on either.
Metastat command warns that this disk "Needs maintenace". Can I just shutdown and power off the machine and then insert an... (5 Replies)
Discussion started by: Echo68
5 Replies
9. Solaris
Hi there,
I have a V440 Server based on Sun Microsystem with Solaris OS.
Is there any way to auto power on the system only with cabling the V440 with 220 v?
Thanks! (10 Replies)
Discussion started by: proof_enrique
10 Replies
10. Red Hat
I am installing Red Hat Linux 6.9 as a VM in Hyper-V on an HP laptop running Windows 10. After the install completes and the VM reboots, it gives me the message, "Detected CPU Family 6 model 142; Warning: Intel CPU model - this hardware has not undergone testing by Red Hat and might not be... (1 Reply)
Discussion started by: tigers580307
1 Replies
LEARN ABOUT SUNOS
installboot
installboot(1M) installboot(1M)
NAME
installboot - install bootblocks in a disk partition
SYNOPSIS
installboot bootblk raw-disk-device
The boot(1M) program, ufsboot, is loaded from disk by the bootblock program which resides in the boot area of a disk partition.
The ufs boot objects are platform-dependent, and reside in the /usr/platform/platform-name/lib/fs/ufs directory. The platform name can be
found using the -i option of uname(1).
The installboot utility is a SPARC only program. It is not supported on the architecture. users should use installgrub(1M) instead.
bootblk The name of the bootblock code.
raw-disk-device The name of the disk device onto which the bootblock code is to be installed; it must be a character device which is read-
able and writable. Naming conventions for a SCSI or IPI drive are c?t?d?s? and c?d?s? for an IDE drive.
Example 1: Installing UFS Boot Block
To install a ufs boot block on slice 0 of target 0 on controller 1 of the platform where the command is being run, use:
example# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk
/dev/rdsk/c1t0d0s0
/usr/platform/platform-name/lib/fs/ufs
directory where ufs boot objects reside.
/platform/platform-name/ufsboot
second level program to boot from a disk or CD
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
od(1), uname(1), boot(1M), init(1M), kadb(1M), kernel(1M), monitor(1M), reboot(1M), rpc.bootparamd(1M), init.d(4), attributes(5)
WARNINGS
The installboot utility fails if the bootblk or openfirmware files do not exist or if the raw disk device is not a character device.
11 Apr 2005 installboot(1M)