reinstall firmware on lacie cloudbox

[fvdw]

If you can access the disk and content when taken it out and connecting it to another computer then we might have a hardware failure in the lacie motherboard.
Did you try the fdisk command ?
If you have another hard disk that you know is ok and contains data you could insert that in the cloudbox and try to use the gdisk and fdisk commands. If that gives a positive result and it can read the partition table we know that the motherboard sata interface is ok.
You can also connect the original disk again to a pc running linux to see if you can read the partition table.

[pauldays]

root@fvdw-sta-kirkwood:/ # fdisk -l /dev/sda

Disk /dev/sda: 2000.3 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/sda doesn't contain a valid partition table
root@fvdw-sta-kirkwood:/ #

[fvdw]

This means you have empty disk, the partition table is removed. All data is lost on the disk.
If you want to restore lacie you need to get from someone partition images, we don't have them, and follow a comicate process to get it installed. Alternative install fvdw-sl firmware uding the auto installer of the tvdw-sl console that runs under windows.

Still I wonder how the partion table can be lost, a power failure can not cayse that

Ps If only the partition table was removed and no writing has been done to the disk you could try to generate the original partition table to gain access to the data that still might be present on the disk. A partition table only points the operation system were to find the data on the disk. If however writing has been done to this disk after removing the partition table then this no longer is option

[pauldays]

fvdw,

I can assure you, the drive has info and partitions. I re-connected the internal drive to my eSata dock, and inside there is i think some wierd RAID linux system and all data in on "1".

As I previously stated, I extracted the data last week. I just wanted to restore the original firmware. I installed yours on a NS2, but, it dissappears from the network from time to time, and I kind of wanted to keep this stock.

Suggestions?

[Jocko]

Hi,

That would mean you have a hardware issue with your cloudbox.

Did you make the test asked by fvdw with another disk on the cloudbox ? (to check if you see its partition table)

[pauldays]

Hi Jocko,

No i dont have any other space disk. I am thinking of writing now a mail to Lacie, though i know its a waste of time, to see if they have an image i could push or something. I did have the exact same issue with my NetworkSpace 2, and that I did load the custom firmware but its not stable, so I wanted to keep this stock.

Paul

[fvdw]

:scratch strange that you can see the partition table when you connect the disk to your esata dock and not when it is in the cloudbox. Its the reason why ir fails to boot. The bootloader cannot find the required partitions.

How do you read the partition table when connected to your esata dock? And how does it look like?

Ps you could put your ns2 disk in the cloudbox and see if the standalone kernel can read it. Even if it is a recent fvdw-sl version that is on that disk your cloudbox should be able to boot it. The kernel on fvdw-sl support multiple devices like ns2 and cloudbox. This way you could test if the cloudbox hardware is ok