Bug 327513

Summary:	Second hard disc reported too small (pata-via)
Product:	[openSUSE] openSUSE 10.3	Reporter:	Forgotten User xI2C5NvggO <forgotten_xI2C5NvggO>
Component:	Basesystem	Assignee:	E-mail List <kernel-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None	CC:	jkosina
Version:	RC 1
Target Milestone:	---
Hardware:	i686
OS:	openSUSE 10.3
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Forgotten User xI2C5NvggO 2007-09-22 19:06:45 UTC

Trying to do a 'new installation' of 10.3 RC1 on my primary test machine, for these tests I use a second 10GB HD, sdb (first HD sda has 10.2 and 'another' OS on it). May be relevant that sdb is ATA66, sda is ATA100

First time round, installer complained it couldn't read partition table (which was created a few weeks ago by a 10.3 Beta 3 installation) - attempting to select manually using 'expert partitioning' YaST insists it is only 4.3GB

Exit & re-boot, BIOS also says 4.3G! so power off and on again and it's back to 10G (which is what it IS).

If instead I put in an install CD for 10.3Beta3 it stays as 10G all the way through to ready-to-install (where I aborted it).

Changed to a 40G drive for sdb and the problem has disappeared - always reports as 40G. This drive is ATA100 though (as is the primary drive sda), the 10G one giving problems is ATA66.

4.3GB looks suspiciously like 2**32 bytes - maybe a bug in pata_via where something uses ulong where it needs more bits?

Not sure what logs might be useful, please advise if required.

Comment 1 Forgotten User xI2C5NvggO 2007-09-22 19:09:24 UTC

Hardware details omitted: it's a Gigabyte GA7VT600 with AMD 2400XP processor & 1G RAM. IDE hard discs.

Comment 2 Forgotten User xI2C5NvggO 2007-09-22 20:35:18 UTC

Booting installer with 'brokenmodules=pata_via' seems to fix the problem. Not sure whether it's YaST or pata_via but one of them is the cause...

Comment 3 Jiri Kosina 2007-09-26 09:20:44 UTC


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