[LS-Pro XHL 1TB, firmware 1.10-0.73]
- I want my LS to be online every day for a certain time (i.e. starting at 8am, hibernating at 11pm). With the current SleepTimer this doesn't work.
- The ftp-daemon (proftpd) uses the wrong time. In /etc/proftpd/proftpd.conf the entry "TimesGMT off" is wrong and has to be changed into "TimesGMT on".
- NTP is used via cron but should also be used at startup.
- The WebAccess-Feature is pretty buggy. Multiple upload doesn't work for example. I also had problems with corrupted downloads. Maybe its due to the use of https and works better with http but nevertheless this shouldn't happen. The WebAccess could be something very important if it would get some more work.
- HDD-Spindown doesn't work.
dil wrote:[LS-Pro XHL 1TB, firmware 1.10-0.73]
- I want my LS to be online every day for a certain time (i.e. starting at 8am, hibernating at 11pm). With the current SleepTimer this doesn't work.
Seems I found the solution for that problem here on the forum in a posting from Colin137.
I always thought that the LS is always off if the power-switch is set to "Off" and always on if it is set to "On". And so I used the "Auto"-setting when I tried the SleepTimer. But that's only useful for working with the NAS Navigator-Software (or WOL). You have to set the power-switch to "On" to use the SleepTimer. Standby and resume work like a charme then.
But there are three things that should be changed though:
- In the LS-manual it should be added on the SleepTimer-Page (p. 31) that the power-switch has to be set to "On".
- The manual describes that you could wake up the LS in standby-mode by holding "down the power button on the front panel for 3 seconds". Unfortunetly the LS XHL doesn't have a power button on the front panel. It has a function button but that doesn't wake up the LS XHL. And WOL - which would be the smartest solution - is ignored.
- The timestamp for the shutdown could be set up to 27:45h (the resume-timestamp is correct ending at 23:45h).
Great help here on the forum. Thanks a lot! Gives the product a much better value.
> And WOL - which would be the smartest solution - is ignored.
Interesting then that every few minutes (no fixed times) three WOL magic packets (containing the LS-XHL's MAC address) are sent to the LS-XHL IP address by 'something' not yet identified, but possibly NASSVC...
Maybe that's to keep the drive from spinning down (even though I have set the option to spin down in the web interface)?
WOL packets sent from NasNav2 to 'keep it awake' incase you have it in auto-shutdown mode. That's how it stays awake/wakes up in auto mode.
---
It's not likely to be NASNavi(2) because I have set this not to start at a reboot, and it's not in my Task Manager Processes list.
However NASSVC.EXE, described at the "NAS Power Management Service" is running, started automatically via the 'simple' command:
C:\Program Files\BUFFALO\NASNAVI\nassvc.exe -Service_Execute -dcyc=60 -dto=3 -dluc=0 -dmin=1 -dmax=60 -dflc=0 -apc=0 -log=0 -pm=1 -pall=1 -phttp=0 -pbc=0 -ppro=0 -pcyc=0 -pmin=1 -pmax=60 -pflc=0
I've no idea about the function of the parameters, but as far as I can judge NASSVC is the only piece of Buffalo software that needs to be running to enable the LS-XHL to act as a target backup device, being sent data via a non-Buffalo program.
@johngray,
While it's a separate executable, it's part of the NasNavigator package.
Uninstalling NasNav2 will indeed remove Nassvc.exe.
And I don't understand your coorelation to Nassvc being required to use the XHL as a target backup device....
We ran EMC Networker, EMC Retrospect, and played w/ the Memeo backup/sync tools, all without having that service enabled. All that service does is keep the xhl awake (or wakes it up) if you have it in 'auto' mode.
Change it to manual mode if you don't want the service/app package installed...
@johngray,
Ahh, gotcha. Think we likely mis-read eachothers' replies.
Your explanation makes sense to me now, sorry for the confusion.
---
I have a LAN that does not connect to the internet, therefore NTP is disabled and clock issues become a problem. Whenever I am out of the office for the day, I always disconnect my drive and place it in a safe. When I reconnect the drive, I have to manually reset the drive's date and time.
It would be a great feature if the firmware program would automatically seek the system time and set the drive clock accordingly when the drives were reconnected and powered up.
I'd add the following:
JohnGray wrote:
OK, I see what you mean! My concern is that the LS-XHL should be active just before a scheduled backup runs. This could be done by running the NASSVC service (to keep it active all the time?) or, perhaps, by sending it a WOL magic packet to wake it up shortly before the backup needs to run. More investigation needed...
The LS-XHL doesn't need to be active to back itself up. Is that what you were saying? It wakes itself up to do the backup. Now if you are using it as the target for a backup of another Linkstation, yes, you have to turn it on or have a scheduled wake up a few minutes before the backup.
parsobarus wrote:
The LS-XHL doesn't need to be active to back itself up. Is that what you were saying? It wakes itself up to do the backup. Now if you are using it as the target for a backup of another Linkstation, yes, you have to turn it on or have a scheduled wake up a few minutes before the backup.
No, I am not using any backup ON the LS-XHL. I will be writing TO it from ShadowProtect and from ROBOCOPY, just as if it were a large external disk. I need to test whether the LS-XHL can be woken up by a WOL command...
for new ideas, please now use the Idea Exchange Board.