Single disk LaCie Cloudbox

How does one recover it in cause of failure?

…I own a Lacie Cloudbox [which] just stopped working suddenly. Doesn’t seem to be a physical disc problem, more like file system … It uses RAID (single disc) … If there’s someone here that would be into walking me through the steps involved to mount this drive in Mac, Windows, or Linux, that would be amazing.

First thing is that single-disk unit, with no provision to install a second drive, does not need RAID. Despite that, most NAS vendors use the same firmware for the entire product lineup. This has a side effect of single-disk models being unnecessarily complex. There still will be multiple partitions, and instead of using a simple partition for data, an md-raid JBOD will be used.

Now, let’s move on to the actual problem at hand. If a disk fails in a single-disk unit, it is a job for a skilled technician, no way around it. If it is a filesystem issue, this is a job for recovery software (like our

Theoretically, one may want to try to access data with a Linux, but that’s not likely to have effect. The NAS uses Linux internally; if the Linux was able to read data, there will be no need for recovery. The recovery is required precisely because Linux can’t access the filesystem any longer. While with a failed RAID some clever jiggling with mdadm parameters can (and often does) solve the problem, in a filesystem there are much fewer parameters to fiddle with. A single-disk unit can’t have problem with its RAID because it has no RAID, so we’re going straight to the filesystem level.

RAID Reconstructor vs LaCie 5Big NAS

If you have a problem with deleted files on a LaCie NAS, you ask on the Tech Support Forum:

[someone] have got a Lacie 5big [and need to recover some data from it]… It is a 5 disk raid5 array. [so they put 4 disks into windows PC]…where I hoped to use raid reconstructor and captain nemo to get to the important files

My first problem was that win7 listed the disks in disk manager with each disk having 7 healthy partitions, but wouldn’t show them as active under my computer. Likewise, it would appear that Raid Reconstructor couldn’t see them as well.

I then moved on to r-studio, which could see them…but saying that there was no file hierarchy found…

If there’s a solution to getting the disks to appear to Raid Reconstructor… Otherwise, any other advice on the situation would be appreaciated…

Looks like a set of multiple issues,

  1. Only using 4 disks out of 5 is a nice trick indeed. As it is a RAID5, you only need 4 disks to make it readable.
  2. Captain Nemo is largely irrelevant in this specific case. WinHex may have been handy, but that’s a whole lot different ballgame.
  3. Disk Management cannot make Linux partitions active or mount them in any useful way, do not expect much from it.
  4. RAID Reconstructor only works with entire disks, not partitions. While we are at it, ReclaiMe RAID Recovery has the same limitation. Both of these are not really useful for NASes.
  5. R-Studio will work, but requires precise RAID parameters. Eventually, this comes as a solution after the original poster tries multiple combinations of RAID parameters, and the disk order. The disks in the array are not in the bay order:

    the numbered 1-5 bays on the Lacie 5big actually did not house the drives in their ‘correct’ order. The raid drive 1 was the Lacie drive 5 [and so on]

Well, could we have dealt with this? Home NAS Recovery handles partition tables properly, checked. It will figure RAID parameters, including disk order and whatnot, checked. XFS filesystem, checked. Looks like yes, Home NAS Recovery can do this job.

Recover data from LaCie 1TB NAS

Neil seems to have a problem with its 1TB LaCie NAS.

… Lacie NAS 1TB drive… I can’t even get a connection to it. I … put [the drive] into my computer using a free SATA port. … I can see the drive only in Disk Management…Windows tells me that there is 100% free space available…How can I possibly recover my data from this drive?

What Filesystem is Lacie using?

Last question first, LaCie uses EXT3 or XFS filesystem, depending on the exact model/firmware.

As far as recovery goes, we can do that, since this is a NAS version of the LaCie.  If it were a USB/Firewire/Thunderbolt version, we would have passed the opportunity. As it is, single drive NAS with EXT3 (or XFS) is pretty easy. The damage should be not that bad, because not being able to connect to the unit at all suggests some kind of instantaneous and total failure of either the unit itself or firmware in it. Such cases tend not to damage the filesystem, because there is no time to do the said damage.

As a side note, Disk Management does not show free space for EXT3, or any other Linux filesystem. It does not know how to read them, so it assumes all the space is free.