(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Printer Friendly Version



reconstructing dparam disk geometry changed


What is this stuff?

If this isn't exactly what you wanted, please try our Search (there's a LOT of techy and non-techy stuff here about Linux, Unix, Mac OS X and just computers in general!):



From: Bela Lubkin <belal@caldera.com>
Subject: Re: OSR 5.0.6a Strange problem after BIOS upgrade FLASH and IDE
Date: Wed, 16 Jan 2002 23:05:26 GMT
References: <20020113144645.I14415@mammoth.ca.caldera.com> <Pine.SC5.4.43.0201161231040.3858-100000@xenau105.zenez.com> 

Boyd Lynn Gerber wrote:

> On Sun, 13 Jan 2002, Bela Lubkin wrote:
> > Since you have a new blank-slate Unix install on the 80GB drive, and
> > have the 40GB drive in place, you're most of the way there.  You need to
> > do something like:
> >
> >   strings -a /dev/rhd20 | grep cyls= > /tmp/old-parms
> 
> I found 9693 128 63 as the correct parameters.
> 
> >   dparam /dev/rhd10                         # print existing parms
> >   dparam /dev/rhd10 cyls hds ... cyls secs
> 
> dparam /dev/rhd20 9693 128 0 0 0 8 19157 63 and setting the bios to auto
> was the solution.
> 
> I have found through a bit of testing that after a HD has been installed
> and working to not run the BIOS HD detect when adding a new HD.  It is
> better to manually set it up with the proper HD settings.
> 
> Thanks to every one.  I was finally able to recover my friends data.



You seem to think that the most important thing learned here is "don't
run BIOS HD detect after the HD is already working with OpenServer".  I
say you've learned something far more important (which ought to be
written up for the FAQ).

That is: if you _do_ run the BIOS HD detect, and lose control of the
drive, you can recover it.

First, learn the "right" parameters according to Unix.  You might have
previously recorded them, might be able to `strings` the drive, might be
able to examine /usr/adm/messages or /usr/adm/syslog from a prior backup
of the drive.  Or you might, in fact, be able to use one of the BIOS's
parameter sets (does 9693/128/63 match any of the configs the BIOS came
up with?)  -- that is, it may be the case that even with the BIOS
claiming the same parameters as it always did, you still need to have
Unix restamp the drive.

Second, restamp the drive.  That means getting the Unix kernel up and
running, could be from a boot floppy, the install CD with "tools", a 3rd
party crash recovery floppy (RecoverEDGE, AirBag, etc.), or by putting
in a different hard disk and doing a minimal install.  Get to a shell
prompt.  Find or create a device node that points to the drive in
question (/dev/rhd00 if it's primary/master; could be rhd10 or something
else).  Run:

  dparam -w /dev/rhd00
  dparam    /dev/rhd00
            # or rhd10 or whatever

to print existing parameters, then run:



  dparam    /dev/rhd00 cyls hds ppp qqq rrr sss cyls secs
            # or rhd10 or whatever

where ppp/qqq/rrr/sss are the middle 4 of the existing parameters, and
cyls/hds/secs are the "right" parameters.  "cyls" gets stamped twice,
once for the size of the drive and once for landing zone.

Third, go into BIOS setup and set the drive back to "auto".

Fourth, if necessary, rearrange drives (e.g. if this was once, and is
desired again to be the boot drive, move it back to primary/master).

This won't necessarily work in all cases, it's just _one_ discovered way
of recovering from an IDE disk geometry problem.  Also, steps "Second"
and "Third" might need to be done in the reverse order, and you will
probably have to change things again in the BIOS if you physically
rearrange drives.

>Bela<
 



Click here to add your comments



Don't miss responses! Subscribe to Comments by RSS or by Email

Click here to add your comments


If you want a picture to show with your comment, go get a Gravatar



/Bofcusm/1410.html copyright 1997-2004 (various authors) All Rights Reserved

Have you tried Searching this site?

Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.

Publishing your articles here

Jump to Comments



Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.



More:
       - OSR5
       - Bofcusm
       - Bela


Unix/Linux Consultants

Skills Tests

Guest Post Here











My Favorites

Change Congress