Blinking Blue Light (big one), Drive Invisible on network

[area52a]

OK, here's an update...

I purchased an entire (used) 5big enclosure w/power supply (no drives)...I have first taken just the power supply & plugged it into my distressed unit, same thing happens, boots fine, all 5 drive lights indicate everything is ok, the big blue main LED is blinking blue & the NAS is not visible on the network.

I am thinking I can take my 5 drives & drop them into the empty 5big enclosure I bought & see what happens then. (I am thinking since the 5 drives all seem ok, that it may be a hardware issue (the main 5big box itself)....

Does any of what I am trying to do make sense?

I am trying to be cautious as I do not want to lose the files on the drives.

(should I try to put the drives into the other unit I bought? Is there a chance it will show up on the network? Can doing that affect the data on the drives?....Sorry, as mentioned before, I am not entirely computer savvy)

I am willing to try other options but to be honest, I do not really know what "standalone kernel" or "raid array" mean, therefore I would need someone to hold my hand & totally walk me through the procedure..LOL

I just want to transfer the data at this point (I have already bought a USB connected storage unit).


Thanks again, Dennis

[Glaven Clattuck]

I had a problem similar to yours, using the fvdw-modlaità console in stand-alone mode, with the guidance of j@ocko and @fvdw, I resolved.
Then downloaded the program, follow the instructions, begins to post the results as suggested by @jocko and you will solve.

[fvdw]

your problem is probably not the hardware but the lacie operating system on your disks, so using the new empty enclosure is not required I think

So do as Jocko suggested in this post viewtopic.php?f=26&t=2317#p22494
Download the fvdw-sl console from here viewtopic.php?f=7&t=2691 install it on your windows PC and choose action load and start standalone kernel and read the instruction given how to do that and how to handle the nas.
There is even a help page included in the fvdw-sl console desribing in detail to perform this action.
if this kernel succefull loads then you will be able to connect to your 5big2 using the telnet client that is automatically startup by the fvdw-sl console and we can start to examine the disks using this client.

You need a windows PC connected your the same LAN as yout 5big2 and using a wired connecting.
Disable your firewall on your PC to allow the fvdw-sl programs to find and access your nas. Or grant access through the firewall if your windows system ask this.

if the raid array is ok or can be repaired then there is a good chance that we can recover your data

[area52a]

OK, I hope I downloaded the correct files. First I downloaded a file that gives instructions on what to do (install_fvdw_sl_firmware_hlp), I also downloaded "fvdw-sl-console-6-16-1-9feb2016" (in 4 parts)...Are those the correct files? They have an ending ".rar". I tried to open them & I am unable to. Do I need all 4 parts or just 1? Do I need a special .rar opener software?What do I need to do next? How can choose option, load?

[Jocko]

Hi area52a,

I also downloaded "fvdw-sl-console-6-16-1-9feb2016" (in 4 parts)...Are those the correct files? They have an ending ".rar". I tried to open them & I am unable to.

It is a rar archive split in 4 parts.
So you need all of them and keep them in a same location before uncompressing. If you have made several attempts check to have the same syntax on all names (with several attempts you may have an index "(1)" or (2) ..(n) added in some names => remove the downloaded file on wrong attempts and remove the index on the filename of the right attempts)
With a rar archive you should open it by any common zip program (by default you can install the free version of winrar).
Then just ask to uncompress after selecting the part1

Otherwise, I advice you to read carefully the help about the action "load a standalone kernel".
on the board there are also several topics where members fail to get a telnet access. You can read them but mainly the issues were :
- use a wireless connection on their laptop
- did not set rightly the firewall on their laptop (you can try first to disable it)
- several network cards were enabled on the laptop (this is important on a win10; keep only one network card)
- run the action "load a standalone kernel" where as the nas was already running

[Jocko]

Another information when you will succeed to get a telnet access, to use the mdadm command, you need to download the binary first :

Code: Select all

tftp -l /sbin/mdadm -r mdadm -g ippc

where ippc is the IP of your laptop
set run permissions on it

Code: Select all

chmod 755  /sbin/mdadm

Then you should be able to run the asked mdadm command

Code: Select all

mdadm --examine /dev/sd[abcde]2