[Bug 1931790] Re: Unable to mount btrfs RAID 1 filesystem after reboot - Error - device total_bytes should be at most X but found Y
Ravindran K
1931790 at bugs.launchpad.net
Wed Aug 11 14:09:01 UTC 2021
Hi Lukasz,
Unfortunately I could not find much alternatives/solutions in multiple
forums..
The best and easy workaround (if you are prepared to wait infinely: as noone responds to these one off issues) would be to install the mainline tool and install a older version of kernel:
https://ubuntuhandbook.org/index.php/2020/08/mainline-install-latest-kernel-ubuntu-linux-mint/
This will most likely work as it has worked for multiple people..Make
sure you choose old version of kernel like 5.4 (that worked for me).
Useful Tip:Try booting using Ubuntu Mint USB to see if you btrfs volume
readily mounts.
The other alternatuve solution which I discovered the hardway is to
break one of the disks (In my case, I rebuilt both disks one after the
other due to some issues) and re-add it and rebuild to see if that
solves..
The other best solution would be to delete both the raid devices and
create a new raid 1 volume from scratch while booted on the new kernel.
ofcourse this needs enough space and a backup which you can restore.
I reiterate, please backup if you data is valuable before you try
anything as inadvertently you might lose data while troubleshooting this
issue... All the best ..keep us posted :)
Regards
Ravindran
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to btrfs-progs in Ubuntu.
https://bugs.launchpad.net/bugs/1931790
Title:
Unable to mount btrfs RAID 1 filesystem after reboot - Error - device
total_bytes should be at most X but found Y
Status in Ubuntu:
New
Status in btrfs package in Ubuntu:
New
Status in btrfs-progs package in Ubuntu:
New
Bug description:
Hi,
I'm unable to mount my newly created btrfs RAID 1 filesystem after
reboot..I performed the below steps with my 2 X 1 TB drives:
* created a new btrfs filesystem
mkfs.btrfs /dev/sdd1
* mounted it to /mnt/datanew
mount -t btrfs /dev/sdd1 /mnt/datanew
* copied over data from my previous NTFS volume on /dev/sde1 (which I
intended to add later as a mirror) - took 3.5 hrs
* added a new volume
mkfs.btrfs device add /dev/sde1
* started balance and convert to raid 1 - took 8 to 10
hours..overnight
btrfs balance start -dconvert=raid1 -mconvert=raid1 /mnt/datanew
* rebooted next morning
I seeing below errors:
[ 792.045980] BTRFS info (device sdd1): allowing degraded mounts
[ 792.045988] BTRFS info (device sdd1): disk space caching is enabled
[ 792.045990] BTRFS info (device sdd1): has skinny extents
[ 792.047498] BTRFS error (device sdd1): device total_bytes should be at most 1000201841152 but found 1000203804672
[ 792.049207] BTRFS error (device sdd1): failed to read chunk tree: -22
[ 792.051525] BTRFS error (device sdd1): open_ctree failed
* Manual mount has below error additonally
mount: /mnt/datanew: wrong fs type, bad option, bad superblock on /dev/sde1, missing codepage or helper program, or other error.
* Verified the data seems intact (apparently no errors), superblock
seems fine.. tried btrfs rescue commands.. no issues found to fix
* Found several hits on search but not many solutions..except "btrfs filesystem resize max /" which doesnt work as I'm unable to mount in the first place..
btrfs filesystem resize max /mnt/datanew/
ERROR: not a btrfs filesystem: /mnt/datanew/
Any suggestions? Thanks
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubuntu-release-upgrader-core 1:21.04.13
ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12
Uname: Linux 5.11.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
CasperMD5CheckResult: pass
CrashDB: ubuntu
Date: Sun Jun 13 11:17:02 2021
InstallationDate: Installed on 2021-05-16 (27 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_IN:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_IN
SHELL=/bin/bash
SourcePackage: ubuntu-release-upgrader
Symptom: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1931790/+subscriptions
More information about the foundations-bugs
mailing list