From: C Anthony Risinger <anthony@extof.me>
To: Evert Vorster <evorster@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Slow link/Capacity changed + Kernel OOPS... possible hardware issues, ideas?
Date: Sat, 9 Oct 2010 05:30:59 -0500 [thread overview]
Message-ID: <AANLkTinx6bYPxRFP5eoT37igWJuyFMAiUMUqoVFRzVB+@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimC140L6Wv23NTNHcffSmeqeHKcM0DH0D-fUMz8@mail.gmail.com>
On Fri, Oct 8, 2010 at 11:00 PM, Evert Vorster <evorster@gmail.com> wro=
te:
> Hi there...
>
> I'm not an expert..... however, since you don't care about the data o=
n
> the SSD anymore, reformat it, and fill it up, then verify what you
> have written.
>
> However, if the capacity has changed, would that not be enough reason
> to have ASUS replace it?
yeah, i suppose i could :-)
so i tried throwing ubuntu 10.10 on it (had archlinux previously), as
i made a live USB disk so my fianc=E9 could use it to write a paper
today/tomorrow, and sure enough it worked, no problems whatsoever.
been running several hours now after install... so i'm fairly
convinced the SSD is still good enough, and i have no idea at this
point what went wrong. oh well.
C Anthony
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-10-09 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-08 3:07 Slow link/Capacity changed + Kernel OOPS... possible hardware issues, ideas? C Anthony Risinger
2010-10-08 3:20 ` Chris Ball
2010-10-08 4:34 ` C Anthony Risinger
2010-10-08 14:53 ` Chris Mason
2010-10-08 23:28 ` C Anthony Risinger
[not found] ` <AANLkTimC140L6Wv23NTNHcffSmeqeHKcM0DH0D-fUMz8@mail.gmail.com>
2010-10-09 10:30 ` C Anthony Risinger [this message]
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=AANLkTinx6bYPxRFP5eoT37igWJuyFMAiUMUqoVFRzVB+@mail.gmail.com \
--to=anthony@extof.me \
--cc=evorster@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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).