[Resolved] BTRFS error

[c3p0]

I have the following error-messages:

Code: Select all

Welcome to openSUSE Leap 42.3 - Kernel 4.4.132-53-default (tty1).

linux-wsr3 login: [    51.315163] BTRFS error (device sda2): parrent transid verify failed on 6647595008 wanted 182271 found 173853
........
[    51.317145] systemd-journalid[392]: Failed to truncate file to its own size: Read-only file system
........

Host Operating System: openSUSE 42.2
VirtualBox Graphical User Interface Version 5.1.32_SUSE r120294
I need to repair above VrtualBox machine

[socratis]

1. Where do you get that message?
2. Why do you think this is due to VirtualBox?

[c3p0]

1. I get that message in the VirtualBox guest window at starting it;
2. I think this is due to VirtualBox, because it worked fine about 3 months;

Is there any way to repair that VirtualMachine ?
Is there any way to get access for files in that VirtualMachine ?

[socratis]

1. I get that message in the VirtualBox guest window at starting it;

Then it's a guest error, right?

2. I think this is due to VirtualBox, because it worked fine about 3 months.

That's not a good enough reason. Everything works until it breaks. Even the lamp on my desk...

We're going to need a complete VBox.log, from a complete VM run:

• Gathering the necessary information:
  1. Start the VM from cold-boot (not from a paused or saved state).
  2. Observe the error. Do *not* crop the errors. Post them whole.
  3. Shutdown the VM (force close it if you have to).
• With the VM completely shut down (not paused or saved), right-click on the VM in the VirtualBox Manager and select "Show Log".
• Save only the first "VBox.log", ZIP it and attach it to your response. See the "Upload attachment" tab below the reply form.

[c3p0]

Code: Select all

ound 181135
[    7393121] BTRFS error (device sda2): parrent transid verify failed on 6648610816 wanted 182271 found 181135

Welcome to openSUSE Leap 42.3 - Kernel 4.4.132-53-default (tty1).

linux-wsr3 login [    140.801746] BTRFS error (device sda2): parrent transid verify failed on 6647595008 wanted 182271 found 173853
[    140.802107] BTRFS error (device sda2): parrent transid verify failed on 6647595008 wanted 182271 found 173853
[    140.803029] system-journalid[395]: Failed to truncate file to its own size: Read-only file system
[    140.803111] system-journalid[395]: Failed to truncate file to its own size: Read-only file system
[    140.803142] system-journalid[395]: Failed to truncate file to its own size: Read-only file system
[    140.803364] BTRFS error (device sda2): parrent transid verify failed on 6647595008 wanted 182271 found 173853
[    140.804944] BTRFS error (device sda2): parrent transid verify failed on 6647595008 wanted 182271 found 173853
[    140.805598] BTRFS error (device sda2): parrent transid verify failed on 6647595008 wanted 182271 found 173853
[    140.806997] BTRFS error (device sda2): parrent transid verify failed on 6647595008 wanted 182271 found 173853
[    140.809402] system-journalid[395]: Failed to truncate file to its own size: Read-only file system
[    140.809471] system-journalid[395]: Failed to truncate file to its own size: Read-only file system
[    140.809501] system-journalid[395]: Failed to truncate file to its own size: Read-only file system
[    140.809529] system-journalid[395]: Failed to truncate file to its own size: Read-only file system
[    153.053060] system-journalid[395]: Failed to truncate file to its own size: Read-only file system
[    153.053173] system-journalid[395]: Failed to truncate file to its own size: Read-only file system
[    153.053275] system-journalid[395]: Failed to truncate file to its own size: Read-only file system
[    153.053376] system-journalid[395]: Failed to truncate file to its own size: Read-only file system
[    153.053475] system-journalid[395]: Failed to truncate file to its own size: Read-only file system
[    153.053576] system-journalid[395]: Failed to truncate file to its own size: Read-only file system
[    153.053710] system-journalid[395]: Failed to truncate file to its own size: Read-only file system
[    153.053833] system-journalid[395]: Failed to truncate file to its own size: Read-only file system
[    153.053936] system-journalid[395]: Failed to truncate file to its own size: Read-only file system
[    153.069939] system-journalid[395]: Failed to truncate file to its own size: Read-only file system

[socratis]

VirtualBox VM 5.1.32_SUSE r120294 linux.amd64 (openSUSE Buildservice) release log

It looks like you're using the distro's fork version of VirtualBox. You can either ask in their forums for help, or completely remove/uninstall/delete/purge their version and install the official version from the Downloads section of VirtualBox. Plus it's an older version, we're not up to 5.2.12.

Now, you're on a Linux host. And there have been some instances where the Linux filesystem goes read-only, if it detects an abnormality. See:

• Fedora 27 guest frequently goes into read only fs mount
• raid-check crashes client VirtualMachine

I'd start by checking your host's hard drive. And the fact that you have the VM running from an external drive, will definitely NOT help the situation, especially when it's not a native filesystem, but one that has to be supported by FUSE:

00:00:00.748614 File system of '/run/media/suluq/21D5106D0A8E743F/ORACLE.VB/PISMO-GQ-SUSE
                /PISMO-GQ-LEAP.vhd' is fuse

[c3p0]

I could try to start this guest vbox under windows 7, there I will install the last version of VirtualBox for Windows ....

[c3p0]

I connected a HDD with Windows 10 installed and run Win 10.
I installed: VirtualBox Version 5.2.12 r122591 (Qt5.6.2)
After that I did try to start the VBox that could not start:

Code: Select all

Welcome to openSUSE Leap 42.3 - Kernel 4.4.132-53-default (tty1).

linux-wsr3 login [    61.987882] BTRFS error (device sda2): parent transid verify failed on 664759008 wanted 182271 found 173853
[    61.988652] BTRFS error (device sda2): parent transid verify failed on 664759008 wanted 182271 found 173853
[    61.989349] BTRFS error (device sda2): parent transid verify failed on 664759008 wanted 182271 found 173853
[    61.989985] BTRFS error (device sda2): parent transid verify failed on 664759008 wanted 182271 found 173853
[    61.989349] BTRFS error (device sda2): parent transid verify failed on 664759008 wanted 182271 found 173853
........
[    61.991369]system-journalid[387]: Failed to truncate file to its own size: Read-only file system
........

[socratis]

Re-install your guest, or install a second instance of the guest VM. Do you still have that problem? And try to avoid your portable USB driver, copy the VHD in your actual hard drive. Try to simplify your setup until you find which of the candidates is responsible for this.

[c3p0]

I have installed another guest VM that is 11 GB. It starts and works fine.
The guest VM that can not start is 25 GB. I need to access files from its file system and upload them on a safe place.
I remember I installed guest VM size 11 GB on a portable USB SSD, I made a copy of it on a HDD and used the copy 3-4 months the size of .VHD file increased to 25 GB. Now I just need to get some files from that guest VM.
After that I installed a second instance of the guest VM on local HDD, its size is 5 GB and it works fine.

[socratis]

I have installed another guest VM that is 11 GB. It starts and works fine

Which proves that there's something wrong with the first guest, not necessarily VirtualBox.

I need to access files from its file system and upload them on a safe place.

I won't point you to a backup, because chances are you don't have one, otherwise we wouldn't be having this discussion .

What you can do is to add your original VDI as a secondary drive on your new guest. Or boot your original guest from a LiveDVD. Then you can access your files, just like you would do on a real system...

[c3p0]

If I can to add my original VHD as a secondary drive on my new working guest that will be a great solution!

[socratis]

Sure, just shutdown both VMs, not paused or saved, complete shutdown (you wouldn't move hard drives while the computer is running, would you?) and then add a 2nd hard drive to your working guest. When asked if you would like to create a new HD or use an existing one, point it to the existing one. Done.

Make a backup first. You didn't do it before, don't keep on skipping the backups. They're vital if something happens with your data.

[c3p0]

Thank you very much !!!!
It is fantastic, because your advice is great one and I have access to 25 GB .vhd and I can backup files, an I can upload files to a safe place!
Thank you again !!!!

[socratis]

\o/
Glad you got it going. Marking as [Resolved].