Lacie 2bign_v2 support

[wd9895]

Ok, will let you know when the toy is available.

In principle I only want a the big bunch of capacity, no mirroring. Speed will be sufficiently be available as there are not more than 3 users working simoultanously on the drive.

So my wish: adressing the two drives as two shares or one share with the combined size of both drives. Any solution is welcome.

[Jocko]

So my wish: adressing the two drives as two shares or one share with the combined size of both drives. Any solution is welcome.

Hi wd9895

The version 14.1 beta used by Draftmancorp runs as the current firmware but now when you create a share you must select a disk. So if you make only one share by drive you get your wanted configuration

To merge the two disks and that they runs as there are only one, LV manager tools must be yet installed (but it's planned)

Currently I work on a script to update the disks configuration in the database to handle if you swap them or install a new disk.

[wd9895]

You deserve my full respect for this programmers work. I'd have no clue how to do it or would need weeks to understand this.

[wd9895]

Guys, I want to migrate to FVDW/JOCKO firmware as soon as possible. Lacie original FW sucks.
Yesterday I received the product, could not get it in the IP list of my router and made a factory reset. This took a few hours (!) du to Raid syncs (...)
My 2Big2 has FW2.28 and a capacity of 2,7 TB (reported).

Now the mess: the upgrade to FW 2.29.x went through to 100% but not successfully - it blinks red/blue/red/blue.

Fortunately the weekend will be rainy and I'm not in a hurry (wife, etc ;-)). So I will restore with fdisk the entire system or if possible install your alternativ kernel. Any help is welcome.

[fvdw]

this evening we will send you some files

[fvdw]

I will post files in minute.

What is the size of the disk you want to install ? I will prepare a default database for two disks. Currently the firmware doesn't support raid yet. You will see the disks as two individual. Anyhow as you are offline a prepared a database for 2 pcs 2 TB disk, but can be changed later easy and will also work with bigger or smaller disk. Only total size reading in some menu's will not be correct.
To get correct reading of the size we need to set the disksize manually in the database. Soon a script will come to do that automatically.

To install the firmware you need to use the fvdw-sl console and choose action install fvdw-sl firmware (read the help tekst in the separate help menu first...).
The disk you are going to use must be empty without partitions. if there are any you must delete them using either fdisk (for ms-dos tabel) or gdisk for GPT table. Both are include in the standalone kernel.

Put the standalone kernel (#108) that I will sent you in the tftp directory of the fvdw-sl console (this can be found in the directory were you installed the fvdw-sl console). Also put there the normal operation kernel (#109) and the database file (unpack the zip archives first of course)

Now connect your 2big2 to the network and put a disk in slot 1. Keep it switched off.
Choose the action install fvdw-sl firmware as action in the fvdw-sl menu
Pretend that you have a nwsp2
Choose the correct standalone kernel (the one I have sent you)
And wait until the command window comes up mentioning that it waits for u-boot.
Start the 2big2
It should be detected by the command window and it will interrupt boot and load the kernel. After that it will wait 12 seconds and then starts a telnet client that you can use to connect to the 2big2 running the standalone kernel.
Username: root
password: giveit2me
You will get a command prompt
If you disk is not empty you can now use fdisk or gdisk to delete the partitions (fdisk /dev/sda or gdisk /dev/sda to enter these programs give command p to show the partition table and use d command to delete any of them. After deleting them all give command w to leave fdisk or gdisk and write the new table to disk)

Now follow the rest of the instructions and let the installer script prepare your disk. Device id is sda, select do not make a backup of lacie partitions
if you disk is smaller then 2TB you can use either ms-dos partition bale or GPT, if it is bigger then 2 TB you must use GPT as partition table.
When the script mentions 100% completed do not reboot yet
We need to write a newer kernel to sda6 and replace the default database
To do this we upload the production kernel and the database via tftp

In the telnet client give the commands

Code: Select all

tftp -r UIMAGE-26394-NWSP2CL-109 -l UIMAGE-26394-NWSP2CL-109 -g ip-pc


replace "ip-nas" in this code by the actual ip address of your pc running the fvdw-sl console
write it to sda6

Code: Select all

dd if=UIMAGE-26394-NWSP2CL-109 of=/dev/sda6

upload the new database

Code: Select all

tftp -r nas_conf_db.xml -l nas_conf_db.xml -g ip-pc


replace "ip-nas" in this code by the actual ip address of your pc running the fvdw-sl console
Make a mountpoint for sda5

Code: Select all

mkdir /sda5

mount sda5

Code: Select all

mount /dev/sda5 /sda5

copy the database

Code: Select all

cp nas_conf_db.xml /sda5/etc/nas_conf_db.xml

umount sda5

Code: Select all

umount /sda5

Done reboot the nas to see if it accessible via fvdw-sl webinterface

Code: Select all

reboot -f

note that the normal kernel is not accessible on 192.168.1.252 or 0.252 it will have an ip address assigned by your dhcp server

let us know the result so far

write the new database
After that we reboot the box with command reboot -f in the telnet client.

[wd9895]

Hi Fvdw,

many thanks for the instructions and the file.
It looks maybe strange too you but first step for me is to backup existing partition tables (2x1,5 TB Seagates) to anyhow find back to Lacie original although it's not very likely.

The 2big2 now runs on latest FW quite fast and stable. The FW upgrade and (maybe) Raid re-sync simply takes much more time compared to NW2. It requires a few hours blinking red/blue. That's new to me.

So first challenge it to get root and to backup partitions. Do you have hints for this issue?

Remark to everyone who is interessted in buying these kind of models: it's rather fast but also louder than NW2. The blower is a bit annoying :(

[fvdw]

So first challenge it to get root and to backup partitions. Do you have hints for this issue?

You can use the standalone kernel uploaded and started via fvdw-sl console.That will give you telnet access (just like putty on nwsp2).
Now you have a linux command prompt.
You could back up the root partitions of lacie by using the dd command and store them in memory (they must ne smaller then 256 MB in that case)
then sent with the tftp to your windows pc. In fact the fvdw-installer script will do this when you answer yes to make backlups
If I remember wel you only need to make backups of sda6, sda7 and sda8
(sda1 is extended partition, sda9 is empty, sda5 is swap and sda2 is the big data partion containing the shares)
Maybe good before running the installer and auto backup to list the partition table here to see if it is the same as the other Lacie's (very likely)

[fvdw]

if you make the backups using the fvdw-sl installer script it might fail with a message that it can't mount sda9

In that case give command

Code: Select all

mknod -m 666 /dev/sda9 b 8 9

and try again
(sda9 is missing in the standalone kernel as device as it is not used by fvdw-sl firmware, small bug :mrgreen: )

[wd9895]

So, first feedback:
Confirm one disk is in the tray, no backup of LaCie FW required (still sucks)
console download & started: success
IP doesn't work on 192.168.0.252 or 192.168.1.252, my NAS has a fix address in the route so I took this.
Loaded standalone (108) image in console, Uboot, Telnet startet.
deleted all partitions with GDISK.

Existing one is (better was):

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 2930277168 sectors, 1.4 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 1C7384FE-830A-4343-A1FE-C2E1277D5279
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 2930277134
Partitions will be aligned on 2048-sector boundaries
Total free space is 31282 sectors (15.3 MiB)

Number Start (sector) End (sector) Size Code Name
1 4036608 4038655 1024.0 KiB 0700 primary
2 4048896 2930274575 1.4 TiB 0700 primary
3 4040704 4042571 934.0 KiB 0700 primary
4 4044800 4046848 1.0 MiB 0700 primary
5 2048 514047 250.0 MiB 0700 primary
6 530432 546497 7.8 MiB 0700 primary
7 546816 578945 15.7 MiB 0700 primary
8 579584 2266409 823.6 MiB 0700 primary
9 2267136 4018221 855.0 MiB 0700 primary
10 4020224 4036289 7.8 MiB 0700 primary

Loaded script, chmodded and started it: success
Answered questions:
- no partitions (new)
- smaller than 2TB
- GPT format

Script started, copied 14.0 image and the error message "writing firmware failed"
Script ends

Actual GPT table

Command (? for help): p
Disk /dev/sda: 2930277168 sectors, 1.4 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 1C7384FE-830A-4343-A1FE-C2E1277D5279
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 2930277134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number Start (sector) End (sector) Size Code Name
1 2048 1050623 512.0 MiB 8300 Linux filesystem
2 1050624 2099199 512.0 MiB 8300 Linux filesystem
3 2099200 3147775 512.0 MiB 8200 Linux swap
4 3147776 3164159 8.0 MiB 8300 Linux filesystem
5 3164160 4737023 768.0 MiB 8300 Linux filesystem
6 4737024 4753407 8.0 MiB 8300 Linux filesystem
7 4753408 5801983 512.0 MiB 8300 Linux filesystem
8 5801984 2930277134 1.4 TiB 8300 Linux filesystem

So, what went wrong in the script ?