Loading ...
Sorry, an error occurred while loading the content.
 

Re: [nslu2-linux] Re: NSLU2 RAM failure?

Expand Messages
  • Stephen Miller
    I think it might be a Flash CRC error being reported. It might be worth flashing a version that puts things in a bit different place to see if it works or
    Message 1 of 4 , Feb 20, 2010
      I think it might be a Flash CRC error being reported. It might be worth flashing a version that puts things in a bit different place to see if it works or fails differently.
      sdm485


      On 10-02-20 11:20 AM, reuter.rudolf wrote:
       



      --- In nslu2-linux@ yahoogroups. com, "reuter.rudolf" <reuterru@.. .> wrote:
      >
      > Hello,
      > On a second NSLU2 I installed SlugOS 4.8 beta. When I try to login, after entering the password PuTTY says: "Server unexpectedly closed network connection".
      > Next action was to connect a HyperTerminal to the serial link ttyS0 (115200 baud 8N1). The last lines in the boot log are:
      > INIT: Entering runlevel: 3
      > Data CRC cee07dfc != calculated CRC ae2900a4 for node at 0042f66c
      > Starting OpenBSD Secure Shell server: sshd
      > done.
      >
      > OpenEmbedded Linux LKG300DB0 ttyS0
      >
      > SlugOS 4.8-beta LKG300DB0 ttyS0
      >
      > LKG300DB0 login:
      >
      > A logread showed:
      > Feb 20 14:15:27 (none) user.warn kernel: Data CRC cee07dfc != calculated CRC ae2
      > 900a4 for node at 0042f66c (dez. 4.388.460, RAM)
      >
      > Hence, I assume it could be a RAM failure.
      >
      > Does anybody know how to do a RAM test?
      >
      > Regards, Rudolf
      > p.s. Going back to UNSLUng 6.10 did work, but I wanted to have SlugOS 4.8.
      >
      I found a RAM test program: memtester. I checked 21 MB of RAM: all OK

      How can I find that CRC error?

      Regards, Rudolf

      Console output of the RAM test:
      root@LKG300DB0: ~$ scp rudi@192.168. 17.28:/home/rudi/ Install/SlugOS/ memtester memtester
      The authenticity of host '192.168.17. 28 (192.168.17. 28)' can't be established.
      RSA key fingerprint is 6:2a:8b:49:3c: 60:7f:8b: d7:ef:03: 3c:bf:b0: 50:63.
      Are you sure you want to continue connecting (yes/no)? yes
      Warning: Permanently added '192.168.17. 28' (RSA) to the list of known hosts.
      rudi@192.168. 17.28's password:
      memtester 100% 10KB 10.4KB/s 00:00
      root@LKG300DB0: ~$ free
      total used free shared buffers
      Mem: 30376 9140 21236 0 0
      Swap: 0 0 0
      Total: 30376 9140 21236
      root@LKG300DB0: ~$ memtester 21 2
      memtester version 4.0.6 (32-bit)
      Copyright (C) 2006 Charles Cazabon.
      Licensed under the GNU General Public License version 2 (only).

      pagesize is 4096
      pagesizemask is 0xfffff000
      want 21MB (22020096 bytes)
      got 21MB (22020096 bytes), trying mlock ...locked.
      Loop 1/2:
      Stuck Address : ok
      Random Value : ok
      Compare XOR : ok
      Compare SUB : ok
      Compare MUL : ok
      Compare DIV : ok
      Compare OR : ok
      Compare AND : ok
      Sequential Increment: ok
      Solid Bits : ok
      Block Sequential : ok
      Checkerboard : ok
      Bit Spread : ok
      Bit Flip : ok
      Walking Ones : ok
      Walking Zeroes : ok


    • reuter.rudolf
      Hello Stephen, Thank you for giving help. That was exactely the cause of the error. In order to troubleshoot I put a terminal on /dev/ttyS0: HyperTerminal
      Message 2 of 4 , Mar 4, 2010
        Hello Stephen,

        Thank you for giving help. That was exactely the cause of the error.

        In order to troubleshoot I put a terminal on /dev/ttyS0:
        HyperTerminal 115200baud8N1 on ttyS0:
        root@LKG300DB0:~$ Data CRC cee07dfc != calculated CRC ae2900a4 for node at 0042f66c
        Data CRC cee07dfc != calculated CRC ae2900a4 for node at 0042f66c
        logread:
        Feb 20 14:15:27 (none) user.warn kernel: Data CRC cee07dfc != calculated CRC ae2
        900a4 for node at 0042f66c (dez. 4.388.460, RAM)
        $ turnup memstick -i /dev/sda1 -t ext3
        cpio: Read error at byte 126976 in file ./usr/sbin/sshd, padding with zeros
        NOTE: must be a defective NAND flash page
        Next I overwrote the defective "sshd" from an archive to the USB stick and it works. Sigh!

        Best regards,
        Rudolf

        --- In nslu2-linux@yahoogroups.com, Stephen Miller <steve@...> wrote:
        >
        > I think it might be a Flash CRC error being reported. It might be worth
        > flashing a version that puts things in a bit different place to see if
        > it works or fails differently.
        > sdm485
        >
        >
        > On 10-02-20 11:20 AM, reuter.rudolf wrote:
        > >
        > >
        > >
        > > --- In nslu2-linux@yahoogroups.com
        > > <mailto:nslu2-linux%40yahoogroups.com>, "reuter.rudolf" <reuterru@>
        > > wrote:
        > > >
        > > > Hello,
        > > > On a second NSLU2 I installed SlugOS 4.8 beta. When I try to login,
        > > after entering the password PuTTY says: "Server unexpectedly closed
        > > network connection".
        > > > Next action was to connect a HyperTerminal to the serial link ttyS0
        > > (115200 baud 8N1). The last lines in the boot log are:
        > > > INIT: Entering runlevel: 3
        > > > Data CRC cee07dfc != calculated CRC ae2900a4 for node at 0042f66c
        > > > Starting OpenBSD Secure Shell server: sshd
        > > > done.
        > > >
        > > > OpenEmbedded Linux LKG300DB0 ttyS0
        > > >
        > > > SlugOS 4.8-beta LKG300DB0 ttyS0
        > > >
        > > > LKG300DB0 login:
        > > >
        > > > A logread showed:
        > > > Feb 20 14:15:27 (none) user.warn kernel: Data CRC cee07dfc !=
        > > calculated CRC ae2
        > > > 900a4 for node at 0042f66c (dez. 4.388.460, RAM)
        > > >
        > > > Hence, I assume it could be a RAM failure.
        > > >
        > > > Does anybody know how to do a RAM test?
        > > >
        > > > Regards, Rudolf
        > > > p.s. Going back to UNSLUng 6.10 did work, but I wanted to have
        > > SlugOS 4.8.
        > > >
        > > I found a RAM test program: memtester. I checked 21 MB of RAM: all OK
        > >
        > > How can I find that CRC error?
        > >
        > > Regards, Rudolf
        > >
        > > Console output of the RAM test:
        > > root@LKG300DB0:~$ scp rudi@...
        > > <mailto:rudi%40192.168.17.28>:/home/rudi/Install/SlugOS/memtester
        > > memtester
        > > The authenticity of host '192.168.17.28 (192.168.17.28)' can't be
        > > established.
        > > RSA key fingerprint is 6:2a:8b:49:3c:60:7f:8b:d7:ef:03:3c:bf:b0:50:63.
        > > Are you sure you want to continue connecting (yes/no)? yes
        > > Warning: Permanently added '192.168.17.28' (RSA) to the list of known
        > > hosts.
        > > rudi@... <mailto:rudi%40192.168.17.28>'s password:
        > > memtester 100% 10KB 10.4KB/s 00:00
        > > root@LKG300DB0:~$ free
        > > total used free shared buffers
        > > Mem: 30376 9140 21236 0 0
        > > Swap: 0 0 0
        > > Total: 30376 9140 21236
        > > root@LKG300DB0:~$ memtester 21 2
        > > memtester version 4.0.6 (32-bit)
        > > Copyright (C) 2006 Charles Cazabon.
        > > Licensed under the GNU General Public License version 2 (only).
        > >
        > > pagesize is 4096
        > > pagesizemask is 0xfffff000
        > > want 21MB (22020096 bytes)
        > > got 21MB (22020096 bytes), trying mlock ...locked.
        > > Loop 1/2:
        > > Stuck Address : ok
        > > Random Value : ok
        > > Compare XOR : ok
        > > Compare SUB : ok
        > > Compare MUL : ok
        > > Compare DIV : ok
        > > Compare OR : ok
        > > Compare AND : ok
        > > Sequential Increment: ok
        > > Solid Bits : ok
        > > Block Sequential : ok
        > > Checkerboard : ok
        > > Bit Spread : ok
        > > Bit Flip : ok
        > > Walking Ones : ok
        > > Walking Zeroes : ok
        > >
        > >
        >
      Your message has been successfully submitted and would be delivered to recipients shortly.