Blue LED Blinking and no network access to 2Big Network

[Jocko]

I think (and it is what fvdw wanted), is to investigate first the disk state before installing our firmware.

Indeed, and I assume it is your case, if you set a raid5 on them, there are some system files stored on the data volume (raid5). So your behaviour may happen if :
- fs system on the raid is corrupted
- fw fails to assemble the raid (fail disk state on at least 2 disks)
- there is an issue (hardware) on the sata port.

So please to post the expected output (fdisk) and there are others...

Note: anyhow if you want to backup your data, you will have to do them...

[PaaNooS]

So I've download 5 rar files, extract them into a folder and run 'fvdw-sl-console.exe'.
I take the message 'Enter password for fvdw-sl-console'.
While entering the 5 numbers I find into 'keyfile.txt' file I take the message 'You didn't say the correct magic word'.

So where am I wrong ?

And some more questions.
How connect my PC and my NAS ?
Now they are connected in my local network via a network hub and both of them have static addresses. Is this OK ?

Is anywhere a link with step-by-step instructions ?

[PaaNooS]

Finally I found some answers and followed the procedure

From Load standalone kernel help
Instructions:
Switch off your NAS and follow the instructions that will appear in the main fvdw-sl console window, below some extra information:
(1) Switch off your NAS and start fvdw-sl console and choose action "standalone kernel, load and start" - OK
(2) Answer the question in the dialog boxes that will popup. 'Is your device supported?' - answered YES
(2) Select the stanalone kernel file to be loaded - so which is the correct UIMAGE file for my NAS ? I've selected UIMAGE-26394-2BIG1-27-1-1-1-standalone. Is this the correct file ?
(3) Start your NAS as soon as a window pops up with the remark that it waits for u-boot.........After starting the kernel the command window will close automatic. - Everything OK
(4) After closing the command window automatically the fvdw-sl console wait 15 seconds to start a telnet client enabling you to log in to the NAS. OK
(6) Log in using the telnet client - Here's my issue. Telnet client opens but without any command. Just a blinking cursor

So what is the next step ?

[fvdw]

You selected the wrong file, you must select the kirkwood standalone kernel.
When telnet client pops up login using username: root and password: giveit2me

[PaaNooS]

You selected the wrong file, you must select the kirkwood standalone kernel.
When telnet client pops up login using username: root and password: giveit2me

OK finally I've login.
Run fdisk -l but I don't know what I expect to see

You can see the results to attach file

How can I see my files ?

[PaaNooS]

You selected the wrong file, you must select the kirkwood standalone kernel.
When telnet client pops up login using username: root and password: giveit2me

OK finally I've login.
Run fdisk -l but I don't know what I expect to see

You can see the results to attach file

How can I see my files ?

[fvdw]

We need output of

Code: Select all

gdisk -l /dev/sda
Gdisk -l /dev/sdb

This to see if we can access the partitions on the disk and which type they are.
You will find 10 partitions on each disk. In lacie firmware the data files are stored in partition 2. If these are raid you need to assemble the raid array first to be able to see your files. For that you need to upload mini glibc and tools. To do that give command fvdw-sl-programs and choose option 4.
After that use this command to build the raid array

Code: Select all

mdadm -assemble /dev/md0 /dev/sda2 /dev/sdb2

If that succeeds mount the array

Code: Select all

mkdir /md0
mount /dev/md0 /md0

If that succeeds you will find your files in folder /md0

Code: Select all

ls -al /md0

[PaaNooS]

We need output of

Code: Select all

gdisk -l /dev/sda
Gdisk -l /dev/sdb

This to see if we can access the partitions on the disk and which type they are.
You will find 10 partitions on each disk. In lacie firmware the data files are stored in partition 2. If these are raid you need to assemble the raid array first to be able to see your files. For that you need to upload mini glibc and tools. To do that give command fvdw-sl-programs and choose option 4.
After that use this command to build the raid array

Code: Select all

mdadm -assemble /dev/md0 /dev/sda2 /dev/sdb2

mdadm: option -s not valid in manage mode


If that succeeds mount the array

Code: Select all

mkdir /md0
mount /dev/md0 /md0

If that succeeds you will find your files in folder /md0

Code: Select all

ls -al /md0

[PaaNooS]

Sorry how can I send you the output of gdisk command ?

[PaaNooS]

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: 7814037168 sectors, 3.6 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): AB19109A-4435-4C22-972E-72E4071BC2AB
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 7814037134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2029 sectors (1014.5 KiB)

Number Start (sector) End (sector) Size Code Name
1 2048 4095 1024.0 KiB EF02 grub_core
2 4096 397311 192.0 MiB 0700 boot_rescue
3 397312 399359 1024.0 KiB 0700 nv_data
4 399360 3545087 1.5 GiB FD00 root_1
5 3545088 6690815 1.5 GiB FD00 root_2
6 6690816 8787967 1024.0 MiB FD00 var
7 8787968 9312255 256.0 MiB FD00 swap
8 9312256 7814037119 3.6 TiB FD00 slot1.8
root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sdb
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/sdb: 7814037168 sectors, 3.6 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 0B3970A2-87E8-4AA3-94F6-F049C9A1A830
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 7814037134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2029 sectors (1014.5 KiB)

Number Start (sector) End (sector) Size Code Name
1 2048 4095 1024.0 KiB EF02 grub_core
2 4096 397311 192.0 MiB 0700 boot_rescue
3 397312 399359 1024.0 KiB 0700 nv_data
4 399360 3545087 1.5 GiB FD00 root_1
5 3545088 6690815 1.5 GiB FD00 root_2
6 6690816 8787967 1024.0 MiB FD00 var
7 8787968 9312255 256.0 MiB FD00 swap
8 9312256 7814037119 3.6 TiB FD00 slot2.8