General NAS-Central Forums

Welcome to the NAS community
It is currently Sun Oct 22, 2017 2:42 am

View unanswered posts | View active topics


Board index » Hardware » Lacie » 2big Network

All times are UTC




Post new topic Reply to topic  Page 2 of 2
  [ 25 posts ]  Go to page Previous  1, 2
  Previous topic | Next topic 
Author Message
danyboy666
PostPosted: Thu Dec 10, 2015 4:54 am 
Offline

Joined: Sat Dec 05, 2015 9:31 pm
Posts: 16
fvdw wrote:
two things

Quote:
Is it possible the NAS U-boot isn't compatible with the 2.2.3 firmware?

u-boot just loads a kernel and a kernel command line, the kernel loads the boot scripts from lacie inside the root file system, so in principle u-boot is compatible with any version of the firmware as long as the kernel and root file system are on the correct place

Next I looked somewhat closer to your demsg output and see this
Code:
[   16.920514] CPU: Testing write buffer coherency: ok
[   16.924094] NET: Registered protocol family 16
[   16.928174] Orion ID: MV88F5182-A2. TCLK=166666667.

Notice the orion ID
This means don't have a 2big_v2 but a older orion based 2big_v1, or you have a replace motherboard inside this nas.
A 2big_v2 has a kirkwood processor with ID MV88F6182
You can check easily if you open it and look on the code on the processor, if it mentions 5182 then it is an orion based 2big_v1
It must mention this otherwise kernel won't run and won't gives this cpu id

Of course firmware and installation instructions for 2big_v2 will not work on this device ;)


These are the images i've been using for my 2Big Network procedure all along
http://downloads.lacie.nas-central.org/Users/Mijzelf/2big/Partitions%202.2.3/
Code:
mbr+label.gz   269   2012-Feb-02 19:59
sda6.gz   2062440   2012-Feb-02 19:35
sda7.tgz   2587888   2012-Feb-02 19:36
sda8.tgz   42059420   2012-Feb-02 19:45


I knew from the start i had a 2Big Network 1 see post #1 :) "2BIGV2NAS" model "LAC301421U" but i've been using http://lacie.nas-central.org/wiki/Installing_firmware_on_fresh_disks_(2Big_2)#Create_partitions prodecure with those image files.

I noticed it woudn't work as soon i saw the NAS trying to rewrite one disk at boot...

Code:
Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb1               1         125     1004031   5 Extended
/dev/sdb2             126       30401   243191970  83 Linux
/dev/sdb5               1          16      128457  82 Linux swap
/dev/sdb6              17          17        8001  83 Linux
/dev/sdb7              18          18        8001  83 Linux
/dev/sdb8              19          40      176683+ 83 Linux
/dev/sdb9              41         124      674698+ 83 Linux
/dev/sdb10            125         125        8001  83 Linux


The only thing i lack i think is the proper partition table and images files for the V1 NAS.

There i saw Mijzelf files http://downloads.lacie.nas-central.org/Users/Mijzelf/

Code:
Parent directory/   -   -
2big/   -   2012-Feb-02 19:35
2big2/   -   2011-May-28 11:48
5Big/   -   2011-Oct-22 09:53
5Big2/   -   2013-May-10 16:02
D2Network2/   -   2012-Oct-16 09:59
EdMini/   -   2010-Dec-16 14:50
EdMiniV2/   -   2010-Nov-23 20:53
Ethernet Big Disk/   -   2011-Mar-10 21:20
FFP-Capsule/   -   2012-Jul-11 19:27
Networkspace/   -   2011-May-21 07:40
Networkspace Max/   -   2013-Mar-23 11:30
Networkspace2/   -   2014-Feb-05 16:36
tmp/


http://downloads.lacie.nas-central.org/ ... zelf/2big/

Quote:
Partitions 2.2.3/ - 2012-Feb-02 19:59
2big_uImage_modules.tar.gz 3263855 2011-Oct-09 14:00
md0.gz 2274250 2010-Mar-21 13:27
md1.gz 52665297 2010-Mar-21 13:39
sda6.gz


http://downloads.lacie.nas-central.org/ ... s%202.2.3/

Code:
checksums.md5   175   2012-Feb-02 20:04
mbr+label.gz   269   2012-Feb-02 19:59
sda6.gz   2062440   2012-Feb-02 19:35
sda7.tgz   2587888   2012-Feb-02 19:36
sda8.tgz


What should i use ?

These seem right to me but i did not see a procedure or partition table to know how to use them... Like i've said there are bits of procedures here and there but nothing conslusive enough that i can follow. I looked literaly all over the internet. Either the files are gone, web site goes 404 or i find right files but without valid procedure to get me doing.

Code:
md0.gz   2274250   2010-Mar-21 13:27
md1.gz   52665297   2010-Mar-21 13:39
sda6.gz   2067435   2010-Mar-21 13:30


I'm experimeting alot but not enough it seems...

p.s. I'm glad you took the time to look at this again :).
Top
 Profile  
 
danyboy666
PostPosted: Sat Dec 12, 2015 6:08 pm 
Offline

Joined: Sat Dec 05, 2015 9:31 pm
Posts: 16
I'm guessing no one wants to help me with this. This topic can be closed thanks.
Top
 Profile  
 
fvdw
PostPosted: Sat Dec 12, 2015 10:51 pm 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 773
well sometimes you must have a little patience ;) we have also other things to take care off

You must have the files from the 2big/ folder of Mijzelf
The installation proces is almost the same as for 2big2.

Here you can find a how-to
viewtopic.php?p=4881#p4881
You can use the sda6,7 and 8 files from mijzelf or try to get them following the links in the link provide (if they still work)

Don't give up so easy :D

ps you also could consider to use the fvdw-sl firmware. (http://plugout.net)
Top
 Profile  
 
danyboy666
PostPosted: Sun Dec 13, 2015 8:19 pm 
Offline

Joined: Sat Dec 05, 2015 9:31 pm
Posts: 16
Yeah i have a short temper i have to admit but as for patience i have lots of it since i started in IT :P

I'll try the method you linked me to altough i'm pretty sure i've already tried it but with the wrongs images files. It resulted in partitions size not being big enough though but it think i was using the NAS default partition table which may have been incorrect after all.

Code:
Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb1               1         125     1004031   5 Extended
/dev/sdb2             126       30401   243191970  83 Linux
/dev/sdb5               1          16      128457  82 Linux swap
/dev/sdb6              17          17        8001  83 Linux
/dev/sdb7              18          18        8001  83 Linux
/dev/sdb8              19          40      176683+ 83 Linux
/dev/sdb9              41         124      674698+ 83 Linux
/dev/sdb10            125         125        8001  83 Linux


I'll quote the method you linked here me to so i can easily find it back ;)

Code:
I did some more digging on the internet and I believe I found valuable information. I do not know if the procedure below works but I am sure it is worth a try and I would like to hear from people that tried it here. Bear in mind that the procedure is a bit hardcore for Linux newbies, however with some effort it is doable.
The guide below is inspired by this thread in a german NAS forum: http://forum.nas-portal.org/showthread.php?t=6864

What you’ll need
2 SATA drives unformatted and unpartitioned of the same size
2 SATA ports in a computer
A computer running Ubuntu or a Windows computer with a virtual Ubuntu machine

Preparation
If you run Windows I suggest you install Virtualbox and create a virtual Ubuntu machine. It is necessary for the process of creating the Lacie 2big Network RAID and image transference. If you don’t know how to do that you’ll have to investigate on the internet. There are several guides available online. Google is your friend. ;-)

Partitioning
Start the Ubuntu operating system and connect both SATA drives to your computer (one at a time or both at the same time, it does not matter in this step). Open GParted and make sure the drives were recognized (they are recognized if they appear in the device list in GParted).
Let’s say you connected both drives at the same time and the drives were recognized and appear as /dev/sda and /dev/sdb in the GParted device list.
Create the partitions following the scheme below:

/dev/sda
sda1: Extended Partition – size: 1GB (this partition will hold other system partitions)
sda2: Primary Partition – size: rest of the drive (this partition contains userdata)
sda5: SWAP Partition – size: 128MB (this partition is to be created inside the extended partition)
sda6: uImage – size: 8MB (this partition is to be created inside the extended partition)
sda7: rootfs Image – size: 8 MB (this partition is to be created inside the extended partition)
sda8: rootfs (Overlay) Image – size: 173MB (this partition is to be created inside the extended partition)
sda9: Rest of extended partition – size: rest of the extended partition (this partition is to be created inside the extended partition)

/dev/sdb
sdb1: Extended Partition – size: 1GB (this partition will hold other system partitions)
sdb2: Primary Partition – size: rest of the drive (this partition contains userdata)
sdb5: SWAP Partition – size: 128MB (this partition is to be created inside the extended partition)
sdb6: uImage – size: 8MB (this partition is to be created inside the extended partition)
sdb7: rootfs Image – size: 8 MB (this partition is to be created inside the extended partition)
sdb8: rootfs (Overlay) Image – size: 173MB (this partition is to be created inside the extended partition)
sdb9: Rest of extended partition – size: rest of the extended partition (this partition is to be created inside the extended partition)

Do not format any of the partitions yet. Leave them as unallocated. Formatting will be done later.

Creating the RAID array
Lacie made its product so that it only recognizes the drives if they are configured in a RAID array. Simply copying the images to both drives won’t work.
To create the RAID array connect both partitioned drives at the same time in the Ubuntu machine. Let’s say they are recognized as /dev/sda and /dev/sdb.
Open a terminal window in Ubuntu and use the following commands to create the RAID arrays:

Code:
sudo mdadm -create /dev/md0 -level=1 raid-devices=2 /dev/sda7 /dev/sdb7
sudo mdadm -create /dev/md1 -level=1 raid-devices=2 /dev/sda8 /dev/sdb8
sudo mdadm -create /dev/md2 -level=1 raid-devices=2 /dev/sda9 /dev/sdb9
sudo mdadm -create /dev/md3 -level=1 raid-devices=2 /dev/sda5 /dev/sdb5
sudo mdadm -create /dev/md4 -level=1 raid-devices=2 /dev/sda2 /dev/sdb2


If everything went well you shold have the arrays created now on /dev/md0 to /dev/md4.

Copying the images
Now we have to copy the Lacie images to the RAID array. Get the images at the following addresses:

http://www.reparix.ch/bilder/sda6.bz2
http://www.reparix.ch/bilder/sda7.bz2
http://www.reparix.ch/bilder/sda8.bz2

Untar this file and you’ll have three files: sda6, sda7 and sda8. These images are to be transferred to the RAID array.
Open a terminal window in Ubuntu and use the following commands to transfer the images to the RAID array:

Code:
sudo dd if=sda6 of=/dev/sda6
sudo dd if=sda6 of=/dev/sdb6
sudo dd if=sda7 of=/dev/md0
sudo dd if=sda8 of=/dev/md1


After this we should have the images transferred. Now we have to create the filesystems that are still missing in the RAID array. Open a terminal window in Ubuntu and use the following commands to create the filesystems:

Code:
sudo mkswap /dev/md3
sudo mkxfs /dev/md4
sudo mke2fs-j /dev/md2


Now everything should be fine. Just install the drives in the Lacie 2big Network NAS and hope for the best. :-D
I have not tested this procedure yet. I intend to do so, but if anyone can test it and post back I would appreciate.


Links in that post were outdated. Also i'm not really sure abouth using 2.2.3 images files from Mijzelf for such an old version of this NAS. I'll try to find the original image files from that topic

http://www.reparix.ch/bilder/sda6.bz2
http://www.reparix.ch/bilder/sda7.bz2
http://www.reparix.ch/bilder/sda8.bz2

btw it would be great if somebody would still have a link for those.

The closest i've found were edmini v2 images files. http://gpl.nas-central.org/LACIE/ethernet_disk_mini_v2_-_ethernet_big_disk/EDmini_v2_partition_images/

If i use those will i be able to update with a real 2Big Network v1 FW later on?

Anywais i'll give it a shot again and report back with some results.

In the meanwhile i've ordered 2 1TB WD Blue from amazon. I know i should have gone with WD Red which are designed to be NAS specifics but i've figured sine this NAS is already 6 year old and only have S-ATA 2 controller speeds Blue HDD's shouldn't be a problem. I'd like your thoughts on that matter.

You help is really appreciated. Something it's good to have a second set of eyes for these kind of things.

Also i will definitly come to use your firmware if i really can't get Lacie own firmware to work on this NAS. It really seem useful to lots of people out there. I usually like to test out the real FW beforehand and decide if i need more features or not afterwards.
Top
 Profile  
 
danyboy666
PostPosted: Fri Dec 18, 2015 11:50 pm 
Offline

Joined: Sat Dec 05, 2015 9:31 pm
Posts: 16
I give up on lacie firmware. I feel like i'm doing all this work and at the end it'll be limited as hell with functionalities. Maybe i should try with my new disks but smart tells me my seagates are good so i'm not risking me new WDs in this piece of crap.

How can i install your fimware from CLI since i can't get lacie firmwareup and running?
Top
 Profile  
 
fvdw
PostPosted: Sat Dec 19, 2015 9:57 am 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 773
I suggest you register at plugout.net and download the fvdw-sl console to install it. This console is running on a pc with windows OS connected to the same LAN

http://plugout.net
Top
 Profile  
 
danyboy666
PostPosted: Sun Dec 20, 2015 5:02 am 
Offline

Joined: Sat Dec 05, 2015 9:31 pm
Posts: 16
fvdw wrote:
I suggest you register at plugout.net and download the fvdw-sl console to install it. This console is running on a pc with windows OS connected to the same LAN

http://plugout.net


After trying about a hundred time restoring the original LaCie images and with equal attempts failed I finaly gave up and tried your installer. I got it on first try but after i sent the command to reboot the NAS is still unresponsive.

edit:

On second try i got it (still trying to figure out what was wrong with first try)... Anywais i'm in the web interface right now so that's a win :)
Top
 Profile  
 
danyboy666
PostPosted: Sun Dec 20, 2015 7:27 pm 
Offline

Joined: Sat Dec 05, 2015 9:31 pm
Posts: 16
I tought your firwmare had raid support. I read in 16.0.3 release note that it was suppose to have setup available from the web interface for RAID1 in version 16.1 but i have also read 16.1 release note and you still need to set it up manually?

http://plugout.net/viewtopic.php?f=7&t=2313

How can i be sure i set my disk as RAID1 correctly without screwing up my install? Do i only need to create sdb8 partition or do i have to copy the whole partition table without copying fvdw files to the second disk from sda to sdb and set up a raid only for partition sd[ab]8 partition?

What happens if my install goes bad? Let say i lose /dev/sda for some reason since i don't have your firmware install on sdb i will lose the nas again and then I will need to go thru the step to reinstall your firmware again to recover my data from sdb8?

In reality this does not fit my description for a RAID1 setup. Can you explain this to me? Maybe i got this wrong though.


Last edited by danyboy666 on Sun Dec 20, 2015 8:34 pm, edited 2 times in total.

Top
 Profile  
 
fvdw
PostPosted: Sun Dec 20, 2015 8:05 pm 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 773
Yes raid still needs manual install, we didn't find time yet to complete the web interface for that.
I suggest you put the questions on raid on the plugout forum. The expert Jocko is very familiar with raid and can give you the help you need. I do not use raid myself as I do not see much advantage of it but can give a lot of headache if the array fails for whatever reason
Top
 Profile  
 
danyboy666
PostPosted: Sun Dec 20, 2015 8:28 pm 
Offline

Joined: Sat Dec 05, 2015 9:31 pm
Posts: 16
Well the principle for having RAID1 NAS is exactly for that purpose. In case a HDD fails... The RAID1 is easily recoverable but a reinstall of the whole nas can be quite a chore. RAID is a security for our data which is exactly what we need with those devices. If a HDD fail without a RAID we can't recover our data at all... just a thought.

On the other hand i want to say thanks and congrats for your firmware. It is a nice piece of software. They are much needed tools which LaCie would never have implemented in the first place in their FW. But It only missing RAID built-in imh. Even if you don't see the utility for it it's still is must have feature for fvdw i'm pretty sure others will agree. As i mentioned a HDD can fail at anytime for multiple reasons but a RAID is easily recoverable even if it fails at least our data is safe. At least it can be mounted on any debian distro if the worst happens.
Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  Page 2 of 2
  [ 25 posts ]  Go to page Previous  1, 2

Board index » Hardware » Lacie » 2big Network

All times are UTC


Who is online

Users browsing this forum: No registered users and 9 guests

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
cron
Powered by phpBB® Forum Software © phpBB Group