fvdw wrote: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
fvdw wrote:I again edited my last post, commands were incomplete
jojodude wrote:fvdw wrote: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
Ok as I navigate through the folders I can see the files that I had on the device. What do I do to gain access to them via File Explorer and be able to mount a share drive there?
Thank you so much for your prompt responses so far and getting me to this point.
is there someway to install the firmware from Lacie using this mechanism OR do I need to download all the files on to my computer first and reformat and install the fvdw firmware.
fvdw wrote:
In which folder did you find them?, are they in tmp folder?
And is there on the disk a folder with name OpenShare ? (i think it should be in the shares folder).
I am not very familiar with lacie firmware but I believe in case of factory restore it moves the data files to a folder in tmp.
You could use the linux mv command to move the files to the OpenShare folder. Then they should become visible in explorer
fvdw wrote:Another way to get the files from the disk is connecting an usb disk formatted in fat32 to your usb port.
As last resort you could try to use a mini ftp server that can be installed on the standalone kernel
For that I need to have alook in my notes how this can be done, but you will need a ftp clinet to access the server.
/dev/sda2 /media/internal_6 xfs rw,nosuid,nodev,usrquota,prjquota 0 0
/dev/sda2 /lacie/tmp xfs rw,nosuid,nodev,usrquota,prjquota 0 0
/dev/sda2 /lacie/var xfs rw,nosuid,nodev,usrquota,prjquota 0 0
/dev/sda2 /lacie/torrent_dir xfs rw,nosuid,nodev,usrquota,prjquota 0 0
/dev/sda2 /lacie/afp_db xfs rw,nosuid,nodev,usrquota,prjquota 0 0
/dev/loop1p1 /media/external_usb_9 vfat rw,nosuid,nodev,fmask=0000,dmask=0000,codepage=cp437,iocharset=iso8859-1 0 0
/dev/sda2 /shares/MyShare xfs rw,nosuid,nodev,usrquota,prjquota 0 0
/dev/sda2 /shares/OpenShare xfs rw,nosuid,nodev,usrquota,prjquota 0 0
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
mkdir /sdb1
mount /dev/sdb1 /sdb1
vsftpd &
fvdw wrote:Apparently one of the folders in /sda2/shares are mounted on /shares/Myshare and OpenShare folders in the system root file system of lacie. Why they are not visible in explorer is a mystery. Everythings seem to be ok, if we can mount sda2 the lacie firmware should also be able :scratch
However you mentioned you are using windows 10.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
That would mean it work in your windows 10 setup
Anyhow point to check, Windows 10 by default disables smb1 protocol and then you will not see the nas in explorer. Before going further lets clarify this point.
Did you change something in windows 10 (in windows setup you can enable/disable smb1 protoco)
about usb disk
If you have a usb disk formatted in fat32 connect it to your nas.
It should be visible as sdb1
mount it
- Code: Select all
mkdir /sdb1
mount /dev/sdb1 /sdb1
Now you can use sdb1 folder to copy the folders containing your files (linux cp command)
Else I could format a normal USB Key I suppose and use that instead?
fvdw wrote:using the mini ftp server
Run on the telnet window the command: fvdw-sl-programs
Then a menu will appear
select "Upload and extract glibc mini and tools"
fvdw wrote:After start the server
- Code: Select all
vsftpd &
Connect to the server using a ftp client like FileZilla
username: root
password: giveit2me
port 21
ip: nas ip see main window of the fvdw-sl console
VERY IMPORTANT: be sure your ftp client is set to binary transfer mode !
If you don't do that then some file will become corrupt as in ftp protocol will take out <CR> characters in certain files. This is not an error but by design of the protocol. If you use binary transfer this won't happen.
Return to Lacie Network Space vs2 and max version
Users browsing this forum: No registered users and 4 guests