Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Problem Resolution Sure Solution 1008903.1 : Ultra[TM] 60: Error: Server unable to boot with error message: MSGREJ not expected
PreviouslyPublishedAs 212251 Symptoms Ultra 60 unable to bootup. Following error messages are displayed on the console. WARNING: /pci@1f,4000/scsi@3 (glm0): MSGREJ not expected WARNING: /pci@1f,4000/scsi@3 (glm0): got SCSI bus reset WARNING: /pci@1f,4000/scsi@3/sd@0,0 (sd0): SCSI transport failed: reason 'reset' : retrying command The glm error messages repeats numerous times until system panics with panic string unable to mount root filesystem and reboots. /pci@1f,4000/scsi@3/sd@0,0 is the U60's boot disk. - Can boot cdrom into single-user mode. - fsck passes on all slices on boot disk. - Can mount root filesystem on /a. - format-->analyze-->read tests on c0t0d0 passes with no SCSI errors. - Any attempts to boot from boot disk fails with above MSGREJ errors. Resolution 1. One reason seen to cause these boot failures and MSGREJ errors are invalid entries in the /kernel/drv/sd.conf file. sd.conf with invalid entries: name="sd" class="scsi" class_prop="atapi" target=0 lun=0; target=0 lun=1; target=0 lun=2; target=0 lun=3; target=0 lun=4; target=0 lun=5; sd.conf with corrected entries: name="sd" class="scsi" class_prop="atapi" target=0 lun=0; name="sd" class="scsi" target=0 lun=1; name="sd" class="scsi" target=0 lun=2; name="sd" class="scsi" target=0 lun=3; name="sd" class="scsi" target=0 lun=4; name="sd" class="scsi" target=0 lun=5; - boot cdrom -s - mount root filesystem to /a - vi /a/kernel/drv/sd.conf to correct invalid entries - umount /a - init 6 2. Another reason for this error is due to an invalid setting for 'scsi_options' in the /etc/system file. For example, in one customer case, the scsi_options variable was set to 0x43ff8 (the default on solaris 8 and 9 is 0x107ff8), removing the customized setting (which is not needed) allowed the system to boot normally. Product Ultra 60 Workstation MSGREJ, scsi_options, sd.conf, boot Previously Published As 49494 Change History Date: 2005-04-05 User Name: 97961 Action: Approved Comment: Publishing. No further edits. Version: 3 Date: 2005-04-05 User Name: 97961 Action: Accept Comment: Version: 0 Date: 2005-04-05 User Name: 35753 Action: Approved Comment: 1) Wording change. 2) formatting (STM). Ready for FR. Version: 0 Date: 2005-04-04 User Name: 35753 Action: Accept Comment: Version: 0 Date: 2005-04-04 User Name: 97961 Action: Reassign Comment: As per: http://kmo.central/vbp/Knowledge-Process-Updating.htm This need to be TRed. Please note: - Updates although minor must go through the TR process. Knowledge Engineers are now subject matter experts and cannot pass judgement on updates to minor technical info changes. - Being a TR yourself does not mean that you can move the document directly to "Final Review". It needs to be verified by another party in the TR stage. - The updater/author cannot be the TR for the same document. Version: 0 Date: 2005-04-04 User Name: 26973 Action: Approved Comment: simply added another reason for this message to this doc. please do final review. Version: 0 Date: 2005-04-04 User Name: 26973 Action: Update Started Comment: want to add my latest escalation onto what is in this doc. Version: 0 Date: 2003-05-20 User Name: Administrator Action: Migration from KMSCreator Comment: updated by : Sophia Naudin comment : No comment date : Dec 13, 2002 updated by : Dean Clausen comment : Title and spellcheck. - Issued date : Dec 13, 2002 updated by : Vincent Tram comment : Article created. date : Dec 12, 2002 updated by : Vincent Tram comment : No comment date : Dec 12, 2002 updated by : Vincent Tram comment : added properites and permissions date : Dec 12, 2002 Version: 0 Product_uuid 29fbc43a-0a18-11d6-8111-b340515b0ffc|Ultra 60 Workstation Attachments This solution has no attachment |
||||||||||||
|