> Hate to change the conversation here but that's why I hate hardware RAID. > If it was software RAID, Linux would always tell you what's going on. > Besides, Linux knows much more about what is going on on the disk and what is about to happen (like a megabyte DMA transfer). > > BTW, check if something is creating: > > /forcefsck These exist: -rw-r--r-- 1 root root 0 Jul 7 10:03 .autofsck -rw-r--r-- 1 root root 0 Jul 7 10:03 .autorelabel What does that mean? > That would make the fsck run every time. > > GKH > >> Matt wrote: >>> I have CentOS 6.x installed on a "HP ProLiant DL380 G5" server. It >>> has eight 750GB drives in a hardware RAID6 array. Its acting as a >>> host for a number of OpenVZ containers. >>> >>> Seems like every time I reboot this server which is not very often it >>> sits for hours running a disk check or something on boot. The server >>> is located 200+ miles away so its not very convenient to look at. Is >>> there anyway to tell if it plans to run this or tell it not too? >>> >>> Right now its reporting one of the drives in array is bad and last >>> time it did this a reboot resolved it. >> >> You need to know what it's running. If it's doing an fsck, that will take >> a lot of time. If it's firmware in the RAID controller, that's different. >> You can run tune2fs /dev/whatever and see how often it wants to run fsck. >> For that matter, what's the entry in /etc/fstab? >> >> mark >> >> _______________________________________________ >> CentOS mailing list >> CentOS at centos.org >> http://lists.centos.org/mailman/listinfo/centos >> > > > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos