View previous topic :: View next topic |
Author |
Message |
jesnow l33t
Joined: 26 Apr 2006 Posts: 895
|
Posted: Wed Aug 09, 2023 6:52 pm Post subject: btrfs fail [reboot fixed it] |
|
|
Hi Everybody:
I came back to one of my systems after a long absence, and was happily updating it when I discovered that my /home partition was mounted ro. How strange! dmesg was showing a lot of errors "parent transid verify failed", so I tried to unmount it and remount it rw, and the result is "Remounting read-write after error is not allowed". /dev/sda2 is my root partition, so no problem there. I'm not doing anything wild with device spanning or raid or anything, it's just a single partition.
Like this:
Code: |
[5612398.825391] BTRFS error (device sdb2): parent transid verify failed on 1081245696 wanted 318164 found 317050
[5612398.914624] BTRFS error (device sdb2): parent transid verify failed on 1081245696 wanted 318164 found 317050
[5612398.914828] BTRFS error (device sdb2): parent transid verify failed on 1081245696 wanted 318164 found 317050
[5612398.915012] BTRFS error (device sdb2): parent transid verify failed on 1081245696 wanted 318164 found 317050
[5612398.915201] BTRFS error (device sdb2): parent transid verify failed on 1081245696 wanted 318164 found 317050
[5613763.557702] BTRFS error (device sdb2): parent transid verify failed on 1081245696 wanted 318164 found 317050
[5613763.557895] BTRFS error (device sdb2): parent transid verify failed on 1081245696 wanted 318164 found 317050
[5613763.558060] BTRFS error (device sdb2): parent transid verify failed on 1081245696 wanted 318164 found 317050
[5613763.558230] BTRFS error (device sdb2): parent transid verify failed on 1081245696 wanted 318164 found 317050
[5614034.505211] BTRFS error (device sdb2): parent transid verify failed on 1081245696 wanted 318164 found 317050
[5614034.505449] BTRFS error (device sdb2): parent transid verify failed on 1081245696 wanted 318164 found 317050
[5615317.208062] BTRFS error (device sdb2): Remounting read-write after error is not allowed
[5615346.255533] BTRFS error (device sdb2): Remounting read-write after error is not allowed
[5615378.656773] BTRFS error (device sdb2): Remounting read-write after error is not allowed
[5615561.539611] BTRFS error (device sdb2): Remounting read-write after error is not allowed
[5615586.859330] BTRFS error (device sdb2): Remounting read-write after error is not allowed
[5615618.355992] BTRFS error (device sdb2): Remounting read-write after error is not allowed
[5615635.885596] device-mapper: uevent: version 1.0.3
[5615635.885641] device-mapper: ioctl: 4.45.0-ioctl (2021-03-22) initialised: dm-devel@redhat.com
[5615636.438752] SGI XFS with ACLs, security attributes, realtime, scrub, repair, quota, no debug enabled
[5615636.443563] JFS: nTxBlock = 8192, nTxLock = 65536
[5615636.453610] ntfs: driver 2.1.32 [Flags: R/W MODULE].
[5615636.652116] BTRFS info (device sda2): using free space tree
[5615636.652119] BTRFS info (device sda2): has skinny extents
[5615636.653993] BTRFS info (device sda2): enabling ssd optimizations
[5615636.668279] BTRFS info (device sda2): using free space tree
[5615636.668282] BTRFS info (device sda2): has skinny extents
[5615636.669141] BTRFS info (device sda2): enabling ssd optimizations
[5615636.725314] BTRFS info (device sdb1): using free space tree
[5615636.725317] BTRFS info (device sdb1): has skinny extents
[5615636.840258] BTRFS info (device sdb1): enabling ssd optimizations
[5615636.957023] BTRFS info (device sdb1): using free space tree
[5615636.957026] BTRFS info (device sdb1): has skinny extents
[5615637.065460] BTRFS info (device sdb1): enabling ssd optimizations
[5615637.186255] BTRFS error (device sdb2): Remounting read-write after error is not allowed
[5615639.270847] device-mapper: core: cleaned up
[5616877.843991] BTRFS error (device sdb2): Remounting read-write after error is not allowed
|
Now I'm confused how to proceed. I can mount /dev/sdb2 on /home or anywhere else as long as it's ro. But if I can't write to it, how can I run fsck on it? The gentoo manual is pretty skimpy on what to do, and honestly, until now I never had many disk errors, I mostly use ext4 on my machines. I now have to wait until emerge finishes to do anything, but would appreciate any insight.
Fortunately I have it set up so that I can log in even if /home is mounted ro, I just can't do lots of things.
Cheers,
Jon.
Last edited by jesnow on Thu Aug 10, 2023 3:05 pm; edited 1 time in total |
|
Back to top |
|
|
grknight Retired Dev
Joined: 20 Feb 2015 Posts: 2004
|
Posted: Wed Aug 09, 2023 8:07 pm Post subject: |
|
|
N.B. I am not a btrfs expert and am only repeating from searches and documentation.
This is a serious error.
Some suggestions, including the former BTRFS wiki, say to use mount -o ro,usebackuproot,remount /home (or -o ro,remount,rescue on a kernel 5.9 or newer) if it is anywhere near recoverable. If so, then it may be possible to mount rw.
Failing that, there is btrfs check or btrfs rescue. Please read about these before doing anything
In any case, all operations should be preceded by a full backup as there is corruption and the potential of loss of data doing anything (even in ro). |
|
Back to top |
|
|
jesnow l33t
Joined: 26 Apr 2006 Posts: 895
|
Posted: Wed Aug 09, 2023 8:27 pm Post subject: |
|
|
Fortunately, this particular machine has no critical data on it, I keep all my data on my server, backed up. This machine is a client I use to display things on my conference room big screen monitor.
I could lose /home entirely and not care. The disk may be bad -- that ssd was a really peculiar on that I got for $20 but is slow as mud. I will try to btrfs rescue it when it's done updating, many thanks. When mounted ro, it looks like everything is there.
Cheers,
Jon.
grknight wrote: | N.B. I am not a btrfs expert and am only repeating from searches and documentation.
This is a serious error.
Some suggestions, including the former BTRFS wiki, say to use mount -o ro,usebackuproot,remount /home (or -o ro,remount,rescue on a kernel 5.9 or newer) if it is anywhere near recoverable. If so, then it may be possible to mount rw.
Failing that, there is btrfs check or btrfs rescue. Please read about these before doing anything
In any case, all operations should be preceded by a full backup as there is corruption and the potential of loss of data doing anything (even in ro). |
|
|
Back to top |
|
|
jesnow l33t
Joined: 26 Apr 2006 Posts: 895
|
Posted: Thu Aug 10, 2023 2:58 pm Post subject: |
|
|
Well, a reboot fixed it. I think.
I rebooted after the system update and got:
Code: |
pogacar jesnow # dmesg | grep -i btrfs
[ 0.523304] Btrfs loaded, crc32c=crc32c-generic, zoned=yes, fsverity=yes
[ 3.959845] BTRFS: device fsid 52ae97d2-ebae-4e40-884a-61566c895134 devid 1 transid 59823 /dev/sdb1 scanned by (udev-worker) (451)
[ 3.961592] BTRFS: device fsid 4639603d-e819-4971-9420-285e0a10a69a devid 1 transid 318162 /dev/sdb2 scanned by (udev-worker) (400)
[ 3.963058] BTRFS: device fsid 3fc4e249-971c-4a9e-8d0a-1b65d3209028 devid 1 transid 24 /dev/sda2 scanned by (udev-worker) (398)
[ 3.963881] BTRFS: device fsid f24b3f8b-56fa-4b6d-8ddb-be462eff9e9d devid 1 transid 47387 /dev/sda1 scanned by (udev-worker) (394)
[ 4.275624] BTRFS info (device sda1): using crc32c (crc32c-intel) checksum algorithm
[ 4.275680] BTRFS info (device sda1): enabling ssd optimizations
[ 4.275692] BTRFS info (device sda1): using free space tree
[ 5.597200] BTRFS info (device sdb2): using crc32c (crc32c-intel) checksum algorithm
[ 5.597206] BTRFS info (device sdb2): using free space tree
[ 5.608908] BTRFS info (device sdb2): bdev /dev/sdb2 errs: wr 15, rd 0, flush 0, corrupt 0, gen 0
[ 5.630092] BTRFS info (device sdb2): enabling ssd optimizations
[ 5.630094] BTRFS info (device sdb2): start tree-log replay
[ 5.834616] BTRFS info (device sdb2): checking UUID tree
[ 252.726357] BTRFS error (device sdb2): bdev /dev/sdb2 errs: wr 16, rd 0, flush 0, corrupt 0, gen 0
pogacar jesnow #
|
But not the very alarming errors that prompted this post.
Cheers,
Jon. |
|
Back to top |
|
|
Zucca Moderator
Joined: 14 Jun 2007 Posts: 3930 Location: Rasi, Finland
|
Posted: Thu Aug 10, 2023 5:16 pm Post subject: |
|
|
I'd make a backup now. At least backup .config or whatever may your $XDG_CONFIG_HOME be. _________________ ..: Zucca :..
My gentoo installs: | init=/sbin/openrc-init
-systemd -logind -elogind seatd |
Quote: | I am NaN! I am a man! |
|
|
Back to top |
|
|
jesnow l33t
Joined: 26 Apr 2006 Posts: 895
|
Posted: Mon Aug 14, 2023 10:45 pm Post subject: |
|
|
Yes of course. I think possibly this SSD is wonky. It has no data on it, it is a client-only system.
Thanks!
Jon. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|