no wiec:
Aug 27 00:02:29 serwer kernel: EXT3-fs error (device ide0(3,65)): ext3_get_inode_loc: unable to read inode block - i
Aug 27 00:02:30 serwer kernel: EXT3-fs error (device ide0(3,65)): ext3_get_inode_loc: unable to read inode block - i
Aug 27 00:02:30 serwer kernel: EXT3-fs error (device ide0(3,65)): ext3_get_inode_loc: unable to read inode block - i
Aug 27 00:05:12 serwer kernel: EXT3-fs error (device ide0(3,65)) in ext3_reserve_inode_write: IO failure
Aug 27 00:05:12 serwer kernel: EXT3-fs error (device ide0(3,65)) in ext3_reserve_inode_write: IO failure
Aug 27 00:25:31 serwer kernel: journal_bmap: journal block not found at offset 2060 on ide0(3,65)
Aug 27 00:25:31 serwer kernel: Aborting journal on device ide0(3,65).
Aug 27 00:25:31 serwer kernel: ext3_abort called.
Aug 27 00:25:31 serwer kernel: EXT3-fs abort (device ide0(3,65)): ext3_journal_start: Detected aborted journal
Aug 27 00:25:31 serwer kernel: Remounting filesystem read-only
Aug 27 09:51:46 serwer kernel: EXT3-fs error (device ide0(3,65)): ext3_readdir: directory #180225 contains a hole at
Aug 27 09:51:47 serwer kernel: EXT3-fs error (device ide0(3,65)): ext3_readdir: directory #180225 contains a hole at
Aug 27 09:52:52 serwer kernel: EXT3-fs error (device ide0(3,65)): ext3_readdir: directory #32769 contains a hole at
Aug 27 09:52:59 serwer kernel: EXT3-fs error (device ide0(3,65)): ext3_readdir: directory #2 contains a hole at offs
Aug 27 09:53:32 serwer kernel: EXT3-fs error (device ide0(3,65)): ext3_readdir: directory #2 contains a hole at offs
Aug 27 09:53:52 serwer last message repeated 3 times
Aug 27 09:54:02 serwer kernel: EXT3-fs error (device ide0(3,65)): ext3_readdir: directory #32769 contains a hole at
i to jest uszkodzony dysk ;]
ja to robie tak:
odpalam sambe i kopiuje na dysk dane jak sie zapelni caly bez bledow to znaczy ze jest ok jak sie wywala to sie wqu... ;]
te bledy ktore widzisz sa na dysku 40GB gdy go ogranicze zwora do 32GB to nie ma bledow ;]