storage down

[virendrata]

Hi All,

We have a NetApp 2050 with NetApp Release 7.3.5.1.

Our storage is down and booting continously as the root volume have failed. Can you please let me know if we can recover the data.

++++++++++++++++++++++++++

Boot Loader version 1.3
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.
Portions Copyright (C) 2002-2006 Network Appliance Inc.

2048MB RAM installed
CPU Type: Mobile Intel(R) Celeron(R) CPU 2.20GHz

Starting AUTOBOOT press Ctrl-C to abort...
Loading:....................0x200000/44314868 0x2c430f4/14474492 0x3a10df0/1414090 0x3b6a1ba/6 Entry at 0x00200000
Starting program at 0x00200000
Press CTRL-C for special boot menu
The platform doesn't support service processor
Thu May 17 05:40:13 GMT [cf.nm.nicTransitionUp:info]: Interconnect link 0 is UP
Thu May 17 05:40:20 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 0b.
Thu May 17 05:40:20 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 1b.
Thu May 17 05:40:21 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 1a.
Thu May 17 05:40:21 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 1d.
Thu May 17 05:40:21 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 1c.

NetApp Release 7.3.5.1: Sat Jan 29 12:45:56 PST 2011
Copyright (c) 1992-2010 NetApp.
Starting boot on Thu May 17 05:40:05 GMT 2018
Thu May 17 05:40:24 GMT [nvram.battery.turned.on:info]: The NVRAM battery is turned ON. It is turned OFF during system shutdown.
Thu May 17 05:40:27 GMT [disk.init.failure.spinup:error]: Disk 0c.00.6 has failed to spin up and cannot be used. Please replace it with a new drive.
Thu May 17 05:40:27 GMT [disk.init.failure.spinup:error]: Disk 0c.00.8 has failed to spin up and cannot be used. Please replace it with a new drive.
Thu May 17 05:40:27 GMT [disk.init.failure.spinup:error]: Disk 0c.00.10 has failed to spin up and cannot be used. Please replace it with a new drive.
Thu May 17 05:40:27 GMT [disk.init.failure.spinup:error]: Disk 0c.00.11 has failed to spin up and cannot be used. Please replace it with a new drive.
Thu May 17 05:40:27 GMT [diskown.isEnabled:info]: software ownership has been enabled for this system
Thu May 17 05:40:31 GMT [config.noPartnerDisks:CRITICAL]: No disks were detected for the partner; this node will be unable to takeover correctly
Thu May 17 05:40:31 GMT [fmmb.current.lock.disk:info]: Disk 0a.16 is a local HA mailbox disk.
Thu May 17 05:40:31 GMT [fmmb.current.lock.disk:info]: Disk 0a.17 is a local HA mailbox disk.
Thu May 17 05:40:31 GMT [fmmb.instStat.change:info]: normal mailbox instance on local side.
Thu May 17 05:40:32 GMT [fmmb.instStat.change:info]: no mailbox instance on partner side.
Root volume is failed (all disks may not yet be visible).
Rebooting... (ctrl-c to break reboot loop)

*> aggr status
Aggr State Status Options
aggr0 failed raid_dp, aggr diskroot, ignore_inconsistent=on,
partial lost_write_protect=off
No root aggregate or root traditional volume found.
You must specify a root aggregate or traditional volume with
"aggr options <name> root" before rebooting the system.

[GidonMarcus]

hi

# any operation in response to this thread are on your own risk. no one here take any responsibility on the consequences. this is a open forum and responses here can be written by anyone #

What is the situation with the partner ? if the partner online be extra careful with what you doing so you don't take it down.

for the disks that fail sppining. tTry re-seating the disks boot again.

if it fail and come back to loader, go again to boot_diags anf - try the "disk unfail " command for each of them.

if that fail, please privde "sysconfig -a" and "sysconfig -r" outputs.

if all attempts to bring the root up. you can re-create it with new disks. or if you don't have them. try to take disks ownership by the partner and re-map the shares/exports/lun on the filer

Gidi