Hi,
ich bekomme folgende Fehlermeldung bei einem Rechner:
Aug 25 11:40:37 clust01 kernel: ide_dmaproc: chipset supported ide_dma_timeout func only: 14
Aug 25 11:40:37 clust01 kernel: hda: status timeout: status=0xd0 { Busy }
Aug 25 11:40:37 clust01 kernel: hda: drive not ready for command
Aug 25 11:40:37 clust01 kernel: ide0: reset: success
Seit dem kann kann ich nichts mehr auf die Platte schreiben. Ich bekomme dann
clust01:/var/log# touch test
touch: creating `test': Read-only file system
Aber natürlich ist die Platte rw gemountet:
clust01:/# mount
/dev/hda3 on / type ext3 (rw,errors=remount-ro)
DMA hab ich erstmal ausgeschaltet.
Wenn's hilft:
clust01:/# hdparm -v -i /dev/hda
/dev/hda:
multcount = 0 (off)
I/O support = 0 (default 16-bit)
unmaskirq = 0 (off)
using_dma = 0 (off)
keepsettings = 0 (off)
nowerr = 0 (off)
readonly = 0 (off)
readahead = 8 (on)
geometry = 2482/255/63, sectors = 39876480, start = 0
Model=IC35L020AVVA07-0, FwRev=VA1OA52A, SerialNo=VNC106A1GAT41A
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=52
BuffType=DualPortCache, BuffSize=1863kB, MaxMultSect=16, MultSect=off
CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=39876480
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
AdvancedPM=yes: disabled (255) WriteCache=enabled
Drive Supports : ATA/ATAPI-5 T13 1321D revision 1 : ATA-2 ATA-3 ATA-4 ATA-5
busstate = 1 (on)
clust01:/# cat /proc/ide/via
----------VIA BusMastering IDE Configuration----------------
Driver Version: 3.35
South Bridge: VIA vt82c686b
Revision: ISA 0x40 IDE 0x6
Highest DMA rate: UDMA100
BM-DMA base: 0xdc00
PCI clock: 33.3MHz
Master Read Cycle IRDY: 0ws
Master Write Cycle IRDY: 0ws
BM IDE Status Register Read Retry: yes
Max DRDY Pulse Width: No limit
-----------------------Primary IDE-------Secondary IDE------
Read DMA FIFO flush: yes yes
End Sector FIFO flush: no no
Prefetch Buffer: no no
Post Write Buffer: no no
Enabled: yes yes
Simplex only: no no
Cable Type: 80w 40w
-------------------drive0----drive1----drive2----drive3-----
Transfer Mode: PIO PIO UDMA PIO
Address Setup: 30ns 120ns 30ns 120ns
Cmd Active: 90ns 90ns 90ns 90ns
Cmd Recovery: 30ns 30ns 30ns 30ns
Data Active: 90ns 330ns 90ns 330ns
Data Recovery: 30ns 270ns 30ns 270ns
Cycle Time: 120ns 600ns 60ns 600ns
Transfer Rate: 16.6MB/s 3.3MB/s 33.3MB/s 3.3MB/s
clust01:/# cat /proc/ide/hda/model
IC35L020AVVA07-0
clust01:/# cat /proc/ide/hda/settings
name value min max mode
---- ----- --- --- ----
acoustic 0 0 254 rw
address 0 0 2 rw
bios_cyl 2482 0 65535 rw
bios_head 255 0 255 rw
bios_sect 63 0 63 rw
breada_readahead 8 0 255 rw
bswap 0 0 1 r
current_speed 69 0 69 rw
failures 0 0 65535 rw
file_readahead 124 0 16384 rw
ide_scsi 0 0 1 rw
init_speed 12 0 69 rw
io_32bit 0 0 3 rw
keepsettings 0 0 1 rw
lun 0 0 7 rw
max_failures 1 0 65535 rw
max_kb_per_request 128 1 255 rw
multcount 0 0 16 rw
nice1 1 0 1 rw
nowerr 0 0 1 rw
number 0 0 3 rw
pio_mode write-only 0 255 w
slow 0 0 1 rw
unmaskirq 0 0 1 rw
using_dma 0 0 1 rw
wcache 0 0 1 rw[[/code]
chipset supported ide_dma_timeout func only
chipset supported ide_dma_timeout func only
Ich hab noch was entdeckt:
dmesg gibt folgendes aus:
EXT3-fs error (device ide0(3,3)) in ext3_orphan_del: Journal has aborted
ext3_reserve_inode_write: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device ide0(3,3)) in ext3_reserve_inode_write:
Journal has aborted
EXT3-fs error (device ide0(3,3)) in ext3_delete_inode: Journal has aborted
EXT3-fs error (device ide0(3,3)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,3)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,3)) in start_transaction: Journal has aborted
Sieht nciht gut aus, oder?
Grüße,
Hosi
dmesg gibt folgendes aus:
EXT3-fs error (device ide0(3,3)) in ext3_orphan_del: Journal has aborted
ext3_reserve_inode_write: aborting transaction: Journal has aborted in __ext3_journal_get_write_access<2>EXT3-fs error (device ide0(3,3)) in ext3_reserve_inode_write:
Journal has aborted
EXT3-fs error (device ide0(3,3)) in ext3_delete_inode: Journal has aborted
EXT3-fs error (device ide0(3,3)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,3)) in start_transaction: Journal has aborted
EXT3-fs error (device ide0(3,3)) in start_transaction: Journal has aborted
Sieht nciht gut aus, oder?
Grüße,
Hosi
- pdreker
- Beiträge: 8298
- Registriert: 29.07.2002 21:53:30
- Lizenz eigener Beiträge: MIT Lizenz
- Wohnort: Nürnberg
Kabel kontrollieren und das Checktool des Plattenherstellers 'mal drüberlaufen lassen...
Patrick
Patrick
Definitely not a bot...
Jabber: pdreker@debianforum.de
Jabber: pdreker@debianforum.de