Bug 219769

Summary:	YaST isn't able to handle sscsi devices on em64t on installation
Product:	[openSUSE] openSUSE 10.2	Reporter:	Tim Arnold <tarnold>
Component:	YaST2	Assignee:	Thomas Fehr <fehr>
Status:	RESOLVED DUPLICATE	QA Contact:	Jiri Srain <jsrain>
Severity:	Normal
Priority:	P5 - None
Version:	Beta 2
Target Milestone:	---
Hardware:	64bit
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	/tmp/YaST2/y2log /tmp/YaST2/y2start.log

Description Tim Arnold 2006-11-10 10:45:40 UTC

This bug appears on two HP ProLiant (zert35.suse.de / zert45.suse.de)

Machine Specs:

Label           : Proliant DL360G4 (1HE Rackserver)
S/N             :
Mainboard       : HP proprietary Proliant DL360G4
Chipset         : Intel E7520
BIOS            : ProLiant System BIOS - P54 (06/01/2005)
Processor(s)    : 2x (4x log.) Intel Xeon 3.60 GHz/800 MHz(2 Mbyte L2) EM64T
RAM             : 2x 1GB PC2700 DDR ECC CL2,5 Reg. DIMMs = 2 GByte
Graphics        : (onboard) ATI Rage XL, 8192 kByte SGRAM
Ethernet NIC    : (onboard) 2x HP NC7782 (Broadcom NetXtreme BCM5704) Gigabit
IDE Controller  : (onboard) Intel 6300ESB Ultra ATA Storage Controller
CD-ROM Lw       : 1x COMPAQ CRN-8245B, ATAPI CD-ROM drive
RAID            : 1x SmartArray P600 SAS-to-RAID (256MB)
RAID BIOS       :    Firmware v1.18
HDDs            : 1x Hotplug HP DG036A8B53, SAS, 36 GByte 2.5" am P600
Floppy-Lw       : (none)
Bus-Slots       : CHECK: 2x PCI-X 64Bit/100+MHz
PowerSupply     : CHECK: 1x HotSwap HP DPS-460BB B, max. 460W



During installation an error message occurs that says: "parted isn't able to handle device /dev/XXXX". In the partitioner module of yast you can see the device, but without any information out of the partition table and it is not possible to create or edit any partiton. Performing fdisk or parted on a console properly works, so it must be a bug in YaST. I'll add /var/log/YaST2 as an attachement.

Comment 1 Tim Arnold 2006-11-10 10:47:32 UTC

Created attachment 104629 [details]
/tmp/YaST2/y2log

Comment 2 Tim Arnold 2006-11-10 10:48:33 UTC

Created attachment 104630 [details]
/tmp/YaST2/y2start.log

Comment 3 Hannes Reinecke 2006-11-13 08:55:08 UTC

I have nothing to do with YaST2.

Comment 4 Stefan Hundhammer 2006-11-13 10:53:51 UTC

Steffen, since Thomas Fehr isn't available, please have a look at this. Also please evaluate the severity of this issue. Is this really a blocker?

Comment 5 Steffen Winterfeldt 2006-11-13 11:50:20 UTC

After looking at the code it seems it doesn't deal with /dev/cciss/cXdX
properly because of the additional directory level. At least the
cXdX part is lost along the way, but I've no idea how to fix the code up.

Seems we have to wait for Thomas.

Anyway, I don't see this as blocker as only smartarray controller are
affected and that's more a typical sles hardware.

Comment 6 Thomas Fehr 2006-11-13 12:10:00 UTC

This is also reported as #219496 and yes, the fix will have to wait until I
am back from vacation unless someone is willing to dive into depths of libstorage.

Comment 7 Alexander Osthof 2006-11-28 09:12:32 UTC


*** This bug has been marked as a duplicate of bug 223460 ***