After Upgrade to Fedora 40 2nd NVME is not usable and therefore boot takes up 5 - 15 mins

inkyous · May 1, 2024, 8:15am

I use Fedora since 37 and so far it was flawless.
During Update from 39 → 40 almost everything went wrong.

Some Errors during installation led to blackscreen with no options.

So I reinstalled Fedora from scratch but since that the 2nd nvme drive isn’t working.
I use Fedora KDE, the KDE Partitionmanager shows the following:

The unusable nvme is selected. If I try to create a new Table it throws an error

Befehl: sfdisk --wipe=always /dev/nvme1n1
Create new Partitionstable on the device „/dev/nvme1n1: Error
Create new Partitionstable (Type: gpt) on „/dev/nvme1n1“: Error
I translated it from German

gparted doesn’t list the Drive at all same for fdisk -l

sudo fdisk -l
Disk /dev/nvme0n1: 931,51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WD_BLACK SN770 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: D404B508-32E5-41AE-9A84-10F255F31DA0

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1230847 1228800 600M EFI System
/dev/nvme0n1p2 1230848 3327999 2097152 1G Linux extended boot
/dev/nvme0n1p3 3328000 1953523711 1950195712 929,9G Linux filesystem

Disk /dev/zram0: 8 GiB, 8589934592 bytes, 2097152 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
inkY@inkY:~$

I think this leads to a slower Boot, It needs from 5 - 15 minutes after update.
Before it took >2mins

systemd-analyze

Startup finished in 16.738s (firmware) + 1.881s (loader) + 3.733s (kernel) + 4min 1.672s (initrd) + 1min 30.468s (userspace) = 5min 54.496s
graphical.target reached after 1min 30.452s in userspace.

systemd-analyze blame

4min 2.031s sys-module-fuse.device
4min 1.995s sys-devices-platform-serial8250-serial8250:0-serial8250:0.19-tty-ttyS19.device
4min 1.995s dev-ttyS19.device
4min 1.988s dev-ttyS16.device
4min 1.988s sys-devices-platform-serial8250-serial8250:0-serial8250:0.16-tty-ttyS16.device
4min 1.986s dev-ttyS18.device
4min 1.986s sys-devices-platform-serial8250-serial8250:0-serial8250:0.18-tty-ttyS18.device
4min 1.985s dev-ttyS0.device
4min 1.985s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
4min 1.984s dev-ttyS1.device
4min 1.984s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
4min 1.983s dev-ttyS28.device
4min 1.983s sys-devices-platform-serial8250-serial8250:0-serial8250:0.28-tty-ttyS28.device
4min 1.982s sys-devices-platform-serial8250-serial8250:0-serial8250:0.10-tty-ttyS10.device
4min 1.982s dev-ttyS10.device
4min 1.982s dev-ttyS12.device
4min 1.982s sys-devices-platform-serial8250-serial8250:0-serial8250:0.12-tty-ttyS12.device
4min 1.981s dev-ttyS25.device
4min 1.981s sys-devices-platform-serial8250-serial8250:0-serial8250:0.25-tty-ttyS25.device
4min 1.981s dev-ttyS20.device
4min 1.981s sys-devices-platform-serial8250-serial8250:0-serial8250:0.20-tty-ttyS20.device
4min 1.981s dev-ttyS21.device
4min 1.981s sys-devices-platform-serial8250-serial8250:0-serial8250:0.21-tty-ttyS21.device
4min 1.981s sys-devices-platform-serial8250-serial8250:0-serial8250:0.13-tty-ttyS13.device
4min 1.981s dev-ttyS13.device
4min 1.980s sys-devices-platform-serial8250-serial8250:0-serial8250:0.11-tty-ttyS11.device
4min 1.980s dev-ttyS11.device
4min 1.980s dev-ttyS2.device
4min 1.980s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
4min 1.980s dev-ttyS30.device
4min 1.980s sys-devices-platform-serial8250-serial8250:0-serial8250:0.30-tty-ttyS30.device
4min 1.979s dev-ttyS23.device
4min 1.979s sys-devices-platform-serial8250-serial8250:0-serial8250:0.23-tty-ttyS23.device
4min 1.979s dev-ttyS26.device
4min 1.979s sys-devices-platform-serial8250-serial8250:0-serial8250:0.26-tty-ttyS26.device
4min 1.978s dev-ttyS17.device
4min 1.978s sys-devices-platform-serial8250-serial8250:0-serial8250:0.17-tty-ttyS17.device
4min 1.978s dev-ttyS8.device
4min 1.978s sys-devices-platform-serial8250-serial8250:0-serial8250:0.8-tty-ttyS8.device
4min 1.978s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
4min 1.978s dev-ttyS3.device
4min 1.977s dev-ttyS14.device
4min 1.977s sys-devices-platform-serial8250-serial8250:0-serial8250:0.14-tty-ttyS14.device
4min 1.977s dev-ttyS15.device
4min 1.977s sys-devices-platform-serial8250-serial8250:0-serial8250:0.15-tty-ttyS15.device
4min 1.977s sys-devices-platform-serial8250-serial8250:0-serial8250:0.24-tty-ttyS24.device
4min 1.977s dev-ttyS24.device
4min 1.977s dev-ttyS22.device
4min 1.977s sys-devices-platform-serial8250-serial8250:0-serial8250:0.22-tty-ttyS22.device
4min 1.977s sys-devices-platform-serial8250-serial8250:0-serial8250:0.5-tty-ttyS5.device
4min 1.977s dev-ttyS5.device
4min 1.976s sys-devices-platform-serial8250-serial8250:0-serial8250:0.7-tty-ttyS7.device
4min 1.976s dev-ttyS7.device
4min 1.976s dev-ttyS31.device
4min 1.976s sys-devices-platform-serial8250-serial8250:0-serial8250:0.31-tty-ttyS31.device
4min 1.975s dev-ttyS27.device
4min 1.975s sys-devices-platform-serial8250-serial8250:0-serial8250:0.27-tty-ttyS27.device
4min 1.975s dev-ttyS29.device
4min 1.975s sys-devices-platform-serial8250-serial8250:0-serial8250:0.29-tty-ttyS29.device
4min 1.975s sys-devices-platform-serial8250-serial8250:0-serial8250:0.4-tty-ttyS4.device
4min 1.975s dev-ttyS4.device
4min 1.974s sys-devices-platform-serial8250-serial8250:0-serial8250:0.6-tty-ttyS6.device
4min 1.974s dev-ttyS6.device
4min 1.973s dev-ttyS9.device
4min 1.973s sys-devices-platform-serial8250-serial8250:0-serial8250:0.9-tty-ttyS9.device
4min 1.971s sys-module-configfs.device
4min 1.946s sys-subsystem-net-devices-enp7s0.device
4min 1.946s sys-devices-pci0000:00-0000:00:1c.2-0000:07:00.0-net-enp7s0.device
3min 47.911s dev-disk-by\x2duuid-0752b590\x2de6da\x2d47db\x2d81c4\x2d1f1725c2e8f5.device
3min 47.911s dev-disk-by\x2dlabel-fedora.device
3min 47.911s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b444a485aa7b5\x2dpart3.device
3min 47.911s sys-devices-pci0000:00-0000:00:06.0-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p3.device
3min 47.911s dev-disk-by\x2dpartuuid-47e47757\x2d8bc7\x2d4616\x2da3cd\x2db14826d034f7.device
3min 47.911s dev-disk-by\x2ddiskseq-1\x2dpart3.device
3min 47.911s dev-disk-by\x2did-nvme\x2dWD_BLACK_SN770_1TB_22424Y478313\x2dpart3.device
3min 47.911s dev-nvme0n1p3.device
3min 47.911s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart3.device
3min 47.911s dev-disk-by\x2did-nvme\x2dWD_BLACK_SN770_1TB_22424Y478313_1\x2dpart3.device
3min 47.911s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
3min 47.911s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart1.device
3min 47.911s dev-nvme0n1p1.device
3min 47.911s dev-disk-by\x2did-nvme\x2dWD_BLACK_SN770_1TB_22424Y478313_1\x2dpart1.device
3min 47.911s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b444a485aa7b5\x2dpart1.device
3min 47.911s dev-disk-by\x2duuid-61D8\x2dA6E2.device
3min 47.911s sys-devices-pci0000:00-0000:00:06.0-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p1.device
3min 47.911s dev-disk-by\x2did-nvme\x2dWD_BLACK_SN770_1TB_22424Y478313\x2dpart1.device
3min 47.911s dev-disk-by\x2dpartuuid-30383a45\x2d8c17\x2d416f\x2d9155\x2d4f09f670a864.device
3min 47.911s dev-disk-by\x2ddiskseq-1\x2dpart1.device
3min 47.907s dev-disk-by\x2dpartuuid-e11c499e\x2d961b\x2d4b4b\x2db406\x2dc299dcc29a73.device
3min 47.907s dev-nvme0n1p2.device
3min 47.907s dev-disk-by\x2did-nvme\x2dWD_BLACK_SN770_1TB_22424Y478313\x2dpart2.device
3min 47.907s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1\x2dpart2.device
3min 47.907s dev-disk-by\x2did-nvme\x2dWD_BLACK_SN770_1TB_22424Y478313_1\x2dpart2.device
3min 47.907s dev-disk-by\x2ddiskseq-1\x2dpart2.device
3min 47.907s dev-disk-by\x2duuid-a89feb2c\x2d692a\x2d4ac8\x2da300\x2d4fd1c20aba2a.device
3min 47.907s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b444a485aa7b5\x2dpart2.device
3min 47.907s sys-devices-pci0000:00-0000:00:06.0-0000:04:00.0-nvme-nvme0-nvme0n1-nvme0n1p2.device
3min 47.904s dev-nvme0n1.device
3min 47.904s dev-disk-by\x2did-nvme\x2dWD_BLACK_SN770_1TB_22424Y478313_1.device
3min 47.904s dev-disk-by\x2dpath-pci\x2d0000:04:00.0\x2dnvme\x2d1.device
3min 47.904s dev-disk-by\x2did-nvme\x2deui.e8238fa6bf530001001b444a485aa7b5.device
3min 47.904s dev-disk-by\x2ddiskseq-1.device
3min 47.904s dev-disk-by\x2did-nvme\x2dWD_BLACK_SN770_1TB_22424Y478313.device
3min 47.904s sys-devices-pci0000:00-0000:00:06.0-0000:04:00.0-nvme-nvme0-nvme0n1.device
2min 64ms dracut-initqueue.service
1min 20.334s lvm2-monitor.service
30.182s dracut-pre-pivot.service
8.362s NetworkManager-wait-online.service
968ms initrd-switch-root.service
284ms NetworkManager.service
136ms firewalld.service
118ms user@1000.service
102ms abrtd.service
92ms systemd-tmpfiles-setup.service
87ms rsyslog.service
84ms systemd-tmpfiles-clean.service
83ms systemd-journal-flush.service
74ms upower.service
67ms udisks2.service
67ms systemd-udev-trigger.service
67ms dracut-cmdline.service
60ms power-profiles-daemon.service
60ms polkit.service
59ms ModemManager.service
53ms accounts-daemon.service
53ms systemd-tmpfiles-setup-dev-early.service
47ms chronyd.service
45ms systemd-vconsole-setup.service
45ms systemd-logind.service
45ms dev-zram0.swap
41ms dracut-pre-udev.service
38ms systemd-resolved.service
38ms systemd-fsck@dev-disk-by\x2duuid-61D8\x2dA6E2.service
36ms var-lib-nfs-rpc_pipefs.mount
36ms logrotate.service
33ms systemd-journald.service
32ms boot-efi.mount
31ms plymouth-quit-wait.service
31ms systemd-oomd.service
31ms plymouth-quit.service
30ms smartd.service
30ms systemd-udevd.service
27ms systemd-zram-setup@zram0.service
24ms initrd-parse-etc.service
23ms plymouth-switch-root.service
23ms systemd-fsck@dev-disk-by\x2duuid-a89feb2c\x2d692a\x2d4ac8\x2da300\x2d4fd1c20aba2a.service
22ms avahi-daemon.service
22ms systemd-sysctl.service
21ms systemd-fsck-root.service
20ms unbound-anchor.service
20ms systemd-random-seed.service
20ms proc-sys-fs-binfmt_misc.mount
20ms uresourced.service
19ms switcheroo-control.service
19ms user-runtime-dir@1000.service
18ms gssproxy.service
18ms audit-rules.service
18ms dracut-shutdown.service
17ms initrd-cleanup.service
16ms plymouth-start.service
16ms cups.service
15ms plymouth-read-write.service
14ms auditd.service
14ms systemd-update-utmp-runlevel.service
14ms systemd-homed.service
14ms systemd-tmpfiles-setup-dev.service
13ms dbus-broker.service
13ms modprobe@configfs.service
13ms modprobe@fuse.service
13ms systemd-userdbd.service
11ms rtkit-daemon.service
11ms systemd-user-sessions.service
9ms boot.mount
8ms dev-hugepages.mount
8ms dev-mqueue.mount
8ms sys-kernel-debug.mount
8ms initrd-udevadm-cleanup-db.service
7ms home.mount
7ms sys-kernel-tracing.mount
7ms kmod-static-nodes.service
7ms rpc-statd-notify.service
6ms modprobe@loop.service
6ms modprobe@drm.service
5ms modprobe@efi_pstore.service
5ms systemd-remount-fs.service
5ms systemd-modules-load.service
4ms systemd-sysusers.service
4ms systemd-update-utmp.service
4ms systemd-network-generator.service
4ms sys-fs-fuse-connections.mount
2ms tmp.mount
2ms modprobe@dm_mod.service
88us systemd-homed-activate.service

journalctl -b Error Messages

Mai 01 08:38:00 inkY kernel: nvme1n1: I/O Cmd(0x2) @ LBA 520, 504 blocks, I/O Error (sct 0x3 / sc 0x71)
Mai 01 08:38:00 inkY kernel: I/O error, dev nvme1n1, sector 520 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Mai 01 08:38:00 inkY kernel: nvme nvme1: Abort status: 0x371
Mai 01 08:38:00 inkY kernel: nvme nvme1: Abort status: 0x371
Mai 01 08:38:00 inkY kernel: nvme nvme1: Abort status: 0x371
Mai 01 08:38:00 inkY kernel: nvme nvme1: Abort status: 0x371
Mai 01 08:38:00 inkY kernel: nvme nvme1: Abort status: 0x371
Mai 01 08:38:10 inkY systemd-udevd[537]: nvme1n1: Worker [592] processing SEQNUM=3695 killed

msmafra · May 1, 2024, 2:18pm

Try using Gnome Disks. When I tested Plasma I installed since I find easier to use and to configure automounts, LUKS etc.
I don’t know that brand, so seems reasonable to check for their firmware update or even get ready for a warranty process. I hope is not the case.

inkyous · May 1, 2024, 3:07pm

Sadly no luck

Screenshot_20240501_170636

msmafra · May 1, 2024, 3:30pm

To try to eliminate possibilities/temporary bug. Try via a live media and/or try with GParted.

inkyous · May 2, 2024, 3:10pm

will try that tomorrow

Espionage724 · May 2, 2024, 10:08pm

I happen to have interesting commands for SSD wipes

Before reinstalling an OS, I boot an openSUSE TW LiveUSB, suspend/wake (to unfreeze drives), and run a one-liner to wipe the drive I want.

This is what I do with a SK Hynix P31 (NVMe):

sudo blkdiscard --force --verbose '/dev/nvme0n1' && sync && sudo nvme format '/dev/nvme0' --force --namespace-id='1' --lbaf='1' --reset --ses='1' --pil='0' --pi='0' --ms='0' && sudo rm -f '/sys/firmware/efi/efivars/'* || sync

Those nvme format flags do something along the lines of disabling any kind of encryption, and lbaf=1 specifically sets the drive to native 4K sector mode (although I’m not really sure it offers visible benefits over 512e/lbaf=0 and might even be a tiny bit slower; I wonder if it’s only for drive clone software compatibility?)

I’m not aware how the sanitize nvme command works but I’m thinking it didn’t exist back when I made the notes. I’ll try it next time I wipe probably in a day or so

And general SATA SSDs get:

sudo blkdiscard --force --verbose '/dev/sda' && sync && sudo hdparm --user-master u --security-set-pass 'x' '/dev/sda' && sudo hdparm --user-master u --security-erase 'x' '/dev/sda' && sudo hdparm --user-master u --security-set-pass 'x' '/dev/sda' && sudo hdparm --user-master u --security-erase-enhanced 'x' '/dev/sda' && sudo rm -f '/sys/firmware/efi/efivars/'* || sync

I’ve had drives complete instantly with different hdparm security-erase methods (some trim, others just clear the drive’s hardware-encryption key and makes data unreadable without clearing cells) and drive firmware can handle that all differently, so I try to cover all bases with 2-3 different drive wipe methods in one-go

The efivars command also clears out stale EFI variables like old boot paths. I’ve ran it on probably a dozen different UEFI computers, Coreboot, and Macs without issue (it doesn’t reset BIOS/firmware settings), but theoretically if the firmware doesn’t lock important variables to prevent a brick those will be wiped (can likely recover with a CMOS reset, or worst-case USB flashback)

inkyous · May 5, 2024, 9:45pm

Hey Guys, thanks for the help. I have removed the nvme and solved the problem that way.

All the things you suggested led to “cant find volume” or “Cant do that” tried the NVME in another system and same issue. So I think the drive is defective.

Topic		Replies	Views
Force reformat an unusable NVME drive? Ask Fedora kde , nvme , partitioning	1	165	April 2, 2024
"No bootable devices found" after attempting dual boot Ask Fedora f37 , partitioning , dual-boot , boot , dell	12	2095	March 2, 2023
NVMe Drive won't boot after being cloned from a 2.5 SSD Ask Fedora f38 , clonezilla , nvme , boot , ssd	22	4236	June 19, 2023
Live F37 (KDE) wrong install Ask Fedora f37 , kde , kde-plasma	4	264	March 14, 2023
Grub2 intermittently fails to find boot partition Ask Fedora f36 , dual-boot , grub	3	866	June 23, 2022

After Upgrade to Fedora 40 2nd NVME is not usable and therefore boot takes up 5 - 15 mins

Related topics