Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
Operating System - Tru64 Unix
cancel
Showing results for 
Search instead for 
Did you mean: 

Disklabel V4.0 for 18Gb Drives ST318404L MAG3182L

Scot Needy
Occasional Contributor

Disklabel V4.0 for 18Gb Drives ST318404L MAG3182L

Hi,

It's been a long time for me. I have 6 new drives that I need to format, all 18Gb.
SEAGATE ST318404L
FUJITSU MAG3182L

Do I need to add an entry in /etc/disktab or is there an easier solution. If not does anyone have a sample disktab?

8 REPLIES
Rob Leadbeater
Honored Contributor

Re: Disklabel V4.0 for 18Gb Drives ST318404L MAG3182L

Hi,

On 4.0F, you should just be able to write a standard label with "disklabel -wr rzN" and then edit it as required...

Cheers,

Rob
Scot Needy
Occasional Contributor

Re: Disklabel V4.0 for 18Gb Drives ST318404L MAG3182L

Right but the disklabel uses /etc/disktab for the drive geometry. I know for instance a 9gb disk is rz29b. But what can I use for the type hear?


disklabel -wr /dev/rrz9a RZ29B put the wrong geometry on the drive.

Thanks
Rob Leadbeater
Honored Contributor

Re: Disklabel V4.0 for 18Gb Drives ST318404L MAG3182L

Hi,

If a disk type isn't in /etc/disktab, it appears to just use a default geometry.

Just tried this on a 36GB disk and it works fine - see attached.

On 4.0F you don't need to use the drive type. You only mentioned 4.0 though... what specific version are you running (sizer -v)

Cheers,

Rob

P.S. A 9GB drive is an RZ40, not RZ29.
Scot Needy
Occasional Contributor

Re: Disklabel V4.0 for 18Gb Drives ST318404L MAG3182L

4.0 D

I can use disklabel -p /dev/rrz9a
which prints.
# /dev/rrz9a:
type: SCSI
disk: ST318404
label:
flags: dynamic_geometry
bytes/sector: 512
sectors/track: 248
tracks/cylinder: 19
sectors/cylinder: 4712
cylinders: 7508
sectors/unit: 35378533
rpm: 7200
interleave: 1
trackskew: 45
cylinderskew: 39
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0

8 partitions:
# size offset fstype [fsize bsize cpg]
a: 131072 0 unused 0 0 # (Cyl. 0 - 27*)
b: 262144 131072 unused 0 0 # (Cyl. 27*- 83*)
c: 35378533 0 unused 0 0 # (Cyl. 0 - 7508*)
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: 17492658 393216 unused 0 0 # (Cyl. 83*- 3795*)
h: 17492659 17885874 unused 0 0 # (Cyl. 3795*- 7508*)

but cannot read (-r) or edit (-e). Nor can I newfs the partition.
Steven Schweda
Honored Contributor

Re: Disklabel V4.0 for 18Gb Drives ST318404L MAG3182L

> [...] but cannot read (-r) or edit (-e).

"I cannot" is not a useful problem
description. Actual command(s)? Actual
output?

> Nor can I newfs the partition.

Which partition is "the partition"?

As usual, showing actual commands with their
actual output can be more helpful than vague
descriptions and interpretations.
Rob Leadbeater
Honored Contributor

Re: Disklabel V4.0 for 18Gb Drives ST318404L MAG3182L

OK, on 4.0D you do need to specify a type, however that doesn't have to be in /etc/disktab.

From the manpage for disklabel:

"If your disk type is not specified in the /etc/disktab file, disklabel uses the default partition information in the driver."

Therefore something like this:

# disklabel -wr rz9 wibble

should work fine.

As Steven says, seeing exactly what you're doing would be useful...

Cheers,

Rob
Scot Needy
Occasional Contributor

Re: Disklabel V4.0 for 18Gb Drives ST318404L MAG3182L

Ok, I think I have it now. I got rz9 working. I was thinking I needed to use a valid entry from /etc/disktab.
These were the same errors I got with rz9.

# disklabel -r rz11
Disk is unlabeled or, /dev/rrz11a does not start at block 0 of the disk

# disklabel -p rz11
# /dev/rrz11a:
type: SCSI
disk: MAG3182L
label:
flags: dynamic_geometry
bytes/sector: 512
sectors/track: 248
tracks/cylinder: 19
sectors/cylinder: 4712
cylinders: 7508
sectors/unit: 35378533
rpm: 10025
interleave: 1
trackskew: 71
cylinderskew: 101
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0

8 partitions:
# size offset fstype [fsize bsize cpg]
a: 131072 0 unused 0 0 # (Cyl. 0 - 27*)
b: 262144 131072 unused 0 0 # (Cyl. 27*- 83*)
c: 35378533 0 unused 0 0 # (Cyl. 0 - 7508*)
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: 17492658 393216 unused 0 0 # (Cyl. 83*- 3795*)
h: 17492659 17885874 unused 0 0 # (Cyl. 3795*- 7508*)

# disklabel -r rz11
Usage:
...

# disklabel -wr rz11 MAG3182L
# disklabel -r rz11
# /dev/rrz11a:
type: SCSI
disk: MAG3182L
label:
flags: dynamic_geometry
bytes/sector: 512
sectors/track: 248
tracks/cylinder: 19
sectors/cylinder: 4712
cylinders: 7508
sectors/unit: 35378533
rpm: 10025
interleave: 1
trackskew: 71
cylinderskew: 101
headswitch: 0 # milliseconds
track-to-track seek: 0 # milliseconds
drivedata: 0

8 partitions:
# size offset fstype [fsize bsize cpg]
a: 131072 0 unused 0 0 # (Cyl. 0 - 27*)
b: 262144 131072 unused 0 0 # (Cyl. 27*- 83*)
c: 35378533 0 unused 0 0 # (Cyl. 0 - 7508*)
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: 17492658 393216 unused 0 0 # (Cyl. 83*- 3795*)
h: 17492659 17885874 unused 0 0 # (Cyl. 3795*- 7508*)
# newfs /dev/rz11c
Warning: 3876 sector(s) in last cylinder unallocated
/dev/rrz11c: 35378532 sectors in 7509 cylinders of 19 tracks, 248 sectors
17274.7MB in 470 cyl groups (16 c/g, 36.81MB/g, 8832 i/g)
super-block backups (for fsck -b #) at:
...
Thanks to all.
Rob Leadbeater
Honored Contributor

Re: Disklabel V4.0 for 18Gb Drives ST318404L MAG3182L

Glad you worked it out. Remember to say thanks by assigning points.

By the way, is there any particular reason that you're using UFS rather than AdvFS ? I don't think I've ever used newfs on Tru64/Digital Unix...

Cheers,

Rob