Recently I tried to reserve some space for iSCSI. After setting it in the dashboard I received a generic error I cannot remember. So I restarted the device. It started but now I cannot access any files on it, cannot access the dashboard (getting this message: Your device may be powering on. Please try again in a few minutes.) and the front led keeps blinking blue every 0,5 seconds.

I can ping the device on its IP address but that is about it. No access at all. When I swap the disks to another identical Lacie it acts the same so no hardware error I guess.

Tried to reset the device to factory default but when it starts it should blink red/blue and front led stays on blue for about a minute and then it starts to blink blue again. Left the device for almost a week now like this but still no change.

I have critical data on this device. Can somebody please help me out here?

How are your command line skills? Fvdw has some interesting tool called 'stand alone kernel', which you can use to boot an altenative kernel, which gives you shell access, without touching the disk. This tool can be used to investigate what is going wrong, or manually perform a factory reset, or copy your data.

Sure. First part is get the stand alone kernel running. For that part you can find instructions on plugout.net.

When you have shell access execute

Code:

cat /proc/partitionscat /proc/mountscat /proc/mdstat

to find out the partitions, the mounts, and the state of the raid arrays. Actually I don't think the latter 2 will tell anything, as the stand alone kernel won't try to assemble the Lacie file systems.

This evening I will release an updated version of the fvdw-sl-console an new standalone kernels. This new setup will set the ip address of the nas automatic tovthe value that is set for the nas in the console and should solve telnet connection issues on LAN not using ip starting with 192.168.0 or 192.168.1

If you cannot wait you can do following. In your case you use an ip pool starting with 192.168.10 , the old console in principle is designed to work with ip starting with 192.168.0 and 192.168.1. And assignbitself the static addresses 192.168.0.252 and 192.168.1.252. These wont be accesible in your lan set up. However the standalone kernel will also ask a dynamic ip from the dhcp server in your lan. So look in the client list of dhcp server to find it. It is not nessary the same as used by uboot to upload the kernel. If that doesn't work change your network ip pool so you can use the static addresses as described. Last option wait for the new release.

It's OK. That are flash partitions, not disks. They are not assumed to have a partition table.

I see one weird thing. In /proc/partitions 5 disks are recognized (sda,sdb,sdc,sdd,sde), but in your fdisk -l listing /dev/sdd is lacking. Did you do a bad copy&paste job, or did the disk indeed disappear between the 2 commands?

Anyhow, you seem to have at least 4 disks with a readable partition table. Let's have a look at the raid metadata. Can you post the output of

Who is online

Users browsing this forum: No registered users and 9 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum