Bug 157778

Summary:	System does not boot SLES9 SP3 with external SCSI Storage
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Joseph Salisbury <jsalisbury>
Component:	Kernel	Assignee:	E-mail List <kernel-maintainers>
Status:	RESOLVED INVALID	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P1 - Urgent
Version:	RC 4
Target Milestone:	---
Hardware:	x86-64
OS:	SLES 9
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Joseph Salisbury 2006-03-13 21:48:48 UTC

We were running SLES9 with the 2.6.5-7.244-smp kernel.  We decided to upgrade to SLES9 SP3 to get an asyncio bug fix.  The SP3 kernel we are using is 2.6.5-7.244-smp.  However, the SLES9 with SP3 will not boot with external scsi storage attached.  

The version of SLES9 with the 2.6.5-7.244-smp kernel boots fine with the external scsi storage.  However, as soon as we upgraded to SP3, the system would no longer boot - unless we disconnected the external storage.  

The system is an AMD based IBM eSeries 366.  We are running the x86_64 version of the kernel.  The boot disk is an internal SAS driver, which uses the adp94xx provided by IBM.

We think that the new SP3 kernel is looking for the boot disk on the external storage.  That might be the reason the system does not boot.  However, that dosen't explain why the system will boot with the old version of SLES9.  Maybe the SP3 kit changed some config files and loads the modules in a differant order?

Comment 1 Greg Kroah-Hartman 2006-03-14 19:00:06 UTC

Changing the priority isn't going to do anything :)

Anyway, you say this is SLES9, yet you have SUSE Linux 10.0 as the product.

Which is it?

Comment 2 Joseph Salisbury 2006-03-14 19:05:56 UTC

We are running SLES9.  The problem showed up after applying SP3.  

We would have selected SLES9 for the product.  However, the bugzilla drop down box only offered SUSE Linux 10.0 and SUSE Linux 10.1.  There was no product option of SLES9.

Comment 3 Greg Kroah-Hartman 2006-03-14 19:12:23 UTC

That is because you need to go through the proper support proceedure
for SLES9 issues.  Please contact your support representitive and they 
will start the process for you.

Am closing this for now.

Comment 4 Joseph Salisbury 2006-03-14 19:19:31 UTC

Thanks for the help!