General NAS-Central Forums

Welcome to the NAS community
It is currently Sat Nov 25, 2017 12:16 am

All times are UTC




Post new topic Reply to topic  [ 54 posts ]  Go to page 1, 2, 3, 4  Next
Author Message
PostPosted: Tue Apr 28, 2015 12:54 pm 
Offline

Joined: Tue Apr 28, 2015 12:42 pm
Posts: 27
I have a Lacie 5big network 2.

Recently I tried to reserve some space for iSCSI. After setting it in the dashboard I received a generic error I cannot remember. So I restarted the device. It started but now I cannot access any files on it, cannot access the dashboard (getting this message: Your device may be powering on. Please try again in a few minutes.) and the front led keeps blinking blue every 0,5 seconds.

I can ping the device on its IP address but that is about it. No access at all. When I swap the disks to another identical Lacie it acts the same so no hardware error I guess.

Tried to reset the device to factory default but when it starts it should blink red/blue and front led stays on blue for about a minute and then it starts to blink blue again. Left the device for almost a week now like this but still no change.

I have critical data on this device. Can somebody please help me out here?

Thanks in advance!

Frank


Top
 Profile  
 
PostPosted: Tue Apr 28, 2015 6:50 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6079
How are your command line skills? Fvdw has some interesting tool called 'stand alone kernel', which you can use to boot an altenative kernel, which gives you shell access, without touching the disk. This tool can be used to investigate what is going wrong, or manually perform a factory reset, or copy your data.

More info here.


Top
 Profile  
 
PostPosted: Tue Apr 28, 2015 9:20 pm 
Offline

Joined: Tue Apr 28, 2015 12:42 pm
Posts: 27
If you can give me some hints, I am more than willing to investigate.
After reading this forum this afternoon I already discovered that part.

But I am afraid I might do something wrong and erase the data on my disks.

Kind regards,

Frank


Top
 Profile  
 
PostPosted: Wed Apr 29, 2015 7:51 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6079
Sure. First part is get the stand alone kernel running. For that part you can find instructions on plugout.net.

When you have shell access execute
Code:
cat /proc/partitions
cat /proc/mounts
cat /proc/mdstat
to find out the partitions, the mounts, and the state of the raid arrays. Actually I don't think the latter 2 will tell anything, as the stand alone kernel won't try to assemble the Lacie file systems.


Top
 Profile  
 
PostPosted: Thu Apr 30, 2015 11:40 am 
Offline

Joined: Tue Apr 28, 2015 12:42 pm
Posts: 27
Thanks! Will be away until the 2nd week of May.
Afterwards I will play around and let you know the results.

Kind regards,

Frank


Top
 Profile  
 
PostPosted: Tue May 12, 2015 2:28 pm 
Offline

Joined: Tue Apr 28, 2015 12:42 pm
Posts: 27
Steps I have taken.

1. downloaded fvdw-sl-console-5-3-15-1-18feb2014-64bits and extracted it.
2. physically connected the NAS and my laptop to a switch.
3. set my ip address to 192.168.10.10, disabled firewall and antivirus.
4. shut down Lacie.
5. opened FVDW-SL and changed ip address for NAS to 192.168.10.6 (originally it was 192.168.10.6).
6. click action, select standalone kernel, load and start.
7. select UIMAGE-395-NWSP2CL-179-standalone file.
8. turn on NAS.
9. I can see the tftp32 software upload the file to the NAS.
Connection received from 192.168.10.6 on port 1672 [12/05 16:12:17.582]
Read request for file <UIMAGE-395-NWSP2CL-179-standalone>. Mode octet [12/05 16:12:17.582]
OACK: <timeout=5,> [12/05 16:12:17.582]
Using local port 60786 [12/05 16:12:17.582]
<UIMAGE-395-NWSP2CL-179-standalone>: sent 10453 blks, 5351920 bytes in 3 s. 0 blk resent [12/05 16:12:20.915]
10. dos box gives information about transfer and starting kernel.
11. Dtelnet starts, but couldn't connect to the NAS on ip address 192.168.10.6.

Tried the same with ip address 192.168.1.252 and my computer being 192.168.1.10. Still no luck.

Cannot telnet to the NAS. Cannot ping the NAS.

Please help me out here!


Top
 Profile  
 
PostPosted: Tue May 12, 2015 4:26 pm 
Offline

Joined: Wed Mar 18, 2009 11:13 pm
Posts: 773
This evening I will release an updated version of the fvdw-sl-console an new standalone kernels. This new setup will set the ip address of the nas automatic tovthe value that is set for the nas in the console and should solve telnet connection issues on LAN not using ip starting with 192.168.0 or 192.168.1

If you cannot wait you can do following. In your case you use an ip pool starting with 192.168.10 , the old console in principle is designed to work with ip starting with 192.168.0 and 192.168.1. And assignbitself the static addresses 192.168.0.252 and 192.168.1.252. These wont be accesible in your lan set up. However the standalone kernel will also ask a dynamic ip from the dhcp server in your lan. So look in the client list of dhcp server to find it. It is not nessary the same as used by uboot to upload the kernel. If that doesn't work change your network ip pool so you can use the static addresses as described. Last option wait for the new release.


Top
 Profile  
 
PostPosted: Wed May 13, 2015 6:46 am 
Offline

Joined: Tue Apr 28, 2015 12:42 pm
Posts: 27
Dear fvdw,

I will wait for the updated version and will let you know.

Thanks!

Frank


Top
 Profile  
 
PostPosted: Mon May 18, 2015 8:04 am 
Offline

Joined: Tue Apr 28, 2015 12:42 pm
Posts: 27
Finally got the standalone kernel to work and I can use telnet now.

I ran:
cat /proc/partitions
cat /proc/mounts
cat /proc/mdstat
fdisk -l

But I am not a Linux guy and can't make much of it. Disk /dev/mtdblock0 doesn't contain a valid partition table and disk /dev/mtdblock1 doesn't contain a valid partition table. That doesn't sound ok.

Trying to figure out a way to access my old shares and copy everything to another disk. Can anyone help or should I post this on plugout.net?

Below the output of the commands.

Thanks,

Frank

Code:
root@fvdw-sta-kirkwood:/ # cat /proc/partitions
major minor  #blocks  name

  31        0        500 mtdblock0
  31        1          4 mtdblock1
   8        0  976762584 sdc
   8        1          1 sdc1
   8        2  974751907 sdc2
   8        5     256977 sdc5
   8        6       8001 sdc6
   8        7       8001 sdc7
   8        8     851413 sdc8
   8        9     875511 sdc9
   8       10       8001 sdc10
   8       16  976762584 sdb
   8       17          1 sdb1
   8       18  974751907 sdb2
   8       21     256977 sdb5
   8       22       8001 sdb6
   8       23       8001 sdb7
   8       24     851413 sdb8
   8       25     875511 sdb9
   8       26       8001 sdb10
   8       32  976762584 sda
   8       33          1 sda1
   8       34  974751907 sda2
   8       37     256977 sda5
   8       38       8001 sda6
   8       39       8001 sda7
   8       40     851413 sda8
   8       41     875511 sda9
   8       42       8001 sda10
   8       48  976762584 sde
   8       49          1 sde1
   8       50  974751907 sde2
   8       53     256977 sde5
   8       54       8001 sde6
   8       55       8001 sde7
   8       56     851413 sde8
   8       57     875511 sde9
   8       58       8001 sde10
   8       64  976762584 sdd
   8       65          1 sdd1
   8       66  974751907 sdd2
   8       69     256977 sdd5
   8       70       8001 sdd6
   8       71       8001 sdd7
   8       72     851413 sdd8
   8       73     875511 sdd9
   8       74       8001 sdd10

root@fvdw-sta-kirkwood:/ # cat /proc/mounts
rootfs / rootfs rw,size=255048k,nr_inodes=63762 0 0
none /proc proc rw,relatime 0 0
none /sys sysfs rw,relatime 0 0
none /dev/pts devpts rw,relatime,mode=600 0 0

root@fvdw-sta-kirkwood:/ # cat /proc/mdstat
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4]
unused devices: <none>

root@fvdw-sta-kirkwood:/ # fdisk -l

Disk /dev/mtdblock0: 0 MB, 512000 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock0 doesn't contain a valid partition table

Disk /dev/mtdblock1: 0 MB, 4096 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Disk /dev/mtdblock1 doesn't contain a valid partition table

Disk /dev/sdc: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdc1               1         250     2008093+  5 Extended
/dev/sdc2             251      121601   974751907+ 83 Linux
/dev/sdc5               1          32      256977  82 Linux swap
/dev/sdc6              33          33        8001  83 Linux
/dev/sdc7              34          34        8001  83 Linux
/dev/sdc8              35         140      851413+ 83 Linux
/dev/sdc9             141         249      875511  83 Linux
/dev/sdc10            250         250        8001  83 Linux

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sdb1               1         250     2008093+  f Win95 Ext'd (LBA)
/dev/sdb2             251      121601   974751907+ 83 Linux
/dev/sdb5               1          32      256977  83 Linux
/dev/sdb6              33          33        8001  83 Linux
/dev/sdb7              34          34        8001  83 Linux
/dev/sdb8              35         140      851413+ 83 Linux
/dev/sdb9             141         249      875511  83 Linux
/dev/sdb10            250         250        8001  83 Linux

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sda1               1         250     2008093+  5 Extended
/dev/sda2             251      121601   974751907+ 83 Linux
/dev/sda5               1          32      256977  82 Linux swap
/dev/sda6              33          33        8001  83 Linux
/dev/sda7              34          34        8001  83 Linux
/dev/sda8              35         140      851413+ 83 Linux
/dev/sda9             141         249      875511  83 Linux
/dev/sda10            250         250        8001  83 Linux

Disk /dev/sde: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks  Id System
/dev/sde1               1         250     2008093+  5 Extended
/dev/sde2             251      121601   974751907+ 83 Linux
/dev/sde5               1          32      256977  82 Linux swap
/dev/sde6              33          33        8001  83 Linux
/dev/sde7              34          34        8001  83 Linux
/dev/sde8              35         140      851413+ 83 Linux
/dev/sde9             141         249      875511  83 Linux
/dev/sde10            250         250        8001  83 Linux


Top
 Profile  
 
PostPosted: Mon May 18, 2015 12:24 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6079
Quote:
Disk /dev/mtdblock0 and /dev/mtdblock1 doesn't contain a valid partition table. That doesn't sound ok.
It's OK. That are flash partitions, not disks. They are not assumed to have a partition table.

I see one weird thing. In /proc/partitions 5 disks are recognized (sda,sdb,sdc,sdd,sde), but in your fdisk -l listing /dev/sdd is lacking. Did you do a bad copy&paste job, or did the disk indeed disappear between the 2 commands?

Anyhow, you seem to have at least 4 disks with a readable partition table. Let's have a look at the raid metadata. Can you post the output of
Code:
mdadm --examine /dev/sd[abcde]


Top
 Profile  
 
PostPosted: Mon May 18, 2015 12:34 pm 
Offline

Joined: Tue Apr 28, 2015 12:42 pm
Posts: 27
Hi Mijzelf,

Just posted several outputs on plugout.net. But here you go.

In the web console I issued the iSQSI command to reserve (I think 1TB) for it and after the reboot it refused to reboot.

Regards,

Frank

Code:
root@fvdw-sta-kirkwood:/ # mdadm --examine /dev/sd[abcde]
/dev/sda:
   MBR Magic : aa55
Partition[0] :      4016187 sectors at           63 (type 05)
Partition[1] :   1949503815 sectors at      4016250 (type 83)
/dev/sdb:
   MBR Magic : aa55
Partition[0] :      4016187 sectors at           63 (type 0f)
Partition[1] :   1949503815 sectors at      4016250 (type 83)
/dev/sdc:
   MBR Magic : aa55
Partition[0] :      4016187 sectors at           63 (type 05)
Partition[1] :   1949503815 sectors at      4016250 (type 83)
/dev/sde:
   MBR Magic : aa55
Partition[0] :      4016187 sectors at           63 (type 05)
Partition[1] :   1949503815 sectors at      4016250 (type 83)


Previous output on plugout.net

Code:
root@fvdw-sta-kirkwood:/ # ls -l /dev/sd[abcde]*
brw-rw----    1 root     root        8,   0 May  3 11:01 /dev/sda
brw-rw----    1 root     root        8,   1 May  3 11:01 /dev/sda1
brw-rw-rw-    1 root     root        8,  10 May  3 11:01 /dev/sda10
brw-rw----    1 root     root        8,   2 May  3 11:01 /dev/sda2
brw-rw----    1 root     root        8,   3 May  3 11:01 /dev/sda3
brw-rw----    1 root     root        8,   4 May  3 11:01 /dev/sda4
brw-rw----    1 root     root        8,   5 May  3 11:01 /dev/sda5
brw-rw----    1 root     root        8,   6 May  3 11:01 /dev/sda6
brw-rw----    1 root     root        8,   7 May  3 11:01 /dev/sda7
brw-rw----    1 root     root        8,   8 May  3 11:01 /dev/sda8
brw-rw-rw-    1 root     root        8,   9 May  3 11:01 /dev/sda9
brw-rw-r--    1 root     root        8,  16 May  3 11:01 /dev/sdb
brw-r--r--    1 root     root        8,  17 May  3 11:01 /dev/sdb1
brw-r--r--    1 root     root        8,  18 May  3 11:01 /dev/sdb2
brw-rw----    1 root     root        8,  19 May  3 11:01 /dev/sdb3
brw-rw----    1 root     root        8,  20 May  3 11:01 /dev/sdb4
brw-rw----    1 root     root        8,  21 May  3 11:01 /dev/sdb5
brw-rw----    1 root     root        8,  22 May  3 11:01 /dev/sdb6
brw-rw----    1 root     root        8,  23 May  3 11:01 /dev/sdb7
brw-rw----    1 root     root        8,  24 May  3 11:01 /dev/sdb8
brw-rw----    1 root     root        8,  32 May  3 11:01 /dev/sdc
brw-rw----    1 root     root        8,  33 May  3 11:01 /dev/sdc1
brw-rw----    1 root     root        8,  34 May  3 11:01 /dev/sdc2
brw-rw----    1 root     root        8,  35 May  3 11:01 /dev/sdc3
brw-rw----    1 root     root        8,  36 May  3 11:01 /dev/sdc4
brw-rw----    1 root     root        8,  37 May  3 11:01 /dev/sdc5
brw-rw----    1 root     root        8,  38 May  3 11:01 /dev/sdc6
brw-rw----    1 root     root        8,  39 May  3 11:01 /dev/sdc7
brw-rw----    1 root     root        8,  40 May  3 11:01 /dev/sdc8
brw-rw----    1 root     root        8,  64 May  3 11:01 /dev/sde
brw-rw----    1 root     root        8,  65 May  3 11:01 /dev/sde1
brw-rw----    1 root     root        8,  66 May  3 11:01 /dev/sde2

root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.5

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


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************

Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 00000000-0000-0000-0000-000000000000
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 8-sector boundaries
Total free space is 5477 sectors (2.7 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   2         4016250      1953520064   929.6 GiB   8300  Linux filesystem
   5             126          514079   251.0 MiB   8200  Linux swap
   6          514143          530144   7.8 MiB     8300  Linux filesystem
   7          530208          546209   7.8 MiB     8300  Linux filesystem
   8          546273         2249099   831.5 MiB   8300  Linux filesystem
   9         2249163         4000184   855.0 MiB   8300  Linux filesystem
  10         4000248         4016249   7.8 MiB     8300  Linux filesystem

root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.5

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


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************

Disk /dev/sdb: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 00000000-0000-0000-0000-000000000000
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 8-sector boundaries
Total free space is 5477 sectors (2.7 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   2         4016250      1953520064   929.6 GiB   8300  Linux filesystem
   5             126          514079   251.0 MiB   8300  Linux filesystem
   6          514143          530144   7.8 MiB     8300  Linux filesystem
   7          530208          546209   7.8 MiB     8300  Linux filesystem
   8          546273         2249099   831.5 MiB   8300  Linux filesystem
   9         2249163         4000184   855.0 MiB   8300  Linux filesystem
  10         4000248         4016249   7.8 MiB     8300  Linux filesystem

root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sdc
GPT fdisk (gdisk) version 0.8.5

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


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************

Disk /dev/sdc: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 00000000-0000-0000-0000-000000000000
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 8-sector boundaries
Total free space is 5477 sectors (2.7 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   2         4016250      1953520064   929.6 GiB   8300  Linux filesystem
   5             126          514079   251.0 MiB   8200  Linux swap
   6          514143          530144   7.8 MiB     8300  Linux filesystem
   7          530208          546209   7.8 MiB     8300  Linux filesystem
   8          546273         2249099   831.5 MiB   8300  Linux filesystem
   9         2249163         4000184   855.0 MiB   8300  Linux filesystem
  10         4000248         4016249   7.8 MiB     8300  Linux filesystem

root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sdd
GPT fdisk (gdisk) version 0.8.5

Problem opening /dev/sdd for reading! Error is 2.
The specified file does not exist!

root@fvdw-sta-kirkwood:/ # gdisk -l /dev/sde
GPT fdisk (gdisk) version 0.8.5

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


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format.
***************************************************************

Disk /dev/sde: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 00000000-0000-0000-0000-000000000000
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 8-sector boundaries
Total free space is 5477 sectors (2.7 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   2         4016250      1953520064   929.6 GiB   8300  Linux filesystem
   5             126          514079   251.0 MiB   8200  Linux swap
   6          514143          530144   7.8 MiB     8300  Linux filesystem
   7          530208          546209   7.8 MiB     8300  Linux filesystem
   8          546273         2249099   831.5 MiB   8300  Linux filesystem
   9         2249163         4000184   855.0 MiB   8300  Linux filesystem
  10         4000248         4016249   7.8 MiB     8300  Linux filesystem


root@fvdw-sta-kirkwood:/ # mdadm --examine /dev/sda2
/dev/sda2:
          Magic : a92b4efc
        Version : 0.90.00
           UUID : 9b62e8da:8318eaee:02e8a5b3:5e7f9db2
  Creation Time : Thu Jan  1 00:01:07 1970
     Raid Level : raid5
  Used Dev Size : 974751808 (929.60 GiB 998.15 GB)
     Array Size : 3899007232 (3718.38 GiB 3992.58 GB)
   Raid Devices : 5
  Total Devices : 4
Preferred Minor : 4

    Update Time : Mon May 18 09:28:40 2015
          State : clean
 Active Devices : 4
Working Devices : 4
 Failed Devices : 1
  Spare Devices : 0
       Checksum : b88d136b - correct
         Events : 309582

         Layout : left-symmetric
     Chunk Size : 64K

      Number   Major   Minor   RaidDevice State
this     2       8        2        2      active sync   /dev/sda2

   0     0       8       34        0      active sync   /dev/sdc2
   1     1       8       18        1      active sync   /dev/sdb2
   2     2       8        2        2      active sync   /dev/sda2
   3     3       8       66        3      active sync   /dev/sde2
   4     4       0        0        4      faulty removed


Top
 Profile  
 
PostPosted: Mon May 18, 2015 12:43 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6079
You might be able to assemble the (degraded) array:
Code:
mdadm --assemble /dev/md0 /dev/sd[abce]2 --run
and mount it.
Code:
mkdir -p /tmp/mountpoint
mount -o ro /dev/md0 /tmp/mountpoint


So there is definitely something wrong with sdd. It's not listed by fdisk -l, it's not found by gdisk, and it's removed from the raid array.


Top
 Profile  
 
PostPosted: Mon May 18, 2015 12:51 pm 
Offline

Joined: Tue Apr 28, 2015 12:42 pm
Posts: 27
Ok, that worked. :D
If I now go to /tmp/mountpoint/shares I see folder 1 to 5 and an ls of each folder gives me the data.

e.g.
Code:
root@fvdw-sta-kirkwood:/tmp/mountpoint/shares # ls 1
Diverse                       SERA OVERZETTEN IN AMSTERDAM
Oude gebruikers       Virtuele Servers


You are about to be a life saver!

If I look at the outputs I have given, it appears to me 1 disk (the last one) is causing these problems?

How do I proceed from here? Can I take out that drive and start the NAS? Afterwards put it back on so it may recover that disk? Or put it a new disk? Please advise. I am not very familiar with Linux.

Kind regards,

Frank


Top
 Profile  
 
PostPosted: Mon May 18, 2015 1:27 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6079
sdd is not the last disk, I think, but the last but one. sde is the last one.

It is possible that the box will boot normally when you just pull that disk, and reboot the box. Maybe the OS was tricked by the blinking effect of that disk.

But if your data is important, I would first copy it away to another (usb) disk.

I think that disk is dead. So you should insert a new one.


Top
 Profile  
 
PostPosted: Mon May 18, 2015 1:32 pm 
Offline

Joined: Tue Apr 28, 2015 12:42 pm
Posts: 27
Ok, first things first. So I need to attach a large usb disk to copy the data to the usb disk.

Or can I copy it to another NAS using the FTP protocol?

Can you give me instructions how to do that (I prefer using FTP and network) or point me to a post where this is explained?

Regards,

Frank


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

All times are UTC


Who is online

Users browsing this forum: No registered users and 8 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