|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
Date: Fri, 2 Oct 1998 09:03:53 +0200 (MET DST) From: Mikael Abrahamsson <swmike@swm.pp.se> To: Claudiu Balciza <cbalciza@geocities.com> cc: Linux SCSI <linux-scsi@vger.rutgers.edu> In-Reply-To: <000501bdedd1$37f20e80$0300010a@claudiu.altex.ro> On Fri, 2 Oct 1998, Claudiu Balciza wrote: > Oct 1 01:05:13 digital kernel: scsi : aborting command due to timeout : pid > 125633, scsi0, channel 0, id 0, lun 0 Write (6) 05 40 63 f4 00 > ---------------------- > > At that time it was executing updatedb.cron, logrotate and database sweep > As I remember, this happened before (yet rare) but I cannot remember if it > happened > under kernel 2.0.35 I used previously. > What does that means ? > Is there any _danger_ message hidden ? When I started getting these messages I didnt think there was something majorly wrong, or that it was a cable fault. After about 2 months I started to get bad sectors on my / mounted Quantum Atlas 2gig. It got worse and worse over time. My theory is that these above messages are because the drive starts retrying to read sectors and succeeds after a lot of attempts. I replaced the drive shortly afterwards and after low level formattning it I now use it for non-crucial temp storage. Then again, it might be a cable problem too. Be warned, though. ----- Mikael Abrahamsson email: swmike@swm.pp.se - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@vger.rutgers.edu
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |