System:
Kernel: 6.10.11-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/vmlinuz-6.10-x86_64 root=/dev/sda4 rw quiet
udev.log_priority=3
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.43 wm: xfwm4 v: 4.18.0
with: xfce4-panel tools: light-locker vt: 1 dm: LightDM v: 1.32.0
Distro: Manjaro base: Arch Linux
Machine:
Type: Desktop System: Shuttle product: DS81D v: V1.0
serial: <superuser required>
Mobo: Shuttle model: FS81 v: 1.0 serial: <superuser required> part-nu: 1.0
uuid: <superuser required> UEFI: American Megatrends v: 3.14
date: 09/17/2018
Battery:
Message: No system battery data found. Is one present?
Memory:
System RAM: total: 16 GiB available: 15.51 GiB used: 3.33 GiB (21.5%)
Message: For most reliable report, use superuser + dmidecode.
Array-1: capacity: 32 GiB slots: 4 modules: 2 EC: None
max-module-size: 8 GiB note: est.
Device-1: ChannelA-DIMM0 type: DDR3 detail: synchronous size: 8 GiB
speed: 1600 MT/s volts: curr: 2 min: 1.35 max: 2 width (bits): data: 64
total: 64 manufacturer: Crucial part-no: CT102464BF160B.C16
serial: <filter>
Device-2: ChannelA-DIMM1 type: no module installed
Device-3: ChannelB-DIMM0 type: DDR3 detail: synchronous size: 8 GiB
speed: 1600 MT/s volts: curr: 2 min: 1.35 max: 2 width (bits): data: 64
total: 64 manufacturer: Crucial part-no: CT102464BF160B.C16
serial: <filter>
Device-4: ChannelB-DIMM1 type: no module installed
PCI Slots:
Permissions: Unable to run dmidecode. Root privileges required.
CPU:
Info: model: Intel Core i7-4785T bits: 64 type: MT MCP arch: Haswell
gen: core 4 level: v3 note: check built: 2013-15 process: Intel 22nm
family: 6 model-id: 0x3C (60) stepping: 3 microcode: 0x28
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
smt: enabled cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB
desc: 4x256 KiB L3: 8 MiB desc: 1x8 MiB
Speed (MHz): avg: 1496 min/max: 800/3200 scaling: driver: intel_cpufreq
governor: schedutil cores: 1: 1496 2: 1496 3: 1496 4: 1496 5: 1496 6: 1496
7: 1496 8: 1496 bogomips: 35131
Flags: abm acpi aes aperfmperf apic arat arch_perfmon avx avx2 bmi1 bmi2
bts clflush cmov constant_tsc cpuid cpuid_fault cx16 cx8 de ds_cpl dtes64
dtherm dts epb ept ept_ad erms est f16c flexpriority flush_l1d fma fpu
fsgsbase fxsr ht ibpb ibrs ida invpcid lahf_lm lm mca mce md_clear mmx
monitor movbe msr mtrr nonstop_tsc nopl nx pae pat pbe pcid pclmulqdq
pdcm pdpe1gb pebs pge pln pni popcnt pse pse36 pti pts rdrand rdtscp
rep_good sdbg sep smep smx ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp
syscall tm tm2 tpr_shadow tsc tsc_adjust tsc_deadline_timer vme vmx vnmi
vpid x2apic xsave xsaveopt xtopology xtpr
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data status: Unknown: No mitigations
Type: reg_file_data_sampling status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
sanitization
Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
STIBP: conditional; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics
vendor: Holco Enterprise Co /Shuttle driver: i915 v: kernel arch: Gen-7.5
process: Intel 22nm built: 2013 ports: active: DP-2,HDMI-A-1 empty: DP-1,
HDMI-A-2, HDMI-A-3, VGA-1 bus-ID: 00:02.0 chip-ID: 8086:0412
class-ID: 0300
Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 24.1.2
compositor: xfwm4 v: 4.18.0 driver: X: loaded: modesetting
alternate: fbdev,vesa dri: crocus gpu: i915 display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 96 s-size: 1016x285mm (40.00x11.22")
s-diag: 1055mm (41.54")
Monitor-1: DP-2 pos: right model: 100027813 serial: <filter> built: 2021
res: 1920x1080 hz: 60 dpi: 80 gamma: 1.2 chroma: red: x: 0.651 y: 0.329
green: x: 0.318 y: 0.620 blue: x: 0.149 y: 0.071 white: x: 0.314 y: 0.329
size: 609x348mm (23.98x13.7") diag: 690mm (27.2") ratio: 16:9
modes: 1920x1080, 1680x1050, 1280x1024, 1440x900, 1280x960, 1280x800,
1152x864, 1280x720, 1024x768, 832x624, 800x600, 720x576, 720x480,
640x480, 720x400
Monitor-2: HDMI-A-1 mapped: HDMI-1 pos: primary,left model: 100094417
serial: <filter> built: 2022 res: 1920x1080 hz: 60 dpi: 82 gamma: 1.2
chroma: red: x: 0.651 y: 0.329 green: x: 0.318 y: 0.620 blue: x: 0.149
y: 0.071 white: x: 0.314 y: 0.329 size: 598x336mm (23.54x13.23")
diag: 685mm (27") ratio: 16:9 modes: 1920x1080, 1680x1050, 1280x1024,
1440x900, 1280x960, 1280x800, 1152x864, 1280x720, 1024x768, 832x624,
800x600, 720x576, 720x480, 640x480, 720x400
API: EGL v: 1.5 hw: drv: intel crocus platforms: device: 0 drv: crocus
device: 1 drv: swrast gbm: drv: crocus surfaceless: drv: crocus x11:
drv: crocus inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 24.2.2-arch1.1
glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 4600 (HSW
GT2) device-ID: 8086:0412 memory: 1.46 GiB unified: yes
API: Vulkan v: 1.3.295 layers: 7 device: 0 type: integrated-gpu name: Intel
HD Graphics 4600 (HSW GT2) driver: mesa intel v: 24.2.2-arch1.1
device-ID: 8086:0412 surfaces: xcb,xlib
Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
driver: snd_hda_intel v: kernel bus-ID: 00:03.0 chip-ID: 8086:0c0c
class-ID: 0403
Device-2: Intel 8 Series/C220 Series High Definition Audio vendor: Holco
Enterprise Co /Shuttle driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
chip-ID: 8086:8c20 class-ID: 0403
API: ALSA v: k6.10.11-2-MANJARO status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: JACK v: 1.9.22 status: off tools: N/A
Server-2: PipeWire v: 1.2.3 status: off with: pipewire-media-session
status: active tools: pw-cli
Server-3: PulseAudio v: 17.0 status: active with: pulseaudio-alsa
type: plugin tools: pacat,pactl,pavucontrol
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Holco Enterprise Co /Shuttle driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp2s0 state: down mac: <filter>
Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Holco Enterprise Co /Shuttle driver: r8169 v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168
class-ID: 0200
IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: noprefixroute scope: link
IF-ID-1: enp0s20u2u1u1 state: unknown speed: -1 duplex: half mac: <filter>
IP v4: <filter> type: dynamic noprefixroute scope: global
broadcast: <filter>
IP v6: <filter> type: dynamic noprefixroute scope: global
IP v6: <filter> type: noprefixroute scope: link
Info: services: NetworkManager, sshd, systemd-timesyncd
WAN IP: <filter>
Bluetooth:
Device-1: T & A Mobile Phones TCL TAB 8 LE driver: rndis_host,usbfs
type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-2.1.1:7
chip-ID: 1bbb:0173 class-ID: 0a00 serial: <filter>
Device-2: Cambridge Silicon Radio Bluetooth Dongle (HCI mode)
driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1
bus-ID: 3-6:5 chip-ID: 0a12:0001 class-ID: e001
Report: ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0 lmp-v: 6
status: discoverable: no pairing: no class-ID: 6c0104
Logical:
Message: No logical block device data found.
RAID:
Message: No RAID data found.
Drives:
Local Storage: total: 1.43 TiB used: 890.24 GiB (60.7%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/sda maj-min: 8:0 vendor: Fanxiang model: S301 512GB
size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 195 scheme: GPT
ID-2: /dev/sdb maj-min: 8:16 vendor: Crucial model: CT1000MX500SSD1
size: 931.51 GiB block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s
tech: SSD serial: <filter> fw-rev: 045 scheme: GPT
ID-3: /dev/sdc maj-min: 8:32 model: USB DISK 3.0 size: 57.77 GiB
block-size: physical: 512 B logical: 512 B type: USB rev: 3.2 spd: 5 Gb/s
lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter> fw-rev: PMAP
scheme: MBR
Message: No optical or floppy data found.
Partition:
ID-1: / raw-size: 192.22 GiB size: 192.22 GiB (100.00%)
used: 116.43 GiB (60.6%) fs: btrfs dev: /dev/sda4 maj-min: 8:4 label: N/A
uuid: N/A
ID-2: /boot raw-size: 1.3 GiB size: 1.25 GiB (95.88%)
used: 319.8 MiB (25.0%) fs: ext4 dev: /dev/sda2 maj-min: 8:2 label: Boot
uuid: d7c5b3f3-f6a2-46ea-a020-fc5e9aaf918b
ID-3: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%)
used: 54.1 MiB (10.6%) fs: vfat dev: /dev/sda1 maj-min: 8:1 label: EFI
uuid: 0C5A-87F5
ID-4: /home raw-size: 931.51 GiB size: 915.82 GiB (98.32%)
used: 773.45 GiB (84.5%) fs: ext4 dev: /dev/sdb1 maj-min: 8:17 label: home
uuid: bfa899b9-f545-4ead-a125-da3138006af5
Swap:
Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
compressor: zstd max-pool: 20%
ID-1: swap-1 type: partition size: 31.52 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/sda6 maj-min: 8:6 label: N/A
uuid: 2c99a5cd-a236-42fc-a710-770a98b1b5b3
Unmounted:
ID-1: /dev/sda3 maj-min: 8:3 size: 136.36 GiB fs: ntfs label: Windows 10
uuid: 5208F48108F464FF
ID-2: /dev/sda5 maj-min: 8:5 size: 15.38 GiB fs: ext4 label: Ubuntu
uuid: 0ce37a6d-d76f-4599-ae2e-a701a9836721
ID-3: /dev/sda7 maj-min: 8:7 size: 1.79 GiB fs: vfat label: N/A
uuid: 80E5-D996
ID-4: /dev/sda8 maj-min: 8:8 size: 16 MiB fs: <superuser required>
label: N/A uuid: N/A
ID-5: /dev/sdc1 maj-min: 8:33 size: 57.73 GiB fs: exfat label: Linux
uuid: 4E21-0000
ID-6: /dev/sdc2 maj-min: 8:34 size: 32 MiB fs: vfat label: VTOYEFI
uuid: 223C-F3F8
USB:
Hub-1: 1-0:1 info: full speed or root hub ports: 2 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-2: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:8000
class-ID: 0900
Hub-3: 2-0:1 info: full speed or root hub ports: 2 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-4: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 8087:8008
class-ID: 0900
Hub-5: 3-0:1 info: hi-speed hub with single TT ports: 10 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
class-ID: 0900
Hub-6: 3-2:2 info: Hitachi ports: 4 rev: 2.1 speed: 480 Mb/s (57.2 MiB/s)
lanes: 1 mode: 2.0 chip-ID: 045b:0209 class-ID: 0900
Hub-7: 3-2.1:4 info: Hitachi ports: 4 rev: 2.1
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 045b:0209
class-ID: 0900
Device-1: 3-2.1.1:7 info: T & A Mobile Phones TCL TAB 8 LE
type: bluetooth,CDC-data driver: rndis_host,usbfs interfaces: 3 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
chip-ID: 1bbb:0173 class-ID: 0a00 serial: <filter>
Device-2: 3-5:3 info: Logitech Keyboard K120 type: keyboard,HID
driver: hid-generic,usbhid interfaces: 2 rev: 1.1
speed: 1.5 Mb/s (183 KiB/s) lanes: 1 mode: 1.0 power: 90mA
chip-ID: 046d:c31c class-ID: 0300
Device-3: 3-6:5 info: Cambridge Silicon Radio Bluetooth Dongle (HCI mode)
type: bluetooth driver: btusb interfaces: 2 rev: 2.0
speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
chip-ID: 0a12:0001 class-ID: e001
Hub-8: 3-7:8 info: Genesys Logic Hub ports: 4 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 100mA
chip-ID: 05e3:0608 class-ID: 0900
Device-1: 3-8:9 info: Genesys Logic GL827L SD/MMC/MS Flash Card Reader
type: mass storage driver: usb-storage interfaces: 1 rev: 2.0
speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
chip-ID: 05e3:0723 class-ID: 0806
Device-2: 3-10:10 info: Areson Corp 2.4G Wireless Receiver
type: keyboard,mouse driver: hid-generic,usbhid interfaces: 2 rev: 1.1
speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 100mA
chip-ID: 25a7:fa10 class-ID: 0301
Hub-9: 4-0:1 info: super-speed hub ports: 2 rev: 3.0
speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 1d6b:0003
class-ID: 0900
Hub-10: 4-2:2 info: Hitachi ports: 4 rev: 3.0 speed: 5 Gb/s (596.0 MiB/s)
lanes: 1 mode: 3.2 gen-1x1 chip-ID: 045b:0210 class-ID: 0900
Hub-11: 4-2.1:3 info: Hitachi ports: 4 rev: 3.0
speed: 5 Gb/s (596.0 MiB/s) lanes: 1 mode: 3.2 gen-1x1 chip-ID: 045b:0210
class-ID: 0900
Device-1: 4-2.3:4 info: Phison SP Mobile C31 (64GB) type: mass storage
driver: usb-storage interfaces: 1 rev: 3.2 speed: 5 Gb/s (596.0 MiB/s)
lanes: 1 mode: 3.2 gen-1x1 power: 896mA chip-ID: 13fe:6300 class-ID: 0806
serial: <filter>
Sensors:
System Temperatures: cpu: 58.0 C mobo: N/A
Fan Speeds (rpm): N/A
Repos:
Packages: pm: pacman pkgs: 2374 libs: 589 tools: pamac,yay pm: flatpak
pkgs: 0
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https://volico.mm.fcix.net/manjaro/stable/$repo/$arch
2: https://manjaro.kurdy.org/stable/$repo/$arch
3: https://mirrors2.manjaro.org/stable/$repo/$arch
4: https://ohioix.mm.fcix.net/manjaro/stable/$repo/$arch
5: https://forksystems.mm.fcix.net/manjaro/stable/$repo/$arch
6: https://mirrors.manjaro.org/repo/stable/$repo/$arch
7: https://cofractal-ewr.mm.fcix.net/manjaro/stable/$repo/$arch
8: https://repo.ialab.dsu.edu/manjaro/stable/$repo/$arch
9: https://nnenix.mm.fcix.net/manjaro/stable/$repo/$arch
10: https://uvermont.mm.fcix.net/manjaro/stable/$repo/$arch
11: https://nocix.mm.fcix.net/manjaro/stable/$repo/$arch
12: https://coresite.mm.fcix.net/manjaro/stable/$repo/$arch
13: https://mnvoip.mm.fcix.net/manjaro/stable/$repo/$arch
14: http://mirror.fcix.net/manjaro/stable/$repo/$arch
15: https://southfront.mm.fcix.net/manjaro/stable/$repo/$arch
16: https://muug.ca/mirror/manjaro/stable/$repo/$arch
17: https://edgeuno-bog2.mm.fcix.net/manjaro/stable/$repo/$arch
18: https://mirror.xenyth.net/manjaro/stable/$repo/$arch
19: https://ridgewireless.mm.fcix.net/manjaro/stable/$repo/$arch
20: https://codingflyboy.mm.fcix.net/manjaro/stable/$repo/$arch
21: https://opencolo.mm.fcix.net/manjaro/stable/$repo/$arch
22: https://irltoolkit.mm.fcix.net/manjaro/stable/$repo/$arch
23: https://ziply.mm.fcix.net/manjaro/stable/$repo/$arch
24: https://manjaro.mirrors.lavatech.top/stable/$repo/$arch
25: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
26: https://ipng.mm.fcix.net/manjaro/stable/$repo/$arch
27: https://mirrors.ft.uam.es/manjaro/stable/$repo/$arch
28: https://mirror.init7.net/manjaro/stable/$repo/$arch
29: https://ask4.mm.fcix.net/manjaro/stable/$repo/$arch
30: https://ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch
31: https://mirror.raiolanetworks.com/manjaro/stable/$repo/$arch
32: https://manjaro.mirror.wearetriple.com/stable/$repo/$arch
33: https://mirror.math.princeton.edu/pub/manjaro/stable/$repo/$arch
34: https://manjaro.ynh.ovh/stable/$repo/$arch
35: http://manjaro.mirrors.uk2.net/stable/$repo/$arch
36: https://mirror.koddos.net/manjaro/stable/$repo/$arch
37: https://ftp.nluug.nl/pub/os/Linux/distr/manjaro/stable/$repo/$arch
38: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
39: https://mirror.easyname.at/manjaro/stable/$repo/$arch
40: https://mirror.ufam.edu.br/manjaro/stable/$repo/$arch
41: https://mirror.futureweb.be/manjaro/stable/$repo/$arch
42: http://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
43: https://manjaro.ipacct.com/manjaro/stable/$repo/$arch
44: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
45: https://mirror.ufro.cl/manjaro/stable/$repo/$arch
46: https://mirror.funami.tech/manjaro/stable/$repo/$arch
47: https://gsl-syd.mm.fcix.net/manjaro/stable/$repo/$arch
48: https://mirror.csclub.uwaterloo.ca/manjaro/stable/$repo/$arch
49: https://mirrors.up.pt/pub/manjaro/stable/$repo/$arch
50: https://mirror.archlinux.tw/Manjaro/stable/$repo/$arch
51: http://ftp.tsukuba.wide.ad.jp/Linux/manjaro/stable/$repo/$arch
52: https://mirror.2degrees.nz/manjaro/stable/$repo/$arch
53: https://mirror.freedif.org/Manjaro/stable/$repo/$arch
54: https://mirror.telepoint.bg/manjaro/stable/$repo/$arch
55: https://mirror.albony.xyz/manjaro/stable/$repo/$arch
56: http://mirror.is.co.za/mirrors/manjaro.org/stable/$repo/$arch
57: https://mirror.phoepsilonix.love/manjaro/stable/$repo/$arch
Processes:
CPU top: 5 of 279
1: cpu: 99.1% command: QtWebEngineProcess pid: 2479 mem: 319.3 MiB (2.0%)
2: cpu: 56.9% command: falkon pid: 1768 mem: 472.5 MiB (2.9%)
3: cpu: 21.5% command: QtWebEngineProcess pid: 2530 mem: 208.8 MiB (1.3%)
4: cpu: 20.3% command: QtWebEngineProcess pid: 2504 mem: 208.4 MiB (1.3%)
5: cpu: 15.5% command: scrcpy pid: 1815 mem: 113.2 MiB (0.7%)
Memory top: 5 of 279
1: mem: 497.7 MiB (3.1%) command: telegram-desktop pid: 2030 cpu: 0.3%
2: mem: 472.5 MiB (2.9%) command: falkon pid: 1768 cpu: 56.9%
3: mem: 423.5 MiB (2.6%) command: firefox pid: 1775 cpu: 2.4%
4: mem: 319.3 MiB (2.0%) command: QtWebEngineProcess pid: 2479 cpu: 99.1%
5: mem: 208.8 MiB (1.3%) command: QtWebEngineProcess pid: 2530 cpu: 21.5%
Info:
Processes: 279 Power: uptime: 20m states: freeze,standby,mem,disk
suspend: s2idle avail: shallow wakeups: 0 hibernate: platform
avail: shutdown, reboot, suspend, test_resume image: 6.19 GiB
services: upowerd,xfce4-power-manager Init: systemd v: 256
default: graphical tool: systemctl
Compilers: clang: 18.1.8 gcc: 14.2.1 alt: 13 Shell: Bash v: 5.2.32
running-in: xfce4-terminal inxi: 3.3.36
Thanks for the tip on fdisk. file -s /dev/sda4 still shows what I call the correct UUID which agrees with what gparted shows. fdisk is showing what I’ve been calling the wrong UUID. And grub-probe doesn’t even run now. The real cause I think is them being different. Which one is right. I think I can change the UUID in parted or was it gdisk.
[gnuorder-ds81d ~]# grub-probe /dev/sda4
grub-probe: error: failed to get canonical path of `dev'.
[gnuorder-ds81d ~]# pwd
/root
[gnuorder-ds81d ~]# fdisk -l /dev/sda -o +UUID
Disk /dev/sda: 476.94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: Fanxiang S301 51
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 7A8D344F-38A6-4D0B-988C-8E4BD2D4999B
Device Start End Sectors Size Type UUID
/dev/sda1 2048 1050623 1048576 512M EFI System 9129381E-B041-4DE5-BD51-ED963C0DAD3F
/dev/sda2 1050624 3784703 2734080 1.3G Linux filesystem 7D4D6686-1379-49FF-A2FB-7E1A591ED60A
/dev/sda3 3784704 289748991 285964288 136.4G Microsoft basic data 16C37FB7-1D98-4354-A83E-83F0B5C166F1
/dev/sda4 289748992 692854783 403105792 192.2G Linux filesystem 4E18BE9D-1C64-41AF-8E57-E7CA2CF5B6EE
/dev/sda5 901859328 934119423 32260096 15.4G Linux filesystem B336AB75-38FA-4E3D-8FAE-4C8961E8C838
/dev/sda6 934119424 1000214527 66095104 31.5G Linux swap 6536A947-D974-4855-A5BF-5E6F78C978DD
/dev/sda7 692854784 696604671 3749888 1.8G Microsoft basic data F708B1AD-27EA-4C95-8428-276429C47632
/dev/sda8 696604672 696637439 32768 16M Linux filesystem FB665D61-0D49-429B-A720-0E8199C8B80C
Partition table entries are not in disk order.
[gnuorder-ds81d ~]# file -s /dev/sda4
/dev/sda4: BTRFS Filesystem label "Manjaro", sectorsize 4096, nodesize 16384, leafsize 16384, UUID=c29fdc05-ea12-4e06-8421-24cde767c946, 124826017792/206390165504 bytes used, 1 devices
I’d suggest using UUIDS as soon as practical - sudo blkid should find them easily enough.
Although it may be unlikely for the nodes to change, you will likely find yourself in trouble if you boot with another disk connected, or opt to multiboot with another OS (on a separate disk) at a future time.
That is all.
1 Like
I plan to as soon as I sort this out. blkid still doesn’t show the btrfs UUID. File and fdisk show different UUIDs.
This, as of recently, is flagged as an EOL kernel. Run 6.11 if you want the latest.
Ignore grub-probe, it’s little use to most people except to dual boot Windows easily. You fix this by fixing the main issue(s). It is really a mash of bourne shell scripts that I find very finicky. I am surprised it even worked for you before with this setup.
I don’t like changing the actual partition UUID in cases like this unless I know for fact it changed, and I want it back. Are you certain the only reference to that UUID was in fstab? Plus it doesn’t find the root of the problem, which may or may not be solved.
It does. Did you check if your boot was mounted properly once inside the chroot? I know I’ve even run into that, and just had to mount the boot partition before manajro-chroot, even though it should work.
It’s late here.
To clarify, you have booted a live image, then done a sudo lsblk -f, and got the output from there? (And getting on a supported kernel might even help.)
inxi data shows BTRFS root partition /dev/sda4 has 0% free space and no UUID
ID-1: / raw-size: 192.22 GiB size: 192.22 GiB (100.00%)
used: 116.43 GiB (60.6%) fs: btrfs dev: /dev/sda4 maj-min: 8:4 label: N/A
uuid: N/A
/dev/sda1 - vfat /boot/efi - 0.02% free space - uuid: 0C5A-87F5
/dev/sda2 - ext4 /boot - 4.2% free space - uuid: d7c5b3f3-f6a2-46ea-a020-fc5e9aaf918b
/dev/sdb1 - ext4 /home - 1.68% free space - uuid: bfa899b9-f545-4ead-a125-da3138006af5
I would suggest testing if this filesystem has no space left
(even if only 60% is used)
sudo btrfs filesystem usage /
You find good Information about Btrfs in the wiki
I increased it’s size with gparted not long ago. df and gparted both say I have 75G free. So does your suggested command. I am going to have to learn more about btrfs.
[gnuorder@gnuorder-ds81d shared]$ sudo btrfs filesystem usage /
Overall:
Device size: 192.22GiB
Device allocated: 125.64GiB
Device unallocated: 66.58GiB
Device missing: 0.00B
Device slack: 0.00B
Used: 116.20GiB
Free (estimated): 74.95GiB (min: 74.95GiB)
Free (statfs, df): 74.94GiB
Data ratio: 1.00
Metadata ratio: 1.00
Global reserve: 177.06MiB (used: 0.00B)
Multiple profiles: no
Data,single: Size:123.66GiB, Used:115.29GiB (93.23%)
/dev/sda4 123.66GiB
Metadata,single: Size:1.98GiB, Used:933.95MiB (46.14%)
/dev/sda4 1.98GiB
System,single: Size:4.00MiB, Used:64.00KiB (1.56%)
/dev/sda4 4.00MiB
Unallocated:
/dev/sda4 66.58GiB
I’m booted up now but from the live image it looked pretty much like this:
[gnuorder@gnuorder-ds81d ~]$ sudo lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 vfat FAT32 EFI 0C5A-87F5 456.8M 11% /boot/efi
├─sda2 ext4 1.0 Boot d7c5b3f3-f6a2-46ea-a020-fc5e9aaf918b 877.5M 25% /boot
├─sda3 ntfs Windows 10 5208F48108F464FF
├─sda4 74.9G 61% /
├─sda5 ext4 1.0 Ubuntu 0ce37a6d-d76f-4599-ae2e-a701a9836721
└─sda6 swap 1 2c99a5cd-a236-42fc-a710-770a98b1b5b3 [SWAP]
sdb
└─sdb1 ext4 1.0 home bfa899b9-f545-4ead-a125-da3138006af5 100.8G 84% /home
sdc
├─sdc1 exfat 1.0 Linux 4E21-0000
└─sdc2 vfat FAT16 VTOYEFI 223C-F3F8
sdd
From in the chroot I would only get info on fsavail, fsuse, and mountpoint. sda4 has never shown a UUID. Same with blkid. The UUID that is in my fstab is the one I’ve used since installing. I have it commented out now.
How do I upgrade the kernal? I thought pamac did that. I upgraded not long ago using pamac and the gui software manager says I’m up to date.
Edit. Figured out the kernel upgrade. I don’t know if I want to do it now until I get this UUID thing figured out.
I found this which matches my situation. Of course no solution so I joined the redit and will ask. There is a btrfs tool to change the UUID but I’ll hold off on doing that. Also I’ll try the btrfs scrub.
https://www.reddit.com/r/btrfs/comments/v4sxzc/comment/ib8z0sy/
[gnuorder@gnuorder-ds81d ~]$ sudo btrfs scrub start -Bd /
Starting scrub on devid 1
Scrub device /dev/sda4 (id 1) done
Scrub started: Wed Oct 16 15:00:27 2024
Status: finished
Duration: 0:04:33
Total to scrub: 116.20GiB
Rate: 435.86MiB/s
Error summary: csum=2
Corrected: 0
Uncorrectable: 2
Unverified: 0
ERROR: there are 1 uncorrectable errors
BTRFS volumes work much like Apple’s APFS in that the actual available space reported spans all volumes on the disk.
In this case, 75 GB is the amount available to the entire disk; every (BTRFS) volume thus indicates 75 GB because it is shared by all volumes, and not allocated per volume like a conventional filesystem (EXT4, HFS+, for NTFS for example).
To put this in perspective; say you have a 70 GB file; you copy that file to any partition shpwing 75 GB available; when the copy completes, every BTRFS file system on that disk will now show 5 GB available.
I’ve been using APFS for many years, but this concept still confuses me momentarily when moving back and forth between Manjaro and MacOS. 
I’m new to btrfs but I only have the one partition and haven’t added any volumes to it. I understand it also uses compression. I did resize it using gparted to make it larger. I don’t know if gparted also resizes the filesystem.
But when you do, at least you might better understand, if it seems strange at first.
I won’t offer any advice as such, because I’ve never actually used BTRFS myself; I simply understand some of the basics.
If I ever decide to use BTRFS no doubt that will change accordingly.
Cheers.
That’s good to know. I seem to remember gparted giving a warning back when ntfs was fairly new saying you had to use ntfsresize after you resized with gparted.
Having this, without RAID or backups, would make me reinstall. Copy what you need off, and re-create the file system. You can actually see what files are affected in those bad chunks. But it does get a little more on the advanced side of btrfs most people never need. (Using btrfs inspect-internal to translate logical addresses, to inodes, to files.)
Especially given the situation, there’s also the chance of this still being faulty hardware. Btrfs is actually good at catching things like this. If you did remake the file system or reinstall, at least you will know for fact it’s your hardware if it happens again.
1 Like
This should not happen at all ! 
Well I found no answer. I’m going to reformat to ext4.
You had an answer…
There is a serious problem with your data. Yes, it needs to be rebuilt.
Ironically it was the built in btrfs checksumming that caught the problem before it could of have been something worse.
ext4 would have carried on, and had a chance of doing something much worse. (If this was any sort of hardware issue, you will find out soon enough.) But I would advise against it, especially given the circumstances.
1 Like
In the link I gave earlier the method for using chroot with BTRFS is adequately described. If you now finally read that link you will discover the subtle differences between what is needed (for BTRFS) and the method that you used:
How this may have affected the outcome, I can’t say with certainty.
Probably for the best.
Cheers.