I/O error in filesystem ("sdb1") meta-data dev sdb1 block 0x54f839cff

After a reboot of the system, Suse cannot mount “sdb1”.

This messages comes from dmesg:
attempt to access beyond end of device
sdb1: rw=0, want=22808861952, limit=1334025547
I/O error in filesystem (“sdb1”) meta-data dev sdb1 block 0x54f839cff (“xfs_read_buf”) error 5 buf count 512
XFS: size check 2 failed

what can be wrong ?

Rgds,
Nordhuus

When you id not do any special actions (partitioning?) before the shutdown before this boot, I guess that the disk is gone.

I would suggest to make backups of all the other partitions on the same disk asap.

It was just a normal reboot. Nothing was done. It is just one partition on sdb. and it is11 TB.

When i type : parted /dev/sdb print
Disk geometry for /dev/sdb: 0kB - 12TB
Disk label type: msdos
Number Start End Size Type File system Flags
1 32kB 683GB 683GB primary xfs type=83
Information: Don’t forget to update /etc/fstab, if necessary.

System: Suse Linux 10.0
Kernel:2.6.16.53-0.16-smp x86_64
Hardware: Dell PE 2950 with 3 x DELL MD1000 enclosures.
RAID controller PERC 5 / E

Rgds,
Nordhuus

nordhuus wrote:
> After a reboot of the system, Suse cannot mount “sdb1”.
>
> This messages comes from dmesg:
> attempt to access beyond end of device
> sdb1: rw=0, want=22808861952, limit=1334025547
> I/O error in filesystem (“sdb1”) meta-data dev sdb1 block 0x54f839cff
> (“xfs_read_buf”) error 5 buf count 512
> XFS: size check 2 failed
>
> what can be wrong ?

hcvv wrote:
> When you id not do any special actions (partitioning?) before the
> shutdown before this boot, I guess that the disk is gone.
>
> I would suggest to make backups of all the other partitions on the
> same disk asap.

I think that is wise advice. I guess another possibility is an XFS bug
or some other minor corruption, so it might be worth asking about the
symptoms on the XFS list and running the repair tool. I’m not expert
enough to know the correct invocation, sorry. Details of the list is at

http://oss.sgi.com/mailman/listinfo/xfs

Cheers, Dave

When you want to show how the disk is partitioned, please use

fdisk -l /dev/sdb

And when you want to show this (or any other) computer text, please use CODE tags aound it: Posting in Code Tags - A Guide

You also could try to check/repair the file system with

fsck /dev/sdb1

But I doubt that this works when the partition itself is not correct.

EDIT:
I did not see dhj-novell’s advise, but trying to find out about XFS problems seems like a good advice to me.