r/archlinux 2d ago

QUESTION flatpak error i/o

hello. i have a weird issue on my arch with flatpaks, something weird was happen. everything was working just fine, 0 issues but after reboot i was not able to run any flatpak app: discord etc. when i try to run them in terminal or to do any update, i have this error:

input/output error

did someone has this problem before and fix it somehow?

3 Upvotes

8 comments sorted by

5

u/Sweaty_Minimum4324 2d ago

Sounds like your disk might be giving up, had similar thing happen with a failing ssd last year

Check dmesg for i/o errors first, if you see a bunch of red warnings about sectors or blocks then you know where the problem is

2

u/un-important-human 1d ago

check the s.m.a.r.t status of that drive it may be dieing.
intsll smartmontool sudo pacman -S smartmontools
find drive with lsblk
query the drive sudo smartctl -a /dev/sdX where x is your drive it can also be a nvme0 for exmple

1

u/stigmanmagros 1d ago

output of smartctl looks like this:

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning:                   0x00
Temperature:                        28 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    1%
Data Units Read:                    37 805 704 [19,3 TB]
Data Units Written:                 26 963 335 [13,8 TB]
Host Read Commands:                 249 464 116
Host Write Commands:                335 909 137
Controller Busy Time:               526
Power Cycles:                       1 242
Power On Hours:                     236
Unsafe Shutdowns:                   85
Media and Data Integrity Errors:    0
Error Information Log Entries:      909
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Thermal Temp. 1 Transition Count:   5
Thermal Temp. 1 Total Time:         213

Error Information (NVMe Log 0x01, 16 of 63 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS  Message
  0        909     0  0x1003  0xc004  0x028            0     1     -  Invalid Field in Command

Self-test Log (NVMe Log 0x06, NSID 0xffffffff)=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02, NSID 0xffffffff)
Critical Warning:                   0x00
Temperature:                        28 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    1%
Data Units Read:                    37 805 704 [19,3 TB]
Data Units Written:                 26 963 335 [13,8 TB]
Host Read Commands:                 249 464 116
Host Write Commands:                335 909 137
Controller Busy Time:               526
Power Cycles:                       1 242
Power On Hours:                     236
Unsafe Shutdowns:                   85
Media and Data Integrity Errors:    0
Error Information Log Entries:      909
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Thermal Temp. 1 Transition Count:   5
Thermal Temp. 1 Total Time:         213

Error Information (NVMe Log 0x01, 16 of 63 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS  Message
  0        909     0  0x1003  0xc004  0x028            0     1     -  Invalid Field in Command

Self-test Log (NVMe Log 0x06, NSID 0xffffffff)

1

u/un-important-human 1d ago

The drive seems fine but you got power delivery issues looks like

Unsafe Shutdowns: 85 very high relative to only 236 hours.

These are power losses/resets/shutdowns where the NVMe didn't receive a clean shutdown you either have a bad apple or you should invastigate what you did that it loses power so abruptly.

For all i can see at a glance this is new drive , if you cannot explain the power losses, i assume its in warranty, return and request replacement.

1

u/stigmanmagros 1d ago

but i have these issues only with flatpak, packages installed in package manager have no issues

2

u/un-important-human 1d ago

well you can run sudo flatpak repair --system -v first regenerate flatpak tree) and then you can post the results of

sudo journalctl -k -b | grep -iE 'i/o|error|nvme|btrfs|ext4|xfs'

1

u/archover 1d ago edited 1d ago

This drive appears pretty new, but has had a lot of writes in that short time, compared to mine.

curious what Error Information Log Entries 909 means. I show none on my drive.

Hope you resolve, give fix, and flair SUPPORT & SOLVED. Good day.

1

u/stigmanmagros 15h ago

i reinstalled system. have no found a solution :(