NetApp存储无法开机问题处理-(初始化重装系统)

测试环境:    
原有存储是两个独立控制器+磁盘柜,目前是一个控制器+磁盘柜。开机启动时,先开启扩展柜,一分钟后开启控制器。发现系统起不来,经过多次尝试失败后,决定通过维护模式进入系统进行查看。(类似于Windows7的维护模式一样)

问题处理:    
开机boot启动项,按Ctrl+C命令中断正常启动,进入到boot menu菜单。    
Starting AUTOBOOT press Ctrl-C to abort...    
Loading X86_64/freebsd/image1/kernel:0x200000/10088648 0xb9f0c8/4301024 Entry at 0x80271e20    
Loading X86_64/freebsd/image1/platform.ko:0xfba000/1990365 0x11a0000/296352 0x11e85a0/273360    
Starting program at 0x80271e20    
NetApp Data ONTAP 8.3.1P2    
Copyright (C) 1992-2015 NetApp.    
All rights reserved.    
Checking boot device filesystem    
** /dev/da0s1    
** Phase 1 - Read and Compare FATs    
** Phase 2 - Check Cluster Chains    
** Phase 3 - Checking Directories    
** Phase 4 - Checking for Lost Files    
69 files, 1011584 free (31612 clusters)    
MARK FILE SYSTEM CLEAN? yes    
MARKING FILE SYSTEM CLEAN    
Retry #1 of 5: /sbin/fsck_msdosfs /dev/da0s1    
Retry #2 of 5: /sbin/fsck_msdosfs /dev/da0s1    
Repaired boot device filesystem    
*******************************    
*                             *    
* Press Ctrl-C for Boot Menu. *    
*                             *    
*******************************     
^CBoot Menu will be available.

WARNING:  The battery is unfit to retain data during a power  
          outage.  This is likely because the battery is    
          discharged but could be due to other temporary    
          conditions.    
          When the battery is ready, the boot process will    
          complete and services will be engaged.    
          To override this delay, press ‘c‘ followed by ‘Enter‘    
c

CAUTION: Using this appliance without NVRAM  
         battery backup coupled with a power    
         failure condition CAN CAUSE DATA LOSS.    
Are you sure you want to continue (y or n)? y    
Proceeding without NVRAM battery backup.

Please choose one of the following:

(1) Normal Boot.        #正常启动    
(2) Boot without /etc/rc.   #启动存储时,不执行/etc/rc设置参数    
(3) Change password.      #如果忘记了超级用户密码,可以在此修改    
(4) Clean configuration and initialize all disks. #清除配置,初始化所有的磁盘    
(5) Maintenance mode boot.  #进入维护模式,当系统进不去的时候可以尝试用维护模式进入    
(6) Update flash from backup config. #从备份配置中升级flash    
(7) Install new software first.    #安装新的软件    
(8) Reboot node.         #重启节点    
Selection (1-8)? 5    
ixgbe: e1a: ** JUMBOMBUF DEBUG ** switching to large buffers(9k -> 3k): (sz = 5120)!    
ixgbe: e1b: ** JUMBOMBUF DEBUG ** switching to large buffers(9k -> 3k): (sz = 5120)!    
ixgbe: e2a: ** JUMBOMBUF DEBUG ** switching to large buffers(9k -> 3k): (sz = 5120)!    
ixgbe: e2b: ** JUMBOMBUF DEBUG ** switching to large buffers(9k -> 3k): (sz = 5120)!    
Ipspace "iwarp-ipspace" created    
WAFL CPLEDGER is enabled. Checklist = 0x7ff841ff    
add host 127.0.10.1: gateway 127.0.20.1    
5    
    You have selected the maintenance boot option:    
    the system has booted in maintenance mode allowing the    
    following operations to be performed:    
    ?                     acorn            
    acpadmin              aggr             
    cna_flash             disk             
    disk_latency          disk_list        
    disk_mung             disk_shelf       
    diskcopy              disktest         
    dumpblock             environment      
    fcadmin               fcstat           
    fctest                fru_led          
    ha-config             halt             
    help                  ifconfig         
    key_manager           led_off          
    led_on                nv8              
    raid_config           sasadmin         
    sasstat               scsi             
    sesdiag               sldiag           
    storage               stsb             
    sysconfig             systemshell      
    ucadmin               version          
    vmservices            vol              
    vol_db                vsa              
    xortest          
    Type "help <command>" for more details.

In a High Availablity configuration, you MUST ensure that the    
    partner node is (and remains) down, or that takeover is manually    
    disabled on the partner node, because High Availability    
    software is not started or fully enabled in Maintenance mode.

FAILURE TO DO SO CAN RESULT IN YOUR FILESYSTEMS BEING DESTROYED

NOTE: It is okay to use ‘show/status‘ sub-commands such as  
    ‘disk show or aggr status‘ in Maintenance mode while the partner is up    
Continue with boot? y    
y    
Ipspace "acp-ipspace" created    
original max threads=40, original heap size=41943040    
bip_nitro Virtual Size Limit=79455027 Bytes    
bip_nitro: user memory=724406272, actual max threads=41, actual heap size=43201331    
WARNING: Giving up waiting for mroot    
Tue Feb 14 07:59:49 UTC 2017    
*> ? #可以看到在维护模式下支持的命令参数    
?                   disktest            key_manager         stsb               
acorn               dumpblock           led_off             sysconfig          
acpadmin            environment         led_on              systemshell        
aggr                fcadmin             nv8                 ucadmin            
cna_flash           fcstat              raid_config         version            
disk                fctest              sasadmin            vmservices         
disk_latency        fru_led             sasstat             vol                
disk_list           ha-config           scsi                vol_db             
disk_mung           halt                sesdiag             vsa                
disk_shelf          help                sldiag              xortest            
diskcopy            ifconfig            storage            
*> disk show    
Local System ID: 1575136460

DISK       OWNER                    POOL   SERIAL NUMBER         HOME                    DR HOME    
------------ -------------            -----  -------------         -------------           -------------           
0a.10.6      sz-3240-02(1575136687)    Pool0  LXW6RH4M              sz-3240-02(1575136687)                        
0b.10.7      sz-3240-02(1575136687)    Pool0  LXW63XYM              sz-3240-02(1575136687)                        
0a.10.2      sz-3240-01(1575136460)    Pool0  LXW72ZGM              sz-3240-01(1575136460)                        
0b.10.5      sz-3240-01(1575136460)    Pool0  LXW1W02M              sz-3240-01(1575136460)                        
0b.10.11     sz-3240-02(1575136687)    Pool0  LXW6364M              sz-3240-02(1575136687)                        
0a.10.8      sz-3240-02(1575136687)    Pool0  LXV3HE7L              sz-3240-02(1575136687)                        
0b.10.9      sz-3240-02(1575136687)    Pool0  LXW5YNSM              sz-3240-02(1575136687)                        
0a.10.4      sz-3240-01(1575136460)    Pool0  LXWT76HL              sz-3240-01(1575136460)                        
0b.10.3      sz-3240-01(1575136460)    Pool0  LXW6ELRM              sz-3240-01(1575136460)                        
0a.10.10     sz-3240-02(1575136687)    Pool0  LXW6DTTM              sz-3240-02(1575136687)                        
0b.10.1      sz-3240-01(1575136460)    Pool0  LXW6R84M              sz-3240-01(1575136460)                        
0a.10.0      sz-3240-01(1575136460)    Pool0  LXV3GV4L              sz-3240-01(1575136460)                        
由上图可以看到,存储12块磁盘被平均分配到了两个控制器上,由于目前只有一个控制器,所以很有可能系统在另外一个控制器上,而另外一个控制器缺少,导致开机无法启动。    
现在手工把所有的磁盘都分配到当前控制器上。      
*> disk reassign -s 1575136687 -d 1575136460 
#把1575136687控制器上的磁盘都重新分配给1575136460控制器    
#reassign {-s <old_sysid>} [-d <new_sysid>] [-p <partner_sysid>]- reassign disks from old filer    
Partner node must not be in Takeover mode during disk reassignment from maintenance mode.    
Serious problems could result!!    
Do not proceed with reassignment if the partner is in takeover mode. Abort reassignment (y/n)? n    
After the node becomes operational, you must perform a takeover and giveback of the HA partner node to ensure disk reassignment is successful.    
Do you want to continue (y/n)? y    
Disk ownership will be updated on all disks previously belonging to Filer with sysid 1575136687.    
Do you want to continue (y/n)? y    
Cannot do remote rescan. Use ‘run local disk show‘ on the console of sz-3240-01 for it to scan the newly assigned disks    
Feb 14 08:04:52 [sz-3240-01:diskown.RescanMessageFailed:warning]: Could not send rescan message to sz-3240-01. Use the "disk show" command in nodeshell of sz-3240-01 for it to scan the newly inserted disks.    
*> disk show                               
Local System ID: 1575136460

DISK       OWNER                    POOL   SERIAL NUMBER         HOME                    DR HOME    
------------ -------------            -----  -------------         -------------           -------------           
0a.10.6   sz-3240-01(1575136460)    Pool0  LXW6RH4M              sz-3240-01(1575136460)                        
0b.10.7   sz-3240-01(1575136460)    Pool0  LXW63XYM              sz-3240-01(1575136460)                        
0a.10.2   sz-3240-01(1575136460)    Pool0  LXW72ZGM              sz-3240-01(1575136460)                        
0b.10.5   sz-3240-01(1575136460)    Pool0  LXW1W02M              sz-3240-01(1575136460)                        
0b.10.11  sz-3240-01(1575136460)    Pool0  LXW6364M              sz-3240-01(1575136460)                        
0a.10.8   sz-3240-01(1575136460)    Pool0  LXV3HE7L              sz-3240-01(1575136460)                        
0b.10.9   sz-3240-01(1575136460)    Pool0  LXW5YNSM              sz-3240-01(1575136460)                        
0a.10.4   sz-3240-01(1575136460)    Pool0  LXWT76HL              sz-3240-01(1575136460)                        
0b.10.3   sz-3240-01(1575136460)    Pool0  LXW6ELRM              sz-3240-01(1575136460)                        
0a.10.10  sz-3240-01(1575136460)    Pool0  LXW6DTTM              sz-3240-01(1575136460)                        
0b.10.1   sz-3240-01(1575136460)    Pool0  LXW6R84M              sz-3240-01(1575136460)                        
0a.10.0   sz-3240-01(1575136460)    Pool0  LXV3GV4L              sz-3240-01(1575136460)                        
现在所有的磁盘都已经划分到现有控制器下了,接下来重新安装存储操作系统:    
*> halt    
Waiting for PIDS:  624.    
Terminated    
Uptime: 8m46s    
System halting...    
Phoenix TrustedCore(tm) Server    
Copyright 1985-2006 Phoenix Technologies Ltd.    
All Rights Reserved    
BIOS version: 5.3.0    
Portions Copyright (c) 2007-2014 NetApp, Inc. All Rights Reserved

CPU = 1 Processors Detected, Cores per Processor = 4  
Intel(R) Xeon(R) CPU           L5410  @ 2.33GHz    
Testing RAM    
512MB RAM tested    
8192MB RAM installed    
6144 KB L2 Cache    
System BIOS shadowed    
USB 2.0: MICRON eUSB DISK    
BIOS is scanning PCI Option ROMs, this may take a few seconds...    
+++++++++++++++++++    
Boot Loader version 3.6    
Copyright (C) 2000-2003 Broadcom Corporation.    
Portions Copyright (C) 2002-2014 NetApp, Inc. All Rights Reserved.    
CPU Type: Intel(R) Xeon(R) CPU           L5410  @ 2.33GHz    
机器起来后,要手工启动存储的系统:    
LOADER-A> boot_ontap    
Loading X86_64/freebsd/image1/kernel:0x200000/10088648 0xb9f0c8/4301024 Entry at 0x80271e20    
Loading X86_64/freebsd/image1/platform.ko:0xfba000/1990365 0x11a0000/296352 0x11e85a0/273360    
Starting program at 0x80271e20    
NetApp Data ONTAP 8.3.1P2    
Copyright (C) 1992-2015 NetApp.    
All rights reserved.    
*******************************    
*                             *    
* Press Ctrl-C for Boot Menu. *    
*                             *    
*******************************     
^CBoot Menu will be available.

WARNING:  The battery is unfit to retain data during a power  
          outage.  This is likely because the battery is    
          discharged but could be due to other temporary    
          conditions.    
          When the battery is ready, the boot process will    
          complete and services will be engaged.    
          To override this delay, press ‘c‘ followed by ‘Enter‘    
c

CAUTION: Using this appliance without NVRAM  
         battery backup coupled with a power    
         failure condition CAN CAUSE DATA LOSS.    
Are you sure you want to continue (y or n)? y    
Proceeding without NVRAM battery backup.

Please choose one of the following:

(1) Normal Boot.  
(2) Boot without /etc/rc.    
(3) Change password.    
(4) Clean configuration and initialize all disks.    
(5) Maintenance mode boot.    
(6) Update flash from backup config.    
(7) Install new software first.    
(8) Reboot node.    
Selection (1-8)? 4    
ixgbe: e1a: ** JUMBOMBUF DEBUG ** switching to large buffers(9k -> 3k): (sz = 5120)!    
ixgbe: e1b: ** JUMBOMBUF DEBUG ** switching to large buffers(9k -> 3k): (sz = 5120)!    
ixgbe: e2a: ** JUMBOMBUF DEBUG ** switching to large buffers(9k -> 3k): (sz = 5120)!    
ixgbe: e2b: ** JUMBOMBUF DEBUG ** switching to large buffers(9k -> 3k): (sz = 5120)!    
Ipspace "iwarp-ipspace" created    
WAFL CPLEDGER is enabled. Checklist = 0x7ff841ff    
add host 127.0.10.1: gateway 127.0.20.1    
Zero disks, reset config and install a new file system?:    
Please answer yes or no    
Zero disks, reset config and install a new file system?: yes    
This will erase all the data on the disks, are you sure?: y    
Rebooting to finish wipeconfig request.    
Waiting for PIDS:  615.    
Skipped backing up /var file system to CF.    
Terminated    
.    
Uptime: 3m13s    
System rebooting...

Phoenix TrustedCore(tm) Server    
Copyright 1985-2006 Phoenix Technologies Ltd.    
All Rights Reserved    
BIOS version: 5.3.0    
Portions Copyright (c) 2007-2014 NetApp, Inc. All Rights Reserved

CPU = 1 Processors Detected, Cores per Processor = 4  
Intel(R) Xeon(R) CPU           L5410  @ 2.33GHz    
Testing RAM    
512MB RAM tested    
8192MB RAM installed    
6144 KB L2 Cache    
System BIOS shadowed    
USB 2.0: MICRON eUSB DISK    
BIOS is scanning PCI Option ROMs, this may take a few seconds...    
+++++++++++++++++++    
Boot Loader version 3.6    
Copyright (C) 2000-2003 Broadcom Corporation.    
Portions Copyright (C) 2002-2014 NetApp, Inc. All Rights Reserved.

CPU Type: Intel(R) Xeon(R) CPU           L5410  @ 2.33GHz

Starting AUTOBOOT press Ctrl-C to abort...  
Loading X86_64/freebsd/image1/kernel:0x200000/10088648 0xb9f0c8/4301024 Entry at 0x80271e20    
Loading X86_64/freebsd/image1/platform.ko:0xfba000/1990365 0x11a0000/296352 0x11e85a0/273360    
Starting program at 0x80271e20    
NetApp Data ONTAP 8.3.1P2    
Copyright (C) 1992-2015 NetApp.    
All rights reserved.    
*******************************    
*                             *    
* Press Ctrl-C for Boot Menu. *    
*                             *    
*******************************     
Wipe filer procedure requested.

WARNING:  The battery is unfit to retain data during a power  
          outage.  This is likely because the battery is    
          discharged but could be due to other temporary    
          conditions.    
          When the battery is ready, the boot process will    
          complete and services will be engaged.    
          To override this delay, press ‘c‘ followed by ‘Enter‘    
c

CAUTION: Using this appliance without NVRAM  
         battery backup coupled with a power    
         failure condition CAN CAUSE DATA LOSS.    
Are you sure you want to continue (y or n)? y    
Proceeding without NVRAM battery backup.    
ixgbe: e1a: ** JUMBOMBUF DEBUG ** switching to large buffers(9k -> 3k): (sz = 5120)!    
ixgbe: e1b: ** JUMBOMBUF DEBUG ** switching to large buffers(9k -> 3k): (sz = 5120)!    
ixgbe: e2a: ** JUMBOMBUF DEBUG ** switching to large buffers(9k -> 3k): (sz = 5120)!    
ixgbe: e2b: ** JUMBOMBUF DEBUG ** switching to large buffers(9k -> 3k): (sz = 5120)!    
original max threads=40, original heap size=41943040    
bip_nitro Virtual Size Limit=80844390 Bytes    
bip_nitro: user memory=742682624, actual max threads=42, actual heap size=44459622    
Ipspace "iwarp-ipspace" created    
WAFL CPLEDGER is enabled. Checklist = 0x7ff841ff    
add host 127.0.10.1bootarg.bootmenu.selection is |4a|    
: gateway 127.0.20.1    
..............................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................    
接下来就漫长的等待了,初始化的时候是所有的硬盘同时做条带化,与硬盘数目多少无关,只与硬盘容量和转数相关。    
重启完成后,就会进入到初始化配置界面,包括集群设置、IP地址设置等等(后面会介绍,尽情期待)

时间: 2024-10-19 05:11:29

NetApp存储无法开机问题处理-(初始化重装系统)的相关文章

重置出错?微软Win10平板Surface Pro 4重装系统教程详解

重置出错?微软Win10平板Surface Pro 4重装系统教程详解 2015-12-11 15:27:30来源:IT之家作者:凌空责编:凌空 评论:65 Surface Pro 4系统重置出错该怎么办? Surface Pro 4无法启动该怎办? Surface Pro 4平板如何重装Win10系统? 在Win10刚刚发布时,很多用户在升级Windows10后重置系统时遇到了错误.这一问题在微软自家Surface平板中也同样可能出现.今天IT之家在重置一台Surface Pro 4平板时就遇

使用Perfstat工具收集Netapp存储诊断信息

概要简介 Perfstat是一个Netapp存储诊断数据命令行收集工具,该工具能够收集Netapp存储的详尽的信息,包括配置信息和性能数据,针对于Netapp存储OS的2种模式分别有两个版本: 存储模式 Perfstat版本 7 mode Perfstat 7 Cluster Mode Perfstat 8 perfstat 7.x用于收集 7 mode Netapp存储的信息,perfstat 8.x主要用于收集Cluster mode Netapp存储信息 注意: 从Netapp Data

netAPP存储恢复删除数据方法-留着万一有用呢

[存储数据恢复背景介绍] 某公司的netAPP存储设备,因为实习生在操作过程中的误操作导致存储内部分重要数据被删除,该存储采用的是WAFL文件系统,底层是多块硬盘组成的raid阵列.下面小编将为大家详细介绍该案例的数据恢复过程,同时该数据恢复方法同样适用于netAPP其他型号存储的误删除数据的恢复. [存储数据误删除恢复方法] 对存储设备的原始数据进行镜像备份,这样做的目的是为了在数据恢复过程中对镜像数据进行分析与恢复,保留用户的存储设备原始状态,以免因数据恢复工作人员的操作对原始数据进行更改或

NetApp存储数据误删除恢复报告

一.NetApp存储阵列简要: NetApp FAS3220是NetApp推出的中端存储阵列,针对NAS和SAN环境构建,被定制为虚拟化.私有云或传统.早先的用途,适用于从几TB到超过2PB的存储需求,提供数据保护,可扩展性,自动精简配置,精简克隆,备份和灾难恢复,下面就讲解NetApp FAS 3220存储的数据恢复的方法. 二.NetApp存储阵列故障信息: 本次讲解的NetApp FAS 3220型号的存储,硬件环境是一共96块600G的SAS硬盘,硬盘和普通的硬盘还不一样,这个硬盘的扇区

重装系统必做之——更换Windows系统的默认临时文件的存储目录

作为一名计算机爱好者,重装电脑是家常便饭,但是重装电脑的目的无非就是: 1.操作系统更新换代: 2.系统速度太慢: 或者更多.... 我们大多数目的都是上述中第2点,有时候是否仅仅重装系统而忽略了一些可能必要的优化工作呢? 我有个习惯,就是在重装后做做C盘(系统盘)的工作,尤其是——更换系统默认的临时文件存放目录. 随着我们电脑使用的时间增加,系统默认的临时文件夹里的“垃圾”就会越来越多,占用C盘空间,这对于我这种轻度强迫症患者来说已经是不可容忍的了,但是,我们不可能每天去翻翻C盘的Temp文件

DELL Precision Tower7910重装系统+开机出现GRUB界面如何处理

想给实验室的工作站重新装个Win7系统,因为以前并没装过工作站的系统,发现和普通的电脑装系统还是有些不一样的.主要的问题就在于主板的不同. 尝试了老毛桃U盘启动盘安装,结果在WinPE里面提示找不到硬盘,修复引导也不行,失败. 尝试了开机之后采用硬盘装系统,结果前面进行的都很顺利,却在一次重启之后电脑蓝屏了,如下图所示,也告知失败. 尝试了用软碟通(Ultraiso)刻录了系统盘进行安装,也是不行. 最后上DELL官网上看了下,找到了一个安装教程,使用光盘安装的,并且这里还有个重点,安装系统的时

华硕笔记本重装系统bios设置

华硕笔记本重装系统bios设置 华硕笔记本重装系统bios设置怎么弄?华硕笔记本bios设置是怎样的?为什么需要华硕笔记本重装系统bios设置?现在小编就来跟大家介绍下华硕笔记本bios设置. 对于笔记本怎么重装系统来说,不少笔记本都是需要简单更改下Bios设置,才可以从光盘或者是U盘启动,而这个华硕笔记本也是不例外. 华硕笔记本重装系统之修改BIOS设置: 1. 首先大家电脑开机后按F2键进入Bios设置. 华硕笔记本重装系统bios设置(图1) 2. 然后切换到Security标签,接着找到

重装系统(win7)

-_-|| 第一次装,可谓艰难险阻 一:准备 1.U盘(大小至少4G)——本人用了4G的 2.查询自己的电脑进入BIOS的方法——本人电脑机型为华硕X550VC,开机长按F2(当时为保险起见,也同时按了Fn) 3.电脑里的需要的东西,该备份的备份到别的U盘或者移动硬盘去 二:制作 1.制作U盘启动盘——本人用的老毛桃(http://www.laomaotao.in/) U盘启动盘制作工具,下载——本人下载了装机版——教程如下http://www.laomaotao.org/jiaocheng/9

更换电脑主板,又不想重装系统的解决方法

现在很多计算机用户在更换新硬件是更偏向于DIY,所以这篇教程写给那些自己换主板,但是不知道如何保留现有操作系统的用户. 在开始之前,先说明一下这篇教程的方法:本教程是通过卸载现有主板芯片组驱动和控制器驱动的方法,以防止发生更换主板之后和原有驱动发生冲突,导致不能开机必须重装系统的现象. 特别说明:本教程仅供参考,且更换主板适合有一定计算机硬件操作基础的用户,如果您对计算机中的主板构造不够了解,很容易造成硬件方面的损坏. 准备工作:准备更换系统的主机一台(正常开机),一块新主板,螺丝刀.特别注意: