On Tuesday 28 December 2004 12:16 pm, Andrew Brown wrote:
There is a known flaw in the version of parted shipped with suse 9.1, and possibly 9.0, which leads to strangeness reading LBA drives. I ran into this problem a couple of weeks ago, and there is a fix posted on the Suse web site. I don't know if that is your problem (one of th esymptoms is that the computer won't boot into windows after Suse has been installed) but it might be worth looking at. The diagnostic for me was that yast crashed with a segfault every time I tried to run the partition manager sectio of it, which clearly relies on parted. If you google the archives of this list for a message headed "sudden excitement in a partition table" you'll find what I did to fix it.
According to your previous post, you updated parted, changed the BIOS to recognize the drive as LBA instead of AUTO and sent added "hda=3737,255,63" to your boot options. Unfortunately, I've got the most current version (parted-1.6.6-43) of parted that I can find for SuSE 9.0 from their ftp server. I tried changing the BIOS setting but that didn't help and adding "hdb=3737,255,63" (it's the primary/slave drive on her system) didn't help. I also tried passing the exact c,h,s numbers from the bios but had no luck. At this point, I think I'm going to pull the drive and try attaching it to a Windows box with DVD burner. That's not going to be fun, but if I backup everything she's got then I can wipe that drive and put a better filesystem than FAT on it and she'll get all her data back. Thanks to everybody who tried helping out. -- "Only two things are infinite, the universe and human stupidity, and I'm not sure about the former." - Albert Einstein Mark McKibben http://www.coffeebear.net/