SUMMARY: Problem booting Solaris 2.5.1 x86 on SCSI disk.

From: Dennis F. Morse (dmorse@Morsesoft.COM)
Date: Fri Mar 27 1998 - 03:48:13 CST


ORIGINAL QUESTION:

>I have Solaris 2.5.1 x86 installed on a SCSI disk on a Dell PowerEdge 2100.
>All the recommended patches are installed and it runs great. However,
>I need to have a dual boot capability and have installed a seconds SCSI
>disk as target 0 and changed the original disk from target 0 to target 1.
>
>With the boot disk changed from SCSI target 0 to target 1 and the system
>will no longer boot. I can select the Solaris secondary boot loader and I
>enter "b -r" to reconfigure the kernel. I finds the kernel and starts to
>boot, but fails with the following error.
>
> eip(e040a7cc), eflags(10206), ebp(e050e0c8), uesp(e040259e), esp(050e0a0)
> eax(24), ebs(e0500003), exc(e050fbff), edx(24), esi(3), edi(0)
> cr0(80050033), cr2(24), cr3(64d000)
> cs(158) ds(160) ss(24) es(160) fs(1a8) gs(1b0)
> panic: Page Fault
> BAD TRAP
> Page Fault
> Kernel fault at addr=0x24, pte=0x0
> pid=0, pc=0xe040a7cc, sp=0xe040259e, eflags=0x10206
>
>I've tried all the tricks I know for SPARC systems, but can't get the system
>to boot. Specifically,
>
> 1) /etc/vfstab has been edited and c0t0 changed to c0t1.
> 2) touch /reconfigure
> 3) Moved /etc/path_to_inst to /etc/path_to_inst.old and created a
> new file with one line consisting of a `#'.
>
>I also have noticed the same problem on another system after a second
>Adaptec 2940-UW PCI SCSI card was installed. If the original card was
>moved or the second card installed in a lower PCI slot then the original
>the system failed to boot with an error similar to the one above.
>
>I checked SunSolve, the sun-manager archives, and the Sun-Managers and
>Solaris 2.x FAQs and didn't see any help. Can anyone shed some light on
>this? Surely the OS doesn't have to be reinstalled just to move a SCSI disk!
>
>I will summary, and thanks in advance.
>
>Dennis Morse
---------

ANSWERS:

I got two replies. Thanks to Ning Zhang and Joel Lee.

 o Ning Zhang <btinz@ui.uis.doleta.gov>
        there is a possibility that your IRQ setting has conflict. If you
        can't find problem from Solairs side, check cmos and the irq setting.

 o Joel Lee <jlee@thomas.com>
        Under the CMOS, did you specify of the existence of these changes?

Neither of these were my particular problem. I kept trying different things
and when I enabled the verbose flag in the Secondary x86 boot loader I saw
the reference to "/etc/bootrc". Not being as experienced with Solaris x86 I
wasn't aware of this file.

I found a reference to it in the SunSoft ``Solaris 2.5.1 x86 Device
Configuration Guide,'' in Appendix A, Post Installation Configuration, pages
45-47. It describes how to reconfigure the system to move an EISA adapter.
In my case it was the SCSI target ID, but the concepts are the same.
I performed the following steps to switch the SCSI target ID from 0 to 1.

    1. edit /etc/bootrc and change the line

            setprop boot-path /pci@0,0/pci9004,8078@12/cmdk@0,0:a
        to
            setprop boot-path /pci@0,0/pci9004,8078@12/cmdk@1,0:a

    2. Saved /etc/path_to_inst as /etc/path_to_inst.sav and created
        a new file with a single line containing a `#' character.

    3. Edited /etc/vfstab and changed the string /c0t0 to /c0t1.

    4. touched /reconfigure.

    5. Rebooted the system.

The system is now running great with Windows NT 4.0, Linux 2.0.31, and
Solaris 2.5.1 installed. I'm using the Linux LILO loader as the master
boot loader with options for all three OSes.

Regards,

Dennis Morse



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:34 CDT