Thanks to all the people who send me the comments, specially to:
- Knut Hellebo
- Cliff
- Jude T. Cruz
- Kurt Carlson
- Dr. Thomas P. Blinn
- Paul Kitwin
- Robert L. McMillin
______________________________________________________________________
The first point was to make a backup of the disk with the problem. After
that, I made the disklabel -rw /dev/rrz2c.
Once the disk had the label, I edit it and made the partition avialable. I
rebooted the server to be sure that everythin was ok. It was.
I had no problem after all.
Some of the reasons of this are copied below:
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
I believe this is because it is not strictly necessary to do a disklabel to
build a filesystem if you're using DEC disks. DEC has been known to ship
systems this way, though I think it's very sloppy of them to do
so. I personally would *never* do this.
Could be . . .
What kind of drive is it? What firmware level? I have found that if the
firmware is old (less than 16 on rz29s and 8 on rz28s) you can run into
lots of weirdness, especially on newer controllers.
By the device, I am guessing that the drive is in the cabinet, 3rd drive
down, coming off of the integrated controller.
Could be a dying drive. Could be a failing connector in the BA35X.
Try it in a different slot.
What version of Digital UNIX did you say you are running? It can make a
difference in the messages that come out and what they mean.
I would assume that you're getting the error you see from disklabel because
the drive isn't labelled. As long as all the file systems are located
where the default partition boundaries would put them for the drive in
question, you will be able to mount the file systems even without a disk
label. If you do put a label back on the disk, be sure to edit it to
correspond to the actual uses of the partitions.
It's been a long time since I've used ufs, but I recall it's possible to
create a filesystem on an unlabeled disk... which sounds like what you
have.
Some newer versions of unix don't pay much attention to the disklabel. I do
now with Digital UNIX (v3.2 and higher) and advfs you can relabel a disk
dynamically, I cannot speak for ufs. The obvious caveat is that
you have to make sure the partitions are the same size (or entire disk).
Relabeling may help, but if you don't know exactly what the partitions are
now then don't try it without a backup that's current.
Did you use LSM on that disk ? You are experiencing a problem with BLOCK 0
of the disk, which normally is READ-ONLY. If you are (or were) using LSM,
check the LSM manual about volencap and advfs volumen encapsulation, they
talk about this somewhere.
In any case, if you have data on that disk, BACK UP THE DATA before messing
around with disklabel.
This is normal if the disk is brand new or have been used by another
architecture (eg Sun). Just label the disk and the message will go away. --
I would not touch that label until you back it up. I would guess that you
are using rz2c. It seems that you can use the c partition without labeling
a disk. The symptoms you describe are consistant with someone doing that.
If you don't need to partition the disk, I would leave it alone. If you do
need to use the label features, then you will have to back it up and then
make the changes.
Received on Fri May 16 1997 - 00:18:37 NZST