Re: strange behavior after reboot, iceweasel locking everything up

[Camaleón <noelamac@gmail.com>]

On Sun, 12 Aug 2012 12:45:03 -0400, Tony Baldwin wrote:

> Yesterday I had to reboot my machine. Cleaning house, I had dislodged
> the plug for a power strip that powered the computer, monitor, and
> printer.
> 
> Now, I am seeing very odd behavior.

(...)

> The only anomalies I have noted in dmesg, etc., are that some sectors of
> my hdd are not reading correctly, or something. A file system check
> forced on a second reboot yesterday failed, which is disconcerting, but
> I'm not certain what to make of that.
> 
> dmesg | tail gives me
> [79477.080607] ata6.00: failed command: READ DMA EXT 
> [79477.080621] ata6.00: cmd 25/00:08:9d:23:9f/00:00:6c:00:00/e0 tag 0 dma 4096 in 
> [79477.080624]          res 51/40:00:9d:23:9f/40:00:6c:00:00/00 Emask 0x9 (media error)
> [79477.080631] ata6.00: status: { DRDY ERR } 
> [79477.080635] ata6.00: error: { UNC } [79477.196994] ata6.00: configured for UDMA/33
> [78506.185310] sd 5:0:0:0: [sda] Unhandled sense code 
> [78506.185315] sd 5:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> [78506.185322] sd 5:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
> [78506.185331] Descriptor sense data with sense descriptors (in hex):
> [78506.185335]         72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
> [78506.185351]         6c 9f 23 9d
> [78506.185358] sd 5:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
> [78506.185368] sd 5:0:0:0: [sda] CDB: Read(10): 28 00 6c 9f 23 9d 00 00 08 00
> [78506.185378] end_request: I/O error, dev sda, sector 1822368669
> [78506.185398] ata6: EH complete
> 
> I don't know what to make of that.

(...)

Wow! Just to prevent from a disaster, ensure you have a full and updated backup 
copy of your whole data. Then you can proceed with some basic tests:

1/ Check the cabling inside the computer, mainly sata cables, they could have been 
moved or be badly seated (ensure that all sata connectors are firmly tighten).

2/ Use sata quality cables when possible. For testing purposes, you can try with a
different sata cable, at least for the device attached to ata6.00 port 
("dmesg | grep -i ata6.00" will tell what's hanging there).

3/ Download the disk utilities from the hard disk manufacturer (which usually runs 
from an ISO livecd) and scan your hard disks for smart or another errors (always run
soft/non-destructive tests).

4/ From a LiveCD, you can additionaly get the results from "smartcl" long test mode 
to compare with the results from step 3/.

And provide the results of all these set of tests :-)

Greetings,

-- 
Camaleón