死 harddisk or 死 motherboard

chancho

Feb 21 08:29:08 Server kernel: [1795700.903731] ata1.00: status: { DRDY }
Feb 21 08:29:08 Server kernel: [1795705.920460] ata1: link is slow to respond, please be patient (ready=0)
Feb 21 08:29:08 Server kernel: [1795710.933801] ata1: device not ready (errno=-16), forcing hardreset
Feb 21 08:29:08 Server kernel: [1795710.933814] ata1: soft resetting link
Feb 21 08:29:08 Server kernel: [1795711.474349] ata1.00: configured for UDMA/33
Feb 21 08:29:08 Server kernel: [1795711.474358] ata1.00: retrying FLUSH 0xea Emask 0x4
Feb 21 08:29:08 Server kernel: [1795711.474668] ata1.00: device reported invalid CHS sector 0
Feb 21 08:29:08 Server kernel: [1795711.474702] ata1: EH complete
Feb 21 08:27:52 Server smbd[4984]: [2012/02/21 08:27:52.361571,  0] printing/print_cups.c:318(cups_cache_reload_async)
Feb 21 08:27:52 Server smbd[4984]:   Unable to get printer list - server-error-internal-error
Feb 21 08:27:52 Server smbd[1274]: [2012/02/21 08:27:52.362072,  0] printing/print_cups.c:487(cups_async_callback)
Feb 21 08:27:52 Server smbd[1274]:   failed to retrieve printer list: NT_STATUS_UNSUCCESSFUL
Feb 21 08:29:08 Server kernel: [1795771.820501] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Feb 21 08:29:08 Server kernel: [1795771.824597] ata1.00: failed command: FLUSH CACHE EXT
Feb 21 08:29:08 Server kernel: [1795771.828634] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Feb 21 08:29:08 Server kernel: [1795771.828637]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 21 08:29:08 Server kernel: [1795771.836700] ata1.00: status: { DRDY }
Feb 21 08:29:08 Server kernel: [1795776.853806] ata1: link is slow to respond, please be patient (ready=0)
Feb 21 08:29:08 Server kernel: [1795781.867142] ata1: device not ready (errno=-16), forcing hardreset
Feb 21 08:29:08 Server kernel: [1795781.867160] ata1: soft resetting link
Feb 21 08:29:08 Server kernel: [1795782.181011] ata1.00: configured for UDMA/33
Feb 21 08:29:08 Server kernel: [1795782.181021] ata1.00: retrying FLUSH 0xea Emask 0x4
Feb 21 08:29:08 Server kernel: [1795782.181332] ata1.00: device reported invalid CHS sector 0
Feb 21 08:29:08 Server kernel: [1795782.181362] ata1: EH complete
Feb 21 08:30:08 Server kernel: [1795842.860493] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Feb 21 08:30:08 Server kernel: [1795842.864713] ata1.00: failed command: FLUSH CACHE EXT
Feb 21 08:31:30 Server kernel: [1795842.868961] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Feb 21 08:31:30 Server kernel: [1795842.868964]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 21 08:31:30 Server kernel: [1795842.877046] ata1.00: status: { DRDY }
Feb 21 08:31:30 Server kernel: [1795847.893825] ata1: link is slow to respond, please be patient (ready=0)
Feb 21 08:31:30 Server kernel: [1795852.907140] ata1: device not ready (errno=-16), forcing hardreset
Feb 21 08:31:30 Server kernel: [1795852.907154] ata1: soft resetting link
Feb 21 08:31:30 Server kernel: [1795853.431004] ata1.00: configured for UDMA/33
Feb 21 08:31:30 Server kernel: [1795853.431013] ata1.00: retrying FLUSH 0xea Emask 0x4
Feb 21 08:31:30 Server kernel: [1795853.431323] ata1.00: device reported invalid CHS sector 0
Feb 21 08:31:30 Server kernel: [1795853.431343] ata1: EH complete
Feb 21 08:31:30 Server kernel: [1795913.900497] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Feb 21 08:31:30 Server kernel: [1795913.904561] ata1.00: failed command: FLUSH CACHE EXT
Feb 21 08:31:30 Server kernel: [1795913.908589] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Feb 21 08:31:30 Server kernel: [1795913.908591]          res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 21 08:31:30 Server kernel: [1795913.916650] ata1.00: status: { DRDY }
Feb 21 08:31:30 Server kernel: [1795918.927115] ata1: link is slow to respond, please be patient (ready=0)
Feb 21 08:31:30 Server kernel: [1795923.940452] ata1: device not ready (errno=-16), forcing hardreset
Feb 21 08:31:30 Server kernel: [1795923.940466] ata1: soft resetting link
Feb 21 08:31:30 Server kernel: [1795924.254320] ata1.00: configured for UDMA/33
Feb 21 08:31:30 Server kernel: [1795924.254329] ata1.00: retrying FLUSH 0xea Emask 0x4
Feb 21 08:31:30 Server kernel: [1795924.254658] ata1.00: device reported invalid CHS sector 0
Feb 21 08:31:30 Server kernel: [1795924.254690] ata1: EH complete

最近Server 無返應, error.log as above. 唔知是死harddisk or 死主板　?

ps. sorry, don't know how to use [code]

howdy

I would check your HDD cable connection and also the HDD with the manufacturer's diagnostic tool.  (using smartctl to read the SMART log may give you some hint also).

This is assuming you have had no problem with the system before. I remember having similar problem with a workstation in which it reset the SATA connection every now and then...... but it's a fixable driver problem

icarus-c

回復 1# chancho

if you have another sata controller to try with, try it.
it could be hard drive failure, faulty cable, controller or driver bug

chancho

the motherboard is a itx 330 and running up-to-date archlinux. there is no other controller. so i guess it is hard disk failure.

kelvin929

Feb 21 08:29:08 Server kernel: [1795711.474349] ata1.00: configured for UDMA/33
cable

chancho

what is that mean ?

chancho

smartctl said completed without error

howdy

smartctl said completed without error
chancho 發表於 2012-2-21 14:21

have you checked other attributes and see if there is anything abnormal?

by the way, did you update system packages since the last known-good time?

chancho

system became normal after a hard reset. it happened before during the chinese new year. so it is the second time in around 1 month. i will try another cable. it is the cheapest way.