[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] SATA HDD Problem


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: Markus Hardiyanto <informatics2k1@xxxxxxxxx>
  • Date: Sun, 15 Jul 2007 23:44:06 -0700 (PDT)
  • Delivery-date: Sun, 15 Jul 2007 23:42:01 -0700
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type:Message-ID; b=6hAjb8rVWgleJVNSeOOMpVLW7CK/Fw5QKfpVRVujT16tMuc9Gbn0/4rrfAQUfHR+j6n1RlBbG3YYdhIf2LLodUgM5V0nblVS3yuUlQKE6s2GbkPnwEhYP57HpnLddXhynj+mx3GwoDchz3Nn3hDnanOD8HS9ex+l7NQt4ZQEyEw=;
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello,

i installed xen with 2.6.18 kernel and having problem with sata HDD on my 
server.. here is the error message from /var/log/messages:

Jul 14 06:46:39 cl-44 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 
0x0 action 0x0

Jul 14 06:46:39 cl-44 kernel: ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 
0x51 err 0x4 (device error)

Jul 14 06:46:39 cl-44 kernel: ata1: EH complete

Jul 14 06:46:39 cl-44 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 
0x0 action 0x0

Jul 14 06:46:39 cl-44 kernel: ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 
0x51 err 0x4 (device error)

Jul 14 06:46:39 cl-44 kernel: ata1: EH complete

Jul 14 06:46:39 cl-44 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 
0x0 action 0x0

Jul 14 06:46:39 cl-44 kernel: ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 
0x51 err 0x4 (device error)

Jul 14 06:46:39 cl-44 kernel: ata1: EH complete

Jul 14 06:46:39 cl-44 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 
0x0 action 0x0

Jul 14 06:46:39 cl-44 kernel: ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 
0x51 err 0x4 (device error)

Jul 14 06:46:39 cl-44 kernel: ata1: EH complete

Jul 14 06:46:39 cl-44 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 
0x0 action 0x0

Jul 14 06:46:39 cl-44 kernel: ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 
0x51 err 0x4 (device error)

Jul 14 06:46:39 cl-44 kernel: ata1: EH complete

Jul 14 06:46:39 cl-44 kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 
0x0 action 0x0

Jul 14 06:46:39 cl-44 kernel: ata1.00: tag 0 cmd 0xb0 Emask 0x1 stat 
0x51 err 0x4 (device error)

Jul 14 06:46:39 cl-44 kernel: ata1: EH complete





Jul 14 06:50:13 cl-44 kernel: hda: status error: status=0x20 { DeviceFault }

Jul 14 06:50:13 cl-44 kernel: ide: failed opcode was: unknown

Jul 14 06:50:13 cl-44 kernel: hda: ATAPI reset complete

Jul 14 06:50:13 cl-44 kernel: hda: status error: status=0x20 { DeviceFault }

Jul 14 06:50:13 cl-44 kernel: ide: failed opcode was: unknown

Jul 14 06:50:13 cl-44 kernel: hda: ATAPI reset complete

Jul 14 06:50:13 cl-44 kernel: hda: status error: status=0x20 { DeviceFault }

Jul 14 06:50:13 cl-44 kernel: ide: failed opcode was: unknown

Jul 14 06:50:13 cl-44 kernel: hda: status error: status=0x20 { DeviceFault }

Jul 14 06:50:13 cl-44 kernel: ide: failed opcode was: unknown

Jul 14 06:50:13 cl-44 kernel: hda: ATAPI reset complete

Jul 14 06:50:13 cl-44 kernel: hda: status error: status=0x20 { DeviceFault }

Jul 14 06:50:13 cl-44 kernel: ide: failed opcode was: unknown

Jul 14 06:50:13 cl-44 kernel: hda: ATAPI reset complete

Jul 14 06:50:13 cl-44 kernel: hda: status error: status=0x20 { DeviceFault }

Jul 14 06:50:13 cl-44 kernel: ide: failed opcode was: unknown

Jul 14 06:50:13 cl-44 kernel: hda: status error: status=0x20 { DeviceFault }

Jul 14 06:50:13 cl-44 kernel: ide: failed opcode was: unknown

Jul 14 06:50:13 cl-44 kernel: hda: ATAPI reset complete

Jul 14 06:50:13 cl-44 kernel: hda: status error: status=0x20 { DeviceFault }

Jul 14 06:50:13 cl-44 kernel: ide: failed opcode was: unknown

Jul 14 06:50:13 cl-44 kernel: hda: ATAPI reset complete

Jul 14 06:50:13 cl-44 kernel: hda: status error: status=0x20 { DeviceFault }

Jul 14 06:50:13 cl-44 kernel: ide: failed opcode was: unknown

Jul 14 06:50:13 cl-44 kernel: hda: status error: status=0x20 { DeviceFault }

Jul 14 06:50:13 cl-44 kernel: ide: failed opcode was: unknown



Jul 14 06:55:38 cl-44 smartd[2673]: smartd version 5.36 
[x86_64-redhat-linux-gnu] Copyright (C) 2002-6 Bruce Allen

Jul 14 06:55:38 cl-44 smartd[2673]: Home page is 
http://smartmontools.sourceforge.net/

Jul 14 06:55:38 cl-44 smartd[2673]: Opened configuration file 
/etc/smartd.conf

Jul 14 06:55:38 cl-44 smartd[2673]: Configuration file /etc/smartd.conf 
parsed.

Jul 14 06:55:38 cl-44 smartd[2673]: Device: /dev/sda, opened

Jul 14 06:55:38 cl-44 smartd[2673]: Device: /dev/sda, not found in 
smartd database.

Jul 14 06:55:39 cl-44 smartd[2673]: Device: /dev/sda, is SMART capable. 
Adding to "monitor" list.

Jul 14 06:55:39 cl-44 smartd[2673]: Monitoring 1 ATA and 0 SCSI devices

Jul 14 06:55:39 cl-44 smartd[2673]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 06:55:39 cl-44 smartd[2673]: Sending warning via mail to root ...

Jul 14 06:55:39 cl-44 smartd[2673]: Warning via mail to root: successful

Jul 14 06:55:39 cl-44 smartd[2673]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 06:55:39 cl-44 smartd[2673]: Sending warning via mail to root ...

Jul 14 06:55:39 cl-44 smartd[2673]: Warning via mail to root: successful

Jul 14 06:55:39 cl-44 smartd[2687]: smartd has fork()ed into background 
mode. New PID=2687.

Jul 14 07:25:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 07:25:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 07:55:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 07:55:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 08:04:49 cl-44 init: Trying to re-exec init

Jul 14 08:25:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 08:25:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 08:55:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 08:55:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 09:25:40 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 09:25:40 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 09:55:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 09:55:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 10:25:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 10:25:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 10:55:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 10:55:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 11:25:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 11:25:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 11:55:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 11:55:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 12:25:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 12:25:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 12:55:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 12:55:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 13:25:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 13:25:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 13:55:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 13:55:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 14:25:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 14:25:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 14:55:40 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 14:55:40 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 15:25:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 15:25:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 15:55:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 15:55:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 16:25:39 cl-44 smartd[2687]: Device: /dev/sda, 60 Currently 
unreadable (pending) sectors

Jul 14 16:25:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 16:55:39 cl-44 smartd[2687]: Device: /dev/sda, 63 Currently 
unreadable (pending) sectors

Jul 14 16:55:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 17:25:39 cl-44 smartd[2687]: Device: /dev/sda, 90 Currently 
unreadable (pending) sectors

Jul 14 17:25:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 17:55:39 cl-44 smartd[2687]: Device: /dev/sda, 90 Currently 
unreadable (pending) sectors

Jul 14 17:55:39 cl-44 smartd[2687]: Device: /dev/sda, 65 Offline 
uncorrectable sectors

Jul 14 18:25:39 cl-44 smartd[2687]: Device: /dev/sda, 90 Currently 
unreadable (pending) sectors

Jul 14 18:25:39 cl-44 smartd[2687]: Device: /dev/sda, 90 Offline 
uncorrectable sectors

Jul 14 18:55:39 cl-44 smartd[2687]: Device: /dev/sda, 90 Currently 
unreadable (pending) sectors

Jul 14 18:55:39 cl-44 smartd[2687]: Device: /dev/sda, 90 Offline 
uncorrectable sectors

Jul 14 19:25:39 cl-44 smartd[2687]: Device: /dev/sda, 90 Currently 
unreadable (pending) sectors

Jul 14 19:25:39 cl-44 smartd[2687]: Device: /dev/sda, 90 Offline 
uncorrectable sectors

Jul 14 19:55:40 cl-44 smartd[2687]: Device: /dev/sda, 90 Currently 
unreadable (pending) sectors

Jul 14 19:55:40 cl-44 smartd[2687]: Device: /dev/sda, 90 Offline 
uncorrectable sectors

Jul 14 20:25:39 cl-44 smartd[2687]: Device: /dev/sda, 90 Currently 
unreadable (pending) sectors

Jul 14 20:25:39 cl-44 smartd[2687]: Device: /dev/sda, 90 Offline 
uncorrectable sectors



from smarctl command:

# smartctl -l error -d ata /dev/sda

smartctl version 5.36 [i686-redhat-linux-gnu] Copyright (C) 2002-6 Bruce 
Allen

Home page is http://smartmontools.sourceforge.net/



=== START OF READ SMART DATA SECTION ===

SMART Error Log Version: 1

ATA Error Count: 52 (device log contains only the most recent five errors)

        CR = Command Register [HEX]

        FR = Features Register [HEX]

        SC = Sector Count Register [HEX]

        SN = Sector Number Register [HEX]

        CL = Cylinder Low Register [HEX]

        CH = Cylinder High Register [HEX]

        DH = Device/Head Register [HEX]

        DC = Device Command Register [HEX]

        ER = Error register [HEX]

        ST = Status register [HEX]

Powered_Up_Time is measured from power on, and printed as

DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,

SS=sec, and sss=millisec. It "wraps" after 49.710 days.



Error 52 occurred at disk power-on lifetime: 4015 hours (167 days + 7 hours)

  When the command that caused the error occurred, the device was 
active or idle.



  After command completion occurred, registers were:

  ER ST SC SN CL CH DH

  -- -- -- -- -- -- --

  10 51 01 6e 43 f9 ed



  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  -- -- -- -- -- -- -- --  ----------------  --------------------

  37 00 01 6e 43 f9 ed 00      05:03:57.209  SET MAX ADDRESS EXT

  27 00 00 6e 43 f9 e0 00      05:03:57.164  READ NATIVE MAX ADDRESS EXT

  37 00 00 6e 43 f9 ed 00      05:03:57.164  SET MAX ADDRESS EXT

  27 00 01 6e 43 f9 e0 00      05:03:57.164  READ NATIVE MAX ADDRESS EXT

  37 00 01 6e 43 f9 ed 00      05:04:01.507  SET MAX ADDRESS EXT



Error 51 occurred at disk power-on lifetime: 4015 hours (167 days + 7 hours)

  When the command that caused the error occurred, the device was 
active or idle.



  After command completion occurred, registers were:

  ER ST SC SN CL CH DH

  -- -- -- -- -- -- --

  10 51 01 6e 43 f9 ed



  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  -- -- -- -- -- -- -- --  ----------------  --------------------

  37 00 01 6e 43 f9 ed 00      05:03:57.209  SET MAX ADDRESS EXT

  27 00 00 6e 43 f9 e0 00      05:03:57.164  READ NATIVE MAX ADDRESS EXT

  37 00 00 6e 43 f9 ed 00      05:03:57.164  SET MAX ADDRESS EXT

  27 00 01 af 4b f9 e0 00      05:03:57.164  READ NATIVE MAX ADDRESS EXT

  29 00 01 af 4b f9 e0 00      05:03:57.164  READ MULTIPLE EXT



Error 50 occurred at disk power-on lifetime: 4014 hours (167 days + 6 hours)

  When the command that caused the error occurred, the device was 
active or idle.



  After command completion occurred, registers were:

  ER ST SC SN CL CH DH

  -- -- -- -- -- -- --

  10 51 01 6e 43 f9 ed



  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  -- -- -- -- -- -- -- --  ----------------  --------------------

  37 00 01 6e 43 f9 ed 00      03:54:04.428  SET MAX ADDRESS EXT

  27 00 00 6e 43 f9 e0 00      03:54:02.348  READ NATIVE MAX ADDRESS EXT

  37 00 00 6e 43 f9 ed 00      03:54:02.288  SET MAX ADDRESS EXT

  27 00 01 6e 43 f9 e0 00      03:54:02.072  READ NATIVE MAX ADDRESS EXT

  37 00 01 6e 43 f9 ed 00      03:54:02.001  SET MAX ADDRESS EXT



Error 49 occurred at disk power-on lifetime: 4014 hours (167 days + 6 hours)

  When the command that caused the error occurred, the device was 
active or idle.



  After command completion occurred, registers were:

  ER ST SC SN CL CH DH

  -- -- -- -- -- -- --

  10 51 01 6e 43 f9 ed



  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  -- -- -- -- -- -- -- --  ----------------  --------------------

  37 00 01 6e 43 f9 ed 00      03:54:00.392  SET MAX ADDRESS EXT

  27 00 00 6e 43 f9 e0 00      03:54:02.348  READ NATIVE MAX ADDRESS EXT

  37 00 00 6e 43 f9 ed 00      03:54:02.288  SET MAX ADDRESS EXT

  27 00 01 af 4b f9 e0 00      03:54:02.072  READ NATIVE MAX ADDRESS EXT

  29 00 01 af 4b f9 e0 00      03:54:02.001  READ MULTIPLE EXT



Error 48 occurred at disk power-on lifetime: 4013 hours (167 days + 5 hours)

  When the command that caused the error occurred, the device was 
active or idle.



  After command completion occurred, registers were:

  ER ST SC SN CL CH DH

  -- -- -- -- -- -- --

  10 51 01 6e 43 f9 ed



  Commands leading to the command that caused the error were:

  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name

  -- -- -- -- -- -- -- --  ----------------  --------------------

  37 00 01 6e 43 f9 ed 00      03:24:05.625  SET MAX ADDRESS EXT

  27 00 00 6e 43 f9 e0 00      03:24:05.565  READ NATIVE MAX ADDRESS EXT

  37 00 00 6e 43 f9 ed 00      03:24:05.349  SET MAX ADDRESS EXT

  27 00 01 6e 43 f9 e0 00      03:24:05.278  READ NATIVE MAX ADDRESS EXT

  37 00 01 6e 43 f9 ed 00      03:24:05.132  SET MAX ADDRESS EXT



i check on this.. http://bugzilla.kernel.org/show_bug.cgi?id=8650 it seems that 
it the same problem that i encounter.. how to solve this?

thanks
 
Best Regards,
Markus



Send instant messages to your online friends http://uk.messenger.yahoo.com 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.