Computer failure troubleshooting on MX Linux after formatting

I have to say I am stumped by what has been happening to my old ASUS desktop.

I used to have it a my mom’s but it stopped booting after Linux Mint upgrades last year. So I brought it home but am just now getting to work on the issues.

I had used an SSD I had on hand when I set it up for her. It lasted maybe 6 months in her home before issues began.

Yesterday, I completely wiped the drive and created a new gpt and then formatted to ext 4 the single partition. Installed MX Linux and thought things were good for about two hours. Then I saw tons of error popups about the drive being full. What???

I only installed, updated and added 3 flatpaks: input-leap for sharing mouse keyboard from other computers and localsend to be able to send docs/images/sound files from other computers to this one.

So I tried again. I ended up installing 3 times before assuming the disk must be bad, as e2fsck gave not only errors about padding but also non-contiguous usage, and saying Y to fix, then running again, same errors appeared.

So new SSD installed this morning with MX Linux. All good for about 4 hours, then I checked disk usage around lunch time and thought, “How can there be 125 GB used with only MX and a couple of flatpaks installed?”

After work, opened the file manager, still no errors like the last ones, but now MX Package installer gave the error could not download list of packages, check your APT sources.

So I used CLI to update and got

Err:4 http://deb.debian.org/debian bookworm InRelease
  Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm_InRelease into data and signature failed
Err:1 http://security.debian.org/debian-security bookworm-security InRelease
  Error writing to file - write (28: No space left on device) [IP: 2a04:4e42:d::644 80]
Get:3 http://mirror.math.princeton.edu/pub/mxlinux/mx/repo bookworm InRelease [25.3 kB]
Err:3 http://mirror.math.princeton.edu/pub/mxlinux/mx/repo bookworm InRelease
  Error writing to file - write (28: No space left on device) [IP: 128.112.18.21 80]
Reading package lists... Error!
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://deb.debian.org/debian bookworm InRelease: Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm_InRelease into data and signature failed
W: Failed to fetch http://deb.debian.org/debian/dists/bookworm-updates/InRelease  Error writing to file - write (28: No space left on device) [IP: 2a04:4e42:d::644 80]
W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease  Splitting up /var/lib/apt/lists/deb.debian.org_debian_dists_bookworm_InRelease into data and signature failed
W: Failed to fetch http://security.debian.org/debian-security/dists/bookworm-security/InRelease  Error writing to file - write (28: No space left on device) [IP: 2a04:4e42:d::644 80]
W: Failed to fetch http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/dists/bookworm/InRelease  Error writing to file - write (28: No space left on device) [IP: 128.112.18.21 80]
W: Some index files failed to download. They have been ignored, or old ones used instead.
E: Write error - write (28: No space left on device)
E: IO Error saving source cache
E: The package lists or status file could not be parsed or opened.

And checking Thunar, File System size 456 GB used.

I am no hardware expert, but I know now it is not the drive. It has to be a cable or the motherboard, something is causing this to happen.

Any ideas on why a simple Linux install would cause the space used to grow exponentially until out of space?

Specs:

System: Kernel: 6.12.8-1-liquorix-amd64 [6.12-10~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0 intel_pstate=disable amd_pstate=disable BOOT_IMAGE=/boot/vmlinuz-6.12.8-1-liquorix-amd64 root=UUID=<filter> ro quiet splash Desktop: Xfce v: 4.20.0 tk: Gtk v: 3.24.38 info: xfce4-panel wm: xfwm v: 4.20.0 vt: 7 dm: LightDM v: 1.32.0 Distro: MX-23.5_ahs_x64 Libretto Jan 12 2025 base: Debian GNU/Linux 12 (bookworm) Machine: Type: Desktop Mobo: ASUSTeK model: M32CD_A_F_K20CD_K31CD v: Rev 1.xx serial: <superuser required> UEFI: American Megatrends v: 1102 date: 04/12/2018 CPU: Info: model: Intel Core i5-6400 bits: 64 type: MCP arch: Skylake-S gen: core 6 level: v3 note: check built: 2015 process: Intel 14nm family: 6 model-id: 0x5E (94) stepping: 3 microcode: 0xF0 Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB L3: 6 MiB desc: 1x6 MiB Speed (MHz): avg: 3100 min/max: 800/2701 boost: enabled scaling: driver: acpi-cpufreq governor: ondemand cores: 1: 3100 2: 3100 3: 3100 4: 3100 bogomips: 21599 Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx Vulnerabilities: Type: gather_data_sampling status: Vulnerable: No microcode Type: itlb_multihit status: KVM: VMX disabled Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT disabled Type: mds mitigation: Clear CPU buffers; SMT disabled Type: meltdown mitigation: PTI Type: mmio_stale_data mitigation: Clear CPU buffers; SMT disabled Type: reg_file_data_sampling status: Not affected Type: retbleed mitigation: IBRS 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: IBRS; IBPB: conditional; STIBP: disabled; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected Type: srbds mitigation: Microcode Type: tsx_async_abort status: Not affected Graphics: Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: Gigabyte driver: nouveau v: kernel non-free: 530.xx+ status: current (as of 2023-03) arch: Pascal code: GP10x process: TSMC 16nm built: 2016-21 pcie: gen: 1 speed: 2.5 GT/s lanes: 4 link-max: gen: 3 speed: 8 GT/s ports: active: HDMI-A-1 empty: DVI-D-1 bus-ID: 01:00.0 chip-ID: 10de:1d01 class-ID: 0300 temp: 30.0 C Display: x11 server: X.Org v: 1.21.1.7 compositor: xfwm v: 4.20.0 driver: X: loaded: modesetting unloaded: fbdev,vesa dri: nouveau gpu: nouveau display-ID: :0.0 screens: 1 Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 509x286mm (20.04x11.26") s-diag: 584mm (22.99") Monitor-1: HDMI-A-1 mapped: HDMI-1 model: Samsung C27F390 serial: <filter> built: 2022 res: 1920x1080 hz: 60 dpi: 82 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 1920x1080 min: 720x400 API: OpenGL v: 4.3 Mesa 24.2.2-1~mx23ahs renderer: NV138 direct-render: Yes Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel alternate: snd_soc_avs bus-ID: 00:1f.3 chip-ID: 8086:a170 class-ID: 0403 Device-2: NVIDIA GP108 High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 4 link-max: gen: 3 speed: 8 GT/s bus-ID: 01:00.1 chip-ID: 10de:0fb8 class-ID: 0403 API: ALSA v: k6.12.8-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl Network: Device-1: Realtek RTL8821AE 802.11ac PCIe Wireless Network Adapter vendor: AzureWave driver: rtl8821ae v: kernel modules: wl pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8821 class-ID: 0280 IF: wlan0 state: up mac: <filter> Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: c000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200 IF: eth0 state: down mac: <filter> Bluetooth: Device-1: IMC Networks Bluetooth Radio type: USB driver: btusb v: 0.8 bus-ID: 1-7:2 chip-ID: 13d3:3414 class-ID: e001 serial: <filter> Report: hciconfig ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 2.1 lmp-v: 4.0 sub-v: a041 hci-v: 4.0 rev: e2f Info: acl-mtu: 820:8 sco-mtu: 255:16 link-policy: rswitch hold sniff park link-mode: peripheral accept service-classes: rendering, capturing, object transfer, audio, telephony Drives: Local Storage: total: 698.73 GiB used: 457.12 GiB (65.4%) SMART Message: Unable to run smartctl. Root privileges required. ID-1: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q scheme: GPT ID-2: /dev/sdb maj-min: 8:16 type: USB vendor: SanDisk model: USB 3.2Gen1 size: 232.97 GiB block-size: physical: 512 B logical: 512 B type: N/A serial: <filter> rev: 1.00 scheme: MBR SMART Message: Unknown USB bridge. Flash drive/Unsupported enclosure? Partition: ID-1: / raw-size: 465.51 GiB size: 457.13 GiB (98.20%) used: 457.12 GiB (100.0%) fs: ext4 dev: /dev/sda2 maj-min: 8:2 ID-2: /boot/efi raw-size: 256 MiB size: 252 MiB (98.46%) used: 274 KiB (0.1%) fs: vfat dev: /dev/sda1 maj-min: 8:1 Swap: Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) ID-1: swap-1 type: file size: 4 GiB used: 0 KiB (0.0%) priority: -2 file: /swap/swap Sensors: System Temperatures: cpu: 38.0 C mobo: N/A gpu: nouveau temp: 30.0 C Fan Speeds (RPM): N/A gpu: nouveau fan: 1714 Repos: Packages: 2149 pm: dpkg pkgs: 2141 libs: 1068 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm pkgs: 0 pm: flatpak pkgs: 8 No active apt repos in: /etc/apt/sources.list Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list 1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware Active apt repos in: /etc/apt/sources.list.d/debian.list 1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware 2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware Active apt repos in: /etc/apt/sources.list.d/mx.list 1: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm main non-free 2: deb http://mirror.math.princeton.edu/pub/mxlinux/mx/repo/ bookworm ahs Info: Processes: 260 Uptime: 9h 39m wakeups: 1 Memory: 15.55 GiB used: 1.38 GiB (8.9%) Init: SysVinit v: 3.06 runlevel: 5 default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12 Client: shell wrapper v: 5.2.15-release inxi: 3.3.26 Boot Mode: UEFI```

I tried installing the MX without AHS and had to install extra stuff for this pc after, so I installed MX 23.5 AHS.

I am at a loss.

Thanks,
Sheila

1 Like

My guess is that MX while running finds some error that leads to eternal error messages in /var/log…

So, you might get a clue by studying what is in /var/log
but first
use du to check which part of the filesystem is increasing… most likely /var but maybe /tmp or maybe something unexpected.

2 Likes

Yep, 446G in /var. /log has the 445 GB. Syslog is too large to open in notepad, should I try it in another app?

Nevermind. I never installed any apps so none to use since none can now be installed.

Maybe from live session?

Thanks
Sheila

2 Likes

Will it open with “head”? That way it might not have to read the whole file. Once you find out who is filling up syslog you can kill that process, or alter it so it writes less often.

2 Likes

Or maybe erase syslog, let it start filling up again, run “top” to see what process is active.

2 Likes

“Head” command, limiting to 100, still a lot to post here. How far should I look?

Sheila

1 Like

Are all 100 entries from the same process?

1 Like

vi will open any size of file
or tail it

You need to look at it
or
there may be some clue in messages or dmesg or any of the logs

1 Like

Here are the 100:

sudo head -n 100 /var/log/syslog
2025-02-11T07:45:01.488988-05:00 mx-asus kernel: Linux version 6.12.8-1-liquorix-amd64 (stevep@mxlinux.org) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 ZEN SMP PREEMPT liquorix 6.12-10~mx23ahs (2025-01-03)
2025-02-11T07:45:01.489029-05:00 mx-asus kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.12.8-1-liquorix-amd64 root=UUID=a5ca5999-5fab-49df-97af-099d46d4a732 ro quiet splash
2025-02-11T07:45:01.489031-05:00 mx-asus kernel: BIOS-provided physical RAM map:
2025-02-11T07:45:01.489031-05:00 mx-asus kernel: BIOS-e820: [mem 0x0000000000000000-0x0000000000057fff] usable
2025-02-11T07:45:01.489032-05:00 mx-asus kernel: BIOS-e820: [mem 0x0000000000058000-0x0000000000058fff] reserved
2025-02-11T07:45:01.489032-05:00 mx-asus kernel: BIOS-e820: [mem 0x0000000000059000-0x000000000009efff] usable
2025-02-11T07:45:01.489032-05:00 mx-asus kernel: BIOS-e820: [mem 0x000000000009f000-0x000000000009ffff] reserved
2025-02-11T07:45:01.489035-05:00 mx-asus kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000086933fff] usable
2025-02-11T07:45:01.489036-05:00 mx-asus kernel: BIOS-e820: [mem 0x0000000086934000-0x0000000086934fff] ACPI NVS
2025-02-11T07:45:01.489036-05:00 mx-asus kernel: BIOS-e820: [mem 0x0000000086935000-0x000000008695efff] reserved
2025-02-11T07:45:01.489039-05:00 mx-asus kernel: BIOS-e820: [mem 0x000000008695f000-0x00000000869a9fff] usable
2025-02-11T07:45:01.489040-05:00 mx-asus kernel: BIOS-e820: [mem 0x00000000869aa000-0x00000000874bafff] reserved
2025-02-11T07:45:01.489040-05:00 mx-asus kernel: BIOS-e820: [mem 0x00000000874bb000-0x000000008cfa4fff] usable
2025-02-11T07:45:01.489042-05:00 mx-asus kernel: BIOS-e820: [mem 0x000000008cfa5000-0x000000008e6abfff] reserved
2025-02-11T07:45:01.489043-05:00 mx-asus kernel: BIOS-e820: [mem 0x000000008e6ac000-0x000000008e6e4fff] ACPI data
2025-02-11T07:45:01.489043-05:00 mx-asus kernel: BIOS-e820: [mem 0x000000008e6e5000-0x000000008f28bfff] ACPI NVS
2025-02-11T07:45:01.489043-05:00 mx-asus kernel: BIOS-e820: [mem 0x000000008f28c000-0x000000008fa8afff] reserved
2025-02-11T07:45:01.489044-05:00 mx-asus kernel: BIOS-e820: [mem 0x000000008fa8b000-0x000000008fafdfff] type 20
2025-02-11T07:45:01.489044-05:00 mx-asus kernel: BIOS-e820: [mem 0x000000008fafe000-0x000000008fafefff] usable
2025-02-11T07:45:01.489046-05:00 mx-asus kernel: BIOS-e820: [mem 0x000000008fb00000-0x000000008fbfffff] reserved
2025-02-11T07:45:01.489047-05:00 mx-asus kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
2025-02-11T07:45:01.489047-05:00 mx-asus kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
2025-02-11T07:45:01.489047-05:00 mx-asus kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
2025-02-11T07:45:01.489048-05:00 mx-asus kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
2025-02-11T07:45:01.489048-05:00 mx-asus kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
2025-02-11T07:45:01.489048-05:00 mx-asus kernel: BIOS-e820: [mem 0x0000000100000000-0x000000046effffff] usable
2025-02-11T07:45:01.489051-05:00 mx-asus kernel: amd_pstate: driver is explicitly disabled
2025-02-11T07:45:01.489051-05:00 mx-asus kernel: NX (Execute Disable) protection: active
2025-02-11T07:45:01.489052-05:00 mx-asus kernel: APIC: Static calls initialized
2025-02-11T07:45:01.489052-05:00 mx-asus kernel: efi: EFI v2.4 by American Megatrends
2025-02-11T07:45:01.489052-05:00 mx-asus kernel: efi: ESRT=0x8f9d0e98 ACPI=0x8e6b8000 ACPI 2.0=0x8e6b8000 SMBIOS=0xf05e0 SMBIOS 3.0=0x8f9ce000 
2025-02-11T07:45:01.489053-05:00 mx-asus kernel: efi: Remove mem39: MMIO range=[0xe0000000-0xefffffff] (256MB) from e820 map
2025-02-11T07:45:01.489055-05:00 mx-asus kernel: e820: remove [mem 0xe0000000-0xefffffff] reserved
2025-02-11T07:45:01.489056-05:00 mx-asus kernel: efi: Not removing mem40: MMIO range=[0xfe000000-0xfe010fff] (68KB) from e820 map
2025-02-11T07:45:01.489056-05:00 mx-asus kernel: efi: Not removing mem41: MMIO range=[0xfec00000-0xfec00fff] (4KB) from e820 map
2025-02-11T07:45:01.489056-05:00 mx-asus kernel: efi: Not removing mem42: MMIO range=[0xfee00000-0xfee00fff] (4KB) from e820 map
2025-02-11T07:45:01.489057-05:00 mx-asus kernel: efi: Remove mem43: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map
2025-02-11T07:45:01.489057-05:00 mx-asus kernel: e820: remove [mem 0xff000000-0xffffffff] reserved
2025-02-11T07:45:01.489057-05:00 mx-asus kernel: SMBIOS 3.0.0 present.
2025-02-11T07:45:01.489060-05:00 mx-asus kernel: DMI: ASUSTeK COMPUTER INC. M32CD_A_F_K20CD_K31CD/M32CD_A_F_K20CD_K31CD, BIOS 1102 04/12/2018
2025-02-11T07:45:01.489060-05:00 mx-asus kernel: DMI: Memory slots populated: 2/2
2025-02-11T07:45:01.489060-05:00 mx-asus kernel: tsc: Detected 2700.000 MHz processor
2025-02-11T07:45:01.489061-05:00 mx-asus kernel: tsc: Detected 2699.909 MHz TSC
2025-02-11T07:45:01.489061-05:00 mx-asus kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
2025-02-11T07:45:01.489061-05:00 mx-asus kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
2025-02-11T07:45:01.489064-05:00 mx-asus kernel: last_pfn = 0x46f000 max_arch_pfn = 0x400000000
2025-02-11T07:45:01.489064-05:00 mx-asus kernel: MTRR map: 4 entries (3 fixed + 1 variable; max 23), built from 10 variable MTRRs
2025-02-11T07:45:01.489064-05:00 mx-asus kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
2025-02-11T07:45:01.489065-05:00 mx-asus kernel: last_pfn = 0x8faff max_arch_pfn = 0x400000000
2025-02-11T07:45:01.489065-05:00 mx-asus kernel: found SMP MP-table at [mem 0x000fcc80-0x000fcc8f]
2025-02-11T07:45:01.489065-05:00 mx-asus kernel: esrt: Reserving ESRT space from 0x000000008f9d0e98 to 0x000000008f9d0ed0.
2025-02-11T07:45:01.489068-05:00 mx-asus kernel: Using GB pages for direct mapping
2025-02-11T07:45:01.489068-05:00 mx-asus kernel: Secure boot disabled
2025-02-11T07:45:01.489068-05:00 mx-asus kernel: RAMDISK: [mem 0x2767d000-0x2fb35fff]
2025-02-11T07:45:01.489069-05:00 mx-asus kernel: ACPI: Early table checksum verification disabled
2025-02-11T07:45:01.489069-05:00 mx-asus kernel: ACPI: RSDP 0x000000008E6B8000 000024 (v02 ALASKA)
2025-02-11T07:45:01.489069-05:00 mx-asus kernel: ACPI: XSDT 0x000000008E6B80A8 0000CC (v01 _ASUS_ Desktop  01072009 AMI  00010013)
2025-02-11T07:45:01.489070-05:00 mx-asus kernel: ACPI: FACP 0x000000008E6DA378 00010C (v05 ALASKA A M I    01072009 AMI  00010013)
2025-02-11T07:45:01.489085-05:00 mx-asus kernel: ACPI: DSDT 0x000000008E6B8200 022174 (v02 ALASKA A M I    01072009 INTL 20120913)
2025-02-11T07:45:01.489086-05:00 mx-asus kernel: ACPI: FACS 0x000000008F28BF80 000040
2025-02-11T07:45:01.489086-05:00 mx-asus kernel: ACPI: APIC 0x000000008E6DA488 000084 (v03 ALASKA A M I    01072009 AMI  00010013)
2025-02-11T07:45:01.489086-05:00 mx-asus kernel: ACPI: FPDT 0x000000008E6DA510 000044 (v01 ALASKA A M I    01072009 AMI  00010013)
2025-02-11T07:45:01.489087-05:00 mx-asus kernel: ACPI: FIDT 0x000000008E6DA558 00009C (v01 ALASKA A M I    01072009 AMI  00010013)
2025-02-11T07:45:01.489087-05:00 mx-asus kernel: ACPI: MCFG 0x000000008E6DA5F8 00003C (v01 ALASKA A M I    01072009 MSFT 00000097)
2025-02-11T07:45:01.489089-05:00 mx-asus kernel: ACPI: HPET 0x000000008E6DA638 000038 (v01 ALASKA A M I    01072009 AMI. 0005000B)
2025-02-11T07:45:01.489090-05:00 mx-asus kernel: ACPI: SSDT 0x000000008E6DA670 00036D (v01 SataRe SataTabl 00001000 INTL 20120913)
2025-02-11T07:45:01.489090-05:00 mx-asus kernel: ACPI: LPIT 0x000000008E6DA9E0 000094 (v01 INTEL  SKL      00000000 MSFT 0000005F)
2025-02-11T07:45:01.489090-05:00 mx-asus kernel: ACPI: SSDT 0x000000008E6DAA78 000248 (v02 INTEL  sensrhub 00000000 INTL 20120913)
2025-02-11T07:45:01.489091-05:00 mx-asus kernel: ACPI: SSDT 0x000000008E6DACC0 002BAE (v02 INTEL  PtidDevc 00001000 INTL 20120913)
2025-02-11T07:45:01.489091-05:00 mx-asus kernel: ACPI: SSDT 0x000000008E6DD870 000BE3 (v02 INTEL  Ther_Rvp 00001000 INTL 20120913)
2025-02-11T07:45:01.489091-05:00 mx-asus kernel: ACPI: SSDT 0x000000008E6DE458 00002B (v02 INTEL  UsbCTabl 00001000 INTL 20120913)
2025-02-11T07:45:01.489094-05:00 mx-asus kernel: ACPI: DBGP 0x000000008E6DE488 000034 (v01 INTEL           00000000 MSFT 0000005F)
2025-02-11T07:45:01.489094-05:00 mx-asus kernel: ACPI: DBG2 0x000000008E6DE4C0 000054 (v00 INTEL           00000000 MSFT 0000005F)
2025-02-11T07:45:01.489094-05:00 mx-asus kernel: ACPI: SSDT 0x000000008E6DE518 00071D (v02 INTEL  xh_rvp08 00000000 INTL 20120913)
2025-02-11T07:45:01.489095-05:00 mx-asus kernel: ACPI: SSDT 0x000000008E6DEC38 005359 (v02 SaSsdt SaSsdt   00003000 INTL 20120913)
2025-02-11T07:45:01.489095-05:00 mx-asus kernel: ACPI: UEFI 0x000000008E6E3F98 000042 (v01                 00000000      00000000)
2025-02-11T07:45:01.489095-05:00 mx-asus kernel: ACPI: SSDT 0x000000008E6E3FE0 000E73 (v02 CpuRef CpuSsdt  00003000 INTL 20120913)
2025-02-11T07:45:01.489098-05:00 mx-asus kernel: ACPI: MSDM 0x000000008E6E4E58 000055 (v01 _ASUS_ Desktop  00000001 MSFT 00000000)
2025-02-11T07:45:01.489098-05:00 mx-asus kernel: ACPI: BGRT 0x000000008E6E4EB0 000038 (v01 ALASKA A M I    01072009 AMI  00010013)
2025-02-11T07:45:01.489098-05:00 mx-asus kernel: ACPI: DMAR 0x000000008E6E4EE8 000078 (v01 INTEL  SKL      00000001 INTL 00000001)
2025-02-11T07:45:01.489099-05:00 mx-asus kernel: ACPI: Reserving FACP table memory at [mem 0x8e6da378-0x8e6da483]
2025-02-11T07:45:01.489099-05:00 mx-asus kernel: ACPI: Reserving DSDT table memory at [mem 0x8e6b8200-0x8e6da373]
2025-02-11T07:45:01.489099-05:00 mx-asus kernel: ACPI: Reserving FACS table memory at [mem 0x8f28bf80-0x8f28bfbf]
2025-02-11T07:45:01.489102-05:00 mx-asus kernel: ACPI: Reserving APIC table memory at [mem 0x8e6da488-0x8e6da50b]
2025-02-11T07:45:01.489102-05:00 mx-asus kernel: ACPI: Reserving FPDT table memory at [mem 0x8e6da510-0x8e6da553]
2025-02-11T07:45:01.489102-05:00 mx-asus kernel: ACPI: Reserving FIDT table memory at [mem 0x8e6da558-0x8e6da5f3]
2025-02-11T07:45:01.489103-05:00 mx-asus kernel: ACPI: Reserving MCFG table memory at [mem 0x8e6da5f8-0x8e6da633]
2025-02-11T07:45:01.489103-05:00 mx-asus kernel: ACPI: Reserving HPET table memory at [mem 0x8e6da638-0x8e6da66f]
2025-02-11T07:45:01.489103-05:00 mx-asus kernel: ACPI: Reserving SSDT table memory at [mem 0x8e6da670-0x8e6da9dc]
2025-02-11T07:45:01.489104-05:00 mx-asus kernel: ACPI: Reserving LPIT table memory at [mem 0x8e6da9e0-0x8e6daa73]
2025-02-11T07:45:01.489106-05:00 mx-asus kernel: ACPI: Reserving SSDT table memory at [mem 0x8e6daa78-0x8e6dacbf]
2025-02-11T07:45:01.489107-05:00 mx-asus kernel: ACPI: Reserving SSDT table memory at [mem 0x8e6dacc0-0x8e6dd86d]
2025-02-11T07:45:01.489107-05:00 mx-asus kernel: ACPI: Reserving SSDT table memory at [mem 0x8e6dd870-0x8e6de452]
2025-02-11T07:45:01.489107-05:00 mx-asus kernel: ACPI: Reserving SSDT table memory at [mem 0x8e6de458-0x8e6de482]
2025-02-11T07:45:01.489108-05:00 mx-asus kernel: ACPI: Reserving DBGP table memory at [mem 0x8e6de488-0x8e6de4bb]
2025-02-11T07:45:01.489108-05:00 mx-asus kernel: ACPI: Reserving DBG2 table memory at [mem 0x8e6de4c0-0x8e6de513]
2025-02-11T07:45:01.489110-05:00 mx-asus kernel: ACPI: Reserving SSDT table memory at [mem 0x8e6de518-0x8e6dec34]
2025-02-11T07:45:01.489110-05:00 mx-asus kernel: ACPI: Reserving SSDT table memory at [mem 0x8e6dec38-0x8e6e3f90]
2025-02-11T07:45:01.489111-05:00 mx-asus kernel: ACPI: Reserving UEFI table memory at [mem 0x8e6e3f98-0x8e6e3fd9]
2025-02-11T07:45:01.489111-05:00 mx-asus kernel: ACPI: Reserving SSDT table memory at [mem 0x8e6e3fe0-0x8e6e4e52]
1 Like

Vi:


(1) Another program may be editing the same file.  If this is the case,
    be careful not to end up with two different instances of the same
    file when making changes.  Quit, or continue with caution.
(2) An edit session for this file crashed.
    If this is the case, use ":recover" or "vim -r syslog"
    to recover the changes (see ":help recovery").
    If you did this already, delete the swap file "/var/tmp/syslog.swp"
    to avoid this message.

E325: ATTENTION
Found a swap file by the name "/tmp/syslog.swp"
          owned by: root   dated: Tue Feb 11 18:32:01 2025
         [cannot be read]
While opening file "syslog"
             dated: Tue Feb 11 18:35:03 2025
      NEWER than swap file!

(1) Another program may be editing the same file.  If this is the case,
    be careful not to end up with two different instances of the same
    file when making changes.  Quit, or continue with caution.
(2) An edit session for this file crashed.
    If this is the case, use ":recover" or "vim -r syslog"
    to recover the changes (see ":help recovery").
    If you did this already, delete the swap file "/tmp/syslog.swp"
    to avoid this message.

"syslog"

I have no idea what any of that means.

Sheila

1 Like

I looked at the first 100 entries in the syslog on this laptop and the notable difference is that not all of them came from the kernel, as yours appear to be. Maybe the kernel is stuck trying to initialize things but unable to complete the process.

Does this problem happen if you do a live-boot of another OS?

1 Like

This is the last part of dmesg. Not sure how much before this might matter, but did not want to post that entire file–long!

[    1.778044] Freeing initrd memory: 135908K
[    1.793932] Segment Routing with IPv6
[    1.793936] RPL Segment Routing with IPv6
[    1.793955] In-situ OAM (IOAM) with IPv6
[    1.794074] Key type dns_resolver registered
[    1.794486] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[    1.794602] microcode: Current revision: 0x000000f0
[    1.794605] microcode: Updated early from: 0x000000c2
[    1.794762] IPI shorthand broadcast: enabled
[    1.797513] sched_clock: Marking stable (1793001973, 3717588)->(1800326387, -3606826)
[    1.797706] registered taskstats version 1
[    1.797919] Loading compiled-in X.509 certificates
[    1.800780] Demotion targets for Node 0: null
[    1.800869] Key type .fscrypt registered
[    1.800874] Key type fscrypt-provisioning registered
[    1.806758] RAS: Correctable Errors collector initialized.
[    1.820176] clk: Disabling unused clocks
[    1.820178] PM: genpd: Disabling unused power domains
[    1.821032] Freeing unused decrypted memory: 2028K
[    1.821498] Freeing unused kernel image (initmem) memory: 3628K
[    1.821569] Write protecting the kernel read-only data: 30720k
[    1.822128] Freeing unused kernel image (rodata/data gap) memory: 776K
[    1.822168] Run /init as init process
[    1.822169]   with arguments:
[    1.822170]     /init
[    1.822171]     splash
[    1.822184]   with environment:
[    1.822185]     HOME=/
[    1.822185]     TERM=linux
[    1.822186]     BOOT_IMAGE=/boot/vmlinuz-6.12.8-1-liquorix-amd64
[    2.007612] usb-storage 4-2:1.0: USB Mass Storage device detected
[    2.008024] scsi host4: usb-storage 4-2:1.0
[    2.008109] usbcore: registered new interface driver usb-storage
[    2.008131] ACPI: bus type drm_connector registered
[    2.008682] cryptd: max_cpu_qlen set to 1000
[    2.009097] input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/0003:046D:C077.0001/input/input3
[    2.009141] hid-generic 0003:046D:C077.0001: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:14.0-9/input0
[    2.009579] i801_smbus 0000:00:1f.4: SPD Write Disable is set
[    2.009606] i801_smbus 0000:00:1f.4: SMBus using PCI interrupt
[    2.009678] usbcore: registered new interface driver uas
[    2.010933] i2c i2c-0: Successfully instantiated SPD at 0x50
[    2.011562] input: Logitech USB Keyboard as /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.0/0003:046D:C31C.0002/input/input4
[    2.013991] AES CTR mode by8 optimization enabled
[    2.018183] r8169 0000:04:00.0 eth0: RTL8168g/8111g, d0:17:c2:ae:e6:97, XID 4c0, IRQ 136
[    2.018188] r8169 0000:04:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]
[    2.021584] Linux agpgart interface v0.103
[    2.027764] sr 2:0:0:0: [sr0] scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray
[    2.027782] cdrom: Uniform CD-ROM driver Revision: 3.20
[    2.046913] sr 2:0:0:0: Attached scsi CD-ROM sr0
[    2.095016] hid-generic 0003:046D:C31C.0002: input,hidraw1: USB HID v1.10 Keyboard [Logitech USB Keyboard] on usb-0000:00:14.0-10/input0
[    2.099454] input: Logitech USB Keyboard Consumer Control as /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:046D:C31C.0003/input/input5
[    2.149931] input: Logitech USB Keyboard System Control as /devices/pci0000:00/0000:00:14.0/usb1/1-10/1-10:1.1/0003:046D:C31C.0003/input/input6
[    2.150155] hid-generic 0003:046D:C31C.0003: input,hidraw2: USB HID v1.10 Device [Logitech USB Keyboard] on usb-0000:00:14.0-10/input1
[    2.150222] usbcore: registered new interface driver usbhid
[    2.150223] usbhid: USB HID core driver
[    2.269952] MXM: GUID detected in BIOS
[    2.270044] ACPI: \_SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM
[    2.270138] nouveau 0000:01:00.0: NVIDIA GP108 (138000a1)
[    2.380936] nouveau 0000:01:00.0: bios: version 86.08.17.00.70
[    2.381092] nouveau 0000:01:00.0: pmu: firmware unavailable
[    2.381607] Console: switching to colour dummy device 80x25
[    2.381636] nouveau 0000:01:00.0: vgaarb: deactivate vga console
[    2.381761] nouveau 0000:01:00.0: bios: M0203E type 04
[    2.381764] nouveau 0000:01:00.0: fb: 2048 MiB of unknown memory type
[    2.393536] nouveau 0000:01:00.0: drm: VRAM: 2048 MiB
[    2.393539] nouveau 0000:01:00.0: drm: GART: 536870912 MiB
[    2.393541] nouveau 0000:01:00.0: drm: BIT table 'A' not found
[    2.393543] nouveau 0000:01:00.0: drm: BIT table 'L' not found
[    2.393544] nouveau 0000:01:00.0: drm: TMDS table version 2.0
[    2.396840] nouveau 0000:01:00.0: drm: MM: using COPY for buffer copies
[    2.436122] [drm] Initialized nouveau 1.4.0 for 0000:01:00.0 on minor 0
[    2.504492] fbcon: nouveaudrmfb (fb0) is primary device
[    2.551149] Console: switching to colour frame buffer device 240x67
[    2.553527] nouveau 0000:01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
[    2.562760] nouveau 0000:01:00.0: drm: Disabling PCI power management to avoid bug
[    2.594236] raid6: skipped pq benchmark and selected avx2x4
[    2.594239] raid6: using avx2x2 recovery algorithm
[    2.594463] xor: automatically using best checksumming function   avx       
[    2.594627] async_tx: api initialized (async)
[    3.067802] scsi 4:0:0:0: Direct-Access      USB      SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6
[    3.076917] sd 4:0:0:0: [sdb] 488570880 512-byte logical blocks: (250 GB/233 GiB)
[    3.079075] sd 4:0:0:0: [sdb] Write Protect is off
[    3.079077] sd 4:0:0:0: [sdb] Mode Sense: 43 00 00 00
[    3.080325] sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[    3.099910]  sdb: sdb1 sdb2
[    3.100054] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[    3.965818] Btrfs loaded, assert=on, zoned=yes, fsverity=yes
[    4.180034] EXT4-fs (sda2): mounted filesystem a5ca5999-5fab-49df-97af-099d46d4a732 ro with ordered data mode. Quota mode: none.
[    4.660055] intel_pmc_core INT33A1:00:  initialized
[    4.685230] EDAC ie31200: No ECC support
[    4.703232] mei_me 0000:00:16.0: enabling device (0000 -> 0002)
[    4.703426] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    4.704066] iTCO_vendor_support: vendor-support=0
[    4.704250] sr 2:0:0:0: Attached scsi generic sg1 type 5
[    4.705877] ee1004 0-0050: 512 byte EE1004-compliant SPD EEPROM, read-only
[    4.707997] sd 4:0:0:0: Attached scsi generic sg2 type 0
[    4.715558] iTCO_wdt iTCO_wdt: Found a Intel PCH TCO device (Version=4, TCOBASE=0x0400)
[    4.718944] iTCO_wdt iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[    4.800169] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    4.816147] Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    4.816353] Loaded X.509 cert 'wens: 61c038651aabdcf94bd0ac7ff06c7248db18c600'
[    4.819075] cfg80211: loaded regulatory.db is malformed or signature is missing/invalid
[    4.850880] asus_wmi: ASUS WMI generic driver loaded
[    4.870057] asus_wmi: Initialization: 0x0
[    4.870080] asus_wmi: BIOS WMI version: 0.9
[    4.870113] asus_wmi: SFUN value: 0x0
[    4.870115] eeepc-wmi eeepc-wmi: Detected ASUSWMI, use DCTS
[    4.872108] input: Eee PC WMI hotkeys as /devices/platform/eeepc-wmi/input/input7
[    4.906026] intel_tcc_cooling: Programmable TCC Offset detected
[    4.908692] snd_hda_intel 0000:01:00.1: Disabling MSI
[    4.908698] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client
[    4.909023] intel_rapl_common: Found RAPL domain package
[    4.909025] intel_rapl_common: Found RAPL domain core
[    4.909027] intel_rapl_common: Found RAPL domain dram
[    4.931421] rtl8821ae 0000:03:00.0: enabling device (0000 -> 0003)
[    4.934542] snd_hda_intel 0000:01:00.1: bound 0000:01:00.0 (ops nv50_audio_component_bind_ops [nouveau])
[    4.937607] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input8
[    4.937648] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input9
[    4.937684] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input10
[    4.937714] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input11
[    4.942426] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC887-VD: line_outs=4 (0x14/0x15/0x16/0x17/0x0) type:line
[    4.942431] snd_hda_codec_realtek hdaudioC0D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
[    4.942434] snd_hda_codec_realtek hdaudioC0D0:    hp_outs=1 (0x19/0x0/0x0/0x0/0x0)
[    4.942435] snd_hda_codec_realtek hdaudioC0D0:    mono: mono_out=0x0
[    4.942437] snd_hda_codec_realtek hdaudioC0D0:    dig-out=0x11/0x0
[    4.942438] snd_hda_codec_realtek hdaudioC0D0:    inputs:
[    4.942439] snd_hda_codec_realtek hdaudioC0D0:      Front Mic=0x1b
[    4.942441] snd_hda_codec_realtek hdaudioC0D0:      Rear Mic=0x18
[    4.942442] snd_hda_codec_realtek hdaudioC0D0:      Line=0x1a
[    4.949607] rtl8821ae: Using firmware rtlwifi/rtl8821aefw_29.bin
[    4.949612] rtl8821ae: Using firmware rtlwifi/rtl8821aefw_wowlan.bin
[    4.953148] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[    4.953489] rtlwifi: rtlwifi: wireless switch is on
[    4.958416] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input12
[    4.958455] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1f.3/sound/card0/input13
[    4.958489] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1f.3/sound/card0/input14
[    4.958521] input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1f.3/sound/card0/input15
[    4.958552] input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1f.3/sound/card0/input16
[    4.958584] input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1f.3/sound/card0/input17
[    4.958616] input: HDA Intel PCH Line Out Side as /devices/pci0000:00/0000:00:1f.3/sound/card0/input18
[    4.958645] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1f.3/sound/card0/input19
[    4.987485] wl: loading out-of-tree module taints kernel.
[    4.987490] wl: module license 'MIXED/Proprietary' taints kernel.
[    4.987491] Disabling lock debugging due to kernel taint
[    4.987492] wl: module license taints kernel.
[    5.892328] mousedev: PS/2 mouse device common for all mice
[    5.916457] Bluetooth: Core ver 2.22
[    5.916472] NET: Registered PF_BLUETOOTH protocol family
[    5.916474] Bluetooth: HCI device and connection manager initialized
[    5.916477] Bluetooth: HCI socket layer initialized
[    5.916478] Bluetooth: L2CAP socket layer initialized
[    5.916480] Bluetooth: SCO socket layer initialized
[    6.016916] usbcore: registered new interface driver btusb
[    6.257069] Bluetooth: hci0: RTL: examining hci_ver=06 hci_rev=000a lmp_ver=06 lmp_subver=8821
[    6.258064] Bluetooth: hci0: RTL: rom_version status=0 version=1
[    6.258080] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821a_fw.bin
[    6.258575] Bluetooth: hci0: RTL: loading rtl_bt/rtl8821a_config.bin
[    6.258722] Bluetooth: hci0: RTL: cfg_sz 10, total sz 17438
[    6.543089] EXT4-fs (sda2): re-mounted a5ca5999-5fab-49df-97af-099d46d4a732 r/w. Quota mode: none.
[    6.714966] lp: driver loaded but no devices found
[    6.719644] ppdev: user-space parallel port driver
[    6.723506] FAT-fs (sda1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[    6.733801] loop: module loaded
[    6.768786] Adding 4194300k swap on /swap/swap.  Priority:-2 extents:20 across:445775872k SS
[    6.900601] networking done
[    7.007408] RPC: Registered named UNIX socket transport module.
[    7.007410] RPC: Registered udp transport module.
[    7.007411] RPC: Registered tcp transport module.
[    7.007411] RPC: Registered tcp-with-tls transport module.
[    7.007412] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    7.023557] netfs: FS-Cache loaded
[    7.047079] Bluetooth: hci0: RTL: fw version 0x0e2fa041

I cannot believe the system is even usuable with 100% desk usage. But it is. Next I can try to empty the syslog, but I do not know how to watch what happens then to repeat the issue causing errors.

Sheila

1 Like

The problem is not instant. As I said, it took about 5 hours for me to check it and note that the disk usage had gone from minmal to 140 GB then about 4 hours later it was full.

How would running a live session without installing anything (or do I need to) have the same issue with filling up the drive?

Thanks,
Sheila

1 Like

Vi detects that some other process is writing on the file.
Vi was a bad idea, drop it.

2 Likes

You’re right, a live boot won’t help. You’d have to install a different OS on the disk to do what I was suggesting. My mistake.

1 Like

I don’t care to install another OS, same or different one, I have them all on flash drive. I just do not know how to assess it once reinstalled or if it is even necessary considering there is no slowdown in using the current system. Do I delete syslog and it will auto regenerate and then look at it?

Sorry, this is beyond my scope of knowledge.

Sheila

1 Like

cat /dev/null >syslog
That makes an empty file… better than deleting it.

I hope you are using normal MX ( ie not MXahs)
That older desktop does not need ahs, and it may even cause trouble.

You have to identify the process writing these excessive messages.

1 Like

You probably missed it but I installed MX non-AHS, even though I have a new Nvidia graphics card installed, it is an i-5 processor, but then MX had to keep installing new things to work the newer hardware. So next try, I did install AHS. You want me to install it again?

Let me remove the syslog and report back first.

Sheila

1 Like

I don’t think it worked. I checked and it is still 225 GB and cat the log is still running.

1 Like

I finally killed it as it kept writing the same error over and over at current timestamp:

2025-02-11T07:45:54.578397-05:00 mx-asus kernel: pcieport 0000:00:1c.6: AER: Correctable error message received from 0000:00:1c.6
2025-02-11T07:45:54.578397-05:00 mx-asus kernel: pcieport 0000:00:1c.6: AER: found no error details for 0000:00:1c.6
2025-02-11T07:45:54.578398-05:00 mx-asus kernel: pcieport 0000:00:1c.6: AER: Correctable error message received from 0000:00:1c.6
2025-02-11T07:45:54.578398-05:00 mx-asus kernel: pcieport 0000:00:1c.6: PCIe Bus Error: severity=Correctable, type=Physical Layer, (Receiver ID)
2025-02-11T07:45:54.578398-05:00 mx-asus kernel: pcieport 0000:00:1c.6:   device [8086:a116] error status/mask=00000001/00002000
2025-02-11T07:45:54.578399-05:00 mx-asus kernel: pcieport 0000:00:1c.6:    [ 0] RxErr                 
2025-0
1 Like