From: "Sascha Retzki" <sretzki@gmx.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] read: i/o error: at installation
Date: Sat, 21 Oct 2006 20:49:10 +0200 [thread overview]
Message-ID: <f71fd85142b0463c66b84bcb8f6c0838@mail.gmx.net> (raw)
In-Reply-To: <ae6312490610211111x2e37eab4v86137d5d55772b59@mail.gmail.com>
>
> and it prompts me again to partdisk, and it never ends. I really don't think
> that this is the hard disks problem, it's a barely used 160GB Maxtor drive.
> Has anyone had any problems similar to this? Could it be because some of the
> hardware? (Unlikely, but...)
Sure about the disk? Disks may be broken when they arrive (broke on transport), etc.
'Not used much' may mean 'maybe I could not yet discover the issues'
So what is the controller involved? What chipset, etc?
next prev parent reply other threads:[~2006-10-21 18:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-21 18:11 Yosyp Bin Laden
2006-10-21 18:49 ` Sascha Retzki [this message]
2006-10-21 20:12 ` Yosyp Bin Laden
2006-10-22 15:45 ` erik quanstrom
2006-10-22 17:15 ` Yosyp Bin Laden
2006-10-22 18:03 ` Russ Cox
2006-10-23 0:04 ` Yosyp Bin Laden
2006-10-23 21:50 ` Yosyp Bin Laden
2006-10-22 15:42 ` erik quanstrom
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f71fd85142b0463c66b84bcb8f6c0838@mail.gmx.net \
--to=sretzki@gmx.de \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).