Hello Mike,
The problem is solved. Read further:
1. $ turnup memstick -i /dev/sda1 -t ext3
Message: cpio: Read error at byte 126976 in file ./usr/sbin/sshd, padding with zeros
Means: a NAND flash page was defect.
2. $ scp rudi@192.168.
I copied a good version of "sshd" to /root (in flash ROM).
3. $ mount -t ext3 /dev/sda1 /media/sda1
$ cp sshd /media/sda1/
$ reboot
repaired "sshd" on memstick works - Problem was solved.
4. I know that this was possible only, because I had a serial link via ttyS0. Do you see any possibility to fix that via network?
Thanks for your help.
Best Regards, Rudolf
--- In nslu2-linux@
> --- In nslu2-linux@
> >
> > reuter.rudolf wrote:
> > > Hello,
> > > I have already setup a NSLU2 working with SlugOS 4.8 beta. Now I wanted to setup a second NSLU2 with SlugOS 4.8 beta. I did so with upslug2.
> > >
> > > My problem is that I can not login as root (password opeNSLUg).
> > > According to the PuTTY log file, the password was accepted, then a session should be opened, but I got the message "Server unexpectedly closed network connection".
> > >
> > > I flashed the NSLU2 3 times with the same file and got always the same behaviour.
> > >
> > > I have searched the mail list and googled, but no hint to this problem.
> > >
> > > Now I need help from the group, please.
> > >
> > > Regards, Rudolf
> > >
> >
> > Oops - I'm going backwards through my email backlog. Based on the log
> > below, you have the correct password and are logged in. Perhaps that
> > CRC error is more problematic than they usually are -- would depend on
> > what data was there.
> >
> > -Mike (mwester)
>
> Hello Mike,
> Thank you very much for taking care of my problem.
> I connected a Hyperterminal to the serial port ttyS0. So I could see a CRC error:
> Data CRC cee07dfc != calculated CRC ae2900a4 for node at 0042f66c
> Just now I came to the conclusion, that it could come from the jffs2 file system and maybe the NAND flash.
>
> But how to fix it?
>
> uNSLUng 6.10 did work, but not SlugOS 4.8. I flashed it now 4 times, with no success.
> The reason I am using SlugOS 4.8 is, that I have a driver problem in SlugOS 5.3, which I could not solve. Under SlugOS 4.8 every thing works fine since 10 month. Then I wanted to upgrade to SlugOS 5.3 on a second NSLU2, but failed.
>
> Best regards, Rudolf
> p.s. I started another post "NSLU2 RAM failure?" after seeing that CRC failure.
>
> >
> > > PuTTY log shortened:
> > > =~=~=~=~=~=~
> > > Event Log: Writing new session log (SSH raw data mode) to file: putty.log
> > > Event Log: Looking up host "192.168.17.
> > > Event Log: Connecting to 192.168.17.81 port 22
> > > Event Log: Server version: SSH-2.0-OpenSSH_
> > > Event Log: We claim version: SSH-2.0-PuTTY_
> > > Outgoing packet type 20 / 0x14 (SSH2_MSG_KEXINIT)
> > > Event Log: Using SSH protocol version 2
> > > Event Log: Doing Diffie-Hellman group exchange
> > > Outgoing packet type 30 / 0x1e (SSH2_MSG_KEX_
> > > Incoming packet type 31 / 0x1f (SSH2_MSG_KEX_
> > > Event Log: Doing Diffie-Hellman key exchange with hash SHA-256
> > > Outgoing packet type 32 / 0x20 (SSH2_MSG_KEX_
> > > Incoming packet type 33 / 0x21 (SSH2_MSG_KEX_
> > > Event Log: Host key fingerprint is:
> > > Event Log: ssh-rsa 2048 12:7f:25:c1:
> > > Outgoing packet type 21 / 0x15 (SSH2_MSG_NEWKEYS)
> > > Event Log: Initialised AES-256 SDCTR client->server encryption
> > > Event Log: Initialised HMAC-SHA1 client->server MAC algorithm
> > > Outgoing raw data
> > > Incoming packet type 21 / 0x15 (SSH2_MSG_NEWKEYS)
> > > Event Log: Initialised AES-256 SDCTR server->client encryption
> > > Event Log: Initialised HMAC-SHA1 server->client MAC algorithm
> > > Outgoing packet type 5 / 0x05 (SSH2_MSG_SERVICE_
> > > 00000000 00 00 00 0c 73 73 68 2d 75 73 65 72 61 75 74 68 ....ssh-userauth
> > > Incoming packet type 6 / 0x06 (SSH2_MSG_SERVICE_
> > > 00000000 00 00 00 0c 73 73 68 2d 75 73 65 72 61 75 74 68 ....ssh-userauth
> > > Outgoing packet type 50 / 0x32 (SSH2_MSG_USERAUTH_
> > > 00000000 00 00 00 04 72 6f 6f 74 00 00 00 0e 73 73 68 2d ....root....
> > > 00000010 63 6f 6e 6e 65 63 74 69 6f 6e 00 00 00 04 6e 6f connection..
> > > 00000020 6e 65 ne
> > > Incoming packet type 51 / 0x33 (SSH2_MSG_USERAUTH_
> > > 00000000 00 00 00 12 70 75 62 6c 69 63 6b 65 79 2c 70 61 ....publickey,
> > > 00000010 73 73 77 6f 72 64 00 ssword.
> > > Outgoing packet type 50 / 0x32 (SSH2_MSG_USERAUTH_
> > > 00000000 00 00 00 04 72 6f 6f 74 00 00 00 0e 73 73 68 2d ....root....
> > > 00000010 63 6f 6e 6e 65 63 74 69 6f 6e 00 00 00 08 70 61 connection..
> > > 00000020 73 73 77 6f 72 64 00 XX XX XX XX XX XX XX XX XX ssword.XXXXXXXXX
> > > 00000030 XX XX XX XXX
> > > Outgoing packet type 2 / 0x02 (SSH2_MSG_IGNORE)
> > > Event Log: Sent password
> > > Incoming packet type 52 / 0x34 (SSH2_MSG_USERAUTH_
> > > Event Log: Access granted
> > > Outgoing packet type 90 / 0x5a (SSH2_MSG_CHANNEL_
> > > 00000000 00 00 00 07 73 65 73 73 69 6f 6e 00 00 01 00 00 ....session.
> > > 00000010 00 40 00 00 00 40 00 .@...@.
> > > Outgoing raw data
> > > 00000000 92 a2 ca 83 14 1e 44 f5 a1 ef 30 e6 f3 8e c5 5b ......D...0.
> > > 00000010 5c 60 e5 cb 97 5d 41 76 e5 ac c4 77 86 d6 69 72 \`...]Av...w.
> > > 00000020 72 9e 70 9e af 67 6c fa c6 5b 0c e0 0d 88 61 19 r.p..gl..[..
> > > 00000030 87 04 f1 68 03 aa 0a 9e d8 16 26 f8 c1 17 da 37 ...h......&.
> > > 00000040 5b 4e c0 f2 [N..
> > > Event Log: Server unexpectedly closed network connection
> > >
> > > missing ------------
> > > Incoming packet type 91 / 0x5b (SSH2_MSG_CHANNEL_
> > > Event Log: Opened channel for session
> > > Outgoing packet type 98 / 0x62 (SSH2_MSG_CHANNEL_
> > > 00000000 00 00 00 00 00 00 00 07 70 74 79 2d 72 65 71 01 ........pty-
> > > 00000010 00 00 00 05 78 74 65 72 6d 00 00 00 60 00 00 00 ....xterm...
> > > 00000020 20 00 00 00 00 00 00 00 00 00 00 00 10 03 00 00 ............
> > > 00000030 00 7f 80 00 00 96 00 81 00 00 96 00 00 ............
> > > Incoming raw data .\.6
> > > Incoming packet type 99 / 0x63 (SSH2_MSG_CHANNEL_
> > > Event Log: Allocated pty (ospeed 38400bps, ispeed 38400bps)
> > > Outgoing packet type 98 / 0x62 (SSH2_MSG_CHANNEL_
> > > 00000000 00 00 00 00 00 00 00 05 73 68 65 6c 6c 01 ........shell.
> > > Incoming packet type 93 / 0x5d (SSH2_MSG_CHANNEL_
> > > Incoming packet type 99 / 0x63 (SSH2_MSG_CHANNEL_
> > > Event Log: Started a shell/command
> > > Incoming packet type 94 / 0x5e (SSH2_MSG_CHANNEL_
> > > 00000000 00 00 01 00 00 00 00 32 4c 61 73 74 20 6c 6f 67 .......2Last log
> > > 00000010 69 6e 3a 20 53 75 6e 20 46 65 62 20 31 34 20 31 in: Sun Feb 14 1
> > > 00000020 34 3a 30 30 3a 34 35 20 32 30 31 30 20 66 72 6f 4:00:45 2010 fro
> > > 00000030 6d 20 72 75 64 69 32 0d 0d 0a m rudi2...
> > > Incoming packet type 94 / 0x5e (SSH2_MSG_CHANNEL_
> > > ... now waitung for shell input.
>
No comments:
Post a Comment