Bricked??

Bricked??

Postby panico » Sat Jan 18, 2025 8:06 pm

Hi you all!

I have been testing the firmware from a week ago and it is very interesting. I have set up a 4 disk raid1, and it was working fine.

The problem is that yesterday I disconnected the ethernet cable from the NAS, because I wanted to unplug the NAS from the network due a test I was performing with other machine.

When I plug the ethernet cable back in the morning, I coudnt connect to the web interface, so I reset the NAS because I thougth that maybe a reboot were mandatory to take all the ip config (the four leds were steady at that moment, no alarm at all). From this very moment, the nas is blinking blue in the front and the four disk in an eternal bootloop (I have left it in this status three hours to discard an array reconstruction or something like that), but the RJ45 leds are steady all the time, not a blink. I have tried extracting the disks, plug them back, leave only the first one... nothing changes.

I have tried to reach the nas but nothing shows on ARP, also I have connected the NAS directly to my PC and I found that the OS doesn't detect the connection, is like the RJ45 NAS led's were on, but the connector doesn't work at all, so I can't do nothing trougth UBOOT.

Any ideas? the data is not a problem, I was just testing so there is nothing in the disk that was important.

Thanks in adavance.
panico
Donator VIP
Donator VIP
 
Posts: 7
Joined: Thu Jan 09, 2025 12:35 pm

Re: Bricked??

Postby fvdw » Sat Jan 18, 2025 10:41 pm

How did you reset the nas? If you did a power cut and the nas was writing data to disk then it may have caused corruption of system files. If there is no important data on the nas I would recommend that you repeat the installation.

ps normally unpluging/pluging he network cable should give no problem.
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Bricked??

Postby panico » Sun Jan 19, 2025 9:37 am

Thanks for the reply.

I performed a power cut, yes. I'm pretty new to the nas world and this firm itself, so I have noticed that when I use the back switch (on/auto/off) or the big front button functionality to turn it down, it remains still on, no matter the time I wait, but in this case I'm afraid that I should have performed a shot press on the front button.

I'm gonna reinstall all the firm again, but my problem and my question is: how? the nas ethernet connector doesn't seem to work (when I plug directly the NAS to my computer with the ethernet cable, the computer's ethernet port doesn't light up, is like I'm were connecting and unplugged cable). Also, when I connect the power to the nas, both ethernet leds on the NAS port lights on, but stays completely still.

I have checked the forum looking for a similar case o looking for a button combination or procedure to reset to default the firmware (I think that the firm still works somehow because it recognizes a 4 disk array due the led combination, if I connect the first disk only, the fourth led also lights up) but I haven't found anything.

If somebody can point me to a post or a tutorial/instructions, or give me the first step to start, I'll be very thankful.

Thanks in advance.
panico
Donator VIP
Donator VIP
 
Posts: 7
Joined: Thu Jan 09, 2025 12:35 pm

Re: Bricked??

Postby fvdw » Sun Jan 19, 2025 9:54 am

how did you install the firmware for the first time?

And, you should use a router with dhcp server to let the nas acquire an ip if it is set to dynamic ip. In that situation the dhcp server will assign an ip to the nas. If you connect the nas directly to your pc, that pc must also have a dhcp server running.

If you have set the nas to get a static ip it is a different story when the firmware is running. However for installation the nas boot loader will try to get an ip from a dhcp server.

What was your setting when our firmware was running, dynamic or static ip?
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Bricked??

Postby panico » Sun Jan 19, 2025 2:58 pm

Static. Mi router has also a static ip for the NAS mac, and a DHCP server running. I have configured the computer, when I connected the NAS directly, as dhcp server first, and second as static ip with the ip configured as gateway in the NAS as the computer ip and the gateway of the computer with the NAS ip. Nothing.

Also, I think that is important that the NAS doesn't seem to have a working ethernet port. When I conect the cable attached to the NAS to the computer or to the router, none of them light up the port, is like when I connect a cable that is not connected.

Thanks.

EDIT: I instaled the firmware using the fvdw-sl-console, following the instructions on the forum. Buty now the nas is not reachable :(
panico
Donator VIP
Donator VIP
 
Posts: 7
Joined: Thu Jan 09, 2025 12:35 pm

Re: Bricked??

Postby fvdw » Sun Jan 19, 2025 4:20 pm

ok I see,
But as said when installing the firmware the uboot (the bootloader of the nas) will try to get a dynamic ip and use that to receive the signal of the fvdw-sl console to interupt boot and load the standalone kernel so you must remove the static assignment to the mac of the nas from your pc and router.

About ethernet port.
I doubt if it is really broken. Can only happen if there was a lighting strike or so on the power supply of the nas or other high voltage.
Long schot maybe it is a bad connection or broken ethernet cable. You could try to clean the ethernet port contacts and try another cable. Typically the leds flicker even when the nas is switched off.
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands


Return to Lacie 5Big Network vs1

Who is online

Users browsing this forum: No registered users and 3 guests