Accessing my cloudbox-slow blinking blue light

[deepeedoubleu]

Trying to access/recover my lacie cloudbox. all of a sudden my cloudbox can no longer be accessed. I am getting a slow flashing blue light. I have tried recovery using the network assistant and just go back to the slow blinking light. I have attempted two resets and all go back to the slow blinking blue light. Also i have attempted to connect using an ethernet cable using lacies ip configurator and it says it found the drive, but no drive actually appears to connect. I cant access the drive on the network, ethernet, or through the network assistant. I am at a loss and really concerned if these files might be gone. I have begun working with lacie, but their suggestions have not worked as of yet. Can anyone help me?

Should i consider removing the drive from the casing and buying a network enclosure to access the files again? Would this even work?

Thanks!

[fvdw]

I assume you are using the lacie firmware?
If correct then blue flashing means that the drive didn't complete boot. Buying a new enclosure will not help as the lacie firmware is loaded from disk. So putting this disk in a new enclosre will give same problem. Unfortunate lacie uses a complicated setup on the cloudbox including a raid array for data storage.
You can use our fvdw-sl console to access your device and try to repair it using the standalone kernel that comes with the fvdw-sl console. Do some reading in the topics you can find in this clodbox sub forum to find out how to use the console and standalone kernel and give it a try. Of course we will try to help you but please try first by yourself.
Ps your data will be most probably still ok

[deepeedoubleu]

Thank you,

Yes, I am currently using the lacie firmware. I have loaded the connsole and tried the Standalone kernel, load and start. Telnet comes up, but connection times out and I am not asked for a login. I tried using the Connect option in Telnet, but I don't see where I can enter a login. I am not an expert at this by any means. Any help you can provide would be appreciated. I really hope I do not lose these files. I am ready to go by a new drive as soon I know I can access/copy these files.

Thank you

[deepeedoubleu]

Oh and also, since trying this the blue light has started flashing faster than before (not sure if this is good or bad).

Thanks!

[fvdw]

Please describe how your LAN is setup, and describe exactly what you see in the fvdw-sl (u-boot) command window when the standalone kernel is uploaded and started. This might help us to indetify why the kernel is not loaded

If you get this problem something is not right in your network setup, some common problems

- Using a wireless connection
Do not use a wireless connection for you computer to the lan, use a wired connection.
Because of interference on wireless connections the uploading of the standalone kernel may fail.

-Firewall of your PC blocking programs used by the console to access the LAN
Also you need to allow the console and the telnet client to pass your firewall, if you don't know how to to do that disable your firewall temporarily.
(normally your pc will ask you to grant access when using the console)

[deepeedoubleu]

Thank you,

I have confirmed I attempted using the console with a wired connection to my router. I turned off my firewall and now telnet connects. I tried using the login provided in the directions, but I dont know what to do next. This is what I see in telnet:

fvdw-sta-kirkwood login: root
Password: (I entered giveit2me, but it doesnt show on the screen)
root@fvdw-sta-kirkwood:/ #

I don't know where to go from here. What number should I enter Would you be able to direct me? I appreciate your help. Sorry if Im expected to know where to go from this point.

Thank you again

[fvdw]

Did you read other pists in the cloudbox sub forum? There you can find posts of others with similar problem. ;)

Anyhow give the following command to see if the hard disk is accesible.

Code: Select all

gdisk -l /dev/sda

You should get as output the partition table of the disk. Post the outpur here. So we can judge if it is a correct table

[deepeedoubleu]

Thank you,

I have searched other posts and have copied the info below. Unfortunately, it seems that nothing is coming up when entering gdisk -1 /dev/sda. Is there anything I can do?


fvdw-sta-kirkwood login: root
Password:
root@fvdw-sta-kirkwood:/ # gdisk -1 /dev/sda
GPT fdisk (gdisk) version 0.8.5

Usage: gdisk [-l] device_file
root@fvdw-sta-kirkwood:/ # mkdir /sda7
root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
mount: mounting /dev/sda7 on /sda7 failed: Function not implemented
root@fvdw-sta-kirkwood:/ # ls /sda7/boot.log
ls: /sda7/boot.log: No such file or directory
root@fvdw-sta-kirkwood:/ # gdisk -1 /dev/sda
GPT fdisk (gdisk) version 0.8.5

Usage: gdisk [-l] device_file
root@fvdw-sta-kirkwood:/ #



Thank you

[fvdw]

You use as option -1 (the number 1) you should use the letter l from leonard (do not use capital L but non capital l)

And you cannotmount the partitions yet as you need to assemble the raid array first

[deepeedoubleu]

oh im an idiot haha. here is the output:

fvdw-sta-kirkwood login: root
Password:
root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sda

Code: Select all

GPT fdisk (gdisk) version 0.8.5

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 5860533168 sectors, 2.7 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 48EB39C7-FA39-4315-9B4C-B7E4FE438E83
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5860533134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048            4095   1024.0 KiB  EF02  grub_core
   2            4096          397311   192.0 MiB   8300  boot_rescue
   3          397312          399359   1024.0 KiB  8300  nv_data
   4          399360         3545087   1.5 GiB     FD00  root_1
   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      5860533134   2.7 TiB     FD00  user_data
root@fvdw-sta-kirkwood:/ #

I thank you for your help. Please advise what I should do next.

Lacie has told me the drive has went faulty, but they have not suggested any testing and have been quick to sell me services to recover the drive. I am hoping I do not have to rely on them. At least so I can get the files off the drive onto a new drive.