Thanks B.R. Stephen
At 09:02 AM 12/17/2001 -0600, you wrote: >On Mon, 17 Dec 2001 22:55:13 +0800 >Stephen Liu <[EMAIL PROTECTED]> implied: > > > Hi, > > > > Thanks for your continuous support and time spent. The problem is now > > solved by re-installing RH7.2. But I am still interested to find out > > its cause and its remedy for future use. > > > > On Monday 17 December 2001 22:18, you wrote: > > > > > Does a bootdisk work? If so, it's probably a geometry mismatch. If > > > not, or if you didn't make a bootdisk to try it with, there's more > > > work. Here's what's needed if you can't test it with a bootdisk or > > > it failed using that, too. > > > > A bootdisk worked but have to use 'I', the interactive operation, to > > turn off WINE. How to find out geometry mismatch ? > > > > > The second stage boot loader has been started, but it can't load > > > the descriptor table from the map file. This is typically caused > > > by a media failure or by a geometry mismatch. > > > > How to rectify it in future if its failure is due to geometry mismatch > > ? > >That was answered already, in the part about manually partitioning and >using fdisk and (possibly) having to set the proper CHS, etc. > > > Thanks in advance. > > > > B.R. > > Stephen > > > > > I'd first look at the "geometry mismatch" part to see if that's it. > > > If it's "media failure" that's so broad as to be almost impossible > > > to track down. But if it meant that the drive was bad (one possible > > > definition) then you'd never be able to get it to boot all of the > > > way no matter what. > > > > > > The easiest way to check the geometry is to first find out what the > > > geometry of the drive should be. Most times it's labelled right on > > > it. In some, you'll need to lok on the website somewhere to find > > > out. > > > > > > Then restart the installation. When you get to disk partitioning, > > > choose fdisk. At the commandline enter "p" to see what you have. 3 > > > things that you should note. First, does it have the right number of > > > CHS specified for what you know it should be? Second, take a look at > > > the "blocks" column and see if there are any plus (+) signs attached > > > to any of the numbers. Third, are there any overlaps of partitions > > > (i.e. sda1 ends on 100 and sda2 starts on 100)? > > > > > > If the first instance is a problem, you'll need to go into expert > > > mode and fix it (too long of an explanation on how, so grab some > > > howtos and start reading). If the second one is a problem, you'll > > > need to repartition (maybe even manually) to fix it. (I allowed the > > > installer to auto partition for me once and it ended up like this. I > > > used it that way for over 1.5 years before I finally fixed it. A > > > bootdisk will usually still work if it's this problem.) If the third > > > part is it, same as the second part: repartition and likely do so > > > manually to prevent the problem > > > > > > That's about the best shot I can make at this point. _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
