NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Beta Tester Wanted (new Windows app for ReadyNAS)
Hi, all I recently created a small Windows app for ReadyNAS series of NAS, which will let user to start, monitor and shutdown a ReadyNAS system from task tray. It emulates RAIDar Protocol ...
Hi guys. I am very sorry for not replying comments so long.
I have not noticed your comments until lately. The mail notification system of forum didn't work again. Now I understand I shouldn't count on it.
Masato, I don't know much about RAIDiator 5.xx. Shutdown function of NAS Herder emulates the shutdown from FrontView. So correct command string is necessary to perform it. If anyone tell me the command string, it might become possible.
zamboni, as you said, desktop gadget is, unfortunately, a dying technology. So no plan to make a gadget version. Regarding email notification, it would be possible. On the other hand, a ReadyNAS system has built-in email notification system. I think if a disk dies, it will be notifyed by the system itself. So it depends on necessity.
UteDohrs, a system of RAIDiator 6.xx seems to pretend to be x86 architecture even if it is actually arm based. It is interesting. Are there any difference of functions between x86 based and arm based especially on remote power on/off?
And fastfwd, yeah, you are comletely right. Current version of NAS Herder uses "expected" temperature range in responce of RAIDar Protocol to determine which item would be regarded as CPU. And as you described, it is not always true.
So, thanks to your information, I made a test version from verson 0.9.7. The algorithm to determine item of CPU is as follows:
Step 1: Use ReadyNAS model tabled based on enclosure.db. The model table will be saved in the same folder in csv format. You can edit the table from Settings Dialog -> Other tab -> "Change index type". Or you can directly edit the csv file. On closing Settings Dialog or restarting NAS Herder, new table will be reflected.
Step 2: If there is no information which matches the model name of current system, use the "expectred" temperature range as a fallback method.
I think this algorithm will cover the problem in principle. However, there are still a few problems:
Problem 1: Is there any clue in RAIDar Protocol to tell the revision of the systems like ReadyNAS 2100? Otherwise, it will be left to each user to manually edit the model table.
Problem 2: This is more essential. The enclosure.db inside a system of RAIDiator 4.xx has information only on the system of that version. It is quite natual but it means the same information on the system of 5.xx and 6.xx is necessary as well. Has anyone successfully retrieved the information already? I myself am going to get the system of 6.xx and so I will try it later though.
I have not noticed your comments until lately. The mail notification system of forum didn't work again. Now I understand I shouldn't count on it.
Masato, I don't know much about RAIDiator 5.xx. Shutdown function of NAS Herder emulates the shutdown from FrontView. So correct command string is necessary to perform it. If anyone tell me the command string, it might become possible.
zamboni, as you said, desktop gadget is, unfortunately, a dying technology. So no plan to make a gadget version. Regarding email notification, it would be possible. On the other hand, a ReadyNAS system has built-in email notification system. I think if a disk dies, it will be notifyed by the system itself. So it depends on necessity.
UteDohrs, a system of RAIDiator 6.xx seems to pretend to be x86 architecture even if it is actually arm based. It is interesting. Are there any difference of functions between x86 based and arm based especially on remote power on/off?
And fastfwd, yeah, you are comletely right. Current version of NAS Herder uses "expected" temperature range in responce of RAIDar Protocol to determine which item would be regarded as CPU. And as you described, it is not always true.
So, thanks to your information, I made a test version from verson 0.9.7. The algorithm to determine item of CPU is as follows:
Step 1: Use ReadyNAS model tabled based on enclosure.db. The model table will be saved in the same folder in csv format. You can edit the table from Settings Dialog -> Other tab -> "Change index type". Or you can directly edit the csv file. On closing Settings Dialog or restarting NAS Herder, new table will be reflected.
Step 2: If there is no information which matches the model name of current system, use the "expectred" temperature range as a fallback method.
I think this algorithm will cover the problem in principle. However, there are still a few problems:
Problem 1: Is there any clue in RAIDar Protocol to tell the revision of the systems like ReadyNAS 2100? Otherwise, it will be left to each user to manually edit the model table.
Problem 2: This is more essential. The enclosure.db inside a system of RAIDiator 4.xx has information only on the system of that version. It is quite natual but it means the same information on the system of 5.xx and 6.xx is necessary as well. Has anyone successfully retrieved the information already? I myself am going to get the system of 6.xx and so I will try it later though.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
