Lost Dog
09-18-2004, 01:24 PM
My kernel log is filling up with things like this:
Sep 18 10:50:19 (none) kernel: EXT2-fs error (device ide0(3,9)): ext2_free_blocks: Freeing blocks not in datazone - block = 1129270597, count = 1
and
Sep 18 10:50:19 (none) kernel: attempt to access beyond end of device
Sep 18 10:50:19 (none) kernel: 03:09: rw=0, want=154482746, limit=131072
Sep 18 10:50:19 (none) kernel: EXT2-fs error (device ide0(3,9)): ext2_free_branches: Read failure, inode=4127, block=154482745
When I run e2fsck, /dev/hda4 comes up clean but /dev/hda9 usually gives me page after page of messages about illegal blocks and clearing them out. It finds duplicate bad blocks and other issues.
Once it's done I can run e2fsck again and it says there are no problems... If there were bad sectors wouldn't they be found each time it is run?
I should probably add that this is a HDVR2 running a manually monted 4.0. The hard drive is a Samsung spinpoint 120gig.
Sep 18 10:50:19 (none) kernel: EXT2-fs error (device ide0(3,9)): ext2_free_blocks: Freeing blocks not in datazone - block = 1129270597, count = 1
and
Sep 18 10:50:19 (none) kernel: attempt to access beyond end of device
Sep 18 10:50:19 (none) kernel: 03:09: rw=0, want=154482746, limit=131072
Sep 18 10:50:19 (none) kernel: EXT2-fs error (device ide0(3,9)): ext2_free_branches: Read failure, inode=4127, block=154482745
When I run e2fsck, /dev/hda4 comes up clean but /dev/hda9 usually gives me page after page of messages about illegal blocks and clearing them out. It finds duplicate bad blocks and other issues.
Once it's done I can run e2fsck again and it says there are no problems... If there were bad sectors wouldn't they be found each time it is run?
I should probably add that this is a HDVR2 running a manually monted 4.0. The hard drive is a Samsung spinpoint 120gig.