Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
festplattem meldung im syslog
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

 
Reply to topic    Gentoo Forums Forum Index Deutsches Forum (German)
View previous topic :: View next topic  
Author Message
pieter_parker
Veteran
Veteran


Joined: 07 Aug 2006
Posts: 1488
Location: 127.0.0.1

PostPosted: Tue Aug 12, 2008 7:18 pm    Post subject: festplattem meldung im syslog Reply with quote

Code:

Aug 12 21:11:57 desktop ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
Aug 12 21:11:57 desktop ata5.00: cmd ec/00:00:00:00:00/00:00:00:00:00/00 tag 0 pio 512 in
Aug 12 21:11:57 desktop res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 12 21:11:57 desktop ata5.00: status: { DRDY }
Aug 12 21:11:57 desktop ata5: hard resetting link
Aug 12 21:12:03 desktop ata5: port is slow to respond, please be patient (Status 0x80)
Aug 12 21:12:07 desktop ata5: softreset failed (device not ready)
Aug 12 21:12:07 desktop ata5: hard resetting link
Aug 12 21:12:13 desktop ata5: port is slow to respond, please be patient (Status 0x80)
Aug 12 21:12:17 desktop ata5: softreset failed (device not ready)
Aug 12 21:12:17 desktop ata5: hard resetting link
Aug 12 21:12:23 desktop ata5: port is slow to respond, please be patient (Status 0x80)
Aug 12 21:12:44 desktop su[24311]: Successful su for root by peter
Aug 12 21:12:44 desktop su[24311]: + pts/7 peter:root
Aug 12 21:12:44 desktop su[24311]: pam_unix(su:session): session opened for user root by (uid=1000)
Aug 12 21:12:52 desktop ata5: softreset failed (device not ready)
Aug 12 21:12:52 desktop ata5: limiting SATA link speed to 1.5 Gbps
Aug 12 21:12:52 desktop ata5: hard resetting link
Aug 12 21:12:57 desktop ata5: softreset failed (device not ready)
Aug 12 21:12:57 desktop ata5: reset failed, giving up
Aug 12 21:12:57 desktop ata5.00: disabled
Aug 12 21:12:57 desktop ata5: EH complete
Aug 12 21:13:25 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:25 desktop end_request: I/O error, dev sde, sector 8279
Aug 12 21:13:25 desktop EXT3-fs error (device sde1): ext3_get_inode_loc: unable to read inode block - inode=2, block=1027
Aug 12 21:13:25 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:25 desktop end_request: I/O error, dev sde, sector 63
Aug 12 21:13:25 desktop printk: 119 messages suppressed.
Aug 12 21:13:25 desktop Buffer I/O error on device sde1, logical block 0
Aug 12 21:13:25 desktop lost page write due to I/O error on sde1
Aug 12 21:13:25 desktop EXT3-fs error (device sde1) in ext3_reserve_inode_write: IO failure
Aug 12 21:13:25 desktop WARNING: at fs/buffer.c:1169 mark_buffer_dirty()
Aug 12 21:13:25 desktop Pid: 24345, comm: kio_file Tainted: P        2.6.24-gentoo-r7 #2
Aug 12 21:13:25 desktop [<c019573c>] mark_buffer_dirty+0x7c/0x90
Aug 12 21:13:25 desktop [<c01bd928>] ext3_commit_super+0x48/0x80
Aug 12 21:13:25 desktop [<c01be290>] ext3_handle_error+0x70/0xc0
Aug 12 21:13:25 desktop [<c0128d9b>] printk+0x1b/0x20
Aug 12 21:13:25 desktop [<c01be320>] __ext3_std_error+0x40/0x60
Aug 12 21:13:25 desktop [<c01b654f>] ext3_reserve_inode_write+0x3f/0x80
Aug 12 21:13:25 desktop [<c0180ae0>] filldir64+0x0/0xe0
Aug 12 21:13:25 desktop [<c01b65aa>] ext3_mark_inode_dirty+0x1a/0x40
Aug 12 21:13:25 desktop [<c01c65ff>] journal_start+0x7f/0xb0
Aug 12 21:13:25 desktop [<c01b95b9>] ext3_dirty_inode+0x79/0x90
Aug 12 21:13:25 desktop [<c0191470>] __mark_inode_dirty+0x30/0x170
Aug 12 21:13:25 desktop [<c0180ae0>] filldir64+0x0/0xe0
Aug 12 21:13:25 desktop [<c012cda3>] current_fs_time+0x13/0x20
Aug 12 21:13:25 desktop [<c0180ae0>] filldir64+0x0/0xe0
Aug 12 21:13:25 desktop [<c0180d2e>] vfs_readdir+0x8e/0x90
Aug 12 21:13:25 desktop [<c0180da2>] sys_getdents64+0x72/0xd0
Aug 12 21:13:25 desktop [<c010427e>] sysenter_past_esp+0x5f/0x85
Aug 12 21:13:25 desktop [<c0450000>] rpc_sleep_on+0x0/0x260
Aug 12 21:13:25 desktop =======================
Aug 12 21:13:25 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:25 desktop end_request: I/O error, dev sde, sector 63
Aug 12 21:13:25 desktop Buffer I/O error on device sde1, logical block 0
Aug 12 21:13:25 desktop lost page write due to I/O error on sde1
Aug 12 21:13:25 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:25 desktop end_request: I/O error, dev sde, sector 146800719
Aug 12 21:13:25 desktop EXT3-fs error (device sde1): ext3_get_inode_loc: unable to read inode block - inode=9175041, block=18350082
Aug 12 21:13:25 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:25 desktop end_request: I/O error, dev sde, sector 63
Aug 12 21:13:25 desktop Buffer I/O error on device sde1, logical block 0
Aug 12 21:13:25 desktop lost page write due to I/O error on sde1
Aug 12 21:13:25 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:25 desktop end_request: I/O error, dev sde, sector 731381839
Aug 12 21:13:25 desktop EXT3-fs error (device sde1): ext3_get_inode_loc: unable to read inode block - inode=45711361, block=91422722
Aug 12 21:13:25 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:25 desktop end_request: I/O error, dev sde, sector 63
Aug 12 21:13:25 desktop Buffer I/O error on device sde1, logical block 0
Aug 12 21:13:25 desktop lost page write due to I/O error on sde1
Aug 12 21:13:25 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:25 desktop end_request: I/O error, dev sde, sector 8279
Aug 12 21:13:25 desktop EXT3-fs error (device sde1): ext3_get_inode_loc: unable to read inode block - inode=11, block=1027
Aug 12 21:13:25 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:25 desktop end_request: I/O error, dev sde, sector 63
Aug 12 21:13:25 desktop Buffer I/O error on device sde1, logical block 0
Aug 12 21:13:25 desktop lost page write due to I/O error on sde1
Aug 12 21:13:27 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:27 desktop end_request: I/O error, dev sde, sector 8279
Aug 12 21:13:27 desktop EXT3-fs error (device sde1): ext3_get_inode_loc: unable to read inode block - inode=2, block=1027
Aug 12 21:13:27 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:27 desktop end_request: I/O error, dev sde, sector 63
Aug 12 21:13:27 desktop Buffer I/O error on device sde1, logical block 0
Aug 12 21:13:27 desktop lost page write due to I/O error on sde1
Aug 12 21:13:27 desktop EXT3-fs error (device sde1) in ext3_reserve_inode_write: IO failure
Aug 12 21:13:27 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:27 desktop end_request: I/O error, dev sde, sector 63
Aug 12 21:13:27 desktop Buffer I/O error on device sde1, logical block 0
Aug 12 21:13:27 desktop lost page write due to I/O error on sde1
Aug 12 21:13:27 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:27 desktop end_request: I/O error, dev sde, sector 146800719
Aug 12 21:13:27 desktop EXT3-fs error (device sde1): ext3_get_inode_loc: unable to read inode block - inode=9175041, block=18350082
Aug 12 21:13:27 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:27 desktop end_request: I/O error, dev sde, sector 63
Aug 12 21:13:27 desktop Buffer I/O error on device sde1, logical block 0
Aug 12 21:13:27 desktop lost page write due to I/O error on sde1
Aug 12 21:13:27 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:27 desktop end_request: I/O error, dev sde, sector 731381839
Aug 12 21:13:27 desktop EXT3-fs error (device sde1): ext3_get_inode_loc: unable to read inode block - inode=45711361, block=91422722
Aug 12 21:13:27 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:27 desktop end_request: I/O error, dev sde, sector 63
Aug 12 21:13:27 desktop Buffer I/O error on device sde1, logical block 0
Aug 12 21:13:27 desktop lost page write due to I/O error on sde1
Aug 12 21:13:27 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:27 desktop end_request: I/O error, dev sde, sector 8279
Aug 12 21:13:27 desktop EXT3-fs error (device sde1): ext3_get_inode_loc: unable to read inode block - inode=11, block=1027
Aug 12 21:13:27 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:27 desktop end_request: I/O error, dev sde, sector 63
Aug 12 21:13:27 desktop Buffer I/O error on device sde1, logical block 0
Aug 12 21:13:27 desktop lost page write due to I/O error on sde1
Aug 12 21:13:31 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:31 desktop end_request: I/O error, dev sde, sector 12423
Aug 12 21:13:31 desktop Buffer I/O error on device sde1, logical block 1545
Aug 12 21:13:31 desktop lost page write due to I/O error on sde1
Aug 12 21:13:31 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:31 desktop end_request: I/O error, dev sde, sector 12431
Aug 12 21:13:31 desktop Aborting journal on device sde1.
Aug 12 21:13:31 desktop sd 4:0:0:0: [sde] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
Aug 12 21:13:31 desktop end_request: I/O error, dev sde, sector 12423

dateiensystem fehler oder hardware fehler in der festplatte ? was genau bedeuten diese meldungen ?
Back to top
View user's profile Send private message
Finswimmer
Bodhisattva
Bodhisattva


Joined: 02 Sep 2004
Posts: 5467
Location: Langen (Hessen), Germany

PostPosted: Tue Aug 12, 2008 8:59 pm    Post subject: Reply with quote

Boote mal von der LiveCD und lass dann das FS checken.
Aber ich tippe trotzdem auf nen HW-Defekt.

Tobi
_________________
Bitte auf Rechtschreibung, korrekte Formatierung und Höflichkeit achten!
Danke
Back to top
View user's profile Send private message
pieter_parker
Veteran
Veteran


Joined: 07 Aug 2006
Posts: 1488
Location: 127.0.0.1

PostPosted: Thu Aug 14, 2008 11:26 pm    Post subject: Reply with quote

beim reboot hat der sata controler das laufwerk nicht mehr angezeigt
es war/ist sde gewesen, nun sind alle nachfolgenden laufwerke um eins verrueckt, ziemliches durcheinander nun
laesst sich irgendwie festlegen welche festplatte welches sdX ist ?
Back to top
View user's profile Send private message
ChrisJumper
Advocate
Advocate


Joined: 12 Mar 2005
Posts: 2403
Location: Germany

PostPosted: Fri Aug 15, 2008 12:00 am    Post subject: Reply with quote

Quote:
aesst sich irgendwie festlegen welche festplatte welches sdX ist?


Mit udev kann man entsprechende Regeln erstellen, die dann einer Festplatte, Usbstick, SD-Karte, Drucker oder Kamera einen bestimmten Gerätenamen zuweisen.

Merkwürdigerweise bist du schon der dritte in meinem Bekanntenkreis dem in dieser Woche eine Festplatte kaputt gegangen ist. Mir selber auch zwei! Neue kaufen und das Backup nicht vergessen.... Ach ja.. hier im Forum meinte mal einer wenn die komisch klackern kann man die nochmal ins Tiefkühlfach legen.. sie dann anschließen und sie geht evtl noch ein wenig und man hat zeit Daten zu retten. Mir hat dieser Tipp bei einer festplatte wirklich geholfen ;)
Back to top
View user's profile Send private message
Finswimmer
Bodhisattva
Bodhisattva


Joined: 02 Sep 2004
Posts: 5467
Location: Langen (Hessen), Germany

PostPosted: Fri Aug 15, 2008 5:42 am    Post subject: Reply with quote

ChrisJumper wrote:
Quote:
aesst sich irgendwie festlegen welche festplatte welches sdX ist?


Mit udev kann man entsprechende Regeln erstellen, die dann einer Festplatte, Usbstick, SD-Karte, Drucker oder Kamera einen bestimmten Gerätenamen zuweisen.

Merkwürdigerweise bist du schon der dritte in meinem Bekanntenkreis dem in dieser Woche eine Festplatte kaputt gegangen ist. Mir selber auch zwei! Neue kaufen und das Backup nicht vergessen.... Ach ja.. hier im Forum meinte mal einer wenn die komisch klackern kann man die nochmal ins Tiefkühlfach legen.. sie dann anschließen und sie geht evtl noch ein wenig und man hat zeit Daten zu retten. Mir hat dieser Tipp bei einer festplatte wirklich geholfen ;)


Aber vorher luftdicht verpacken, wenn Wasser reinkommt (Schwitzwasser) ist erst recht Sense ;)

Tobi
_________________
Bitte auf Rechtschreibung, korrekte Formatierung und Höflichkeit achten!
Danke
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Deutsches Forum (German) All times are GMT
Page 1 of 1

 
Jump to:  
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