June 28th, 2014 // 8:31 pm @ Andrew Preece
While working on-site with a customer, I was attempting to upgrade the firmware in the LaCie 2Big Network 2 NAS.
These units have a bit of a reputation for issues after upgrading the firmware, and this one was no exception.
After applying the update, the web interface displayed a messages along the lines of “completion is taking too long. Please check the IP address in use”.
Frustratingly, one of the issues in the release notes addresses the use of static IP addresses on these devices.
Once it became evident that the unit wasn’t going to reboot, all hope of a quick recovery on-site vanished and I was left with no choice but to take the unit off the customers site and into the workshop.
After attempting a number of the knowledge base articles on LaCie’s website, including this one: https://www.lacie.com/no/support/support_manifest.htm?id=10477&article=1394, I Google’d a little more broadly and found this article:Â https://www.rh-webs.net/2009/08/the-great-lacie-1tb-big-disk-recovery-experiment/
Assuming the LaCie 2Big Network 2 was built along similar lines, I was able to remove the two drives, still in their cradles (not voiding the warranty), and using an old PC with on-board SATA and an Ubuntu Live CD, I was able to follow along with almost the same steps as Mycroft and recover the data.
I will give a little bit more info regarding the specifics for the LaCie 2Big Network 2 as there are some useful hints to actually finding your data.
- Get yourself an Ubuntu Live CD:Â http://www.ubuntu.com/download/desktop.Â I used the 32-bit build as I knewÂ it will work on theÂ hardware I had kicking around.
- Grab your LaCie drives out of the chassis, but do not remove them from their LaCie cradles… there is a “Warranty Void” sticker over one of the screws. Â Don’t forget to label them in some way to ensure the left drive goes in back in the left-hand slot and the right to the right.
- Connect both the drives to your PC using SATA cables and power connectors – I used SATA 1 and SATA 2 on the Asus motherboard I had, and then connected a SATA DVD drive to SATA 6 to allow me to quickly boot and run the Ubuntu Live CD.
- Boot the Ubuntu Live distort and select “Try Ubuntu” mode when presented with the chance.
- From the Dash Home, type “Terminal” into the Search bar and open “Terminal”. Â This is an easy way to access theÂ CLI for Ubuntu – called a shell (as opposed to a DOS Prompt!).
- Once you have “root” access to the server, which you need to do low-level disk commands that we will be entering later, execute the following commands.
sudo apt-get install gparted
- You can then start “gparted”, or else just use the built-in “fdisk” tools to examine the partitions on the drives pulled from the LaCie.
I found that there are a series of partitions, but the one you are most interested in are the largest ones on the physical drives. Â For me, they were /dev/sda2 and /dev/sdb2.
sudo apt-get install mdadm
- When installing mdadm, you can safely select “No Configuration” for the postfix component of the installation. Â mdadmÂ will take a little while to analyse the disks and work out which ones are configured and what drives are present.
mdadm –query /dev/sda2
- This shows that this drive was the secondÂ member of a RAID0 software RAID device on a previous Linux installation. Â This is good news. Â Running the same command on the other partition, /dev/sdb2, showed that it was the first member of the same software RAID device.
mdadm -A /dev/md5 /dev/sdb2 /dev/sda2
- This will recreate the RAID0 stripe that was in place in the LaCie. Â Once the drives are back functioning as a software RAID volume, you can then mount the volume under a mount point and access the data on the filesystem.
mount /dev/md5 /mnt
- This mounts the software RAID volume under /mnt. Â You can then use a file browser to navigate through the volume. Â What I found is that all of my data was under the “shares” folder in numbered folders “1, 2, 3, 4”, which loosely lines up with the number of shares that were on the system when it was “working”.
- As I have large network-attached storage array not made by LaCie also on the network I was recovering from, I was able to simply mount an NFS share from the other NAS to another mount point and then use “rsync” to copy all the data (ignoring the permissions – something I will fix manually once the data is copied back to a replacement NAS).
As it stands at the time of writing, I have been able to recover all of the data from 3 shared drives on the old LaCie NAS with no issues.