ATA problems again ...

Johan Ström johan at stromnet.org
Mon Jul 17 09:59:22 UTC 2006


On 17 jul 2006, at 00.53, Mike Tancsa wrote:

> At 03:02 PM 14/07/2006, Miroslav Lachman wrote:
>
>
>> After reboot (command reboot), system boot up with both disks  
>> attached and start autosynchronization. I do not know, if this is  
>> hw or sw error, I got
>
> Install the smartmontools from
>
> /usr/ports/sysutils/smartmontools/
>
> and post the output of
> smartctl -a /dev/ad8

I tried this on my SATA disk ad6:
=== START OF INFORMATION SECTION ===
Model Family:     Maxtor MaXLine III family
Device Model:     Maxtor 7L300S0
Serial Number:    L60CJKPH
Firmware Version: BANC1G10
User Capacity:    300,090,728,448 bytes
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   7
ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 0
Local Time is:    Mon Jul 17 11:54:35 2006 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
....
SMART Error Log Version: 1
No Errors Logged

Any other output from smartctl that can help? Both my ad4 and ad6 are  
the same.

Now I had yet another crash.. They are very much more intense now the  
latest days... Two crashes ago I changed the SATA cable to ad4, i  
wonder if that had anything to do with it... On the other hand, now  
it was ad6 that got lost, so why would ad4's cable make any  
difference.. i'll change ad6 now too when i've taken the box down..

Jul 16 03:27:25 elfi kernel: ad6: FAILURE - device detached
Jul 16 03:27:25 elfi kernel: subdisk6: detached
Jul 16 03:27:25 elfi kernel: ad6: detached
Jul 16 03:27:25 elfi kernel: GEOM_MIRROR: Device gm0s1: provider  
ad6s1 disconnected.
Jul 16 03:27:25 elfi kernel: g_vfs_done():mirror/gm0s1f[READ 
(offset=27210082304, length=2048)]error = 6
Jul 16 03:27:25 elfi kernel: g_vfs_done():mirror/gm0s1f[READ 
(offset=35153985536, length=32768)]error = 6
Jul 16 03:27:25 elfi kernel: ufs_access(): Error retrieving ACL on  
object (6).
Jul 16 03:27:25 labdator kernel: nfs: server 192.168.1.2 not  
responding, still trying
Jul 16 03:27:25 labdator kernel: nfs: server 192.168.1.2 OK

Those last 3 messages seems to be very related to the gmirror going  
to degraded mode? Some ACL reading and a mounted NFS system  
(192.168.1.2 is the failing box).

Is there some way to enable more debug info output or something??

Johan



More information about the freebsd-stable mailing list