Re: e2fsck /dev/md0 issues
On Sun, 2008-12-21 at 05:42 +0100, M.Lewis wrote:
>
> I having an issue with my RAID array. I get some errors on boot, but the
> boot process is going beyond them and mounting the drive anyhow. So far
> as I can tell, all the data is present and readable. I would like to
> resolve these errors though. I'm not sure if it matters, but LVM is not
> installed on /dev/md0.
>
> I've tried all the possible (I think) combinations of 'e2fsck -b xxxxx
> /dev/md0' with no luck at all. Google searches have not yet produced
> anything that has seemed to help.
>
> rattler:~# e2fsck /dev/md0
> e2fsck 1.41.3 (12-Oct-2008)
> The filesystem size (according to the superblock) is 244190000 blocks
> The physical size of the device is 244189984 blocks
> Either the superblock or the partition table is likely to be corrupt!
> Abort<y>? no
>
> /dev/md0 contains a file system with errors, check forced.
> Pass 1: Checking inodes, blocks, and sizes
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
> /dev/md0: 430478/61054976 files (0.6% non-contiguous),
> 81536022/244190000 blocks
> rattler:~#
>
> Even if I abort the above check, the error is still present.
>
> Thanks,
> M
> --
Better use smart control (smartctl or smartd) to check the disks.
If there is an error logged, just replace the disk.
Best,
Rob
Reply to: