Re: READ FPDMA QUEUED und Daten weg
Hallo,
das es sich um ein Testing handelt schrieb ich nicht, da es mit dem
Squeeze das am selben PC installiert ist ebenso passiert.
Am Mittwoch, 18. April 2012 schrieb Siegfrid Brandstätter:
> Hallo,
> beim booten meines PC`s habe ich seit heute Probleme. Es kommt zu
> einem extrem langen Bootvorgang.
> Fehlermeldung die ich finde ist:
>
> fsck.ext4: Attempt to read block from filesystem resulted in short
> read while trying to open /dev/mapper/backup-Kino
> Could this be a zero-length partition?
>
> Im syslog fand ich dann noch:
>
> Apr 18 17:47:40 testing kernel: [ 7.881401] input: HDA Intel PCH
> HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
> Apr 18 17:47:40 testing kernel: [ 7.881980] input: HDA Intel PCH
> Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
> Apr 18 17:47:40 testing kernel: [ 8.172688] EXT4-fs (dm-0): re-
> mounted. Opts: (null)
> Apr 18 17:47:40 testing kernel: [ 8.224541] EXT4-fs (dm-0): re-
> mounted. Opts: errors=remount-ro
> Apr 18 17:47:40 testing kernel: [ 8.361205] loop: module loaded
> Apr 18 17:47:40 testing kernel: [ 8.395076] w83627ehf: Found
> NCT6776F chip at 0x290
> Apr 18 17:47:40 testing kernel: [ 12.168866] ata2.00: exception
> Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
> Apr 18 17:47:40 testing kernel: [ 12.169562] ata2.00: irq_stat
> 0x40000008
> Apr 18 17:47:40 testing kernel: [ 12.169963] ata2.00: failed
> command: READ FPDMA QUEUED
> Apr 18 17:47:40 testing kernel: [ 12.170489] ata2.00: cmd
> 60/08:00:7d:48:37/00:00:1c:00:00/40 tag 0 ncq 4096 in
> Apr 18 17:47:40 testing kernel: [ 12.170490] res
> 41/40:00:84:48:37/00:00:1c:00:00/40 Emask 0x409 (media error) <F>
> Apr 18 17:47:40 testing kernel: [ 12.172061] ata2.00: status: {
> DRDY ERR }
> Apr 18 17:47:40 testing kernel: [ 12.172469] ata2.00: error: { UNC
> } Apr 18 17:47:40 testing kernel: [ 12.180183] ata2.00: configured
> for UDMA/133
> Apr 18 17:47:40 testing kernel: [ 12.180191] ata2: EH complete
> Apr 18 17:47:40 testing kernel: [ 14.249397] ata2.00: exception
> Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
> Apr 18 17:47:40 testing kernel: [ 14.250086] ata2.00: irq_stat
> 0x40000008
> Apr 18 17:47:40 testing kernel: [ 14.250486] ata2.00: failed
> command: READ FPDMA QUEUED
> Apr 18 17:47:40 testing kernel: [ 14.251019] ata2.00: cmd
> 60/08:00:7d:48:37/00:00:1c:00:00/40 tag 0 ncq 4096 in
> Apr 18 17:47:40 testing kernel: [ 14.251020] res
> 41/40:00:84:48:37/00:00:1c:00:00/40 Emask 0x409 (media error) <F>
> Apr 18 17:47:40 testing kernel: [ 14.252589] ata2.00: status: {
> DRDY ERR }
> Apr 18 17:47:40 testing kernel: [ 14.252996] ata2.00: error: { UNC
> } Apr 18 17:47:40 testing kernel: [ 14.255722] ata2.00: configured
> for UDMA/133
> Apr 18 17:47:40 testing kernel: [ 14.255732] ata2: EH complete
> Apr 18 17:47:40 testing kernel: [ 16.646295] ata2.00: exception
> Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
> -||-
> Apr 18 17:47:40 testing kernel: [ 92.794323] ata2.00: status: {
> DRDY ERR }
> Apr 18 17:47:40 testing kernel: [ 92.794324] ata2.00: error: { UNC
> } Apr 18 17:47:40 testing kernel: [ 92.797679] ata2.00: configured
> for UDMA/133
> Apr 18 17:47:40 testing kernel: [ 92.797690] sd 1:0:0:0: [sdb]
> Unhandled sense code
> Apr 18 17:47:40 testing kernel: [ 92.797692] sd 1:0:0:0: [sdb]
> Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> Apr 18 17:47:40 testing kernel: [ 92.797694] sd 1:0:0:0: [sdb]
> Sense Key : Medium Error [current] [descriptor]
> Apr 18 17:47:40 testing kernel: [ 92.797696] Descriptor sense data
> with sense descriptors (in hex):
> Apr 18 17:47:40 testing kernel: [ 92.797698] 72 03 11 04 00
> 00 00 0c 00 0a 80 00 00 00 00 00
> Apr 18 17:47:40 testing kernel: [ 92.797701] 1c 37 48 28
> Apr 18 17:47:40 testing kernel: [ 92.797703] sd 1:0:0:0: [sdb]
> Add. Sense: Unrecovered read error - auto reallocate failed
> Apr 18 17:47:40 testing kernel: [ 92.797706] sd 1:0:0:0: [sdb] CDB:
> Read(10): 28 00 1c 37 48 25 00 00 40 00
> Apr 18 17:47:40 testing kernel: [ 92.797710] end_request: I/O
> error, dev sdb, sector 473385000
> Apr 18 17:47:40 testing kernel: [ 92.797713] Buffer I/O error on
> device dm-3, logical block 4
> Apr 18 17:47:40 testing kernel: [ 92.797717] Buffer I/O error on
> device dm-3, logical block 5
> Apr 18 17:47:40 testing kernel: [ 92.797719] Buffer I/O error on
> device dm-3, logical block 6
> Apr 18 17:47:40 testing kernel: [ 92.797720] Buffer I/O error on
> device dm-3, logical block 7
> Apr 18 17:47:40 testing kernel: [ 92.797722] Buffer I/O error on
> device dm-3, logical block 8
> Apr 18 17:47:40 testing kernel: [ 92.797724] Buffer I/O error on
> device dm-3, logical block 9
> Apr 18 17:47:40 testing kernel: [ 92.797726] Buffer I/O error on
> device dm-3, logical block 10
> Apr 18 17:47:40 testing kernel: [ 92.797728] Buffer I/O error on
> device dm-3, logical block 11
> Apr 18 17:47:40 testing kernel: [ 92.797735] ata2: EH complete
>
Wie stellt man fest was "dm-3" ist?
> später dann von:
> logical block 15 bis-
> Apr 18 17:47:40 testing kernel: [ 116.551944] Buffer I/O error on
> device dm-3, logical block 21
> Apr 18 17:47:40 testing kernel: [ 116.551946] Buffer I/O error on
> device dm-3, logical block 22
> Apr 18 17:47:40 testing kernel: [ 116.551948] Buffer I/O error on
> device dm-3, logical block 23
> Apr 18 17:47:40 testing kernel: [ 116.551957] ata2: EH complete
>
> 47:40 testing kernel: [ 213.446953] ata2: EH complete
> Apr 18 17:47:40 testing kernel: [ 215.326336] ata2.00: exception
> Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
> Apr 18 17:47:40 testing kernel: [ 215.356078] ata2.00: irq_stat
> 0x40000008
> Apr 18 17:47:40 testing kernel: [ 215.385754] ata2.00: failed
> command: READ FPDMA QUEUED
> Apr 18 17:47:40 testing kernel: [ 215.415416] ata2.00: cmd
> 60/08:00:25:48:37/00:00:1c:00:00/40 tag 0 ncq 4096 in
> Apr 18 17:47:40 testing kernel: [ 215.415417] res
> 41/40:00:28:48:37/00:00:1c:00:00/40 Emask 0x409 (media error) <F>
> Apr 18 17:47:40 testing kernel: [ 215.415419] ata2.00: status: {
> DRDY ERR }
> Apr 18 17:47:40 testing kernel: [ 215.415420] ata2.00: error: { UNC
> } Apr 18 17:47:40 testing kernel: [ 215.418695] ata2.00: configured
> for UDMA/133
> Apr 18 17:47:40 testing kernel: [ 215.418703] sd 1:0:0:0: [sdb]
> Unhandled sense code
> Apr 18 17:47:40 testing kernel: [ 215.418705] sd 1:0:0:0: [sdb]
> Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
> Apr 18 17:47:40 testing kernel: [ 215.418707] sd 1:0:0:0: [sdb]
> Sense Key : Medium Error [current] [descriptor]
> Apr 18 17:47:40 testing kernel: [ 215.418709] Descriptor sense data
> with sense descriptors (in hex):
> Apr 18 17:47:40 testing kernel: [ 215.418710] 72 03 11 04 00
> 00 00 0c 00 0a 80 00 00 00 00 00
> Apr 18 17:47:40 testing kernel: [ 215.418714] 1c 37 48 28
> Apr 18 17:47:40 testing kernel: [ 215.418716] sd 1:0:0:0: [sdb]
> Add. Sense: Unrecovered read error - auto reallocate failed
> Apr 18 17:47:40 testing kernel: [ 215.418719] sd 1:0:0:0: [sdb] CDB:
> Read(10): 28 00 1c 37 48 25 00 00 08 00
> Apr 18 17:47:40 testing kernel: [ 215.418723] end_request: I/O
> error, dev sdb, sector 473385000
> Apr 18 17:47:40 testing kernel: [ 215.418732] ata2: EH complete
> Apr 18 17:47:40 testing kernel: [ 215.418757] EXT4-fs (dm-3): can't
> read group descriptor 3
> Apr 18 17:47:40 testing kernel: [ 217.151825] fuse init (API version
> 7.17)
> Apr 18 17:47:41 testing acpid: starting up with netlink and the input
> layer
> Apr 18 17:47:41 testing acpid: 1 rule loaded
> Apr 18 17:47:41 testing acpid: waiting for events: event logging is
> off Apr 18 17:47:41 testing NetworkManager[2084]: <info>
> NetworkManager (version 0.9.2.0) is starting...
> usw.
>
> Am Ende konnte ich nur mit "Ctrl+D" KDE starten.
>
Wenn ich in der "fstab" den Eintrag von:
"/dev/mapper/backup-Kino /Kino ext4 defaults 0 2" deaktiviere, kann
ich ohne "Ctrl+D" in KDE einloggen. Jedoch werden auch dabei Minutenlang
obige Fehler ausgegeben. Aber in der "/var/log/fsck/checkfs" steht dann
nichts mehr von Fehlern
>
> In "/var/log/fsck/checkfs" steht:
>
> Log of fsck -C -R -A -a
> Wed Apr 18 17:45:19 2012
>
> fsck from util-linux 2.20.1
> /dev/mapper/xvt1-root: clean, 9985/85008 files, 263692/339968 blocks
> /dev/mapper/backup-bk1: clean, 302126/14721024 files,
> 11781019/58880000 blocks
> fsck.ext4: Attempt to read block from filesystem resulted in short
> read while trying to open /dev/mapper/backup-Kino
> Could this be a zero-length partition?
> fsck died with exit status 8
> Wed Apr 18 17:45:59 2012
>
> Leider verstehe ich die letzte Frage nicht was dies bedeutet, ( Could
> this be a zero-length partition?) Die Daten sind dort zum Grossteil
> nicht mehr vorhanden.
>
Von ca. 30 Filmen gibt es gerade noch einen Ordner mit einem Film.
> Wie kann ich es reparieren? Danke
> für Hilfe im voraus.
--
Einen Schönen Gruß,
Sigi
Reply to: