Hi,

I have issue with KDE Neon not detecting my Crucial P5 SSD. It works on other distros that I have tried (KDE Manjaro and Elementary OS) and on Windows 10.

The problems started during installation from Live USB. The SSD would not appear in partition selection step of installation. After rebooting from Live USB installation SSD was not detected in BIOS or Windows (while prior booting to Live USB was) and I had to unplug the PC from the power and plug in again for SSD to reappear (in BIOS and Windows). In rare occasions SSD would actually appear in KDE partition manager but it would fail to create new partitions. I have managed to create new partitions with GParted (when SSD was available) and then proceed with installation (I use /home and /swap on problematic SSD). After logging in into plasma session the problems continued - in rare occasions everything works perfectly but in most cases I just see black screen with mouse pointer.

Here is output from fdisk -l when SSD is working:

Code: Select all

Disk /dev/nvme0n1: 931,53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 980 PRO 1TB                 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: D6210730-D20F-4FA1-90C0-4FFA1B120C8F

Device              Start        End    Sectors   Size Type
/dev/nvme0n1p1       2048     206847     204800   100M EFI System
/dev/nvme0n1p2     206848     239615      32768    16M Microsoft reserved
/dev/nvme0n1p3     239616 1571825491 1571585876 749,4G Microsoft basic data
/dev/nvme0n1p4 1571825664 1572863999    1038336   507M Windows recovery environment
/dev/nvme0n1p5 1573888000 1953525134  379637135   181G Linux filesystem
/dev/nvme0n1p6 1572864000 1573887999    1024000   500M EFI System

Partition table entries are not in disk order.


Disk /dev/nvme1n1: 931,53 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: CT1000P5SSD8                           
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 09B4FB46-A65C-473C-BB20-61C203231E15

Device             Start        End   Sectors   Size Type
/dev/nvme1n1p1      2048      34815     32768    16M Microsoft reserved
/dev/nvme1n1p2     34816  976777215 976742400 465,8G Microsoft basic data
/dev/nvme1n1p3 976777216  993554431  16777216     8G Linux swap
/dev/nvme1n1p4 993554432 1953523711 959969280 457,8G Linux filesystem


I have also noticed if I don't login to plasma session and use only tty session everything works.

Here is the output from dmesg (only part related to nvme fail) when it fails to load:

Code: Select all

[   19.719136] nvme 0000:4c:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x0010 address=0xffae0000 flags=0x0000]
[   49.820561] nvme nvme1: I/O 903 QID 10 timeout, aborting
[   49.820576] nvme nvme1: I/O 388 QID 24 timeout, aborting
[   49.820582] nvme nvme1: I/O 386 QID 25 timeout, aborting
[   49.820586] nvme nvme1: I/O 133 QID 26 timeout, aborting
[   66.148102] fbcon: Taking over console
[   66.148181] Console: switching to colour frame buffer device 128x48
[   80.471156] nvme nvme1: I/O 11 QID 0 timeout, reset controller
[   80.471236] nvme nvme1: I/O 903 QID 10 timeout, reset controller
[  147.402803] nvme nvme1: Device not ready; aborting reset, CSTS=0x1
[  147.419291] blk_update_request: I/O error, dev nvme1n1, sector 1069629488 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  147.419299] nvme nvme1: Abort status: 0x371
[  147.419344] nvme nvme1: Abort status: 0x371
[  147.419345] nvme nvme1: Abort status: 0x371
[  147.419346] nvme nvme1: Abort status: 0x371
[  147.419534] blk_update_request: I/O error, dev nvme1n1, sector 1069469832 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  147.419541] blk_update_request: I/O error, dev nvme1n1, sector 1069658208 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  147.419637] blk_update_request: I/O error, dev nvme1n1, sector 1069637664 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  152.962922] nvme nvme1: Device not ready; aborting reset, CSTS=0x1
[  152.962946] nvme nvme1: Removing after probe failure status: -19
[  158.482937] nvme nvme1: Device not ready; aborting reset, CSTS=0x1
[  158.483065] nvme1n1: detected capacity change from 1953525168 to 0
[  158.483083] Buffer I/O error on dev nvme1n1p4, logical block 9437218, lost async page write
[  158.483083] blk_update_request: I/O error, dev nvme1n1, sector 1471968480 op 0x1:(WRITE) flags 0x800 phys_seg 1 prio class 0
[  158.483126] Aborting journal on device nvme1n1p4-8.
[  158.483157] Buffer I/O error on dev nvme1n1p4, logical block 9437219, lost async page write
[  158.483179] Buffer I/O error on dev nvme1n1p4, logical block 59801600, lost sync page write
[  158.483202] Buffer I/O error on dev nvme1n1p4, logical block 9437220, lost async page write
[  158.483245] JBD2: Error -5 detected when updating journal superblock for nvme1n1p4-8.
[  158.483269] Buffer I/O error on dev nvme1n1p4, logical block 9437223, lost async page write
[  158.483325] blk_update_request: I/O error, dev nvme1n1, sector 1069118248 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  158.483327] EXT4-fs error (device nvme1n1p4) in ext4_reserve_inode_write:5755: Journal has aborted
[  158.483331] blk_update_request: I/O error, dev nvme1n1, sector 1073246336 op 0x0:(READ) flags 0x3000 phys_seg 1 prio class 0
[  158.483334] Buffer I/O error on dev nvme1n1p4, logical block 9437224, lost async page write
[  158.483334] EXT4-fs error (device nvme1n1p4): ext4_dirty_inode:5957: inode #2359388: comm Thread (pooled): mark_inode_dirty error
[  158.483341] EXT4-fs error (device nvme1n1p4) in ext4_dirty_inode:5959: Journal has aborted
[  158.483346] EXT4-fs error (device nvme1n1p4): ext4_journal_check_start:83: comm Thread (pooled): Detected aborted journal
[  158.483355] Buffer I/O error on dev nvme1n1p4, logical block 0, lost sync page write
[  158.483357] EXT4-fs (nvme1n1p4): I/O error while writing superblock
[  158.483359] EXT4-fs (nvme1n1p4): Remounting filesystem read-only
[  158.483367] EXT4-fs error (device nvme1n1p4): ext4_read_inode_bitmap:201: comm plasma_session: Cannot read inode bitmap - block_group = 304, inode_bitmap = 9961488
[  158.483382] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359546: comm kded5: reading directory lblock 0
[  158.483391] Buffer I/O error on dev nvme1n1p4, logical block 9437226, lost async page write
[  158.483500] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359546: comm kded5: reading directory lblock 0
[  158.483523] Buffer I/O error on dev nvme1n1p4, logical block 9437227, lost async page write
[  158.483549] Buffer I/O error on dev nvme1n1p4, logical block 0, lost sync page write
[  158.483565] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359546: comm kded5: reading directory lblock 0
[  158.483583] EXT4-fs (nvme1n1p4): I/O error while writing superblock
[  158.483626] blk_update_request: I/O error, dev nvme1n1, sector 1069731856 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
[  158.483631] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359546: comm kded5: reading directory lblock 0
[  158.483640] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359546: comm kded5: reading directory lblock 0
[  158.483655] EXT4-fs (nvme1n1p4): I/O error while writing superblock
[  158.483675] EXT4-fs warning (device nvme1n1p4): ext4_end_bio:342: I/O error 10 writing to inode 2359324 starting block 133716483)
[  158.483707] EXT4-fs (nvme1n1p4): I/O error while writing superblock
[  158.483733] blk_update_request: I/O error, dev nvme1n1, sector 1069052024 op 0x1:(WRITE) flags 0x103000 phys_seg 1 prio class 0
[  158.483737] EXT4-fs (nvme1n1p4): failed to convert unwritten extents to written extents -- potential data loss!  (inode 2359324, error -30)
[  158.483742] Buffer I/O error on device nvme1n1p4, logical block 9522178
[  158.492969] EXT4-fs (nvme1n1p4): I/O error while writing superblock
[  158.507106] EXT4-fs (nvme1n1p4): I/O error while writing superblock
[  158.507816] EXT4-fs (nvme1n1p4): I/O error while writing superblock
[  158.508878] EXT4-fs (nvme1n1p4): I/O error while writing superblock
[  158.509818] JBD2: Error while async write back metadata bh 9437199.
[  158.509887] JBD2: Error while async write back metadata bh 9437218.
[  158.509888] JBD2: Error while async write back metadata bh 9437219.
[  158.511313] JBD2: Error while async write back metadata bh 9437220.
[  158.512004] JBD2: Error while async write back metadata bh 9437223.
[  158.512647] JBD2: Error while async write back metadata bh 9437224.
[  158.512648] JBD2: Error while async write back metadata bh 9437226.
[  158.512649] JBD2: Error while async write back metadata bh 9437227.
[  158.512658] JBD2: Error while async write back metadata bh 9437239.
[  158.515261] JBD2: Error while async write back metadata bh 9437240.
[  158.515269] JBD2: Error while async write back metadata bh 9437258.
[  158.516528] JBD2: Error while async write back metadata bh 9437339.
[  158.517172] JBD2: Error while async write back metadata bh 9437407.
[  158.517817] JBD2: Error while async write back metadata bh 9437523.
[  158.518420] JBD2: Error while async write back metadata bh 9437525.
[  158.519005] JBD2: Error while async write back metadata bh 9445408.
[  158.519567] JBD2: Error while async write back metadata bh 9445424.
[  158.520109] JBD2: Error while async write back metadata bh 9445431.
[  158.520624] JBD2: Error while async write back metadata bh 9445432.
[  158.521131] JBD2: Error while async write back metadata bh 9445434.
[  158.521622] JBD2: Error while async write back metadata bh 9445436.
[  158.522097] JBD2: Error while async write back metadata bh 9445457.
[  158.522557] JBD2: Error while async write back metadata bh 9445471.
[  158.523019] JBD2: Error while async write back metadata bh 9961472.
[  158.523447] JBD2: Error while async write back metadata bh 9961473.
[  168.723112] EXT4-fs error: 593 callbacks suppressed
[  168.723115] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359302: comm systemd: reading directory lblock 0
[  168.723359] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359302: comm systemd: reading directory lblock 0
[  169.177273] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359316: comm login: reading directory lblock 0
[  169.179000] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359316: comm login: reading directory lblock 0
[  169.179048] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359316: comm login: reading directory lblock 0
[  169.179171] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359316: comm login: reading directory lblock 0
[  169.752612] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359302: comm systemd: reading directory lblock 0
[  169.753070] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359302: comm systemd: reading directory lblock 0
[  169.753187] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359302: comm systemd: reading directory lblock 0
[  169.754104] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359302: comm systemd: reading directory lblock 0
[  181.919742] EXT4-fs error: 201 callbacks suppressed
[  181.919745] EXT4-fs error (device nvme1n1p4): __ext4_get_inode_loc_noinmem:4445: inode #2359639: block 9437237: comm sudo: unable to read itable block
[  234.442140] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359302: comm bash: reading directory lblock 0
[  234.443290] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359302: comm bash: reading directory lblock 0
[  234.449392] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359302: comm bash: reading directory lblock 0
[  234.450022] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359302: comm bash: reading directory lblock 0
[  237.260112] EXT4-fs error (device nvme1n1p4): __ext4_get_inode_loc_noinmem:4445: inode #2359639: block 9437237: comm sudo: unable to read itable block
[  237.282328] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359302: comm systemd: reading directory lblock 0
[  237.284329] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359302: comm systemd: reading directory lblock 0
[  237.284357] EXT4-fs error (device nvme1n1p4): __ext4_find_entry:1524: inode #2359302: comm systemd: reading directory lblock 0


I have found someone suggesting adding nvme_core.default_ps_max_latency_us to grub but it didn't help. GRUB:

Code: Select all

# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nvme_core.default_ps_max_latency_us=5500"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"


Other relevant info:
Secure boot = disabled
Fast boot = disabled

Specs:
MBO: Gigabyte B550 Vision d
CPU: AMD Ryzen 9 5950X
GPU: Asus RTX 3090
SSD1: Samsung 980 Pro 1TB
SSD2: Crucial P5 1TB
RAM: 32 GB DDR4

I would appreciate any help as I am out of options.

Thanks,
Dorian

Hi, same problem here with exactly the same drive nvme Crucial P5. After trying to install latest neon the only way to recover the nvme is to shutdown the PC and boot it again.
Did you ever solve this problem? I havent found much info on the internet. It seems nobody knows and I also filed a bug in KDE bugs but I doubt it would seen.

Unfortunately I did not manage to solve the issue. I eventually went with Kubuntu as I did not have issues with it.

Thanks, I am on Kubuntu at the moment and it works perfectly fine Im just furious I couldnt find and answer to this weird issue on happening with Neon.

Until it is not too late, I recommend you recover all your data from your SSD using services specified in this domain, like salvagedata.com. I have personally used it in the past, which has saved me from lots of stress. Nowadays, you can't trust SSDs or Hard drives for storing data, especially when everyone has important personal and work files. I prefer storing all my data on cloud storage. I do this to not take any risks and keep my important files safe and secure. Even if my laptop gets robbed or lost, my data will stay safe, and I will have access to it no matter what.