Update ended in readonly filesystem

[Zesko]

Try to run

$ sudo btrfs inspect-internal logical-resolve 253952 /
$ sudo btrfs inspect-internal logical-resolve 3037134 /
$ sudo btrfs inspect-internal logical-resolve 180469760 /

[Adramyttium]

@Adramyttium

ERROR: logical ino ioctl: No such file or directory

ERROR: logical ino ioctl: No such file or directory

in each case.

[Zesko]

I guess that btrfs-progs tool can’t find or read some file if this file is already gone but its checksum is present. That is why it would be marked as the corrupted file in the Btrfs log.

---

Edit://

This is my stupid thought, sorry.

Look at the mismatched checksum:

@Adramyttium

csum 0xc341dc86 expected csum 0xc341fc86

0xc341dc86 =/= 0xc341fc86 → That looks like d does not match f.
The damaged file must be there.

I think btrfs inspect logical-resolve <logical> <path> has some bug. I will report the bug on btrfs-prog github

[Adramyttium]

I see what you are referring to. As for my immediate situation, is there any way to resolve this? Or do I need to replace the NVME drive?

[1efaf7d71a8637c6800a]

I can have a look at it too. What is your status? I mean, have you backed up your data i.e. copied over what you need to an external drive? Did you make a bootable Manjaro live stick (or a different distro)?

[Zesko]

Testing your hardware is not easy:

• Check a cable (NVME PCIe does not use the cable)

• Test your RAMs (Remove all RAMs and test every single RAM with test tool for example memtest and copying any large file 10 GB+ on the same filesystem and check it with sha1sum, if both files match correctly. Test 10 times repetitions)

• If all RAM tests pass, then replace your disk with another disk

• If the problem persists after replacing the drive, the mainboard or the CPU cache is probably the problem.

[1efaf7d71a8637c6800a]

Let’s try to fix what’s there Zesko. Why would you assume RAM’s fault?
Did you use Timeshift to Btrfs-snaphot on regular basis? If so, about how often, hourly, daily, weekly, on boot?

[Adramyttium]

A appreciate your willingness to help!

The good news is that almost all of my urgent data is in the cloud and was up to date before this disaster struck. The few items that weren’t in the cloud that have been backed up on a separate USB device. I have a live stick ready. FYI - I use an encrypted LUKS device. The most I might lose is some ancient archived emails in Thunderbird.

My chief worry at this point is if the NVME drive hardware itself is flawed, or if BTRFS was somehow the source of my problem.

I did take snaps regularly, but I can’t remember the preset frequency (it was probably weekly). The latest snap was taken at the beginning of the upgrade process where I ran into this error.

[1efaf7d71a8637c6800a]

If it is new as you say, it should not be a hardware mistake. Let’s try to look at it with btrfs built-in commands.
Therefore please boot the computer into the live environment and tell me when you have, here.

[Adramyttium]

I will do that, but circumstances are such that I have to be away from the machine for a few hours. May I reply to this thread when I’m available again? Again, I GREATLY appreciate your willingness to help me, a total stranger, and I want to be sure to not waste any of your time.

[Zesko]

@1efaf7d71a8637c6800a

Why would you assume RAM’s fault?

@1efaf7d71a8637c6800a

If it is new as you say, it should not be a hardware mistake.

That is not true.
In my real experience, I had bought a new RAM, it had already been damaged (Only 1 random bit is damaged), thanks Btrfs stopped copying my new backup to other hard drive because the backup was corrupted.

Do not trust new hardware after buying it!
And don’t trust old hardware. Every hardware has a lifespan limit.

BTRFS error occurred while copying the zip file

Hi everyone, I got the BTRFS error while copying the zip file in my disk using BTRFS. The Copy process is canceled immediately. I tried cp ❯ cp ~/MEGA1.zip ~/Downloads cp: error reading '/home/zesko/MEGA1.zip': Input/output error if cp does not work, I tried scp: ❯ scp ~/MEGA1.zip ~/Downloads cp: error reading '/home/zesko/MEGA1.zip': Input/output error if scp does not work, I tried rsync: ❯ rsync -c ~/MEGA1.zip ~/Downloads rsync: [sender] read errors mapping "/home/zesko/MEGA1.zip":…

[1efaf7d71a8637c6800a]

Huh I was in the same position you are in right now so I appreciate to help (where I can). As said, I will check again into this thread until we have a solution or we are sure we can’t find one.

Plan is to find error messages and then act accordingly. I will be back tomorrow night or Friday too so don’t worry.

@Zesko

In my real experience, I had bought a new RAM, it had already been damaged (Only 1 random bit is damaged), thanks Btrfs stopped copying my new backup to other hard drive because the backup was corrupted.

Do not trust new hardware after buying it!

Yes, RAM can be the root of the evil in some cases, true. However there are many errors btrfs can spawn and yours does not seem to liken Adram's.
There are to my knowledge several error scenarios and one should look at which method to fix the filesystem with. I will not recommend anything that is not recommended at Welcome to BTRFS documentation! — BTRFS documentation

Edit: Oops sorry Zesko your errors are in fact similar…
How do I get the strike-through option for text?

[Adramyttium]

Hey, I just wanted to let you know that I’m not going to need your help. Upon further research, the drive has failed and will need to be replaced.

I came to this conclusion after reading this article. My smartctl analysis yielded the same error, and thus it’s time to move on. Thank you again for your willingness to help!

[andreas85]

So btrfs did rescue you

At the right time, in letting you know that the data had been altered.

With an other filesystem you would have noticed it a lot later.