The gui-install failed for some reason. Looks like bad initialization on 
variables or something because the install succeeded fine. There is a 
bug open on this, please add your data to it:6652722 SXDE GUI installer 
sometimes crashes unexpectedly.

Please attach logs and add your specific info. As for the FMA error, I 
don't know..

sarah
****

Miroslav Nachev wrote:
> Hi Sarah,
>
> Please find the attached logs as gz archive:
> /var/sadm/system/logs/install_log
> /var/sadm/system/nsi/gui-install_log_2008_01_27
>
>> When you say you received Installation Failed, I assumed the GUI 
>> reported this to you? 
> Yes, that message was reported from GUI Installer.
>
>> Which would certainly cause a failure in boot. I am assuming you 
>> can't boot at all? 
> No, the system works fine and the graphics also. There are some error 
> messages but the system is working.
>
>
> Regards,
> Miro.
>
>
> Sarah Jelinek wrote:
>> Miroslav,
>>
>> Nothing in the install log data indicates a failure. Do you have the 
>> gui-install_log available? And, if you could send both of the 
>> install_log and gui-install_log in their entirety? gzip them up or 
>> something. When you say you received Installation Failed, I assumed 
>> the GUI reported this to you?
>>
>> As for the problem events it looks like you have a failure in your 
>> motherboard. Which would certainly cause a failure in boot. I am 
>> assuming you can't boot at all?
>>
>> sarah
>> ****
>>
>> Miroslav Nachev wrote:
>>> Hi,
>>>
>>> At the end of my Solaris installation I received the following 
>>> notification "Installation Failed". The last 5 rows of the 
>>> "Installation Log" are:
>>> *Installing boot information
>>> - Updating boot environment configuration file
>>> - Installing boot blocks (c1d0)
>>> - Installing boot blocks (/dev/rdsk/c1d0s0)
>>> <OM> Enabled Nwam for first reboot
>>> *
>>> After rebooting the system starts but in booting time I have the 
>>> following problem event:
>>> *... EVENT-ID: aa937e27-4cd9-c55e-a894-ce3c0b55062a
>>> ... A problem was detected for a PCIEX device.
>>> ... Refer to http://sun.com/msg/PCIEX-8000-0A for more information.
>>> ... AUTO-RESPONSE: One or more device instances may be disabled
>>> ... IMPACT: Loss of services provided by the device instances 
>>> associated with this fault
>>> ... REC-ACTION: Schedule a repair procedure to replace the affected 
>>> device.  Use fmdump -v -u <EVENT_ID> to identify the device or 
>>> contact Sun for support.
>>> *
>>>
>>> Follow the event dump:
>>> *# fmdump -v -u aa937e27-4cd9-c55e-a894-ce3c0b55062a
>>> TIME                 UUID                                 SUNW-MSG-ID
>>> Jan 27 10:58:54.0375 aa937e27-4cd9-c55e-a894-ce3c0b55062a PCIEX-8000-0A
>>>   100%  fault.io.pciex.device-interr
>>>         Problem in: 
>>> hc://:product-id=S5000PSL:chassis-id=.........:server-id=cosmos/motherboard=0/hostbridge=0/pciexrc=0/pciexbus=1/pciexdev=0/pciexfn=0/pciexbus=2/pciexdev=2/pciexfn=0/pciexbus=4/pciexdev=0/pciexfn=0
>>>  
>>>
>>>            Affects: 
>>> dev:////pci at 0,0/pci8086,25f7 at 2/pci8086,3500 at 0/pci8086,3518 at 
>>> 2/pci8086,3476 at 0 
>>>
>>>                FRU: hc:///component=motherboard
>>>           Location: MB
>>> *
>>> Please find the attached log file with more details.
>>>
>>> Can you give some ideas and suggestions how to solve the problem?
>>>
>>>
>>> Regards,
>>> Miro.
>>>   
>>> ------------------------------------------------------------------------ 
>>>
>>>
>>> _______________________________________________
>>> install-discuss mailing list
>>> install-discuss at opensolaris.org
>>> http://mail.opensolaris.org/mailman/listinfo/install-discuss
>>>   
>>
>

Reply via email to