A1000 RAID Array errors

[caveshepherd]

I keep getting this error on my A1000 on a SunE3500 on boot up or when I start my Ingres databse, which coincidentally is on the said A1000. Can someone shed some light on this error. I have 2 opinions thus far .. Sun claims it's a filesystem overlap and my Ingres administrator clims it's a bad disk in the RAID...

Jul29 04:00:01 orix unix! WARNING. The Array driver is returning an Errored I/O with errno 5, on module 1, Lun 0, Sector 4194300
Jul29 04:00:01 orix unix! WARNING. The Array driver is returning an Errored I/O with errno 5, on module 1, Lun 0, Sector 3145724
Jul29 04:00:01 orix unix! WARNING. The Array driver is returning an Errored I/O with errno 5, on module 1, Lun 0, Sector 2883580
Jul29 04:00:01 orix unix! WARNING. The Array driver is returning an Errored I/O with errno 5, on module 1, Lun 0, Sector 2818044

Thanks a mil. !!

 

[Guest_imported]

I was recieving this same error, in fact it flooded the /var/asm/messages file . My error had to do with my cache batteries going bad. If you run "healthck -a " maybe it will shed some light on your problem.

Cheers.

 

[Apricot]

To avoid the problem described in this SunAlert you should not set the "maxcontig" file system parameter to values greater than 128 for SCSI devices or greater than 16 for IDE devices.

If the "fstyp -v" output indicates that the "maxcontig" file system parameter is set to a value greater than 128 (for SCSI devices) or 16 (for IDE devices) it should be reduced to 128 (for SCSI devices) or 16 (for IDE devices) or below using the "tunefs -a" command (the default value is 16). You need to execute the "tunefs" command as root user. A reboot is not required.

Example: to set the "maxcontig" parameter for the file system on the c0t0d0s0 slice to "16" use:

# tunefs -a 16 /dev/dsk/c0t0d0s0
maximum contiguous block count changes from 256 to 16
The "maxcontig" parameter value set by the "tunefs -a" command will remain across reboots.

regards ph