| View previous topic :: View next topic |
| Author |
Message |
tzzaetaynzz
Apprentice
Joined: 29 Sep 2003
Posts: 221
|
 Posted: Wed Feb 08, 2006 9:55 am Post subject: kernel warnings |
 |
|
hallo an alle,
seit gestern erhalte ich von logwatch eine taegliche zusammenfassung meiner logfiles. nun lese ich:
| Code: | WARNING: Kernel Errors Present
Buffer I/O error on device hda, l...: 102 Time(s)
end_request: I/O error, dev hda, sector...: 102 Time(s)
hda: command error: error=0x54...: 102 Time(s)
hda: command error: status=0x51 { D...: 102 Time(s)
hda: status timeout: error=0x00...: 3 Time(s)
st0: Error on write filemar...: 3 Time(s)
st0: Error with sense data:...: 13 Time(s)
usb 1-5: can't read configurations, error -71...: 1 Time(s)
usb 1-5: device descriptor read/all, error -71...: 1 Time(s) |
mein hda ist ein cd-rom, st0 ist ein dlt laufwerk und usb 1-5 ist mir unbekannt, also ich weiss zumindest nicht was dran haengen sollte.
muss ich mir sorgen machen;
was meint ihr?
_________________
gruss //tzzaettaynzz
---
Have you tried turning it off and on again? |
|
| Back to top |
|
 |
Finswimmer
Bodhisattva
Joined: 02 Sep 2004
Posts: 5467
Location: Langen (Hessen), Germany
|
| Posted: Wed Feb 08, 2006 10:05 am Post subject: |
|
|
Vielleicht bekommst du irgendwie die gesamte Fehlermeldung.
Aber, wenn in hda keine Cd ist, sollte er sowieso nichts zu melden haben.
Oder, du hast ein Programm, welches auf hda zugreift...
Tobi |
|
| Back to top |
|
|
tzzaetaynzz
Apprentice
Joined: 29 Sep 2003
Posts: 221
|
| Posted: Wed Feb 08, 2006 10:21 am Post subject: |
|
|
| Finswimmer wrote: | Vielleicht bekommst du irgendwie die gesamte Fehlermeldung.
|
danke fuer deine prompte antwort.
die gesmte meldung sieht dann wohl so aus.
| Code: | Feb 7 12:01:45 end_request: I/O error, dev hda, sector 0
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 4
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 8
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 12
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 16
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 20
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 24
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 28
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 32
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 36
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 40
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 44
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 48
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 52
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 56
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 60
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 64
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 68
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 72
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 76
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 80
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 84
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 88
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 92
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 96
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 100
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 104
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 108
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 112
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 116
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 120
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 124
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 0
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 4
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 0
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 4
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 8
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 12
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 16
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 20
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 24
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 28
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 32
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 36
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 40
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 44
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 48
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 52
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 56
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 60
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 64
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 68
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 72
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 76
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 80
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 84
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 88
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 92
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 96
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 100
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 104
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 108
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 112
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 116
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 120
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 124
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 0
Feb 7 12:01:45 end_request: I/O error, dev hda, sector 4
Feb 7 20:35:57 end_request: I/O error, dev hda, sector 0
Feb 7 20:35:57 end_request: I/O error, dev hda, sector 8
Feb 7 20:35:57 end_request: I/O error, dev hda, sector 16
Feb 7 20:35:57 end_request: I/O error, dev hda, sector 24
Feb 7 20:35:57 end_request: I/O error, dev hda, sector 32
Feb 7 20:35:57 end_request: I/O error, dev hda, sector 40
Feb 7 20:35:57 end_request: I/O error, dev hda, sector 48
Feb 7 20:35:57 end_request: I/O error, dev hda, sector 56
Feb 7 20:35:57 end_request: I/O error, dev hda, sector 64
Feb 7 20:35:57 end_request: I/O error, dev hda, sector 72
Feb 7 20:35:57 end_request: I/O error, dev hda, sector 80
Feb 7 20:35:57 end_request: I/O error, dev hda, sector 88
Feb 7 20:35:57 end_request: I/O error, dev hda, sector 96
Feb 7 20:35:57 end_request: I/O error, dev hda, sector 104
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 112
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 120
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 0
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 0
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 8
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 16
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 24
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 32
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 40
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 48
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 56
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 64
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 72
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 80
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 88
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 96
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 104
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 112
Feb 7 20:35:58 end_request: I/O error, dev hda, sector 120
Feb 7 20:35:58 end_request: I/O error, dev hda, sector |
| Finswimmer wrote: | Aber, wenn in hda keine Cd ist, sollte er sowieso nichts zu melden haben.
Oder, du hast ein Programm, welches auf hda zugreift...
|
zu beiden zeiten meine ich eine audio cd gerippt zu haben.
diese cds habe ich schon lange und so sehen sie auch aus.
auch ein defektes dlt tape, das meine ganze datensicherung schrottet,
habe ich aus gemacht.
daran wird es wohl liegen, oder?
meine laufwerke st0 und hda sind in ordnung,
nur die medien sind defekt!?
_________________
gruss //tzzaettaynzz
---
Have you tried turning it off and on again? |
|
| Back to top |
|
|
Finswimmer
Bodhisattva
Joined: 02 Sep 2004
Posts: 5467
Location: Langen (Hessen), Germany
|
| Posted: Wed Feb 08, 2006 10:27 am Post subject: |
|
|
Dass Audio Cds solche Meldungen bringen, ist eigentlich normal, zumal wenn sie verkratzt sind.
Audio Cds halten sich nicht an den richtigen Standard, deswegen passiert es auch oft, dass 2 gerippte Mp3s von demselben Titel unterschiedlich groß sind, bzw eine andere MD5 haben.
Sofern das nicht bei Daten Cds passiert, würde ich das getrost irgnorieren.
Tobi |
|
| Back to top |
|
|
tzzaetaynzz
Apprentice
Joined: 29 Sep 2003
Posts: 221
|
| Posted: Wed Feb 08, 2006 10:29 am Post subject: |
|
|
@Finswimmer
vielen dank!
das beruhigt.
_________________
gruss //tzzaettaynzz
---
Have you tried turning it off and on again? |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Deutsches Forum (German) 
