Not able to telnet into nas

Not able to telnet into nas

Postby Doppie » Tue Apr 12, 2016 11:48 am

I am trying to install the firmware on a new disk. I am using XP. I have switched off the firewall, even uninstalled the virusscan. Both computer and nas are on the same subnet. 192.168.1.xxx, ip-address for nas is set to 192.168.1.251. I have started the console and the nas is recognized. TFTP runs fine and executes some code. Then telnet pops up but after a little while the error "connection to ... timed out. Any idea? Otherwise is it possible to take out the disk and install it directly onto it?

Thanks in advance!
Doppie
 
Posts: 11
Joined: Thu Dec 03, 2015 5:39 am

Re: Not able to telnet into nas

Postby fvdw » Tue Apr 12, 2016 7:27 pm

TFTP runs fine and executes some code.


it should show the uploading process and finally mentioning starting kernel (in the u-boot console window)
Did you get that message ?

something like this (note this is an example your kernel name and size as well as Ip's will be different)
Code: Select all
Marvell>> tftpboot 0x800000 UIMAGE-26394-NWSP2CL-59
tftpboot 0x800000 UIMAGE-26394-NWSP2CL-59
Using egiga0 device
TFTP from server 192.168.1.147; our IP address is 192.168.1.197
Filename 'UIMAGE-26394-NWSP2CL-59'.
Load address: 0x800000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ##########################
done
Bytes transferred = 3123520 (2fa940 hex)

Marvell>> bootm 0x800000
bootm 0x800000
## Booting image at 00800000 ...
   Image Name:   Linux-2.6.39.4
   Created:      2012-12-23  21:59:32 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3123456 Bytes =  3 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK

Starting kernel ...
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Not able to telnet into nas

Postby Doppie » Wed Apr 13, 2016 7:13 am

Hi fvdw, thank you for your quick response.
I get the message you showed. It starts with "No lump receive" But it ends the same. The harddisk spins up, telnetwindow shows up and after a little while "connection to 192.168.1.251/telnet timed out". I have tried with a static address on my XP pc 192.168.1.253 and subnetmask 23 but still no connection. Any idea?
Doppie
 
Posts: 11
Joined: Thu Dec 03, 2015 5:39 am

Re: Not able to telnet into nas

Postby fvdw » Wed Apr 13, 2016 5:35 pm

It is not clear to me what you mean with subnet mask 23 :scratch

That the disk spin up is a good sign. It means the kernel loaded, which kernel did you load?

If you load the standalone kernel (kirkwood) the only thing I can think off is that your router doesn't allow to connect to 192.168.1.252 because of wrong subsetmask in the router and/or your pc

Use in the router and pc subset mask 255.255.255.0 to allow access to any ip 192.168.1.xxx in your lan
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Not able to telnet into nas

Postby Jocko » Wed Apr 13, 2016 5:54 pm

Do you mean you have two subnets like 192.168.0.xxx;192.68.1.xxx ?
23 subnet mask means you can handle hosts from 192.168.0.1 to 192.168.1.254 on your LAN
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Not able to telnet into nas

Postby Doppie » Thu Apr 14, 2016 9:53 am

I tried subnetmask /23 because the telnet programm states "connecting to 192.168.1.252/23". To rule out problems on my network I installed a telnet server on a linux pc and I can connect to it from my XP laptop. The image I try to load is UIMAGE-3142-NWSPCL-14. Still no luck. When I connect a USB serial device to the serial connection of the NWSP2 I am able to see the boot message. Is it possible to send the image through this way?
Doppie
 
Posts: 11
Joined: Thu Dec 03, 2015 5:39 am

Re: Not able to telnet into nas

Postby Jocko » Thu Apr 14, 2016 3:35 pm

Hi Doppie,

You misunderstand something :
- To get a telnet access, you must use only standalone kernel image (with Keyword 'standalone' in their filename).
- other kernel images must be used only with the action 'load an External kernel' if you have already installed our firmware image. Its goal is either to test a new kernel version or load a kernel from another source if kernel is corrupted on the disk.
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Not able to telnet into nas

Postby Doppie » Thu Apr 14, 2016 5:24 pm

Hi Jocko, thank you for your quick response. I selected the wrong image )-; . I have a network space vs 2 and now I have used UIMAGE-3142-KIRKWOOD-150-standalone. I get an error message cannot find firmware file on sda5. script will exit. Have I chosen the wrong image?
Doppie
 
Posts: 11
Joined: Thu Dec 03, 2015 5:39 am

Re: Not able to telnet into nas

Postby Jocko » Thu Apr 14, 2016 6:57 pm

Do you unpack all files from fvdw-sl console package ?

Otherwise try again and when you get the error message "Cannot find firmware file on sda5"

please post the output
Code: Select all
mount /dev/sda5 /sda5
ls -l /sda5
cat /sda5/installer.log
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Not able to telnet into nas

Postby Doppie » Thu Apr 14, 2016 7:33 pm

Hi Jocko, it failed see the log. I have used uimage-3142-kirkwood-150-standalone (5739kB). I now have used my Windows 10 pc.

Code: Select all
fvdw-sl-installer log
tftpd ip address 192.168.1.108
getting required programs from tftp server 192.168.1.108
Dialog installed
xterm installed
mke2fs-ext3 present
gdisk present
Start fvdw-sl firmware installer version 3.0.0

selected nas type nwsp2 platform kirkwood
selected disk /dev/sda
gpt support bootloader selected no
selected partion table type msdos
Deleting old msdos partiton table
partitions found before deleting ms-dos partition table = 5 2 1 \n
del = d\n5\nd\n2\nd\n1\nw\n\q\n\n
partitions found after delete ms-dos partition table = \n
deleting ms-dos partition succeeded\n
create new partiton table
create ms-dos partiton table
max cylinder 60801
ms-dos partiton scheme disk last cylinder 60800 (-1)

The number of cylinders for this disk is set to 60801.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
   (e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): Command action
   e   extended
   p   primary partition (1-4)
Partition number (1-4): First cylinder (1-60801, default 1): Last cylinder or +size or +sizeM or +sizeK (9-60801, default 60801):
Command (m for help): Command action
   e   extended
   p   primary partition (1-4)
Partition number (1-4): First cylinder (1-60801, default 1): Last cylinder or +size or +sizeM or +sizeK (73-60801, default 60801):
Command (m for help): Command action
   e   extended
   p   primary partition (1-4)
Partition number (1-4): First cylinder (1-60801, default 1): Last cylinder or +size or +sizeM or +sizeK (137-60801, default 60801):
Command (m for help): Partition number (1-4): Hex code (type L to list codes): Changed system type of partition 3 to 82 (Linux swap)

Command (m for help): Command action
   e   extended
   p   primary partition (1-4)
Selected partition 4
First cylinder (1-60801, default 1): Last cylinder or +size or +sizeM or +sizeK (201-60801, default 60801):
Command (m for help): First cylinder (201-60800, default 201): Last cylinder or +size or +sizeM or +sizeK (209-60800, default 60800):
Command (m for help): First cylinder (201-60800, default 201): Last cylinder or +size or +sizeM or +sizeK (321-60800, default 60800):
Command (m for help): First cylinder (201-60800, default 201): Last cylinder or +size or +sizeM or +sizeK (337-60800, default 60800):
Command (m for help): First cylinder (201-60800, default 201): Last cylinder or +size or +sizeM or +sizeK (409-60800, default 60800):
Command (m for help): The partition table has been altered.
Calling ioctl() to re-read partition table
creating ms-dos partiton table succeeded
format partition 5
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
52304 inodes, 208845 blocks
2088 blocks (1.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=213909504
7 block groups
32768 blocks per group, 32768 fragments per group
7472 inodes per group
Superblock backups stored on blocks:
        32768, 98304, 163840

Writing inode tables: done                           
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 22 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
formatting sda5 succeeded
writing kernel to partition 6
mounting sda 5 succeeded
getting kernel from tftp server
writing kernel to partition 6
9445+1 records in
9445+1 records out
4835944 bytes (4.6MB) copied, 0.402552 seconds, 11.5MB/s
writing kernel to partition 6 succeeded
Getting firmware image from tftp server
firmware disk image uploaded succesfully\n
Unpacking firmware image from archive
cannot find firmware file on sda5, extraction of archive must have failed
Doppie
 
Posts: 11
Joined: Thu Dec 03, 2015 5:39 am

Next

Return to Lacie Network Space vs2 and max version

Who is online

Users browsing this forum: No registered users and 3 guests