I am stuck in emergency mode and can not fix Bluetooth and `tpm_crb`

General system Kernel, boot, graphics & hardware
1

Hello!

I have read the following topics:

Weeks ago, I purchased a new computer case and a new 2 TB SSD NVMe m.2.

I made a clean installation of Endeavour OS Gemini on the 480 SSD Adata SU630. After the successful installation, I booted again in Live USB to create the 2 TB SSD NVMe m.2 partitions – home and opt and the automatic mount with their UUIDs for the fstab file.

I formatted both SSDs as GPT and all the partitions as ext4. I used UEFI. I have latest, LTS and `zen versions of Linux kernels installed.

Everything worked perfectly. But I was irritated with the long tpmrm0 time. I made a research and followed a tip whose command sudo systemctl mask dev-tpmrm0.device.

Then everything worked until it stopped on the 31st July at 16:30 in Brazil (12:30 in Los Angeles and Vancouver, 15:30 in New York, 20:30 in London, 21:30 in Amsterdam, Berlin, Madrid, Paris and Rome, 22:30 in Athens and Kyiv, 23:30 in Tbilisi). Today I am stuck in emergency mode. I investigated the motives and used the command journalectl -xb. I saw that it was a plymouth error.

I booted in the Live USB. I ran the command lsblk -f:

sudo lsblk -f
NAME     FSTYPE   FSVER            LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0    squashfs 4.0                                                                     0   100% /run/archiso/airootfs
sda                                                                                                
├─sda1   vfat     FAT32            EFI         2361-16AF                                           
├─sda2   ext4     1.0              Root        ad6438d7-6e3a-4c86-9af0-6dbcde08fae0                
└─sda3   swap     1                swap        3de32265-311d-40fb-869c-8779c671c7e3                
sdb                                                                                                
sdc      iso9660  Joliet Extension EOS_202404  2024-04-20-15-57-10-00                              
├─sdc1   iso9660  Joliet Extension EOS_202404  2024-04-20-15-57-10-00                     0   100% /run/archiso/bootmnt
└─sdc2   vfat     FAT16            ARCHISO_EFI 7156-9697                                           
nvme0n1                                                                                            
├─nvme0n1p1
│        ext4     1.0              Optional    47b48637-f135-41ea-a598-313bdbc26384                
└─nvme0n1p2
         ext4     1.0              Home        fa06c2b8-eb2b-4b11-b73b-c0238e91887b

Then I ran the following commands:

sudo mount /dev/sda2 /mnt
sudo mount /dev/sda1 /mnt/efi
sudo mount /dev/nvme0n1p2 /mnt/home
sudo mount /dev/nvme0n1p1 /mnt/opt

Then here is the fstab text:

$ sudo cat /mnt/etc/fstab
# <file system>                                   <mount point>  <type>  <options>                                      <dump>  <pass>
UUID=2361-16AF                            /efi           vfat    fmask=0137,dmask=0027                  0               2
UUID=ad6438d7-6e3a-4c86-9af0-6dbcde08fae0 /              ext4    noatime                                        0               1
UUID=fa06c2b8-eb2b-4b11-b73b-c0238e91887b /home          ext4    defaults                                       0               2
UUID=47b48637-f135-41ea-a598-313bdbc26384 /opt           ext4    defaults                                       0               2
UUID=3de32265-311d-40fb-869c-8779c671c7e3 swap           swap    defaults                                       0               0
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777     0               0

I entered into the chroot with the command sudo arch-chroot /mnt and did some following tasks:

  1. I installed breeze-plymouth, plymouth and plymouth-kcm packages.
  2. I ran the commands sudo reinstall-kernels and sudo dracut-rebuild.

After finishing the tasks, I rebooted in the SSD, and ended up stuck again in emergency mode. I saw that they were Bluetooh and tpm_crb errors. I did not know how to fix it, but I made a research about the tpm_crb errors and I saw that it was a UEFI problem. I ran the command bootctl, then the secure boot has already been disabled before:

System:
      Firmware: UEFI 2.70 (American Megatrends 5.13)
 Firmware Arch: x64
   Secure Boot: disabled (setup)
  TPM2 Support: firmware only, driver unavailable
  Measured UKI: no
  Boot into FW: supported

Current Boot Loader:
      Product: systemd-boot 255.4-2-arch
     Features: ✓ Boot counting
               ✓ Menu timeout control
               ✓ One-shot menu timeout control
               ✓ Default entry control
               ✓ One-shot entry control
               ✓ Support for XBOOTLDR partition
               ✓ Support for passing random seed to OS
               ✓ Load drop-in drivers
               ✓ Support Type #1 sort-key field
               ✓ Support @saved pseudo-entry
               ✓ Support Type #1 devicetree field
               ✓ Enroll SecureBoot keys
               ✓ Retain SHIM protocols
               ✓ Menu can be disabled
               ✗ Boot loader sets ESP information
          ESP: n/a
         File: └─/EFI/BOOT/BOOTX64.EFI

Random Seed:
 System Token: set
       Exists: yes

Available Boot Loaders on ESP:
          ESP: /efi (/dev/disk/by-partuuid/37accc23-37a5-4ddc-b22a-607c84af06f9)
         File: ├─/EFI/systemd/systemd-bootx64.efi (systemd-boot 255.4-2-arch)
               └─/EFI/BOOT/BOOTX64.EFI (systemd-boot 255.4-2-arch)

Boot Loaders Listed in EFI Variables:
        Title: Linux Boot Manager
           ID: 0x0002
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/37accc23-37a5-4ddc-b22a-607c84af06f9
         File: └─/EFI/SYSTEMD/SYSTEMD-BOOTX64.EFI

        Title: UEFI OS
           ID: 0x0003
       Status: active, boot-order
    Partition: /dev/disk/by-partuuid/37accc23-37a5-4ddc-b22a-607c84af06f9
         File: └─/EFI/BOOT/BOOTX64.EFI

Boot Loader Entries:
        $BOOT: /efi (/dev/disk/by-partuuid/37accc23-37a5-4ddc-b22a-607c84af06f9)
        token: endeavouros

Default Boot Loader Entry:
         type: Boot Loader Specification Type #1 (.conf)
        title: EndeavourOS (6.10.2-arch1-1)
           id: 7672d332026846318e868f17ab40d4fb-6.10.2-arch1-1.conf
       source: /efi//loader/entries/7672d332026846318e868f17ab40d4fb-6.10.2-arch1-1.conf
     sort-key: endeavouros-6.10.2-arch1-1
      version: 6.10.2-arch1-1
   machine-id: 7672d332026846318e868f17ab40d4fb
        linux: /efi//7672d332026846318e868f17ab40d4fb/6.10.2-arch1-1/linux
       initrd: /efi//7672d332026846318e868f17ab40d4fb/6.10.2-arch1-1/initrd
      options: nvme_load=YES nowatchdog rw root=UUID=ad6438d7-6e3a-4c86-9af0-6dbcde08fae0 resume=UUID=3de32265-311d-40fb-869c-8779c671c7e3 systemd.machine_id=7672d332026846318e868f17ab40d4fb

If you wish to see the short journalectl log and inxi, follow:

  • journalctl -p 3 --since "2024-07-31":
-- Boot ed50238ae78a412d8019ae10f40ee147 --
Jul 31 16:36:17 endeavouros kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xdc31f000-0xdc31ffff flags 0x200] vs dc31f000 4000
Jul 31 16:36:17 endeavouros kernel: tpm_crb MSFT0101:00: error -EBUSY: can't request region for resource [mem 0xdc31f000-0xdc31ffff]
Jul 31 16:36:17 endeavouros kernel: tpm_crb MSFT0101:00: probe with driver tpm_crb failed with error -16
Jul 31 16:36:20 endeavouros kernel: iwlwifi 0000:06:00.0: WRT: Invalid buffer destination
Jul 31 16:36:21 endeavouros systemd-fsck[609]: fsck failed with exit status 4.
Jul 31 16:36:21 endeavouros systemd[1]: Failed to start File System Check on /dev/disk/by-uuid/fa06c2b8-eb2b-4b11-b73b-c0238e91887b.
Jul 31 16:36:22 endeavouros kernel: Bluetooth: hci0: Reading Intel version command failed (-110)
Jul 31 16:36:22 endeavouros kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Jul 31 16:37:10 endeavouros systemd-fsck[814]: fsck failed with exit status 4.
Jul 31 16:37:10 endeavouros systemd[1]: Failed to start File System Check on /dev/disk/by-uuid/fa06c2b8-eb2b-4b11-b73b-c0238e91887b.
Jul 31 16:42:49 endeavouros kernel: watchdog: watchdog0: watchdog did not stop!
-- Boot 64f7e0571c2e412aa9456c96d1031191 --
Jul 31 16:43:11 endeavouros kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xdc31f000-0xdc31ffff flags 0x200] vs dc31f000 4000
Jul 31 16:43:11 endeavouros kernel: tpm_crb MSFT0101:00: error -EBUSY: can't request region for resource [mem 0xdc31f000-0xdc31ffff]
Jul 31 16:43:11 endeavouros kernel: tpm_crb MSFT0101:00: probe with driver tpm_crb failed with error -16
Jul 31 16:43:14 endeavouros kernel: Bluetooth: hci0: No support for _PRR ACPI method
Jul 31 16:43:14 endeavouros kernel: iwlwifi 0000:06:00.0: WRT: Invalid buffer destination
Jul 31 16:43:15 endeavouros systemd-fsck[601]: fsck failed with exit status 4.
Jul 31 16:43:15 endeavouros systemd[1]: Failed to start File System Check on /dev/disk/by-uuid/fa06c2b8-eb2b-4b11-b73b-c0238e91887b.
Jul 31 16:43:18 endeavouros kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 31 16:54:26 endeavouros systemd-fsck[916]: fsck failed with exit status 4.
Jul 31 16:54:26 endeavouros systemd[1]: Failed to start File System Check on /dev/disk/by-uuid/fa06c2b8-eb2b-4b11-b73b-c0238e91887b.
Jul 31 16:55:31 endeavouros kernel: watchdog: watchdog0: watchdog did not stop!
-- Boot 897f8df87f86480392b3f21c50b215fd --
Jul 31 16:55:57 endeavouros kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xdc31f000-0xdc31ffff flags 0x200] vs dc31f000 4000
Jul 31 16:55:57 endeavouros kernel: tpm_crb MSFT0101:00: error -EBUSY: can't request region for resource [mem 0xdc31f000-0xdc31ffff]
Jul 31 16:55:57 endeavouros kernel: tpm_crb MSFT0101:00: probe with driver tpm_crb failed with error -16
Jul 31 16:56:00 endeavouros kernel: Bluetooth: hci0: No support for _PRR ACPI method
Jul 31 16:56:00 endeavouros kernel: iwlwifi 0000:06:00.0: WRT: Invalid buffer destination
Jul 31 16:56:01 endeavouros systemd-fsck[605]: fsck failed with exit status 4.
Jul 31 16:56:01 endeavouros systemd[1]: Failed to start File System Check on /dev/disk/by-uuid/fa06c2b8-eb2b-4b11-b73b-c0238e91887b.
Jul 31 17:13:52 endeavouros systemd-fsck[843]: fsck failed with exit status 4.
Jul 31 17:13:52 endeavouros systemd[1]: Failed to start File System Check on /dev/disk/by-uuid/fa06c2b8-eb2b-4b11-b73b-c0238e91887b.
[...]
-- Boot 3bf9a288f98649228510f99202b0bfd0 --
Jul 31 22:58:21 endeavouros kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xdc31f000-0xdc31ffff flags 0x200] vs dc31f000 4000
Jul 31 22:58:21 endeavouros kernel: tpm_crb MSFT0101:00: error -EBUSY: can't request region for resource [mem 0xdc31f000-0xdc31ffff]
Jul 31 22:58:21 endeavouros kernel: tpm_crb MSFT0101:00: probe with driver tpm_crb failed with error -16
Jul 31 22:58:27 endeavouros kernel: Bluetooth: hci0: No support for _PRR ACPI method
Jul 31 22:58:27 endeavouros kernel: iwlwifi 0000:06:00.0: WRT: Invalid buffer destination
Jul 31 22:58:28 endeavouros systemd-fsck[656]: fsck failed with exit status 4.
Jul 31 22:58:28 endeavouros systemd[1]: Failed to start File System Check on /dev/disk/by-uuid/fa06c2b8-eb2b-4b11-b73b-c0238e91887b.
-- Boot df4efe505d6c4728808ed776531c557b --
Jul 31 23:10:21 endeavouros kernel: tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xdc31f000-0xdc31ffff flags 0x200] vs dc31f000 4000
Jul 31 23:10:21 endeavouros kernel: tpm_crb MSFT0101:00: error -EBUSY: can't request region for resource [mem 0xdc31f000-0xdc31ffff]
Jul 31 23:10:21 endeavouros kernel: tpm_crb MSFT0101:00: probe with driver tpm_crb failed with error -16
  • inxi -Fxz:
System:
  Kernel: 6.8.7-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
  Desktop: KDE Plasma v: 6.0.4 Distro: EndeavourOS base: Arch Linux
Machine:
  Type: Desktop Mobo: BIOSTAR model: X370GT7 serial: <superuser required>
    UEFI: American Megatrends v: 5.13 date: 08/07/2018
CPU:
  Info: 8-core model: AMD Ryzen 7 2700X bits: 64 type: MT MCP arch: Zen+
    rev: 2 cache: L1: 768 KiB L2: 4 MiB L3: 16 MiB
  Speed (MHz): avg: 2450 high: 3700 min/max: 2200/3700 boost: enabled cores:
    1: 2200 2: 3200 3: 2200 4: 2200 5: 2200 6: 3700 7: 2200 8: 2200 9: 2200
    10: 2200 11: 2200 12: 2200 13: 2200 14: 2200 15: 2200 16: 3700
    bogomips: 118203
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
    vendor: Gigabyte driver: amdgpu v: kernel arch: RDNA-1 bus-ID: 0c:00.0
  Display: server: X.Org v: 21.1.13 with: Xwayland v: 23.2.6 driver: X:
    loaded: amdgpu unloaded: modesetting,radeon dri: radeonsi gpu: amdgpu
    resolution: 2560x1440~60Hz
  API: EGL v: 1.5 drivers: radeonsi,swrast platforms:
    active: x11,surfaceless,device inactive: gbm,wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.0.5-arch1.1
    glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 5700 XT (radeonsi
    navi10 LLVM 17.0.6 DRM 3.57 6.8.7-arch1-1)
  API: Vulkan Message: No Vulkan data available.
Audio:
  Device-1: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel
    bus-ID: 0c:00.1
  Device-2: AMD Family 17h HD Audio vendor: Biostar Microtech Intl Corp
    driver: snd_hda_intel v: kernel bus-ID: 0e:00.3
  API: ALSA v: k6.8.7-arch1-1 status: kernel-api
  Server-1: PipeWire v: 1.0.5 status: active
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Biostar Microtech Intl Corp driver: r8169 v: kernel port: f000
    bus-ID: 05:00.0
  IF: enp5s0 state: down mac: <filter>
  Device-2: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi
    v: kernel bus-ID: 06:00.0
  IF: wlan0 state: up mac: <filter>
Bluetooth:
  Device-1: Intel AX210 Bluetooth driver: btusb v: 0.8 type: USB
    bus-ID: 1-11:6
  Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 5.3
    lmp-v: 12
Drives:
  Local Storage: total: 2.53 TiB used: 39.96 GiB (1.5%)
  ID-1: /dev/nvme0n1 vendor: Kingston model: SKC3000D2048G size: 1.86 TiB
    temp: 21.9 C
  ID-2: /dev/sda vendor: A-Data model: SU630 size: 447.13 GiB
  ID-3: /dev/sdb vendor: Kingston model: SA400S37240G size: 223.57 GiB
  ID-4: /dev/sdc vendor: SanDisk model: Cruzer Blade size: 14.32 GiB
    type: USB
Partition:
  ID-1: / size: 10 GiB used: 221.9 MiB (2.2%) fs: overlay source: ERR-102
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 32.5 C mobo: N/A gpu: amdgpu temp: 35.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
  Memory: total: 16 GiB available: 15.57 GiB used: 3.32 GiB (21.3%)
  Processes: 371 Uptime: 1h 2m Init: systemd
  Packages: 1038 Compilers: clang: 17.0.6 gcc: 13.2.1 Shell: Bash v: 5.2.26
    inxi: 3.3.3
2

Adding module_blacklist=tpm-crb as a kernel boot argument might help.

3

I gave a look at the pages Kernel 5.11 probably doesn’t like my TPM settings (Asus X541UAK) and Changing boot options Permanently for an Existing Installation. Then:

  1. I do not have Grub. I use systemd-boot.
  2. I use dracut instead of mkinitcpio and grub-mkconfig.
  3. But I do have the modprobe.d on the folder etc. Can I create a new modprobe configuration file with the command blacklist tpm?

I checked other folders boot and efi:

[root@EndeavourOS /]# ls boot
amd-ucode.img
[root@EndeavourOS /]# ls efi
7672d332026846318e868f17ab40d4fb  EFI  loader
[root@EndeavourOS /]# ls efi/EFI
BOOT  Linux  systemd
[root@EndeavourOS /]# ls efi/EFI/BOOT/
BOOTX64.EFI
[root@EndeavourOS /]# ls efi/EFI/Linux/
[root@EndeavourOS /]# ls efi/EFI/systemd/
systemd-bootx64.efi
4

can you mount /home in emergency mode?

5

Yes, I can totally.

Well, I decided to mount all the partitions and to run the command to unmask the dev-tpmrm0.device. I rebooted into the SSD. The tpm_crb seemed to be fixed, but I still say the Bluetooth’s hci0 error. I did not pay attention to another error that always appeared since 31 July. It was fsck that failed to check the SSD NVMe m.2’s partition home. As I had already mounted them, I investigated it with the command lsblk -f and saw that the partition home’s mount point was empty. I made a research and found the two pages – Failed to start file system check on /dev/disk, dependency failed for /home, dependency failed for local file system and /dev/nvme1n1p1 requires a manual fsck.

Before performing fsck, I had to back some important things to my new 2 TB portable Kingston SSD. After finishing the back, I unmounted all the partitions. I ran the command sudo fsck /dev/sda2. It found an error that turned out to be a defective file on the folder asciidoctor.asciidoctor-vscode-* on the .vscode folder. It fixed the error. Thankfully, I did not lose anything.

I restarted the computer, and now it has booted properly. It has even mounted the /home folder properly. Even though it has resolved the issue, I faced two errors – Bluetooth’s hci0 error and “usb-11” error. I knew what this latter error was. I wanted my Logitech keyboard and mouse, connected to the Logitech Unifying USB receiver, to wake the computer up. Then I noticed that they stopped connecting, and I had to use the wired keyboard and mouse in emergency. I moved the Logitech Unifying USB receiver to the computer case’s front fascia’s USB entrance and reconnected the devices. I updated the devices via grep . /sys/bus/usb/devices/*/product and grep . /sys/bus/usb/devices/*/power/wakeup.

I investigated the Bluetooth’s error. I noticed that it said to be a malformed MSFT vendor. I shut the computer down and tidied up the Linux-compatible Bluetooth and Wi-Fi adapter. I booted and still saw the same Bluetooth error, but I checked that, at the KDE GUI, Bluetooth appeared to work and to be active. It is unclear to me why this error insists.

Now I want to mask the dev-tpmrm0.device, but I will receive again the new tpm_crb error. I do not know if with it, I will have a new fsck problem for my SSD NVMe m.2.

However, since the Logitech Unifying USB receiver was moved to the computer case’s front fascia, the keyboard, and the mouse slow down and fail a bit to answer because of a distance.

6

They do not seem related IMHO. The fsck errors sound like your real/actual problem (disk/FS failure).
If there is no system issue, or any other reasons, I suppose the tpm messages are not fatal/important enough to mask the driver, but now you know how to recover :wink: . So, you may test, or not :man_shrugging: .

7

Unfortunatley mount fails of anything in the fstab are blocking the boot, ending in rescue mode. This was visible in your log. systemd-fsck[814]: fsck failed with exit status 4. The other warnings and error messages are not blocking boot. Even with empty /home you still can log in and do rot tasks. Like @petsam says, the cause for the FS error may be either hardware related or maybe you powered off in the wrong moment. First backup! Check SMART data of your hard disk to find out if it is hardware related, because if it is, you have a repeating serious problem.

8

Despite these error and warning messages do not block the boot and are not fatal or important, I wanted to get rid of some errors.

I created new modprobe configuration files on the folder modproble.d on the folder etc, and ran dracut. Booting, they did not have effect. But I read the topic I cannot find grub file, and followed @pebcak’s suggestion. I added @kmonster’s suggestion module_blacklist=tpm-crb to /etc/kernel/cmdline and ran sudo reinstall-kernels. I booted and saw that it did not have effect either. I gave up.

As for the SSD NVMe m.2 and home partition problem, I decided to select only SSD ADATA SU630 as the only disk during the Calamares installer of Endeavour OS Live USB when I opted to erase. If I opted to partition the disks manually and pointed SSD NVMe m.2 to the partitions home and opt, the installer would always fail. I did it many times before, and the installer’s final step always failed. Therefore, the installer succeeded with only the SSD ADATA SU630 disk. After the succession, I had to point the SSD NVMe m.2 partitions home and opt to /etc/fstab. Of course that, I created the username folder and performed the command chown.

It is good for Endeavour OS Live USB developers to be aware of this issue.

But I made an investigation regarding SSD NVMe problems, I read the topic SSD not showing up, Unable to create a mount point. It seems that maybe I missed a few options that @BendTheKnee for the mount point.

Comparing my SSD NVMe m.2 partition home and the random partition options:

The mine:

# <file system>                           <mount point>  <type>  <options>                     <dump>  <pass>
UUID=fa06c2b8-eb2b-4b11-b73b-c0238e91887b /home           ext4    defaults,errors=remount-ro    0       1
UUID=47b48637-f135-41ea-a598-313bdbc26384 /opt            ext4    defaults                      0       2

The random partition example given by @BendTheKnee:

# <file system>                           <mount point>  <type>  <options>                     <dump>  <pass>
UUID=DEVICE_UUID                          /home           ext4    rw,relatime,nofail,user       0       2

Should I add the options nofail, relatime, rw and user to the partitions home and opt, and should I change 1 to 2 for the partition home?

9

nofail is ok for /home, relatime and rw should be default. I would not recommend user for /home for safety reasons. All that does not answer the question what the cause for the FS error was, or is. My recommendation is clearly: Check your hardware.

10

Good mroning, @kmonster and @petsam!

My SSD NVMe m.2 came again with the same fsck error. Finally I understood what happened. It turned out to be my 2 HDD WD Purple Surveillance. I was cutting many things from it and pasted on my SSD NVMe as a temporary backup because I was going to give it away to my uncle who wanted it.

Thankfully, the SSD NVMe m.2 did not die.

Cutting and pasting something from it caused the SSD NVMe m.2 to slow down and freeze.

After completing the backup from the HDD WD Purple to the SSD NVMe m.2, I was planning to move the backups from the SSD NVMe m.2 to my new portable 2 TB SSD Kingston, and merge several backups into one backup. I also was planning to move the backups from all the SSDs of a small storage size to the same portable SSD and merge them again into one backup.

Before fixing the SSD NVMe m.2 with fsck command, I had to back something from it to the portable SSD, but I have an idea – I am going to move everything from both the HDD WD Purple and the SSD NVMe to the portable SSD while using non-persistent and persistent Endeavour OS Live USB flash drives.

I do not know if you think it is a bad idea.

11

As I have finished the backups, I tested the command fsck, here is the log, @kmonster and @petsam:

$ sudo fsck /dev/nvme0n1p2
fsck from util-linux 2.40
e2fsck 1.47.0 (5-Feb-2023)
Home contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Orphan file (inode 12) block 13 is not clean.
Clear<y>? yes

Home: ***** FILE SYSTEM WAS MODIFIED *****
Home: 218339/121364480 files (0.9% non-contiguous), 13273580/485451089 blocks

It turned to be a defective file copied from the HDD to the SSD. Correct?

I am going to boot to the SSD NVMe m.2 to see if it’s OK.

12

Orphan files are deleted files that still have file metadata in the file system, but that cannot be accessed from the root directory. Cause is either a kernel bug or power outage in the wrong moment. First is i would say very unlikely, as ext code is pretty mature. It is certainly not the result from a copy process.