Problem with add disk

kijan1 · *nix forums beginner Joined: 09 Jun 2006 Posts: 3

Hello All,

I have follows problem:
I added new SCSI disk to DS10 serwer.
Are recognized via system as rz24 and I want add it to
LSM configuration, but I cant initialize it. After use command disklabel I have errors.

#disklabel rz24
Invalid disk label (label is corrupted, or disk is unlabeled)
# disklabel -wr rz24a
disklabel: write block 0: I/O error
# disklabel -z rz24
Disk is unlabeled or, /dev/rrz24a is not in block 0 of the disk
# disklabel -p rz24
# /dev/rrz24a:
type: SCSI
disk: BD009634
label:
flags: dynamic_geometry
bytes/sector: 512
sectors/track: 168
tracks/cylinder: 20
sectors/cylinder: 3360
cylinders: 5273
sectors/unit: 17773524
rpm: 10016
interleave: 1
trackskew: 75
cylinderskew: 85
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 - 39*)
b: 262144 131072 unused 0 0 # (Cyl. 39*- 117*)
c: 17773524 0 unused 0 0 # (Cyl. 0 - 5289*)
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: 8690154 393216 unused 0 0 # (Cyl. 117*- 2703*)
h: 8690154 9083370 unused 0 0 # (Cyl. 2703*- 5289*)

How can I initialize this disk ???

Operating system: Digital UNIX V4.0F
disk type: COMPAQ BD0096349A

#scu show edt

Device: 51024H2 Bus: 0, Target: 0, Lun: 0, Type: Direct Access
Device: CDR-8435 Bus: 1, Target: 0, Lun: 0, Type: Read-Only Direct Access
Device: BD0096349A Bus: 3, Target: 0, Lun: 0, Type: Direct Access

Any idea ???

Best Regards
Kijan

captain · *nix forums beginner Joined: 20 Feb 2005 Posts: 8

Try disklabel -w xxx
where xxx is the disk you are trying to initialise. The use of -r when
the disk genuinely has no label is I think an error in the man page and
I have advised HP of this not so long ago.
regards
stuart mckenzie

kijan1 wrote:

Jack Estes · *nix forums beginner Joined: 11 Oct 2005 Posts: 14

The good Captain is absolutely right; I just checked on a properly
patched 4.0g system so I bet it's there on 4.0e as well.

Why not just zero the label to be safe so you know where you're
starting:
disklabel -z rz24

Then write an initial bootable label to the disk with
disklabel -rw rz24

Then you should can have a look at the resulting label with just
disklabel rz24

And if all is well, go ahead and encapsulate or whatever LSM thingy you
want to do.

I keep wanting to type "dskXX" because it's been so long since I've had
to play with 4.0 devices but now it's stuck in my head and I know I'm
going to screw something up tomorrow at work...Probably time to sign
off and drink this naming scheme out of my head ;-)

Jack

kijan1 wrote:

kijan1 · *nix forums beginner Joined: 09 Jun 2006 Posts: 3

Hello,

So, today I work according with yours sugest and still I can't add label to my disk:

# disklabel -w rz24a
disklabel: ioctl DIOCWDINFO: No disk label on disk;
use "disklabel -wr" to install initial label

When I want to zero label I have follows answare:

# disklabel -z rz24a
Disk is unlabeled or, /dev/rrz24a is not in block 0 of the disk

I used LSM utility also and had follows result:

# voldiskadm

Logical Storage Manager Support Operations
Menu: LogicalStorageManager/Disk

1 Add or initialize a disk
2 Encapsulate a disk
3 Remove a disk
4 Remove a disk for replacement
5 Replace a failed or removed disk
6 Mirror volumes
7 Move volumes from a disk
8 Enable access to (import) a disk group
9 Remove access to (deport) a disk group
10 Enable (online) a disk device
11 Disable (offline) a disk device
list List disk information

? Display help about menu
q Exit from menus

Select an operation to perform: 1

Add or initialize a disk
Menu: LogicalStorageManager/Disk/AddDisk

Use this operation to add a disk to a disk group. You can
select an existing disk group or create a new disk group. You
can also initialize a disk without adding it to a disk group,
which leaves the disk available for use as a replacement disk.
This operation takes, as input, a disk device or partition and
a disk group (or none to leave the disk available for use as a
replacement disk). If you are adding the disk to a disk
group, you will be asked to give a name to the disk.

Select disk device to add [<disk/partition name>,list,q,?] rz24a
voldisk: Warning couldn't update disklabel on rz24a
Disk device rz24a appears to have never been used with LSM.
If rz24a contains valid data then you should encapsulate the
disk partition instead of initializing it as a new LSM disk

Do you wish to encapsulate rz24a? [y,n,q,?] (default: n) y

You can choose to add this disk to an existing disk group, to
create a new disk group, or you can choose to leave the disk
available for use by future add or replacement operations. To
create a new disk group, select a disk group name that does not
yet exist. To leave the disk available for future use, specify
a disk group name of "none".

Which disk group [<group>,none,list,q,?] (default: rootdg) none

The requested operation is to initialize disk rz24a and to leave
this disk free for use as a spare disk.

Continue with operation? [y,n,q,?] (default: y)

Initialize a disk
Menu: LogicalStorageManager/Disk/AddDisk

Initialize a disk
Menu: LogicalStorageManager/Disk/AddDisk

Initialization of disk device rz24a failed.
Error:

The disklabel for /dev/rrz24a does not exist or is corrupted.
Quitting ....

Disk initialization for rz24a completed successfully.

What I do wrong ???

regards
Kijan1

captain · *nix forums beginner Joined: 20 Feb 2005 Posts: 8

Try dropping the partition letter
disklabel -w rz24
and let us know whether you get same error.
regards
jsm
kijan1 wrote:

kijan1 · *nix forums beginner Joined: 09 Jun 2006 Posts: 3

Hi,

When I used command without letter as disk partition, answare is the same:

# disklabel -w rz24
disklabel: ioctl DIOCWDINFO: No disk label on disk;
use "disklabel -wr" to install initial label

Kijan

captain · *nix forums beginner Joined: 20 Feb 2005 Posts: 8

OK. Read the man page for disklabel carefully. Try all the options -
I dont think you can do any harm providing you specify the correct
disk!
For example -W may allow writing to the pack area, or try using the raw
definition of the disk or its partition eg /dev/rrz24c. One or other
of the options will eventually get you there. This happened to me when
changing from Linux labelled disks to Tru64, but I got there in the end
- I just don't remember the exact sequence other that you HAD to drop
the r because the system cannot read info written by another operating
system.
regards
jsm

kijan1 wrote:

Jack Estes · *nix forums beginner Joined: 11 Oct 2005 Posts: 14

Kijan:

As I read through your posts, I see that your command syntax generates
two different errors depending upon whether or not you specify a
partition in the special device name. If you give it a partition, the
command complains that the partition isn't at block 0 so the existing
disklabel (if there really is one) might not even specify an "a"
partition. Maybe partition c is at block zero. Nevertheless, by NOT
specifying a partition letter, it should just try to write an initial
label to the disk using a default partition table.

A good way to verify what's on that disk now IF you have a graphics
head on the system or have an X server running is to run diskconfig and
select rz24. You may get lucky and be able to partition, label, and add
that thing to whatever domain you want right there.

I did notice that the error you got when you did NOT specify a
partition letter prompted you to use the syntax "disklabel -wr rz24"
instead of just "disklabel -w rz24". Have you tried that?

I suppose you could also put that disk in machine that was running some
other operating system and see if you can format it with that O/S's
tool, then put it back in the Alpha and see if you can disklabel it
then. Are you sure the disk is completely healthy in the first place?

Hope that helps.

Jack

Google