From: Cerem Cem ASLAN <ceremcem@ceremcem.net>
To: Chris Murphy <lists@colorremedies.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Unmountable root partition
Date: Thu, 2 Aug 2018 18:57:46 +0300 [thread overview]
Message-ID: <CAN4oSBfGK_vTeSVi+47GoC9i155oyuvvczC5b0vVGEapHY+m4g@mail.gmail.com> (raw)
In-Reply-To: <CAN4oSBczyZBddarXcLKAjOZ=xQsFBSjbbJi-V20UB27Z5x+Y5g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1889 bytes --]
FYI: According to ddrescue, there were read errors in +45% of the
partition. There were no chances to save anything from the disk.
2018-08-01 15:07 GMT+03:00 Cerem Cem ASLAN <ceremcem@ceremcem.net>:
> Yes, command output is as is, because I just copied and pasted into the
> mail. When I omit the `-t btrfs` part, result is the same.
>
> I'm now trying to rescue what I can, so getting a image dump with
> `ddrescue`. It's read about 25% without any errors but it will be expected
> to finish in 6 hours. Then I'll try btrfscue to see what happens.
>
> I know it's totally my fault because I must be ready for a total
> disk/pc/building burn out. Lessons learned.
>
> 2018-08-01 8:32 GMT+03:00 Chris Murphy <lists@colorremedies.com>:
>
>> On Tue, Jul 31, 2018 at 12:03 PM, Cerem Cem ASLAN <ceremcem@ceremcem.net>
>> wrote:
>>
>> > 3. mount -t btrfs /dev/mapper/foo--vg-root /mnt/foo
>> > Gives the following error:
>> >
>> > mount: wrong fs type, bad option, bad superblock on ...
>> >
>> > 4. dmesg | tail
>> > Outputs the following:
>> >
>> >
>> > [17755.840916] sd 3:0:0:0: [sda] tag#0 FAILED Result:
>> > hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
>> > [17755.840919] sd 3:0:0:0: [sda] tag#0 CDB: Read(10) 28 00 00 07 c0 02
>> 00 00
>> > 02 00
>> > [17755.840921] blk_update_request: I/O error, dev sda, sector 507906
>> > [17755.840941] EXT4-fs (dm-4): unable to read superblock
>>
>>
>> Are you sure this is the output for the command? Because you're
>> explicitly asking for type btrfs, which fails, and then the kernel
>> reports EXT4 superblock unreadable. What do you get if you omit -t
>> btrfs and just let it autodetect?
>>
>> But yeah, this is an IO error from the device and there's nothing
>> Btrfs can do about that unless there is DUP or raid1+ metadata
>> available.
>>
>> Is it possible this LV was accidentally reformatted ext4?
>>
>>
>> --
>> Chris Murphy
>>
>
>
[-- Attachment #2: Type: text/html, Size: 2854 bytes --]
prev parent reply other threads:[~2018-08-02 17:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 18:03 Unmountable root partition Cerem Cem ASLAN
2018-07-31 23:04 ` Hans van Kranenburg
2018-08-01 4:42 ` Cerem Cem ASLAN
2018-08-01 5:32 ` Chris Murphy
2018-08-01 12:07 ` Cerem Cem ASLAN
2018-08-02 15:57 ` Cerem Cem ASLAN [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=CAN4oSBfGK_vTeSVi+47GoC9i155oyuvvczC5b0vVGEapHY+m4g@mail.gmail.com \
--to=ceremcem@ceremcem.net \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).