Time out with telnet ? any help

[Cricrou59]

Hi Jocko and thanks for your answer but everything doing fine till message starting kernel and then Nothing happend, the led of the nas blinking red ? please any solution to finish ?

[Jocko]

Hi

everything doing fine till message starting kernel and then Nothing happend

That means the boot loader failed to load the kernel.
So repeat all the previous step but not bootm.

Then do this command

Code: Select all

 printenv

and please to post the related output(without any output is hard to help you)

after you can use bootm to see what happens

[Cricrou59]

Ok Jocko Thanks, I'm trying yet with another disk, after that I will post the report.

[Cricrou59]

Here the report in pj

[Cricrou59]

Re, I've tried to install the firmware normaly with 2 different disks one by one in the left of the nas (viewed on back side) but the issue is the same. When I'm accessing to fvdw-sl-programs it's aborting because the sda is not finded.
See the report here down :
[size=85]There was an error detecting device sda, this device is required to write the image.
Writer will exit
root@(none):/ # cat writer.log
fvdw-sl-image-writer log
tftpd ip address 192.168.0.24
getting required programs from tftp server 192.168.0.24
Dialog installed
xterm installed
Start fvdw-sl image writer version 3.1.0

selected nas type 5big1 platform orion busybox=nok
install busybox1, required for the selected nas
install busybox1 ok
lrwxrwxrwx 1 root root 8 Jan 1 00:01 tar -> busybox1
There was an error detecting device sda, this device is required to install firmware. Writer will exit
root@(none):/ #

[Jocko]

Hi

So it seems you managed to get a telnet access :thumbup

Then from telnet window, please to post these output

Code: Select all

cat /proc/partitions
fdisk -l /dev/sda
gdisk -l /dev/sda

It seems the disk is not detected, so this time try to get a U-boot console and from the nc window (marvell prompt), please to post the output

Code: Select all

ide reset

[Cricrou59]

Hi
Here the post

(none) login: root
Password:
root@(none):/ # cat /proc/partitions
major minor #blocks name

root@(none):/ # fdisk -1 /dev/sda
fdisk: invalid option -- 1
BusyBox v1.21.0 (2016-02-01 22:45:24 CET) multi-call binary.

Usage: fdisk [-ul] [-C CYLINDERS] [-H HEADS] [-S SECTORS] [-b SSZ] DISK

Change partition table

-u Start and End are in sectors (instead of cylinders)
-l Show partition table for each DISK, then exit
-b 2048 (for certain MO disks) use 2048-byte sectors
-C CYLINDERS Set number of cylinders/heads/sectors
-H HEADS
-S SECTORS

root@(none):/ # gdisk -1 /dev/sda
-sh: gdisk: not found
root@(none):/ #

[Cricrou59]

Here the post of nc windows for IDE RESET

provided by fvdw
waiting for u-boot..
starting u-boot net console click on window and press enter


Marvell>> ide reset
ide reset

Reset IDE:
Marvell Serial ATA Adapter
Found adapter at bus 1, device 7 ... Scanning channels
[0 4]: failed to perform ATA Identify command
Failed initializing storage deivce connected to SATA channel 4

Marvell>>

[Jocko]

Thank you for this last feedback

So we understand better what is the issue. It seems there is an hardware issue on the ATA port with your nas.

Before trying to install fvdw-sl firmware, did you have an issue with the NAS ?

[Cricrou59]

in fact I would upgraded the 5 existing disks of 1.5to to new disks of 2to and then I puted the disk one by one after rebuilding the raid each time. When I was puting the last one the blue led was blinking during a while and nothing happend. I have also tell me someone working in Lacie and no issue to resolve the problem because the product was too old. The problem that I have not anymore the existing disks.
I have found your website usefull so I'm trying to repair the NAS