On Thu, 25 Aug 2005, Mike Williams wrote:
> Maxtors RMA process is exceptionally quick and simple though, as long as the
> drive is still detectable by the BIOS.
Sure - we have a *lot* of experience with their RMA process!
> Their warranty periods are 3 year and
> above now too.
> All you pay is
On Thu, 25 Aug 2005, José Pablo Ezequiel Fernández wrote:
> I had very bad experience with bigfoots, about 50% (of 10 or more) died on the
> first 2.5 years.
That's not too bad compared to Maxtors.
I have Seagate (SCSI) disks in servers that have been running for almost 5
years now...
--
--
On Thursday 25 August 2005 20:38, Willie Wong wrote:
> On Thu, Aug 25, 2005 at 08:07:52PM +0200, Volker Armin Hemmann wrote:
> > well, my new seagate died in the first week.. .the second one run for
> > years without problems...
> >
> > Seagate = Sie geht oder sie geht nicht. (it works or not).
>
On Thursday 25 August 2005 16:46, A. Khattri wrote:
> I had a Maxtor drive die just after the one-year warranty expired. We had
> one server with Maxtors that died twice in one year.
>
> Because of this, we now have a "Seagate-only" policy for hard-drives -
> they may cost a bit more but they're re
A. Khattri wrote:
I had a Maxtor drive die just after the one-year warranty expired. We had
one server with Maxtors that died twice in one year.
Because of this, we now have a "Seagate-only" policy for hard-drives -
they may cost a bit more but they're reliable and many come with a three
year wa
On Thu, Aug 25, 2005 at 08:07:52PM +0200, Volker Armin Hemmann wrote:
> well, my new seagate died in the first week.. .the second one run for years
> without problems...
>
> Seagate = Sie geht oder sie geht nicht. (it works or not).
>
If it is DOA or dies very soon, you can always demand they
On Thursday 25 August 2005 15:07, Volker Armin Hemmann wrote:
> On Thursday 25 August 2005 17:46, A. Khattri wrote:
> > I had a Maxtor drive die just after the one-year warranty expired. We had
> > one server with Maxtors that died twice in one year.
> >
> > Because of this, we now have a "Seagate-
On Thursday 25 August 2005 17:46, A. Khattri wrote:
> I had a Maxtor drive die just after the one-year warranty expired. We had
> one server with Maxtors that died twice in one year.
>
> Because of this, we now have a "Seagate-only" policy for hard-drives -
> they may cost a bit more but they're r
On Thu, 25 Aug 2005, Nick Rout wrote:
> From a log investigation you might be right.
>
> Bugger, it is a newish disk too.
>
> Better dig out the receipt and get ready to ask for a replacement.
I had a Maxtor drive die just after the one-year warranty expired. We had
one server with Maxtors that d
On Thursday 25 August 2005 09:13, Matt Nordhoff wrote:
> On 08/24/05 15:59, Nick Rout wrote:
> > For somewhere between 3 days and a week I have been rising to find
> > that /home has become readonly overnight.
>
> Filesystem errors, maybe? That's why I was always getting read-only
> partitions... R
On Wed, 24 Aug 2005 20:13:41 -0400
Matt Nordhoff wrote:
> On 08/24/05 15:59, Nick Rout wrote:
> > For somewhere between 3 days and a week I have been rising to find
> > that /home has become readonly overnight.
> >
> > Basically I have to shut down X, manually kill all processes
> > accessing /h
On 08/24/05 15:59, Nick Rout wrote:
For somewhere between 3 days and a week I have been rising to find
that /home has become readonly overnight.
Basically I have to shut down X, manually kill all processes
accessing /home and then run
umount /home
mount /home
which fixes it until tomorrow morn
Whats your line in fstab for /home?
It does sound cron-job like. Installed a cron daemon recently? Check
/etc/cron.daily or crontab -l
Does ownership change? Permissions?
Cheers,
Chris
Quoting Nick Rout <[EMAIL PROTECTED]>:
> For somewhere between 3 days and a week I have been rising to find
sounds like a cron job
On Wednesday 24 August 2005 14:59, Nick Rout wrote:
> For somewhere between 3 days and a week I have been rising to find
> that /home has become readonly overnight.
>
> Basically I have to shut down X, manually kill all processes
> accessing /home and then run
>
> umount
For somewhere between 3 days and a week I have been rising to find
that /home has become readonly overnight.
Basically I have to shut down X, manually kill all processes
accessing /home and then run
umount /home
mount /home
which fixes it until tomorrow morning.
I also tried mount /home -o remo
15 matches
Mail list logo
