test - no need to respond
My F630 filer won't boot and drops back into OK prompt. The last message before OK is
Mon May 2 12:40:23 GMT [emu_admin]: EMU 4 part number 524287 not supported.
I'm not physically co-located with the unit and will have to direct my onsite guy what to check/fix. This old box is self-maintained.
I understand the problem thanks to a peer on this list. We have to replace the defective EMU. Any quick way to identify the failing EMU?
Also the instructions to boot from the floppy, check volume status, remove floppy then boot normally doesn't make much sense. How does that bypass the failing EMU?
Comments, suggestions?
Thanks in advance.
Rgds,
Dan O'Brien, dmobrien@lcsi.net Cell: 614-783-4859 Work: 614-476-8473
----
Alpha Open Firmware by FirmWorks Copyright 1995-1998 FirmWorks, Network Appliance. All Rights Reserved. Firmware release 2.3_a1
Memory size is 512 MB Testing SIO Testing LCD Probing devices Testing 512MB Complete Finding image... Loading 14 f 5 disk@0 100% Starting ......................................................................... ....
NetApp Release 5.3.6R2: Sat Aug 5 09:40:44 PDT 2000 Copyright (c) 1992-2000 Network Appliance, Inc. Starting boot on Mon May 2 12:40:07 GMT 2005 Scanning for disk drives: ....................................... Configuring disk drives:Local MAC address is 0:60:cf:20:2b:2f 8b.2 8a.13 8b.12 8b.3 8a.12 8a.1 8a.5 8b.11 8b.0 8b.14 8b.5 8a.10 8a.8 8a.9 7a.1 8b.4 8b.8 8b.9 8b.10 8b.1 8b.13 8a.14 8a.11 8a.0 8a.4 8a.3 8a.2 7a.14 7a.10 7a.5 7 a.9 7a.12 7a.13 7a.11 7a.4 7a.0 7a.3 7a.2 7a.8 Disk 7a.11 is reserved for "hot spare"
1 disk is reserved for "hot spare". Restoring parity from NVRAM Loading volume vol0 Replaying WAFL log Mon May 2 12:40:23 GMT [emu_admin]: EMU 4 part number 524287 not supported.
ok ----
Title: Error Message: "EMU X not supported" - NetApp filer
Problem Environment: NetApp filer
Data ONTAP OS 5.2.x
SCSI storage Shelf 2
EFB
F700 series
F500 series
F300 series
F200 series
Data ONTAP
F600 series
Data ONTAP OS 5.3.x
EMU
Data ONTAP OS 5.1.x
Problem Description Error Message: EMU X not supported
Filer does not boot
Cause of this problem: Normally this error occurs when an EMU module is defective.
Solution: Replace or remove the EMU module that is reported on the console as "not supported" Identify which EMU is reporting errors from the console error message logged during an attempt to boot normally. Since the Filer will boot with out an EMU module there are two choices. a. Remove the EMU module from the shelf, replace it with a new one and boot normally. Please refer to the Network Appliance Storage Shelf 2 hardware guide. b. If a replacement EMU is not readily available, boot the filer using the boot floppy diskettes.
At the "5 item menu", Enter 5 for "Maintenance mode". Enter 'vol status' to ensure none of the volumes have "failed". If all volumes are "online", enter 'halt', remove the floppy diskette from the filer, and at the "OK" prompt enter 'boot'. Obtain an EMU. Schedule downtime as soon as possible so that "hot" disk-swapping and shelf environmental error detection functions can be restored.
NOTE: The filer WILL boot without the EMU module installed and serve data normally. All other functions will work except "hot" disk-swapping and shelf environmental error detection for over temperature, fan fails, and power supply failures.
Dan> I understand the problem thanks to a peer on this list. We have Dan> to replace the defective EMU. Any quick way to identify the Dan> failing EMU?
It's probably got some LEDs on the disk tray that's gone bad. Look on the back of the disk shelf. I haven't touched a 630 for quite a while, but it used the same old SCSI shelves as the F500 series, or even the old F300 series possibly. All the fans were on the back of the shelves.
Dan> Also the instructions to boot from the floppy, check volume Dan> status, remove floppy then boot normally doesn't make much Dan> sense. How does that bypass the failing EMU?
It mostly just forces the OS to ignore the EMU (or lack of one) and just boot the system. It's a failsafe way to keep you from losing more than just a disk in a system. At least thats the impression I get from the doc you provided.
The writeup looks really good, so once you get a replacement, you should be all set to go with another small downtime window.
One of the used NetApp places should be able to get you a replacement shelf or EMU without too much problem.
John John Stoffel - Senior Staff Systems Administrator - System LSI Group Toshiba America Electronic Components, Inc. - http://www.toshiba.com/taec john.stoffel@taec.toshiba.com - 508-486-1087
Just a follow up. Received several emails from helpful folks, thanks!
My onsite guy was able to find EMU 4 (7a shelf 0) and unplug it. This allowed the system to come up. We are now looking for a replacement unit. The "spare" we had won't work. Here is the onsite guy's report:
"The spare EMU on the rocks (part number XL401R-02Z); the broken EMU (XL401R-02N) look like identical, but they have different modes with different rear interface panel. SO, we can't use the spare EMU to replace the broken one."
I've contacted a list member for replacement.
Rgds,
Dan O'Brien, dmobrien@lcsi.net Cell: 614-783-4859 Work: 614-476-8473
Dan O'Brien wrote:
My F630 filer won't boot and drops back into OK prompt. The last message before OK is
Mon May 2 12:40:23 GMT [emu_admin]: EMU 4 part number 524287 not supported.
I'm not physically co-located with the unit and will have to direct my onsite guy what to check/fix. This old box is self-maintained.
I understand the problem thanks to a peer on this list. We have to replace the defective EMU. Any quick way to identify the failing EMU?
Also the instructions to boot from the floppy, check volume status, remove floppy then boot normally doesn't make much sense. How does that bypass the failing EMU?
Comments, suggestions?
Thanks in advance.
Rgds,
Dan O'Brien, dmobrien@lcsi.net Cell: 614-783-4859 Work: 614-476-8473
Alpha Open Firmware by FirmWorks Copyright 1995-1998 FirmWorks, Network Appliance. All Rights Reserved. Firmware release 2.3_a1
Memory size is 512 MB Testing SIO Testing LCD Probing devices Testing 512MB Complete Finding image... Loading 14 f 5 disk@0 100% Starting ......................................................................... ....
NetApp Release 5.3.6R2: Sat Aug 5 09:40:44 PDT 2000 Copyright (c) 1992-2000 Network Appliance, Inc. Starting boot on Mon May 2 12:40:07 GMT 2005 Scanning for disk drives: ....................................... Configuring disk drives:Local MAC address is 0:60:cf:20:2b:2f 8b.2 8a.13 8b.12 8b.3 8a.12 8a.1 8a.5 8b.11 8b.0 8b.14 8b.5 8a.10 8a.8 8a.9 7a.1 8b.4 8b.8 8b.9 8b.10 8b.1 8b.13 8a.14 8a.11 8a.0 8a.4 8a.3 8a.2 7a.14 7a.10 7a.5 7 a.9 7a.12 7a.13 7a.11 7a.4 7a.0 7a.3 7a.2 7a.8 Disk 7a.11 is reserved for "hot spare"
1 disk is reserved for "hot spare". Restoring parity from NVRAM Loading volume vol0 Replaying WAFL log Mon May 2 12:40:23 GMT [emu_admin]: EMU 4 part number 524287 not supported.
ok
Title: Error Message: "EMU X not supported" - NetApp filer
Problem Environment: NetApp filer
Data ONTAP OS 5.2.x
SCSI storage Shelf 2
EFB
F700 series
F500 series
F300 series
F200 series
Data ONTAP
F600 series
Data ONTAP OS 5.3.x
EMU
Data ONTAP OS 5.1.x
Problem Description Error Message: EMU X not supported
Filer does not boot
Cause of this problem: Normally this error occurs when an EMU module is defective.
Solution: Replace or remove the EMU module that is reported on the console as "not supported" Identify which EMU is reporting errors from the console error message logged during an attempt to boot normally. Since the Filer will boot with out an EMU module there are two choices. a. Remove the EMU module from the shelf, replace it with a new one and boot normally. Please refer to the Network Appliance Storage Shelf 2 hardware guide. b. If a replacement EMU is not readily available, boot the filer using the boot floppy diskettes.
At the "5 item menu", Enter 5 for "Maintenance mode". Enter 'vol status' to ensure none of the volumes have "failed". If all volumes are "online", enter 'halt', remove the floppy diskette from the filer, and at the "OK" prompt enter 'boot'. Obtain an EMU. Schedule downtime as soon as possible so that "hot" disk-swapping and shelf environmental error detection functions can be restored.
NOTE: The filer WILL boot without the EMU module installed and serve data normally. All other functions will work except "hot" disk-swapping and shelf environmental error detection for over temperature, fan fails, and power supply failures.