Wow - there's a lot here. Let me cover a few of your topics.
"Sleeping" and external drives. This can be a problem on either Windows
or Mac if your sleep settings are not configured correctly -
specifically, "do not go to sleep when an external drive is attached",
or alternatively "do not go to sleep ever." A friend of mine kept
corrupting external drives on his Mac because of his machine going to
sleep. I helped him fix his sleep settings and he's been
corruption-free for quite a while now. I agree with a previous poster -
modern OS's should be able to handle this better even when machines
go to sleep. The sad fact is they don't.
Connecting through NAS: if you are still having the corruption problem
because of sleeping and the above answer doesn't work, just configure
the NAS partiion(s) to mount "read/only" by default. Your Windows
machine can't corrupt your NAS if it can't write to it. My music server
automatically exports two separate shares of my music directories: one
read/write, the other read/only. There's no reason to mount read/write
unless you need to add music or edit metadata. Listening should be
read/only. Dismount/disconnect the read/write
share whenever you're not using it. FWIW I've never had an export share
corrupted by a client whether it be read/write or read/only,
whether the client machine went to sleep, crashed, or exhibited any
other such antisocial behavior.
RAID / Big Ugly/Loud boxes: While RAID is an excellent solution to
certain classes of problems, I don't think it's really ideal for home
music server applications. RAID is great if any downtime is
unacceptable, and/or you have such a large array of discs that
maintaining a 1/1 backup ratio becomes prohibitively expensive. The
downside is that RAID has too many common points of failure. Power
surges, viruses, user error, software upgrade snafus, faulty
controllers, and even near-simultaneous failure rates of hard drives
sourced from the same batch often take out the RAID drive in addition to
the main data drive(s). In terms of probability theory, the whole
reason you backup is to reduce the chance of data loss. By having
additional copies, you utilize the power joint probabilities: one or
more improbable events have to occur simultaneously for you to suffer a
loss. However, joint probabilities become less powerful when
independence is removed. RAID just adds too much dependence to be a
reliable backup scheme for most home applications. These days most of
the "I thought I was backed up my but I lost my data anyway" stories I
hear involve RAID. One such incident happened recently to a member of
this newsgroup, but he was fortunate enough to have additional redundancy.
So to maximize the power of joint probabilities - backup to external
drives that are only connected to the target machine when backups are
refreshed. Otherwise they are kept unconnected and unplugged. Bonus
points if they are kept at another address. Double bonus points if that
address is in another geographic region. Of course at that point you
have far less of a chance of surviving a major cataclysmic event than
your collection does, but until we can backup or clone ourselves that's
what we have to settle for.
The RAID issue ties directly into the "Big ugly box" issue. Once you
don't need onboard RAID, you can settle for a much smaller/quieter/less
ugly box. When building servers for friends that want
small/quiet/unobtrusive, I've been using this enclosure quite a bit lately:
http://amzn.to/1d6nP0N
It can comfortably hold two 3.5" drives - enough for 8TB of internal
space which would even handle TD's collection (warning - it's specs lead
you to believe it may be able to hold three full-size drives, or even
two 3.5" and an optical drive, but unfortunately this isn't true - the
optical drive would have to be external).
Operating System: I'm a big believer in using a full-blown Linux music
server installation rather than a barebones NAS installation. It's far
more robust and far more feature-rich. If you have only a NAS, you
still need an "always up" machine to access/serve the files on the NAS.
While you can try to run the music server program on the NAS, I really
wouldn't recommend it if your collection is as big as the average RMCR
participant's. I run the VoretxBox suite which is basically Fedora
Linux with Squeezebox Server, a few other packages, and some customized
GUI's and extensions. I'm a huge believer in Linux over
either Windows or Mac OS for music servers. When Linux boxes are up and
running, they stay running longer and more reliably with less user
knowledge or input than any other machines I know. I like to joke that
Linux machines should be rebooted once every 6 months to a year whether
they need to or not. WHEN they require upgrade or maintenance, some
expert knowledge may be required. It's good to have a resource
available for those infrequent occurrences. I provide this role for my
non-technical friends who have servers. They leave me alone for months
at a time (at least when it comes to their servers :)
So now you have sleep-robust music shares, reliable backups, a small
quiet and robust server - anything else?
DF