First of all, thanks for an insane amount of information here on the website :)
When turning it the box it tries to boot.
It does boot so far that it initiates the network and becomes active on the configured IP.
However, it gets stuck there, just writing "device may be powering on, please wait" when connecting to the IP in a browser.
The disks some times say stuff and the LED's are blinking.
I tried removing one disk at a time to see if there were hardware failures, but still only same scenario as above.
So I started the FVDW console to see what could be happening.
I can boot the box with the standalone kernel UIMAGE-3142-KIRKWOOD-150-standalone. I get the terminal window and I can log into the device.
So far so good.
If I try to boot the External kernel using
\tftp\firmware\kirkwood\UIMAGE-3142-NWSP2CL-14
it seems to not work. I have waited several minutes, but I cannot ping the IP nor log into the webinterface.
Back to the standalone boot then.
I have uploaded mdmadm to the box and I think I should use it something like this.
- Code: Select all
mdadm --assemble /dev/md0 /dev/sd[abcde]2
But how do I know that md0 etc is actually the correct device names?
There is md0-md17 listed in /dev.
What to look for and how do I proceed?
I think that the box was configured in a standard raid5 configuration and only configured with an ip and some sharing stuff.
The data is IMPORTANT.
Would like to get to a point where data is accessible and copy it out to an external drive of some sort.
Any help appreciated. Thanks
My linux knowledge is limited, but improving slowly.
Sincerely
Peter
