[opensuse-factory] 10.3 RC1 installation - (Second) hard disc seen as wrong size
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). First time round, installer complained it couldn't read partition table (which was created a few weeks ago by a 10.3 Beta installation) - attempting to select manually using 'expert partitioning' YaST informed me it was 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). Try again after using fdisk to delete partitions - no complaint from YaST but we're back to 4.3G. I'm trying to continue but suspect that once power is cycled it will be very unhappy. 4.3GB looks suspiciously like 2**32 bytes - maybe a bug where something uses ulong where it needs more bits? Anyone else see this? -- Richard (MQ) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2007/9/22, Richard (MQ) <osl@16hd.freeserve.co.uk>:
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).
First time round, installer complained it couldn't read partition table (which was created a few weeks ago by a 10.3 Beta installation) - attempting to select manually using 'expert partitioning' YaST informed me it was 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 the bios stated 4.3G, then You has a hardware problem, not a software problem! And if the HD is of only 10 GB, it's a little old and probably at the end of his days. Regards --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Juan Erbes wrote:
2007/9/22, Richard (MQ) <osl@16hd.freeserve.co.uk>:
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).
First time round, installer complained it couldn't read partition table (which was created a few weeks ago by a 10.3 Beta installation) - attempting to select manually using 'expert partitioning' YaST informed me it was 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 the bios stated 4.3G, then You has a hardware problem, not a software problem!
And if the HD is of only 10 GB, it's a little old and probably at the end of his days.
I take your point, but this disc has been used for this same purpose for about a year (some alpha and all beta & gold OpenSuSE releases) without showing anything like this. I've never seen anything similar before... I will try a different disc and report back to this thread before raising a bug. -- Cheers Richard (MQ) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2007/9/22, Richard (MQ) <osl@16hd.freeserve.co.uk>:
Juan Erbes wrote:
2007/9/22, Richard (MQ) <osl@16hd.freeserve.co.uk>:
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).
First time round, installer complained it couldn't read partition table (which was created a few weeks ago by a 10.3 Beta installation) - attempting to select manually using 'expert partitioning' YaST informed me it was 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 the bios stated 4.3G, then You has a hardware problem, not a software problem!
And if the HD is of only 10 GB, it's a little old and probably at the end of his days.
I take your point, but this disc has been used for this same purpose for about a year (some alpha and all beta & gold OpenSuSE releases) without showing anything like this. I've never seen anything similar before...
I will try a different disc and report back to this thread before raising a bug. --
Verify that the problem not resides in the mobo or chipset. I forgot this detail. What chipset has You mobo? regards --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
I will try a different disc and report back to this thread before raising a bug. --
Verify that the problem not resides in the mobo or chipset. I forgot this detail.
What chipset has You mobo?
It's a Gigabyte GA7VT600 with AMD 2400XP processor & 1G RAM. Used quite heavily for several years, now relegated to primary test machine. It has run various flavours of OSL from 10.0 onwards with no problems at all YaST's hardware info says it's using pata_via for the hard discs. Installation completed with no further problems, still ok after power cycle. If I enter BIOS after power-on, drive reports 10G but as soon as 10.3RC1 starts (and pata_via is loaded?) it switches to 4.3G. If instead I put in a 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 and the problem has disappeared - always reports as 40G. This drive is ATA100 though (as is the primary drive sda), the one giving problems is ATA66. I think this is a bug in pata-via and have accordingly opened bug #327513 Regards, -- Richard (MQ) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
YaST's hardware info says it's using pata_via for the hard discs.
I think this is a bug in pata-via and have accordingly opened bug #327513
And indeed 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... (this added to bug report too) -- Regards, Richard (MQ) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On Sat, 22 Sep 2007, Richard (MQ) wrote:
YaST's hardware info says it's using pata_via for the hard discs.
I think this is a bug in pata-via and have accordingly opened bug #327513
And indeed 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... (this added to bug report too)
Maybe this is fixed by the solution to https://bugzilla.novell.com/show_bug.cgi?id=325552 -- Andreas Vetter Fakultaet fuer Physik und Astronomie Universitaet Wuerzburg --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Andreas Vetter wrote:
On Sat, 22 Sep 2007, Richard (MQ) wrote:
YaST's hardware info says it's using pata_via for the hard discs. I think this is a bug in pata-via and have accordingly opened bug #327513 And indeed 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... (this added to bug report too)
Maybe this is fixed by the solution to https://bugzilla.novell.com/show_bug.cgi?id=325552
I think not, but hard to test - it only occurs when booting the install DVD, default is to load pata_via after (correctly) detecting the mobo. The fix that you reference is to use a different kernel, but I don't feel like trying to modify the DVD to do so - too much of a challenge! I'll wait and see what the Novell / OpenSuSE team think next week, but my guess is a bug in the installer which loads the wrong module. Of course it's just possibly a bug in the module itself, maybe triggered by two discs of different DMA rate capability. -- Regards, Richard (MQ) --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Andreas Vetter -
Juan Erbes -
Richard (MQ)