Data Recovery Help

Post Reply
Monding
Posts: 5
Joined: Mon Jan 19, 2015 9:23 pm

Data Recovery Help

Post by Monding » Mon Jan 19, 2015 9:37 pm

Can someone please explain like I'm a five year old on how to recover data off of my LACIE drive?

Recently I had a slow flashing blue light issue on my cloudbox. I followed all of the steps on resetting the drive, all to no avail. I contacted Lacie customer support, who were very helpful, but did not resolve my issue through email correspondance. They asked me to send the drive in for repair and then pay to restore any data. Upon researching data recovery, I came upon this here NAS website, but I am not familiar with just about anything you kind folks are talking about.

I removed the drive from the case and installed it in my windows machine. This was after I tried to connect it directly to my machine via ethernet cable. I booted Ubuntu from CD and did not see the drive on the network. This prompted me to remove the drive and install it directly. Now Ubuntu can see the drive partitions in Gparted. But that is all. I see the partitions but cannot access the data. 8 total partitions.

Please ELI5 on how to recover.

fvdw
Posts: 777
Joined: Wed Mar 18, 2009 11:13 pm

Re: Data Recovery Help

Post by fvdw » Tue Jan 20, 2015 7:54 pm

if you are in lInux you need to mount the partitions to get access, did you do that ?

Monding
Posts: 5
Joined: Mon Jan 19, 2015 9:23 pm

Re: Data Recovery Help

Post by Monding » Tue Jan 20, 2015 9:42 pm

Using Gparted I can see all of the partitions on the drive. I'm unable to mount them as the option is greyed out and will not allow me to mount.

fvdw
Posts: 777
Joined: Wed Mar 18, 2009 11:13 pm

Re: Data Recovery Help

Post by fvdw » Tue Jan 20, 2015 10:36 pm

you must not mount them in gparted but in linux, anyhow after looking to the partition table which is like this (I got it from another user sometime ago

Code: Select all

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048            4095   1024.0 KiB  EF02  grub_core      fvdw: ef02 is bios boot partition
   2            4096          397311   192.0 MiB   8300  boot_rescue    fvdw: 8300 linux file system
   3          397312          399359   1024.0 KiB  8300  nv_data	fvdw: 8300 linux file system
   4          399360         3545087   1.5 GiB     FD00  root_1		fvdw: fd00 Linux raid
   5         3545088         6690815   1.5 GiB     FD00  root_2
   6         6690816         8787967   1024.0 MiB  FD00  var
   7         8787968         9312255   256.0 MiB   FD00  swap
   8         9312256      3907029134   1.8 TiB     FD00  user_data
the issue the data partition is of type raid, that why it cannot mount it.
Maybe some experts here know how to access it, my knowledge of raid is practically zero

Monding
Posts: 5
Joined: Mon Jan 19, 2015 9:23 pm

Re: Data Recovery Help

Post by Monding » Tue Jan 20, 2015 10:48 pm

I see all 8 of these partitions. I think I need to find the raid data to join the partitions and then mount. I appreciate the help.

Jocko
Posts: 99
Joined: Thu Mar 08, 2012 7:47 pm
Contact:

Re: Data Recovery Help

Post by Jocko » Tue Jan 20, 2015 11:27 pm

Hi Monding, Here you can find information for the clodbox raid: http://lacie.nas-central.org/wiki/Category:CloudBox

So you have:

Code: Select all

md8 : active raid1 sda8[0]
      3902362300 blocks super 1.0 [1/1] [U]

md7 : active raid1 sda7[0]
      262132 blocks super 1.0 [1/1] [U]

md6 : active raid1 sda6[0]
      1048564 blocks super 1.0 [1/1] [U]

md5 : active raid1 sda5[0]
      1572852 blocks super 1.0 [1/1] [U]

md4 : active raid1 sda4[0]
      1572852 blocks super 1.0 [1/1] [U]
Note: I don't understand the sense to build raid1 with only one disk...
Basically, to get the mdx device do

Code: Select all

mdadm --assemble /dev/mdx /dev/sda8
and you will be able to mount mdx

Monding
Posts: 5
Joined: Mon Jan 19, 2015 9:23 pm

Re: Data Recovery Help

Post by Monding » Wed Jan 21, 2015 12:32 am

After assembling the sdb8 partition, I am still unable or unclear on how to mount the drive.

Code: Select all

root@ubuntu:~# mdadm --assemble /dev/mdx /dev/sdb8
mdadm: /dev/mdx is an invalid name for an md device.  Try /dev/md/mdx
root@ubuntu:~# mdadm --assemble /dev/md/mdx /dev/sdb8
mdadm: /dev/md/mdx has been started with 1 drive.
New drive listed as /dev/md8/
Gparted states the new device has an unallocated file system and gives no option to mount.

Jocko
Posts: 99
Joined: Thu Mar 08, 2012 7:47 pm
Contact:

Re: Data Recovery Help

Post by Jocko » Wed Jan 21, 2015 1:08 pm

Hi Monding,

I am sorry to cause confusion but when I wrote 'mdx' I meant that you must chose an unused md device (so need to replace x by 0,...9).

So if currently md0 is not used by your laptop, the command is

Code: Select all

mdadm --assemble /dev/md0 /dev/sdb8
Note: the current raid devices are listed in /proc/mdstat, so to find them, do

Code: Select all

cat /proc/mdstat

Monding
Posts: 5
Joined: Mon Jan 19, 2015 9:23 pm

Re: Data Recovery Help

Post by Monding » Wed Jan 21, 2015 11:34 pm

Thank you Jocko. As soon as I entered that command the drive popped up. All the data is there.

It was very easy with your help, but like you said, why RAID1 a single physical drive?

Thanks again!

Jocko
Posts: 99
Joined: Thu Mar 08, 2012 7:47 pm
Contact:

Re: Data Recovery Help

Post by Jocko » Thu Jan 22, 2015 8:37 am

Glad to heard that you found your data.

About a RAID1 with a single physical drive, maybe it is a trick: as the raid is already built, then it is easy to mirror the data in another drive by adding it in the existing raid (even if there is way to do it with a not raid partition).

anandg
Posts: 2
Joined: Wed Aug 19, 2015 5:31 am

Re: Data Recovery Help

Post by anandg » Wed Aug 19, 2015 5:37 am

Hi, I am facing a similar issue. When I connect my lacie drive to my ubuntu computer and run parted, i see the following:

Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 1049kB 538MB 537MB fat32 boot
2 538MB 249GB 248GB ext4
3 249GB 250GB 1558MB linux-swap(v1)


Error: Input/output error during read on /dev/sdb
Retry/Ignore/Cancel? i
Error: The backup GPT table is corrupt, but the primary appears OK, so that will
be used.
OK/Cancel? ok
Model: ATA ST3000DM001-1CH1 (scsi)
Disk /dev/sdb: 3001GB
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 nv_data
4 204MB 1815MB 1611MB root_1 raid
5 1815MB 3426MB 1611MB root_2 raid
6 3426MB 4499MB 1074MB var raid
7 4499MB 4768MB 268MB swap raid
8 4768MB 3001GB 2996GB user_data raid


Error: /dev/mapper/vg-lv: unrecognised disk label

Error: /dev/md4: unrecognised disk label

Error: /dev/md5: unrecognised disk label

Error: /dev/md6: unrecognised disk label

Error: /dev/md7: unrecognised disk label

Error: /dev/md127: unrecognised disk label

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

When I try to assemble /dev/sdb8 i get the following error

root@b:~# mdadm --assemble /dev/md0 /dev/sdb8
mdadm: no recogniseable superblock on /dev/sdb8
mdadm: /dev/sdb8 has no superblock - assembly aborted


Please help me recover my data.
Last edited by anandg on Wed Aug 19, 2015 5:40 am, edited 1 time in total.

anandg
Posts: 2
Joined: Wed Aug 19, 2015 5:31 am

Re: Data Recovery Help

Post by anandg » Wed Aug 19, 2015 5:38 am

When I run the /cat /proc/mdstat I get the following output

root@b:~# cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5] [raid4] [raid10]
md4 : active raid1 sdb4[0]
1572852 blocks super 1.0 [1/1]

md7 : active raid1 sdb7[0]
262132 blocks super 1.0 [1/1]

md127 : active raid1 sdb8[0]
2925610300 blocks super 1.0 [1/1]

md5 : active raid1 sdb5[0]
1572852 blocks super 1.0 [1/1]

md6 : active raid1 sdb6[0]
1048564 blocks super 1.0 [1/1]

unused devices: <none>

lyralemos
Posts: 1
Joined: Wed Sep 02, 2015 12:31 pm

Re: Data Recovery Help

Post by lyralemos » Wed Sep 02, 2015 12:34 pm

anandg wrote:Hi, I am facing a similar issue. When I connect my lacie drive to my ubuntu computer and run parted, i see the following:

Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number Start End Size File system Name Flags
1 1049kB 538MB 537MB fat32 boot
2 538MB 249GB 248GB ext4
3 249GB 250GB 1558MB linux-swap(v1)


Error: Input/output error during read on /dev/sdb
Retry/Ignore/Cancel? i
Error: The backup GPT table is corrupt, but the primary appears OK, so that will
be used.
OK/Cancel? ok
Model: ATA ST3000DM001-1CH1 (scsi)
Disk /dev/sdb: 3001GB
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 nv_data
4 204MB 1815MB 1611MB root_1 raid
5 1815MB 3426MB 1611MB root_2 raid
6 3426MB 4499MB 1074MB var raid
7 4499MB 4768MB 268MB swap raid
8 4768MB 3001GB 2996GB user_data raid


Error: /dev/mapper/vg-lv: unrecognised disk label

Error: /dev/md4: unrecognised disk label

Error: /dev/md5: unrecognised disk label

Error: /dev/md6: unrecognised disk label

Error: /dev/md7: unrecognised disk label

Error: /dev/md127: unrecognised disk label

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

When I try to assemble /dev/sdb8 i get the following error

root@b:~# mdadm --assemble /dev/md0 /dev/sdb8
mdadm: no recogniseable superblock on /dev/sdb8
mdadm: /dev/sdb8 has no superblock - assembly aborted


Please help me recover my data.
I have the same problem as you...
My cloudbox is returning the same error when I try to mount it

Code: Select all

mdadm: no recogniseable superblock on /dev/sdb8
mdadm: /dev/sdb8 has no superblock - assembly aborted
Have you managed to solve this?

spinflip
Posts: 6
Joined: Thu Apr 04, 2013 7:32 am

Re: Data Recovery Help

Post by spinflip » Fri Sep 25, 2015 6:38 am

Hello

I cannot connect to my 3TB Cloudbox anymore, and after some time the LED turns solid red. I did not succeed to mount the partition 8 containing my files and the partition data seems to be corrupted. For instance I get the message "Couldn't find valid filesystem superblock." or "Bad magic number in super-block while trying to oben /dev/sdb". Is it possible to somehow copy all the partition data from a working Cloudbox drive and replace the corrupted structure without data loss? Any other suggestions? Any help would be really appreciated.

Thanks in advance!

Post Reply