Кто виноват - диск?
hi all
Вопрос, наверное, к "железячникам".
Вставил диск. При работе через некоторое время начинаются проблемы.
Господа взгляните на log. Что это значит и кто виноват?
Сей диск, проверен вдоль и поперек badblocks-ом, ami диагностиком, ну и health
диагностиком от производителя диска. Все рапортуют - OK.
--
Artem Zolochevskiy
Kaliningrad
Russia
ICQ: 148168281
09:46:40 debian kernel: hdf: status error: status=0x4e { DriveReady DataRequest CorrectedError Index }
Apr 11 09:46:40 debian kernel:
Apr 11 09:46:40 debian kernel: hdf: drive not ready for command
Apr 11 09:47:00 debian kernel: hdf: dma_timer_expiry: dma status == 0x40
Apr 11 09:47:00 debian kernel: hdf: DMA timeout retry
Apr 11 09:47:00 debian kernel: hdf: timeout waiting for DMA
Apr 11 09:47:00 debian kernel: hdf: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Apr 11 09:47:00 debian kernel:
Apr 11 09:47:00 debian kernel: hdf: drive not ready for command
Apr 11 09:49:03 debian kernel: via_audio: ignoring drain playback error -11
Apr 11 09:51:42 debian kernel: hdf: dma_intr: status=0x06 { CorrectedError Index }
Apr 11 09:51:42 debian kernel:
Apr 11 09:51:42 debian kernel: hdf: status error: status=0x06 { CorrectedError Index }
:
09:51:42 debian kernel:
Apr 11 09:51:42 debian kernel: hdf: drive not ready for command
Apr 11 09:52:12 debian kernel: hdf: lost interrupt
Apr 11 09:52:12 debian kernel: hdf: recal_intr: status=0x10 { SeekComplete }
Apr 11 09:52:12 debian kernel:
Apr 11 09:52:12 debian kernel: hdf: status error: status=0x10 { SeekComplete }
Apr 11 09:52:12 debian kernel:
Apr 11 09:52:12 debian kernel: hdf: DMA disabled
Apr 11 09:52:12 debian kernel: hdf: drive not ready for command
Apr 11 09:52:12 debian kernel: ide2: reset: master: ECC circuitry error
Apr 11 09:52:15 debian kernel: lp0: ECP mode
Apr 11 09:53:25 debian kernel: hdf: lost interrupt
Apr 11 09:53:25 debian kernel: hdf: task_out_intr: status=0x58 { DriveReady SeekComplete DataRequest }
Apr 11 09:53:25 debian kernel:
Apr 11 09:53:25 debian kernel: hdf: status error: status=0x58 { DriveReady SeekComplete DataRequest }
Apr 11 09:53:25 debian kernel:
Apr 11 09:53:25 debian kernel: hdf: drive not ready for command
Apr 11 09:53:25 debian kernel: EXT3-fs error (device hdf1): ext3_add_entry: bad entry in directory #6652054: rec_len %% 4 !=
0 - offset=0, inode=1869815923, rec_len=25965, name_len=98
Apr 11 09:53:25 debian kernel: Aborting journal on device hdf1.
Apr 11 09:53:25 debian kernel: ext3_abort called.
Apr 11 09:53:25 debian kernel: EXT3-fs abort (device hdf1): ext3_journal_start: Detected aborted journal
Apr 11 09:53:25 debian kernel: Remounting filesystem read-only
Apr 11 09:53:25 debian kernel: EXT3-fs error (device hdf1) in start_transaction: Journal has aborted
Apr 11 09:53:25 debian kernel: EXT3-fs error (device hdf1) in ext3_create: IO failure
Apr 11 09:53:25 debian kernel: ext3_reserve_inode_write: aborting transaction: Journal has aborted in __ext3_journal_get_wri
te_access<2>EXT3-fs error (device hdf1) in ext3_reserve_inode_write: Journal has aborted
Apr 11 09:53:25 debian kernel: ext3_reserve_inode_write: aborting transaction: Journal has aborted in __ext3_journal_get_wri
te_access<2>EXT3-fs error (device hdf1) in ext3_reserve_inode_write: Journal has aborted
Apr 11 09:53:25 debian kernel: EXT3-fs error (device hdf1) in ext3_create: Journal has aborted
Apr 11 09:53:25 debian kernel: EXT3-fs error (device hdf1) in start_transaction: Journal has aborted
Reply to: