ONTAP Hardware

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

ONTAP Hardware

Ask a Question

Shelves with 3240 Single enclosure non-HA, with I/O expansion module

KCOKYAMAN
‎2013-01-21 07:05 AM
5,422 Views

Hi Everyone,

How can i reconfigure old fas3240 system. I have 1 fas3240 single enc. non-ha, 2 shelves. I 'm connecting shelves to my fas3240 system and boot.

I get an error messages below when booting;

Starting AUTOBOOT press Ctrl-C to abort...
Loading X86_64/kernel/primary.krn:0x200000/49212136 0x30eeae8/23754912 0x4796388/7980681 0x4f32a11/7 Entry at 0x00202018
Starting program at 0x00202018
MTRR0, will be reset to map region 3G to 4G as UC
BBSP on this platform is 0x0000000000000180
ipmi_init_alloc_request_pool succeed (pool entries 0x80,size per entry 0xe0)
ipmi_init0: DONE.
Press CTRL-C for special boot menu
IPMI:IPMI device rev. 2, firmware rev. 1.0, version 2.0
IPMI:Number of channels 0
ipmi_init1: DONE.
Special boot options menu will be available.
Chelsio T3 RDMA Driver - version 0.1
Ipspace "iwarp-ipspace" created
NetApp Release 7.3.7: Thu May  3 03:48:45 PDT 2012
Copyright (c) 1992-2012 NetApp.
Starting boot on Mon Jan 21 14:39:22 GMT 2013
Mon Jan 21 14:39:39 GMT [nvram.battery.turned.on:info]: The NVRAM battery is turned ON. It is turned OFF during system shutdown.
Mon Jan 21 14:39:44 GMT [diskown.isEnabled:info]: software ownership has been enabled for this system
Mon Jan 21 14:39:49 GMT [sas.link.error:error]: Could not recover link on SAS adapter 0b after 10 seconds. Offlining the adapter.
Mon Jan 21 14:39:49 GMT [sas.link.error:error]: Could not recover link on SAS adapter 1d after 10 seconds. Offlining the adapter.
Mon Jan 21 14:39:52 GMT [sas.link.error:error]: Could not recover link on SAS adapter 1a after 10 seconds. Offlining the adapter.
Mon Jan 21 14:39:52 GMT [sas.link.error:error]: Could not recover link on SAS adapter 1b after 10 seconds. Offlining the adapter.
Mon Jan 21 14:39:58 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 1c.02.5: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3e8:0018.
Mon Jan 21 14:39:58 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 1c.02.4: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3e8:0018.
Mon Jan 21 14:39:58 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 1c.02.2: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3e8:0018.
Mon Jan 21 14:39:58 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 1c.02.3: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3e8:0018.
Mon Jan 21 14:39:58 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 1c.02.0: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3e8:0018.
Mon Jan 21 14:39:58 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 1c.02.1: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3e8:0018.
Mon Jan 21 14:40:11 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 0a.02.5: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3e8:0018.
Mon Jan 21 14:40:11 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 0a.02.4: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3e8:0018.
Mon Jan 21 14:40:11 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 0a.02.2: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3e8:0018.
Mon Jan 21 14:40:11 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 0a.02.0: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3e8:0018.
Mon Jan 21 14:40:11 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 0a.02.1: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3e8:0018.
Mon Jan 21 14:40:11 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 0a.02.3: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3e8:0018.
Mon Jan 21 14:40:12 GMT [diskown.errorReadingOwnership:warning]: error 23 (adapter error prevents command from being sent to device) while reading ownership on disk 1c.02.5 (S/N S0PCNEAB700933)
Mon Jan 21 14:40:12 GMT [diskown.errorReadingOwnership:warning]: error 23 (adapter error prevents command from being sent to device) while reading ownership on disk 1c.02.4 (S/N S0PCNEAB700934)
Mon Jan 21 14:40:12 GMT [diskown.errorReadingOwnership:warning]: error 23 (adapter error prevents command from being sent to device) while reading ownership on disk 1c.02.2 (S/N S0PCNEAB700961)
Mon Jan 21 14:40:12 GMT [diskown.errorReadingOwnership:warning]: error 23 (adapter error prevents command from being sent to device) while reading ownership on disk 1c.02.0 (S/N S0PCNEAB700964)
Mon Jan 21 14:40:12 GMT [diskown.errorReadingOwnership:warning]: error 23 (adapter error prevents command from being sent to device) while reading ownership on disk 1c.02.1 (S/N S0PCNEAB700937)
Mon Jan 21 14:40:12 GMT [diskown.errorReadingOwnership:warning]: error 23 (adapter error prevents command from being sent to device) while reading ownership on disk 1c.02.3 (S/N S0PCNEAB700938)
Mon Jan 21 14:40:27 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 0a.02.5: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3f0:0008.
Mon Jan 21 14:40:27 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 0a.02.4: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3f0:0008.
Mon Jan 21 14:40:27 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 0a.02.3: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3f0:0008.
Mon Jan 21 14:40:27 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 0a.02.0: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3f0:0008.
Mon Jan 21 14:40:27 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 0a.02.1: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3f0:0008.
Mon Jan 21 14:40:27 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 0a.02.2: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3f0:0008.
Mon Jan 21 14:40:40 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 1c.02.5: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3f0:0008.
Mon Jan 21 14:40:40 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 1c.02.3: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3f0:0008.
Mon Jan 21 14:40:40 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 1c.02.4: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3f0:0008.
Mon Jan 21 14:40:40 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 1c.02.2: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3f0:0008.
Mon Jan 21 14:40:40 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 1c.02.0: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3f0:0008.
Mon Jan 21 14:40:40 GMT [scsi.cmd.adapterHardwareError:error]: Disk device 1c.02.1: Adapter detected hardware error: HA status 0xb: cdb 0x28:0000a3f0:0008.
Mon Jan 21 14:40:41 GMT [diskown.errorDuringIO:error]: error 23 (adapter error prevents command from being sent to device) on disk 1c.02.5 (S/N S0PCNEAB700933) while reading individual disk ownership area
Mon Jan 21 14:40:41 GMT [diskown.errorDuringIO:error]: error 23 (adapter error prevents command from being sent to device) on disk 1c.02.3 (S/N S0PCNEAB700938) while reading individual disk ownership area
Mon Jan 21 14:40:41 GMT [diskown.errorDuringIO:error]: error 23 (adapter error prevents command from being sent to device) on disk 1c.02.4 (S/N S0PCNEAB700934) while reading individual disk ownership area
Mon Jan 21 14:40:41 GMT [diskown.errorDuringIO:error]: error 23 (adapter error prevents command from being sent to device) on disk 1c.02.2 (S/N S0PCNEAB700961) while reading individual disk ownership area
Mon Jan 21 14:40:41 GMT [diskown.errorDuringIO:error]: error 23 (adapter error prevents command from being sent to device) on disk 1c.02.0 (S/N S0PCNEAB700964) while reading individual disk ownership area
Mon Jan 21 14:40:41 GMT [diskown.errorDuringIO:error]: error 23 (adapter error prevents command from being sent to device) on disk 1c.02.1 (S/N S0PCNEAB700937) while reading individual disk ownership area
Mon Jan 21 14:40:43 GMT [config.noPartnerDisks:CRITICAL]: No disks were detected for the partner; this node will be unable to takeover correctly
(1)  Normal boot.
(2)  Boot without /etc/rc.
(3)  Change password.
(4)  Assign ownership and initialize disks for root volume.
(4a) Same as option 4, but create a flexible root volume.
(5)  Maintenance mode boot.
Selection (1-5)? 4a
The system has 0 disks assigned whereas it needs 3 to boot, will try to assign the required number.
DBG: SANOWN: total number of disks assigned = 0Could assign only 0 out of the 3 disks required by the system to boot.
PANIC: This system has no disks, and thus no file system can be created on it in process rc on release NetApp Release 7.3.7 on Mon Jan 21 14:40:46 GMT 2013
version: NetApp Release 7.3.7: Thu May  3 03:48:45 PDT 2012
cc flags: 2O
DUMPCORE: START
DUMPCORE: END -- coredump *NOT* written.
halt after panic during system initialization
0 Kudos
View By:
Tags (1)
4 REPLIES 4

peter_lehmann
‎2013-01-21 07:42 AM
5,422 Views

Let's assume you have connected the shelfs correctly. When booting into the "special boot menu", select option 5 = Maintenance Mode.

Then check with the "disk" command if you see the disks physicaly and if yes, assign ownership with the the "disk assign" command. You might need to remove ownership first before being allowed to assign them.

From there on, reboot and then select option 4a again.

KCOKYAMAN
‎2013-01-22 12:05 AM
In response to peter_lehmann
5,422 Views

Thank you Peter,

I can see one of shelves disks and configure root volume with this. But other shelf disks are not shown in "disk" command. I 'm not sure about sas cabling. How can i check? Are there any documentation for "fas3240 single enc. non-ha". There no cabling information for "non-ha" in the "32XX HW Installation Overview - 210-05224+A0" document.

0 Kudos

peter_lehmann
‎2013-01-22 12:44 AM
In response to KCOKYAMAN
5,422 Views

Sure, this is your guide to all version of SAS cabling with NetApp Controllers:

https://library.netapp.com/ecm/ecm_get_file/ECMM1280392

Just look for "Universal SAS and ACP Cabling Guide"...

0 Kudos

KCOKYAMAN
‎2013-01-22 02:00 AM
In response to peter_lehmann
5,422 Views

I assigned 5 disks to controller and choose 4a in "special boot menu". Get messages below;

The system has 5 disks assigned whereas it needs 3 to boot, will try to assign the required number.
Zero disks and install a new file system? y
This will erase all the data on the disks, are you sure? y
Disk '0a.00.1' contains a higher RAID label version 11. Expecting version 9. This disk will not be initialized.
Disk '0a.00.2' contains a higher RAID label version 11. Expecting version 9. This disk will not be initialized.
Disk '0a.00.0' contains a higher RAID label version 11. Expecting version 9. This disk will not be initialized.
Disks with BAD version raid labels have been detected. These disks will not be usable on this version of Ontap. If you proceed with this and later upgrade the version of Ontap, the system may panic because of multiple root volumes. Are you sure you want to continue?y

system cannot boot ONTAP when process finish. i get an error messages below;

PANIC: raid: there are no data or parity disks in process rc on release NetApp Release 7.3.7 on Tue Jan 22 08:59:37 GMT 2013
version: NetApp Release 7.3.7: Thu May  3 03:48:45 PDT 2012
cc flags: 2O
DUMPCORE: START
DumpcoreFlag = 0x0
Dumping to disks: 0a.00.4
...............................................................................................................................
DUMPCORE: END -- coredump written.
halt after panic during system initialization

Can I upgrade data ontap to 8.1.2 in maintenance or loader mode?

0 Kudos
Announcements
All Community Forums
Public