Ext4 fs error device nvme0n1p2 - Исправление ошибок и поиск оптимальных решений проблем

Index
» Newbie Corner
» Potentially broken EXT4 root filesystem, how should I proceed?

Pages: 1

#1 2019-02-14 21:02:45

yaogen: Member; Registered: 2018-08-03; Posts: 4

Potentially broken EXT4 root filesystem, how should I proceed?

During a reboot, fsck failed and boot stopped telling me to run fsck manually. I ran fsck manually and it passed with correcting several inodes. (side question, where can I find the logs of this failed boot etc?)

Rebooted again and now I see some weirdness in the filesystem. It’s limited to 78 files system wide (I think), and it approximates to the same amount of corrections I did before the reboot.

In journalctl I see errors similar to these:

EXT4-fs error (device nvme0n1p2): ext4_lookup:1574: inode #4833958: comm ls: iget: checksum invalid

In terminal I see messages like this:

ls: cannot access 'usr/lib32/libXdmcp.so.6.0.0': Bad message

… as well as (ls output):

lrwxrwxrwx  1 root root       17 May 31  2018 libXdmcp.so -> libXdmcp.so.6.0.0
-?????????  ? ?    ?           ?            ? libXdmcp.so.6.0.0

I was thinking I could reinstall the packages from where these broken files come and it could potentially fix my issues, but I reach out to you guys for some advice before I do anything.

Thanks,

#2 2019-02-14 22:37:59

yaogen: Member; Registered: 2018-08-03; Posts: 4

Re: Potentially broken EXT4 root filesystem, how should I proceed?

Continued tinkering and it may be that I’ve managed to fix my issues. Early times yet though.

I checked the filesystem and saw:

14130x messages like «Illegal block NN in inode MM»
3858x messages like «Block NN causes symlink to be too big»

This is what I did:

Rebooted into the live USB
Mounted a secondary drive.
fsck.ext4 -p [my root device]
fsck.ext4 -z [undo file on secondary drive] [my root device]
Stepped through all errors and allowed fsck to fix them
Rebooted into the system and opted to reinstall all packages (see script below)
Rebooted again …

All seems well, but I had to reinstall glib2 for some reason as neither spotify nor firefox started.

Script I used to reinstall all installed (non-AUR) packages:

#!/bin/bash

pacman -Q | awk '{ print $1 }' | sort > /tmp/pacman-installed.tmp
pacman -Qm | awk '{ print $1 }' | sort | comm -3 /tmp/pacman-installed.tmp - > /tmp/pacman-to-reinstall.tmp

pacman -S --noconfirm $(cat /tmp/pacman-to-reinstall.tmp)
rm /tmp/pacman-{to-reinstall,installed}.tmp

(cred Cerebral in topic https://bbs.archlinux.org/viewforum.php?id=34832)

Should I set this topic to solved?

Источник

View previous topic :: View next topic

Author

Message

xgivolari
n00b
n00b

Joined: 26 Jul 2021
Posts: 62

Posted: Fri Oct 01, 2021 12:15 pm Post subject: [SOLVED] NVMe drive fails on resume

Hello all,

Recently, I bought a Kioxia EXCERIA PLUS G2 M.2 NVMe drive for my desktop system. (MB: GIGABYTE B450M S2H, latest firmware version F62b with Ryzen 5 2600) Cloning my installation from an old hard drive onto the new SSD and booting from it went smoothly. The only problem is that the system always freezes when resuming from suspend. My first suspect was the nvidia driver, but removing that makes no difference. When suspending/resuming from terminal, I can at least quickly run dmesg. The system then seemingly does nothing for roughly a minute, only to reveal a kernel log with several errors. After this, any terminal input fails. Unfortunately, I cannot save the original dmesg log, so I have to type out its content manually from a picture I took with my phone:

Code:

nvme nvme0: Device not ready: aborting reset, CSTS=0x1

nvme nvme0: Removing after probe failure status: -19

nvme nvme0: Device not ready: aborting reset, CSTS=0x1

nvme0n1: detected capacity change from 9776773168 to 0

EXT4-fs error (device nvme0n1p2): ext4_get_inode_loc_noinmem:4444: inode #3063042: block 12061680: comm dmesg: unable to read itable block

EXT4-fs warning (device nvme0n1p2): ext4_end_bio:342: I/O error 10 writing to inode 3015764 starting block 8227588)

EXT4-fs warning (device nvme0n1p2): ext4_end_bio:342: I/O error 10 writing to inode 2097156 starting block 9052450)

Aborting journal on device nvme0n1p2-8.

Buffer I/O error on device nvme0n1p2, logical block 8921122

Buffer I/O error on device nvme0n1p2, logical block 8096260

Buffer I/O error on dev nvme0n1p2, logical block 6324224, lost sync page write

EXT4-fs (nvme0n1p2): Delayed block allocation failed for inode 1967449 at logical offset 14 with max blocks 2 with error 30

JBD2: Error -5 detected when updating journal superblock for nvme0n1p2-8.

<<insert several errors relating to I/O failure / journal abort, filesystem is remounted read-only>>

Kernel is latest 5.14.9, everything else is up to date as well.

Steps I have taken so far to solve this issue:

-removing proprietary nvidia drivers

-disabling PCIe ASPM in BIOS

-booting with nvme_core.default_ps_max_latency_us=0 to disable APST

-checking SMART status, (no issues), updating drive firmware, running fsck and e2fsck unmounted, regenerating journal

-disabling power management for the drive

So far, none if these things has made any difference. Do you know how I can get suspend and resume to work correctly? Thanks!

Last edited by xgivolari on Mon Oct 04, 2021 2:35 pm; edited 1 time in total

mike155
Advocate

Joined: 17 Sep 2010
Posts: 4312
Location: Frankfurt, Germany

Posted: Fri Oct 01, 2021 2:23 pm Post subject:

Seems to be similar to this: https://bbs.archlinux.org/viewtopic.php?id=258883

Quote:

I tried to move the drive from the front nvme slot to the back nvme slot, and sleeping worked. I think this is a fine workaround, but I’ll have to test this setup to see if it’s stable.

Does that help in your case? Anything else in that thread that could help?

You could also ask Google

Code:

nvme «not ready» after suspend

You’ll find many results…

DaggyStyle
Watchman

Joined: 22 Mar 2006
Posts: 5876

Posted: Fri Oct 01, 2021 3:10 pm Post subject:

worth while to check the bios if there is any suspend/resume entry for pci cards _________________ Only two things are infinite, the universe and human stupidity and I’m not sure about the former — Albert Einstein

xgivolari
n00b
n00b

Joined: 26 Jul 2021
Posts: 62

Posted: Sun Oct 03, 2021 3:38 pm Post subject:

@mike155 @DaggyStyle Thank you for your advice. After extensive digging through my BIOS settings, I was not able to find anything of help. At least I have discovered settings for AMD SVE and PCIe ASPM. From what I could gather by reading through other threads about this issue, it looks like this is an AM4 platform-specific thing. In my case at least, APST seems not to be at fault, and disabling it makes no difference.

DaggyStyle
Watchman

Joined: 22 Mar 2006
Posts: 5876

Posted: Sun Oct 03, 2021 6:27 pm Post subject:

can you check previous kernels? to see if it is a regression? _________________ Only two things are infinite, the universe and human stupidity and I’m not sure about the former — Albert Einstein

xgivolari
n00b
n00b

Joined: 26 Jul 2021
Posts: 62

Posted: Mon Oct 04, 2021 12:49 pm Post subject:

DaggyStyle wrote:

can you check previous kernels? to see if it is a regression?

I have tried with the most recent stable version of gentoo-sources, v5.10.68. It makes no difference.

xgivolari
n00b
n00b

Joined: 26 Jul 2021
Posts: 62

Posted: Mon Oct 04, 2021 1:31 pm Post subject:

UPDATE: After experimenting with manually writing into /sys/power/state, I have discovered that suspend2idle actually works! «echo freeze > /sys/power/state» or alternatively «echo s2idle > /sys/power/mem_sleep && echo mem > /sys/power/state» puts my system into a suspend state it can actually resume from. However, suspending via loginctl suspend or XFCE menu still does not work. I edited my /etc/elogind/elogind.conf to this:

SuspendState=mem

SuspendMode=s2idle

But it seems to make no difference.

UPDATE 2: It looks like loginctl can only suspend/resume properly from commandline. Entering loginctl suspend from XFCE results in failure as usual. Playing with the elogind.conf NvidiaSleep option seems to have no effect as well.

UPDATE 3: Loginctl suspend failing turns out to be a known issue as discussed in this thread. I fixed it by placing this script in /lib64/elogind/system/sleep/20-nvidia:

Code:

#!/bin/sh

case «${1-}» in

‘pre’)

/usr/bin/nvidia-sleep.sh suspend

;;

‘post’)

/usr/bin/nvidia-sleep.sh resume &

;;

*)

exit 1

;;

esac

Even though working suspend2ram would still be nice, this issue is for all other intents and purposes now solved.

Display posts from previous:

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum

Источник

Ubuntu 4.13.0-21.24-generic 4.13.13

I have a Razer Blade Stealth 2016. The first Ubuntu I installed was Ubuntu 17.04, which gave me this error after 2 weeks of usage. After that, I installed 16.04 and used it for MONTHS without any problems, until it produced the same error this week. I think it has to do with the ubuntu updates, because I did one recently and one today, just before this problem. Could be a coincidence though.

I notice the error when I try to save something on disk and it says me that the disk is in read-only mode:

lz@lz:/var/log$ touch something
touch: cannot touch ‘something’: Read-only file system

lz@lz:/var/log$ cat syslog
Jan 29 01:07:39 lz kernel: [62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0

lz@lz:/var/log$ dmesg
[62984.375393] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.377374] Aborting journal on device nvme0n1p2-8.
[62984.379343] EXT4-fs (nvme0n1p2): Remounting filesystem read-only
[62984.379516] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.381486] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.383484] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.385469] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.387278] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.389262] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.391252] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[62984.393341] EXT4-fs error (device nvme0n1p2): ext4_find_entry:1442: inode #26607929: comm updatedb.mlocat: checksumming directory block 0
[63285.618078] audit: type=1400 audit(1517195560.393:63): apparmor=»DENIED» operation=»capable» profile=»/usr/sbin/cupsd» pid=22495 comm=»cupsd» capability=12 capname=»net_admin»

Rebooting the ubuntu will give me a black terminal where I can run fsck /dev/nvm30n1p2 (something like that) and it fill fix a lot of orphaned inodes. The majority of time it boots back to the Ubuntu working good, but some times it boots to a broken ubuntu (no images, lots of things broken). I have to reinstall ubuntu then.

Every time I reinstall my Ubuntu, I have to try lots of times until it installs without an Input/Output error. When it installs, I can use it for some hours without having the problem, but if I run the software updates, it ALWAYS crashes and enters in read-only mode, specifically in the part that is installing kernel updates.

I noticed that Ubuntu installs updates automatically when they’re for security reasons. Could this be the reason my Ubuntu worked for months without the problem, but then an update was applied and it broke?

I thought that this bug was happening: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678184 and tried different nvme_core.default_ps_max_latency_us= combinations, all them gave errors. I just changed to 0 and I had no error while using ubuntu (however I didn’t test for a long time) but I still had the error after trying to update my ubuntu.

My Samsung 512gb SSD is:

SAMSUNG MZVLW512HMJP-00000, FW REV: CXY7501Q

on a Razer Blade Stealth.

I also asked this on ask ubuntu, without success: https://askubuntu.com/questions/998471/razer-blade-stealth-disk-corruption-fsck-needed-probably-samsung-ssd-bug-afte

Please help me, as I need this computer to work on lots of things :c
—
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: lz 1088 F…. pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 17.10
InstallationDate: Installed on 2018-01-30 (0 days ago)
InstallationMedia: Ubuntu 17.10 «Artful Aardvark» — Release amd64 (20180105.1)
MachineType: Razer Blade Stealth
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic.efi.signed root=UUID=0ca062da-7e8f-425a-88b1-1f784fb40346 ro quiet splash button.lid_init_state=open nvme_core.default_ps_max_latency_us=0
ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13
RelatedPackageVersions:
linux-restricted-modules-4.13.0-21-generic N/A
linux-backports-modules-4.13.0-21-generic N/A
linux-firmware 1.169.1
Tags: wayland-session artful
Uname: Linux 4.13.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 01/12/2017
dmi.bios.vendor: Razer
dmi.bios.version: 6.00
dmi.board.name: Razer
dmi.board.vendor: Razer
dmi.chassis.type: 9
dmi.chassis.vendor: Razer
dmi.modalias: dmi:bvnRazer:bvr6.00:bd01/12/2017:svnRazer:pnBladeStealth:pvr2.04:rvnRazer:rnRazer:rvr:cvnRazer:ct9:cvr:
dmi.product.family: 1A586752
dmi.product.name: Blade Stealth
dmi.product.version: 2.04
dmi.sys.vendor: Razer

Источник

today I crashed my boot partition. While is normally no problem due backups, I can’t write to the partition anymore.

root@hades ~ # touch /boot/a
touch: cannot touch '/boot/a': Structure needs cleaning

dmesg shows me:

[317873.920810] EXT4-fs error (device md2): ext4_find_dest_de:1932: inode #2: block 518: comm touch: bad entry in directory: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0, size=1024

Even after successfully umount the device, I can’t fsck

root@hades ~ # umount /boot
root@hades ~ # e2fsck /dev/md2
e2fsck 1.45.5 (07-Jan-2020)
/dev/md2 is in use.
e2fsck: Cannot continue, aborting.


root@hades ~ # fsck.ext4 /dev/md2
e2fsck 1.45.5 (07-Jan-2020)
/dev/md2 is in use.
e2fsck: Cannot continue, aborting.

I’m unable to reformat or destroy the partition:

root@hades ~ # wipefs /dev/md2
DEVICE OFFSET TYPE UUID                                 LABEL
md2    0x438  ext4 2112045a-2e84-4c69-8c67-d76e8ad7a13a boot
root@hades ~ # wipefs -a /dev/md2
wipefs: error: /dev/md2: probing initialization failed: Device or resource busy
root@hades ~ # mkfs.ext4 -L boot /dev/md2
mke2fs 1.45.5 (07-Jan-2020)
/dev/md2 contains a ext4 file system labelled 'boot'
    last mounted on /boot on Fri Sep 18 21:33:34 2020
Proceed anyway? (y,N) y
/dev/md2 is apparently in use by the system; will not make a filesystem here!

I also can’t stop the mdam array to set the while raid array to fail:

root@hades ~ # mdadm --stop /dev/md2 --force
mdadm: Cannot get exclusive access to /dev/md2:Perhaps a running process, mounted filesystem or active volume group?


root@hades ~ # mdadm /dev/md2 --fail /dev/nvme0n1p2 --remove /dev/nvme0n1p2
mdadm: set /dev/nvme0n1p2 faulty in /dev/md2
mdadm: hot removed /dev/nvme0n1p2 from /dev/md2
root@hades ~ # mdadm /dev/md2 --fail /dev/nvme1n1p2 --remove /dev/nvme1n1p2
mdadm: set device faulty failed for /dev/nvme1n1p2:  Device or resource busy

mdadm --add /dev/md2 /dev/nvme0n1p2

root@hades ~ # mdadm /dev/md2 --fail /dev/nvme1n1p2 --remove /dev/nvme1n1p2
mdadm: set /dev/nvme1n1p2 faulty in /dev/md2
mdadm: hot removed /dev/nvme1n1p2 from /dev/md2
root@hades ~ # mdadm /dev/md2 --fail /dev/nvme0n1p2 --remove /dev/nvme0n1p2
mdadm: set device faulty failed for /dev/nvme0n1p2:  Device or resource busy

fuser or lsof does now shoe any process except kernel threads:

root@hades ~ # lsof | grep md2
md2_raid1     262                              root  cwd       DIR                9,4     4096          2 /
md2_raid1     262                              root  rtd       DIR                9,4     4096          2 /
md2_raid1     262                              root  txt   unknown                                        /proc/262/exe
jbd2/md2-     599                              root  cwd       DIR                9,4     4096          2 /
jbd2/md2-     599                              root  rtd       DIR                9,4     4096          2 /
jbd2/md2-     599                              root  txt   unknown                                        /proc/599/exe
root@hades ~ # fuser -v /dev/md2
root@hades ~ # fuser -v /dev
                     USER        PID ACCESS COMMAND
/dev:                root     kernel mount /dev
                     root         57 .rc.. kdevtmpfs

I’m not using LVM, no userspace is installed:

root@hades ~ # vgs

Command 'vgs' not found, but can be installed with:

apt install lvm2

The mdadm RAID looks clean:

root@hades ~ # mdadm -D /dev/md2
/dev/md2:
           Version : 1.2
     Creation Time : Wed Jul 17 22:22:07 2019
        Raid Level : raid1
        Array Size : 523712 (511.44 MiB 536.28 MB)
     Used Dev Size : 523712 (511.44 MiB 536.28 MB)
      Raid Devices : 2
     Total Devices : 2
       Persistence : Superblock is persistent

       Update Time : Tue Sep 22 14:30:52 2020
             State : clean
    Active Devices : 2
   Working Devices : 2
    Failed Devices : 0
     Spare Devices : 0

Consistency Policy : resync

              Name : rescue:boot
              UUID : b8cce71f:11cb0913:e75f8623:0846cd86
            Events : 176

    Number   Major   Minor   RaidDevice State
       3     259        2        0      active sync   /dev/nvme0n1p2
       2     259        9        1      active sync   /dev/nvme1n1p2

I’m running Ubuntu 20.04.

Linux hades 5.4.0-47-generic #51-Ubuntu SMP Fri Sep 4 19:50:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linu

I can’t restart the server, because the system isn’t bootable now. Currently I do not have physical access to the machine.

I already shutdown all services except systemd, ssh, polkit, rsyslog and mdadm monitor.

How I could identify the source which is using the device?

Источник

Sep 27 02:54:01 proxmox systemd[1]: Started Proxmox VE replication runner.
Sep 27 02:54:04 proxmox kernel: [2908335.387198] nvme nvme0: Removing after probe failure status: -19
Sep 27 02:54:04 proxmox kernel: [2908335.407127] blk_update_request: I/O error, dev nvme0n1, sector 262865288 op 0x1:(WRITE) flags 0x8800 phys_seg 1 prio class 0
Sep 27 02:54:04 proxmox kernel: [2908335.407142] blk_update_request: I/O error, dev nvme0n1, sector 2048 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 0
Sep 27 02:54:04 proxmox kernel: [2908335.407145] Aborting journal on device nvme0n1p1-8.
Sep 27 02:54:04 proxmox kernel: [2908335.407154] JBD2: Error -5 detected when updating journal superblock for nvme0n1p1-8.
Sep 27 02:54:04 proxmox systemd[1]: Stopped target Local File Systems.
Sep 27 02:54:04 proxmox systemd[1]: Unmounting /mnt/NVMEDISK...
Sep 27 02:54:04 proxmox umount[24549]: umount: /mnt/NVMEDISK: target is busy.
Sep 27 02:54:04 proxmox systemd[1]: mnt-NVMEDISK.mount: Mount process exited, code=exited, status=32/n/a
Sep 27 02:54:04 proxmox systemd[1]: Failed unmounting /mnt/NVMEDISK.
Sep 27 02:54:04 proxmox systemd[1]: mnt-NVMEDISK.mount: Unit is bound to inactive unit dev-disk-byx2duuid-d31acd69x2df784x2d4ba9x2dbfefx2d40036196c03e.device. Stopping, too.
Sep 27 02:54:04 proxmox systemd[1]: Unmounting /mnt/NVMEDISK...
Sep 27 02:54:04 proxmox umount[24550]: umount: /mnt/NVMEDISK: target is busy.
Sep 27 02:54:04 proxmox systemd[1]: mnt-NVMEDISK.mount: Mount process exited, code=exited, status=32/n/a
Sep 27 02:54:04 proxmox systemd[1]: Failed unmounting /mnt/NVMEDISK.
Sep 27 02:54:04 proxmox systemd[1]: mnt-NVMEDISK.mount: Unit is bound to inactive unit dev-disk-byx2duuid-d31acd69x2df784x2d4ba9x2dbfefx2d40036196c03e.device. Stopping, too.
Sep 27 02:54:04 proxmox systemd[1]: Unmounting /mnt/NVMEDISK...
Sep 27 02:54:04 proxmox umount[24551]: umount: /mnt/NVMEDISK: target is busy.
Sep 27 02:54:04 proxmox systemd[1]: mnt-NVMEDISK.mount: Mount process exited, code=exited, status=32/n/a
Sep 27 02:54:04 proxmox systemd[1]: Failed unmounting /mnt/NVMEDISK.
Sep 27 02:54:04 proxmox systemd[1]: mnt-NVMEDISK.mount: Unit is bound to inactive unit dev-disk-byx2duuid-d31acd69x2df784x2d4ba9x2dbfefx2d40036196c03e.device. Stopping, too.
Sep 27 02:54:04 proxmox systemd[1]: Unmounting /mnt/NVMEDISK...
Sep 27 02:54:04 proxmox umount[24552]: umount: /mnt/NVMEDISK: target is busy.
Sep 27 02:54:04 proxmox systemd[1]: mnt-NVMEDISK.mount: Mount process exited, code=exited, status=32/n/a
Sep 27 02:54:04 proxmox systemd[1]: Failed unmounting /mnt/NVMEDISK.
Sep 27 02:54:04 proxmox systemd[1]: mnt-NVMEDISK.mount: Unit is bound to inactive unit dev-disk-byx2duuid-d31acd69x2df784x2d4ba9x2dbfefx2d40036196c03e.device. Stopping, too.
Sep 27 02:54:04 proxmox systemd[1]: Unmounting /mnt/NVMEDISK...
Sep 27 02:54:04 proxmox umount[24553]: umount: /mnt/NVMEDISK: target is busy.
Sep 27 02:54:04 proxmox systemd[1]: mnt-NVMEDISK.mount: Mount process exited, code=exited, status=32/n/a
Sep 27 02:54:04 proxmox systemd[1]: Failed unmounting /mnt/NVMEDISK.
Sep 27 02:54:04 proxmox systemd[1]: mnt-NVMEDISK.mount: Unit is bound to inactive unit dev-disk-byx2duuid-d31acd69x2df784x2d4ba9x2dbfefx2d40036196c03e.device. Stopping, too.
Sep 27 02:54:04 proxmox systemd[1]: Unmounting /mnt/NVMEDISK...
Sep 27 02:54:04 proxmox umount[24554]: umount: /mnt/NVMEDISK: target is busy.
Sep 27 02:54:04 proxmox systemd[1]: mnt-NVMEDISK.mount: Mount process exited, code=exited, status=32/n/a
Sep 27 02:54:04 proxmox systemd[1]: Failed unmounting /mnt/NVMEDISK.
Sep 27 02:54:04 proxmox systemd[1]: mnt-NVMEDISK.mount: Unit is bound to inactive unit dev-disk-byx2duuid-d31acd69x2df784x2d4ba9x2dbfefx2d40036196c03e.device. Stopping, too.
Sep 27 02:54:04 proxmox systemd[1]: Unmounting /mnt/NVMEDISK...
Sep 27 02:54:04 proxmox umount[24555]: umount: /mnt/NVMEDISK: target is busy.

Источник

Мои замораживания человечности и затем показывают черный экран с текстами ошибки цикличного выполнения:

systemd-journald: failed to write entry, ignoring: read-only file system

ext4-fs error device nvme0n1p2 ext4_find_entry:1454: inode #22152700: comm gdm-seesion-wor: reading directory lblock 0

Что это об и как я могу решить это?

Править: У меня также была ошибка Buffer I/0 error on device nvme0n1p2

РЕДАКТИРОВАНИЕ 2: Я смог загрузиться однажды и протестировать исправность диска с smartmontools. Результат передается (но проблема все еще состоит):

Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       KXG5AZNV512G TOSHIBA
Serial Number:                      385S1046T31Q
Firmware Version:                   5106AALA
PCI Vendor/Subsystem ID:            0x1179
IEEE OUI Identifier:                0x00080d
Total NVM Capacity:                 512.110.190.592 [512 GB]
Unallocated NVM Capacity:           0
Controller ID:                      0
Number of Namespaces:               1
Namespace 1 Size/Capacity:          512.110.190.592 [512 GB]
Namespace 1 Formatted LBA Size:     512
Local Time is:                      Fri Jan 31 14:18:35 2020 CET
Firmware Updates (0x14):            2 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL *Other*
Optional NVM Commands (0x005f):     Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat *Other*
Maximum Data Transfer Size:         512 Pages
Warning  Comp. Temp. Threshold:     78 Celsius
Critical Comp. Temp. Threshold:     82 Celsius
Namespace 1 Features (0x02):        NA_Fields

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     8.00W       -        -    0  0  0  0        0       0
 1 +     3.90W       -        -    1  1  1  1        0       0
 2 +     2.00W       -        -    2  2  2  2        0       0
 3 -   0.0500W       -        -    3  3  3  3     1500    1500
 4 -   0.0050W       -        -    4  4  4  4     6000   14000
 5 -   0.0030W       -        -    5  5  5  5    50000   80000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         2
 1 -    4096       0         1

=== 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:                        30 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    3%
Data Units Read:                    5.734.991 [2,93 TB]
Data Units Written:                 6.433.509 [3,29 TB]
Host Read Commands:                 205.819.666
Host Write Commands:                76.731.654
Controller Busy Time:               437
Power Cycles:                       1.362
Power On Hours:                     2.989
Unsafe Shutdowns:                   274
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               30 Celsius

Error Information (NVMe Log 0x01, max 128 entries)
No Errors Logged

РЕДАКТИРОВАНИЕ 3: кажется, что мой SSD имеет некоторый дефект. Я вошел в контакт с Lenovo. Они отправят мне новый SSD в обмен на мой поврежденный.

Трудно для веры этому может произойти точно так же, как это, как smartctl показал мне, диск имеет a Percentage Used: 3% и ноутбуку даже не 2 года. Что-нибудь я могу сделать для улучшения исправности диска в будущем?

РЕДАКТИРОВАНИЕ 4: Я был успешен в начальной загрузке однажды (от 50 попыток), я смог к сдвигу времени назад к более старому устойчивому состоянию, с тех пор больше никаких ошибок (начиная с теперь, по крайней мере), машина, работающая как новорожденный! Я успешно обновил все, никакие ошибки здесь также. Я сбросил свой nvme контроллер и работал sudo fsck -f /dev/nvme0np2, в котором все тесты передали (благодарит @xenoid и @heynnema). Я нашел эту ссылку, которая описала те же признаки, которые я имел; решение состояло в том, чтобы заменить SSD и материнскую плату. Не уверенный все же, если это относится ко мне также.

РЕДАКТИРОВАНИЕ 5: Новые обновления: таким образом, сначала я, проверилось, временно устанавливал Windows, но я хочу сохранить это как свое последнее средство, так как я должен был бы восстановить свою целую систему Linux. Таким образом, я думал, что мог запустить Windows по Живому USB, но нет, это не возможный, Windows, только когда-либо позволяет полную установку (игнорирующий трудные обходные решения). Таким образом, я думал, что, возможно, мог запустить программное обеспечение Utility, предлагаемое Lenovo с помощью Вина, но это также не работало как ожидалось. Используя FreeDOS (как предложенный в видео YouTube) мог бы работать, но еще не попробовали его, также я не уверен, где найти просто простой файл ISO встроенного микропрограммного обеспечения Toshiba, в котором я нуждался бы. Странно, мне не удалось найти мою модель NVMe на веб-сайте встроенного микропрограммного обеспечения Toshiba. Затем я столкнулся с fwupd. Какой большой инструмент, именно так мне нравится он! И Lenovo даже добавила поддержку моей модели Thinkpad, T480s, к LVFS!Отлично! Но не много встроенного микропрограммного обеспечения загружается все же для моей модели. Мой SSD Toshiba однако перечислен в LVFS, но новое встроенное микропрограммное обеспечение (как предложенный с веб-сайта Dell) еще не загружается. Я вошел в контакт с Lenovo об этом, для ускорения вещей. Я также вошел в контакт с Richard Hughes (создатель LVFS) для просьбы его справку. Так как мой Ноутбук не страдает от ошибки только в данный момент, я буду ожидать некоторое время, возможно, новые разработки подходят. Так, как Вы видите, его odysee для меня и все еще движения Я очень благодарен за всю справку сообщества и сообщите мне, есть ли у Вас больше идей и мыслей!

Редактирование 6: Я пытался использовать FreeDOS Живой USB для установки встроенного микропрограммного обеспечения .exe файлы, которые я нашел на Lenovo и домашней странице Dell. Но они оба дали мне высказывание сообщения об ошибке cannot be executed in DOS или что-то как этот. Это происходит, вероятно, из-за этих .exe файлов быть служебным программным обеспечением, что Lenovo и предложение Dell, с GUI и так далее. Таким образом для петляния я должен был бы на самом деле установить Windows временно на моем Ноутбуке.

РЕДАКТИРОВАНИЕ 7: Lenovo отправила мне новый SSD, на этот раз Samsung. Я заменил его своим дефектным SSD, установленным Windows, выполнил микропрограммное использование обновлений Lenovo Vantage (на всякий случай). Я хотел все актуальные встроенные микропрограммные обеспечения, прежде, чем установить Ubuntu 19.10, которая работает действительно великолепно! Особенно kernel-built-in драйверы Nvidia являются просто благословением, ошибками старого сообщения из Ubuntu 18.04. все исчезаются.

Источник