How can i format HD 73 Gb to 512 bytes.

[Gustavo Villafaña]

How I format a HD of 73Gb than this one formatted to 520 bytes and want to to it with 512 format byte, I have them in a repair of FC10, make me a comment existing a tool that suits its purposes to give this type of formats command view, somebody can tell me where can discharge it thanks

tjderby /tmp #diskinfo -v /dev/rdsk/c6t1d0
SCSI describe of /dev/rdsk/c6t1d0:
vendor: HP 73.4G
product id: ST373405FC
type: direct access
size: 140000000 Kbytes
bytes per sector: 520
rev level: HP09
blocks per disk: 140000000
ISO version: 0
ECMA version: 0
ANSI version: 3
removable media: no
response format: 2
(Additional inquiry bytes: (32)45 (33)4b (34)32 (35)4b (36)43 (37)36 (38)54 (39)20 (40)20 (41)20 (42)20 (43)53 (44)45 (45)41 (46)47 (47)41 (48)54 (49)45 (50)20 (51)0 (52)0 (53)0 (54)0 (55)0 (56)0 (57)0 (58)0 (59)0 (60)0 (61)0 (62)0 (63)0 (64)0 (65)0 (66)0 (67)0 (68)0 (69)0 (70)0 (71)0 (72)0 (73)0 (74)0 (75)0 (76)0 (77)0 (78)0 (79)0 (80)0 (81)0 (82)0 (83)0 (84)0 (85)0 (86)0 (87)0 (88)0 (89)0 (90)0 (91)0 (92)43 (93)6f (94)70 (95)79 (96)72 (97)69 (98)67 (99)68 (100)74 (101)20 (102)28 (103)63 (104)29 (105)20 (106)32 (107)30 (108)30 (109)32 (110)20 (111)53 (112)65 (113)61 (114)67 (115)61 (116)74 (117)65 (118)20 (119)41 (120)6c (121)6c (122)20 (123)8 (124)58 (125)3b (126)0 (127)0 (128)0 (129)2 (130)8 (131)0 (132)0 (133)0 (134)0 (135)0 (136)0 (137)0 (138)0

[Glenn S. Davidson]

I'm pretty sure they are formatted in 512 byte sectors. Since I have been using HPUX as far back as 8.x they have been that way.

Perhaps the diskinfo command does something funky in it's reporting but with 140000000 kbytes reporting on a 73.4G drive you gotta know something isn't reporting exactly as it should. The only time I have had to change it was when I built an Oracle filesystem then I changed it at the filesystem level.

[Steven E. Protter]

Shalom,

pvdisplay -v /dev/rdsk/c6t1d0

Might already be the case.

Sector size is going to have next to no impact on actual capacity, performance or any other factor you care about as a sysadmin.

SEP

[Patrick Wallek]

It sounds as if this disk was used with a VA74x0 array at some point. The VA arrays reformat a disk to have 520 byte sectors.

If you want to use the disk in an FC10, then it will have to be reformatted to have 512 byte sectors.

I know there is a procedure to do this, I just can't find it at the moment. I'll keep looking. Hopefully someone else can come up with it in the mean time.

[Gustavo Villafaña]

I see one email whit this.
The command under HP-UX is JBODfmt(1m) . You will need to use the JBODdsp(1m) command to make sure the host can see the JBOD disks and that the JBODfmt(1m) command supports formatting those drives. Do the following -

1. JBODdsp -i this should display all the devices in the JBOD it can see. If the drives in the JBOD cannot be seen the next step cannot be used.

2. JBODfmt -foverride That will format the drives to 512 byte sectors no matter what their current format is.

I think this procedure can help me whit my problem

[Patrick Wallek]

That is it exactly! That should do what you need to do.

I don't know that you necessarily need to use the '-foverride' option though. That tells the command to format the drive no matter what, even if it is already at 512 bytes per sector.

I would just use the '-f' option.

[Torsten.]

Correct, if the disk was in use by a VA7xxx, you need to insert it in a standalone DS240x and run commandview. Select the JBOD and you will get an option to format the drive back to 512k blocks.

[Mink]

I had the same problem an the only resolution is to install Commandview SDM to make a new format of the disk. The JBODfmt Command belongs to this Software that controls VA7400 and DS2405 Enclosures.

cd /opt/sanmgr/commandview/client/sbin
./JBODfmt -f /dev/dsk/c5t11d0

[Marcel Burggraeve]

Like several others already mentioned, jbodfmt is the way to go.
Word of advise, if possible do this on a windows system with a fibre card in it.
Couple of years ago I had no problems at all with jbodfmt on a HP9000 and somewhere last year the latest version of commandview was causing loads of problems with weird errors.
Just before we gave up we gave it a try on a windows system ( DL380 ) and to our surprise/horror it worked right away.