Admins,
Following the replacement of a faulty disk (DS-RZ1DD-VW via HSZ70) I find I am unable to disklabel the new disk.
Questions such as this have been posted before but I'm looking for reasurence.
Results are as follows:
root > disklabel -p rrz20
# /dev/rrz20a:
type: SCSI
disk: HSZ70
label:
flags:
bytes/sector: 512
sectors/track: 169
tracks/cylinder: 20
sectors/cylinder: 3380
cylinders: 5257
sectors/unit: 17769177
rpm: 3600
interleave: 1
trackskew: 7
cylinderskew: 26
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize cpg] # NOTE: values not exact
a: 131072 0 unused 0 0 # (Cyl. 0 - 38*)
b: 262144 131072 unused 0 0 # (Cyl. 38*- 116*)
c: 17769177 0 unused 0 0 # (Cyl. 0 - 5257*)
d: 0 0 unused 0 0 # (Cyl. 0 - -1)
e: 0 0 unused 0 0 # (Cyl. 0 - -1)
f: 0 0 unused 0 0 # (Cyl. 0 - -1)
g: 8687980 393216 unused 0 0 # (Cyl. 116*- 2686*)
h: 8687981 9081196 unused 0 0 # (Cyl. 2686*- 5257*)
root > disklabel -r rrz20
Disk is unlabeled or, /dev/rrz20a is not in block 0 of the disk
root > disklabel -e rrz20
"/tmp/EdDk.aaatrda" 29 lines, 1059 characters
# /dev/rrz20a:
type: SCSI
disk: HSZ70
label:
flags:
bytes/sector: 512
sectors/track: 169
tracks/cylinder: 20
sectors/cylinder: 3380
cylinders: 5257
sectors/unit: 17769177
rpm: 3600
interleave: 1
trackskew: 7
cylinderskew: 26
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0
8 partitions:
# size offset fstype [fsize bsize cpg] # NOTE: values not exact
a: 2221147 0 unused 0 0 # (Cyl. 0 - 657*)
b: 2221147 2221147 unused 0 0 # (Cyl. 657*- 1314*)
c: 2221147 4442294 unused 0 0 # (Cyl. 1314*- 1971*)
d: 2221147 6663441 unused 0 0 # (Cyl. 1971*- 2628*)
e: 2221147 8884588 unused 0 0 # (Cyl. 2628*- 3285*)
f: 2221147 11105735 unused 0 0 # (Cyl. 3285*- 3942*)
g: 2221147 13326882 unused 0 0 # (Cyl. 3942*- 4600*)
h: 2221148 15548029 unused 0 0 # (Cyl. 4600*- 5257*)
Attempting to write a new label
root > disklabel -rw rrz20
disklabel: ioctl DIOCSDINFO: Open partition would move or shrink
Use alternate partition
I believe this is because there is an orphaned lock on this disk and a reboot is required to clear it. Is this correct? Any advice?
TIA
Lawrie
Received on Wed Aug 28 2002 - 11:03:36 NZST