Page 1 of 4
Cant Access NAS - Need to recovery my files
Posted:
Wed Apr 21, 2021 6:55 pmby Goapix
Hi,
After trying to upgrade to the last firmware i lost connection to my NAS, Cant detect it on network.
First i want to try to recovery my files. Its a 3TB HDD and its full of photos, My life...
Then il try to put the firmware again on another disk or in this one. But first i need to recovery my files.
Put the hdd on a usb Enclusure and connected it to PC, used Minitool Recovery software it detects the files but in RAW Format. is there a software that i can use to show me the original "tree" of the files?
Thank you.
Re: Cant Access NAS - Need to recovery my files
Posted:
Wed Apr 21, 2021 9:40 pmby Jocko
Hi
Your data are still here. (it is only an issue on the fw partition)
First you have to use fvdw-sl console to get an access via a standalone kernel from a windows laptop. Did you use it before ?
Re: Cant Access NAS - Need to recovery my files
Posted:
Thu Apr 22, 2021 10:07 amby Goapix
No, didnt used it before.
Re: Cant Access NAS - Need to recovery my files
Posted:
Thu Apr 22, 2021 10:09 amby Jocko
Do you have a windows laptop ? and how do you install the firmware ?
Re: Cant Access NAS - Need to recovery my files
Posted:
Thu Apr 22, 2021 10:15 amby Goapix
i Installed it long time ago. I have here a laptop, i downloaded the RAR part1,2,3,4,5 Unrar it. Is there any tuturial?
Re: Cant Access NAS - Need to recovery my files
Posted:
Thu Apr 22, 2021 10:46 amby Jocko
No there is no howto
Basically, you have to install these rar archives in a folder on your laptop and change nothing here.
Read this topic
https://plugout.net/viewtopic.php?f=7&t=2645Indeed is to get a telnet access on the nas by loading a standalone kernel. So start fvdw-sl console and select action "load standalone kernel and start". There is here a small howto and you have to follow all the steps (for example your nas must be off at the beginning).
When you have to select a kernel image, it is a kirkwood standalone version you must use with a cloudbox.
So first step is to succeed to get a telnet access
Re: Cant Access NAS - Need to recovery my files
Posted:
Thu Apr 22, 2021 10:50 amby Goapix
ok, i am at telnet now. inside the NAS, what command do i need to use to fix the partition?
Re: Cant Access NAS - Need to recovery my files
Posted:
Thu Apr 22, 2021 11:01 amby Jocko
:thumbup
So need to see what is wrong on boot sequence
- Code: Select all
mkdir /sda7 /sda1 /sda2
mount /dev/sda7 /sda7
mount /dev/sda1 /sda1
mount /dev/sda2 /sda2
cat /sda7/boot.log
cat /sda1/boot.log
cat /sda2/boot.log
ls /sda7/lacie-boot
Please to post here all the outputs
Re: Cant Access NAS - Need to recovery my files
Posted:
Thu Apr 22, 2021 11:15 amby Goapix
- Code: Select all
root@fvdw-sta-kirkwood:/ # mkdir /sda7 /sda1 /sda2
root@fvdw-sta-kirkwood:/ # mout /dev/sda7 /sda7
-sh: mout: not found
root@fvdw-sta-kirkwood:/ # mount /dev/sda7 /sda7
root@fvdw-sta-kirkwood:/ # mount /dev/sda1 /sda1
root@fvdw-sta-kirkwood:/ # mount /dev/sda2 /sda2
root@fvdw-sta-kirkwood:/ # cat /sda7/boot.log
start boot log
detect and set platform
cloudbox
kirkwood
UIMAGE-466-KIRKWOOD-7
Current kernel: 4.6.6 #7 PREEMPT Sun May 7 11:50:52 CEST 2017
cloudbox
mount dev/pts
update dev nodes
booting using root file system...
make dev node for buttons...
make dev node for tun device...
enable IP forwarding...
start buttons control daemon
device = cloudbox
source = buttons-cloudbox
buttons-nwsp2 daemon started
Tue Jan 1 16:42:36 UTC 2013
create temporary passwd file
run udevstart to update dev nodes when necessary
depmod: can't create 'modules.dep.bb': No space left on device
inserting kernel modules:
depmod: can't create 'modules.dep.bb': No space left on device
modprobe: module 'iscsi_trgt' not found
create temporary group file
configure loopback network interface
setting reboot and standby
cloudbox
rebootd-cloudbox
cloudbox
standbyd-cloudbox
starting php based setup routines step 1
* Initialize the volatile db file...
Warning: copy(): The first argument to copy() function cannot be a directory in /etc/finc/sysfunc_load_vltl_db.finc on line 36
[ FAIL ]
* Starting udevd... [ OK ]
* Finishing restore RAID devices... [ OK ]
file /etc/system NOT FOUND
* Found database configuration file... [FAIL]
database corrupt !
Loading the bak copy of the database !
Warning: in_array() expects parameter 2 to be array, null given in /etc/finc/internal_dump_xml_config_sub.finc on line 30
* Updating Disks database... * Starting mount of volumes...
* Finishing mount of volumes... [ OK ]
Warning: Invalid argument supplied for foreach() in /etc/finc/exthddfunc_wait_allmountExtHdd.finc on line 59
* Generating Hosts File... [ OK ]
* Configuring System Hostname... [ OK ]
* Configuring LAN interface...
Warning: in_array() expects parameter 2 to be array, null given in /etc/finc/internal_dump_xml_config_sub.finc on line 30
Warning: in_array() expects parameter 2 to be array, null given in /etc/finc/internal_dump_xml_config_sub.finc on line 30
cannot start udhcpc process.
* Initializing Timezone... [ OK ]
* Starting web server...
Warning: Invalid argument supplied for foreach() in /etc/finc/sysfunc_password_configure.finc on line 24
Warning: chdir(): No such file or directory (errno 2) in /etc/finc/daemonfunc_webgui_start.finc on line 207
[ Fail ]
* Starting mount of internal USB ...
* Finishing mount internal USB ... [ OK ]
* Configuring Disks... [ Fail ]
* Configuring Samba... [ OK ]
* Configuring System Users...
Root password: use default password
Set users, linux and samba accounts [ OK ]
* Starting Fvdw-sl Discovery Daemon... [ OK ]
start rpcbind service
starting php based setup routines step 2
starting php based setup routines step 3
* Starting daemon update Hosts File... [ OK ]
* Starting mount of remote shares...
* Finishing mount shares... [ OK ]
* Starting NTP client... [ FAIL ]
Warning: in_array() expects parameter 2 to be array, null given in /etc/finc/internal_dump_xml_config_sub.finc on line 30
Warning: in_array() expects parameter 2 to be array, null given in /etc/finc/internal_dump_xml_config_sub.finc on line 30
Warning: in_array() expects parameter 2 to be array, null given in /etc/finc/internal_dump_xml_config_sub.finc on line 30
Warning: Invalid argument supplied for foreach() in /etc/finc/dm_get_volume_addons.finc on line 54
Warning: Invalid argument supplied for foreach() in /etc/finc/dm_get_volume_addons.finc on line 54
Warning: Invalid argument supplied for foreach() in /etc/finc/dm_get_volume_addons.finc on line 54
Warning: Invalid argument supplied for foreach() in /etc/finc/dm_get_volume_addons.finc on line 54
Warning: Invalid argument supplied for foreach() in /etc/finc/dm_get_volume_addons.finc on line 54
Warning: Invalid argument supplied for foreach() in /etc/finc/dm_get_volume_addons.finc on line 79
Warning: Invalid argument supplied for foreach() in /etc/finc/dm_get_volume_addons.finc on line 79
Warning: Invalid argument supplied for foreach() in /etc/finc/dm_get_volume_addons.finc on line 79
- Code: Select all
Warning: Invalid arroot@fvdw-sta-kirkwood:/ # cat /sda1/boot.log
cat: can't open '/sda1/boot.log': No such file or directory
- Code: Select all
root@fvdw-sta-kirkwood:/ # cat /sda2/boot.log
cat: can't open '/sda2/boot.log': No such file or directory
- Code: Select all
root@fvdw-sta-kirkwood:/ # cat /sda2/boot.log
cat: can't open '/sda2/boot.log': No such file or directory
- Code: Select all
root@fvdw-sta-kirkwood:/ # ls /sda7/lacie-boot
root@fvdw-sta-kirkwood:/ #
Re: Cant Access NAS - Need to recovery my files
Posted:
Thu Apr 22, 2021 11:30 amby Jocko
So it seems you never upgraded the firmware and the firmware is corrupted on the root partition :dry with no more free space!
so post
- Code: Select all
gdisk -l /dev/sda
df -h /dev/sda
cat /sda7/etc/fvdwversion