Sorry I left two pieces of information out. The error existed in Ontap
5.3.4r2 and still occurs after upgrading to Ontap 5.3.6r2. I regret not
replacing the LRC the last down when I replaced the FCAL components.
Max.
-----Original Message-----
From: Knight, Jason [mailto:Jason.Knight@citadelgroup.com]
Sent: Monday, February 12, 2001 6:29 AM
To: 'Levent Kaptanoglu'; Knight, Jason
Cc: toasters(a)mathworks.com
Subject: RE: Recovered Error
Levent,
It is normal (or at least not unusual) to see disk errors during a RAID
SCRUB, RAID SCRUB is looking for bad media. If you start seeing these
errors occur several times a day and on the same disk when the system is not
performing a RAID SCRUB then you might consider failing the disk at a
convenient time and RMA'ing it if you have enough spares, but you should
talk with NetApp support first.
Jason Knight
-----Original Message-----
From: Levent Kaptanoglu [mailto:lkaptan@pro-link.net]
Sent: Monday, February 12, 2001 7:35 AM
To: Knight, Jason
Cc: toasters(a)mathworks.com
Subject: RE: Recovered Error
I have the same error
Could you find any solution ?
===== MESSAGES =====
Sun Feb 11 00:00:04 EET [asup_main]: System Notification mail sent
Sun Feb 11 01:00:00 EET [statd]: 1:00am up 17 days, 16:39 1421477327 NFS
ops, 6827 CIFS ops, 133 HTTP ops
Sun Feb 11 01:00:00 EET [raid_scrub_admin]: Beginning disk scrubbing...
Sun Feb 11 01:23:28 EET [CIFSAuthen]: CIFS - machine password changed on DC
\\MYNETDC1
Sun Feb 11 02:00:00 EET [statd]: 2:00am up 17 days, 17:39 1423199759 NFS
ops, 6829 CIFS ops, 133 HTTP ops
Sun Feb 11 03:00:00 EET [statd]: 3:00am up 17 days, 18:39 1424335238 NFS
ops, 6829 CIFS ops, 133 HTTP ops
Sun Feb 11 03:05:12 EET [isp2100_main]: Disk 1.2(0xfffffc0000caa4c8): op
0x28:016cf560:0080 sector 23917993 recovered error - (1 17, 1)
Sun Feb 11 04:00:00 EET [statd]: 4:00am up 17 days, 19:39 1424889672 NFS
ops, 6829 CIFS ops, 133 HTTP ops
Sun Feb 11 05:00:00 EET [statd]: 5:00am up 17 days, 20:38 1425181655 NFS
ops, 6829 CIFS ops, 133 HTTP ops
Sun Feb 11 05:45:45 EET [consumer]: Scrub found 0 parity inconsistencies
Sun Feb 11 05:45:45 EET [consumer]: Scrub found 0 media errors
Sun Feb 11 05:45:45 EET [consumer]: Disk scrubbing finished...
-----Original Message-----
From: owner-toasters(a)mathworks.com
[mailto:owner-toasters@mathworks.com]On Behalf Of Knight, Jason
Sent: 10 Þubat 2001 Cumartesi 18:27
To: 'Eff Norwood'; Maximus Moua; toasters(a)mathworks.com
Subject: RE: Recovered Error
Have you replaced the LRC? An LRC going bad can show up as disk errors.
Jason Knight
-----Original Message-----
From: Eff Norwood [mailto:eff@cynaptic.com]
Sent: Friday, February 09, 2001 8:15 PM
To: Maximus Moua; toasters(a)mathworks.com
Subject: Re: Recovered Error
What release of ONTAP are you running?
Effrem Norwood
----- Original Message -----
From: "Maximus Moua" <maximus(a)saba.com>
To: <toasters(a)mathworks.com>
Sent: Friday, February 09, 2001 10:14 AM
Subject: Recovered Error
> Hi All,
>
> I recently acquired a filer F720 with 36 G shelf which exibited a sector
> error in the Message log. I have tried swapping drives, replacing FCAL
> controller, cable and terminator. The problem occurs on all the data
> drives, except the spare, during heavy disk activity such as disk
scrubbing
> but less frequently and randomly even when disk activity should be
minimal.
> NetApp tells me this is a soft error and does not warrant concern but I
> wonder if any of you have experience this and can assure me to leave this
> one alone.
>
> Thanks,
>
> -Max
>
> Wed Feb 7 19:26:45 PST [raid_disk_admin]: Spare disk 1.4 (S/N
> 680A845B1K) has been added to the system.
> Wed Feb 7 19:33:46 PST [isp2100_main]: Disk 1.1(0xfffffc0000cbbcb8): op
> 0x28:00529380:0080 sector 5411723 recovered error - (1 17, 3)
> Wed Feb 7 19:41:51 PST [isp2100_main]: Disk 1.1(0xfffffc0000cbb978): op
> 0x28:00a79900:0080 sector 10983747 recovered error - (1 17, 1)
> Wed Feb 7 20:00:00 PST [statd]: 8:00pm up 12 days, 29 mins, 3 NFS ops,
> 48398305 CIFS ops, 810 HTTP ops
> Wed Feb 7 20:16:35 PST [isp2100_main]: Disk 1.0(0xfffffc0000cade18): op
> 0x28:020c22c0:0080 sector 34349865 recovered error - (1 17, 3)
> Wed Feb 7 20:17:56 PST [isp2100_main]: Disk 1.5(0xfffffc0000cc1e38): op
> 0x28:021a93c0:0080 sector 35296301 recovered error - (1 17, 1)
> Wed Feb 7 20:18:52 PST [isp2100_main]: Disk 1.1(0xfffffc0000cc7ad8): op
> 0x28:02249240:0080 sector 35951273 recovered error - (1 17, 1)
> Wed Feb 7 20:20:51 PST [isp2100_main]: Disk 1.5(0xfffffc0000cd6cf8): op
> 0x28:0239ed40:0080 sector 37350752 recovered error - (1 17, 1)
> Wed Feb 7 20:25:13 PST [isp2100_main]: Disk 1.0(0xfffffc0000ca6298): op
> 0x28:02692bc0:0080 sector 40447008 recovered error - (1 16, 0)
> Wed Feb 7 20:44:04 PST [isp2100_main]: Disk 1.1(0xfffffc0000cb8718): op
> 0x28:033932c0:0080 sector 54080224 recovered error - (1 17, 7)
> Wed Feb 7 20:49:34 PST [isp2100_main]: Disk 1.1(0xfffffc0000cb3df8): op
> 0x28:0378e938:0080 sector 58255736 recovered error - (1 17, 1)
> Wed Feb 7 21:00:00 PST [statd]: 9:00pm up 12 days, 1:29 3 NFS ops,
> 48418877 CIFS ops, 810 HTTP ops
> Wed Feb 7 21:03:25 PST [isp2100_main]: Disk 1.1(0xfffffc0000ca99d8): op
> 0x28:041f4af0:0080 sector 69159705 recovered error - (1 17, 3)
> Wed Feb 7 21:04:13 PST [isp2100_main]: Disk 1.1(0xfffffc0000ca5c18): op
> 0x28:04289df0:0080 sector 69770779 recovered error - (1 17, 7)
> Wed Feb 7 21:32:53 PST [consumer]: Reconstruction of data disk in volume
> vol0, RAID group 0, complete.
>