Thecus Support Thread ! Thecus Users Come In..
- Thread starter jupiter12
- Start date
Was not able to locate the 325A model you were referring to. But in general, the VA specification does not tell you how long it can run but tells you what's the max power you can draw from it , how much equipment can be powered from it. Like a PSU watt rating.
(On a side note please take note that VA and Watts are slightly different measurements in AC power , Watts is real power VA is apparent power. This is due to capacitive and inductive loads which cause phase shift between voltage and current. BUT in home use just look at Watt rating upper limit should be fine.)
To get an idea of how long it can run you'll need to take a look at the Runtime graph. It tells you for the amount of power your equipment uses how long it can go.
325A should be sufficient for the NAS alone, assuming it draws around 50watts only but need to look at runtime graph to tell long it can go. I'm guessing should be quite long also, 30 minutes and above since it should do a desktop (~200watts) for at least 5 minutes
takeshi_umuro
Arch-Supremacy Member
- Joined
- Jan 14, 2001
- Messages
- 13,085
- Reaction score
- 1
dear all,
you can go to the thecus n0503 config page under UPS. From there enable the UPS and you will be able to choose the UPS list. The supported list of UPS is under that list. Cheers
you can go to the thecus n0503 config page under UPS. From there enable the UPS and you will be able to choose the UPS list. The supported list of UPS is under that list. Cheers
can all the model be use on it? It is showing only some model that has been tested for Compatibility? Like a few only...
How about the rest?
how does the UPS actually works? Does it mean it supply power via the USB port of the NAS from the UPS thing?
Last edited:
takeshi_umuro
Arch-Supremacy Member
- Joined
- Jan 14, 2001
- Messages
- 13,085
- Reaction score
- 1
Hi bro,
Not really. In fact from the USB models of UPSes, the usb cable from UPS will be plugged to the usb port of the NAS. This is purely for comms so that if the UPS detected a loss in power it will comms to the NAS and the NAS will then do the necessary actions for example shutdown the NAS gracefully on certain conditions as per NAS configuration.
The NAS would still have to be connected to power outlets from the UPS to be protected from surge and loss of power from the mains.
So far supported list is quite little but however on those not supported but listed, I've tried on my MGE pulsar evolution 1500VA. So far so good touch wood. I've tried the settings and it seems to go well. You can configure email alerts if you want to as well
PS: Andrew, would there be any chance that thecus NAS will be VMWare certified? It seems that Netgear ReadyNASes are certified recently. I'm currently running VMWare vSphere and MS clustering 2003 and all seems well on VMWare vSphere. MS Clustering however seems to have some glitches on thin provision luns it seems but I've not enough time to test out that portion so still pending on thecus support engineers to get back on this.
Not really. In fact from the USB models of UPSes, the usb cable from UPS will be plugged to the usb port of the NAS. This is purely for comms so that if the UPS detected a loss in power it will comms to the NAS and the NAS will then do the necessary actions for example shutdown the NAS gracefully on certain conditions as per NAS configuration.
The NAS would still have to be connected to power outlets from the UPS to be protected from surge and loss of power from the mains.
So far supported list is quite little but however on those not supported but listed, I've tried on my MGE pulsar evolution 1500VA. So far so good touch wood. I've tried the settings and it seems to go well. You can configure email alerts if you want to as well
PS: Andrew, would there be any chance that thecus NAS will be VMWare certified? It seems that Netgear ReadyNASes are certified recently. I'm currently running VMWare vSphere and MS clustering 2003 and all seems well on VMWare vSphere. MS Clustering however seems to have some glitches on thin provision luns it seems but I've not enough time to test out that portion so still pending on thecus support engineers to get back on this.
There is a UPS module, APCUPSD modified for use on N5200.
http://www.onbeat.dk/thecus/index.php/N5200_Module:_APCUPSD
What is like about this mod is it is network capable. If you have a computer hooked up to your UPS it can function as a UPS server and relay shut down message to the NAS when power outage is detected.
OF COURSE though you NAS must be on its own UPS (dumb, no data connection) so that when power goes down it will stay alive for as long as it can query the server for shut down message.
Good idea if you ask me but not sure about N0503 support.
http://www.onbeat.dk/thecus/index.php/N5200_Module:_APCUPSD
What is like about this mod is it is network capable. If you have a computer hooked up to your UPS it can function as a UPS server and relay shut down message to the NAS when power outage is detected.
OF COURSE though you NAS must be on its own UPS (dumb, no data connection) so that when power goes down it will stay alive for as long as it can query the server for shut down message.
Good idea if you ask me but not sure about N0503 support.
Thecus promo @ Bizgram
http://www.hardwarezone.com.sg/promos/view/node:25526
Also available @ Fuwell/Laser
Buy any 2200 / 3200pro / n0503 / 4100pro. Free Xmini 2 capsule speakers
http://www.hardwarezone.com.sg/promos/view/node:25526
Also available @ Fuwell/Laser
Buy any 2200 / 3200pro / n0503 / 4100pro. Free Xmini 2 capsule speakers
Sigh.. the free gift like not very good leh
I just want IT show price for n0503 w/o drive.
Wonder if someone could help me with this? Thanks a lot!
SkimMilk
Master Member
- Joined
- Jan 1, 2000
- Messages
- 4,594
- Reaction score
- 2
use the SSHD and Sysusers modules here:
5200 Modules list
Tested working on my n0503 with 3.02.01 firmware
5200 Modules list
Tested working on my n0503 with 3.02.01 firmware
Thanks for the info!
Hey Skimmilk what stripe size do yo use?
just a noob qn....hehe
Scenario: Use NAS for torrenting of files.... Then in such a situation, the download files will be download and seeded to/from a particular folder on the raid drive..
So as you know, there is a danger torrenting as in terms of spyware or viruses from the downloaded files..So in such a case, if i just download such a file and I don't open it yet and left it seeding, will it affect the NAS system?
Anyone using NAS to torrent kenna any spyware and viruses before on the NAS, thus affecting the whole raid drive or the com that accessing it?
will mp3 files contain any possible risk of viruses or spyware? ( I know this is a very noob qn...hope you guys don't mind)
Scenario: Use NAS for torrenting of files.... Then in such a situation, the download files will be download and seeded to/from a particular folder on the raid drive..
So as you know, there is a danger torrenting as in terms of spyware or viruses from the downloaded files..So in such a case, if i just download such a file and I don't open it yet and left it seeding, will it affect the NAS system?
Anyone using NAS to torrent kenna any spyware and viruses before on the NAS, thus affecting the whole raid drive or the com that accessing it?
will mp3 files contain any possible risk of viruses or spyware? ( I know this is a very noob qn...hope you guys don't mind)
Last edited:
SkimMilk
Master Member
- Joined
- Jan 1, 2000
- Messages
- 4,594
- Reaction score
- 2
Yep I believe that is the default value set by the firmware.
I've read however in many forums suggesting that users should set as large as possible a stripe size, particularly but not strictly only to users who store large files on the array.
here's what i've found out so far:
I use RAID 5 for reference but same idea applies to RAID 0
Data storage with respect to Stripe Size
Ok, so how does the stripe size play an important role in your RAID's performance and why is 64kB or even smaller stripes recommended by some people?
Stripe Sizing is only done at the RAID controller (or RAID processing done by software), it cannot be seen by Windows or the system trying to access it.
When data is sent to be written to the RAID, stripe size determines how the data will be split, or STRIPED, to be distributed among the the disks. If stripe size is 2kB and the file incoming is 4kB, it will be split and stored on 2 different disks.
If stripe size is 4kB or large then it will be stored on only 1 disk. When reading and writing, using multiple disks is always faster so 2kB stripe size is fast as long as your files are larger than 2kB. This is the whole idea of striped data, more disks = better performance
So 64kB stripe size would make sense if you use your RAID array for system files that are usually in the order of hundreds of kB to tens of MB.
On the other hand why not use the smallest stripe size so that data is always split up to multiple disks? here is the argument for why stripe size should be as big as possible.
Imagine a GB file being split into tiny 2kB portions, although the process of splitting and joining does not take a significant amount of time, having to do it at this scale time complexity would become significant. And you slowly lose the benefit of striped data
That is why stripe size should be as large as possible. For files smaller than the stripe (which would be few on your NAS), you still get the performance of a single disk (no boost that's all) while for large GB files your performance is not crippled by having to split it up into so many tiny portions. While a small stripe size suffers as the file size gets bigger and bigger.
Disk space with respect to Stripe Size
Now you may be thinking "won't i lose space by storing a small file into a big stripe ?"
The remaining portion of the stripe not used by your small file can still be used and parity can be recalculated on the parity stripe, no problem. It is still continuous with no void spaces.
A simple proof of this would be having your OS run on a striped RAID array. Your OS knows nothing about the RAID array and for that matter its STRIPE SIZE, yet Windows always gives you the same amount of storage regardless of what stripe size you use.
I hope this has been educational and makes sense. Hopefully those who are just about to build their RAID array would be inclined to choose the bigger stripe size and reap the benefits.
Do note that most of what I have mentioned describe the story in a general sense and some raid controllers have specifically optimized Stripe Sizes so check with your manufacturer if you can.
Thank you
I've read however in many forums suggesting that users should set as large as possible a stripe size, particularly but not strictly only to users who store large files on the array.
here's what i've found out so far:
I use RAID 5 for reference but same idea applies to RAID 0
Data storage with respect to Stripe Size
Ok, so how does the stripe size play an important role in your RAID's performance and why is 64kB or even smaller stripes recommended by some people?
Stripe Sizing is only done at the RAID controller (or RAID processing done by software), it cannot be seen by Windows or the system trying to access it.
When data is sent to be written to the RAID, stripe size determines how the data will be split, or STRIPED, to be distributed among the the disks. If stripe size is 2kB and the file incoming is 4kB, it will be split and stored on 2 different disks.
If stripe size is 4kB or large then it will be stored on only 1 disk. When reading and writing, using multiple disks is always faster so 2kB stripe size is fast as long as your files are larger than 2kB. This is the whole idea of striped data, more disks = better performance
So 64kB stripe size would make sense if you use your RAID array for system files that are usually in the order of hundreds of kB to tens of MB.
On the other hand why not use the smallest stripe size so that data is always split up to multiple disks? here is the argument for why stripe size should be as big as possible.
Imagine a GB file being split into tiny 2kB portions, although the process of splitting and joining does not take a significant amount of time, having to do it at this scale time complexity would become significant. And you slowly lose the benefit of striped data
That is why stripe size should be as large as possible. For files smaller than the stripe (which would be few on your NAS), you still get the performance of a single disk (no boost that's all) while for large GB files your performance is not crippled by having to split it up into so many tiny portions. While a small stripe size suffers as the file size gets bigger and bigger.
Disk space with respect to Stripe Size
Now you may be thinking "won't i lose space by storing a small file into a big stripe ?"
The remaining portion of the stripe not used by your small file can still be used and parity can be recalculated on the parity stripe, no problem. It is still continuous with no void spaces.
A simple proof of this would be having your OS run on a striped RAID array. Your OS knows nothing about the RAID array and for that matter its STRIPE SIZE, yet Windows always gives you the same amount of storage regardless of what stripe size you use.
I hope this has been educational and makes sense. Hopefully those who are just about to build their RAID array would be inclined to choose the bigger stripe size and reap the benefits.
Do note that most of what I have mentioned describe the story in a general sense and some raid controllers have specifically optimized Stripe Sizes so check with your manufacturer if you can.
Thank you
Last edited:
Same here. I would like the n0503 without HDD. The free gift also not important.
Any chance of getting the NAS w/o HDD for IT show price?
SkimMilk
Master Member
- Joined
- Jan 1, 2000
- Messages
- 4,594
- Reaction score
- 2
Yo weap0nx, thanks for the info! was too lazy to read up on stripe size and also afraid of losing disk space using large stripes. now with this info, I may rebuild my raid. but that will only be after I upgrade my router (100 to 1Gb).
Important Forum Advisory Note
This forum is moderated by volunteer moderators who will react only to members' feedback on posts. Moderators are not employees or representatives of HWZ Forums. Forum members and moderators are responsible for their own posts.
Please refer to our Community Guidelines and Standards and Terms and Conditions for more information.
