Hi,
since a couple of days I've got these messages in my logs, is a physical
problem with the disk?

Apr 13 06:25:12 linux2 kernel: Directory sread (sector 0x20) failed
Apr 13 06:25:12 linux2 kernel: attempt to access beyond end of device
Apr 13 06:25:12 linux2 kernel: 02:00: rw=0, want=16, limit=4


Thanks,
Luca

--
Luca Ferrari,
fluca1978 [at] virgilio.it
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Luca

Which type of disk? Raid? Which filesystem? What says a file system check
(fsck)?
Can you do a dd if=<your partition> of=/dev/null with the same log?
If not, looks like the filesystem is bad.
> since a couple of days I've got these messages in my logs, is a physical
> problem with the disk?
>
> Apr 13 06:25:12 linux2 kernel: Directory sread (sector 0x20) failed
> Apr 13 06:25:12 linux2 kernel: attempt to access beyond end of device
> Apr 13 06:25:12 linux2 kernel: 02:00: rw=0, want=16, limit=4

--
Tom

LINUX user since kernel 0.99.x 1994.
RPM Alpha packages at http://alpha.steudten.com/packages
Want to know what S.u.S.E 1995 cdrom-set contains?


-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

On Tuesday 13 April 2004 12:41 Thomas Steudten's cat walking on the keyboard
wrote:

> Luca
>
> Which type of disk? Raid? Which filesystem? What says a file system check
> (fsck)?
> Can you do a dd if=<your partition> of=/dev/null with the same log?
> If not, looks like the filesystem is bad.
>

It is a IDE disk, without software raid, formatted as ext2. Since it is the /
partition I cannot run fsck immediately to tell you what says, I need to stop
the machine.

Luca


--
Luca Ferrari,
fluca1978 [at] virgilio.it
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Try fsck.ext2 (or fsck) with -fvn <your root device eg /dev/hda1>.
-n tests in read-only mode.
> It is a IDE disk, without software raid, formatted as ext2. Since it is the /
> partition I cannot run fsck immediately to tell you what says, I need to stop
> the machine.


--
Tom

LINUX user since kernel 0.99.x 1994.
RPM Alpha packages at http://alpha.steudten.com/packages
Want to know what S.u.S.E 1995 cdrom-set contains?


-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

On Tuesday 13 April 2004 13:20 Thomas Steudten's cat walking on the keyboard
wrote:

> Try fsck.ext2 (or fsck) with -fvn <your root device eg /dev/hda1>.
> -n tests in read-only mode.
>

Ok, here there's the result:

fsck 1.27 (8-Mar-2002)
e2fsck 1.27 (8-Mar-2002)
Warning! /dev/hda1 is mounted.
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

30 inodes used (1%)
1 non-contiguous inodes (3.3%)
# of inodes with ind/dind/tind blocks: 10/6/0
6937 blocks used (86%)
0 bad blocks
0 large files

18 regular files
2 directories
0 character device files
0 block device files
0 fifos
0 links
1 symbolic links (1 fast symbolic links)
0 sockets
--------
21 files

it seems correct, isn't it? I've tried also to dd to /dev/null and it worked
well:
16002+0 records in
16002+0 records out
8193024 bytes transferred in 0.454885 seconds (18011202 bytes/sec)

any idea?
Thanks,
Luca



--
Luca Ferrari,
fluca1978 [at] virgilio.it
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

Humm, is it possible, that the device was a floppy?
ls -l /dev/fd0* or cat /proc/devices show you, that
the block device 2:0 is the floppy device.
Check this first.
>>Try fsck.ext2 (or fsck) with -fvn <your root device eg /dev/hda1>.
>>-n tests in read-only mode.
>>
>
>
> Ok, here there's the result:
>
> fsck 1.27 (8-Mar-2002)
> e2fsck 1.27 (8-Mar-2002)
> Warning! /dev/hda1 is mounted.
> 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
>
> 30 inodes used (1%)
> 1 non-contiguous inodes (3.3%)
> # of inodes with ind/dind/tind blocks: 10/6/0
> 6937 blocks used (86%)
> 0 bad blocks
> 0 large files
>
> 18 regular files
> 2 directories
> 0 character device files
> 0 block device files
> 0 fifos
> 0 links
> 1 symbolic links (1 fast symbolic links)
> 0 sockets
> --------
> 21 files
>
> it seems correct, isn't it? I've tried also to dd to /dev/null and it worked
> well:
> 16002+0 records in
> 16002+0 records out
> 8193024 bytes transferred in 0.454885 seconds (18011202 bytes/sec)
>
> any idea?
> Thanks,
> Luca
>
>
>

--
Tom

LINUX user since kernel 0.99.x 1994.
RPM Alpha packages at http://alpha.steudten.com/packages
Want to know what S.u.S.E 1995 cdrom-set contains?


-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html

On Tuesday 13 April 2004 14:44 Thomas Steudten's cat walking on the keyboard
wrote:

> Humm, is it possible, that the device was a floppy?
> ls -l /dev/fd0* or cat /proc/devices show you, that
> the block device 2:0 is the floppy device.
> Check this first.

Maybe you're right! I've found that /dev/fd0 was mounted, now I unmounted it
and I will check the logs.
Thanks,
Luca


--
Luca Ferrari,
fluca1978 [at] virgilio.it
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo [at] vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html