General NAS-Central Forums

Welcome to the NAS community
It is currently Wed Dec 13, 2017 3:28 am

All times are UTC




Post new topic Reply to topic  [ 129 posts ]  Go to page 1, 2, 3, 4, 5 ... 9  Next
Author Message
PostPosted: Thu Jul 09, 2015 10:39 pm 
Offline

Joined: Thu Jul 09, 2015 9:33 pm
Posts: 61
Hi,

I would like to know how to repair my Lacie Cloudbox, after it attempted to install the latest firmware but with no success, because it made my NAS stop working, just a blue led light blinking every 2 seconds.

I have tried to use the method from Lacie using the LNA in Recovery Mode with the latest firmware and the oldests firmwares (filename.capsule). But the LNA find the NAS but after a few minutes it doesn't find it anymore. And nothing happens unless the blue light blinking every 2 seconds.

I could try to use fvdw-sl console, but I can't delete the data inside the hard drive, just repair the boot, which I believe that is not working.

My network is 192.168.2.0 and subnet mask is 255.255.255.0.

What should I do the recover both, the Lacie OS and the data inside the HDD?


Top
 Profile  
 
PostPosted: Sat Jul 11, 2015 9:46 pm 
Offline

Joined: Thu Jul 09, 2015 9:33 pm
Posts: 61
Hi,

I've been trying a lot of solutions that I found in other forums and websites, but none of then had worked in my case. I found this link http://pt.slideshare.net/JordiClopsEste ... a-recovery and when I use Gparted it lists my Lacie Cloudbox as an unnallocated. What should I do to recover the partitions on my Lacie Cloudbox?

My final goal at the moment is to recover the data from the Lacie Cloudbox (I've plugged the 2TB Lacie <Seagate Barracuda 2000GB> HDD into an external usb 3.0 HDD case) and I'm using Ubuntu 15.04 (booted from a pen drive) to try to recover the files.

Tell me what commands should I write to show what is happening in my case (It was a long time that I've used Linux).


Top
 Profile  
 
PostPosted: Sun Jul 12, 2015 12:31 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6087
If gparted shows the disk as unallocated, the partition table is damaged. Are you sure you are looking at the right disk? Size fits? You can use the tool TestDisk to try to recover the partition table. If it succeeds, odds are your box will boot normally.


Top
 Profile  
 
PostPosted: Sun Jul 12, 2015 9:05 pm 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 775
for info this is how the original partition table should look like (note that it is a GPT partition table and a 2TB disk

Code:
cloudbox original partiton table

root@(none):/ # gdisk -l /dev/sda
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: 3907029168 sectors, 1.8 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 3907029134
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      3907029134   1.8 TiB     FD00  user_data


I never tried it myself to write a partition table to a disk with a corrupted partition table. But basically a partition table only is a listing used to determine where each partition starts and ends (sector). If you did not wite to the disk then restoring the original partition table might make your data on the disk accessible again.

However if I were you I would try the fvdw-sl console and the command gdisk to have another look if the table is really gone


Top
 Profile  
 
PostPosted: Mon Jul 13, 2015 12:26 am 
Offline

Joined: Thu Jul 09, 2015 9:33 pm
Posts: 61
Hi, I've tried the command with gdisk and below I post the info:

Code:
GPT fdisk (gdisk) version 0.8.10

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

Creating new GPT entries.
Disk /dev/sda: 488378645 sectors, 1.8 TiB
Logical sector size: 4096 bytes
Disk identifier (GUID): F2408811-B7C6-4CD0-99F9-57CB27A4ABDC
Partition table holds up to 128 entries
First usable sector is 6, last usable sector is 488378639
Partitions will be aligned on 256-sector boundaries
Total free space is 488378634 sectors (1.8 TiB)

Number  Start (sector)    End (sector)  Size       Code  Name


After that, no information was not found.


Last edited by dmiyabara on Mon Jul 20, 2015 9:39 pm, edited 1 time in total.

Top
 Profile  
 
PostPosted: Mon Jul 13, 2015 12:36 am 
Offline

Joined: Thu Jul 09, 2015 9:33 pm
Posts: 61
I've found some differences:

Quote:
Yours: Logical sector size: 512 bytes
Mine: Logical sector size: 4096 bytes


Quote:
Yours: Partitions will be aligned on 2048-sector boundaries
Total free space is 2014 sectors (1007.0 KiB)

Mine: Partitions will be aligned on 256-sector boundaries
Total free space is 488378634 sectors (1.8 TiB)


I have tried to use other softwares in Windows to recover some data, but the data it managed to recover came with the names of changed files, ans it's virtually impossible to find out which files it could recover. So the software could read the information contained on the HDD, and all the files still there.

(sorry for my poor english and because I'm writing in Ubuntu, my screen is flickering (Ubuntu with Nvidia issues) so fast every time that I enter a letter in the keyboard, that I feel dizzy when I look to the monitor.)


Last edited by dmiyabara on Mon Jul 20, 2015 9:41 pm, edited 1 time in total.

Top
 Profile  
 
PostPosted: Mon Jul 13, 2015 7:37 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6087
Quote:
Yours: Logical sector size: 512 bytes
Mine: Logical sector size: 4096 bytes
If you have connected your disk using an usb to sata converter, this is likely the problem. Many converters expose a 4k logical sector size, while the disk over it's sata port exposes a 512B sector size.
For this reason a partition table created over sata is not compatible when connected over usb. Remedy: Another usb converter (As far as I remember you are the first one reporting this issue with an usb3 converter), or connect the disk to (e-)sata.


Top
 Profile  
 
PostPosted: Mon Jul 13, 2015 1:24 pm 
Offline

Joined: Thu Jul 09, 2015 9:33 pm
Posts: 61
Ok, I think I will try to connect using another usb to sata. But if I can't use it (the usb adapter), is there other way to reach my HDD using the Cloudbox case and connect to it using the network?

I'm direct connected to the router using an ethernet cable and the Cloudbox too.


Top
 Profile  
 
PostPosted: Mon Jul 13, 2015 2:11 pm 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 775
You can leavevyour hdd inside the cloudbox connected to the sata port when using the fvdw-sl console standalone kernel. It has GPT support


Top
 Profile  
 
PostPosted: Mon Jul 13, 2015 3:13 pm 
Offline

Joined: Thu Jul 09, 2015 9:33 pm
Posts: 61
Can I request you something? How do I connect to my Cloudbox using the fvdw-sl console and the link to download the right standalone kernel for my Cloudbox?


Top
 Profile  
 
PostPosted: Mon Jul 13, 2015 3:20 pm 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 775
both your PC running the fvdw-sl console (under windows) and the cloudbox must be connected to the LAN using a router.
There is a help file how to use the standalone kernel. Baiscally it comes to this, you leave the cloudbox switched off and start the fvdw-sl console, you choose as action load standalone kernel (chosse kirkwood kernel) and wait until it mentions in a command window that pops up, " waiting for u-boot". Then start your cloudbox. if everything goes well the console will detect the cloudbox and interrupt boot and will automatically upload the standalone kernel and start it. Then a telnet client window will pop up and you can talk to your cloudbox...


Top
 Profile  
 
PostPosted: Tue Jul 14, 2015 12:49 am 
Offline

Joined: Thu Jul 09, 2015 9:33 pm
Posts: 61
fvdw,

I could connect to it, but which commands should I use to search inside the Cloudbox, and what kind of system files should I try to recover?
Is there a way to send the original firmware (I mean the latest) that it couldn't uploaded it correctly when it auto installed and if it corrects the bugs?

I don't know if I'm talking nonsense things, but it's what I imagine that I could do, at least in theory.


Top
 Profile  
 
PostPosted: Tue Jul 14, 2015 9:44 pm 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 775
The blue led flashing could be an indication that the bootloader cannot read the partiton table. This can be because of a faulty disk or corrupt partition table

So first thing you could do after connecting with telnet client is is give the command
Code:
gdisk -l /dev/sda

It should list the partition table, if that is ok then you know the disk works well and has a valid partition table andcan investigate further or write lacie firmware to the partitions. However as it seems the cloudbox uses a raid setup it is not straight forward to look inside the partitions.


Top
 Profile  
 
PostPosted: Wed Jul 15, 2015 1:16 am 
Offline

Joined: Thu Jul 09, 2015 9:33 pm
Posts: 61
Well I tried the telnet client, but it tries to connect and nothing appears. No place to input the username or password. Just say 'Connection to 192.168.2.252/telnet timed out.'
I used the file UIMAGE-3142-NWSP2CL-2, located in the folder kirkwood to load in fvdw-sl console

And tried to ping the address 192.168.2.252 and the four Request timed out. My network is 192.168.2.0.

What should I do next?


Please forget what I had written previously. But if someone makes the same mistake as me, it will be easy to find if you loaded the wrong file. The right one is 'UIMAGE-3142-NWSP2CL-KIRKWOOD-24-standalone' and you find it inside the folder 'tftp'.

Below I post what it showed to me:

Code:
root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sda
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: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 2AF8D378-680C-490D-AAC1-8AA7C45A0B51
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
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      3907029134   1.8 TiB     FD00  user_data
root@fvdw-sta-kirkwood:/ #


I think the partitions are okay now. The USB to SATA should be the problem when I tried to access it before and could not find any partitions, but only messy partitions.

now I'm stuck (but happy), because I do not know what commands to use again... which command should I use to mount or to access the user_data?

And about the original firmware, Mijzelf do you know how to upload using the fvdw-sl console or telnet?


Top
 Profile  
 
PostPosted: Wed Jul 15, 2015 7:35 pm 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 775
as the partition are set up as raind device (not make alot of sense to me on a single drive system) you need to assembele the arry before you can access it.
For example if you want to investigate the root_1 partition you give the command
Code:
mdadm --assemble /dev/md0 /dev/sda4

then mount it
Code:
mkdir sda4
mount /dev/md0 sda4

To view content
Code:
cd /sda4
ls -al


You could do same with root_2 (sda5) and the data partition (sda8)
Use for these respectively md1 and md2 as md0 is now in use for sda4 raid array
Before looking to another partition don't forget to return to system root after you have looked in mountpoint
Code:
cd /


Unfortunate I don't have the original partitions of the cloudbox, we need another member to supply these in case you need them. Uploading can be done with the telnet client by using tftp command.
However I would first check if you can assemble the array's on partition 4, 5 and 8. As when that fails I guess the cloudbox will fail to boot the lacie firmware as well as it also needs to assemble the arrays first


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 129 posts ]  Go to page 1, 2, 3, 4, 5 ... 9  Next

All times are UTC


Who is online

Users browsing this forum: No registered users and 6 guests


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

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group