Yep. I've had that happen across vendors and across drive types.
*ASB *(My XeeSM Profile) <http://XeeSM.com/AndrewBaker> *Exploiting Technology for Business Advantage...* * * On Tue, Sep 28, 2010 at 10:25 AM, Jonathan Link <jonathan.l...@gmail.com>wrote: > Sounds like a bad batch of drives, which could happen with any drive > type/vendor. > > On Tue, Sep 28, 2010 at 10:21 AM, Michael B. Smith > <mich...@smithcons.com>wrote: > >> I’m surely not very happy with SATA right now. I got in two R300’s with >> loads-o-disk as DPM2010 servers for a client last week and I’ve already had >> 4 SATA drives die. WTF?!?! Makes me want to return the whole thing… >> >> >> >> Regards, >> >> >> >> Michael B. Smith >> >> Consultant and Exchange MVP >> >> http://TheEssentialExchange.com <http://theessentialexchange.com/> >> >> >> >> *From:* Erik Goldoff [mailto:egold...@gmail.com] >> *Sent:* Tuesday, September 28, 2010 10:19 AM >> >> *To:* NT System Admin Issues >> *Subject:* Re: Small server >> >> >> >> curious, why do you shun SATA ? >> >> On Tue, Sep 28, 2010 at 10:14 AM, James Kerr <cluster...@gmail.com> >> wrote: >> >> Kind of important software. I would make sure the server was hardware >> RAID1 with 2 hot swap SAS drives NOT SATA at a minimum just for the >> redundancy. No software RAID. Whats wrong with SCSI? >> >> James >> >> >> ----- Original Message ----- From: "John Aldrich" < >> jaldr...@blueridgecarpet.com> >> To: "NT System Admin Issues" <ntsysadmin@lyris.sunbelt-software.com> >> Sent: Tuesday, September 28, 2010 10:08 AM >> Subject: RE: Small server >> >> >> >> >> Sorry. I guess I should have specified this is for Kronos Time Keeper >> Central. >> >> Server hardware requirements are very basic. It has to be capable of >> running >> Windows 2000. It's not a very resource-intensive software. It's got a >> small >> DB and has to be capable of allowing multiple people to access it over the >> network (via "client" software loaded on their machine) The machine that's >> currently running the time and attendance software is a P4 2.8Ghz with 2 >> Gig >> of RAM running Windows 2000. My main problem is that it's running off a >> single HDD, and a SCSI drive at that. >> Cut/paste from the system requirements document: >> 750 Mhz+ 1 Gigabyte NT4 , 2000 Server 2003 Server 1 Gigabyte >> Free disk space. >> >> As you can see it's very basic requirements. TKC has not been updated in a >> LONG time and probably won't be updated ever again. I spoke with a support >> engineer, and he said that he's seen it running on Windows XP, but that's >> not supported, as XP is not a "server" O/S, which is required for multiple >> clients accessing the machine at one time. >> >> Thanks... Hope this answers your questions WRT system requirements. >> >> >> From: Steven M. Caesare [mailto:scaes...@caesare.com] >> Sent: Tuesday, September 28, 2010 9:59 AM >> >> >> To: NT System Admin Issues >> >> Subject: RE: Small server >> >> >> Once again you give us absolutely no app requirements. >> >> Therefore the answer is: maybe. >> >> -sc >> >> From: John Aldrich [mailto:jaldr...@blueridgecarpet.com] >> >> Sent: Tuesday, September 28, 2010 9:55 AM >> To: NT System Admin Issues >> Subject: Small server >> >> I am looking at getting a small server running Windows Server 2003, so I >> can >> have my time and attendance running on a supported O/S. Looking at Dell's >> Premier site, the least expensive option only offers a Software RAID5, >> unless I'm mis-reading the options. Would you guys rather have a Hardware >> RAID0 / RAID1 or a software RAID5? >> >> Any other options I should be looking at for a small server? We're >> primarily >> a Dell shop here, but I can look at others, including "white box" servers, >> so long as I can get some sort of warranty / hardware support on it. >> >> ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
