Subscribe

stuck @ LOADER prompt

FAS2240-4 

 

Started repurposing the FAS(from 7-mode to CDOT)

 

started with 8.1.2RC1 7-mode upgraded to 8.1.4P1 CDOT  (will then upgrade from 8.1.x to 8.2)

controller A is currently zeroing disks  

 

controller B boots to LOADER-B prompt and doesn't respond to keyboard.

 

Boot Loader version 4.1

Copyright (C) 2000-2003 Broadcom Corporation.

Portions Copyright (C) 2002-2011 NetApp

 

CPU Type: Intel(R) Xeon(R) CPU           C3528  @ 1.73GHz

 

The boot media contains a newer firmware image (8.2.0).

 

Warning: Automatic firmware update will start in 5 seconds.

To abort, press Ctrl-C during this period.

 

!!!DO NOT POWER OFF SYSTEM!!!

Firmware is being updated.

 

There appears to be valid data in the NVRAM.  You must boot Data ONTAP in order to flush the NVRAM to disk, and then cleanly shutdown the filer with the halt command.

Automatic firmware update skipped (update_flash command failed).

 

Warning: The boot media contains a newer firmware image (8.2.0).

Please run 'update_flash' at the Loader prompt to update your

system firmware (8.1.0).

 

LOADER-B>

 

Obviously cannot use boot_ontap as it wont record any keypresses. 

 

suggestions?

 

Re: stuck @ LOADER prompt

I did manage it to get it booting it appears as though its trying to update its firmware but its patner node isnt available (upgraded to CDOT)

but it still doesnt respond to keypresses.

 

I cannot reboot and control-C to the LOADER prompt or that will net me the issue in my original post. 

 

Tue Oct 27 19:31:59 GMT [FAS2240b:export.host.resolve.timeout:warning]: Trial 3 for the nameservice lookup request timed out.
Tue Oct 27 19:32:00 GMT [FAS2240b:monitor.globalStatus.critical:CRITICAL]: Controller failover partner unknown. Controller failover not possible.
Tue Oct 27 19:32:02 GMT [FAS2240b:export.host.resolve.timeout:warning]: Trial 1 for the nameservice lookup request timed out.
Tue Oct 27 14:32:06 CDT [FAS2240b:export.host.resolve.timeout:warning]: Trial 2 for the nameservice lookup request timed out.
Tue Oct 27 14:32:09 CDT [FAS2240b:export.host.resolve.timeout:warning]: Trial 3 for the nameservice lookup request timed out.
Tue Oct 27 14:32:10 CDT [FAS2240b:sfu.partnerNotResponding:error]: Partner either responded in the negative, or did not respond in 60 seconds. Aborting shelf firmware update.
Tue Oct 27 14:32:13 CDT [FAS2240b:export.host.resolve.timeout:warning]: Trial 1 for the nameservice lookup request timed out.
Tue Oct 27 14:32:16 CDT [FAS2240b:export.host.resolve.timeout:warning]: Trial 2 for the nameservice lookup request timed out.
Tue Oct 27 14:32:20 CDT [FAS2240b:export.host.resolve.timeout:warning]: Trial 3 for the nameservice lookup request timed out.
Tue Oct 27 14:32:23 CDT [FAS2240b:export.host.resolve.timeout:warning]: Trial 1 for the nameservice lookup request timed out.
Tue Oct 27 14:32:27 CDT [FAS2240b:export.host.resolve.timeout:warning]: Trial 2 for the nameservice lookup request timed out.
Tue Oct 27 14:32:27 CDT [FAS2240b:callhome.performance.snap:info]: Call home for PERFORMANCE SNAPSHOT
Tue Oct 27 14:32:30 CDT [FAS2240b:export.host.resolve.timeout:warning]: Trial 3 for the nameservice lookup request timed out.
Tue Oct 27 14:32:34 CDT [FAS2240b:export.host.resolve.timeout:warning]: Trial 1 for the nameservice lookup request timed out.
Tue Oct 27 14:32:37 CDT [FAS2240b:ses.status.ACPInfo:info]: DS4246 (S/N SHJMS0000000B01) shelf 1 on channel 0a ACP Processor information for SAS shelf ACP processor 2: normal status.
Tue Oct 27 14:32:37 CDT [FAS2240b:export.host.resolve.timeout:warning]: Trial 2 for the nameservice lookup request timed out.
Tue Oct 27 14:32:41 CDT [FAS2240b:export.host.resolve.timeout:warning]: Trial 3 for the nameservice lookup request timed out.
Tue Oct 27 14:32:44 CDT [FAS2240b:export.host.resolve.timeout:warning]: Trial 1 for the nameservice lookup request timed out.

Re: stuck @ LOADER prompt

 

I'm a dork.. I forgot I could use the service processor.  keyboard works just fine in the SP.