I have upgraded my FreeBSD-5.3-p37 based machine to FreeBSD-6.1-p10 last Thursday. The machine is a PIV 3,2 Ghz with 2 Gig RAM with a Promise PDC20371 SATA150 controller, on which two disks (both are Seagate ST3200822AS 3.01) are attached and configured as RAID-1 (from dmesg):

ar0: 190782MB <Promise Fasttrak RAID1> status: READY
ar0: disk0 READY (master) using ad6 at ata3-master
ar0: disk1 READY (mirror) using ad4 at ata2-master

# atacontrol status ar0
ar0: ATA RAID1 subdisks: ad6 ad4 status: READY

This machine gets backed up by another machine using amanda and gtar. Both gtar and amanda are the latest from the ports tree as of Saturday last week both on the backup server as on the client (the machine I'm talking about).

The problem: The machine hangs when the backup runs. The machine is in a datacenter and has a serial console attached. Thanks to a remote access card I was able to reboot the machine and put it into single user in order to fsck -f -y the single disks (i.e. ad4s1x and ad6s1x, where x are the appropriate slice names). I then started the backup again and all went well. Unfortunately this scenario happened twice (Saturday morning and today morning).

I have checked the two disk with smartctl, no errors are logged. syslogd mentioned nothing in the logs too. The machine has run for 1,5 years with FreeBSD-5.3-RELEASE-pxx. I guess something must have changed in the ata driver or the controller goes its way to hell anyway.

Is this a known problem with this controller on FreeBSD-6.1? How can I provide more information (shall I compile in DDB, KDB, KDB_UNATTENDED)?


PS: I hope this is the right mailing list for this question. Else: please advise the proper one :)
freebsd-questions@freebsd.org mailing list
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to