Hard disk for Music Server

One other thing, even though software raid is not the best... It’s still pretty good. The problem, the software usually complements the drive spec only, not the interface between a SCSI driver board (with its own onboard buffer, ROM, and HI speed RAM). So if you lose a drive, you need to replace with the same or use a software patch.. Even more proprietary..
Good place to get malicious, if you’re handy with a GOOD keyboard break routine, and a few other tricks, to speed the console up...Wipe someone elses drive pretty quick. Command line access is pretty hard on a good SCSI board..You ain’t gonna do it over a phone/LAN/WAN/WiFi, or any way. It would be real tough...You gotta be there to access the bios.

Now think, three board per server each board can run 14 devices and one ID for the boards, you have 5 servers. Each drive is 10T, spinning at 10,000 rpm....I wonder how many miles that is in a year? 2.5" or 3.5" 2-6 platters, Sorry I ran out of fingers and toes... It's a lot....Carry the 1, geez that one hell of a cipher!!! Ok brainiacs, step up, way out of my league.. I'm simple.

I’ll ponder that while I feed the chickens...

Regards

Again raid 1+0, look at how it works. Very fast, redundant, and hot swappable...Stripped, and mirrored. Yes I’ve built a hot rod or two..

In other words you could pull a drive, replace it. Take the drive you pulled and start a migration, to build another complete system. Space shuttle crap, and a fast way to RE-build a downed system......I would never need it...

The biggest difference between RAID 5 and RAID 10 is how it rebuilds the disks. RAID 10 only reads the surviving mirror and stores the copy to the new drive you replaced. ... However, if a drive fails with RAID 5, it needs to read everything on all the remaining drives to rebuild the new, replaced disk.

I’m not to fond of Software RAID either, I like SCSI, and onboard, disk low level management... The OS or NOS, well you can get as teckie as you like...LOL I like easy... Not lines of code to just create a BOOT strap, to see a disk, to read a disk, then boot from a 60 POUND, 60 meg hard drive. An IBM 36 was that way, that I maintained for quite a few years...

When were talking Backup, that should be a given, guys.. Really, who doesn’t have a tape backup, or at least a CD backup. A HD or SSD will ALWAYS fail, it’s just a question of when...

Another thing, a PS failure, very seldom leads to a drive failure. I’ve never seen one, lower quality PS of old could lead to drive failures, very rare though. Like MFM, RLL, and ESDI drives, before SCSI, and WAY before, any IDE stuff. Again it is a single failure, BUT no data loss. One of a few reasons for RAID to begin with.
Speed, Reliable, not expensive, redundant, and not necessarily a proprietary part needs to replace a failed one...
Replace a Seagate with a Maxtor, give it a physical ID, terminate, and away you go.....
Regards..

Raid 0 offers no backup, it only spans more than one drive into volume (s) Very bad if there is a drive failure. Raid 5 is good but difficult to repair if there is a failure. 1+0 is much better, gives you failure, hot swaps without downtime or data loss, but during the failure time you will suffer data SLOW downs big time, on a network sharing the files..

More smaller, faster, drives with STRIPPING, will blow your mind with speed. SSD RAID 1+0, 4-10, 2 gig SSD drives, Hot rod buddy...
FTH comes to mind, Faster than hell.

I ran SCSI II raid on my old Novel networks, for some manufacturing software...The 60 meg BOOT drive weighing close to 60 lbs each. Priam, drives with 10" platters? I think......OLD SCHOOL...LOL They were Raid 5 X 5s The rack was close to 400 lbs, the system 36, IBM ran on 220-240.  What a watt sucking setup....Sure was cool, though...HOT, was more like it, come to think of it.. Made barrels of all things...Paper, metal, HS, polys, overpacks....

Regards