Not possible to boot from disk device of Enterprise 3500

[OFC]

The disk device was running in an Enterprise 3500 (slot 0) three month ago in our lab. Then it was removed in oder to have this disk available for future use. Meanwhile the Enterprise was used for other purposes with other disk devices. Today I tried to boot the station with the "old" disk device without success.
How can I restore the system in oder to boot again from the "old" disk?

 

[daFranze]

do you have any error messages?

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years

 

[OFC]

Hi Franz,
I'm getting the message "the file just loaded does not appaear to be executable".
Best regards, Michael

 

[daFranze]

it's propably a fefective bootblock, or you boot from the wrong disk; make sure it is the rifgt disk; to fix the bootblock use what I "stole" from sunsolve:

Sunsolve-Document-16778

Problem Statement

This document can help you troubleshoot boot processes aborted with the
following (boot)-messages:

Boot load failed - illegal instruction
or
The file just loaded does not appear to be executable
or
A bootblock needs to be installed after restoring root filesystem after
a disk replacement

The information in this document is based on the assumption of a
PATH variable that contains /usr/sbin and /usr/bin. Full paths are
specified for commands or files that normally exist outside these
common directories.

You need to take extra steps to complete the procedure described in this
document if the file systems are under control of disk management software
(such as VERITAS or Solstice[TM] DiskSuite).
Resolution

INSTALLING A BOOT BLOCK AND BOOT PROGRAM (ufsboot)
ON THE SOLARIS[TM] BOOT DISK

1. To be sure that you really need to install a boot block and a boot
program, verify that you are using the correct boot command for your
system:

* If you are booting from a CD-ROM or installing the operating system
(OS) from a CD-ROM, make sure the Solaris[TM] Operating System
(Solaris OS) CD is in the CD-ROM drive and that the CD-ROM is
mounted.

If the machine hangs attempting to boot, halt the machine using
<Stop+a>, or use <L1+a> keyboard sequences to produce
the OK prompt.

* If you are booting from a tape, make sure the correct kernel
architecture tape is being used.

* If you are booting from a disk, make sure that the disk-alias you are
using to boot points to a bootable disk.

2. To install a boot block and a boot program, complete the following
procedure (which applies to file systems residing directly on the disk
(dev/dsk/...) ):

ok boot cdrom -s [boots the CD-ROM to SINGLE USER MODE]
# cd /
# fsck /dev/rdsk/c0t0d0s0
# mount /dev/dsk/c0t0d0s0 /a


*** Solaris OS releases up to 2.4 ***

# cp /ufsboot /a/ufsboot
# cd /
# umount /a
# /usr/sbin/installboot /usr/lib/fs/ufs/bootblk /dev/rdsk/c0t0d0s0
# reboot

*** Solaris 2.5 OS and later releases ***

# cp /platform/`uname -i`/ufsboot /a/platform/`uname -i`/ufsboot
# cd /
# umount /a
# /usr/sbin/installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk
/dev/rdsk/c0t0d0s0
# reboot

Note: c0t0d0s0 is an example of the boot device.
Substitute c0t0d0s0 with the appropriate boot device.
Also, the CD used in this preceding step MUST BE the same Solaris OS
version running on the boot disk. For example, if the boot disk loads
Solaris 2.6 OS, use a Solaris 2.6 OS CD. In multi-disk Solaris
OS distribution, you will use OS disk 1 of 2.

For more details, refer to the installboot(1M) manpage. For
Solaris Operating System (x86 Platform Edition) examples, please
refer to document SRDB 16496, a Symptom/Resolution article.

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years

 

[daFranze]

did this fix the problem?

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years

 

[MadCow79]

I've had the same error message with my Ultra10 and Solaris 9 and using the solution above with 'cp /platform/`uname -i`/ufsboot /a/platform/`uname -i`/ufsboot' and I'm getting the following error message: "cp: cannot access /platform/SUNW,Ultra-5_10/ufsboot". ufsboot is missing. How can this be and what (else) can I do to fix this problem?

 

[daFranze]

did you boot from cdrom? is there an ufsboot on that specific CD? (find / -name ufsboot)

Best Regards, Franz
--
Solaris System Manager from Munich, Germany
I used to work for Sun Microsystems Support (EMEA) for 5 years

 

[MadCow79]

I used 'boot cdrom -s' as stated in the solution above

the 'find' finds some ufsboot files, but not for my hardware
('uname -i' returns 'SUNW,Ultra-5_10')

The cd used to boot is 'Solaris 9 Installation CD' which I downloaded from the Sun website. Do I need to boot from a different CD or with different boot options?