免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 7693 | 回复: 2

[RAID与磁盘阵列] netapp fas 3040存储宕机,2个控制器都不断重启,求助! [复制链接]

论坛徽章:
0
发表于 2014-01-10 00:15 |显示全部楼层

控制器a:
CFE version 3.1.0 based on Broadcom CFE: 1.0.40
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.
Portions Copyright (c) 2002-2006 Network Appliance, Inc.

CPU type 0xF29: 2800MHz
Total memory: 0x80000000 bytes (2048MB)


Starting AUTOBOOT press any key to abort...
Loading: 0x200000/33111516 0x2193ddc/31331956 0x3f75450/2557763 0x41e5b93/5 Entry at 0x00200000
Starting program at 0x00200000
Press CTRL-C for special boot menu
Thu Jan  9 13:28:51 GMT [nvram.battery.state:info]: The NVRAM battery is currently ON.

NetApp Release 7.2.4: Fri Nov 16 00:07:27 PST 2007
Copyright (c) 1992-2007 Network Appliance, Inc.
Starting boot on Thu Jan  9 13:28:46 GMT 2014
Thu Jan  9 13:29:03 GMT [ispfc_main:error]: Disk 0b.33 has failed to spin up and cannot be used. Please replace it with a new drive.
Thu Jan  9 13:29:03 GMT [disk.init.failureBytes:error]: Disk 0a.44 failed due to failure byte setting.
Thu Jan  9 13:29:03 GMT [disk.init.failureBytes:error]: Disk 0a.45 failed due to failure byte setting.
Thu Jan  9 13:29:03 GMT [disk.init.failureBytes:error]: Disk 0a.43 failed due to failure byte setting.
Thu Jan  9 13:29:03 GMT [disk.init.failureBytes:error]: Disk 0a.41 failed due to failure byte setting.
Thu Jan  9 13:29:03 GMT [disk.init.failureBytes:error]: Disk 0a.38 failed due to failure byte setting.
Thu Jan  9 13:29:03 GMT [disk.init.failureBytes:error]: Disk 0a.39 failed due to failure byte setting.
Thu Jan  9 13:29:03 GMT [disk.init.failureBytes:error]: Disk 0a.32 failed due to failure byte setting.
Thu Jan  9 13:29:03 GMT [disk.init.failureBytes:error]: Disk 0a.37 failed due to failure byte setting.
Thu Jan  9 13:29:03 GMT [disk.init.failureBytes:error]: Disk 0a.36 failed due to failure byte setting.
Thu Jan  9 13:29:03 GMT [diskown.errorReadingOwnership:warning]: error 19 (disk not ready for requested operation) while reading ownership on disk 0b.33 (S/N )
Thu Jan  9 13:29:04 GMT [disk.init.failureBytes:error]: Disk 0a.21 failed due to failure byte setting.
Thu Jan  9 13:29:04 GMT [disk.init.failureBytes:error]: Disk 0a.19 failed due to failure byte setting.
Thu Jan  9 13:29:04 GMT [diskown.errorDuringIO:error]: error 19 (disk not ready for requested operation) on disk 0b.33 (S/N ) while reading individual disk ownership area
Thu Jan  9 13:29:04 GMT [disk.init.failureBytes:error]: Disk 0a.26 failed due to failure byte setting.
Thu Jan  9 13:29:04 GMT [disk.init.failureBytes:error]: Disk 0a.23 failed due to failure byte setting.
Thu Jan  9 13:29:04 GMT [disk.init.failureBytes:error]: Disk 0a.17 failed due to failure byte setting.
Thu Jan  9 13:29:04 GMT [disk.init.failureBytes:error]: Disk 0a.22 failed due to failure byte setting.
Thu Jan  9 13:29:05 GMT [shm.fab.writeSenseError:warning]: shm: Unable to write failure bytes to disk 0b.33 due to error 5/20/0/1.
Thu Jan  9 13:29:05 GMT [disk.releaseFailed:error]: Disk release failed on 0b.33 with return code 5.
Thu Jan  9 13:29:11 GMT [config.noBloop:CRITICAL]: The local node cannot access the partner node's disk shelves because the partner node's shelves are not connected to the local node through their shelf module B.
add net 127.0.0.0: gateway 127.0.0.1
Thu Jan  9 13:29:15 GMT [fmmbx_instanceWorke:info]: missing lock disks, possibly stale mailbox instance on local side
Thu Jan  9 13:29:15 GMT [fmmb.current.lock.disk:info]: Disk 0a.18 is a local HA mailbox disk.
Thu Jan  9 13:29:15 GMT [fmmb.current.lock.disk:info]: Disk ?.? is a local HA mailbox disk.
Use aggr options root in maintenance mode to specify the proper root volume

Waiting to be taken over.  REBOOT in 22 seconds: UNCERTAIN mailbox status in fm_run0
!!!!!
Thu Jan  9 13:29:15 GMT [rc:info]: Node has encountered a multi-disk or other fatal error, waiting to be taken over.
Waiting to be taken over.  REBOOT in 17 seconds.
Waiting to be taken over.  REBOOT in 12 seconds.
Waiting to be taken over.  REBOOT in 7 seconds.
Waiting to be taken over.  REBOOT in 2 seconds.

论坛徽章:
0
发表于 2014-01-10 00:16 |显示全部楼层
控制器B
CFE version 3.0.0 based on Broadcom CFE: 1.0.40
Copyright (C) 2000,2001,2002,2003 Broadcom Corporation.
Portions Copyright (c) 2002-2005 Network Appliance, Inc.

CPU type 0xF29: 2800MHz
Total memory: 0x80000000 bytes (2048MB)


Starting AUTOBOOT press any key to abort...
Loading: 0x200000/33111516 0x2193ddc/31331956 0x3f75450/2557763 0x41e5b93/5 Entry at 0x00200000
Starting program at 0x00200000
Press CTRL-C for special boot menu
Thu Jan  9 14:09:27 GMT [nvram.battery.state:info]: The NVRAM battery is currently ON.

NetApp Release 7.2.4: Fri Nov 16 00:07:27 PST 2007
Copyright (c) 1992-2007 Network Appliance, Inc.
Starting boot on Thu Jan  9 14:09:22 GMT 2014
Thu Jan  9 14:09:39 GMT [ispfc_main:error]: Disk 0b.33 has failed to spin up and cannot be used. Please replace it with a new drive.
Thu Jan  9 14:09:39 GMT [disk.init.failureBytes:error]: Disk 0a.32 failed due to failure byte setting.
Thu Jan  9 14:09:39 GMT [disk.init.failureBytes:error]: Disk 0a.39 failed due to failure byte setting.
Thu Jan  9 14:09:39 GMT [disk.init.failureBytes:error]: Disk 0a.43 failed due to failure byte setting.
Thu Jan  9 14:09:39 GMT [disk.init.failureBytes:error]: Disk 0a.41 failed due to failure byte setting.
Thu Jan  9 14:09:39 GMT [disk.init.failureBytes:error]: Disk 0a.38 failed due to failure byte setting.
Thu Jan  9 14:09:39 GMT [disk.init.failureBytes:error]: Disk 0a.36 failed due to failure byte setting.
Thu Jan  9 14:09:39 GMT [disk.init.failureBytes:error]: Disk 0a.37 failed due to failure byte setting.
Thu Jan  9 14:09:39 GMT [disk.init.failureBytes:error]: Disk 0a.45 failed due to failure byte setting.
Thu Jan  9 14:09:39 GMT [disk.init.failureBytes:error]: Disk 0a.44 failed due to failure byte setting.
Thu Jan  9 14:09:39 GMT [diskown.errorReadingOwnership:warning]: error 19 (disk not ready for requested operation) while reading ownership on disk 0b.33 (S/N )
Thu Jan  9 14:09:40 GMT [disk.init.failureBytes:error]: Disk 0a.17 failed due to failure byte setting.
Thu Jan  9 14:09:40 GMT [disk.init.failureBytes:error]: Disk 0a.21 failed due to failure byte setting.
Thu Jan  9 14:09:40 GMT [diskown.errorDuringIO:error]: error 19 (disk not ready for requested operation) on disk 0b.33 (S/N ) while reading individual disk ownership area
Thu Jan  9 14:09:40 GMT [disk.init.failureBytes:error]: Disk 0a.26 failed due to failure byte setting.
Thu Jan  9 14:09:40 GMT [disk.init.failureBytes:error]: Disk 0a.23 failed due to failure byte setting.
Thu Jan  9 14:09:40 GMT [disk.init.failureBytes:error]: Disk 0a.22 failed due to failure byte setting.
Thu Jan  9 14:09:40 GMT [disk.init.failureBytes:error]: Disk 0a.19 failed due to failure byte setting.
Thu Jan  9 14:09:41 GMT [disk.releaseFailed:error]: Disk release failed on 0b.33 with return code 5.
No disks were detected on Fibre Channel port A
Rebooting... (ctrl-c to break reboot loop)

论坛徽章:
0
发表于 2014-01-15 13:53 |显示全部楼层
有可能是硬盘背板的问题
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们:huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP