Read only file system

gautier-andreotti · January 19, 2026, 4:43pm

Ubuntu Version: 25.10

File system

Because of a video driver issue I have to hard reset (switch off) my system and change the Bios primary display to my integrated video adapter. After a normal restart when performing an

sudo apt-get update

I receive warning on various files telling me it is a read ony file system

apt-get update
Hit:1 http://ch.archive.ubuntu.com/ubuntu questing InRelease
Hit:2 http://ch.archive.ubuntu.com/ubuntu questing-updates InRelease
Hit:3 http://ch.archive.ubuntu.com/ubuntu questing-backports InRelease
Ign:4 http://security.ubuntu.com/ubuntu questing-security InRelease
Err:5 Index of /ubuntu questing-security Release
Could not open file /var/lib/apt/lists/partial/security.ubuntu.com_ubuntu_dists_questing-security_Release - open (30: Read-only file system) [IP: 2a06:bc80:0:1000::16 80]
Reading package lists… Done
W: chown to _apt:root of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (30: Read-only file system)
W: chmod 0700 of directory /var/lib/apt/lists/partial failed - SetupAPTPartialDirectory (30: Read-only file system)
W: chown to _apt:root of directory /var/lib/apt/lists/auxfiles failed - SetupAPTPartialDirectory (30: Read-only file system)
W: chmod 0755 of directory /var/lib/apt/lists/auxfiles failed - SetupAPTPartialDirectory (30: Read-only file system)
W: Not using locking for read only lock file /var/lib/apt/lists/lock
W: chown to _apt:root of file /var/lib/apt/lists/ch.archive.ubuntu.com_ubuntu_dists_questing_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chmod 0600 of file /var/lib/apt/lists/ch.archive.ubuntu.com_ubuntu_dists_questing_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chown to root:root of file /var/lib/apt/lists/ch.archive.ubuntu.com_ubuntu_dists_questing_InRelease failed - 201::URIDone (30: Read-only file system)
W: chmod 0644 of file /var/lib/apt/lists/ch.archive.ubuntu.com_ubuntu_dists_questing_InRelease failed - 201::URIDone (30: Read-only file system)
W: chown to _apt:root of file /var/lib/apt/lists/ch.archive.ubuntu.com_ubuntu_dists_questing-updates_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chmod 0600 of file /var/lib/apt/lists/ch.archive.ubuntu.com_ubuntu_dists_questing-updates_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chown to root:root of file /var/lib/apt/lists/ch.archive.ubuntu.com_ubuntu_dists_questing-updates_InRelease failed - 201::URIDone (30: Read-only file system)
W: chmod 0644 of file /var/lib/apt/lists/ch.archive.ubuntu.com_ubuntu_dists_questing-updates_InRelease failed - 201::URIDone (30: Read-only file system)
W: chown to _apt:root of file /var/lib/apt/lists/ch.archive.ubuntu.com_ubuntu_dists_questing-backports_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chmod 0600 of file /var/lib/apt/lists/ch.archive.ubuntu.com_ubuntu_dists_questing-backports_InRelease failed - Item::QueueURI (30: Read-only file system)
W: chown to root:root of file /var/lib/apt/lists/ch.archive.ubuntu.com_ubuntu_dists_questing-backports_InRelease failed - 201::URIDone (30: Read-only file system)
W: chmod 0644 of file /var/lib/apt/lists/ch.archive.ubuntu.com_ubuntu_dists_questing-backports_InRelease failed - 201::URIDone (30: Read-only file system)
E: The repository ‘ Index of /ubuntu questing-security Release’ no longer has a Release file.
N: Updating from such a repository can’t be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: Problem unlinking the file /var/cache/apt/pkgcache.bin - RemoveCaches (30: Read-only file system)
W: Problem unlinking the file /var/cache/apt/srcpkgcache.bin - RemoveCaches (30: Read-only file system)
W: Problem unlinking the file /var/cache/apt/pkgcache.bin.bCw2id - RemoveCaches (30: Read-only file system)
W: Problem unlinking the file /var/cache/apt/pkgcache.bin.FI3L6e - RemoveCaches (30: Read-only file system)

I perform a fsck on the volume, no error, check the SSD with smartctl, passed with flying colors. I used the live CD to check the disk and I have no issue writing the disk like this, but each time I boot on it tells me this Read-Only

I tried

sudo mount -o remount /

no error but no joy.

dmesg is full off message about failure to write systemd-journal because of a read-only file system. The timestamp on the logs show they have been modified at the time of the last reboot.

Any help?

Thanks

Actionparsnip · January 19, 2026, 4:57pm

What is the output of:

df -h

Thanks

gautier-andreotti · January 19, 2026, 5:21pm

df -h
Filesystem      Size  Used Avail Use% Mounted on
tmpfs           3.1G  2.6M  3.1G   1% /run
/dev/sdb2       916G   85G  785G  10% /
tmpfs            16G  8.0K   16G   1% /dev/shm
tmpfs           5.0M   16K  5.0M   1% /run/lock
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-journald.service
tmpfs            16G  308K   16G   1% /tmp
tmpfs           1.0M     0  1.0M   0% /run/credentials/systemd-resolved.service
tmpfs           3.1G   96K  3.1G   1% /run/user/1000

Thanks

Actionparsnip · January 19, 2026, 6:35pm

OK so it’s a simple disk setup. If you boot to Ubuntu live USB/CD environment, then you can run an fsck on the file systems to make sure they are healthy. Then reboot, remove the extra boot media and boot as normal

tea-for-one · January 19, 2026, 6:40pm

Is your ESP on a separate disk?
If so, you should run fsck (in a “Try Ubuntu” live session) on the ESP also.

gautier-andreotti · January 19, 2026, 7:39pm

Thanks for your reply.

As mentionned I did a fsck, but each time I restart the system on this boot drive, disks errors came back when I redo the fsck from the Live CD. My conclusion is that the SSD is probably failing.

If you do not have any other suggestion I will close this post

gautier-andreotti · January 19, 2026, 7:40pm

Thanks for your reply.

As mentionned I did a fsck, but each time I restart the system on this boot drive, disks errors came back when I redo the fsck from the Live session. My conclusion is that the SSD is probably failing.

If you do not have any other suggestion I will close this post

guiverc · January 19, 2026, 10:36pm

If problems are detected by the system, a RW (read write) mounted file-system is flipped to RO (read only) to prevent further corruption. It’s usually best to explore this from live media in my experience; with clues usually found in system logs (dmesg or journalctl though that is easiest to explore before rebooting into the live media).

The first thing I do is check health of drive; using it’s inbuilt SMART technology; introduced back in the 90s for hard disks, but also exists on almost all SSDs. It’s where I’d explore the health of the drive; doing that exploration from live media so the disk isn’t trying to be used during your exploration.

If you’ve been using the 6.17 kernel (with Ubuntu 25.10) for some time, I’d not expect any kernel module related issue as being the cause; HOWEVER you do mention video driver issue specifically, but without details. Whilst I’d not expect the kernel module (video driver) issue to call drive issues; it is possible. I’d likely explore that from live media too.

gautier-andreotti · January 20, 2026, 3:50pm

Thanks for your reply.

The system was working initially, then when starting Steam I got a message about 32 bits Nvidia driver was not installed, and in the same message recommanded me to install some nvidia driver, such I did (the libnvidia-gl-580). I don’t know why I got this Nvdia message the Nvidia driver 580 was the one installed and was working previously. Steam was still not working, then I rebooted and the system stops on the Ubuntu loading screen. At this stage with no access to anything visible I have to switch off the system, restarted it with the same result and switched it off again. I went to the Bios, change the initial video adater to the integrated one and got access back to Ubuntu. Then the disk issues started.

I tested the disk with the Live session using:

sudo smartctl -x /dev/sdb2

It is a bit more comprehensive than the Disk GUI (reporting no error) . Result below, some crc error but it seems ok. So it could be the disk, the disk controler, the cables, the power supply or Linux. But the error I detect with fsck after each boot seems very similar each time, so I doubt the controler or the cables are faulty. Anyway I changed to data cable and the port on the mother board, but no joy. Nothing critical on this machine, if no solution I will try a full reinstall.

Result of smartctl

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.17.0-5-generic] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Samsung based SSDs
Device Model:     Samsung SSD 860 QVO 1TB
Serial Number:    S4CZNF0N617054B
LU WWN Device Id: 5 002538 e9061b410
Firmware Version: RVQ02B6Q
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
TRIM Command:     Available, deterministic, zeroed
Device is:        In smartctl database 7.3/5528
ATA Version is:   ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Tue Jan 20 15:07:37 2026 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is:   Unavailable
APM feature is:   Unavailable
Rd look-ahead is: Enabled
Write cache is:   Enabled
DSN feature is:   Unavailable
ATA Security is:  Disabled, frozen [SEC2]
Wt Cache Reorder: Enabled

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

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
					was never started.
					Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
					without error or no self-test has ever 
					been run.
Total time to complete Offline 
data collection: 		(    0) seconds.
Offline data collection
capabilities: 			 (0x53) SMART execute Offline immediate.
					Auto Offline data collection on/off support.
					Suspend Offline collection upon new
					command.
					No Offline surface scan supported.
					Self-test supported.
					No Conveyance Self-test supported.
					Selective Self-test supported.
SMART capabilities:            (0x0003)	Saves SMART data before entering
					power-saving mode.
					Supports SMART auto save timer.
Error logging capability:        (0x01)	Error logging supported.
					General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 (  85) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
					SCT Error Recovery Control supported.
					SCT Feature Control supported.
					SCT Data Table supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAGS    VALUE WORST THRESH FAIL RAW_VALUE
  5 Reallocated_Sector_Ct   PO--CK   100   100   010    -    0
  9 Power_On_Hours          -O--CK   096   096   000    -    18761
 12 Power_Cycle_Count       -O--CK   098   098   000    -    1384
177 Wear_Leveling_Count     PO--C-   086   086   000    -    111
179 Used_Rsvd_Blk_Cnt_Tot   PO--C-   100   100   010    -    0
181 Program_Fail_Cnt_Total  -O--CK   100   100   010    -    0
182 Erase_Fail_Count_Total  -O--CK   100   100   010    -    0
183 Runtime_Bad_Block       PO--C-   100   100   010    -    0
187 Uncorrectable_Error_Cnt -O--CK   100   100   000    -    0
190 Airflow_Temperature_Cel -O--CK   076   049   000    -    24
195 ECC_Error_Rate          -O-RC-   200   200   000    -    0
199 CRC_Error_Count         -OSRCK   099   099   000    -    389
235 POR_Recovery_Count      -O--C-   099   099   000    -    182
241 Total_LBAs_Written      -O--CK   099   099   000    -    188342708641
                            ||||||_ K auto-keep
                            |||||__ C event count
                            ||||___ R error rate
                            |||____ S speed/performance
                            ||_____ O updated online
                            |______ P prefailure warning

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
Address    Access  R/W   Size  Description
0x00       GPL,SL  R/O      1  Log Directory
0x01           SL  R/O      1  Summary SMART error log
0x02           SL  R/O      1  Comprehensive SMART error log
0x03       GPL     R/O      1  Ext. Comprehensive SMART error log
0x04       GPL,SL  R/O      8  Device Statistics log
0x06           SL  R/O      1  SMART self-test log
0x07       GPL     R/O      1  Extended self-test log
0x09           SL  R/W      1  Selective self-test log
0x10       GPL     R/O      1  NCQ Command Error log
0x11       GPL     R/O      1  SATA Phy Event Counters log
0x13       GPL     R/O      1  SATA NCQ Send and Receive log
0x30       GPL,SL  R/O      9  IDENTIFY DEVICE data log
0x80-0x9f  GPL,SL  R/W     16  Host vendor specific log
0xa1           SL  VS      16  Device vendor specific log
0xa5           SL  VS      16  Device vendor specific log
0xce           SL  VS      16  Device vendor specific log
0xe0       GPL,SL  R/W      1  SCT Command/Status
0xe1       GPL,SL  R/W      1  SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (1 sectors)
No Errors Logged

SMART Extended Self-test Log Version: 1 (1 sectors)
No self-tests have been logged.  [To run self-tests, use: smartctl -t]

SMART Selective self-test log data structure revision number 1
 SPAN  MIN_LBA  MAX_LBA  CURRENT_TEST_STATUS
    1        0        0  Not_testing
    2        0        0  Not_testing
    3        0        0  Not_testing
    4        0        0  Not_testing
    5        0        0  Not_testing
  256        0    65535  Read_scanning was never started
Selective self-test flags (0x0):
  After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

SCT Status Version:                  3
SCT Version (vendor specific):       256 (0x0100)
Device State:                        Active (0)
Current Temperature:                    24 Celsius
Power Cycle Min/Max Temperature:     23/24 Celsius
Lifetime    Min/Max Temperature:      5/51 Celsius
Specified Max Operating Temperature:    70 Celsius
Under/Over Temperature Limit Count:   0/0
SMART Status:                        0xc24f (PASSED)

SCT Temperature History Version:     2
Temperature Sampling Period:         10 minutes
Temperature Logging Interval:        10 minutes
Min/Max recommended Temperature:      0/70 Celsius
Min/Max Temperature Limit:            0/70 Celsius
Temperature History Size (Index):    128 (30)

Index    Estimated Time   Temperature Celsius
  31    2026-01-19 17:50    23  ****
  32    2026-01-19 18:00    23  ****
  33    2026-01-19 18:10    24  *****
  34    2026-01-19 18:20    23  ****
  35    2026-01-19 18:30    25  ******
  36    2026-01-19 18:40    24  *****
  37    2026-01-19 18:50     ?  -
  38    2026-01-19 19:00    27  ********
  39    2026-01-19 19:10     ?  -
 ...    ..(  4 skipped).    ..  -
  44    2026-01-19 20:00     ?  -
  45    2026-01-19 20:10    23  ****
 ...    ..( 64 skipped).    ..  ****
 110    2026-01-20 07:00    23  ****
 111    2026-01-20 07:10     ?  -
 112    2026-01-20 07:20    23  ****
 113    2026-01-20 07:30    23  ****
 114    2026-01-20 07:40     ?  -
 115    2026-01-20 07:50     ?  -
 116    2026-01-20 08:00    29  **********
 117    2026-01-20 08:10     ?  -
 118    2026-01-20 08:20    32  *************
 119    2026-01-20 08:30     ?  -
 120    2026-01-20 08:40     ?  -
 121    2026-01-20 08:50    24  *****
 122    2026-01-20 09:00    25  ******
 123    2026-01-20 09:10    23  ****
 124    2026-01-20 09:20    30  ***********
 125    2026-01-20 09:30     ?  -
 126    2026-01-20 09:40    24  *****
 ...    ..(  5 skipped).    ..  *****
   4    2026-01-20 10:40    24  *****
   5    2026-01-20 10:50    23  ****
   6    2026-01-20 11:00    24  *****
   7    2026-01-20 11:10    24  *****
   8    2026-01-20 11:20    24  *****
   9    2026-01-20 11:30    23  ****
 ...    ..( 12 skipped).    ..  ****
  22    2026-01-20 13:40    23  ****
  23    2026-01-20 13:50    24  *****
  24    2026-01-20 14:00    24  *****
  25    2026-01-20 14:10    23  ****
  26    2026-01-20 14:20     ?  -
  27    2026-01-20 14:30     ?  -
  28    2026-01-20 14:40    23  ****
  29    2026-01-20 14:50     ?  -
  30    2026-01-20 15:00    24  *****

SCT Error Recovery Control:
           Read: Disabled
          Write: Disabled

Device Statistics (GP Log 0x04)
Page  Offset Size        Value Flags Description
0x01  =====  =               =  ===  == General Statistics (rev 1) ==
0x01  0x008  4            1384  ---  Lifetime Power-On Resets
0x01  0x010  4           18761  ---  Power-on Hours
0x01  0x018  6    188342708641  ---  Logical Sectors Written
0x01  0x020  6      1436396583  ---  Number of Write Commands
0x01  0x028  6    230770047440  ---  Logical Sectors Read
0x01  0x030  6      2127280850  ---  Number of Read Commands
0x01  0x038  6          345000  ---  Date and Time TimeStamp
0x04  =====  =               =  ===  == General Errors Statistics (rev 1) ==
0x04  0x008  4               0  ---  Number of Reported Uncorrectable Errors
0x04  0x010  4            1086  ---  Resets Between Cmd Acceptance and Completion
0x05  =====  =               =  ===  == Temperature Statistics (rev 1) ==
0x05  0x008  1              24  ---  Current Temperature
0x05  0x020  1              51  ---  Highest Temperature
0x05  0x028  1               5  ---  Lowest Temperature
0x05  0x058  1              70  ---  Specified Maximum Operating Temperature
0x06  =====  =               =  ===  == Transport Statistics (rev 1) ==
0x06  0x008  4            6482  ---  Number of Hardware Resets
0x06  0x010  4               0  ---  Number of ASR Events
0x06  0x018  4             389  ---  Number of Interface CRC Errors
0x07  =====  =               =  ===  == Solid State Device Statistics (rev 1) ==
0x07  0x008  1              14  N--  Percentage Used Endurance Indicator
                                |||_ C monitored condition met
                                ||__ D supports DSN
                                |___ N normalized value

Pending Defects log (GP Log 0x0c) not supported

SATA Phy Event Counters (GP Log 0x11)
ID      Size     Value  Description

gautier-andreotti · January 23, 2026, 12:06pm

I found a sort of solution. I replaced the potentially failing SDD with a HDD, installed Ubuntu 25.10, start it and… stubled on exactly the same issues, some files and file system corruption, with the difference that a HDD dont failed Read Only. So I decided to install another Linux distro, Zorins 18, and it works without any issue, directly on Nvidia driver were the issues started with Ubuntu. At this stage I don’t know what to think. Is it an issue with Ubuntu 25.10 on this specific hardware?

Zorin 18 current kernel version is 6.14.0-37

ogra · January 23, 2026, 12:42pm

Zorin 18 is just Ubuntu 24.04 with a different UI, it uses the same kernel and Nvidia drivers, have you considered using 24.04 and sticking with the LTS ?

gautier-andreotti · January 23, 2026, 1:32pm

Yes of course, but I am curious about what could have cause this specific issue on this system with Ubuntu 25.10. This is my son old gaming computer, nothing critical, I am just using it to poke around new stuff, like Zorin OS (super easy distro by the way)

Actionparsnip · January 23, 2026, 2:25pm

Trying Zorin is basically trying Ubuntu. The packages are near identical. If you’d tried Fedora or Suse, rather than just Ubuntu with different clothing then it’d be trying something different

gautier-andreotti · January 23, 2026, 2:46pm

Ok, but if I do not have the issue with Zorin it seems specifcaly to point to Ubuntu 25.10 on this specific system. I will try the version 24.04.3 LTS.

Actionparsnip · January 23, 2026, 3:40pm

Likely, the reinstall will have made a fresh file system which would be healthy. If its the same storage then it’s likely that hardware is OK

gautier-andreotti · January 24, 2026, 12:36pm

I 99% confirm the disk corruption issue with Ubuntu 25.10 on this specific system. I installed the version 24.03 LTS, no issue (as well as with Zorin 18). Just after, same system, same configuration, with a new 25.10 iso image on a same USB dongle, the version installed (complete disk erase) without any issue but after restarting the disk show signs of corruption. This time I used a HDD and as a HDD don’t failed Read-Only I got some logs, see below. If someone want to investigate further I will keep this disk as it.

13:14:05 kernel: EXT4-fs (sdb2): failed to convert unwritten extents to written extents -- potential data loss!  (inode 29884970, error -5)
13:14:05 kernel: I/O error, dev sdb, sector 8122368 op 0x1:(WRITE) flags 0x0 phys_seg 64 prio class 2
13:14:05 kernel: ata6.00: status: { DRDY }
13:14:05 kernel: ata6: SError: { UnrecovData HostInt Handshk }
13:14:05 kernel: ata6.00: irq_stat 0x28000000, host bus error, interface fatal error
13:14:05 kernel: ata6: SError: { UnrecovData HostInt Handshk }
13:14:05 kernel: ata6.00: irq_stat 0x28000000, host bus error, interface fatal error
13:14:05 kernel: ata6: SError: { HostInt }
13:14:05 kernel: ata6.00: irq_stat 0x20000000, host bus error
13:14:05 kernel: ata6: SError: { UnrecovData HostInt Handshk }
13:14:05 kernel: ata6.00: irq_stat 0x28000000, host bus error, interface fatal error
13:14:05 kernel: ata6: SError: { HostInt }
13:14:05 kernel: ata6.00: irq_stat 0x20000000, host bus error
13:14:05 kernel: ata6: SError: { HostInt }
13:14:05 kernel: ata6.00: irq_stat 0x20000000, host bus error
13:14:05 kernel: EXT4-fs (sdb2): failed to convert unwritten extents to written extents -- potential data loss!  (inode 29884969, error -5)
13:14:05 kernel: I/O error, dev sdb, sector 1101824 op 0x1:(WRITE) flags 0x4000 phys_seg 64 prio class 2
13:14:05 kernel: Buffer I/O error on device sdb2, logical block 995337
13:14:05 kernel: I/O error, dev sdb, sector 8114176 op 0x1:(WRITE) flags 0x4000 phys_seg 64 prio class 2
13:14:05 kernel: Buffer I/O error on device sdb2, logical block 995336
13:14:03 kernel: EXT4-fs (sdb2): failed to convert unwritten extents to written extents -- potential data loss!  (inode 29884970, error -5)
13:14:03 kernel: I/O error, dev sdb, sector 8024064 op 0x1:(WRITE) flags 0x0 phys_seg 64 prio class 2
13:14:02 kernel: ata6.00: status: { DRDY }
13:14:02 kernel: ata6: SError: { UnrecovData HostInt Handshk }
13:14:02 kernel: ata6.00: irq_stat 0x28000000, host bus error, interface fatal error
13:14:02 kernel: ata6: SError: { UnrecovData HostInt Handshk }
13:14:02 kernel: ata6.00: irq_stat 0x28000000, host bus error, interface fatal error
13:14:01 kernel: ata6: SError: { UnrecovData HostInt Handshk }
13:14:01 kernel: ata6.00: irq_stat 0x28000000, host bus error, interface fatal error
13:14:01 kernel: DMAR: DRHD: handling fault status reg 3
13:14:01 kernel: ata6.00: status: { DRDY }
13:14:01 kernel: ata6: SError: { UnrecovData HostInt Handshk }
13:14:01 kernel: ata6.00: irq_stat 0x28000000, host bus error, interface fatal error
13:14:01 kernel: DMAR: [DMA Read NO_PASID] Request device [00:1f.2] fault addr 0xbcc00000 [fault reason 0x0c] non-zero reserved fields in PTE
13:14:01 kernel: ata6.00: status: { DRDY }
13:14:01 kernel: ata6: SError: { UnrecovData HostInt Handshk }
13:14:01 kernel: ata6.00: irq_stat 0x28000000, host bus error, interface fatal error
13:14:01 kernel: DMAR: [DMA Read NO_PASID] Request device [00:1f.2] fault addr 0xbdc00000 [fault reason 0x0c] non-zero reserved fields in PTE
13:14:00 kernel: ata6.00: status: { DRDY }
13:14:00 kernel: ata6: SError: { HostInt CommWake }
13:14:00 kernel: ata6.00: irq_stat 0x20000000, host bus error
13:14:00 kernel: DMAR: [DMA Read NO_PASID] Request device [00:1f.2] fault addr 0xbc800000 [fault reason 0x0c] non-zero reserved fields in PTE
13:12:53 kernel: SQUASHFS error: Failed to read block 0x10ab1363: -5
13:12:47 kernel: DMAR: DRHD: handling fault status reg 3
13:12:34 wireplumber: spa.alsa: can't open control for card hw:1: No such file or directory
13:12:33 gdm-session-wor: gkr-pam: unable to locate daemon control file
13:11:58 systemd-udevd: /usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO="alsa_restore_std" has no matching label, ignoring.
13:11:58 wireplumber: spa.alsa: can't open control for card hw:1: No such file or directory
13:11:44 chronyd: Could not connect to [2620:2d:4000:1::2123]:4460 (1.ntp.ubuntu.com) : No route to host
13:11:39 systemd-udevd: /usr/lib/udev/rules.d/90-alsa-restore.rules:22 GOTO="alsa_restore_std" has no matching label, ignoring.

ogra · January 24, 2026, 7:05pm

Keep the disk and run: ubuntu-bug linux

That will collect all needed logs and help you creating a bug so that the Ubuntu kernel devs get aware of it …

gautier-andreotti · January 25, 2026, 1:55pm

Thanks for your reply

I reported the bug manually the “bug-ubuntu linux” is not running due to corrupted files.

See https://bugs.launchpad.net/ubuntu/+bug/2139029

system · January 26, 2026, 1:56pm

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.