mkfdmn problem

[Amanda Deer]

I am trying to create a domain on a new disk. I can disklabel it ok, but when I try to make the domain it just sits there doing nothing. Any ideas?

[Ivan Ferreira]

What is the command that you are using?

What is the output, or just hang?

Can you sucessfully dd to the disk to read and write some data?

[Amanda Deer]

Command is mkfdmn /dev/disk/dsk30c test

and it just hangs.

[Michael Schulte zur Sur]

Hi,

can you post
disklabel -r dsk30
file /dev/rdisk/dsk30c
?
Any errors in binary errorlog?

greetings,

Michael

[Ivan Ferreira]

Try this and verify that the command does not hangs. If the command hangs, there may be a hardware problem:

dd if=/dev/disk/dsk30c of=/dev/null bs=1024 count=100000

dd if=/dev/zero of=/dev/rdisk/dsk30c bs=1024 count=100000

Is this a local (DAS) disk or a SAN (or SCSI storage) disk?

[Amanda Deer]

dcs1a # file /dev/rdisk/dsk30c
/dev/rdisk/dsk30c: character special (19/699) SCSI #15 "HSZ70" disk #14 (SC
SI ID #2) (SCSI LUN #3) errors = 4/0

dcs1a # disklabel -r dsk30
# /dev/rdisk/dsk30c:
type: SCSI
disk: HSZ70
label:
flags:
bytes/sector: 512
sectors/track: 254
tracks/cylinder: 20
sectors/cylinder: 5080
cylinders: 41986
sectors/unit: 213291762
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 # ~Cyl values
a: 131072 0 unused 0 0 # 0 - 25*
b: 262144 131072 unused 0 0 # 25*- 77*
c: 213291762 0 unused 0 0 # 0 - 41986*
d: 0 0 unused 0 0 # 0 - 0
e: 0 0 unused 0 0 # 0 - 0
f: 0 0 unused 0 0 # 0 - 0
g: 106449273 393216 unused 0 0 # 77*- 21031*
h: 106449273 106842489 unused 0 0 # 21031*- 41986*


Output from dd - the first command came back ok, and the second command returned this message.

dcs1a # dd if=/dev/zero of=/dev/rdisk/dsk30c bs=1024 count=100000
dd write error: Read-only file system
1+0 records in
0+0 records out

[Venkatesh BL]

Have you 'write-protect'ed the disk by any chance?

[Amanda Deer]

Not that I'm aware of.

[Venkatesh BL]

Because, the error suggests that the disk is 'read-only' (Note that the first command reads from the disk and the second command tries to write to the disk).

I would suggest that you check if the disk was configured as read-only on the controller side.

[Amanda Deer]

Logged onto the controller and looked at the unit. It says NOWRITE_PROTECT.