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.
If I’m willing to either let huge chunks go un-used or slice everything below 150Gig, I can get past the format stage of install.
Is this a known OpenSuSE 11.1 64-bit issue? Have there been patches applied? If so I can probably get an updated install DVD from On-Disk, just don’t want to waste the time getting one to find out I’m no better off?
Is it safe to use SystemRescue or Ubuntu 64-bit to create the partitions, then just have OpenSuSE use them? I’ve run into issues with partitions created by different distros before…especially FAT-32 ones, but imagine ext3 will have similar issues across distros.
I have many things I could create the partitions with, I want to know if it is a known bug and if it would be “safe” to create them with another tool. I imagine this “bug” will cascade out to other tools like FSCK and eventually cause issues.
It’s not related to ext3 limits ext3 - Wikipedia, the free encyclopedia
As to what it is I’m not guessing. In my limited opinion it is related to the disk or software but not necessarily as apps, perhaps your install media is corrupt. The tools should be able to do it.
> I have many things I could create the partitions with, I want to know if
> it is a known bug and if it would be “safe” to create them with another
> tool. I imagine this “bug” will cascade out to other tools like FSCK
> and eventually cause issues.
There should be no problem for using another standardized tools. But better
report it on bugzilla.
I find YaST partitioner a bit “buggy” on openSUSE 11.1 :-/
It’s no more buggy than GParted, which is used by most of the “other” tool sets.
For the record, I downloaded that Parted Magic thing someone in this thread suggested. It wouldn’t even boot. I pretty much expected this given the machine had 8 Gig of RAM at the time. Most 32-bit software is so poorly written it cannot handle running on a machine containing more than its maximum requirements. (Want to have a real laugh? Put 8 Gig of RAM into a machine running Windows XP Professional and watch it go through an endless reboot cycle.)
I ended up loosing pretty much everything from the evening of 05/09 forward until today. Heavy sigh.
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.
> It’s no more buggy than GParted, which is used by most of the “other”
> tool sets.
Well, I said that because a few days ago I had to fill a bugzilla for YaST
partitioner: making partitions from 11.1 LiveCD with YaST was not possible
(partition started at cylinder “1” instead “0”), so I had to use another
existing system (openSUSE 10.3) to make those partitions.
