plugout.net

Posted: **Sun Jan 24, 2016 8:02 pm**

Hello all.

This site has been a great resource.

I got my hands on a Lacie 5Big Network 2U 10TB Unit.
Had only 1 3TB Seagate HDD in bay 1. (Official from lacie)
I have 3x3TB and 2x4TB WD RED's waiting to be swapped in.

Used the Console, with the Kirkwood standalone, and everything went well.
Said yes that my unit supports drives greater than 2TB, and yes than I have a drive greater than 2TB.
Then in tftp, I write the firmware for Kirkwood.

Got to the end, typed in reboot -f, and the lights flashed on my 5BIG, and I heard the HDD spinning up.
Maybe a minute later I was disconnect from tftp, and I went to the web interface, nothing. times out.

The assistant app cannot find the NAS.

My setup is my laptop, wireless disabled, hooked up to a dlink router.
The dlink assigns the IPs via DHCP.
and the lacie hooked up to the router aswell.
Nothing else.

My laptop IP is 192.168.1.250
And the 5BIG is 192.168.1.252
These IPs all worked fine during the install.
I waited a great deal of time, and the 5BIG does not respond.
Power off/on didn't change anything.

That's it.
I did it again and again.

Any help is greatly appreciated. I am out of my depth here.

Posted: **Sun Jan 24, 2016 8:27 pm**

The 5big2 will have a different IP when booting the firmware it will request one aform the dhcp server in your LAN. Does your router has DHCP server active ?

If not then the 5big2 will not be able to acquire an ip address and is not reachable.
PS the one set during installation, in your case 192.168.1.252 is set static ones and not used when the firmware is loading.

If you have a DHCP server active then something elese must be wrong.
(a) Have put the disk in bay 1, meaning the most left hand slot seen from the back, correct ?
(b) did the installer finished with installation successfully completed ?

If answer on both questions is yes, turnoff the 5big2, start the fvdw-sl console and load the standalone kernel
Connect with telnet client and perform following commands and post the output

Code: Select all: gdisk -l /dev/sda

Code: Select all: mkdir /sda7 mount /dev/sda7 /sda7 cd sda7 ls -al cat boot.log

Posted: **Sun Jan 24, 2016 8:44 pm**

UPDATE -

ran the entire setup, with a 1.5TB HDD, and it worked.
updated to 16.1 without issue.

Could it be that my 5BIG does not support drives greater than 2TB?
Is there a method to update (the kernel or firmware?) so that it does support drives greater than 2TB?

I'll be busy for the rest of the day, will pop the 3TB HDD back in, and post the results of your queries later tonight if possible.

Thanks

Posted: **Sun Jan 24, 2016 9:19 pm**

Could it be that my 5BIG does not support drives greater than 2TB?

The fvdw-sl kernel support those disks, to use the capacity they need to have a GPT partition table.
However to load the kernel and the firmware the bootloader should also support disks with GPT partition tables.Otherwise it can not read the disk content to load kernel and root files system from the system disk.

I would surprise me if your 5big2 has a boot loader that doesn't support GPT. All 5big2 I have seen supported GPT partition tables. On my 5big2 I use a 3TB disk as system disk
You can check if your bootloader support GPT. If you have the fvdw-sl firmware running, connect to the ssh server with ssh client, for example putty, log in user: root password: giveit2me (assuming you have not changed the default ssh password)
and give this command

Code: Select all: root@fvdwsl-5big2:/ # dmesg | grep command

it should give a response like this

Code: Select all: [ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda7 ro reset=0 productType=BIG5_KW cap=gpt,lba64

If cap=gpt, lba64 is present then your bootloader supports a GPT partition table and is able to boot from any disk having a GPT partition table.

The only thing I can think off is that maybe you did not use a GPT partition but a ms-dos table when installing the firmware on the 3TB disk.

Anyhow a system disk of 1.5 TB with 3 TB disks in the other slots should work fine, the kernel is able to read those disks and mount them in the firmware.

Posted: **Mon Jan 25, 2016 2:36 pm**

To recap, here are my steps :

LAcie 5BIG2 is off.
Has 2 network, 2 USB, 2esata.
Network cable is plugged into LAN1.
Has SEagate 3TB Hdd in Bay 1 (left most)
Start console, run standalone kernel.
Select UIMAGE-3142-NWSP2CL-KIRKWOOD-24-alone
Follow instrucions from Install fvdw sl firmware helpfile.

Onto your queries.

From the 3TB HDD :

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: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): B6FDC30C-6427-4C27-BC1F-4655C19763F2
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
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 5860533134 2.7 TiB 8300 Linux filesystem

----------------------------------------------------------------------------

root@fvdw-sta-kirkwood:/sda7 # ls -al
total 96
drwxr-xr-x 20 root root 4096 Dec 30 2014 .
drwxrwxrwt 13 root root 340 Jan 1 00:01 ..
lrwxrwxrwx 1 root root 20 Dec 30 2014 .mldonkey -> /share/1000/mldonkey
drwxr-xr-x 2 root root 4096 Dec 30 2014 bin
drwxr-xr-x 2 root root 4096 Dec 30 2014 bin_cab
drwxr-xr-x 2 root root 4096 Sep 25 2013 boot
drwxrwxrwx 2 root root 4096 Dec 30 2014 clunc
drwxr-xr-x 4 root root 12288 Dec 30 2014 dev
lrwxrwxrwx 1 root root 12 Dec 30 2014 direct-usb -> ./share/1000
drwxrwxrwx 18 root root 4096 Apr 11 2015 etc
drwxr-xr-x 4 root root 4096 Nov 22 2014 lib
lrwxrwxrwx 1 root root 11 Dec 30 2014 linuxrc -> bin/busybox
drwx------ 2 root root 16384 Jan 3 2008 lost+found
drwxr-xr-x 3 root root 4096 Dec 30 2014 mail
drwxr-xr-x 2 root root 4096 Aug 27 2008 nowhere
drwxr-xr-x 7 root root 4096 Dec 30 2014 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 Dec 30 2014 sbin
drwxrwxrwx 2 root root 4096 Mar 5 2011 share
drwxrwxrwx 2 root root 4096 Dec 30 2014 sys
drwxr-xr-x 22 root root 4096 Dec 30 2014 usr
drwxr-xr-x 2 root root 4096 Mar 9 2012 var

----------------------------------------------------------------

root@fvdw-sta-kirkwood:/sda7 # cat boot.log
cat: can't open 'boot.log': No such file or directory

-----------------------------------------------------------------

root@fvdw-sta-kirkwood:/ # dmesg | grep command
[ 0.000000] Kernel command line: console=ttyS0,115200 netconsole=6666@192.168.1.252/,6666@192.168.1.250/

Posted: **Mon Jan 25, 2016 3:08 pm**

Hi Balou911

You misunderstood what fvdw asked you about checking of the GPT support:
dmesg must not be done via the telnet access provided by fvdw-sl console but directly via a root shell access when the NAS is running in the regular mode.

So use your 1,5TB disk with the ms-dos partition table and after booting the NAS, open a shell window (for example with a SSH client like Putty)

Note: if you do not find boot.log in sda7 that would mean either the bootloader fails to detect the gpt disk or it fails to load the kernel from sda6 (<=> do not detect sda6 or the kernel is corrupted)

plugout.net

5Big Network 2 - doesn't respond after reboot -f

5Big Network 2 - doesn't respond after reboot -f

Re: 5Big Network 2 - doesn't respond after reboot -f

Re: 5Big Network 2 - doesn't respond after reboot -f

Re: 5Big Network 2 - doesn't respond after reboot -f

Re: 5Big Network 2 - doesn't respond after reboot -f

Re: 5Big Network 2 - doesn't respond after reboot -f