Recover the data storaged in a Lacie CloudBox with an Ubuntu Linux

1. LACIE CLOUDBOX DATA
RECOVERY
Document created by Jordi Clopés Esteban
Protected by Creative Commons by-sa 3.0
Twitter @jordiclopes
jordiclopes@gmail.com

2. WHAT WE ARE TALKING ABOUT
Lacie CloudBox is a NAS server for home or small office.
More information: http://www.lacie.com/uk/products/product.htm?id=10597

3. GOAL
Problem:
If the ethernet port becomes unavailable we get a big problem.
Goal:
Recover the data storaged in the hard disk.
I’m using an Ubuntu Linux 12.10 Desktop for that pourpose.

4. PLUG HARD DRIVE
We have to extract the hard disk from the box and plug
it into our PC. Piece of cake!

5. MAIN ISSUE
We can’t mount the data partition because of the file system.
With parted or Gparted frontend we can see our data in
partiton number 8

6. USING PARTED
#apt-get install parted
#parted -l
Model: ATA ST1000DM003-1CH1 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Number Start End Size File system
Name
Flags
1
1049kB 2097kB 1049kB
grub_core bios_grub
2
2097kB 203MB 201MB ext2
boot_rescue
3
203MB 204MB 1049kB ext2
nv_data
4
204MB 1815MB 1611MB ext2
root_1
raid
5
1815MB 3426MB 1611MB ext2
root_2
raid
6
3426MB 4499MB 1074MB ext3
var
raid
7
4499MB 4768MB 268MB linux-swap(v1) swap
raid
8
4768MB 1000GB 995GB
user_dataraid

7. USING GPARTED

8. SO LET’S MOUNT!
If we try to mount that partition as usual we get this:
#mount /dev/sda8 /mnt/disk/
mount: unknown filesystem type 'linux_raid_member'
More information about RAID & LVM2:
http://en.wikipedia.org/wiki/Logical_Volume_Manager_%28Linux%29

9. THE SOLUTION - 1 STEP
Install this packages:
For create & manage raid
#apt-get install mdadm
For manage LVM2
#apt-get install lvm2

10. THE SOLUTION - 2 STEP
Mount /dev/sda8 in /dev/md0
#mdadm --assemble --run /dev/md0 /dev/sda8
If md0 is being used choose another one

11. LVMDISKCAN SHOWS /DEV/MD0
#lvmdiskscan
/dev/ram0 [ 64,00 MiB]
/dev/md0 [ 927,07 GiB] LVM physical volume
/dev/dm-0 [ 927,07 GiB]
/dev/ram1 [ 64,00 MiB]
/dev/sda1 [
1,00 MiB]
/dev/ram2 [ 64,00 MiB]
/dev/sda2 [ 192,00 MiB]
/dev/ram3 [ 64,00 MiB]
/dev/sda3 [
1,00 MiB]
/dev/ram4 [ 64,00 MiB]
/dev/ram5 [ 64,00 MiB]
/dev/ram6 [ 64,00 MiB]
/dev/ram7 [ 64,00 MiB]
/dev/ram8 [ 64,00 MiB]
/dev/ram9 [ 64,00 MiB]
/dev/ram10 [
64,00 MiB]
/dev/ram11 [
64,00 MiB]
/dev/ram12 [
64,00 MiB]
/dev/ram13 [
64,00 MiB]
/dev/ram14 [
64,00 MiB]
/dev/ram15 [
64,00 MiB]
/dev/sdb2 [ 473,21 GiB]
/dev/sdb5 [ 457,37 GiB]
/dev/sdb6 [ 953,00 MiB]
/dev/sdc1 [ 931,51 GiB]
0 disks
24 partitions
0 LVM physical volume whole disks
1 LVM physical volume

12. LVDISPLAY SHOWS LV NAME
#lvdisplay
--- Logical volume --LV Name
/dev/vg/lv
VG Name
vg
LV UUID
ngjboT-YynB-sUwD-KONB-0MFJ-I0gp-LDdR70
LV Write Access
read/write
LV Status
available
# open
0
LV Size
927,07 GiB
Current LE
237330
Segments
1
Allocation
inherit
Read ahead sectors auto
- currently set to
256
Block device
252:0

13. THE SOLUTION - FINAL STEP
Create a folder for mounting the partition with our files
#mkdir /mnt/disk
Mounting /dev/vg/lv
#mount /dev/vg/lv /mnt/disk/

14. HERE WE HAVE OUR DATA
Data is in “shares” folder
#ls -l /mnt/disk/
total 44
drwxr-xr-x 2 root root 4096 gen 30 2013 afp_db
drwxr-xr-x 3 root root 4096 gen 30 2013 autoupdate
drwx------ 2 root root 16384 gen 30 2013 lost+found
drwxr-xr-x 2 root root 4096 gen 30 2013 reserved
drwxr-xr-x 4 root root 4096 gen 30 2013 shares
drwxr-xr-x 2 root root 4096 gen 30 2013 tmp
drwxr-xr-x 3 root root 4096 gen 30 2013 torrent_dir
drwxr-xr-x 5 root root 4096 gen 30 2013 var

15. Hope it could help!
Cheers!
Document created by Jordi Clopés Esteban
Protected by Creative Commons by-sa 3.0
Twitter @jordiclopes
jordiclopes@gmail.com