5 Big Network 2 (Diskless) Factory Firmware Restore

[trisc]

Hello,

I have a Lacie 5 Big Network 2 (Diskless) with 2x WD Blue 500GB, 2x Seagate 3TB, 1x WD Blue 320GB drive.

At present the NAS is undetectable on my network (Linksys (DHCP server running on 192.168.1.xxx range), Windows 8 desktop, Windows 8 laptop and Windows XP laptop)

Troubleshooting performed so far

- NAS does not obtain an IP address from router (tested with multiple routers)
- NAS reset to factory defaults with data loss option and without data loss option. NAS was connected on the network and again direct to PC with cross over cable with no results
- Lacie Network Assistant (LNA) does not detect NAS, Recovery performed via LNA with NAS being detected briefly (during reboot after latest firmware was successfully uploaded to the device and device reboots. Shows up as nas-rescue for 15secs then goes away after NAS is fully initialized)
- Opened case with Lacie support, said the onboard OS is currupted and a re-flash is required. Device needs to be returned to them for fix. (I'm in Guyana and cost to ship back and forth is two high. No feasable since with the total cost can get a brand new device)

- Decide to install FVDW via the windows console
- this was successful using the WD 320GB drive and NAS is up and working perfectly
- Now here is where things get interesting the firmware is to notch hats off to you guys but i am looking to implement RAID 5 for use on this device so ventured into returning to Lacie's crappy firmware as you would say
- Went through the full works as stated in this post "http://plugout.net/viewtopic.php?f=26&t=1402"
- Latest files used with all commands and everything working to perfection but after the reboot NAS initializes with solid Blue LED at front, Solid blue led above bay 1 with disk present (tested with 320GB and 500GB drive on separate occasions)
- Also power switch at the back no longer works. Would need to power off by disconnecting the power cable fully.
- To return the power button functionality a recovery is done via LNA

- Would greatly apreciate your help with this.
- Not sure if the factory restore from above entry pertains to the diskless version.
- RAID functionality is required hence the return to Factory defaults

[fvdw]

mmm...difficult to say what is wrong, seems something is wrong with the disk setup. Did the formatting xfs succeeded ? and also writing the "lacie first boot string " ?

What does the blue led on the front do from power on until it gets steady ?

ps we plan to implement raid in the next release, but still quite some work needs to be done.

[rtcg0]

So this was exactly my issue. I could have wished for the OP to have responded and worked it out.


Brief:
I followed all of the instructions in all of the posts but can't get the 5BIG2 to appear on the network. Is there a way to use UBOOT to boot the Lacie OS and see the console so that I can diagnose what is going on?

Verbose:

I've been lurking here for quite a while but I'm going to need to ask for help. I would like to think that I've done my research and to the best of my ability, I've tried everything that has been suggested. My first attempt was to download the Lacie Crap 2.2.10.x disk image that was posted and 'dd' that to all of the drives. Inserting all of the disks and turning on the Lacie caused the front blue circle LED to come on solid and the five disks flickered and flashed for days as if they were rebuilding an array. I left it alone but could still not access/manage the Lacie device. My dhcpd service never gave an IP address to the Lacie's MAC address, using the Lacie network assistant found nothing and even assigning an IP address in my ARP table did no good. A Lacie network assistance recovery with the 2.2.10.1 capsule failed

SO.. I read all the pages of all the posts on how to return the crap Lacie OS("Firmware") back to the drives and built a master set of instructions that eliminated the instructionst that wouldn't apply to restoring the Lacie OS to new blank hard drives.

In preparation I got Mijzelf's disk images for the 2.2.9.2 version of the 5Big2, upgraded to FVDW version 16 (awesome upgrade, btw. I can use my own local subnet) and then I got busy following the following steps:

Code: Select all

Turn off Lacie 5big2

Connect the LAN1 port of the 5Big2 to the ethernet segment

Only insert ONE of the 5 disks in first(leftmost) slot. (This ensures that it is /dev/sda )

Start FVDW console

Load standalone kernel UIMAGE-3142-NWSP2CL-KIRKWOOD-24-standalone

Power on the 5Big2 when the fvdw console was waiting for uboot so that FVDW could interrupt the 5Big2 bootup and send the standalone kernel

Login with telnet client   root / giveit2me

Delete all partitions using gdisk

write to disk, exit, then come back in to gdisk (This ensures previous partitions weren't 'remembered')

Create a new GPT partition table (Follow the outlined steps to make sda5 (256Meg swap), sda6 (16Meg ??), sda7(16Meg ??), sda8(884Meg OS partition), sda9(884Meg OS parition), sda10(a 16Meg partition to fill with zeros), and then the data partition sda2 (to use the rest of the disk and be formated with xfs)

GPART keystrokes:
Command (? for help): n
5
(accept the default first sector by pressing enter)
+256M
8200

n
6
(accept the default first sector by pressing enter)
+16M
(accept the default by pressing enter)

n
7
(accept the default first sector by pressing enter)
+16M
(press enter)

n
8
(accept the default first sector by pressing enter)
+884M
(press enter)

n
9
(accept the default first sector by pressing enter)
+884M
(press enter)

n
10
(accept the default first sector by pressing enter)
+16M
(press enter)

n
2
(accept the default first sector by pressing enter)
(accept the default last sector by pressing enter)
(press enter)



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

Ensure a correct parition layout before writing to disk...

###
Disk /dev/sdb: 976773168 sectors, 465.8 GiB
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 976773134
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
   2         4245504       976773134   463.7 GiB   8300  Linux filesystem
   5            2048          526335   256.0 MiB   8200  Linux swap
   6          526336          559103   16.0 MiB    8300  Linux filesystem
   7          559104          591871   16.0 MiB    8300  Linux filesystem
   8          591872         2402303   884.0 MiB   8300  Linux filesystem
   9         2402304         4212735   884.0 MiB   8300  Linux filesystem
  10         4212736         4245503   16.0 MiB    8300  Linux filesystem

Command (? for help):
###


Then Write the partition table


Format some partitions

###
mke2fs-64 -j -m 1 /dev/sda7
mke2fs-64 -j -m 1 /dev/sda8
mke2fs-64 -j -m 1 /dev/sda9
###

Send mkfs.xfs to the 5Big2

###
tftp -l /sbin/mkfs.xfs -r mkfs.xfs -g pc-ip
###


Make the 'mkfs.xfs' program executable
###
chmod 755 /sbin/mkfs.xfs
###

Send the mkfs.xfs libraries to the  5Big2
###
tftp -l /glibc-mini-mkfs.xfs-25feb14.tar -r glibc-mini-mkfs.xfs-25feb14.tar -g pc-ip
###

Extract the library files
###
tar -C / -xvf glibc-mini-mkfs.xfs-25feb14.tar
###


NOW format partiton 2 with XFS (included -f for force in case this is ever a redo and the filesystem already exists)

###
mkfs.xfs -f /dev/sda2
###



Place the Lacie OS partition backups from Mijzelf into the TFtp directory on the FVDW console host computer

#prep and use /dev/sda2 as a work space because we are going to have to expand Mijzelf's partition backups and this would probably overwhelm the consoled root (/) partition

###
mkdir /sda2 ; mount /dev/sda2 /sda2 ; cd /sda2
###

Begin sending the partition images from the TFTP server into our working directory and begin restoring them to their rightful places--


--Restore partition sda7--
Make a directory, mount partition sd7 (Using absolute paths as we are sitting in /sda2)

###
mkdir /sda7
mount /dev/sda7 /sda7


Retrieve the partition7 file from the TFTP directory and place it in the current /sda2 directory on the 5Big2
###
tftp -l sda7.txz -r sda7.txz -g ip-pc
###

Make the sda7 partition image extractable by the busybox xz program which requires the .xz extension, use xz to decompress it to a plain tar
and then use tar to extract the archive and send the contents to the proper place (Note: the single line command  xz -d sda7.txz | tar -C /sda7 -xvf -   SHOULD have worked but I think the busybox xz and tar are extra finiky)
###
mv sda7.txz sda7.xz
xz -d sda7.xz
tar -C /sda7 xvf sda7
###

Once successful, unmount /dev/sda7 and remove the sda7 tar file from the working directory

###
umount /sda7
rm sda7
###

Repeat for partition 8


--Restore partition sda8--
Make a directory, mount partition sd7 (Using absolute paths as we are sitting in /sda2)

###
mkdir /sda8
mount /dev/sda8 /sda8


Retrieve the partition7 file from the TFTP directory and place it on the 5Big2
###
tftp -l sda8.txz -r sda8.txz -g ip-pc
###

Make the sda7 partition image extractable by the busybox xz program, use xz to decompress it to a plain tar
and then use tar to send the archive to the proper place
###
mv sda8.txz sda8.xz
xz -d sda8.xz
tar -C /sda8 xvf sda8
###

Once successful, unmount /dev/sda8 and remove the sda8 tar file from the working directory

###
umount /sda8
rm sda8
###


Place the Lacie Kernel -- sda6-5big2.img  -- into the tftp directory

Retrieve kernel's partition then extract it (Note: We are still in the working directory /sda2 )
###
tftp -l sda6.gz -r sda6.gz -g ip-pc
gunzip sda6.gz
###

Now write the extracted kernel image to the 5big2's sda6 partition
###
dd if=sda6 of=/dev/sda6
###

Remove the kernal image file (specifying absolute paths for safety)
###
rm /sda2/sda6
###


Zero out everything in sda10 with the command...

###
dd if=/dev/zero of=/dev/sda10
###



NOTE: Lacie writes the UUID of the disk into the TRUE firmware of the 5Big2 hardware so that if the UUID of the disk volume doesn't match, the system will not use that lacie device.  If we Write a particular string to the disk, then the when the crapy Lacie firmware (Which is actually software) boots it will
cause the box to go into a destructive  new-setup mode and update the firmware with the UUID of the disk volume

Write the Lacie initial setup flag to the disk with

###
echo "LaCieFirstBootLaCie" | dd  of=/dev/sda
###

umount all volumes and power off.

Switch disks and repeat on each disks. (11 minutes per disk is what it took me in addition to the little nap I took due to the boredom.)


So now I'm back to having a solid front LED blue circle with all five lights blinking away like mad doing some big disk activity.
After inserting all five disks (which are mirror duplicates of each other) I booted up the Lacie 5Big2 with the FVDW UBoot Console. Things seemed to go well but now I'm back to having a solid front LED blue circle with all five lights blinking away like mad doing some big disk activity. If I let it sit for days, the lights will probably stop and I'll be left with a brick that has solid blue lights.

Here is text form my UBoot console

Code: Select all

All five drives restored to Crapy Lacie Firmware

provided by fvdw
waiting for u-boot..
starting u-boot net console click on window and press enter


Marvell>>

Marvell>> ide reset
ide reset

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
Port Multiplier found @ 0 0. Vendor: 11ab ports: 4
[0 0 1]: Enable DMA mode
  Device 1 @ 0 0 1:
Model: ST2000DM001-1CH164                       Firm: CC26     Ser#:
 S1E1S1KP
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-0 x 0)
[0 0 2]: Enable DMA mode
  Device 2 @ 0 0 2:
Model: ST2000DM001-1CH164                       Firm: CC26     Ser#:
 S1E1RKZR
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-0 x 0)
[0 0 3]: Enable DMA mode
  Device 3 @ 0 0 3:
Model: ST2000DM001-1CH164                       Firm: CC29     Ser#:
 W1F4HVEK
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-0 x 0)
Port Multiplier found @ 0 1. Vendor: 11ab ports: 4
[0 1 1]: Enable DMA mode
  Device 5 @ 0 1 1:
Model: ST2000DM001-1CH164                       Firm: CC29     Ser#:
 W340BGV7
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-0 x 0)
[0 1 2]: Enable DMA mode
  Device 6 @ 0 1 2:
Model: ST2000DM001-1CH164                       Firm: CC29     Ser#:
 W340BMJA
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-0 x 0)

Marvell>>
Marvell>> bootd
bootd
## Valid EFI partition found ##

Loading from IDE device 3, partition 10: Name: gpt10
  Type: U-Boot

** Bad Magic Number **
## Valid EFI partition found ##

Loading from IDE device 2, partition 10: Name: gpt10
  Type: U-Boot

** Bad Magic Number **
## Valid EFI partition found ##

Loading from IDE device 1, partition 10: Name: gpt10
  Type: U-Boot

** Bad Magic Number **
## Valid EFI partition found ##

Loading from IDE device 6, partition 10: Name: gpt10
  Type: U-Boot

** Bad Magic Number **
## Valid EFI partition found ##

Loading from IDE device 5, partition 10: Name: gpt10
  Type: U-Boot

** Bad Magic Number **
## Valid EFI partition found ##

Loading from IDE device 3, partition 6: Name: gpt6
  Type: U-Boot
   Image Name:   Linux kernel-2.6.31.14-svn6790 [
   Created:      2013-04-12  19:32:20 UTC
   Image Type:   ARM Linux Multi-File Image (uncompressed)
   Data Size:    5545903 Bytes =  5.3 MB
   Load Address: 00008000
   Entry Point:  00008000
   Contents:
   Image 0:  3003728 Bytes =  2.9 MB
   Image 1:  2542163 Bytes =  2.4 MB
   Verifying Checksum ... OK
OK
bootargs from environment variables : console=ttyS0,115200 root=/dev/sda7 ro res
et=0 productType=BIG5_KW cap=gpt,lba64

Starting kernel ...



What now? I'm clueless how to proceed.

[fvdw]

Most likely something might be wrong with the partition image you use. try to use the ones included in the attached archive, they have been used successfully and are not in xz format, they are already gz.
Im not sure if the xz command of the standalone kernel is ok, (it should but I never used it)

Further this puzzle me
You seem to have prepared disk sdb instead of sda ??

Code: Select all

###
Disk /dev/sdb: 976773168 sectors, 465.8 GiB
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 976773134
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
   2         4245504       976773134   463.7 GiB   8300  Linux filesystem
   5            2048          526335   256.0 MiB   8200  Linux swap
   6          526336          559103   16.0 MiB    8300  Linux filesystem
   7          559104          591871   16.0 MiB    8300  Linux filesystem
   8          591872         2402303   884.0 MiB   8300  Linux filesystem
   9         2402304         4212735   884.0 MiB   8300  Linux filesystem
  10         4212736         4245503   16.0 MiB    8300  Linux filesystem

Command (? for help):
###


Then Write the partition table


Then you format sda

Code: Select all

Format some partitions

###
mke2fs-64 -j -m 1 /dev/sda7
mke2fs-64 -j -m 1 /dev/sda8
mke2fs-64 -j -m 1 /dev/sda9
###

furthermore in the output of u-boot I see this

Code: Select all

  Device 3 @ 0 0 3:
Model: ST2000DM001-1CH164                       Firm: CC29     Ser#:
 W1F4HVEK
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1907729.0 MB = 1863.0 GB (-0 x 0)

This sda why does it here mention 2 TB, your gdisk output talks about a 500 GB disk ??

seem you have copied some parts from the how-to.txt file ;)

One thing more if you follow to how-to.txt instruction also rmemeber this

Code: Select all

One thing more. do not insert more then 1 disk, use only a disk in first slot (sda)

iwrite this to sda first sector


echo "LaCieFirstBootLaCie" | dd  of=/dev/sda

[rtcg0]

I believe I did paste something incorrectly. Sorry. I was documenting so many things. I will re-extract your images and do the procedure again. The raid array rebuild seems to have completed. I will take a look at it via mdadm when I boot the stand alone kernel.

Thank you fvdw.

[fvdw]

;) ok
Please note that the procedure on plogout to restore the lacie firmware mentions to use 1 disk only. And add the other disks later

[rtcg0]

Use one disk only? Well, I used one disk at a time and then I put them ALL in and turned on the 5Big2.

Using your partition backups, the Lacie came to life. The raid5 array for the sda2 partition is in the process of being rebuilt. Since the GPT partitions had been previously defined, I didn't bother with redoing the partitioning steps. The modified steps I took were as follows:

Downloaded and extracted the partition backups, placed them in my TFTP download folder, extracted the 5big2-sc1.zip into the TFTP download folder and pasted the following into the console (using a valid Ip address to match my TFTP host)

Code: Select all

#retrieve needed utilities and libraries
tftp -l /sbin/mkfs.xfs -r mkfs.xfs -g 192.168.my.ipaddress
chmod 755 /sbin/mkfs.xfs
tftp -l /glibc-mini-mkfs.xfs-25feb14.tar -r glibc-mini-mkfs.xfs-25feb14.tar -g 192.168.my.ipaddress
tar -C / -xvf glibc-mini-mkfs.xfs-25feb14.tar

#Format/reformat the partitions
mke2fs-64 -j -m 1 /dev/sda7
mke2fs-64 -j -m 1 /dev/sda8
mke2fs-64 -j -m 1 /dev/sda9
mkfs.xfs -f /dev/sda2


#Prep sda7
tftp -l 5big2-sda7.img -r 5big2-sda7.img -g 192.168.my.ipaddress
dd if=5big2-sda7.img of=/dev/sda7
rm 5big2-sda7.img


#prep sda8
mkdir /sda8
mount /dev/sda8 /sda8
tftp -l 5big2-sda8.tgz -r 5big2-sda8.tgz -g 192.168.my.ipaddress
tar -C /sda8 -zxvf 5big2-sda8.tgz
umount /sda8
rm 5big2-sda8.tgz

#prep sda6
tftp -l 5big2-sda6.img -r 5big2-sda6.img -g 192.168.my.ipaddress
dd if=5big2-sda6.img of=/dev/sda6
rm 5big2-sda6.img

#write a Lacy signature to the disk (This seems redundant as we are going to rewrite over this in a second)
tftp -l 5big2-sc1.img -r 5big2-sc1.img -g 192.168.my.ipaddress
dd if=5big2-sc1.img of=/dev/sda bs=1 count=16
rm 5big2-sc1.img

#zero out the data on partition sda10
dd if=/dev/zero of=/dev/sda10

#Tag the drive with the Lacie first boot signature
echo "LaCieFirstBootLaCie" | dd  of=/dev/sda



Interestingly enough, before I started the procedure, I took a look at the disk arrays that Mijzelf's disk images produced. here is what it looked like.

Code: Select all

root@fvdw-sta-kirkwood:/sbin # mdadm --assemble --scan
mdadm main: failed to get exclusive lock on mapfile
mdadm: /dev/md/2_0 has been started with 5 drives.
mdadm: /dev/md/1_0 has been started with 5 drives.
mdadm: /dev/md/3_0 has been started with 5 drives.
mdadm: /dev/md/0_0 has been started with 1 drive (out of 5).
mdadm: /dev/md/(none):4 has been started with 5 drives.

root@fvdw-sta-kirkwood:/sbin # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
md123 : active raid5 sda2[0] sde2[4] sdd2[3] sdc2[2] sdb2[1]
      7805569024 blocks super 1.0 level 5, 512k chunk, algorithm 2 [5/5] [UUUUU]
      [>....................]  resync =  0.1% (3681988/1951392256) finish=1306.8min speed=24838K/sec
     
md124 : active raid1 sda7[0]
      16320 blocks [5/1] [U____]
     
md125 : active raid1 sda5[0] sde5[4] sdd5[3] sdc5[2] sdb5[1]
      255936 blocks [5/5] [UUUUU]
     
md126 : active raid1 sda8[0] sde8[4] sdd8[3] sdc8[2] sdb8[1]
      843328 blocks [5/5] [UUUUU]
     
md127 : active raid1 sda9[0] sde9[4] sdd9[3] sdc9[2] sdb9[1]
      875456 blocks [5/5] [UUUUU]
     
unused devices: <none>


md126? really? I had to run udevstart to get the system to create the /dev/nodes for those devices then I was able to mount them and poke around. I didn't learn anything useful.

Thank you for the partition backups, fvdw. And for the tools. I had offered my friend the fvdw firmware but the RAID and Timemachine backup destination feature required him to use the Crappy Lacie Software