lsblk -o NAME,FSTYPE,FSVER,FSAVAIL,FSUSE%,MOUNTPOINTS
NAME FSTYPE FSVER FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1 ext4 1.0 69.3G 19% /
├─sda2 vfat FAT32 182M 3% /boot/efi
├─sda3
├─sda5 vfat FAT32
├─sda6 vfat FAT32 126.9G 1% /media/murali/AUDIO-VIDEO
└─sda7 vfat FAT32
sr0
 
cannot access '/sys/firmware/efi/efivars': No such file or directory
Are you sure you're booted in EFI mode? That directory will not be there in legacy boot mode
 
When I install Mint Cinnamon...I always choose...Erase disk and install linux Mint...this creates two partitions...Boot and Root.
1719014168006.png

I never have problems...it's hard to help with issues I've never had in the 9 years of running Mint Cinnamon.
Mint is a very solid and stable Distro...the issues we see are usually hardware or user related. :eek:
 
Ditto ^^

1719015381043.png
 
Usually the filesystem gets set to read only if there is an interruption to power, or if there is a problem reading from, or writing to the disk, it sometimes indicates that another bit of hardware is failing.
But most commonly, it indicates a disk related issue (typically a dying HDD/SSD).
Next time it happens, open a terminal and run:
Bash:
sudo dmesg | tail

That will show you the most recent messages from the kernel log and may shed some light on the reason the HDD/SSD was put into read only mode.
Failing that, take a look at some of the other logs, like syslog (tail /var/log/syslog), or systemd’s logs since the most recent boot (journalctl -b).
 
Are you using Cinnamon or another desktop environment? Can you open a terminal and share the output of the following?
Code:
ls -l  /usr/share/thumbnailers ~/.cache/thumbnails
 
ls -l /usr/share/thumbnailers ~/.cache/thumbnails
/home/murali/.cache/thumbnails:
total 32
drwx------ 3 murali murali 4096 Jun 21 18:55 fail
drwx------ 2 murali murali 20480 Jun 23 12:18 large
drwxrwxr-x 2 murali murali 4096 Jun 23 11:16 normal

/usr/share/thumbnailers:
total 40
-rw-r--r-- 1 root root 677 Feb 14 2022 ffmpegthumbnailer.thumbnailer
-rw-r--r-- 1 root root 525 Jun 3 22:10 gdk-pixbuf-thumbnailer.thumbnailer
-rw-r--r-- 1 root root 1304 Mar 24 2022 gsf-office.thumbnailer
-rw-r--r-- 1 root root 158 Jul 28 2023 librsvg.thumbnailer
-rw-r--r-- 1 root root 130 Jun 29 2022 webp-pixbuf.thumbnailer
-rw-r--r-- 1 root root 138 Jun 5 2023 xapp-appimage-thumbnailer.thumbnailer
-rw-r--r-- 1 root root 126 Jun 5 2023 xapp-epub-thumbnailer.thumbnailer
-rw-r--r-- 1 root root 114 Jun 5 2023 xapp-mp3-thumbnailer.thumbnailer
-rw-r--r-- 1 root root 436 Jul 21 2023 xapp-raw-thumbnailer.thumbnailer
-rw-r--r-- 1 root root 691 Jan 4 22:39 xreader.thumbnailer
 
The problem comes up occasionally. Yesterday on doing fsck of my /root drive the following messages came up:
Inodes that were part of a corrupted orphan linked list found. Fix <y>
8 inodes fixed
dierctory structures were ok. So too directory connectivity and reference counts.
block bitmap differences shown, 10
free blocks count wrong
Inode bitmap difference
Free inodes count wrong for 5 groups
After fixing all of that I could boot up and work for some time.
 
/usr/share/thumbnailers:
total 40
-rw-r--r-- 1 root root 677 Feb 14 2022 ffmpegthumbnailer.thumbnailer
-rw-r--r-- 1 root root 525 Jun 3 22:10 gdk-pixbuf-thumbnailer.thumbnailer
-rw-r--r-- 1 root root 1304 Mar 24 2022 gsf-office.thumbnailer
-rw-r--r-- 1 root root 158 Jul 28 2023 librsvg.thumbnailer
-rw-r--r-- 1 root root 130 Jun 29 2022 webp-pixbuf.thumbnailer
-rw-r--r-- 1 root root 138 Jun 5 2023 xapp-appimage-thumbnailer.thumbnailer
-rw-r--r-- 1 root root 126 Jun 5 2023 xapp-epub-thumbnailer.thumbnailer
-rw-r--r-- 1 root root 114 Jun 5 2023 xapp-mp3-thumbnailer.thumbnailer
-rw-r--r-- 1 root root 436 Jul 21 2023 xapp-raw-thumbnailer.thumbnailer
-rw-r--r-- 1 root root 691 Jan 4 22:39 xreader.thumbnailer
What desktop environment are you using for Mint?
 
Today first attempt at booting failed with the following message:
Inittramfs unpacking failed ZSTD compressed data corrupt
failed to execute /init
Kerenl panic
Passing init=option to kernel
show-stack, dump-stack
and the the screen went blank.
But after waiting for some time and doing a boot by pressing the power switch everything was normal!
 
Usually the filesystem gets set to read only if there is an interruption to power, or if there is a problem reading from, or writing to the disk, it sometimes indicates that another bit of hardware is failing.
But most commonly, it indicates a disk related issue (typically a dying HDD/SSD).
Next time it happens, open a terminal and run:
Bash:
sudo dmesg | tail

That will show you the most recent messages from the kernel log and may shed some light on the reason the HDD/SSD was put into read only mode.
Failing that, take a look at some of the other logs, like syslog (tail /var/log/syslog), or systemd’s logs since the most recent boot (journalctl -b).
I just ran sudo dmesg and this is something that came up in the ouput:
0.004187] On node 0, zone DMA: 1 pages in unavailable ranges
[ 0.004230] On node 0, zone DMA: 99 pages in unavailable ranges
[ 0.006863] On node 0, zone DMA32: 512 pages in unavailable ranges
[ 0.012445] On node 0, zone DMA32: 1 pages in unavailable ranges
[ 0.024582] On node 0, zone Normal: 8698 pages in unavailable ranges
[ 0.024741] On node 0, zone Normal: 6656 pages in unavailable ranges
then
[ 0.025502] Policy zone: Normal
[ 0.025504] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-112-generic root=UUID=3d7a50a6-30fd-4632-b216-291d80270276 ro quiet splash
[ 0.025587] Unknown kernel command line parameters "splash BOOT_IMAGE=/boot/vmlinuz-5.15.0-112-generic", will be passed to user space.
further on
[ 1.083568] system 00:05: [mem 0xff000000-0xffffffff] could not be reserved
[ 1.083570] system 00:05: [mem 0xfee00000-0xfeefffff] could not be reserved
further on
[ 2.048558] ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20210730/utaddress-204)
[ 2.048570] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[ 2.048574] ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20210730/utaddress-204)
[ 2.048580] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[ 2.048581] ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20210730/utaddress-204)
[ 2.048587] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[ 2.048588] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GPIO) (20210730/utaddress-204)
[ 2.048594] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[ 2.048595] lpc_ich: Resource conflict(s) found affecting gpio_ich
further on:
[ 73.738069] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 241.816269] FAT-fs (sda6): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 3397.344395] perf: interrupt took too long (2526 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
[ 4150.334316] perf: interrupt took too long (3228 > 3157), lowering kernel.perf_event_max_sample_rate to 61750
[ 6206.555559] perf: interrupt took too long (4061 > 4035), lowering kernel.perf_event_max_sample_rate to 49250
[ 8781.942079] ata1.00: exception Emask 0x10 SAct 0xc00000 SErr 0x450100 action 0x6 frozen
[ 8781.942089] ata1.00: irq_stat 0x08000008, interface fatal error
[ 8781.942091] ata1: SError: { UnrecovData PHYRdyChg CommWake Handshk }
[ 8781.942096] ata1.00: failed command: WRITE FPDMA QUEUED
[ 8781.942097] ata1.00: cmd 61/08:b0:98:f7:91/00:00:07:00:00/40 tag 22 ncq dma 4096 out
res 50/00:10:a0:f7:91/00:00:07:00:00/40 Emask 0x10 (ATA bus error)
[ 8781.942103] ata1.00: status: { DRDY }
[ 8781.942105] ata1.00: failed command: WRITE FPDMA QUEUED
[ 8781.942106] ata1.00: cmd 61/10:b8:a0:f7:91/00:00:07:00:00/40 tag 23 ncq dma 8192 out
res 50/00:10:a0:f7:91/00:00:07:00:00/40 Emask 0x10 (ATA bus error)
[ 8781.942111] ata1.00: status: { DRDY }
[ 8788.098106] ata1.00: exception Emask 0x10 SAct 0x80000 SErr 0x450100 action 0x6 frozen
[ 8788.098119] ata1.00: irq_stat 0x08000000, interface fatal error
[ 8788.098124] ata1: SError: { UnrecovData PHYRdyChg CommWake Handshk }
[ 8788.098129] ata1.00: failed command: WRITE FPDMA QUEUED
[ 8788.098131] ata1.00: cmd 61/a0:98:d0:a1:c8/00:00:05:00:00/40 tag 19 ncq dma 81920 out
res 50/00:a0:d0:a1:c8/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
[ 8788.098138] ata1.00: status: { DRDY }
[ 8788.442059] ata1.00: exception Emask 0x10 SAct 0x400000 SErr 0x450100 action 0x6 frozen
[ 8788.442077] ata1.00: irq_stat 0x08000000, interface fatal error
[ 8788.442082] ata1: SError: { UnrecovData PHYRdyChg CommWake Handshk }
[ 8788.442100] ata1.00: failed command: WRITE FPDMA QUEUED
[ 8788.442104] ata1.00: cmd 61/a0:b0:d0:a1:c8/00:00:05:00:00/40 tag 22 ncq dma 81920 out
res 50/00:a0:d0:a1:c8/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
[ 8788.442113] ata1.00: status: { DRDY }
[ 8788.778085] ata1.00: exception Emask 0x10 SAct 0x100 SErr 0x450100 action 0x6 frozen
[ 8788.778100] ata1.00: irq_stat 0x08000000, interface fatal error
[ 8788.778102] ata1: SError: { UnrecovData PHYRdyChg CommWake Handshk }
[ 8788.778106] ata1.00: failed command: WRITE FPDMA QUEUED
[ 8788.778107] ata1.00: cmd 61/a0:40:d0:a1:c8/00:00:05:00:00/40 tag 8 ncq dma 81920 out
res 50/00:a0:d0:a1:c8/00:00:05:00:00/40 Emask 0x10 (ATA bus error)
[ 8788.778114] ata1.00: status: { DRDY }
 
<Next time it happens, open a terminal and run> Can I do that from a USB with Mint installed on it, in case the Terminal can't be accessed?
 
After rereading your first post I'm going to have to agree with @JasKinasis, getting more of the idea this could be a hardware problem with your disk. How old is that disk? Can you share the output of the following?
Code:
lsblk -f
dmesg | grep sd
 
lsblk -f dmesg | grep sd
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
├─sda1
│ ext4 1.0 3d7a50a6-30fd-4632-b216-291d80270276 69.2G 19% /
├─sda2
│ vfat FAT32 B51E-C122 182M 3% /boot/efi
├─sda3

├─sda5
│ vfat FAT32 DATA 6A2D-702A
├─sda6
│ vfat FAT32 AUDIO-VIDEO
│ 6A8F-29D7 126.7G 1% /media/murali/AUDIO-VIDEO
└─sda7
vfat FAT32 BOOKS 6B14-2A79
sdb
└─sdb1
vfat FAT32 0B88-FA56 28G 3% /media/murali/0B88-FA56
sr0
[ 2.429741] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 2.430071] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[ 2.430095] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 2.430190] sd 0:0:0:0: [sda] Write Protect is off
[ 2.430200] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[ 2.430275] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 2.535460] sda: sda1 sda2 sda3 < sda5 sda6 sda7 >
[ 2.537156] sd 0:0:0:0: [sda] Attached SCSI disk
[ 3.842514] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 3.843233] sd 6:0:0:0: [sdb] 60395520 512-byte logical blocks: (30.9 GB/28.8 GiB)
[ 3.843914] sd 6:0:0:0: [sdb] Write Protect is off
[ 3.843922] sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 3.844601] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 3.867748] sdb: sdb1
[ 3.869870] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[ 9.821802] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
[ 16.115930] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro. Quota mode: none.
[ 40.649454] audit: type=1400 audit(1719122263.976:25): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=895 comm="cupsd" capability=12 capname="net_admin"
[ 73.738069] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[ 241.816269] FAT-fs (sda6): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
 
In that case wouldn't it cause problems every time I boot? The laptop is about 10years old.
Hard disks normally die over time, sometimes showing small symptoms before actually giving out entirely. I had that with one of my systems that was running 247.

Can you share the output the following as well?
Code:
sudo smartctl -a /dev/sda
sudo smartctl -a /dev/sdb
 
sudo smartctl -a /dev/sda
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-112-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Hitachi/HGST Travelstar Z7K500
Device Model: HGST HTS725050A7E630
Serial Number: TF655AY9K71XBL
LU WWN Device Id: 5 000cca 662ed7c4c
Firmware Version: GH2ZB550
User Capacity: 500,107,862,016 bytes [500 GB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 2.6, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Sun Jun 23 15:10:58 2024 IST
SMART support is: Available - device has SMART capability.
SMART support is: 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: ( 45) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
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: ( 90) 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: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 100 100 062 Pre-fail Always - 0
2 Throughput_Performance 0x0005 100 100 040 Pre-fail Offline - 0
3 Spin_Up_Time 0x0007 240 240 033 Pre-fail Always - 1
4 Start_Stop_Count 0x0012 091 091 000 Old_age Always - 14809
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0005 100 100 040 Pre-fail Offline - 0
9 Power_On_Hours 0x0012 025 025 000 Old_age Always - 33285
10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 095 095 000 Old_age Always - 8588
191 G-Sense_Error_Rate 0x000a 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 096 096 000 Old_age Always - 341312329
193 Load_Cycle_Count 0x0012 070 070 000 Old_age Always - 302782
194 Temperature_Celsius 0x0002 130 130 000 Old_age Always - 46 (Min/Max 15/62)
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 36
197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 9503
223 Load_Retry_Count 0x000a 100 100 000 Old_age Always - 0

SMART Error Log Version: 1
ATA Error Count: 20841 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 20841 occurred at disk power-on lifetime: 33284 hours (1386 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 90 e0 a1 c8 05 Error: ICRC, ABRT at LBA = 0x05c8a1e0 = 97034720

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 a0 40 d0 a1 c8 40 00 02:26:35.626 WRITE FPDMA QUEUED
ef 10 03 00 00 00 a0 00 02:26:35.625 SET FEATURES [Enable SATA feature]
47 00 01 00 00 00 a0 00 02:26:35.625 READ LOG DMA EXT
ef 10 02 00 00 00 a0 00 02:26:35.625 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 02:26:35.625 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 20840 occurred at disk power-on lifetime: 33284 hours (1386 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 90 e0 a1 c8 05 Error: ICRC, ABRT at LBA = 0x05c8a1e0 = 97034720

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 a0 b0 d0 a1 c8 40 00 02:26:35.285 WRITE FPDMA QUEUED
ef 10 03 00 00 00 a0 00 02:26:35.285 SET FEATURES [Enable SATA feature]
47 00 01 00 00 00 a0 00 02:26:35.284 READ LOG DMA EXT
ef 10 02 00 00 00 a0 00 02:26:35.284 SET FEATURES [Enable SATA feature]
27 00 00 00 00 00 e0 00 02:26:35.284 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]

Error 20839 occurred at disk power-on lifetime: 33284 hours (1386 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 90 e0 a1 c8 05 Error: ICRC, ABRT at LBA = 0x05c8a1e0 = 97034720

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 a0 98 d0 a1 c8 40 00 02:26:34.929 WRITE FPDMA QUEUED
61 08 80 c0 5e d0 40 00 02:26:34.157 WRITE FPDMA QUEUED
61 08 78 08 1d 0d 40 00 02:26:34.157 WRITE FPDMA QUEUED
61 78 70 00 c8 cd 40 00 02:26:34.157 WRITE FPDMA QUEUED
61 90 68 70 67 bc 40 00 02:26:34.157 WRITE FPDMA QUEUED

Error 20838 occurred at disk power-on lifetime: 33284 hours (1386 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 01 af f7 91 07 Error: ICRC, ABRT at LBA = 0x0791f7af = 127006639

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 10 b8 a0 f7 91 40 00 02:26:28.766 WRITE FPDMA QUEUED
61 08 b0 98 f7 91 40 00 02:26:28.766 WRITE FPDMA QUEUED
61 08 78 b0 14 93 40 00 02:26:25.984 WRITE FPDMA QUEUED
ea 00 00 00 00 00 a0 00 02:26:24.956 FLUSH CACHE EXT
61 08 a0 e0 a0 c8 40 00 02:26:24.956 WRITE FPDMA QUEUED

Error 20837 occurred at disk power-on lifetime: 33282 hours (1386 days + 18 hours)
When the command that caused the error occurred, the device was active or idle.

After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 51 01 09 48 d0 08 Error: ICRC, ABRT 1 sectors at LBA = 0x08d04809 = 147867657

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
35 00 02 08 48 d0 e0 00 00:00:03.950 WRITE DMA EXT
25 00 1f 21 48 c4 e0 00 00:00:03.940 READ DMA EXT
25 00 21 00 48 c4 e0 00 00:00:03.928 READ DMA EXT
25 00 3e 02 7f c4 e0 00 00:00:03.927 READ DMA EXT
25 00 02 00 7f c4 e0 00 00:00:03.917 READ DMA EXT

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Interrupted (host reset) 60% 33257 -
# 2 Extended offline Aborted by host 90% 33199 -
# 3 Short offline Completed without error 00% 33187 -
# 4 Short offline Completed without error 00% 33186 -
# 5 Vendor (0x50) Completed without error 00% 31941 -
# 6 Short offline Completed without error 00% 31941 -
# 7 Vendor (0x50) Completed without error 00% 15406 -
# 8 Short offline Completed without error 00% 15406 -
# 9 Vendor (0x50) Completed without error 00% 15375 -
#10 Short offline Completed without error 00% 15375 -
#11 Vendor (0x50) Completed without error 00% 15020 -
#12 Short offline Completed without error 00% 15020 -
#13 Vendor (0x50) Completed without error 00% 11860 -
#14 Short offline Completed without error 00% 11860 -
#15 Vendor (0x50) Completed without error 00% 10972 -
#16 Short offline Completed without error 00% 10972 -
#17 Vendor (0x50) Completed without error 00% 10585 -
#18 Short offline Completed without error 00% 10585 -
#19 Vendor (0x50) Aborted by host 10% 10262 -
#20 Short offline Completed without error 00% 10262 -
#21 Vendor (0x50) Completed without error 00% 9866 -

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
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.
 
sudo smartctl -a /dev/sdb
smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.15.0-112-generic] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/sdb: Unknown USB bridge [0x058f:0x6387 (0x100)]
Please specify device type with the -d option.

Use smartctl -h to get a usage summary
 

Members online


Top