divvy sees NONFS

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 - Thu Dec  9 05:27:35 1999
Xref: world comp.unix.sco.misc:111483
Newsgroups: comp.unix.sco.misc
Path: world!newsswitch.lcs.mit.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!tor-nx1.netcom.ca!news.louisville.edu!uky.edu!xenitec!news
From: "Radek Tomis" <rts@mediumsoft.cz>
Subject: Re: Problem with FS
Resent-From: mmdf@xenitec.on.ca
Submit-To: scomsc@xenitec.on.ca
Content-Type: text/plain;
        charset="iso-8859-2"
Cc: <hlmbourges.info@wanadoo.fr>
Organization: Medium Soft, a.s.
Date: Thu, 9 Dec 1999 08:46:42 GMT
Message-ID: <015401bf4221$f36d6510$8e0314ac@rtsnt> 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
References: <82h10c$aks$1@wanadoo.fr> <384CA505.EAB50B94@inreach.com> <82ii4c$fnr$1@wanadoo.fr> <19991207050711.29007@tegan.com> <384DAC20.36285710@inreach.com> <19991207202840.11396@tegan.com> 
Sender: news@xenitec.on.ca (xenitec.on.ca News Administrator)
Precedence: list
Lines: 81
X-Mozilla-Status: 8010

> From: Tom Parsons <cis@tegan.com>
> Sent: Wednesday, December 08, 1999 3:28 AM

> Pat Welch enscribed:
> |

[...]

> | > | Pat Welch <patubb@inreach.com> a icrit dans le message :
> | > | 384CA505.EAB50B94@inreach.com...
> | > | > Franck GILBERT wrote:
> | > | > >
> | > | > > I need help !!! Please
> | > | > >
> | > | > > At first I have a FS that type is EAFS.
> | > | > > Now this type is No FS.
> | > | > > HELP, how can I do to make it in EAFS (no destructive solution)?

[...]

> | Something obviously hosed his VTOC. What can be done depends on exactly
> | which SCO release you are on.
>
> Not necessarily.  We don't have all of the information but
> pre-OSR5.0.{something} divvy looked on the primary hard disk for the
> filesystem type while about everything else looked at the actual
> filesystem.  Move the second scsi drive from one 3.2v4.2 system to
> another and you will see non-FS.  Or replace the primary drive and
> the secondard will display non-FS.
>
> Someone along the family tree, divvy started looking at the filesystem
> and by 5.0.,5, this nagging annoyance no longer exists.

Tom, I think you are still being a bit mistaken about these problems.

Pre v5.0.0 `divvy` does not look on the primary drive to obtain file system
*type* of corresponding division on the given partition (no matter whether
this partition is on primary or secondary disk).

The problem is that pre v5.0.0 `divvy` scans "/dev" directory (which is
under normal circumstances on the primary drive, of course) to obtain device
*nodes* (e.g. "/dev/root", "/dev/u"), that can be opened to read the
superblock of the corresponding division and determine its filesystem type
(EAFS, HTFS, etc.), if any. If there is no corresponding device node in
"/dev" for the given division (e.g. in situations that you described above),
then pre v5.0.0 `divvy` skips that division and merely displays "NON FS"
(without division name -- device node name in "/dev" -- that could not be
found). This, however, does not mean, that the file system type
"disappeared". Naming that division ('n'ame command in divvy), which creates
corresponding device node name in "/dev", and running `divvy` again usually
fixes the "problem". If not, then the other most usual problem is different
HDD geometry currently in use (other than the one that was in use when the
division table was created).

v5.0.x `divvy` doesn't need "/dev" entries in order to read divisions'
superblocks to obtain file system type. `divvy` creates corresponding
temporary device nodes itself (whether this applies only for missing "/dev"
entries or for all divisions, I don't know at the moment) and read the
superblock from these temporary device nodes to determine file system type.

Conclusion for `divvy`:

OS          division name   FS type   Possible reason/fix
---------------------------------------------------------------------------
pre v5.0.0  not present     NON FS    name the division and run divvy again
pre v5.0.0  present         NON FS    incorrect HDD geometry in use or
                                      division table/superblock overwritten
                                      or bad track table size change
v5.0.x      doesn't matter  NON FS    incorrect HDD geometry in use or
                                      division table/superblock overwritten
                                      or bad track table size change

Incorrect HDD geometry is usually caused by SCSI adapter change (different
brand or model) for SCSI drives, or LBA/NORMAL setting change for IDE
drives. The original geometry can be determined in most cases.

--
Radek Tomis
rts@mediumsoft.cz

Take Control of Maintaining Your Mac

Take Control of Syncing Data in Leopard

Take Control of Upgrading to Snow Leopard

Take Control of Buying a Mac

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.