NAS not reacting at all

[jmparisot]

Tried again.

Still no luck. It went twice up to saying formating of /dev/sda5 completed but that was it. The next step did not launch (I saw it once so far, trying to install the kernel I think).

Really strange behavior.

Could it be some serious hardware damage though?

[fvdw]

This latest standalone #157 should also support lan2 port of the 5big2.
You can try if that makes a difference.

I have a question. Does the telnet connection loses connection when the scipt stops or do you get a command prompt?
If the script hangs and there is still a connection you should be able to abort the script by ctrl z or ctrl x to get a command prompt.

[jmparisot]

Ok great, I will give it a try tonight using Lan2 of the NAS.

I will also check if I am still able to do a ctrl Z or not.

I know however, that I can open a new telnet window and reconnect to the NAS again. That works for another 6-10 windows, after that connecting to it is not possible at all and I get a connection failed popup from the telnet window. I wonder if there is a limited number of simultaneous connections possible with telnet to the NAS? That would explain that I have too many telnet connections started.

[jmparisot]

Hello,

Still no luck.

Tried to boot from LAN2, however the kernel is transferred, however telnet cannot connect. The IP is still *.252 so should work as with LAN1.

I also tried to do CTRL+Z, it works sometimes, but sometimes it does not work.


Just to make sure again I do the right steps (you never know):

1. NAS is switched off with the power button, one harddrive is inserted in Slot 1. LAN connected to LAN1.
2. Launch FVDW-SL console 6
3. Choose Action > Install fvdw-sl firmware
4. When it says "waiting for uboot", I switch on the NAS.
5. Kernel file is transferred (around 5.6 MB)
6. Telnet launches
7. I login with root and giveit2me (here it sometimes has no reaction anymore)
8. type fvdw-sl-programs
9. I choose "1-Install fvdw-sl firmware on a hard disk"
10. next window "OK"
11. 2-lacie kirkwood 2big2, 5big2
12. Next windows: All Yes/OK
13. Starts (but never gets to the end)



Note: All network connections are switched off except for the network lan. Firewall is disabled, so is the antivirus.

:thinking

[fvdw]

:dry not do good.
Although the connection should be lost when using a wired connection so I still suspect an hardware issue
lets try do some checks and steps manually and see if we can get a working system disk.
Fire up the standalone kernel (#157) and give commands in telnet window

fdisk -l /dev/sda
gdisk -l dev/sda
ifconfig

And post the output

Hopefully in a former run the script succeeded to make the right partition structure so we can skip that step and start to install some files manually in the partitions

[fvdw]

below a how to install the firmware manually with using the standalone kernel, hopefully I did not make typ errors ;)
This step by step manual enables us to repeat a step if fails. and we can see what going on

Assuming a disk is present in most left slot seen from back, and that on this disk the required partition structure for fvdw-sl firmware is present and correct setup, and furthermore that you use fvdw-sl console 6.0

Important: In the command below replace "ip-pc" by actual ip address of your pc running the fvdw-sl console

The the first step is to format partition sda5

Code: Select all

mke2fs-ext3 -j -m 1 /dev/sda5

if that goes well without error continu with writing the kernel to partition sda6
for this we need to mount partition sda5 to store the kernel temporarily

Code: Select all

mkdir /sda5
mount /dev/sda5 /sda5

if mount succeeds upload the kernel via tftp server

Code: Select all

busybox tftp -r firmware/kirkwood/UIMAGE-3142-NWSP2CL-14 -l /sda5/kernel.img -g ip-pc

If that goes well proceed with writing it to sda6

Code: Select all

dd if=/sda5/kernel.img of=/dev/sda6

If that goes well remove the kernel from sda5

Code: Select all

busybox rm /sda5/kernel.img

get the firmware image form tftp server

Code: Select all

busybox tftp -r firmware/fvdw-sl-16-1-base-9feb16.img.tar.gz -l /sda5/firmware.tar.gz -g ip-pc

if that succeeds extract it

Code: Select all

cd /sda5
busybox tar -xzvf  firmware.tar.gz


If that succeeded remove the tar.gz archive and proceed with adapting the firmware for 5big2

Code: Select all

busybox rm firmware.tar.gz
cd /
busybox tftp -r firmware/kirkwood.tar.gz -l /sda5/cor.tar.gz -g ip-pc

If that succeed unpack this archive to the firmware image for this we mount the firmware image first

Code: Select all

mkdir fvdw-sl
mount /sda5/fvdw-sl-16-1-base-9feb16.img /fvdw-sl

if that succeeds extract the archive

Code: Select all

tar -xzvf /sda5/cor.tar.gz -C /fvdw-sl

If that succeeded the remove the correction archive

Code: Select all

busybox rm /sda5/cor.tar.gz

and unmount the firmware image

Code: Select all

umount /fvdw-sl

After that proceed with writing the firmware to sda1, sda2 and sda7

Code: Select all

dd if=fvdw-sl-16-1-base-9feb16.img of=/dev/sda1
dd if=fvdw-sl-16-1-base-9feb16.img of=/dev/sda2
dd if=fvdw-sl-16-1-base-9feb16.img of=/dev/sda7

if that all succeeded you can remove firmware image

Code: Select all

busybox rm /sda5/fvdw-sl-16-1-base-9feb16.img

Now proceed with installing the default database

Code: Select all

busybox tftp -r firmware/sda5-lacie-nwsp.tar.gz -l /sda5/sda5-lacie-nwsp.tar.gz -g ip-pc

if succeeded to upload extract it

Code: Select all

cd /sda5
tar -xzvf sda5-lacie-nwsp.tar.gz
cd /
chmod 777 /sda5/etc/nas_conf_db.xml

remove the database archive

Code: Select all

busybox rm /sda5/sda5-lacie-nwsp.tar.gz
umount /sda5

Last step format partition sda8 this may take some time..

Code: Select all

mke2fs-ext3 -j -m 1 /dev/sda8

create folder public on sda8

Code: Select all

mkdir /sda8
mount /dev/sda8 /sda8
mkdir /sda8/public
chmod 777 /sda8/public
umount /sda8

done

reboot the nas and see if the firmware comes up

Code: Select all

reboot -f

[jmparisot]

Good morning,

Here is the outcome of the first commands:

fvdw-sta-kirkwood login: root
Password:
root@fvdw-sta-kirkwood:/ # fdisk -l /dev/sda
fdisk: device has more than 2^32 sectors, can't use all of them

Disk /dev/sda: 2199.0 GB, 2199023255040 bytes
256 heads, 63 sectors/track, 266305 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 266306 2147483647+ ee EFI GPT
root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 5A381316-5B39-4BEA-BE33-26F5FB39D6EB
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 4062 sectors (2.0 MiB)

Number Start (sector) End (sector) Size Code Name
1 4096 1052671 512.0 MiB 8300 Linux filesystem
2 1052672 2101247 512.0 MiB 8300 Linux filesystem
3 2101248 3149823 512.0 MiB 8200 Linux swap
4 3149824 3166207 8.0 MiB 8300 Linux filesystem
5 3166208 4739071 768.0 MiB 8300 Linux filesystem
6 4739072 4755455 8.0 MiB 8300 Linux filesystem
7 4755456 5804031 512.0 MiB 8300 Linux filesystem
8 5804032 5860533134 2.7 TiB 8300 Linux filesystem
root@fvdw-sta-kirkwood:/ # ifconfig
eth0 Link encap:Ethernet HWaddr 00:D0:4B:93:07:E0
inet addr:192.168.188.252 Bcast:192.168.188.255 Mask:255.255.255.0
inet6 addr: fe80::2d0:4bff:fe93:7e0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:160 errors:0 dropped:0 overruns:0 frame:0
TX packets:352 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:10747 (10.4 KiB) TX bytes:33232 (32.4 KiB)
Interrupt:11

eth0:1 Link encap:Ethernet HWaddr 00:D0:4B:93:07:E0
inet addr:192.168.0.251 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:11

eth0:2 Link encap:Ethernet HWaddr 00:D0:4B:93:07:E0
inet addr:192.168.1.251 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:11

root@fvdw-sta-kirkwood:/ #

I tried to format the sda5, with the following result:

root@fvdw-sta-kirkwood:/ # mke2fs ext3 -j -m 1 /dev/sda5
mke2fs 1.41.14 (22-Dec-2010)
mke2fs: invalid blocks count '/dev/sda5' on device 'ext3'
root@fvdw-sta-kirkwood:/ #

[Jocko]

Hi jmparisot,

You made a typo error on your command missing '-' between mke2fs and ext3 so you have to use

Code: Select all

mke2fs-ext3 -j -m 1 /dev/sda5

[fvdw]

The partition table looks ok so you can proceed with the manual setup step by step. (See remark Jocko!).
From ifconfig I do not see transmit or receive errors, so no clue yet why telnet looses connection :scratch
But lets see what happens when you do the manual setup

[jmparisot]

Nope. Still no luck.

Same behavior...Freezes up...even sometimes when trying to login.

I wonder if mybe my router is dropping the telnet connections...tried twice the "AVM Fritz!Box"...and I do not like those at all, even for other things they try to do whatever they are not supposed to do...

My last hope is to check if I have an old router somewhere that I could use...no clue what else it could be.

Attached some screenshots...showing where it freezes up