Front light blinking red and status Raid is degraded

[Jocko]

Nice !

Is there any way to rebuild the old paths? or it remains only to move the files one by one...

Nope you have to create again the folder tree and move the files one by one.

Note : you can use winscp on your laptop to do it directly (provide a window interface like file explorer and you can use the mouse to move easily the files)

[Glaven Clattuck]

Nice !

Is there any way to rebuild the old paths? or it remains only to move the files one by one...

Nope you have to create again the folder tree and move the files one by one.

Note : you can use winscp on your laptop to do it directly (provide a window interface like file explorer and you can use the mouse to move easily the files)

I'm on Mac, but I think I can find a similar program.

[Glaven Clattuck]

I have a problem.
As mentioned on Mac I found programs similar to WinSCP or through an emulator I could use the same WinSCP, but almost all of them connect via SFTP on port 22. Unfortunately they only show me the Directories that are inside "shares", and they don't let me go back to the root.
I need to go back to the root, because the files are in the path:

/media/internal_1/lost+found/

If I try to use port 2222 I just can't connect.
Any suggestions?

[fvdw]

Maybe using the linux move (mv) command is a solution.
You can use wildcards to move all files in a directory to another one, using the -i option is recommended to prevent overwriting existing files

Examples see here link

[Jocko]

That would mean your sftp serveur is chrooted in the folder shares. Only SCP protocol will allow you to get a full access with your hacked root access,
On mac I do not know gui client app using scp protocol.
What you may try is to mount the folder Lost+found on a folder in shares. Then you should get access on your files with a sftp client app.

Like this :

Code: Select all

mkdir /shares/rescue
chmod 777 /shares/rescue
mount --bind  /media/internal_1/lost+found /shares/rescue

ls  /shares/rescue (to check if you see your files)

After restoring, you have to unmount it and delete the mountpoint

Code: Select all

umount /shares/rescue
rm /shares/rescue

[Glaven Clattuck]

Things are getting worse and worse.
I followed Jocko's suggestion, created the recover directory etc..
but moving files with this GUI program has proved difficult. Large files were almost always terminated sooner.
So I proceeded using the

Code: Select all

mv

command directly
Here at the beginning things worked but at some point errors appeared. The Nas froze and after turning it off and on again I am now in this situation:
The restart procedure is very fast, the blue light remains fixed in front, but all the LED lights of the 5 HDs are off.
I can no longer reach the NAS, but if I ping it the NAS responds.
If I try to connect via SSH this is the answer.

Code: Select all

ssh: connect to host 10.211.55.248 port 2222: Connection refused

Did I lose the fight or is there still something I can do?