Accessing my cloudbox-slow blinking blue light

[fvdw]

I did some reading. We had a similar problem before. There we were able to get the cloudbox up and running again.
Therefor before trying to mount partition 8 lets try if we can bring back you cloudbox to normal operation as well

To do this switch it off and leave it connected to your LAN.
Start de fvdw-sl console (fire wall disabled) but instead of action load and start standalone kernel choose as action "u-boot console". Follow the instruction to get the u-boot window and command prompt (marvell>> or somithing similar)

In the u-boot command window give these commands to reset the cloudbox lacie firmware and activate procedure to load kernel and firmware

Code: Select all

setenv root_part 5
ide reset
setenv image /boot/uImage
run nexus_load_image
run nexus_bootargs
bootm

And report what happens,
If it goes well you cloudbox should boot the lacie firmware, it can take a while before it is up and running so give it time. When the blue light is steady or blinks only for disk access then try to connect to it as you did in the past. If it works do not switch it off and backup your data first before we do any further action.

[deepeedoubleu]

thank you,

I have followed your steps and its states it is "Starting kernel...."

I see the fast blinking blue light is now back to the slow blinking blue light. I am going to step away and let the kernel start. I hope the blue light eventually becomes solid and the drive can be found on the network. Fingers crossed!

Do you know about how long I should allow for the kernel to start? Minutes? Hours?

Thank you again!

[fvdw]

starting the kernel takes less then a minute but after the kernel has started no output will be generated in the u-boot window anymore.
The slow blue blinking might indicate that the lacie firmware is repairing the file system, that may take quite some time.

If it still blinks after a day I think the boot has another problem.
In that case, so still not stable blue light after one day, we could try to use root system on partition 4 instead of 5 to see if that makes the system startup. To do that use these commands and see what happens (but wait first to see if the repair finish or not with using partition 5)

Code: Select all

setenv root_part 4
ide reset
setenv image /boot/uImage
run nexus_load_image
run nexus_bootargs
bootm

[deepeedoubleu]

On my way out this morning i realized i didnt plug in my laptop last nite and died (ugh im an idiot) Drive was still blinking slow this morning. I will have to try again and will get back to you in the next 1-2 days

Thank you

[fvdw]

The laptop my be switched off, only the cloudbox should remain on, if it is still is slowly flashing blue after a day I advise to try the boot from partition 4.

[deepeedoubleu]

Thanks,

The drive was powered through out the nite and i left it all of today. Unfortunately no luck. I have tried partition 4 and will let it sit tonite. Again, it went from fast blinking to slow blinking. I really hope this works. :please

[fvdw]

If it still doesn't work we need to see if we can get sda8 mounted to retrieve your data

Seems for the cloudbox we need a more sophisticated mount command and LVM tools to mount logical volumes
It will become a little complicated ;) below the instructions

Install the new mount command.
Download the attached file and put it in the tftp folder of the fvdw-sl console

mount.tar

Put attached tar archive in the tftp folder of the fvdw-sl console on your pc running the console
copy it to the cloudbox using telnet client and standalone kernel

Code: Select all

cd /
tftp -l mount.tar -r mount.tar -g ip-pc

(replace ip-pc by the actual ip address of the pc running the fvdw-sl console)
it should tell you if the file was uploaded
if upload was ok, unpack it

Code: Select all

tar -xvf mount.tar

---edit---
With the last version 6.0, no need to upload mount manually. Use a new option with fvdw-programs menu :
* run on the telnet window the command: fvdw-sl-programs
(then a menu will appear)
* select "Upload and extract glibc mini and tools"

Jocko

Now assemble the raid array

Code: Select all

mdadm --assemble /dev/md0 /dev/sda8

now try to mount using the new new mount command

Code: Select all

mkdir /md0
/usr/sbin/mount /dev/md0 /md0

(Important: you need to use the prefix /usr/sbin before the mount command)

post what happens

I expect you will get a message like this

mount: unknown filesystem type 'LVM2_member'

If that happens we need to install LVM tools to be able to find out which logical volume LVM volume must be mounted
To install LVM tools download this file
--edit 19 may 16 file replaced as previous one was missing some libs.

lvm-202_02_98-vs3-19mei16.tar

and put it in the tftp folder of the fvdw-sl console and upload it via telnet client

Code: Select all

cd /
tftp -l lvm-202_02_98-vs3-19mei16.tar -r lvm-202_02_98-vs3-19mei16.tar -g ip-pc

(replace ip-pc by the actual ip address of the pc running the fvdw-sl console)
it should tell you if the file was uploaded
if upload was ok, unpack it

Code: Select all

tar -xvf lvm-202_02_98-vs3-19mei16.tar

and scan the disk for LVM volumes

Code: Select all

/usr/sbin/vgscan

[deepeedoubleu]

Thank you,

I have let the drive sit all day and noluck with partition 4. I will try your instructions above when i get home tomorrow. I thank you for all your help and wealth of information. I will follow up

[deepeedoubleu]

Hello,

I have placed the mount.rar file into the tftp folder, but I am having no luck. Do you know what I could be doing wrong? Do I need to extract the mount.rar file?


fvdw-sta-kirkwood login: root
Password:
root@fvdw-sta-kirkwood:/ # cd /
root@fvdw-sta-kirkwood:/ # tftp -l mount.rar -r mount.rar -g 10.0.1.7
tftp: server error: (1) File not found
root@fvdw-sta-kirkwood:/ #

Thank you!

[fvdw]

Then you have put the mount.rar file in the wrong folder on your PC.
You must put it in the tftp sub folder of the fvdw-sl console, the same directory where the standalone kernel is present
So look in the folder were you have installed the console and look for tftp subfolder