*With firmware fvdw-sl-console-6-18-1-v2-29jul2019-32bits
Following trhead https://plugout.net/viewtopic.php?f=28&t=2499&start=20 now I have Ftp server up and running and copying data
Success :punk
Question, When backup finish, Can I use Firmware 18.1 directly to substitute the Lacie firmware or I need to install prior versions first?
UPDATE 1
Using gdisk -w to rebuild mbr was a success
HDD connected using eSata in Windows, disk online, and now I able to explore the partitions and backup important data.
When it finish, I will keep following this trhead https://plugout.net/viewtopic.php?f=28&t=2499&start=20 to try to mount the shared partition and ftp data
Question, i was using firmware ver16.1, can I use the ver18?
Original post
Hello
I have a problem with a Lacie CloudBox 3TB original firmware. I will try to be super concise, long story short.
The NAS was working fine for 7 or 8 years, no one issue, but two days ago was not possible to connect and when trying to connect, after a power off-on, a message saying "the device was power on... wait some minutes" appeared on the web interface.
At this point I decided to connect the HDD to an USB-eSATA and use Gparted, gparted showed all partitions... ok.
Using in Windows an app called "Explore2fs Virtual Volumes" yesterday was possible to see the partitions content, see that my shared data was apparently ok in the HDD and copied some files, but too slow, so I decided keep diggin in the net and found this wonderful site.
*Before starting with the console standalone firmware etc, i followed lacie reset procedure, press the reset button, red light blinking, etc... no results. but, the data still there and accesible using the tools I mention before.
using the search :) I found very a similar case, https://plugout.net/viewtopic.php?f=28&t=2499 and started follow from post1, and all was ok, but in some moment yesterday night (dont ask me why :hammerhead ) in the step where say SL-Console ... U-boot console, in the Marvell>> prompt using help saw the factory command, then used that. after this point this is what I have/see
*I dont want to forget to mention that after the factory command, booted using SL-Kirkwood and leave all night xfs_repair all night, today morning was still repairing and i stopped.
HDD connected to eSATA
gparted doesnt show partitions
Explore2fs doesnt show nothing
Windows show the disk as offline
Back to start of the steps and use again SL-Console
Booting using the stanalone kirkwood and telnet, here the results of gdisk and fdisk
- Code: Select all
root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5
Partition table scan:
MBR: not present
BSD: not present
APM: not present
GPT: present
Found valid GPT with corrupt MBR; using GPT and will write new
protective MBR on save.
Disk /dev/sda: 5860533168 sectors, 2.7 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 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:/ # fdisk -l /dev/sda
fdisk: device has more than 2^32 sectors, can't use all of them
Disk /dev/sda: 2199.0 GB, 2199023255040 bytes
255 heads, 63 sectors/track, 267349 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk /dev/sda doesn't contain a valid partition table
root@fvdw-sta-kirkwood:/ #
Well, as you can see, gdisk show partitions, even the user_data is linux-raid type, but fdisk doesnt show nothing, and gdisk says MBR is corrupt (yesterday night MBR was ok)
Questions if any could help me
Is there any remote possibility to reconstruct rebuild recover the MBR?
Any software to extract raw data, I know this is the last optión...
Really are there the partitions or all is lost and next step will be install this custom firmware and cry alone in the dark?
I think that something is there, cause Gdisk is showing partionts and with the correct type, but cause the MBR is corrupt fdisk doesnt show nothing.
I will keep searching in the forum to see if there any solution or whatever.. :thinking
thanks in advance to all here.
