Blue LED Blinking and no network access to 2Big Network

Re: Blue LED Blinking and no network access to 2Big Network

Postby PaaNooS » Fri Nov 18, 2022 9:00 am

Hello fvdw

as a good student, I've followed your instructions step by step and everything is OK.

Finished without any error message. BUT after command reboot -f front led is steady red and I cannot find my NAS in local network even running fvdw-sl assistant.exe

So I'm waiting for your advice (again) :please
PaaNooS
Donator VIP
Donator VIP
 
Posts: 120
Joined: Tue Nov 15, 2022 10:16 am

Re: Blue LED Blinking and no network access to 2Big Network

Postby fvdw » Fri Nov 18, 2022 9:56 am

which device did you choose when installing firmware ? You must choose lacie kirkwood 2big2
Did you choose that device ?

We noticed that sometimes the internal disks connection are swapped, so what you could try is to move the disk from lefthand side slot (seen from the back) to the righthand slot. However this is unlikely but worth a try.
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Blue LED Blinking and no network access to 2Big Network

Postby Jocko » Fri Nov 18, 2022 10:27 am

Hi

In addition with fvdw, or lacie firmware (kernel) is still present on 2d disk and then the bootloader uses it

So before trying to swap the disks, remove the right disk (when you look at the slot side) and reboot
Jocko
Site Admin - expert
 
Posts: 11529
Joined: Tue Apr 12, 2011 4:48 pm
Location: Orleans, France

Re: Blue LED Blinking and no network access to 2Big Network

Postby PaaNooS » Fri Nov 18, 2022 10:49 am

fvdw wrote:which device did you choose when installing firmware ? You must choose lacie kirkwood 2big2
Did you choose that device ?


Yes. I choosed lacie kirkwood 2big2

fvdw wrote:We noticed that sometimes the internal disks connection are swapped, so what you could try is to move the disk from lefthand side slot (seen from the back) to the righthand slot. However this is unlikely but worth a try.


I tried with no success
PaaNooS
Donator VIP
Donator VIP
 
Posts: 120
Joined: Tue Nov 15, 2022 10:16 am

Re: Blue LED Blinking and no network access to 2Big Network

Postby fvdw » Fri Nov 18, 2022 10:53 am

mmm..very strange put the disk back in most lefthand slot and boot with standalone kernel
At command prompt give commands
Code: Select all
gdisk -l /dev/sda


If it shows the disk and the partitions do
Code: Select all
mkdir /sda7
mount /dev/sda7 /sda7
ls -al /sda7
cat /sda7/boot.log
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Blue LED Blinking and no network access to 2Big Network

Postby fvdw » Fri Nov 18, 2022 10:53 am

mmm..very strange put the disk back in most lefthand slot and boot with standalone kernel
At command prompt give commands
Code: Select all
gdisk -l /dev/sda


If it shows the disk and the partitions do
Code: Select all
mkdir /sda7
mount /dev/sda7 /sda7
ls -al /sda7
cat /sda7/boot.log
fvdw
Site Admin - expert
 
Posts: 13471
Joined: Tue Apr 12, 2011 2:30 pm
Location: Netherlands

Re: Blue LED Blinking and no network access to 2Big Network

Postby PaaNooS » Fri Nov 18, 2022 10:56 am

Jocko wrote:Hi

In addition with fvdw, or lacie firmware (kernel) is still present on 2d disk and then the bootloader uses it

So before trying to swap the disks, remove the right disk (when you look at the slot side) and reboot


I have still right disk removed
PaaNooS
Donator VIP
Donator VIP
 
Posts: 120
Joined: Tue Nov 15, 2022 10:16 am

Re: Blue LED Blinking and no network access to 2Big Network

Postby PaaNooS » Fri Nov 18, 2022 11:01 am

fvdw wrote:mmm..very strange put the disk back in most lefthand slot and boot with standalone kernel
At command prompt give commands
Code: Select all
gdisk -l /dev/sda


If it shows the disk and the partitions do
Code: Select all
mkdir /sda7
mount /dev/sda7 /sda7
ls -al /sda7
cat /sda7/boot.log



root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 7814037168 sectors, 3.6 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 00000000-0000-0000-0000-000000000000
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 7814037134
Partitions will be aligned on 2048-sector boundaries
Total free space is 4062 sectors (2.0 MiB)

Number Start (sector) End (sector) Size Code Name
1 4096 1052671 512.0 MiB 8300 Linux filesystem
2 1052672 2101247 512.0 MiB 8300 Linux filesystem
3 2101248 3149823 512.0 MiB 8200 Linux swap
4 3149824 3166207 8.0 MiB 8300 Linux filesystem
5 3166208 4739071 768.0 MiB 8300 Linux filesystem
6 4739072 4755455 8.0 MiB 8300 Linux filesystem
7 4755456 5804031 512.0 MiB 8300 Linux filesystem
8 5804032 7814037134 3.6 TiB 8300 Linux filesystem
PaaNooS
Donator VIP
Donator VIP
 
Posts: 120
Joined: Tue Nov 15, 2022 10:16 am

Re: Blue LED Blinking and no network access to 2Big Network

Postby PaaNooS » Fri Nov 18, 2022 11:03 am

fvdw wrote:mmm..very strange put the disk back in most lefthand slot and boot with standalone kernel
At command prompt give commands
Code: Select all
gdisk -l /dev/sda


If it shows the disk and the partitions do
Code: Select all
mkdir /sda7
mount /dev/sda7 /sda7
ls -al /sda7
cat /sda7/boot.log


root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 7814037168 sectors, 3.6 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 00000000-0000-0000-0000-000000000000
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 7814037134
Partitions will be aligned on 2048-sector boundaries
Total free space is 4062 sectors (2.0 MiB)

Number Start (sector) End (sector) Size Code Name
1 4096 1052671 512.0 MiB 8300 Linux filesystem
2 1052672 2101247 512.0 MiB 8300 Linux filesystem
3 2101248 3149823 512.0 MiB 8200 Linux swap
4 3149824 3166207 8.0 MiB 8300 Linux filesystem
5 3166208 4739071 768.0 MiB 8300 Linux filesystem
6 4739072 4755455 8.0 MiB 8300 Linux filesystem
7 4755456 5804031 512.0 MiB 8300 Linux filesystem
8 5804032 7814037134 3.6 TiB 8300 Linux filesystem
PaaNooS
Donator VIP
Donator VIP
 
Posts: 120
Joined: Tue Nov 15, 2022 10:16 am

Re: Blue LED Blinking and no network access to 2Big Network

Postby PaaNooS » Fri Nov 18, 2022 11:06 am

root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5

Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 7814037168 sectors, 3.6 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 00000000-0000-0000-0000-000000000000
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 7814037134
Partitions will be aligned on 2048-sector boundaries
Total free space is 4062 sectors (2.0 MiB)

Number Start (sector) End (sector) Size Code Name
1 4096 1052671 512.0 MiB 8300 Linux filesystem
2 1052672 2101247 512.0 MiB 8300 Linux filesystem
3 2101248 3149823 512.0 MiB 8200 Linux swap
4 3149824 3166207 8.0 MiB 8300 Linux filesystem
5 3166208 4739071 768.0 MiB 8300 Linux filesystem
6 4739072 4755455 8.0 MiB 8300 Linux filesystem
7 4755456 5804031 512.0 MiB 8300 Linux filesystem
8 5804032 7814037134 3.6 TiB 8300 Linux filesystem
root@fvdw-sta-kirkwood:/ # mkdir /sda7
root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
root@fvdw-sta-kirkwood:/ # ls -al /sda7
total 96
drwxr-xr-x 20 root root 4096 Jan 1 00:03 .
drwxrwxrwt 13 root root 360 Jan 1 00:05 ..
lrwxrwxrwx 1 root root 14 Jan 1 00:03 .config -> /rw_fs/.config
lrwxrwxrwx 1 root root 20 Jan 1 00:03 .mldonkey -> /share/1000/mldonkey
lrwxrwxrwx 1 root root 15 Jan 1 00:03 .mpd -> /direct-usb/mpd
drwxr-xr-x 2 root root 4096 Jan 1 00:03 bin
drwxr-xr-x 2 root root 4096 Jan 1 00:03 bin_cab
drwxr-xr-x 2 root root 4096 Sep 25 2013 boot
drwxrwxr-x 2 root 999 4096 Jan 1 00:03 clunc
drwxr-xr-x 4 root root 12288 Jan 1 00:03 dev
lrwxrwxrwx 1 root root 12 Jan 1 00:03 direct-usb -> ./share/1000
drwxrwxrwx 18 root root 4096 Jan 1 00:04 etc
drwxr-xr-x 4 root root 4096 Feb 13 2017 lib
lrwxrwxrwx 1 root root 11 Jan 1 00:03 linuxrc -> bin/busybox
drwx------ 2 root root 16384 Jan 3 2008 lost+found
drwxr-xr-x 3 root root 4096 Jan 1 00:03 mail
drwxr-xr-x 2 root root 4096 Aug 27 2008 nowhere
drwxr-xr-x 7 root root 4096 Jan 1 00:03 opt
drwxrwxrwx 2 root root 4096 Mar 5 2011 proc
drwxr-xr-x 2 root root 4096 Jan 3 2008 root
drwxr-xr-x 2 root root 4096 Jan 1 00:03 sbin
drwxrwxr-x 2 root 999 4096 Mar 5 2011 share
drwxrwxrwx 2 root root 4096 Dec 30 2014 sys
drwxrwxr-x 21 root 999 4096 Jan 1 00:03 usr
drwxr-xr-x 2 root root 4096 Mar 9 2012 var
root@fvdw-sta-kirkwood:/ # cat /sda7/boot.log
cat: can't open '/sda7/boot.log': No such file or directory
PaaNooS
Donator VIP
Donator VIP
 
Posts: 120
Joined: Tue Nov 15, 2022 10:16 am

PreviousNext

Return to Lacie 2Big Network vs2

Who is online

Users browsing this forum: No registered users and 7 guests