System hangs, possible drive failure

2ck · 07-10-2010, 08:29 AM

Lately (in the past couple of weeks) my system has been hanging, particularly when I try to watch videos.

I'm not sure why this is happening, but when I looked through my system log files I found what's on the attached file. A couple of other programs that I use frequently (xmms2d and epiphany) have similar entries, and I assumed they are related because they are typically running when the slowdowns occur. Also, my /home partition is giving some errors which may or may not be related.

business_kid · 07-10-2010, 11:01 AM

You hardly need me to tell you this, but these

Jul 9 16:55:22 mirai-desktop kernel: [21240.693152] INFO: task amule:10012 blocked for more than 120 seconds.
Jul 7 20:31:13 mirai-desktop kernel: [ 7328.056311] sd 2:0:0:0: [sda] Unhandled error code
Jul 7 20:31:13 mirai-desktop kernel: [ 7328.056370] lost page write due to I/O error on sda7

All look pretty fatal for sda. Get what data you can off that disk. I suggest power off overnight, then backup first thing in the morning. Don't delay. Then you can start in with fsck -fcvy on each partition. Check the size of /lost+found on each partition. It should have nothing in it.

This could be motherboard, psu, or hard disk, (probably the HD) but it seems like component failure of some sort.

2ck · 07-10-2010, 06:32 PM

Thanks for replying. My partitions are clean and I see no
reason why my hard disk would be malfunctioning. That's
why I posted in this subforum.
What exactly do those log messages mean though?

business_kid · 07-11-2010, 02:51 AM

How do you explauin 'unhandled disk errors' 'lost page writes on sda7' All look pretty fatal for sda, like I said.
I am actually guessing at a disk controller faults. I can afford to be wrong from this distance. Hvae you done an fsck on sda7 with -fcvy as options?

2ck · 07-11-2010, 09:02 AM

I've checked all of my ext3 partitions and run a SMART "extended self-test" on the HD. The disk is only 4 years old and has never had any problems. Anyway, I attached info about the drive.

2ck · 07-11-2010, 08:42 PM

After removing the virtualbox kernel module the problem seems to be gone. I still don't know why that worked exactly, but I'll mark this as solved anyway.

Edit:
Nevermind, the problem is still there, and I am still logging peak load avgs of 7.0 or more.
Also:

Code:

Jul 12 07:32:24 mirai-desktop kernel: [ 1440.680067] INFO: task dpkg:24502 blocked for more than 120 seconds.
Jul 12 07:32:24 mirai-desktop kernel: [ 1440.680071] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 12 07:32:24 mirai-desktop kernel: [ 1440.680075] dpkg          D 0000000000000000     0 24502  14148 0x00000000
Jul 12 07:32:24 mirai-desktop kernel: [ 1440.680080]  ffffffff8145b1f0 0000000000000086 0000000000000000 0000000000000000
Jul 12 07:32:24 mirai-desktop kernel: [ 1440.680085]  ffff8800b9253e28 0000000000000000 000000000000f8a0 ffff8800b9253fd8
Jul 12 07:32:24 mirai-desktop kernel: [ 1440.680090]  0000000000015640 0000000000015640 ffff8800b9cbe2e0 ffff8800b9cbe5d8
Jul 12 07:32:24 mirai-desktop kernel: [ 1440.680095] Call Trace:
Jul 12 07:32:24 mirai-desktop kernel: [ 1440.680118]  [<ffffffffa0183f74>] ? log_wait_commit+0xbf/0x112 [jbd]
Jul 12 07:32:24 mirai-desktop kernel: [ 1440.680125]  [<ffffffff81064afa>] ? autoremove_wake_function+0x0/0x2e
Jul 12 07:32:24 mirai-desktop kernel: [ 1440.680131]  [<ffffffffa017fb51>] ? journal_stop+0x1dd/0x20f [jbd]
Jul 12 07:32:24 mirai-desktop kernel: [ 1440.680137]  [<ffffffffa0180ba0>] ? journal_start+0x96/0xc6 [jbd]
Jul 12 07:32:24 mirai-desktop kernel: [ 1440.680142]  [<ffffffff8110ae50>] ? vfs_fsync_range+0x73/0x9e
Jul 12 07:32:24 mirai-desktop kernel: [ 1440.680146]  [<ffffffff8110aefa>] ? do_fsync+0x28/0x39
Jul 12 07:32:24 mirai-desktop kernel: [ 1440.680149]  [<ffffffff8110af29>] ? sys_fsync+0xb/0x10
Jul 12 07:32:24 mirai-desktop kernel: [ 1440.680155]  [<ffffffff81010b42>] ? system_call_fastpath+0x16/0x1b
Jul 12 07:34:42 mirai-desktop kernel: [ 1579.130237] ata3: EH in SWNCQ mode,QC:qc_active 0x2 sactive 0x2 
Jul 12 07:34:42 mirai-desktop kernel: [ 1579.130248] ata3: SWNCQ:qc_active 0x2 defer_bits 0x0 last_issue_tag 0x1 
Jul 12 07:34:42 mirai-desktop kernel: [ 1579.130251]   dhfis 0x2 dmafis 0x0 sdbfis 0x0 
Jul 12 07:34:42 mirai-desktop kernel: [ 1579.130258] ata3: ATA_REG 0x41 ERR_REG 0x40
Jul 12 07:34:42 mirai-desktop kernel: [ 1579.130263] ata3: tag : dhfis dmafis sdbfis sacitve
Jul 12 07:34:42 mirai-desktop kernel: [ 1579.130269] ata3: tag 0x1: 1 0 0 1   
Jul 12 07:34:42 mirai-desktop kernel: [ 1579.130288] ata3.00: exception Emask 0x1 SAct 0x2 SErr 0x0 action 0x6 frozen
Jul 12 07:34:42 mirai-desktop kernel: [ 1579.130294] ata3.00: Ata error. fis:0x21
Jul 12 07:34:42 mirai-desktop kernel: [ 1579.130302] ata3.00: failed command: READ FPDMA QUEUED
Jul 12 07:34:42 mirai-desktop kernel: [ 1579.130316] ata3.00: cmd 60/08:08:0f:fc:00/00:00:00:00:00/40 tag 1 ncq 4096 in
Jul 12 07:34:42 mirai-desktop kernel: [ 1579.130319]          res 41/40:0c:0f:fc:00/40:00:00:00:00/40 Emask 0x9 (media error)
Jul 12 07:34:42 mirai-desktop kernel: [ 1579.130325] ata3.00: status: { DRDY ERR }
Jul 12 07:34:42 mirai-desktop kernel: [ 1579.130330] ata3.00: error: { UNC }
Jul 12 07:34:42 mirai-desktop kernel: [ 1579.130345] ata3: hard resetting link
Jul 12 07:34:42 mirai-desktop kernel: [ 1579.130349] ata3: nv: skipping hardreset on occupied port
Jul 12 07:34:43 mirai-desktop kernel: [ 1579.596069] ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Jul 12 07:34:43 mirai-desktop kernel: [ 1579.612287] ata3.00: configured for UDMA/100
Jul 12 07:34:43 mirai-desktop kernel: [ 1579.612309] ata3: EH complete

I'm starting to think there is a problem with my hd.