topic Re: PANIC: sanown: received add for already known disk in process in ONTAP Hardware

PANIC: sanown: received add for already known disk in process

gabrie — Thu, 05 Jun 2025 07:05:08 GMT

I recently got an old NetApp Fas3050 for my homelab and to learn about NetApps. I received two heads and two disk shelves. When I received it, it took me quite some time to figure out the wiring of the cabling between heads and shelves. I finally got it working and created a LUN on it. But for some DR / replication testing I decided I want to make two separate NetApps of it. So I used this instruction to create a single cabled unit: http://www.flickr.com/photos/60938528@N00/5184699197/

Unfortunately now the unit won't boot anymore. I receive the errors below. Is this because the unit misses the old config and can I simply reset it (how?). Or is the cabling for the single unit cabling still wrong?

Regards

Gabrie

Error below:

CPU type 0xF29: 2800MHz

Total memory: 0xC0000000 bytes (3072MB)

Starting AUTOBOOT press any key to abort...

Loading: 0x200000/42260372 0x2a4d794/14350620 0x37fd0b0/1732666 0x39a40ea/6 Entry at 0x00200000

Starting program at 0x00200000

Press CTRL-C for special boot menu

Thu Nov 11 20:56:23 GMT [nvram.battery.state:info]: The NVRAM battery is currently ON.

Thu Nov 11 20:56:56 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 0d.

NetApp Release 7.3.3RC1: Wed Jan 6 23:50:42 PST 2010

Starting boot on Thu Nov 11 20:56:18 GMT 2010

Thu Nov 11 20:56:56 GMT [fci.initialization.failed:error]: Initialization failed on Fibre Channel adapter 0b.

PANIC: sanown: received add for already known disk in process sanown_notify on release NetApp Release 7.3.3RC1 on Thu Nov 11 20:57:01 GMT 2010

version: NetApp Release 7.3.3RC1: Wed Jan 6 23:50:42 PST 2010

cc flags: 8O

DUMPCORE: START

DUMPCORE: END -- coredump *NOT* written.

halt after panic during system initialization

CFE version 3.1.0 based on Broadcom CFE: 1.0.40

CPU type 0xF29: 2800MHz

Total memory: 0xC0000000 bytes (3072MB)

Re: PANIC: sanown: received add for already known disk in process

ekashpureff — Thu, 18 Nov 2010 00:06:02 GMT

Looks like a disk ownership issue.

Did you get the right disks/shelves separated ?

Boot and hit ctrl-C when it says to get the boot menu.

At the boot menu (options 1-5) enter in '22/7' for the Secret boot menu.

You'll get to explore the maint mode boot menu, including things like unassigning and reassigning your disks.

Enjoy.

I hope this response has been helpful to you.

At your service,

Eugene E. Kashpureff
ekashp@kashpureff.org
Fastlane NetApp Instructor and Independent Consultant
http://www.fastlaneus.com/ http://www.linkedin.com/in/eugenekashpureff

(P.S. I appreciate points for helpful or correct answers.)

Re: PANIC: sanown: received add for already known disk in process

palbers — Thu, 18 Nov 2010 16:42:46 GMT

Gabrie,

You may also want to check the value of the pre boot environment

variable:

fc-non-array-adapter-list

The contents of the variable might look like the following

4a,4b,0a,0c

Try adding that second connection you cabled up to the list and see if

that helps. This is

usually involved with adding new first disk shelves on new loops on a

V-Series system,

but may be at play in your configuration.

Best Regards,

-paul

Re: PANIC: sanown: received add for already known disk in process

fschub — Mon, 04 Mar 2013 11:16:32 GMT

thanks for your post, it helped me. Had the same problem and wrong adapters in my list, and especially got the problem because there where adapters on this list connected to SAN storage.

regards - Frank