Blue LED Blinking and no network access to 2Big Network

[PaaNooS]

Hello guys

Just a quick question.
'.streams' is a system folder ?
After backup with goodsync appeared to NAS a hidden folder with the name '.streams' that cannot delete. So I wonder if it's a NAS system folder that have to leave it alone.

[Jocko]

Hi

You have had to run a backup from a NTFS disk (so I assume from windows) to a linux OS using ext3/4 fs (the NAS). With samba4, the alternate data streams set by NTFS on a file are not managed by an ext3/4 fs. So samba stores these alternate data in a system folder '.streams' as soon as at least one file of the current folder has this data type (like file downloaded from Internet,...).

You can delete this folder only from the shell console and if you do it and you restore later the files this alternate information will be lost. Then it is what you want to do with these alternate data, can say if you have or not to delete this folder.

[PaaNooS]

OK

I see.

Thanks again

[PaaNooS]

Hello guys

thanks to you my NAS works perfect.
So I think different ways to take advantage of him.
My question is if I can connect my NAS with my camera to use it as a NVR and if so how can I do that ??

[Jocko]

Hi

Currently only usb camera can be used. But some month ago, I worked to use a newer motion version which allows to manage LAN camera. So on next month, I will look if I can make a beta version for testing. Please to note with a 2big2 you can manage only 2 camera (or 3 with a low resolution)

[PaaNooS]

Hi

Currently only usb camera can be used. But some month ago, I worked to use a newer motion version which allows to manage LAN camera. So on next month, I will look if I can make a beta version for testing. Please to note with a 2big2 you can manage only 2 camera (or 3 with a low resolution)

Hi Jocko

Thank you for your reply. I'm waiting for good news

[PaaNooS]

Hello guys
Wish you Happy New Year !!

I've a new issue
I wanna expand my NAS capacity from 3TB to 4TB

So I left my old 3TB disk A to left drive tray (tray 1) and put a new 4TB disk to right tray (tray 2)
System saw new disk and start synchronizing
After many many hours synchronizing completed.
Next I pulled out old 3TB disk and tried to boot from new 4TB disk (tray 2) with no luck with front led flashing blue.
I tried also with new 4TB into left tray (tray 1) but nothing changed
So what's my mistake ?
In normally NAS could boot even with only one disk in any tray, right ?

[Jocko]

Hi

I assume you use your nas with a raid1 on the data volume. Please to note what you want to do is the single case where you can not do it fully from the firmware GUI.
* First, restart the nas with this hardware configuration :
- old sda disk in the left slot
- new sdb disk in right slot
* Backup some system files:
open a shell window and run

Code: Select all

cd /rw_fs
tar -czf /direct-usb/fvdw/back-mysda5.tgz etc
chmod 666 /direct-usb/fvdw/back-mysda5.tgz

(tarball will be available in the fvdw on your laptop via samba)
* Store the tarball on your laptop: location tftp folder of fvdw-sl console
* Stop the nas, remove all disk and put only the new sda disk in the left slot
* Use fvdw-sl console to install the firmware on the new disk but do not restart yet the nas after doing it and keep open the telnet window :
Do the action : "Standalone kernel, load and start". (Note : you have to select the kernel image: UIMAGE-3142-KIRKWOOD-171-standalone)
Run in the telnet window, the command: fvdw-sl-programs and select "install fvdw-sl firmware" ....
* Upload the tarball and restore the backup system files

Code: Select all

umount /dev/sda5
mkdir /sda5
mount /dev/sda5 /sda5
cd /sda5/tmp
tftp -l /sda5/tmp/back-mysda5.tgz -r back-mysda5.tgz -g IP-PC
tar -xf /sda5/tmp/back-mysda5.tgz -C /sda5

(IP-PC is the IP address of your laptop)
* Stop the nas, insert the new sdb disk and restart the nas.
As I am not fully sure what will be the raid statut after rebooting, please to post these outputs :

Code: Select all

mount
mdadm --examine /dev/sd[ab]8
cat /etc/mdadm.conf
mdadm --detail /dev/md0


May be you should include again sda8 (Vol-A) in your raid to restore fully your configuration. In this case I will post some additional commands.

[PaaNooS]

Hi

I assume you use your nas with a raid1 on the data volume. Please to note what you want to do is the single case where you can not do it fully from the firmware GUI

Hi Jocko

I've restart the procedure from the beginning (- old sda disk in the left slot - new sdb disk in right slot) and is still synchronizing, so we have to wait until the end

In the meantime let make clear some things

Now my NAS looks like attach image.
So have I to wait to complete synchronize ?
Have I to put an empty (with no partitions) sdb ?
I can delete existing partitions with "MiniTool Partition Manager"

* Backup some system files:
open a shell window and run

you mean "putty" or "fvdw-sl console" ?
with sda and sdb in the slots ?

what is tarball ?

[Jocko]

Hi

Yes, you have to wait from completing synchronization because sdb will be used to restoring your data when sda (new disk without data on sda8) will be re-add in raid1 volume.

fvdw-sl console must be used only for initializing the new sda disk, you have to use putty (or web-console) on the other steps