Shulou(Shulou.com)06/02 Report--

Test environment:

The original storage is two independent controllers + disk cabinets, which is currently a controller + disk cabinets. When starting up, open the expansion cabinet first, and then turn on the controller one minute later. Found that the system can not get up, after many failed attempts, decided to enter the system through maintenance mode to check. (similar to the maintenance mode of Windows7)

Problem handling:

Boot the boot startup item, press the Ctrl+C command to interrupt the normal startup, and enter the boot menu menu.

Starting AUTOBOOT press Ctrl-C to abort...

Loading X86_64/freebsd/p_w_picpath2/kernel:0x200000/10088648 0xb9f0c8/4301024 Entry at 0x80271e20

Loading X86_64/freebsd/p_w_picpath2/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. # start normally

(2) Boot without / etc/rc. # when starting storage, the / etc/rc setting parameter is not executed

(3) Change password. # if you forget the superuser password, you can change it here

(4) Clean configuration and initialize all disks. # clear the configuration and initialize all disks

(5) Maintenance mode boot. # enter maintenance mode. When the system cannot enter, you can try to use maintenance mode to enter.

(6) Update flash from backup config. # upgrade flash from backup configuration

(7) Install new software first. # install new software

(8) Reboot node. # restart the node

Selection (1-8)? 5

Ixgbe: E1A: * * JUMBOMBUF DEBUG * * switching to large buffers (9k-> 3k): (sz = 5120)!

Ixgbe: ELB: * * 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

five

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" 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

* >? # you can see the command parameters supported in maintenance mode

? 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)

As you can see from the figure above, the storage of 12 disks is evenly distributed between the two controllers. Since there is currently only one controller, it is very likely that the system is on another controller, while the other controller is missing, resulting in boot failure.

Now manually assign all the disks to the current controller.

* > disk reassign-s 1575136687-d 1575136460

# reassign all disks on the 1575136687 controller to the 1575136460 controller

# reassign {- s} [- d] [- p]-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 (YBO)? 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 (YBO)? Y

Disk ownership will be updated on all disks previously belonging to Filer with sysid 1575136687.

Do you want to continue (YBO)? 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)

Now that all the disks are divided under the existing controller, reinstall the storage operating system:

* > 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

After the machine is up, start the storage system manually:

LOADER-A > boot_ontap

Loading X86_64/freebsd/p_w_picpath2/kernel:0x200000/10088648 0xb9f0c8/4301024 Entry at 0x80271e20

Loading X86_64/freebsd/p_w_picpath2/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: ELB: * * 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/p_w_picpath2/kernel:0x200000/10088648 0xb9f0c8/4301024 Entry at 0x80271e20

Loading X86_64/freebsd/p_w_picpath2/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: ELB: * * 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

. . . . .

Then there is a long wait. During initialization, all the hard drives are striped at the same time, which has nothing to do with the number of hard drives, but only related to the capacity and revolutions of the hard drives.

After the restart is completed, you will go to the initialization configuration interface, including cluster settings, IP address settings, and so on (described later, and look forward to it)

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.