DrayTek UK Users' Community Forum

Help, Advice and Solutions from DrayTek Users

Vigor 2760 not recording SysLog to USB stick

More
03 Oct 2017 09:48 #7 by piste basher
Replied by piste basher on topic Re: Vigor 2760 not recording SysLog to USB stick
FAT16 or, preferably, FAT32

Please Log in or Create an account to join the conversation.

  • ben_london
  • Topic Author
  • Offline
  • New Member
  • New Member
More
03 Oct 2017 10:53 #8 by ben_london
Replied by ben_london on topic Re: Vigor 2760 not recording SysLog to USB stick

Piste Basher wrote: FAT16 or, preferably, FAT32


OK, the stick is formatted as FAT32, so no luck there :(

Please Log in or Create an account to join the conversation.

More
03 Oct 2017 17:02 #9 by piste basher
Replied by piste basher on topic Re: Vigor 2760 not recording SysLog to USB stick
1MB is quite a lot of logs I expect - maybe you haven't reached that yet? I've just plugged a stick into my 2925 to see what happens.

Edit - well mine is showing 2 pages already, so it looks as though it's not the 1MB that's the problem.

Please Log in or Create an account to join the conversation.

  • ben_london
  • Topic Author
  • Offline
  • New Member
  • New Member
More
03 Oct 2017 20:06 #10 by ben_london
Replied by ben_london on topic Re: Vigor 2760 not recording SysLog to USB stick

Piste Basher wrote: 1MB is quite a lot of logs I expect - maybe you haven't reached that yet? I've just plugged a stick into my 2925 to see what happens.

Edit - well mine is showing 2 pages already, so it looks as though it's not the 1MB that's the problem.



Yup, I can't work it out. Tried a 3rd USB stick just now, formatted to FAT32.
All looks good but it doesn't event write the Syslog folder to drive.

Please Log in or Create an account to join the conversation.

More
25 Jan 2018 07:27 #11 by geoffa48
Just wondering if there was any resolution to this as I have the same problem.

Please Log in or Create an account to join the conversation.

More
25 Jan 2018 20:07 #12 by geoffa48
Just been trying this in newly released 3.8.7 and it appears to be fixed, should anyone be interested.

Please Log in or Create an account to join the conversation.