From: Andrey Zhunev <a-j@a-j.ru>
To: Chris Murphy <lists@colorremedies.com>
Cc: xfs list <linux-xfs@vger.kernel.org>
Subject: Re: Need help to recover root filesystem after a power supply issue
Date: Wed, 10 Jul 2019 19:07:46 +0300 [thread overview]
Message-ID: <1015034894.20190710190746@a-j.ru> (raw)
In-Reply-To: <CAJCQCtSpkAS086zSDCfB1jMQXZuacfE-SfyqQ2td4Ven4GwAzg@mail.gmail.com>
Wednesday, July 10, 2019, 6:45:28 PM, you wrote:
> On Wed, Jul 10, 2019 at 9:29 AM Andrey Zhunev <a-j@a-j.ru> wrote:
>>
>> Well, this machine is always online (24/7, with a UPS backup power).
>> Yesterday we found it switched OFF, without any signs of life. Trying
>> to switch it on, the PSU made a humming noise and the machine didn't
>> even try to start. So we replaced the PSU. After that, the machine
>> powered on - but refused to boot... Something tells me these two
>> failures are likely related...
> Most likely the drive is dying and the spin down from power failure
> and subsequent spin up has increased the rate of degradation, and
> that's why they seem related.
> What do you get for:
> # smarctl -x /dev/sda
The '-x' option gives a lot of output.
It's pasted here: https://pastebin.com/raw/yW3yDuSF
Well, if there are evidnces the drive is really dying - so be it...
I just need to recover the data, if possible.
On the other hand, if the drive will work further - I will find some
unimportant files to store...
---
Best regards,
Andrey
next prev parent reply other threads:[~2019-07-10 16:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 9:47 Need help to recover root filesystem after a power supply issue Andrey Zhunev
2019-07-10 14:30 ` Chris Murphy
2019-07-10 15:28 ` Andrey Zhunev
2019-07-10 15:45 ` Chris Murphy
2019-07-10 16:07 ` Andrey Zhunev [this message]
2019-07-10 16:46 ` Chris Murphy
2019-07-10 16:47 ` Chris Murphy
2019-07-10 17:16 ` Andrey Zhunev
2019-07-10 18:03 ` Chris Murphy
2019-07-10 18:35 ` Carlos E. R.
2019-07-10 19:30 ` Chris Murphy
2019-07-10 23:43 ` Andrey Zhunev
2019-07-11 2:47 ` Carlos E. R.
2019-07-11 7:10 ` Andrey Zhunev
2019-07-11 10:23 ` Carlos E. R.
2019-07-10 16:51 ` Chris Murphy
-- strict thread matches above, loose matches on Subject: below --
2019-07-10 9:56 Andrey Zhunev
2019-07-10 13:26 ` Eric Sandeen
2019-07-10 13:58 ` Andrey Zhunev
2019-07-10 14:23 ` Eric Sandeen
2019-07-10 15:02 ` Andrey Zhunev
2019-07-10 15:23 ` Eric Sandeen
2019-07-10 18:21 ` Carlos E. R.
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=1015034894.20190710190746@a-j.ru \
--to=a-j@a-j.ru \
--cc=linux-xfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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