[Bug 508017] New: Unable to format SATA drives when 8Gig of RAM installed fsck fails as well
http://bugzilla.novell.com/show_bug.cgi?id=508017 Summary: Unable to format SATA drives when 8Gig of RAM installed fsck fails as well Classification: openSUSE Product: openSUSE 11.1 Version: Final Platform: 64bit OS/Version: openSUSE 11.1 Status: NEW Severity: Normal Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: roland@logikalsolutions.com QAContact: jsrain@novell.com Found By: --- User-Agent: Opera/9.64 (X11; Linux x86_64; U; en) Presto/2.1.1 64-bit 11.1 from DVD purchased from On-Disk. Asus M2N4-SLI NVidia 8 Gig of RAM 3 SATA drives 250Gig, 1TB, and 1TB This machine had this very install on it prior to Dolphin pooching up a delete and corrupting a partition. I had a 500+Gig /home and 900+Gig /books partition, but those might have originally been created with 64-bit Ubuntu. Clean wipe and re-install attempt has been hitting brick wall for days now. I ran every diagnostic Western Digital provides for those 1TB drives and they show no errors. Doesn't matter if I have RAID turned on or off. I can tell the install to create a partition > 150Gig and format it ext3, but when the format gets out beyond 150Gig the install hangs. Usually a hard lock with dead mouse and keyboard. I have identified the problem though. Nobody tested anything with the maximum configuration. I tried installing Ubuntu 9.10 64-bit and it installed on the first try. No such love with OpenSuSe. In an act of sheer frustration I took 4Gig out of the machine and put in the original 2Gig so I was back down to 6 Gig of RAM. I got past the format stage, but was still unable to install...but I was trying to install on one of the 1TB drives (where I was before). One last attempt, putting the root partition on the 250Gig drive and everything else (including swap) on the pair of TB drives got it all working. This is definitely an OpenSuSE bug. Reproducible: Always Steps to Reproduce: 1.Install 8Gig of RAM in a machine with this motherboard and several SATA drives 2. Try to run the installation procedure formatting partitions larger than 300Gig 3. Actual Results: Hang-o-ramma sometimes crash dump info on screen Expected Results: clean formated partitions with installation continuing. Ubuntu 9.10 64-bit able to cleanly format all partitions and install on this very setup. Only known work around is to remove 2Gig of RAM. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=508017 shuang qiu <sqiu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED CC| |sqiu@novell.com AssignedTo|bnc-team-screening@forge.pr |aschnell@novell.com |ovo.novell.com | -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=508017 User aschnell@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=508017#c1 Arvin Schnell <aschnell@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|aschnell@novell.com |kernel-maintainers@forge.pr | |ovo.novell.com --- Comment #1 from Arvin Schnell <aschnell@novell.com> 2009-07-21 03:05:13 MDT --- "hard lock" indicates a kernel problem. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=508017 User roland@logikalsolutions.com added comment http://bugzilla.novell.com/show_bug.cgi?id=508017#c2 --- Comment #2 from Roland Hughes <roland@logikalsolutions.com> 2009-07-21 06:39:05 MDT --- Judging from the fact removing 2Gig fixed the problem, I'm willing to bet that both routines are calling a service to calculate maximum free memory but using some 32-bit data type which cannot possibly contain the result. Ordinarily this would just result in some bizarre negative number, but they then use that result in a calculation for some kind of allocation which is the root of the hard lock. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=508017 User jeffm@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=508017#c3 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High Status|ASSIGNED |NEEDINFO CC| |jeffm@novell.com Info Provider| |roland@logikalsolutions.com --- Comment #3 from Jeff Mahoney <jeffm@novell.com> 2009-09-02 12:37:37 MDT --- The "sometimes crash dump on the screen" part of it is important. If there is a kernel failure, we need to be able to isolate it. If your analysis is correct and it's that it's doing too large an allocation, it could be the OOM killer, but we'd need to know for certain. Since there can sometimes be a race between an Oops and when it's displayed, can you switch to console mode as root and run "klogconsole -r 0 -l8" and then try to reproduce? That will dump the messages on the current console. The Oops can be big, so providing a photo is fine if you have no other way to capture it. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=508017 User jeffm@novell.com added comment http://bugzilla.novell.com/show_bug.cgi?id=508017#c4 --- Comment #4 from Jeff Mahoney <jeffm@novell.com> 2009-09-02 13:03:17 MDT --- As a note, I have two systems with 8 GB RAM. I don't have a 1 TB disk installed in either of them, but when I use a sparse file I don't run into any problems. The most memory I've seen mkfs take up is about ~ 50 MB. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=508017 http://bugzilla.novell.com/show_bug.cgi?id=508017#c5 Jeff Mahoney <jeffm@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |RESOLVED Info Provider|roland@logikalsolutions.com | Resolution| |NORESPONSE --- Comment #5 from Jeff Mahoney <jeffm@novell.com> 2009-11-24 17:47:29 UTC --- No update in 2 months. Closing as NORESPONSE. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=508017 http://bugzilla.novell.com/show_bug.cgi?id=508017#c6 --- Comment #6 from Roland Hughes <roland@logikalsolutions.com> 2009-11-24 18:01:00 UTC --- There has been no update because I haven't been running OpenSuSE. Given the critical nature of the bug I had to abandon the platform. I'm now running KUbuntu. You still have a bug when a system has 8Gig of RAM and a 1TB disk drive installed. It trashes everything when it attempts to format the drive or run a check on it. Now that 1TB drives are well under $100 you are going to be seeing this problem relentlessly. I simply could not use a platform which was so unstable. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com