Problem with FS
Franck GILBERT
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)?
Franck GILBERT
Pat Welch
Use divvy to re-id the EAFS partition, making sure that the create new
FS column says NO.
What version of SCO? And what happened that caused the problem?
--
---------------------------------------------
Pat Welch, UBB Computer Services
SCO Authorized Reseller
Unix/Hardware/BB Sales & Support
Year 2000: Consulting and Repairs
*** 26 Days left 'til 1/1/2000 **
(209) 745-1401 Fax: (209) 745-5640
Nationwide pager: (800) 608-7122
E-mail: pat...@inreach.com
----------------------------------------------
Franck GILBERT
problem.
Like you write me, I use divvy and I use the t(ype) command at the main menu
but, I have the next error : division already in use, filesystem type may
only be selected for new filesystem ....
Thank
Pat Welch <pat...@inreach.com> a écrit dans le message :
384CA505...@inreach.com...
Tom Parsons
| Pat, I use a system V release 3.2. I dont know what that caused this
| problem.
| Like you write me, I use divvy and I use the t(ype) command at the main menu
| but, I have the next error : division already in use, filesystem type may
| only be selected for new filesystem ....
You received erroneous advice.
The correct advice is:
DO NOTHING.
You can't change the filesystem type without destroying the contents of
the filesystem and the non-FS entry is not causing any problems. Leave
it alone.
<and>
Run "uname -X" and find out what release you have. It will be displayed
on the Release line. Include this in future posts because it usually
is needed for correct answers.
--tom
|
| Pat Welch <pat...@inreach.com> a icrit dans le message :
| 384CA505...@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)?
| > >
| > > Franck GILBERT
| >
| > Use divvy to re-id the EAFS partition, making sure that the create new
| > FS column says NO.
| >
| > What version of SCO? And what happened that caused the problem?
| >
| > --
| > ---------------------------------------------
| > Pat Welch, UBB Computer Services
| > SCO Authorized Reseller
| > Unix/Hardware/BB Sales & Support
| > Year 2000: Consulting and Repairs
| > *** 26 Days left 'til 1/1/2000 **
| > (209) 745-1401 Fax: (209) 745-5640
| > Nationwide pager: (800) 608-7122
| > E-mail: pat...@inreach.com
| > ----------------------------------------------
|
--
==========================================================================
Tom Parsons t...@tegan.com
==========================================================================
Pat Welch
Arrgh. Sorry, Franck and Tom!
Fortunately divvy won't do what I had you mistakenly try.
That's what happens when I'm in a hurry and misread what was written. I
was thinking of renaming a partition when you're upgrading from 4.x and
you want to mount the old disk to copy stuff. Mea Culpa.
Something obviously hosed his VTOC. What can be done depends on exactly
which SCO release you are on.
--
---------------------------------------------
Pat Welch, UBB Computer Services
SCO Authorized Reseller
Unix/Hardware/BB Sales & Support
Year 2000: Consulting and Repairs
*** 25 Days left 'til 1/1/2000 **
Tom Parsons
|
| Fortunately divvy won't do what I had you mistakenly try.
|
| That's what happens when I'm in a hurry and misread what was written. I
| was thinking of renaming a partition when you're upgrading from 4.x and
| you want to mount the old disk to copy stuff. Mea Culpa.
|
| 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.
Radek Tomis
> Sent: Wednesday, December 08, 1999 3:28 AM
> Pat Welch enscribed:
> |
[...]
> | > | Pat Welch <pat...@inreach.com> a icrit dans le message :
> | > | 384CA505...@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
r...@mediumsoft.cz