Re: In which device i have to check for bad blocks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



That doesn't sound like software at all. Check your fans/heatsinks/hardware.


Pavlos Parissis wrote:

On 10 Dec 2002 23:16:19 +0100 Shark <tester0@xxxxxxxx> wrote:


El mar, 10-12-2002 a las 21:07, Pavlos Parissis escribiσ:
> Hello,
> When we have ataraid enabled from the kernel and we use
> /dev/ataraid/d0pN for RAID 1 and kernel see also the 2 disks as
> dev/hde and /dev/hdh, in which device
> i have to check for badblocks.

/dev/ataraid/d0pN

(this will repair both hde and hdh)


I think that the fsck -c don't fix badblocks but reports them, i don't know
any kind of software which can fixs bad blocks.
Today i tried fsck -c to /dev/ataraid/d0pN and to /dev/hdg and /dev/hde
and it didn't report any bad blocks.
As a result i have to search in other place to find the cause of my
problems.
Why did i do fsck today?Because i went to the server an it was frozen!!!
I saw in the logs that

Dec 10 20:19:25 mainserver kernel: Unable to handle
kernel NULL pointer dereference at virtual address 0000000c
Dec 10 20:19:25 mainserver kernel: printing eip:
Dec 10 20:19:25 mainserver kernel: c01297d0
Dec 10 20:19:25 mainserver kernel: *pde = 00000000
Dec 10 20:19:25 mainserver kernel: Oops: 0000
Dec 10 20:19:25 mainserver kernel: CPU: 0
Dec 10 20:19:25 mainserver kernel: EIP: 0010:[<c01297d0>] Not tainted
Dec 10 20:19:25 mainserver kernel: EFLAGS: 00010046
Dec 10 20:19:25 mainserver kernel: eax: 01600000 ebx: 40000000 ecx:
00000000 edx: 00000000
Dec 10 20:19:25 mainserver kernel: esi: 00000000 edi: 00000206 ebp: d1a106c0 esp: df7f1e64
Dec 10 20:19:25 mainserver kernel: ds: 0018 es: 0018 ss: 0018
Dec 10 20:19:25 mainserver kernel: Process kjournald pid: 131,
stackpage=df7f1000)
Dec 10 20:19:25 mainserver kernel: Stack: c8e2dbd0
c55ffd20 c535c3c0 c4ccb000 c0160743 40000000
df7f40e4 00000000 Dec 10 20:19:25 mainserver kernel: 00000fac
c69b9054 00000000 da4807b0 c535c3c0 c60b9300
00001896 c01c96fb Dec 10 20:19:25 mainserver kernel: 00000000
c02d9370 4a494847 c600e540 c600e5c0 c600e7c0
c600e4c0 c600e3c0 Dec 10 20:19:25 mainserver kernel: Call Trace: [<c0160743>] [<c01c96fb>]
[<c0162ac3>] [<c0162920>]
[<c0106ff6>]
Dec 10 20:19:25 mainserver kernel: [<c0162940>]
Dec 10 20:19:25 mainserver kernel: Dec 10 20:19:25 mainserver kernel: Code: 2b 59 0c 89
d8 f7 76 18 89 c3 8b 41 14 89 44 99 18 89 59 14


And when I tried to compile kernel 2.4.20 i got 3 segmentation faults and
after
3 efforts i managed to start the compile and server restarted by it
self!!!!!!!!
Afte the reset i managed to compile the kernel without any problems.
I reset the server and now its up with kernel 2.4.20  6:49 hours.

shall i blame the DDR chip set for these???
or there is a problem with the driver for the controller?

PAvlos











[Index of Archives]     [Linux RAID]     [Linux Device Mapper]     [Linux IDE]     [Linux SCSI]     [Kernel]     [Linux Books]     [Linux Admin]     [GFS]     [RPM]     [Yosemite Campgrounds]     [AMD 64]

  Powered by Linux