Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

format.dat with Fujutsu MAF3364LC

72 views
Skip to first unread message

James Simmons

unread,
Sep 2, 2004, 2:18:08 PM9/2/04
to
Hi All,

I just purchased 7 Fujitsu MAF3364LC drives to upgrade my RAID5. I am
replacing my 9.1 GB drives.

The problem is that my format.dat does not contain a definition for the
MAF3364LC. I have been trying to format with the data contained in the
Fujitsu user document, with no success. Each format takes 97 minutes and I
am running out of time. The restore of the data will take over 2 days,
alone, if I ever get this configured correctly.

The user doc says this drive has:
Formatted Capacity: 36.4GB
Unformatted Capacity: 45.6GB
Number Disks: 10
Number Heads: 19
Number Cylinders: 10,200
RPM: 10025 +/- 0.5%

It does NOT list number of sectors/track, so I have been experimenting with
different values from 420, down to 390, with no success. I always get the
message from format that the "Current deometry overshoots actuial geometry
of disk". This, even though I have gotten well below the rated formatted
capacity.

Any help will be appreciated.

James

Note: Take out the spam for email reply.


Dave Uhring

unread,
Sep 2, 2004, 2:38:38 PM9/2/04
to
On Thu, 02 Sep 2004 18:18:08 +0000, James Simmons wrote:

> The problem is that my format.dat does not contain a definition for the
> MAF3364LC. I have been trying to format with the data contained in the
> Fujitsu user document, with no success. Each format takes 97 minutes and I
> am running out of time. The restore of the data will take over 2 days,
> alone, if I ever get this configured correctly.

That particular model is not listed, but contact information for Fujitsu
is:

http://groups.google.com/groups?selm=04May18.004010edt.453131-7513%40jane.cs.toronto.edu&output=gplain

Michael Laajanen

unread,
Sep 2, 2004, 3:35:22 PM9/2/04
to
HI,

Why do you need to worry about format.dat?

A modern SCSI drive should not need that info, I have needed that info
once on a special drive that did have a special firmware from a old
Tandem. at that time I did use a Adaptec SCSI controller on a PC in
office and did a "low level format<CTRL>-<A> at boot" which made Solaris
format to work.

How do you do the format?

/michael

Casper H.S. Dik

unread,
Sep 2, 2004, 3:35:37 PM9/2/04
to
"James Simmons" <ja...@pcug.us> writes:

>The problem is that my format.dat does not contain a definition for the
>MAF3364LC. I have been trying to format with the data contained in the
>Fujitsu user document, with no success. Each format takes 97 minutes and I
>am running out of time. The restore of the data will take over 2 days,
>alone, if I ever get this configured correctly.

You shouldn't need one; moreover, you really shouldn't format drives;
they come formatted and formatting does take a very long time.

(The system basically tells the drive to "go format itself" and the
drive then goes away for a very, very, long time.

Casper

James Simmons

unread,
Sep 2, 2004, 4:47:06 PM9/2/04
to
Hi Michael,

I first tried to use Sun Solstice, but it came back with an error, saying it
had to change the data size to 512.

I then used the solaris format command, and selected the "Other" selection.
I entered the info I had, but it didn't work. I have been playing with
format ever since.

James

"Michael Laajanen" <michael.laajanen.no-spam.@telia.com> wrote in message
news:_BKZc.102403$dP1.3...@newsc.telia.net...

James Simmons

unread,
Sep 2, 2004, 4:55:32 PM9/2/04
to
Casper,

Sun Solstice could not handle the drive. It threw an error about changing
the data block size. That I why I had to resort to format.

Do you have a format.dat entry for this drive?

James

"Casper H.S. Dik" <Caspe...@Sun.COM> wrote in message
news:41377609$0$43451$e4fe...@news.xs4all.nl...

Michael Laajanen

unread,
Sep 3, 2004, 2:47:14 AM9/3/04
to
Hi,

James Simmons wrote:
> Hi Michael,
>
> I first tried to use Sun Solstice, but it came back with an error, saying it
> had to change the data size to 512.
>
> I then used the solaris format command, and selected the "Other" selection.
> I entered the info I had, but it didn't work. I have been playing with
> format ever since.
>
> James

Always put your post below the original post ( don't top post) so it is
easier to read :)

A SCSI drive is intelligent(for being a disk) so you usually don't talk
about discs and heads, that is taking care of by the local CPU.

Like I wrote I have had this problem once on a special SCSI drive which
was solved using a PC SCSI controller and by means of a low lever
format. I don't know if Suns "low level format" program which they use
when the OEM the drives is available somewhere or if the function can be
done in a som other Solaris code.

Have you tried "looking for backuop labels"?

Could you post the commands you are trying?

Hmm, I now thinking about Joerg Shilling who writes the fantastic
cdrecord program, he has something like that you could try and see if he
reponds to this or via a new posting from you with a cleaver subject :)

Casper should also know alot on this and how to make Solaris cheat format.

/michael

Scott Howard

unread,
Sep 3, 2004, 5:54:13 AM9/3/04
to
James Simmons <ja...@pcug.us> wrote:
> Do you have a format.dat entry for this drive?

You don't need one! (for about the 3rd time).

Run "format", select the disk, type "type", select "0" (Auto configure),
type "label" and "yes".

All done. Nothing more to do. No format.dat needed.

Scott

Coy Hile

unread,
Sep 3, 2004, 11:53:44 AM9/3/04
to

This may be a bit OT for this thread, but what is the analogous
procedure for IDE drives? I find no "auto configure" option in the menu
when I try to format the drive in my Netra X1 for instance.

Thanks,

--
Coy Hile
hi...@cse.psu.edu

James Simmons

unread,
Sep 3, 2004, 5:33:37 PM9/3/04
to

"Scott Howard" <sc...@hunterlink.net.au> wrote in message
news:1094205259.146192@docbert...

Scott,

I will try to be gentle.... I have said before that the format.dat DOES NOT
contain the entries for these drives! When format displays the know drive
types, it is displaying the information from the format.dat file.

There is no need to be cranky.

For everyone else, I finally got down to something that would format (367
sectors/track), using the other data from the fujitsu user doc. Sun format
failed. Could not write VTOC.

Here is the results:

format> inquiry
Vendor: FUJITSU
Product: MAF3364LCX
Revision: 2412
format> current
Current Disk = c1t0d0
<Fujitsu 36.4G MAF3364 cyl 10198 alt 2 hd 19 sec 368>
/iommu@f,e0000000/sbus@f,e0001000/dma@0,81000/esp@0,80000/sd@0,0

format> format
Ready to format. Formatting cannot be interrupted
and takes 97 minutes (estimated). Continue? y
Beginning format. The current time is Fri Sep 3 16:20:12 2004

Formatting...
99% complete done2:14:07 remaining)
Warning: error writing VTOC.
Warning: error reading backup label.
Warning: error reading backup label.
Warning: error reading backup label.
Warning: error reading backup label.
Warning: error reading backup label.
Warning: no backup labels

Verifying media...
pass 0 - pattern = 0xc6dec6de
0/0/0

Warning:Drive may be reserved or has been removed, aborting surface
analysis.
Warning: error writing VTOC.
Warning: error reading backup label.
Warning: error reading backup label.
Warning: error reading backup label.
Warning: error reading backup label.
Warning: error reading backup label.
Warning: no backup labels
format>

James Simmons

unread,
Sep 3, 2004, 6:59:34 PM9/3/04
to

"Scott Howard" <sc...@hunterlink.net.au> wrote in message
news:1094205259.146192@docbert...
Scott,
Here is the output of the type using selection 0:

format> inquiry
Vendor: FUJITSU
Product: MAF3364LCX
Revision: 2412
format> type


AVAILABLE DRIVE TYPES:
0. Auto configure
1. Quantum ProDrive 80S
2. Quantum ProDrive 105S
3. CDC Wren IV 94171-344
4. SUN0104
5. SUN0207
6. SUN0327
7. SUN0340
8. SUN0424
9. SUN0535
10. SUN0669
11. SUN1.0G
12. SUN1.05
13. SUN1.3G
14. SUN2.1G
15. SUN2.9G
16. Zip 100
17. Zip 250
18. SUN18G
19. Fujitsu 36.4G MAF3364
20. other
Specify disk type (enter its number)[19]: 0
Must reformat device to 512-byte blocksize. Continue? y
Formatting...
Auto configure failed
format>


Joerg Schilling

unread,
Sep 3, 2004, 8:05:36 PM9/3/04
to
In article <Rq5_c.3941$lv3.1...@news4.srv.hcvlny.cv.net>,
James Simmons <ja...@pcug.us> wrote:

>Here is the results:
>
>format> inquiry
>Vendor: FUJITSU
>Product: MAF3364LCX
>Revision: 2412
>format> current
>Current Disk = c1t0d0
><Fujitsu 36.4G MAF3364 cyl 10198 alt 2 hd 19 sec 368>
>/iommu@f,e0000000/sbus@f,e0001000/dma@0,81000/esp@0,80000/sd@0,0
>
>format> format
>Ready to format. Formatting cannot be interrupted
>and takes 97 minutes (estimated). Continue? y
>Beginning format. The current time is Fri Sep 3 16:20:12 2004
>
>Formatting...
> 99% complete done2:14:07 remaining)
>Warning: error writing VTOC.
>Warning: error reading backup label.

If you like to get error messages, you may want to check sformat.

It is part of the CSWschilyutils package

http://www.blastwave.org/packages.php

--
EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
j...@cs.tu-berlin.de (uni) If you don't have iso-8859-1
schi...@fokus.fraunhofer.de (work) chars I am J"org Schilling
URL: http://www.fokus.fraunhofer.de/usr/schilling ftp://ftp.berlios.de/pub/schily

James Simmons

unread,
Sep 4, 2004, 4:16:12 AM9/4/04
to

"Joerg Schilling" <j...@cs.tu-berlin.de> wrote in message
news:chb0sg$m5v$1...@news.cs.tu-berlin.de...

> In article <Rq5_c.3941$lv3.1...@news4.srv.hcvlny.cv.net>,
> James Simmons <ja...@pcug.us> wrote:
>
> >Here is the results:
======snip=======

>Warning: error reading backup label.
>
> If you like to get error messages, you may want to check sformat.
>
> It is part of the CSWschilyutils package
>
> http://www.blastwave.org/packages.php
>
> --
> EMail:jo...@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353
Berlin
> j...@cs.tu-berlin.de (uni) If you don't have iso-8859-1
> schi...@fokus.fraunhofer.de (work) chars I am J"org Schilling
> URL: http://www.fokus.fraunhofer.de/usr/schilling
ftp://ftp.berlios.de/pub/schily
Thanks J"org, but format -m -M gives errors also. Here is the output:
somesystem:root>format -m -M -d c1t0d0
Searching for disks...done

FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk
repair - repair a defective sector
label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show vendor, product and revision
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> disk


AVAILABLE DISK SELECTIONS:
0. c0t1d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248> storage

/iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@1,0
1. c0t3d0 <SUN18G cyl 7506 alt 2 hd 19 sec 248> root

/iommu@f,e0000000/sbus@f,e0001000/espdma@f,400000/esp@f,800000/sd@3,0
2. c1t0d0 <drive not available>
/iommu@f,e0000000/sbus@f,e0001000/dma@0,81000/esp@0,80000/sd@0,0
3. c1t1d0 <drive not available>
/iommu@f,e0000000/sbus@f,e0001000/dma@0,81000/esp@0,80000/sd@1,0
4. c1t2d0 <drive not available>
/iommu@f,e0000000/sbus@f,e0001000/dma@0,81000/esp@0,80000/sd@2,0
5. c1t3d0 <drive not available>
/iommu@f,e0000000/sbus@f,e0001000/dma@0,81000/esp@0,80000/sd@3,0
6. c1t4d0 <drive not available>
/iommu@f,e0000000/sbus@f,e0001000/dma@0,81000/esp@0,80000/sd@4,0
7. c1t5d0 <drive not available>
/iommu@f,e0000000/sbus@f,e0001000/dma@0,81000/esp@0,80000/sd@5,0
8. c1t6d0 <drive not available>
/iommu@f,e0000000/sbus@f,e0001000/dma@0,81000/esp@0,80000/sd@6,0
Specify disk (enter its number)[2]: 2

AVAILABLE DRIVE TYPES:
0. Auto configure
1. Quantum ProDrive 80S
2. Quantum ProDrive 105S
3. CDC Wren IV 94171-344
4. SUN0104
5. SUN0207
6. SUN0327
7. SUN0340
8. SUN0424
9. SUN0535
10. SUN0669
11. SUN1.0G
12. SUN1.05
13. SUN1.3G
14. SUN2.1G
15. SUN2.9G
16. Zip 100
17. Zip 250
18. SUN18G

19. other
Specify disk type (enter its number): 0
Inquiry:
00 00 02 42 3b 00 01 3a 46 55 4a 49 54 53 55 20 ...B;..:FUJITSU
4d 41 46 33 33 36 34 4c 43 58 20 20 20 20 20 20 MAF3364LCX
32 34 31 32 20 20 20 20 30 30 30 31 33 30 35 38 2412 00013058
Product id: MAF3364LCX
Capacity: 04 42 60 f3 00 00 02 04
blocks: 71459059 (0x44260f3)
blksize: 516
disk name: `X `


Must reformat device to 512-byte blocksize. Continue? y

Mode sense page 0x3 (current):
header: 23 00 10 08 04 42 60 f4 00 00 02 04
data: 83 16 00 13 00 14 00 00 00 13 01 a4 02 04 00 01
00 47 00 6c 40 00 00 00

Mode select page 0x3 (pf):
header: 00 00 00 08 04 42 60 f4 00 00 02 00
data: 03 16 00 13 00 14 00 00 00 13 01 a4 02 00 00 01
00 47 00 6c 40 00 00 00
Formatting...

Mode sense page 0x4 (default):
header: 23 00 10 08 00 00 00 00 00 00 02 04
data: 84 16 00 27 d9 13 00 00 00 00 00 00 00 00 00 00
00 00 00 00 27 29 00 00
pcyl: 10201
heads: 19
rpm: 10025
format_time: 97 minutes
format_timeout set to 11640 seconds, 11640 required
Illegal request during format
ASC: 0x24 ASCQ: 0x0
cmd: 00 01 00 04 00 02 2d 78 ef ff ed 2c ef ff ed 28
00 00 00 04 00 00 00 04 06 ff 00 eb ef ff eb c8
00 00 00 00
cdb: 04 10 00 00 00 00
sense: 70 00 05 00 00 00 00 28 00 00 00 00 24 00 00 00
00 00 00 04
Reformat device to 512-byte blocksize failed
Configuration via generic SCSI-2 information failed
Auto configure failed
format>

James


Joerg Schilling

unread,
Sep 4, 2004, 5:11:18 AM9/4/04
to
In article <gRe_c.4629$lv3.2...@news4.srv.hcvlny.cv.net>,
James Simmons <ja...@pcug.us> wrote:

>> If you like to get error messages, you may want to check sformat.
>>
>> It is part of the CSWschilyutils package
>>
>> http://www.blastwave.org/packages.php

>format_timeout set to 11640 seconds, 11640 required


>Illegal request during format
>ASC: 0x24 ASCQ: 0x0
>cmd: 00 01 00 04 00 02 2d 78 ef ff ed 2c ef ff ed 28
> 00 00 00 04 00 00 00 04 06 ff 00 eb ef ff eb c8
> 00 00 00 00
>cdb: 04 10 00 00 00 00
>sense: 70 00 05 00 00 00 00 28 00 00 00 00 24 00 00 00
> 00 00 00 04
>Reformat device to 512-byte blocksize failed

Well, it is obvious that the drive did not like the command
and it is highly probable that the cause is a bug in Sun's format
program.

Did you try sformat?

Do you know that sformat has been tested for being able to change the sector
size?

BTW: Sun's format appeared _after_ Sun did get knowledge about my sformat.
When I the created Generic SCSI driver scg and sformat, you have been
forced to boot a stand alone disk formatting program instead of SunOS.

Michael Laajanen

unread,
Sep 4, 2004, 7:58:26 AM9/4/04
to
HI,

James Simmons wrote:
> "Scott Howard" <sc...@hunterlink.net.au> wrote in message
> news:1094205259.146192@docbert...
>
>>James Simmons <ja...@pcug.us> wrote:
>>
>>>Do you have a format.dat entry for this drive?
>>

<snip>

> 20. other
> Specify disk type (enter its number)[19]: 0
> Must reformat device to 512-byte blocksize. Continue? y
> Formatting...
> Auto configure failed
> format>
>
>

James, go with Joergs sformat(install it from www.blastwave.org) if
that fails Joerg might have a bug and that will likely be easier to get
a workaround with than format since Sun likes to ship Sun labeled drives :))

/michael

0 new messages