Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 26 Apr 2011 22:57:05 +0300
From:      George Kontostanos <gkontos.mail@gmail.com>
To:        Alexander Motin <mav@freebsd.org>
Cc:        FreeBSD Stable <freebsd-stable@freebsd.org>
Subject:   Re: Promise SATA controller issues...
Message-ID:  <BANLkTikZEQgQcRaKo9eeXYCV4=FK9FNjkA@mail.gmail.com>
In-Reply-To: <4DB71F80.8030901@FreeBSD.org>
References:  <mailpost.1303845053.5718357.47999.mailing.freebsd.stable@FreeBSD.cs.nctu.edu.tw> <4DB71C65.7070700@FreeBSD.org> <BANLkTimkvfQHNjtWOxHZcqD=bJuD1hsW8Q@mail.gmail.com> <4DB71F80.8030901@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
The system was up since April 21 when I upgraded to the latest world &&
kernel.
There are 2 pools, a mirror with root on ZFS for the OS and a Raidz1 just
for the data.

hp# zpool status
  pool: tank
 state: ONLINE
 scrub: scrub completed after 1h30m with 0 errors on Tue Apr 26 22:48:32
2011
config:

    NAME              STATE     READ WRITE CKSUM
    tank              ONLINE       0     0     0
      raidz1          ONLINE       0     0     0
        label/zdisk1  ONLINE       0     0     0
        label/zdisk2  ONLINE       0     0     0
        label/zdisk3  ONLINE       0     0     0

errors: No known data errors

  pool: zroot
 state: ONLINE
 scrub: none requested
config:

    NAME           STATE     READ WRITE CKSUM
    zroot          ONLINE       0     0     0
      mirror       ONLINE       0     0     0
        gpt/disk0  ONLINE       0     0     0
        gpt/disk1  ONLINE       0     0     0


The server is a SOHO fileserver with a few other services:

sshd_enable="YES"
named_enable="YES"   #Caching name server
samba_enable="YES"
dhcpd_enable="YES"
squid_enable="YES"
apcupsd_enable="YES"
apache22_enable="YES"
mysql_enable="YES"
syslogd_flags="-a 10.10.10.1"     #Cisco Pix logging
snmpd_enable="YES"
nagios_enable="YES"
munin_node_enable="YES"
bsdstats_enable="YES"
smartd_enable="YES"

There was nothing out of the ordinary before this except some repeated power
failures that where handled by the UPS as you can see in the logs:

Apr 24 20:33:53 hp apcupsd[870]: Power failure.
Apr 24 20:33:55 hp apcupsd[870]: Power is back. UPS running on mains.
Apr 24 20:38:03 hp apcupsd[870]: Power failure.
Apr 24 20:38:04 hp apcupsd[870]: Power is back. UPS running on mains.
Apr 24 21:45:47 hp apcupsd[870]: Power failure.
Apr 24 21:45:49 hp apcupsd[870]: Power is back. UPS running on mains.
Apr 24 22:43:56 hp apcupsd[870]: Power failure.
Apr 24 22:43:57 hp apcupsd[870]: Power is back. UPS running on mains.
Apr 24 23:05:46 hp apcupsd[870]: Power failure.
Apr 24 23:05:47 hp apcupsd[870]: Power is back. UPS running on mains.
Apr 25 00:20:32 hp apcupsd[870]: Power failure.
Apr 25 00:20:33 hp apcupsd[870]: Power is back. UPS running on mains.
Apr 25 01:23:22 hp apcupsd[870]: Power failure.
Apr 25 01:23:23 hp apcupsd[870]: Power is back. UPS running on mains.
Apr 25 06:26:40 hp apcupsd[870]: Power failure.
Apr 25 06:26:42 hp apcupsd[870]: Power is back. UPS running on mains.
Apr 25 11:05:03 hp apcupsd[870]: Power failure.
Apr 25 11:05:04 hp apcupsd[870]: Power is back. UPS running on mains.
Apr 25 13:05:20 hp apcupsd[870]: Power failure.
Apr 25 13:05:21 hp apcupsd[870]: Power is back. UPS running on mains.
Apr 25 13:32:48 hp apcupsd[870]: Power failure.
Apr 25 13:32:50 hp apcupsd[870]: Power is back. UPS running on mains.
Apr 25 13:35:06 hp apcupsd[870]: Power failure.
Apr 25 22:08:35 hp kernel: ata4: SIGNATURE: ffffffff
Apr 25 22:08:35 hp kernel: ata4: timeout waiting to issue command
Apr 25 22:08:35 hp kernel: ata4: error issuing SETFEATURES SET TRANSFER MODE
command
.........


On Tue, Apr 26, 2011 at 10:39 PM, Alexander Motin <mav@freebsd.org> wrote:

> George Kontostanos wrote:
> > Please let me know what kind of information might be also useful.
>
> I don't know. What were the first messages before the problem? Was there
> any specific activity? It would be most useful if you could reproduce
> the problem in controllable environment.
>
> >     There was no changes specific to the Promise controllers for a long
> >     time. Mostly because I have no any documentation for them. For the
> same
> >     reason I hardly can say what could be wrong there. Some additional
> >     information is definitely required.
>
> --
> Alexander Motin
>



-- 
George Kontostanos
aisecure.net <http://www.aisecure.net>;



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTikZEQgQcRaKo9eeXYCV4=FK9FNjkA>