Summary: Can't get second hard disk to boot

From: Christopher E. Olaes (colaes@hercules.nhlbi.nih.gov)
Date: Mon Jun 03 1996 - 14:15:11 CDT


Summary Can boot second disk:

Thanks to all who replied...
First of all I wrote down, that the machine I was trying to boot was a sun3.
That was incorrect it is actually a sun4e.

And since the os on this machine is sunos4.0.3e, the eeprom values were quite
different...

Anyway the reason why I could not boot from my machine from a specified disk
using the command....boot sd(,2,1) was that the eeprom was set incorrectly.

There is an eeprom value called: sd-targets...followed by a sequence...like
012345678... The sequence on my eeprom was 201345678... I guess what it does
is map this sequence to the scsi targets... Therefore, target 2 becomes target
0 and target 0 becomes target 1.

So I set the sd-targets variable it back to 012345678 and it worked fine...

Thanks to all who replied.....

Chris

>
> Forwarded message:
> >From colaes Fri May 24 17:02:28 1996
> Subject: More problems
> To: sun-managers@ra.mcs.anl.gov (Sun-Managers Group)
> Date: Fri, 24 May 1996 17:02:28 -0400 (EDT)
> X-Mailer: ELM [version 2.4 PL24]
> MIME-Version: 1.0
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: 7bit
> Content-Length: 1868
>
>
> HI Everyone,
>
> I have a sun3 that has a bad hardisk which is actually the system disk.
> The system has another hard disk and I am attempting to copy all the files
> and partitions over to this disk.
>
> My plan was to make the second disk the new system disk and then I could
> get rid of all together the system disk....
>
> After I was completed with that I ran the installboot utility to init
> the boot sector on this second disk, and proceeded to halt the system.
>
> I then did a probe-scsi a the boot prom...
>
> And say that the system disk (disk1) was target 0
> And the second disk (new system disk) was target 2
> on the same scsi controller.
>
> So I did the following command.
>
> boot sd(,8,1)
> But this did not work
>
> The error message I got was:
> Booting from: sd(0,8,1)
> Invalid SCSI target number ffffffd0 Can't open boot device
> Available devices
> SCSI disk [disk-device] (sd)
> SCSI tape [tape-device] (st)
> vm [network-device] (vm)
> le [network-device] le
>
> At this point, I don't now what else to do.... I have tried
> other paramenters to boot from...but I just can't seem to get
> my second disk to boot.
>
> IF anyone has anything they would like to share with me on
> how I can boot the second disk.. I would be extremely greatful..
>
> Thanks
> Chris
>
> --
> --------------------------------------------------------------------------
> - Christoper E. Olaes National Institutes of Health -
> - Network Engineer Lab of Cardiac Energetics -
> - -
> - Telephone: 301-496-0941 Building 10, Room B1D-161A -
> - FAX: 301-402-2389 Bethesda, MD 20892-1061 -
> - Pager: 301-701-4442 -
> - Email: colaes@zeus.nhlbi.nih.gov -
> --------------------------------------------------------------------------
>
>
> --
> --------------------------------------------------------------------------
> - Christoper E. Olaes National Institutes of Health -
> - Network Engineer Lab of Cardiac Energetics -
> - -
> - Telephone: 301-496-0941 Building 10, Room B1D-161A -
> - FAX: 301-402-2389 Bethesda, MD 20892-1061 -
> - Pager: 301-701-4442 -
> - Email: colaes@zeus.nhlbi.nih.gov -
> --------------------------------------------------------------------------
>

-- 
******************************************************************************
*** Chris Olaes				            Network Administrator  ***
***                        Intercom: 25                                    ***
***                        Pager: 301-701-4442                             ***
***                        colaes@hercules.nhlbi.nih.gov                   ***
****************************************************************************** 



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:00 CDT