From: Ruediger Meier <sweet_f_a@gmx.de>
To: Sergey Zolotarev <szx@live.ru>
Cc: "util-linux@vger.kernel.org" <util-linux@vger.kernel.org>
Subject: Re: Fix partition order killed my hard drive (twice)
Date: Mon, 13 Apr 2015 12:27:44 +0200 [thread overview]
Message-ID: <201504131227.45506.sweet_f_a@gmx.de> (raw)
In-Reply-To: <DUB119-W10D0E142F9CF92AA8A3436B4E70@phx.gbl>
On Monday 13 April 2015, Sergey Zolotarev wrote:
> Hello,
>
> Is it possible that fdisk could damage / kill a hard drive after
> using the "Fix partition order" command?
I remember there was such bug in past. Which version are you using?
$ fdisk -V
> It seems that that is
> exactly what happened to me two times already, with two different
> hard drives.
>
> First time I thought that it was my hard drive's fault as it was
> pretty old and cheap, So I bought a new not-so-cheap one and was
> quite happy with until today, when I used that evil command again!
>
> Both of HDDs seem unrecoverable. When either is plugged BIOS gets
> stuck at initial screen (can't even enter setup). Using a USB adapter
> didn't help either... I'm not an expert in hard drives, but could it
> be the result of a corrupted / bad sector in the place where the
> partition table is stored?
First I would try to boot via rescue CD or similar.
Then check how the partitiontable looks now (fdisk -l) and try to mout
partitions manually. If you are missing partitions or if you just can't
mount them then you may try to repair/recover the partition table.
cu,
Rudi
next prev parent reply other threads:[~2015-04-13 10:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 10:11 Fix partition order killed my hard drive (twice) Sergey Zolotarev
2015-04-13 10:27 ` Ruediger Meier [this message]
2015-04-14 2:53 ` Dale R. Worley
2015-04-13 10:31 ` Karel Zak
2015-04-13 13:58 ` Peter Cordes
[not found] ` <DUB119-W317EAA79F1829FA13DAEA6B4E60@phx.gbl>
[not found] ` <20150418034306.GF3933@cordes.ca>
2015-04-18 6:25 ` Sergey Zolotarev
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=201504131227.45506.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=szx@live.ru \
--cc=util-linux@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