Blue LED Blinking and no network access to 2Big Network

[PaaNooS]

root@fvdw-sta-kirkwood:/ # mdadm -assemble /dev/md0 /dev/sda2 /dev/sdb2
mdadm: option -s not valid in manage mode

[PaaNooS]

I feel that I'm very close to my files thanks to you

So what the next step ?

[fvdw]

Sorry my fault, command should be

Code: Select all

mdadm --assemble /dev/md0 /dev/sda2 /dev/sdb2

[PaaNooS]

Sorry my fault, command should be

Code: Select all

mdadm --assemble /dev/md0 /dev/sda2 /dev/sdb2

root@fvdw-sta-kirkwood:/ # mdadm --assemble /dev/md0 /dev/sda2 /dev/sdb2
mdadm: no recogniseable superblock on /dev/sda2
mdadm: /dev/sda2 has no superblock - assembly aborted

[fvdw]

Mmm...
I did not look well to the output of gdisk that you posted

Code: Select all

Number Start (sector) End (sector) Size Code Name
1 2048 4095 1024.0 KiB EF02 grub_core
2 4096 397311 192.0 MiB 0700 boot_rescue
3 397312 399359 1024.0 KiB 0700 nv_data
4 399360 3545087 1.5 GiB FD00 root_1
5 3545088 6690815 1.5 GiB FD00 root_2
6 6690816 8787967 1024.0 MiB FD00 var
7 8787968 9312255 256.0 MiB FD00 swap
8 9312256 7814037119 3.6 TiB FD00 slot1.8
root@fvdw-sta-kirkwood

This is not a normal partition table for a 2big2 :scratch . Did your nas run with this setup ?

Anyhow it seem the data partition is nr 8 in your case
So in the assemble command use /dev/sda8 /dev/sdb8 instead of /dev/sda2 and /dev/sdb2

[PaaNooS]

Mmm...
I did not look well to the output of gdisk that you posted

Code: Select all

Number Start (sector) End (sector) Size Code Name
1 2048 4095 1024.0 KiB EF02 grub_core
2 4096 397311 192.0 MiB 0700 boot_rescue
3 397312 399359 1024.0 KiB 0700 nv_data
4 399360 3545087 1.5 GiB FD00 root_1
5 3545088 6690815 1.5 GiB FD00 root_2
6 6690816 8787967 1024.0 MiB FD00 var
7 8787968 9312255 256.0 MiB FD00 swap
8 9312256 7814037119 3.6 TiB FD00 slot1.8
root@fvdw-sta-kirkwood

This is not a normal partition table for a 2big2 :scratch . Did your nas run with this setup ?

Anyhow it seem the data partition is nr 8 in your case
So in the assemble command use /dev/sda8 /dev/sdb8 instead of /dev/sda2 and /dev/sdb2

root@fvdw-sta-kirkwood:/ # mdadm --assemble /dev/md0 /dev/sda8 /dev/sdb8
mdadm: /dev/md0 has been started with 2 drives.
root@fvdw-sta-kirkwood:/ # mkdir /md0
root@fvdw-sta-kirkwood:/ # mount /dev/md0 /md0
mount: unknown filesystem type 'LVM2_member'

[fvdw]

Looks like your disks use a similar setup as the cloudbox
Ti get to the data we need to use lvm. I need to have a look in my archive how to do it.

Ps. If you succeed to access your data files be aware that copying 3 TB via ftp or usb will take a long time.

[PaaNooS]

Ps. If you succeed to access your data files be aware that copying 3 TB via ftp or usb will take a long time.

This is my dream. To see my data. Most of them are included into another NAS (WD MyCloud EX2 Ultra) so only some GB are for copying.

root@fvdw-sta-kirkwood:/ # ls -al /md0
total 0
drwxr-xr-x 2 root root 40 Jan 1 01:24 .
drwxrwxrwt 13 root root 540 Jan 1 01:24 ..

[PaaNooS]

Looks like your disks use a similar setup as the cloudbox.

Remember that first I tried to reset my NAS even without hard disks, or including only disk #1, or including only disk#2.
And in normal is about a RAID 1 NAS. So I don't know if these 'reset' attempts changed NAS setup

[fvdw]

I found the topic were we discussed and solved a similar issue
See here https://plugout.net/viewtopic.php?f=28&t=2499&hilit=mdadm&start=30#p22538
To make this work you will need the attached archive, put it in the tftp folder of the fvdw-sl console

To install do this when running standalone kernel (replace ip-pc by actual ip of your pc running the fvdw-sl console)

Code: Select all

tftp -l lvm-202_02_98-vs3-19mei16.tar -r lvm-202_02_98-vs3-19mei16.tar -g ip-pc

tar -xvf lvm-202_02_98-vs3-19mei16.tar

In the topic I just referred to you can find info how to use it and get lvm working to retrieve the required info to be able to mount your data partition