low level format with FX - SOLVED

SGI hardware problems, solutions, tips, hacks, etc.
Forum rules
Any posts concerning pirated software or offering to buy/sell/trade commercial software are subject to removal.
User avatar
hhoffman
Posts: 91
Joined: Fri Apr 01, 2011 7:45 am
Location: Berlin, Germany

low level format with FX - SOLVED

Unread postby hhoffman » Mon Dec 04, 2017 8:57 am

I have a question about 'fx' in irix. How can I 'low level format' an extra harddrive (fibrechannel) and is it possible to change the blocksize of the drive? I try to use IBM SAN drives in a SGI D-brick. The drives have an unusable blocksize (not 512).

Do I need to boot the installation tools for getting FORMAT option for 'fx'?
Don't see it in irix itself.
Last edited by hhoffman on Thu Dec 14, 2017 1:53 pm, edited 2 times in total.

robespierre
Posts: 1615
Joined: Mon Sep 12, 2011 2:28 pm
Location: Boston

Re: low level format with FX

Unread postby robespierre » Mon Dec 04, 2017 11:26 am

you must invoke fx with the -x flag to see all of the commands.
Then use label/set/geometry to change the block size, and then /format.
:PI: :O2: :Indigo2IMP: :Indigo2IMP:

User avatar
hhoffman
Posts: 91
Joined: Fri Apr 01, 2011 7:45 am
Location: Berlin, Germany

Re: low level format with FX

Unread postby hhoffman » Tue Dec 05, 2017 8:06 am

I tried to do it like you have described and was left with an unusable harddrive:

Code: Select all

fx/label> se

----- please choose one (? for help, .. to quit this menu)-----
[para]meters              [part]itions              [s]giinfo
[g]eometry                [m]anufacturer_params     [b]ootinfo
fx/label/set> g

NOTE: you will need to reformat the disk after changing
the drive geometry.  This will cause all data on the drive
to be lost.  Continue? yes
fx/label/set/geometry: Tracks/zone = (20435)
fx/label/set/geometry: Alt sect/zone = (46124)
fx/label/set/geometry: Alt track/zone = (52)
fx/label/set/geometry: Alt track/volume = (832)
fx/label/set/geometry: Track Skew = (104)
fx/label/set/geometry: Cylinder Skew = (194)
fx/label/set/geometry: Data bytes/sec = (524) 512
 * * * * * W A R N I N G * * * * *
about to modify drive parameters on disk dksc(2,89,0)! ok? yes
dksc2d89vol: [Alert] Media error: Media format corrupted (asc=0x31, asq=0x0)
dksc2d89vol:   retrying request
dksc2d89vol: [Alert] Media error: Media format corrupted (asc=0x31, asq=0x0)
dksc2d89vol:   retrying request
dksc2d89vol: [Alert] Media error: Media format corrupted (asc=0x31, asq=0x0)
dksc2d89vol:   retrying request
dksc2d89vol: [Alert] Media error: Media format corrupted (asc=0x31, asq=0x0)
|$(3)dksc2d89vol: I/O error, retries exhausted
dksc2d89vol: [Alert] Media error: Media format corrupted (asc=0x31, asq=0x0)
dksc2d89vol:   retrying request
dksc2d89vol: [Alert] Media error: Media format corrupted (asc=0x31, asq=0x0)
dksc2d89vol:   retrying request
dksc2d89vol: [Alert] Media error: Media format corrupted (asc=0x31, asq=0x0)
dksc2d89vol:   retrying request
dksc2d89vol: [Alert] Media error: Media format corrupted (asc=0x31, asq=0x0)
|$(3)dksc2d89vol: I/O error, retries exhausted
Warning: error setting drive parameters (page 3): I/O error
dksc2d89vol: [Alert] Media error: Media format corrupted (asc=0x31, asq=0x0)
dksc2d89vol:   retrying request
dksc2d89vol: [Alert] Media error: Media format corrupted (asc=0x31, asq=0x0)
dksc2d89vol:   retrying request
dksc2d89vol: [Alert] Media error: Media format corrupted (asc=0x31, asq=0x0)
dksc2d89vol:   retrying request
dksc2d89vol: [Alert] Media error: Media format corrupted (asc=0x31, asq=0x0)
|$(3)dksc2d89vol: I/O error, retries exhausted
Warning: error setting drive parameters (page 4): I/O error

----- please choose one (? for help, .. to quit this menu)-----
[para]meters              [part]itions              [s]giinfo
[g]eometry                [m]anufacturer_params     [b]ootinfo
fx/label/set>

about to destroy data on disk dksc(2,89,0)! ok? yes
writing label info to dksc(2,89,0)
fx/auto: Error:  Invalid argument:  on write at block 2 for 1 block
retry #2
fx/auto: Error:  Invalid argument:  on write at block 2 for 1 block
retry #3
fx/auto: Error:  Invalid argument:  on write at block 2 for 1 block
retry #4
fx/auto: Error:  Invalid argument:  on write at block 2 for 1 block
fx/auto: Warning:  can't write sgilabel

what can I do now? Can anyone help?

jwhat
Posts: 334
Joined: Sat Aug 09, 2003 6:25 pm
Location: Australia

Re: low level format with FX

Unread postby jwhat » Sat Dec 09, 2017 11:56 am

Hi hhoffman,

Two possible ways to recover are:
1. see if there is vendor tool
2. Use Linux tools.

I am pretty sure last time I had problem this was fixed via Linux utilities - sg3_utils (sg_scan, sg_format etc)

Bit of web surfing should find it. Issue is typically disk with 520 sector size needs to be converted to 512:

http://sg.danny.cz/sg/sg3_utils.html

Cheers,

jwhat.
jwhat - ask questions, provide answers

User avatar
hhoffman
Posts: 91
Joined: Fri Apr 01, 2011 7:45 am
Location: Berlin, Germany

Re: low level format with FX

Unread postby hhoffman » Tue Dec 12, 2017 9:16 am

Hi jwhat,

sorry no way, going one after a another:

1. IBM tools for IBM FC drives do not exist any more, since IBM does no hardware anymore. It disappeared from the IBM website/ftp.
2. sg3_utils gave me an error, when I tried to change the blocksize of one FC drive

Code: Select all

IBM-SSG   H0BE146         A00E      peripheral_type: disk [0x0]
Mode Sense <block descriptor> data, prior to changes:
Number of blocks=275154368 [0x106665c0]
Block size=512 [0x20c]
MODE SELECT command: Illegal request
try '-v' for more information


What to do do now?
hhoffman

User avatar
jan-jaap
Donor
Donor
Posts: 4955
Joined: Thu Jun 17, 2004 11:35 am
Location: Wijchen, The Netherlands
Contact:

Re: low level format with FX

Unread postby jan-jaap » Tue Dec 12, 2017 12:17 pm

Some disk firmware does not allow changing the block size. Some appears to support it, but it's not really implemented, or buggy, or both.

I've got a bricked 300GB 15K disk here somewhere. It was really cheap. Now I know why. Fortunately I bought one to test first, and not 16 (I wanted them for my TP9100 I think)
:PI: :Indigo: :Indigo: :Indy: :Indy: :Indy: :Indigo2: :Indigo2: :Indigo2IMP: :Octane: :Octane2: :O2: :O2+: Image :Fuel: :Tezro: :4D70G: :Skywriter: :PWRSeries: :Crimson: :ChallengeL: :Onyx: :O200: :Onyx2: :O3x02L:
To accentuate the special identity of the IRIS 4D/70, Silicon Graphics' designers selected a new color palette. The machine's coating blends dark grey, raspberry and beige colors into a pleasing harmony. (IRIS 4D/70 Superworkstation Technical Report)

User avatar
hhoffman
Posts: 91
Joined: Fri Apr 01, 2011 7:45 am
Location: Berlin, Germany

Re: low level format with FX

Unread postby hhoffman » Tue Dec 12, 2017 12:20 pm

hm, what about extracting the firmware, changing it and getting it back to the FC drive?

jwhat
Posts: 334
Joined: Sat Aug 09, 2003 6:25 pm
Location: Australia

Re: low level format with FX

Unread postby jwhat » Tue Dec 12, 2017 1:19 pm

Hi hhoffman,

Ok if it is IBM fc disk then you should be able to find spec sheet on hgst site.

Read details on scsi format command and check to see if this allows setting of sector size.

Example:
https://www.hgst.com/sites/default/file ... nal.v6.pdf
https://www.hgst.com/sites/default/file ... _INTv4.pdf

The ibm / hgst sheets have very detailed run down on all scsi commands that are supported, see section 3.1 of example and read sector size info and note 3. It says that for this disk type (not sure if this is same as yours) that you should be able to change sector size via format.

The sg3_utils pretty much map straight to scsi command set.

Looking at results from your error it appears you already have sector size set to 512.
Which is different to fx report of 524, so disk appears to now think it is 512 sectors.

What happens if you now do scsi format ( or this what prior error was from) ?

Finally your disk is reporting as: IBM-SSG == IBM Storage Solutions Group, so looks like you disk might have “special” firmware as Jan-Jaap mentioned. I do not know of any way to change firmware (ie some generic SCSI tool) without vendor specific utility.

These tips are from experimenter not expert ... I have only touched this stuff a couple of times and that was some time ago ;-)

Cheers,

jwhat
jwhat - ask questions, provide answers

User avatar
hhoffman
Posts: 91
Joined: Fri Apr 01, 2011 7:45 am
Location: Berlin, Germany

Re: low level format with FX - SOLVED

Unread postby hhoffman » Thu Dec 14, 2017 9:37 am

hey thank you to everyone for the good ideas and the help!

I finally could manage it changing the block size of the IBM FC drives from 524 bytes to 'usefull' 512 bytes by using sg3_utils.

sgi_Zx10.jpg


It took some time to get the sg3_utils working on my sgi Zx10 test system. I used CentOS 4.9 i386 on it and sg3_utils-1.20.tgz. Some tests with newer versions (and also the src.rpm's) did not work for me on my setup and gave me errors like described above.

However, what might be interesting: I used very cheap IBM 146GB 2Gbit/s FC drives, found on the web for EUR 1,99 each.

robespierre
Posts: 1615
Joined: Mon Sep 12, 2011 2:28 pm
Location: Boston

Re: low level format with FX - SOLVED

Unread postby robespierre » Thu Dec 14, 2017 8:55 pm

It looks like when you tried using fx, you had the same drive visible (and being accessed by) an automount daemon. "Media format corrupted" etc.

Setting the drive geometry should not cause any READ or WRITE activity to the drive at all, so these errors are not coming from fx. I think to succeed in using fx for this task, you need to tell the OS to stop trying to monitor the drive for mountable volumes. Starting from the single-user state (init S) or the standalone shell would be one way to achieve that, but you simultaneously need to have drivers for the Fibre Channel HBA loaded, which could rule them out.

If you refer to the SCSI Command Reference Manual by Seagate, it says that a FORMAT command uses the block size and number of blocks received in a preceding MODE SELECT command, or else these parameters are unchanged. This implies that the device must be idle during the transmission of the MODE SELECT command, and then the FORMAT command, which means some other process cannot try to mount it or an error will result.
:PI: :O2: :Indigo2IMP: :Indigo2IMP:


Return to “SGI: Hardware”

Who is online

Users browsing this forum: No registered users and 2 guests