My original question stated below was answered by several folks. Thanks
for the help!!!
:As I have mentioned in the past, I am new at Unix Admin.
:but I am supposed to upgrade our DEC 3000/400 from
:DU 2.0 to 4.0A. As I prepare for this I have been
:trying to plan for disk space to do a custom installation.
:Part of this was to run -- disklabel -- with no flags, so
:that I could see the partitions on our two disks. When
:I ran -- disklabel rz2 -- I got back the requested information
:but when I ran --- disklabel rz3 --- all that I got was
:the following message:
:
: "Bad pack magic number (label is damaged, or pack is unlabeled)"
:
:My question is -- will this be a problem when I upgrade?
:And if so what do I need to do?
:I did learn that about 3 months ago one of the disks on
:our machine crashed and was replaced but I don't know
:if it was the same disk.
Summary:
The answer to my question was basically no...there will not be any major
problems. But most people suggested that I go ahead and label the disk.
Below are typical responses but probably the most insight came from
Cliff who wrote :
What this probably means is that someone put in the disk and then did a
newfs /dev/rz3c without labeling the disk. I have had a user do this on
a 3.0 that I upgraded to 3.2g, and had no problems. I did take
advantage of the chance to label the disk after the upgrade. I have not
checked with 4.0, but I suspect it would work. As a matter of principle
I think I would have all the disks on my system labeled. I don't know
this for sure, but I suspect that you can only use the c partition on an
unlabeled disk since that is almost universally used as the entire disk.
-cliff
---------------------------------------------------
A similar comment from Alan:
The disk doesn't have a label. It should be a problem, but is
often wise to labels on disks. Sometimes default partition tables
change from version to version and the label ensures that the
size and offset of partitions doesn't move anything around. If
you use the disk as a single big partition, then labeling it
won't be a problem. The label is only the first sector of the
disk and neither file system uses that space. If the disk is
used as raw space (such as for a database), that should be a
problem either.
If the drive is partitioned, you'll want to ensure that when
the disk is labeled the partitions are the same.
Received on Tue Mar 04 1997 - 23:11:29 NZDT