BTRFS Crashes Machine

[orbvs]

Hi
If you want to use 4K sectors, that means a complete re-install...... what happens if you remove?

If I remove what particularly? The 'nvme.core' line, or another bit?

Everything is backed up, and I'm willing to reinstall or "break" this machine trying to fix this issue.

[malcolmlewis]

If I remove what particularly? The 'nvme.core' line, or another bit?

Everything is backed up, and I'm willing to reinstall or "break" this machine trying to fix this issue.

Hi
The nvme one, just reboot and at grub press the 'e' key to edit and arrow down to the linuxefi line and delete temporarily, press F10 to boot and see how it goes.

To change the format, you need to boot from a rescue USB device so the nvme device is not mounted....

FOR REFERENCE ONLY THIS IS DESTRUCTIVE!!

Check NVME

nvme id-ns -H /dev/nvmeXnY


Set to 4096 rather than 512


nvme format --lbaf=NUMBER /dev/nvmeXnY

[orbvs]

malcolmlewis,

If I remove the 'nvme.core=0' line, typically the machine boots fine, but at some point (within a couple hours) the GUI dies and I see the 'BTRFS error' on the screen (from my earlier post in this thread).

There are some Stack exchange posts on the issue, and other forums (including on Western Digital's forum), but they seem concerned with startup--as in Linux would not boot without the GRUB parameter, whereas I find boot and userland are fine, but the system experiences crashes after a while.

I'll try cloning the drive and seeing if it could be hardware, but I'm not sure how a GRUB config would change a hardware issue. Hence this curious and tricky problem...

[karlmistelberger]

Oh yikes, I do see quite a few worrying errors, or at least they seem worrying to me. Again, I am largely ignorant of these things. But I am learning! I have bolded the errors I see below. "device incomplete in udev" seems...bad. But I do not have LVM running on this machine, so I'm unsure why I am seeing an error from lvm?

Nothing to worry here but lvm. Make sure it is disabled by running "systemctl disable --now lvm2-monitor.service lvm2-lvmpolld.socket":

erlangen:~ # systemctl list-unit-files lvm* 
UNIT FILE             STATE    VENDOR PRESET
lvm2-lvmpolld.service static   -            
lvm2-monitor.service  disabled enabled      
lvm2-pvscan@.service  static   -            
lvm2-lvmpolld.socket  disabled enabled      

4 unit files listed. 
erlangen:~ # systemctl list-units lvm*      
  UNIT LOAD ACTIVE SUB DESCRIPTION
0 loaded units listed. Pass --all to see loaded but inactive units, too. 
To show all installed unit files use 'systemctl list-unit-files'. 
erlangen:~ #

Note: lvm is installed, but deactivated:

erlangen:~ # journalctl -g lvm2 
-- Journal begins at Wed 2021-12-15 08:27:08 CET, ends at Sun 2022-01-09 20:31:25 CET. -- 
-- Boot 0649246d479f442b84ce423b79792aab --
-- Boot ca63465bf82b4a56bc3c2b1447f08a75 --
-- Boot 1812fef95504402d897a10d449778ced --
-- Boot 8f709d2700c54d5f906c110ad60706a7 --
-- Boot 6a6d9bafb74d46f4a8621995d122e49d --
-- Boot 08c401e4fad5451bbf656cd6a9cfe6ff --
-- Boot 8e72b8f2b5754a00993ef0a24000c6fb --
-- Boot 86ae4c0590c447dcafb81ab753c7d1c8 --
-- Boot 63f2559c364844a1989d150c53a90c0d --
-- Boot 2af3377281f049bb812bbf5f7a4fca54 --
-- Boot 76efbe153a694e2b8f85b457af196df0 --
Jan 09 19:48:26 erlangen [RPM][14533]: erase liblvm2cmd2_03-2.03.12-3.2.x86_64: success
Jan 09 19:48:26 erlangen [RPM][14533]: install liblvm2cmd2_03-2.03.12-3.3.x86_64: success
Jan 09 19:48:26 erlangen [RPM][14533]: erase liblvm2cmd2_03-2.03.12-3.2.x86_64: success
Jan 09 19:48:26 erlangen [RPM][14533]: install liblvm2cmd2_03-2.03.12-3.3.x86_64: success
Jan 09 19:53:29 erlangen [RPM][18965]: erase lvm2-2.03.12-3.2.x86_64: success
Jan 09 19:53:29 erlangen [RPM][18965]: install lvm2-2.03.12-3.3.x86_64: success
Jan 09 19:53:30 erlangen [RPM][18965]: erase lvm2-2.03.12-3.2.x86_64: success
Jan 09 19:54:11 erlangen [RPM][21326]: erase libbd_lvm2-2.26-2.1.x86_64: success
Jan 09 19:54:12 erlangen [RPM][21326]: install libbd_lvm2-2.26-2.2.x86_64: success
Jan 09 19:54:12 erlangen [RPM][21326]: erase libbd_lvm2-2.26-2.1.x86_64: success
Jan 09 19:54:12 erlangen [RPM][21326]: install libbd_lvm2-2.26-2.2.x86_64: success
-- Boot 25050f121f7049d0a3af17c30dfd481c --
erlangen:~ #

[orbvs]

Nothing to worry here but lvm. Make sure it is disabled by running "systemctl disable --now lvm2-monitor.service lvm2-lvmpolld.socket":

Thank you for that! I've disabled it from spamming my logs now.

I'll keep playing around with this kernel paramater, and report back what I find (if anything can be systematically determined).

Thank you so much!

[karlmistelberger]

Thank you for that! I've disabled it from spamming my logs now.

lvm2 does much more than spamming the logs. It can cause delays on shutdown and more. That's why I bothered. As a rule of thumb: If you don't use it disable:

erlangen:~ # systemctl list-unit-files | grep enabled | grep disabled      
apache2.service                              enabled         disabled
avahi-daemon.service                         disabled        enabled 
bluetooth.service                            enabled         disabled
chronyd.service                              enabled         disabled
FR735.service                                enabled         disabled
GARMIN.service                               enabled         disabled
hd-idle.service                              enabled         disabled
lm_sensors.service                           enabled         disabled
lvm2-monitor.service                         disabled        enabled 
minidlna.service                             enabled         disabled
ModemManager.service                         disabled        enabled 
nscd.service                                 disabled        enabled 
smartd.service                               disabled        enabled 
systemd-networkd.service                     enabled         disabled
systemd-remount-fs.service                   enabled-runtime disabled
systemd-resolved.service                     enabled         disabled
lvm2-lvmpolld.socket                         disabled        enabled 
systemd-networkd.socket                      enabled         disabled
backup-home.timer                            enabled         disabled
btrfs-defrag.timer                           disabled        enabled 
btrfs-trim.timer                             disabled        enabled 
fetchmail.timer                              enabled         disabled
mdcheck_start.timer                          disabled        enabled 
packagekit-background.timer                  enabled         disabled
erlangen:~ #