Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
get_disk_attributes: Stop reason: CR_OBJ_NOT_FOUND on Controller's console screen
2012-05-29
08:42 AM
17,751 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Has anyone ran across this message before? I'm seeing this message hundreds of times on a controller. I've done some searching but have not run across any articles. I've checked and there is no message on the console before these messages begin. I'm running DOT 8.0.1P4 on a fas3270.
24 REPLIES 24
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Got the same message today. We are running the OnTap Version 8.0.2P6 7-mode on a FAS6040 HA pair.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm seeing this message too. DOT 8.0.1 7-mode on FAS2040 pair
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That pops up in the console screen when I am in System Manager 2.0.1 at the same time and SM makes a call to the filer. It looks like the error appears once for every disk in the system. I DO NOT see the error when using SM 2.0
FAS3140 DOT 8.0.2P3 7-Mode HA Pair with SAS and SATA drives.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am investigating this and am looking for a bug report or KB article that can offer more information on your issue.
Thanks,
Christine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Christin,
Any luck finding out what is throwing this on the system console... I just noticed it today, and was trying to investigate.
Happens on one of the clustered pair of a FAS3270 - NetApp Release 8.0.2P4 7-Mode - console
get_disk_attributes: Stop reason: CR_OBJ_NOT_FOUND
get_disk_attributes: Stop reason: CR_OBJ_NOT_FOUND
get_disk_attributes: Stop reason: CR_OBJ_NOT_FOUND
get_disk_attributes: Stop reason: CR_OBJ_NOT_FOUND
get_disk_attributes: Stop reason: CR_OBJ_NOT_FOUND
Thanks,
-Brian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We are currently reviewing the documentation and I will post a link shortly.
Christine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Same messages here. Running 8.0.2P3 7-Mode on V3240. OnCommand SM is 2.0.
Best wishes,
Pedro Rocha.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Seeing the same here as well, no news?
get_disk_attributes: Stop reason: CR_OBJ_NOT_FOUND
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am also getting the same messages on the console when I login to OnCommand System Manager 2.0.1 and try to access the storage on the left hand side menu. Any update on this as to why it is happening. I am getting this on FAS3170 and V3170 with DOT 8.0.2P1 7-mode.
get_disk_attributes: Stop reason: CR_OBJ_NOT_FOUND
Thanks
Pankaj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So far the only suggested solition is to upgrade to the later versions of Ontap..
Netapp makes it sound like a simple solution, that we all are going to implement. Yea right[:-\]
They kept referring me to a document that was internal only with no public information and the netapp community..
That was until i pointed out that i was poster 5
I believe there is a bigger problem than they want us to know
Good luck
Brian R. Tusler
Martin Marietta Materials Inc.
2710 Wycliff Rd
<geo:0,0?q=2710WycliffRd%0ARaleigh%2CNC.27607>Raleigh, NC. 27607<geo:0,0?q=2710WycliffRd%0ARaleigh%2CNC.27607>
919-882-2225<tel:9198822225> work
919-427-5828<tel:9194275828> cel
Sent from a Martin Marietta Materials mobile device
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
tuslerbz1 wrote:
So far the only suggested solition is to upgrade to the later versions of Ontap..
Netapp makes it sound like a simple solution, that we all are going to implement. Yea right[:-\]
Yeah, not so easy for those of us who can't upgrade to 8.1!
Nice to finally get some information though, thanks Christine.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Netapp is referring me to this Bug report, and the Netapp Community
http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=426418
Bug ID
426418
Title
Bug information not available
Fixed-In Version
· Data ONTAP 8.1RC1<http://support.netapp.com/download/software/ontap/8.1RC1/> (First Fixed) - Fixed
· Data ONTAP 8.1<http://support.netapp.com/download/software/ontap/8.1/> (GA<http://support.netapp.com/download/defs/ontap.shtml>) - Fixed
· Data ONTAP 8.1.1RC1<http://support.netapp.com/download/software/ontap/8.1.1RC1/> (RC<http://support.netapp.com/download/defs/ontap.shtml>) - Fixed
Requested, reason, impact, workaround,fix!
Otherwise you are out of luck…
Guess we will just have to deal with it…
Any thoughts on that
Thx
-Brian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would love to know about this as well. Whenever they post the ultra-shady bug's where no information is listed, we find a lot of trouble. This is not how a responsible support organization should run.
Another great example of this was when the MOOS drives were failing right and left for tons of customers and they just wanted to keep the whole thing under wrap.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I just wanted to provide an update on this thread. Here is the information I received from our Engineering team:
The message 'get_disk_attributes: Stop reason: CR_OBJ_NOT_FOUND' is a console message generated on Data ONTAP 8.0.x systems configured in HA pairs. It is generated when one node of an HA pair attempts to perform certain operations on disks owned by the partner node. These operations may be initiated by management applications like the System Manager. This message does not indicate an error condition, and can safely be ignored on systems running Data ONTAP 8.0.x.
The public report should be available soon. Thank you all for patience on this issue.
Christine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I also ran into this today. Working with NetApp we found that this is a "new" BURT 426418 (new only because the website has no information listed about it). According to NetApp, they can be safely ignored, and the issue was resolved in 8.1. Hopefully this helps others out!
Brandon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Will OnCommnad System Manager contain any fix for this?!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Looks like this is fixed in version 2.0.2 of System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
i won't confirm that it is fixed in Version 2.0.2. We have System Manager 2.0.2, and a Metrocluster with 8.0.2P4 and the Message appeared right in my console.
We have planned to Upgrade to Ontap 8.1.1P1 on next Monday, maybe that will solve the Problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Yes I have seen this in the console also on 2.0.2 since posting this. Oh well!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Seems to be System Manager related for us as it only started when we upgraded to System Manager 2.0.1 a few months ago. Why an upgrade to 8.1 when System Manager triggers it?