plugout.net

the instructions say:- "Then Click on the button Accept and you must get this success message :
Ok: Install patch successful".

I don't get en error-message, but neither do i get

Code: Select all

Install patch successful

Instead I get a message saying (roughly) "Web interface needs re-starting". I cliick on 'OK', the web-page does blank for less than 1 second, then reappears. The "success" message never shows.

I've now tried three times: same every time.

Meanwhile on <Fileshare> page <Backup> tab the message "No USB disk found" continues to be displayed, despite the fact that this

Code: Select all

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 1
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=1d6b ProdID=0002 Rev=04.14
S:  Manufacturer=Linux 4.14.133 ehci_hcd
S:  Product=EHCI Host Controller
S:  SerialNumber=orion-ehci.0
C:  #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub

T:  Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  2 Spd=480 MxCh= 0
D:  Ver= 2.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=18a5 ProdID=0237 Rev=05.10
S:  Manufacturer=Verbatim
S:  Product=Portable USB 3.0 Drive
S:  SerialNumber=1609100004018952
C:  #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=500mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage


is showing on the <Attached Devices> page <USB_Devices> tab

Any ideas?

Hi

So your USB 3.0 is detected but however if the firmware failed to mount a partition from it like an external share (bad fs or you enabled the advanced mode) then the backup claims rightly there is no usb share !

Can you post a screen capture of the external disks menu

Hi Jocko

Thanks for the prompt response.

I'm sorry but I don't know what you mean by " the external disks menu".

Does the attached tell you what you need to know? (Disk 2 is the usb drive I'm trying to use).

EDIT
Having typed this and tried to upload a .png file (77KB), it doesn't get uploaded for some reason. Is that above the limit?

EDIT 2

I guess you meant this (silly of me. Sorry!)

Hi

Yes it is the expected screen capture :thumbup
So you use as option the default mount mode: all partition on an external disk is mounted as an external share.

But it seems there is no partition mounted from any usb drive according with your capture (not sure because the capture does not content the related table or very partially, I think only the hearder)

This would mean either the fs on the partition is corrupted or the firmware does not support it.

Please to post

Code: Select all

cat /proc/partitions

Hi

Here it is

Code: Select all

login as: root
root@192.168.1.103's password:
root@fvdwsl-base:/ # cat /proc/partitions
major minor  #blocks  name

   1        0       4096 ram0
   1        1       4096 ram1
   1        2       4096 ram2
   1        3       4096 ram3
   1        4       4096 ram4
   1        5       4096 ram5
   1        6       4096 ram6
   1        7       4096 ram7
   1        8       4096 ram8
   1        9       4096 ram9
   1       10       4096 ram10
   1       11       4096 ram11
   1       12       4096 ram12
   1       13       4096 ram13
   1       14       4096 ram14
   1       15       4096 ram15
  31        0        500 mtdblock0
  31        1          4 mtdblock1
   8        0  976762584 sda
   8        1     514080 sda1
   8        2     514080 sda2
   8        3     514080 sda3
   8        4          1 sda4
   8        5     835380 sda5
   8        6      64260 sda6
   8        7     514080 sda7
   8        8  973482772 sda8
   8       16  976762582 sdb
   8       17     131072 sdb1
   8       18  976628736 sdb2
root@fvdwsl-base:/ #


But I'm puzzled by this

(not sure because the capture does not content the related table or very partially, I think only the hearder)

becasue the screen capture included everything that appears on that tab; there is no related table.

So your usb is sdb drive, please to post

Code: Select all

gdisk -l /dev/sdb

and

Code: Select all

file -bs /dev/sdb1
file -bs /dev/sdb2

to see what is it their fs ?

Hi

Here's the output

Code: Select all

root@fvdwsl-base:/ # gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.5

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

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 1953525164 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 14DD9D44-CA40-11EA-AB8B-4CCC6A2DE693
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525130
Partitions will be aligned on 2048-sector boundaries
Total free space is 5481 sectors (2.7 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048          264191   128.0 MiB   0C01
   2          264192      1953521663   931.4 GiB   0700  Ba
root@fvdwsl-base:/ # file -bs /dev/sdb1
data
root@fvdwsl-base:/ # file -bs /dev/sdb2
Linux rev 1.0 ext3 filesystem data, UUID=55fa20e2-ae02-0e41-5501-761ad4aa4d61, volume name "fvdw_backup"
root@fvdwsl-base:/ #


Hi

Ok I think I understand your issue.

So sd1 is a Microsoft technical partition and I assume your disk was formatted for a microsoft usage.
Now It seems you changed the fs on sdb2 to be ext3 but you do not do it from your nwsp2 and surely from a Microsoft OS. This because the partition type did not have been updated: still 0700 whereas the right code should be 8300. Windows never update it when you format a disk.

So the firmware assumes it should find a windows partition and tries to mount it as such. Of course it fails!

Now you have to change the partition type, so do

Code: Select all

gdisk /dev/sdb

and do this sequence (type enter at each step)

Code: Select all

t
2
8300
p


So you should see the new partition table with the new partition type code on sdb2, then type 'w' and confirm 'y'

unplug your usb drive and replug it. After a short time sdb2 should be mounted as an external public share

Hi Jocko

That did the trick! Went without a hitch.

Thanks very much.

Robert

Nice !

Anyhow I think we have to update the firmware to avoid such a behaviour