From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vk0-f48.google.com ([209.85.213.48]:38392 "EHLO mail-vk0-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388953AbeHANxA (ORCPT ); Wed, 1 Aug 2018 09:53:00 -0400 Received: by mail-vk0-f48.google.com with SMTP id k82-v6so9158546vkd.5 for ; Wed, 01 Aug 2018 05:07:31 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: From: Cerem Cem ASLAN Date: Wed, 1 Aug 2018 15:07:30 +0300 Message-ID: Subject: Re: Unmountable root partition To: Chris Murphy Cc: Btrfs BTRFS Content-Type: multipart/alternative; boundary="000000000000fd228a05725e8929" Sender: linux-btrfs-owner@vger.kernel.org List-ID: --000000000000fd228a05725e8929 Content-Type: text/plain; charset="UTF-8" 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 : > On Tue, Jul 31, 2018 at 12:03 PM, Cerem Cem ASLAN > 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 > --000000000000fd228a05725e8929 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Yes, command output is as is, because I just copied and pa= sted into the mail. When I omit the `-t btrfs` part, result is the same.=C2= =A0

I'm now trying to rescue what I can, so getting = a image dump with `ddrescue`. It's read about 25% without any errors bu= t it will be expected to finish in 6 hours. Then I'll try=C2=A0btrfscue= to see what happens.=C2=A0

I know it's totall= y my fault because I must be ready for a total disk/pc/building burn out. L= essons learned.=C2=A0

2018-08-01 8:32 GMT+03:00 Chris Murphy &= lt;lists@color= remedies.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=3DDID_BAD_TARGET driverbyte=3DDRIVER_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<= br> 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

--000000000000fd228a05725e8929--