On Wed, Jan 24, 2007 at 11:07:24PM +0100, Tobias Walkowiak wrote: > [...] > Jan 24 22:56:54 newt kernel: ata2: hard resetting port > Jan 24 22:56:54 newt kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) > Jan 24 22:56:54 newt kernel: ata2.00: configured for UDMA/33 > Jan 24 22:56:54 newt kernel: sd 1:0:0:0: SCSI error: return code = 0x08000002 > Jan 24 22:56:54 newt kernel: sdb: Current: sense key: Aborted Command > Jan 24 22:56:54 newt kernel: Additional sense: No additional sense information > Jan 24 22:56:54 newt kernel: end_request: I/O error, dev sdb, sector 128931703 > Jan 24 22:56:54 newt kernel: loop2: loop_end_io_transfer err=-5 bi_rw=0x0 > [...] > with the last line repeating severeal times. Now I wonder if that's an > error in loop-aes, the harddisk or the linux kernel (my feelings tell me > that it is the latter one). Thanks for your answers and hints. After doing checks with a simple badblocks(8) several errors have been shown. The smartmontools weren't working on that drive. I get an error like Default self test failed [unsupported scsi opcode] So, there have been no SW-related errors neither to the kernel (what wonder, although I'm using a 2.6.18 ;) nor to loop-aes (sorry for having even the least doubt ;) but simply some blocks near the end of the hard drive are broken. Now I will try out the Seagate support for Maxtor harddisks. Thanks again and best wishes Tobias -- [id] tw@xxxxxxxxxxxxxxxxxxx [gpg ID] 1024D/25B20A1E [net place] http://tobias-walkowiak.de [message] ><> Jesus loves you <><
Attachment:
signature.asc
Description: Digital signature
