These are my settings for a Buffalo LS220D in NAVIGATOR ->Management -> Name/Time/Language -> Time -> Edit
******************************** (The firmware is up to date.)
Date/Time Source: X means Selected
X Enable
NTP IP Address*: ntp.jst.mffeed.ad.jp
X Use Default NTP Server
NTP Synchronization Frequency: Every 3 hours
Time Zone:
(UTC-05:00) Eastern Time (US & Canada)
After pressing "OK"
Get error message:
Failed to sync with NTP server. Settings were saved.
**************************************
Then selecting Name/Time/Language -> Time -> Edit
Shows: Date/Time Source: Enabled (02/24/2020 20:14:30)
SHOULD BE: (15:14:30) In ERROR by 5:00 hours.
This is causing a problem with the "Sleep Timer" it's OFF when it should be ON and vice versa.
**************************************
So I tried
Time Zone:
(UTC-10:00) Hawaii
Shows: Date/Time Source: Enabled (02/24/2020 15:20:01)
Which is what it should be.
********************************************
Three Questions:
1. Why do I get the error message:
Failed to sync with NTP server. Settings were saved.
2. Why do I have to set time zone to UTC -10:00 when I am in the Eastern US time zone of UTC -05:00
3. Should I be selecting a different time server? If so which one?
Thanks for any input.
Did you check your network settings? Is there a valid dns entry?
1) Set the correct time and timezone manually
2) activate ntp
I have had the following problem:
The nas can not sync if the timedifference is to big
Quote from: As3nd0r on February 25, 2020, 03:00:31 AM
Did you check your network settings? Is there a valid dns entry?
Forgive my ignorance but I don't know what you mean by this.
The NAS has an IP address of 192.168.X.X and is usable on the local LAN.
I can get to the settings in Navigator. Must be missing something here.
I'm assuming you mean something else.
Also I'm assuming this has nothing to do with FTP access to the files.
Thanks,
Herb
no worries, Right-click on the Linkstation icon in NasNavigator and open settings. Go into advanced settings - IP address and check if DHCP is enabled.
If DHCP is disabled, check the entries for gateway and primary and secondary DNS. If those are invalid or blank, your LinkStation will be working fine locally but won't be able to connect to anything outside your local network (including NTP server). Gateway = how do I get out of the local network. Typically your routers IP. DNS = what IP is behind abcdefg.com so I know where to go. Can be any valid DNS, i.e. your providers, google (8.8.8.8), 1.1.1.1 etc.
If DHCP is enabled, network settings are unlikely to be the issue here. (unless of course all DHCP clients have internet connectivity issues and the ones that are working are configured manually).
Quote from: As3nd0r on February 25, 2020, 10:33:35 PM
no worries, Right-click on the Linkstation icon in NasNavigator and open settings. Go into advanced settings - IP address and check if DHCP is enabled.
If DHCP is disabled, check the entries for gateway and primary and secondary DNS. If those are invalid or blank, your LinkStation will be working fine locally but won't be able to connect to anything outside your local network (including NTP server). Gateway = how do I get out of the local network. Typically your routers IP. DNS = what IP is behind abcdefg.com so I know where to go. Can be any valid DNS, i.e. your providers, google (8.8.8.8), 1.1.1.1 etc.
If DHCP is enabled, network settings are unlikely to be the issue here. (unless of course all DHCP clients have internet connectivity issues and the ones that are working are configured manually).
You were correct DHCP was disabled.
When I click on Enable I get the following message:
Default gateway and DNS server addresses cannot be changed because DHCP is enabled for LAN port 1.
Under Network Settings this appears but is grayed out: Default Gateway Address: 192.168.0.1 (This is address of router)
Querying of the time server (which I set to pool.ntp.org) worked.
However the address of the LS220 changed from 192.168.0.125 to 192.168.0.104
I assume this is due to DHCP being enabled.
Because I map this drive in windows explorer I would like to keep it at 192.168.0.125
Is there anyway to keep the LS220 address at an unchanging address like 192.168.0.125 ?
Many thanks, you have been very helpful.
Herb
I believe I have it working with a fixed address for the LS220. This is what I did.
Open Navigator ->Search Again -> Properties -> IP Address
Uncheck: Use DHCP , RenewIP address
Enter the following:
IP Address 192.168.0.125
Sub Mask 255.255.255.0
Default gate 192.168.0.1
Hit OK
Still in Navigator:
Menu -> Properties -> Open Settings -> Advanced Settings -> Network -> IP Address List
Double click LAN Port 1
Enter the following:
Default gate 192.168.0.1
Primary DNS Server 208.67.222.222 (use whatever you want these are OpenDNS)
Secondary DNS Server 208.67.220.220 ( Google is 8.8.8.8 or 8.8.4.4)
Hit Close
In my Archer C7 router I entered this: DHCP -> Reserved Addresses place:
MAC Address Reserved IP
84-AF-EC-XX-D8-xx 192.168.0.125 Enabled (MAC & IP as appropriate)
Comments or suggestions are welcome.
All I can say is it seems to be working okay.
Again thanks for the help.
Herb
That should work fine :)
Reviving old thread here:
The time has stopped working. In my last post, shown below, it apparently worked until the change to DST. Now I get a message it cannot sync to the time sever.
I use the SLEEP TIMER to shut the LS220 OFF for about 8 hours every day. If the time is incorrect the LS220 shuts off when I need to use it because of the apparently incorrect time.
I have also tried to use the local time which is synced to time.windows.com which is correct. However the LS220 seems to have the same problem with that.
I am coming to the conclusion that A.) the TIME function of my LS220 is buggy or B.) the LS220 SLEEP TIMER is buggy.
Idea or suggestions welcome.
Thanks in advance.
Burt
From Feb 2020:
I believe I have it working with a fixed address for the LS220. This is what I did.
Open Navigator ->Search Again -> Properties -> IP Address
Uncheck: Use DHCP , RenewIP address
Enter the following:
IP Address 192.168.0.125
Sub Mask 255.255.255.0
Default gate 192.168.0.1
Hit OK
Still in Navigator:
Menu -> Properties -> Open Settings -> Advanced Settings -> Network -> IP Address List
Double click LAN Port 1
Enter the following:
Default gate 192.168.0.1
Primary DNS Server 208.67.222.222 (use whatever you want these are OpenDNS)
Secondary DNS Server 208.67.220.220 ( Google is 8.8.8.8 or 8.8.4.4)
Hit Close
In my Archer C7 router I entered this: DHCP -> Reserved Addresses place:
MAC Address Reserved IP
84-AF-EC-XX-D8-xx 192.168.0.125 Enabled (MAC & IP as appropriate)
Quote from: burt on February 26, 2020, 08:27:38 AM
Because I map this drive in windows explorer I would like to keep it at 192.168.0.125
Is there anyway to keep the LS220 address at an unchanging address like 192.168.0.125 ?
You would need to set a static IP, which you have done.
Also, you can map drives with the NAS hostname (machine name), instead of the IP. That probably would be better anyway, it would completely avoid IP address changes.
As to the time problems:
Given the various bugs that exist with the LS220 series, I would not be surprised if one or both of these things are because of firmware bugs.
I am using that same time server: ntp.jst.mffeed.ad.jp with automatic settings on my terastation, and have not encountered that issue with the time server. I don't use the sleep modes.
What is the DHCP pool range for your archer router?
The reservation sounds fine, but I would suggest to use a static IP address that is not in the pool range.
My router uses 192.168.x.100 to 192.168.x.150 for DHCP.
I assign static IPs to my terastations that are outside of that 100 to 150 range.
Ethernet Frame size is at the default: 1500 bytes
Gateway - router internal address
DNS - router internal address
I wonder if your NAS is having problems resolving DNS.
Some DNS servers don't like 3rd party DNS queries (if a host is not part of a network, it won't resolve the address. The DNS server will just reject the request of the outside host).
Try changing the DNS IP to your archer gateway IP, and set the time server to automatic again with the sleep timer off as a test. This way you can at least see what is going on with the time server.
If it works, turn the sleep timer on.
I'm surprised the sleep timer would start acting up just because of daylight time. Maybe getting the time server back on automatic settings- will resolve that.
By chance, have your region's DST dates changed in the last ~10 years?
I believe NTP won't adjust the time if it gets to far out of sync. I believe you can disable NTP, set the correct time, then re-enable NTP to get things syncing again.
Kane 88
As to the time problems:
Given the various bugs that exist with the LS220 series, I would not be surprised if one or both of these things are because of firmware bugs.
I am using that same time server: ntp.jst.mffeed.ad.jp with automatic settings on my terastation, and have not encountered that issue with the time server. I don't use the sleep modes.
Sorry I did not mention this. I never got this to work without setting time zone to UTC -10 Hawaii. I live in Ohio.
I use(d) pool.ntp.org and could set the TZ to UTC -5 which is correct. Buffalo tech suggested this server.
What is the DHCP pool range for your archer router?
The reservation sounds fine, but I would suggest to use a static IP address that is not in the pool range.
My router uses 192.168.x.100 to 192.168.x.150 for DHCP. Mine is 192.168.x.100 to 192.168.0.199. Curious why you want to be out of the range.
I assign static IPs to my terastations that are outside of that 100 to 150 range.
Ethernet Frame size is at the default: 1500 bytes
Gateway - router internal address
DNS - router internal address
I wonder if your NAS is having problems resolving DNS. Changing this had no effect same error.
Some DNS servers don't like 3rd party DNS queries (if a host is not part of a network, it won't resolve the address. The DNS server will just reject the request of the outside host).
Try changing the DNS IP to your archer gateway IP, and set the time server to automatic again with the sleep timer off as a test. This way you can at least see what is going on with the time server.
If it works, turn the sleep timer on.
I'm surprised the sleep timer would start acting up just because of daylight time. Maybe getting the time server back on automatic settings- will resolve that.
I'm not sure that it happened at that time. I didn't start noticing the problem for several days or maybe a week after the change.
Thanks
Quote from: 1000001101000 on April 08, 2020, 08:25:29 AM
By chance, have your region's DST dates changed in the last ~10 years?
I believe NTP won't adjust the time if it gets to far out of sync. I believe you can disable NTP, set the correct time, then re-enable NTP to get things syncing again.
DST times have not changed recently that I am aware of.
I also believe the time has to be reasonably close and I have made sure that the time is correct within a minute or so. That produces no joy.
Thanks
Don't worry with the DHCP reservation. It's fine. I was just pointing out that a reservation isn't needed if you gave the NAS an IP like 192.168.x.40 or .240 for your setup, since neither are in your DHCP pool.
even with the pool.ntp.org working ok, I would assume the sleep timer should run fine. That's gotta be a firmware bug.
if not then maybe the system isn't updating every 3 hours, I only sync mine once per day.
or maybe the firmware won't play nice w/sleep, unless using the default ntp server.
It is odd you can get to pool.ntp.org, but not the other one. It's still possible the default .jp server isn't resolving for whatever reason.
I only mentioned DNS because that Open DNS and other settings you noted recently- don't work for everyone.
I wouldn't use 3rd party addresses for DNS, unless I know my ISP allows it...
https://support.opendns.com/hc/en-us/articles/227988727-How-can-I-tell-if-my-ISP-Allows-Third-Party-DNS-Providers-
going with the idea that maybe it won't play nice w/o defaults:
what about this, using the numeric for the NTP default?
ntp.jst.mfeed.ad.jp (Default Server) of 210.173.160.87
http://forums.buffalotech.com/index.php?topic=10346.0
Here the third latest "suggestion from Buffalo: Do a firmware update from 1.73 to 1.74: Did absolutely no good.
Here is the second latest: Try clearing the cache to your browser, then once this is done try changing the DNS to the suggested Google DNS address, then attempt to sync to your NTP server. If this does not work try using a different browser. All of the above improved nothing.
Here is the latest: However if this is a case of firmware corruption these is a 100% clean cut way of resolving it, however it does destroy any data on the unit. Please make sure any critical data is backed up before trying the steps that have been attached to this email. A pdf file with instructions was attached. I wold attach it but I don't see how.
i am in process of doing this now.
Anyone have an approximate time for the "Create RAID Array" to complete? The window that is open doesn't seem to update either the % progress or time remaining numbers. I am really impressed with the fine quality of the Buffalo software.
Thanks for any information.
Herb
Sorry for this omission:
Forgot to mention my LS220 has (2) 1TB drives. I'm sure this will affect the time.
Thanks all.
Herb
I have no idea how or why you are seeing 'Create RAID array', unless you've already reloaded the firmware. If I remember right, the LS220D defaults to RAID 1 when the firmware is loaded.
If you are reloading the firmware and starting over from scratch:
Then before doing that, I would suggest taking the drives out, wipe them, and on a windows machine- do a full write surface scan on each one.
It is possible there may be bad sectors on these disks, in areas where the firmware was being stored.
The only way you'll be able to fully tell- is to get a software like hard disk sentinel (it is free from www.hdsentinel.com) and do a full write surface scan.
Do the tests and let us know what the smart info is, this way we can rule out any drive failure problems. Although bad sectors might not be the problem, it doesn't hurt to get them ruled out.
Quote from: Kane88 on April 12, 2020, 02:22:16 AM
I have no idea how or why you are seeing 'Create RAID array', unless you've already reloaded the firmware. If I remember right, the LS220D defaults to RAID 1 when the firmware is loaded.
Sorry my memory is so foggy so quickly. Frankly I didn't have much hope this was going to work.
From what I remember I think the default is RAID 0 as I had to select RAID 1 and wait for between 2 and 3 hours for it to complete.
If you are reloading the firmware and starting over from scratch:
Yes I did per this from Buffalo Tech Support: "With the previous test ruing out a caching issue, with the interface reverting changes after they are saved and this is confirmed not a browser caching issue this has come down to a case of probable firmware corruption. The previous update of firmware could have potentially fixed this issue however it was not guaranteed.
However if this is a case of firmware corruption these is a 100% clean cut way of resolving it, however it does destroy any data on the unit.
Please make sure any critical data is backed up before trying the steps that have been attached to this email."
Then before doing that, I would suggest taking the drives out, wipe them, and on a windows machine- do a full write surface scan on each one.
It is possible there may be bad sectors on these disks, in areas where the firmware was being stored.
The only way you'll be able to fully tell- is to get a software like hard disk sentinel (it is free from www.hdsentinel.com) and do a full write surface scan.
Do the tests and let us know what the smart info is, this way we can rule out any drive failure problems. Although bad sectors might not be the problem, it doesn't hurt to get them ruled out.
This did take a long time (not with hdsentinel) but the drives are okay. I'm not so sure with all of the internal software in modern drives this testing has a lot of value. My $0.02The ntp server problem seems to be fixed.
SMB appears to play nicer on my network.
It will take a few weeks before I'm confident of the Sleep Timer.Herb
Modern drives might mark them as weak sectors, which still can lead to problems. It is always best to run a surface scan when in doubt. Bad sectors need to be marked bad, so that disks are properly useable, especially in these devices that have little error reporting and troubleshooting tools.
We have no way of telling how old a person's drives are, or if they have been mishandled.
Viewing SMART data doesn't mean the buffalo device itself is actually marking bad sectors and remapping them, to where the drive(s) operate correctly.
And sometimes underlying problems don't appear, until such full tests are ran.
When in doubt, I do a test.
I'm glad your disks are ok.
What did you do to fix the NTP problem?
Quote
What did you do to fix the NTP problem?
As I understand this process it reloads firmware and replaces operating system files on the disks.
I downloaded the LSUpdater files, modified the lsupdater.ini file and ran LSUpdater as instructed in a pdf file Buffalo Tech Support sent me.
I would have attached the pdf but I can't seem to find how to do that.
HOW TO:
This will update the firmware, and files on the disk drive(s).
It will DESTROY ALL YOUR DATA on the all drives. BACKUP, backup your data.
STEP 1:
Modify LSUpdater.ini
[Flags]
VersionCheck = 0
NoFormatting = 0 (This is different compared to https://herzig-net.de/?page=unbrick_ls-wxl )
[SpecialFlags]
Debug = 1
STEP 2:
Run LSupdater.exe
STEP3:
Click: on top left corner (there are some gold rings there)
Select: Debug(D)...
STEP4:
Windows opens with title: DeBug Mode (there are 8 check boxes, check ALL eight)
_Update BOOT _Do not check version
_Update KERNEL _Rebuild partition table
_Update initrd _Delete user-config
_Update rootfs _Force update
STEP 5:
Click: OK
Be patient and follow the prompts.
The unit will have to be totally configured as if it is new. All user settings and data has been wiped out.
END of HOW TO:
This procedure will update the firmware and not destroy the data (hopefully I wouldn't take the chance), back up first.
https://www.buffalotech.com/knowledge-base/updating-the-firmware-on-a-terastation-or-linkstation-from-a-windows-pc
Herb
Hello,
Regrettably today 20 April 2020 I see that my LS220D will NOT sync with the NTP server.
My view of this Buffalo device sinks lower and lower with each passing day.
Herb
That might explain some of your email issues too. If your system clock is messed up SSL connections will be rejected.
If all else fails, you can install Debian Linux on it rather than the stock firmware:
https://github.com/1000001101000/Debian_on_Buffalo
Finally this is put to rest.
Embarrassing error on my part.
I have a RG (Residential Gateway) for my ADSL service from AT&T. That feeds an Archer C7 router that provides wireless and wired ports. It allows binding of MAC addresses with IP addresses. As I map several drives in Windows is is very handy having them at fixed addresses.
My error was I mistook an 'B' for a '8' in the LS220's MAC. It worked if I select DHCP but not when assigned a static IP to the NAS.
Fixed this and everything seems to be working including the email notifications. gmail would not work. Got message from Google that a non-secure device had tried to access gmail. Changed to an AT&T email account and it worked.
Herb