Thanks! I got some progress with that. I was able to priv set advanced and 'disk unfail' while the system was up. I should have searched NOW.
Webster, Stetson wrote:
http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=185042 http://now.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=185042
*Stetson M. Webster** *Professional Services Engineer - NCDA, NCIE-SAN NetApp Global Services - Southeast District
919.250.0052 Mobile Stetson.Webster@netapp.com mailto:Stetson.Webster@netapp.com
netapp.com/accelerate http://www.netapp.com/us/company/events/accelerate/?ref_source=eSig
http://media.netapp.com/images/accelerate-sig2.jpg http://www.netapp.com/us/company/events/accelerate/?ref_source=eSig
-----Original Message----- From: Adam McDougall [mailto:mcdouga9@egr.msu.edu] Sent: Tuesday, September 23, 2008 12:28 PM To: toasters@mathworks.com Subject: How to re-fail a disk to trigger autosupport?
We had a disk fail in a shelf on a filer with expired support, which
created a case at the time but it was closed without replacement due to
lack of support on the filer. However, as part of the support agreement
on a new cluster, it was in a shelf that would be covered when attached
to one of the new filers. Now that we have that shelf attached to the
new filer, all I get is:
Mon Sep 22 17:18:22 EDT [hostname: disk.init.failureBytes:error]: Disk
0b.23 failed due to failure byte setting. I tried replugging the disk
and all I got was the same message in the log. After the message in the
log, the filer acts like the disk isn't present as per commands below.
How can I trick it intro triggering an autosupport so my bad disk gets
replaced? Thanks.
disk fail 0b.23
disk fail: Disk 0b.23 not found
disk show 0b.23
DISK OWNER POOL SERIAL NUMBER