plugout.net

Hello
Newbie here. Stumbled across this after a lot of desperate searching for solutions.

Situation:
I have a Networkspace 2 that was running without any issues until some months back. Suddenly it seems, I have lost access to my Openshare drive which I use for backing up files but also to store most of my working documents, photos, music etc. I did not run any upgrades on the device. I cannot browse it from Windows Explorer or map any drives to the shares on the NAS. I am running the Lacie Network assistant and from that I can see the device but cannot connect to it using the Connect Manually option *in fact I don't recall ever being able to do that*. I am able to connect to the dashboard using the web access option from the Lacie Network Assistant. I can navigate to the Openshare folder but there are no files in it. The drive information does show that there is over 100gb of data on it.

Setup:
I am running Windows 10. Originally this Networkspace2 was connected to another computer running Windows95. I have been using it connected to the current computer on Win10 for some time - the loss of access seems to have occurred potentially after an abrupt loss of power to the device. I have never been able to successfully upgrade the firmware of the device using the Lacie upgrade capsule - it simply doesn't accept it.

HELP!!
Is there a way to restore access to my files and the underlying structure? I have tried all tricks short of a factory reset that is recommended - a bit wary of doing it and lose all access to the device and all the files - even if Lacie seems to indicate that it won't delete the data.

Note: I have not tried to install the fvdw-sl yet. I will be happy to try it but want to see what others say first.

Screen shots are attached covering what I see when trying to access it various ways.

What is your goal? Recover your data or get the device working again?

I guess first option recover your data.
You could load our standalone kernel using the fvdw-sl console (see download topic of this forum) and try mount the data partition to see what is still there or investigate what is wrong with the disk if mount fails.
Doing this will not affect you data as the kernel runs in RAM.

fvdw wrote:What is your goal? Recover your data or get the device working again?

I guess first option recover your data.
You could load our standalone kernel using the fvdw-sl console (see download topic of this forum) and try mount the data partition to see what is still there or investigate what is wrong with the disk if mount fails.
Doing this will not affect you data as the kernel runs in RAM.

Thanks for the response. I would ideally like to do both - recover the data and get the device working again - whereby I can access it as a share on the Network to back files onto or also use as a media server as it was before.

I will start with the fvdw-sl console - is that version 18.1 that is referred to on this post: http://plugout.net/viewtopic.php?f=7&t=3086 with the five separate rar files?

@fvdw I have installed the software but am struggling to find any posts that clearly outline what I should do to check the device and then gain access to the files? Can someone point me in the right direction? I don't want to install the firmware until I get the files copied off the device - or am able to repair the current firmware/operating system.

oke, first read this topic http://plugout.net/viewtopic.php?f=7&t=2645 to be sure you have a correct setup, using wired connection and disabling all other network cards is important otherwise the console will not detect your ns2

When ready poweroff your ns2 and start fvdw-sl console and choose as action load and start standalone kernel.
There is a help displayed in the main window of the console.
Select the kirkwood standalone kernel and start your ns2 when the command window mentions : waiting for uboot..
The console will detect the start of the ns2 and upload the kernel and start it, after 15 sec a telnet window will open when correct enabling you to login, report back when you have telnet access

I made some edits in last post to make it more clear

fvdw wrote:oke, first read this topic http://plugout.net/viewtopic.php?f=7&t=2645 to be sure you have a correct setup, using wired connection and disabling all other network cards is important otherwise the console will not detect your ns2

When ready poweroff your ns2 and start fvdw-sl console and choose as action load and start standalone kernel.
There is a help displayed in the main window of the console.
Select the kirkwood standalone kernel and start your ns2 when the command window mentions : waiting for uboot..
The console will detect the start of the ns2 and upload the kernel and start it, after 15 sec a telnet window will open when correct enabling you to login, report back when you have telnet access

Ok I got the Telnet window to open :)

Try to mount the data partition

Code: Select all

mkdir /sda2
mount /dev/sda2 /sda2

If that succeeds give command to list content

Code: Select all

ls -al /sda2

Post the output

If it fails to mount post the error message

If the mount error is related to file system we can try to repair it. lacie uses xfs file system
To be able to repair it or check it you must upload some programs.
In the telnet window type

Code: Select all

/fvdw-sl-programs

A menu should be presented now, chose nr 4 Upload and extract glibc mini and tools
When succesfully done give command

Code: Select all

xfs_repair -n /dev/sda2

The -n option will prevent xfs_repair from actually making changes , it will with that option only list what actions need to be done to perform it.
Better have a look to those first before trying a repair. Be aware that performing xfs_repair is not without risk. But if the file system is corrupt it is the only chance you have to get your data back

fvdw wrote:Try to mount the data partition

Code: Select all

mkdir /sda2
mount /dev/sda2 /sda2

If that succeeds give command to list content

Code: Select all

ls -al /sda2

Post the output

If it fails to mount post the error message

If the mount error is related to file system we can try to repair it. lacie uses xfs file system
To be able to repair it or check it you must upload some programs.
In the telnet window type

Code: Select all

/fvdw-sl-programs

A menu should be presented now, chose nr 4 Upload and extract glibc mini and tools
When succesfully done give command

Code: Select all

xfs_repair -n /dev/sda2

The -n option will prevent xfs_repair from actually making changes , it will with that option only list what actions need to be done to perform it.
Better have a look to those first before trying a repair. Be aware that performing xfs_repair is not without risk. But if the file system is corrupt it is the only chance you have to get your data back

the output looks like this:

Code: Select all

root@fvdw-sta-kirkwood:/ # ls -al /sda2
total 0
drwxr-xr-x    9 root     root            95 Feb 15 16:38 .
drwxrwxrwt   13 root     root           360 Feb 15 23:59 ..
drwxr-xr-x    2 root     root             6 Feb 15 16:38 afp_db
drwxr-xr-x    2 root     root            14 Jan  8  2000 images
drwxr-xr-x    3 root     root            18 Jan  1  1970 share
drwxr-xr-x    6 root     root            38 Apr 10  2010 shares
drwxr-xr-x    2 root     root             6 Feb 15 16:38 tmp
drwxr-xr-x    3 root     root            25 Apr 23  2019 torrent_dir
drwxr-xr-x    6 root     root            68 Jan  1  2000 var
root@fvdw-sta-kirkwood:/ #

Oke, so filesystem is ok
Now look in the different folders

Code: Select all

ls -al /sda2/share
ls -al /sda2/shares
ls -al /sda2/tmp
Etc