Hello All,
original and update message below. Compaq support came through with the
anwser, to:
root2: disklabel -Fs dsk9c unused
This worked where disklabel -wr, combined with rebooting, and the CDE Disk
Configuration utility didn't. He explained it as the partition table
wasn't being updated, the partition table being in the first 16 blocks of
the disk 0-15, and the partitions are in blocks 16 plus. Also noteable,
initially we used the file command to the raw partition "file
/dev/rdisk/dsk9c , and dsk9a" to confirm we were communicating to the
device.
I received quick responses from Murtaza Talawala, Timothy Brown, Dr. Thomas
Blinn and John Venier. I've included Dr Blinn's response as it provided
direction that something was written to the disk, and recommended a format.
It turns out the condition dsk9 was in, the scu utility replied that dsk9a,
or dsk9c was not attached to a SCSI device.
>>>>START from Dr. Blinn
Something got written onto the disk. After you reboot (to assure you don't
have stale in-memory data), try a low-level format on the disk (use the "scu
-f /dev/rdisk/dsk9a format" command to get it started, or do "scu -f
/dev/rdisk/dsk9a" from the command line and look at the format help, then
use the format subcommand and wait for it to complete). Then re-label the
disk, reboot again, and you should be able to do the mkfdmn correctly. In
fact, I'd probably do the format first, before the first reboot.
<<<<<<END from Dr. Blinn
Best Regards, Blake
-----Update Message-----
Hello All,
I incorrectly pasted the wrong error message for the advscan -g command. It
is:
Scanning devices rdb1_dmn
Partition Domain Id
Can't open device rdb1_dmna
I haven't had the opportunity to reboot, but can do that tomorrow morning.
-----Original Message-----
Hello Admin Guru's,
I did the mkfdmn command, mistakenly, before I did the disklabel. Now
subsequent mkfdmn commands fail. Were on a fresh install of TRU64 5.1A sp1,
firmware 6.0. The correct sequence would have been:
root2: hwmgr -view dev | grep dsk9
59: /dev/disk/dsk9c SWXCR ctlr-2-unit-0
root2: disklabel -wrt advfs dsk9
root2: mkfdmn dsk9c db1_dmn
Which now fails as:
/dev/disk/dsk9c or an overlapping partition is open.
Quitting ....
mkfdmn: can't create new domain 'db1_dmn'
There's no directory or symbolic link under /etc/fdmns. I've tried rmfdmn,
disklabel -z dsk9, and advscan -g db1_dmn ...which replied with:
/dev/disk/dsk9c or an overlapping partition is open.
Quitting ....
mkfdmn: can't create new domain 'db1_dmn'
Things look pretty much the same for dsk9a to dsk9h under /dev/disk/ and
/dev/rdisk. disklabel -er dsk9 editing "unused" to "AdvFS" had the same
results. Any ideas what to try next?
Best Regards,
Blake Brehl
Anritsu Company United States
root2: disklabel -r dsk9
# /dev/rdisk/dsk9c:
type: SWXCR
disk: SWXCR
label:
flags: dynamic_geometry
bytes/sector: 512
sectors/track: 32
tracks/cylinder: 128
sectors/cylinder: 4096
cylinders: 13017
sectors/unit: 53317632
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
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 - 31
b: 262144 131072 unused 0 0 #
32 - 95
c: 53317632 0 AdvFS 0 0 #
0 - 13016
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: 52924416 393216 unused 0 0 #
96 - 13016
h: 0 0 unused 0 0 #
0 - 0
This message is intended for the use of the individual/entity to whom it is addressed. This message may contain privileged information exempt from disclosure. If you are not the addressee, distribution or copying of this message, or dissemination of the information contained herein is strictly prohibited. If you should receive this message in error, please destroy it, or return to sender, Thank You
Received on Thu Feb 21 2002 - 16:51:34 NZDT