Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

4000

February 3rd, 2010 09:00

Corrupt label - bad geometry

I have allocated a new dev from symm.

This is what I get when I try to newfs the device:

Feb  3 09:10:47  abc01         Corrupt label - bad geometry
Feb  3 09:10:47 abc01 scsi: [ID 107833 kern.notice]   Label says 97203
840 blocks; Drive says 24301440 blocks

And I can't relabel the device because it can't write to the vtoc.

5 Practitioner

 • 

274.2K Posts

February 10th, 2010 12:00

SKT probably was on the right track but there might be many reasons what can cause the situation you ran into

Many Operating Systems do use the first blocks on a disk device to store information about how the disk device is to be vitualized

On Solaris 10 you would have

  SMI Label
  EFI Label
Your OS found a label on the first device you were trying, which told it that the device is 97203840 blocks

but when it checked the undelying SCSI device it only found  24301440 blocks

!! Beware !!

This would realy make me wonder why.

Usually Solaris does a Autoconfiguration from the SCSI Information if this first blocks are empty

If Solaris finds acceptable data on these first blocks it will not try to fix using the SCSI information

You should try to understand why this situation occured and make sure you are accessing the correct device

You might be misleaded by the history of the device, the device entry on your Solaris System or by the way you try access the device

If I had to continue in this case I would have liked to have a full emcgrab and a current symapi database/Symmetrix configuration including the masking/access database to verify the mapping

If you are really really really sure you are working with the correct device/dtata, you'll have to correct the discrepancy between Solaris device and SCSI device information

This is not to be done by

    format -> label

but by

    format -> type

If this is not working, there are other ways to clear the first blocks first

31 Posts

February 3rd, 2010 23:00

Label says 46.35G while drive says 11.58 GB. Does that ring a bell? can you explain a little more on your setup like OS, volume manager, path manager etc if any.

31 Posts

February 3rd, 2010 23:00

check emc203991

http://csgateway.emc.com/primus.asp?id=emc203991

 

Message was edited by: The Benevolent Moderator

217 Posts

February 3rd, 2010 23:00

OS Sun 10.

Using power path.

217 Posts

February 3rd, 2010 23:00

OS: Red Hat Enterprise Linux, in the solution

But mine is Solaris.

31 Posts

February 5th, 2010 01:00

Please remember to update us once fixed.

217 Posts

February 6th, 2010 04:00

SKT,

I had to un mask the dev and gave them a new dev

217 Posts

February 12th, 2010 03:00

Thanks for the input, what will be the other ways
No Events found!

Top