[sclug] file system errors on SATA drive

[Darren Davison]

hi,

I recently started getting errors on a new (3 mth old) SATA drive...


Feb 14 20:59:26 hepburn kernel: [19843599.100000]
__journal_remove_journal_head: freeing b_committed_data
Feb 14 20:59:26 hepburn kernel: [19843599.100000]
__journal_remove_journal_head: freeing b_committed_data
Feb 14 20:59:36 hepburn kernel: [19843609.384000] kjournald starting.
Commit interval 5 seconds
Feb 14 20:59:36 hepburn kernel: [19843609.384000] EXT3-fs warning (device
sda1): ext3_clear_journal_err: Filesystem error recorded from previous
mount: IO failure
Feb 14 20:59:36 hepburn kernel: [19843609.384000] EXT3-fs warning (device
sda1): ext3_clear_journal_err: Marking fs in need of filesystem check.
Feb 14 20:59:36 hepburn kernel: [19843609.396000] EXT3-fs warning: mounting
fs with errors, running e2fsck is recommended
Feb 14 20:59:36 hepburn kernel: [19843609.396000] EXT3 FS on sda1, internal
journal
Feb 14 20:59:36 hepburn kernel: [19843609.396000] EXT3-fs: recovery
complete.
Feb 14 20:59:36 hepburn kernel: [19843609.396000] EXT3-fs: mounted
filesystem with ordered data mode.


If I umount it and remount it, it works fine (r/w) for a short while, then
the same errors occur and it gets marked as read-only.

Attempting to run e2fsck fails due to a bad superblock, and using any of the
other superblocks gives the same error:

root at hepburn:~# mke2fs -n /dev/sda
mke2fs 1.39 (29-May-2006)
/dev/sda is entire device, not just one partition!
Proceed anyway? (y,n) y
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
19546112 inodes, 39072726 blocks
1953636 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=41943040
1193 block groups
32768 blocks per group, 32768 fragments per group
16384 inodes per group
Superblock backups stored on blocks: 
        32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632,
		2654208, 4096000, 7962624, 11239424, 20480000, 23887872

root at hepburn:~# e2fsck -b 32768 /dev/sda
e2fsck 1.39 (29-May-2006)
e2fsck: Bad magic number in super-block while trying to open
/dev/sda

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>



Any idea what I need to do here?

Thanks!

-- 
Darren Davison
Public Key: 0xE855B3EA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.tmdg.co.uk/pipermail/sclug/attachments/20070215/7c5c007c/attachment.bin