Lacie 2bign_v2 support

[wd9895]

Just bought a 2big2 3TB 2 discs for a very competitive price.
I'm curious if the firmware will run on this device somewhen.

[fvdw]

the kernel I made for 5big5 is suitable for 2big2 as well, I already adapted if for it.
Three things will need to be done, you will need
-the new kernel,
-an adapted default database
- fvdw-sl-14-1

We are still testing 14-1 for mutiple disks on Draftmancorp's nas.
But I will open a topic for 2big2 support and sent yu some files if you are willing to test it.
For installation we use the fvdw-sl-console
Alsoe there you will need another standalone kernel as the current one doesn't has support for port mutipliers which are used by 5big5. Don't know if the 2big2 uses them, it could also have just two sata ports

[Mijzelf]

There is something strange with the 2big2 regarding sata ports. A kirkwood has 2 sata ports, and this is the internal slot-to-diskname database from the GPL:

Code: Select all

/* internal disk map */

static struct lacie_disk net2big_v2_disks[] = {
        {
                .host_no = 0,
                .channel = 0,
                .id      = 0,
                .letter  = 'a',
        },
        {
                .host_no = 1,
                .channel = 0,
                .id      = 0,
                .letter  = 'b',
        },
};

If you compare this to the table of the 5big2, you'd say there are no port multipliers, as all channels on the 5big2 are >0. But the 2Big2 has also an esata port, so either an extra sata controller is used, or a port multiplier.
The 5big2 also has 2 esata ports, so maybe a multiplier has a channel 0, and are they used for esata on the 5big2.

[fvdw]

indeed could be as you described.
I used the same table as you posted in the kernel for the 2big2, so if wd9895 is willing to install it we will see.

[Jocko]

@fvdw

if wd9895 uses his NAS with RAID feature, he must deal with the fact that feature won't be restored for a long time ( at least 3 months)

[wd9895]

Cool, the drive is on its way to me. I will check the existing config and inform you here.
Raid is not the plan just a JBOD.

I would appreciate to testdrive the kernel, etc.

[Mijzelf]

JBOD is just another incarnation of RAID. In Linux it uses the same engine.

[fvdw]

was JBOD not an equivalent for "Just Another Bunch of Disks" accessed individual

[Mijzelf]

JBOD (Just a bunch of disks or Just a bunch of drives) is when a number of drives are used, but are not in a RAID configuration. The drives may be handled as separate logical volumes, or they may be combined into a single logical volume using a system like LVM.

Actually I knew it only in the last meaning, but not as LVM, but more as a 'pseudo raid level', as explained on pcguide.com.
Using mdadm you can create a JBOD by choosing raid level 'linear'.

But maybe wd9895 indeed meant he wants to access all disks individually. (All disks? Max 3). In that case there is no problem at all, I suppose.

[fvdw]

its up to him, adding raid support requires more time. But just using all the disk indivudually is already operational

@wd9895, let us know when you have your new toy and we can sent yopu same files for trial
ps you will need the fvdw-sl console installed in windows