Why am I getting a Bad Disk Label Error?

[catapultpy]

I recently replaced a failed disk with another spare that I had but when it was inserted this is what I get: "disk has no valid labels. It will be taken out of service."

"1 disks have downrev firmware. They will be updated automaticaly using...."

This filer is an F820. The disk is a 68.0GB 520B/sect.

What can I do to correct this?

Thanks,

Paul Yates

Catapult Exploration LLC

[ewerner]

Paul,

From the error, it looks like that particular disk has an older firmware version and OnTAP is looking for the updated version.

Can you provide the firmware versions of the other disks with sysconfig -a so we can see what they are working with?

[catapultpy]

Thanks for your response. How can I update this specific disk?

Paul Yates

Catapult Exploration LLC

I noticed the Rev: for the disk that I replaced is NA08 It is Disk # 51.

NetApp Release 7.1.3: Tue May 27 01:41:45 PDT 2008

System ID: 0033608229 (alamo)

System Serial Number: 1032237 (alamo)

System Rev: B0

Backplane Part Number: 110-02401

Backplane Rev: B0

Backplane Serial Number: 1032237

slot 0: System Board 733 MHz (NetApp System Board VII F2)

Model Name: F820

Part Number: 110-00018

Revision: F2

Serial Number: 266605

Firmware release: 4.2.3_i1

Processors: 1

Processor ID: 0x686

Microcode Version: 0x8

Memory Size: 1024 MB

CIOB Revision ID: 5

slot 0: FastEnet-10/100 Ethernet Controller

Device Type: 82559

e0 MAC Address: 00:a0:98:02:d3:c1 (auto-unknown-cfg_down)

memory mapped I/O base 0xd8100000, size 0x1000

I/O base 0xffc0, size 0x40

memory mapped I/O base 0xd8000000, size 0x100000

I/O base 0xffb0, size 0x10

slot 4: 10/100/1000 Ethernet Controller IV

e4 MAC Address: 00:02:b3:b2:0a:ec (auto-1000t-fd-up)

Device Type: Rev 2

memory mapped I/O base 0xe8400000, size 0x20000

memory mapped I/O base 0xe8420000, size 0x20000

I/O base 0xcfe0, size 0x20

slot 8: FC Host Adapter 8a (Dual-channel, QLogic 2200A rev. 5, 64-bit, L

)

Firmware rev: 2.2.3

Host Loop Id: 7 FC Node Name: 2:001:00e08b:248bcc

Cacheline size: 8 FC Packet size: 2048

SRAM parity: Yes External GBIC: No

Link Data Rate: 1 Gbit

16: NETAPP X272_SCHT6073F10 NA16 68.0GB 520B/sect (3HZX43QK0

9MFT7)

17: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1VZAB0

1HXQN)

18: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1W0QA0

1KP2G)

19: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1VZ210

1KP1Q)

20: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1W0QC0

1MMHF)

21: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1VZ4X0

1Y70V)

22: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1W0Y70

1KNYF)

23: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1VN960

0SAP2)

24: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1TZ410

9Y4SL)

25: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1TY5L0

0LPQU)

26: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1TYC60

0LPVN)

27: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK0H8260

88JZ3)

28: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1W1DT0

1KP0K)

29: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1W2YF0

1KNQ2)

32: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1W17A0

1KNDC)

33: NETAPP X235_HJURD073F10 NA09 68.0GB 520B/sect (303S3358)

34: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1VZCJ0

1MNEV)

35: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1W2PC0

1MN10)

36: NETAPP X235_HJURD073F10 NA09 68.0GB 520B/sect (303T3016)

37: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1VZ520

1ZXPF)

38: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1VXWS0

1HWQC)

39: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1VYS50

1Y6XR)

40: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1W1K10

1J0FE)

41: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1VTRS0

1J0DF)

42: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1W2D00

1MMRE)

43: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1VP9J0

1KP0F)

44: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1VTXP0

1Z8H0)

45: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1TSY00

1Y3GF)

48: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1VZQJ0

1HZQV)

49: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1VM600

1KNQ4)

50: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1W0RP0

1J0VP)

51: NETAPP X235_HJURD073F10 NA08 68.0GB 520B/sect (???)

52: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1V85V0

1MNDG)

53: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1W0SM0

1MMTT)

54: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1VYYM0

1HXDF)

55: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1V1V40

9K1CD)

56: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1V26V0

0QWN9)

57: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1TRQN0

7Y91S)

58: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1TRNR0

0RFX3)

59: NETAPP X272_HJURE073F10 NA14 68.0GB 520B/sect (415N8927)

60: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1W0RF0

1KNP7)

61: NETAPP X235_SCHT5073F10 NA09 68.0GB 520B/sect (3EK1VXD10

1MNFZ)

Shelf 1: LRC Firmware rev. LRC A: 11 LRC B: 11

Shelf 2: LRC Firmware rev. LRC A: 11 LRC B: 11

Shelf 3: LRC Firmware rev. LRC A: 11 LRC B: 11

I/O base 0xdf00, size 0x100

memory mapped I/O base 0xe8201000, size 0x1000

slot 10: 10/100/1000 Ethernet Controller IV

e10 MAC Address: 00:02:b3:b2:0b:b5 (auto-unknown-cfg_down)

Device Type: Rev 2

memory mapped I/O base 0xe8020000, size 0x20000

memory mapped I/O base 0xe8000000, size 0x20000

I/O base 0xefe0, size 0x20

slot 11: NVRAM (NetApp NVRAM III)

Revision: A0

Serial Number: 53797

Memory Size: 128 MB

Battery Status: OK

prefetchable memory base 0xe0000000, size 0x8000000

[ewerner]

I found the following directions for you on our NOW site:

Command for updating disk firmware

Use the disk_fw_update command from the storage system console to update firmware on all disks or a specified disk on a storage system.

The disk_fw_update command updates disks for which firmware files are present in the /etc/disk_fw directory and which need to be updated. It does not update other disks.

The disk_fw_update command is applicable to SCSI, Fibre Channel, SATA, and SAS disks.

For more information, see the disk_fw_update(1) man page.

Attention: This command makes disks inaccessible for up to two minutes, so network sessions using the storage system should be terminated before running the command. This is particularly true for CIFS sessions, which otherwise are terminated while this command executes.

When to update disk firmware manually

If you receive error messages about firmware compatibility, you must manually update your disk firmware.

• Manually update disk firmware with the disk_fw_update command.
• Download the new disk firmware from the NOW site, then enter the following command at the storage system prompt:disk_fw_update

Note: When you upgrade the storage system software, disk firmware is updated automatically as part of the storage system software upgrade process. A manual update is not necessary unless the new firmware is not compatible with the storage system disks.

Let me know if you have further questions.

Thanks

-Ethan

[catapultpy]

Well I hope that I not going to be a bother. The disk is not part of the system. It is being ignored. I tried to update the firmware from a cmd prompt telnet to the filer but it says No disk in primary FC loop eligible for download. Firmware up to date on all disk drives.

Yet when I look at the disks in filerview the one identified as broken is not a part of the all disks but part of the broken disks.

???

[ewerner]

It's not a bother at all, Paul, but I'm somewhat at a loss now since I was pretty sure that would fix this issue.

Can anyone else shed some light on this issue and give Paul (and me, so I can understand too) a hand?

Thanks!

[catapultpy]

Below is the last of a syslog of my filer after replacing the disk that had a "Bad Disk Label Error with a disk that had the same firmware version. Now I am getting a foreign VA.

Why am I getting this? What do I need to do to get this disk accepted into my volumes and a blank disk available? Should I zero this disk?

Help if you can.

Thanks,

Paul Y

Thu Nov 19 13:21:06 CST : Initiating rescan on channel 8a

Thu Nov 19 13:21:08 CST : Failed to build FCAL map on Fibre Channel adapter 8a -- resetting adapter.

Thu Nov 19 13:21:20 CST : Initiating rescan on channel 8b

Thu Nov 19 13:21:23 CST : Failed to build FCAL map on Fibre Channel adapter 8b -- resetting adapter.

Thu Nov 19 13:21:38 CST : Disk 8b.51 Shelf 3 Bay 3 S/N is missing from the system

Thu Nov 19 13:21:43 CST : Initiating rescan on channel 8a

Thu Nov 19 13:21:43 CST : Disk 8b.51 Shelf 3 Bay 3 S/N has been inserted into the system

Thu Nov 19 13:21:46 CST : Initiating rescan on channel 8b

Thu Nov 19 13:21:49 CST : Firmware is up-to-date on all disk shelves.

Thu Nov 19 13:21:49 CST : Upgrading RAID labels.

Thu Nov 19 13:21:49 CST : Volume foreign:VA, rgobj_verify: RAID object 0 has only 1 valid children, expected 14.

Thu Nov 19 13:21:49 CST : Volume foreign:VA, plexobj_verify: Plex 0 only has 0 working RAID groups (1 total) and is being taken offline

Thu Nov 19 13:21:49 CST : Volume foreign:VA, mirrorobj_verify: No operable plexes found.

Thu Nov 19 13:21:49 CST : raidtree_verify: Volume VA is a foreign volume and is being taken offline. Use the 'vol online' command to bring it online.

Thu Nov 19 13:21:56 CST : System Notification mail sent: System Alert from alamo

[pascalduk]

You get the message because the new spare was not zeroed and still (partial) data from a volume. Just destroy the volume and zero the disk.

[eric_barlier]

pascal is right, the disk has got some data on it. the volume name will be easy to spot, from memory I think it will have a () at the end of it.

There are ways to force a disk to become a spare, I have a workaround that is intrusive as it needs a reboot so I wont post it here.

In the current state you ll be fine once the volume has been deleted.

Cheers,

Eric

[catapultpy]

Thanks,

Is there no way to zero the disk with destroying the volume?

Paul

[eric_barlier]

Hi Paul,

You might have misunderstood a bit. Im not sure but as we are talking about destroying volumes lets make sure we get it right.

Can you post the output of

vol status

Here? You are supposed to only destroy that volume that was created when the new disk was added. Not any other volume.

We should be able to help you if you send us the output of command above.

Cheers,

Eric

[danielpr]

Seems to be some confusion in the problem understanding

Let me know if my following point are right

o You had a failed disk (media error) you have pulled out and put another disks from different shelf

o Now this disk is not coming up as spare instead its in Failed disk pool.

o The spare disk which is failed state now will have some old data (But you dont need that data right ?)

o Now you want to make sure that the replaced disk should come as spare instead in broken pool.

Just wondering which volume your talking about destroying  and which disks you expect to be zerod.

If you zero the disks any point of time you wont get data back. I would recommend you to contact NGS.

Thanks

Daniel

[catapultpy]

Thanks for your reply. Actually, it is a very long story. My filer already had its spare disk accidentally allocated to the volume and so we now have no spare. I have to actively monitor the filer for disk failures because of this fact. So when I have a disk fail I have to quickly replace it. I had purchased extra 72 GB disks for that very purpose but unfortunately the two drives I received must have had some data left on them and so I am getting a bad label error on both drives. I would like to clear that data off of those drives so that they will be accepted by the filer as a empty disk that can be used. I am not a Net App expert and really was given the job of IT because I had the most experience in the PC world. Our filer is too old and is considered at EOL and so not supported by Net App. So here I am with drives I can't use and the lack of knowledge to clear the data from the disks. This filer works well when the disks don't fail and even then if I have replacements then I can just replace the drives until such time as I can destroy the aggregate and then rebuild it with a spare drive. As it should be.

Paul Yates

[danielpr]

Thanks that explains clearly.. Can you share the following command out put?

# vol status -f

# vol status -s

# vol status -r

# aggr status -r

Thanks

Daniel

[obiwan___]

I've had the same issue, and failed to find the answer in the forums. The solution is to use the following command:

disk unfail -s <disk>

Repeat for each affected disk. You'll need to run "set priv advanced" to be able to use the unfail command.

[catapultpy]

It turned out that the firmware version on my drive was earlier than the replacement drive. I was fortunate enough that the company that I purchased the drive from exchanged it for one that they put the same version as what I needed.

[AVANISHRANJAN]

We got usually Foreign Volume when we transfer a set of disk having data to another filer. Its showing VM volume it means that disk would not be well sanatized when that disk was being given back to the vendor.

You could do one thing you need to give back that disk to the vendor from where you bought as when one disk is failed will not be accepted by the filer.

Avanish Ranjan,