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.
On 8/21/2014 12:43 PM, 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.assuming thats a hp smartarray raid controller, use hpacucli to diagnose the raid problem. degraded raid6 is /really/ slow. -- john r pierce 37N 122W somewhere on the middle of the left coast
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
On Thu, Aug 21, 2014 at 3:43 PM, Matt <matt.mailinglists at gmail.com> 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. >run: tune2fs -l /dev/mapper/<whatever_the_disk_is_called> check: Maximum mount count Next check after if those are NOT -1 and 0 respectively change settings by running: tune2fs -i 0 -c 0 /dev/mapper/<whatever_the_disk_is_called>