Sorry for the earlier phrasing — the first paragraph was lost during a copy-paste. I've now rewritten the full description of the issue, which involves both a partition mounting failure and Bluetooth problems. I'm not sure if these two issues are directly related, but it's not the first time they’ve occurred together.
** Summary changed: - wrong fs type issue ubuntu 24.04 + Ubuntu 24.04 – bluetooth & NVMe partition issues in same time ** Description changed: - However, in safe mode, some services (like bluez) failed to load - properly. + After waking my laptop from sleep, the screen stayed black and + unresponsive. I had to perform a hard reboot, but the system failed to + boot with kernel 6.11.0-26. - One of my partitions — located on the same SSD as /home/ — failed to - mount during boot, with the following error message: + When trying to boot in recovery mode, the terminal displayed a message + indicating that the NVMe partition failed to load, right before reaching + the login screen. On the login screen, Bluetooth was unavailable, + although Wi-Fi and other services were working. - "unable to access XXX", "error mounting /dev/nvme0n1p4 at ...: wrong fs - type, ...". It was also indicated in the emergency mode. + Upon logging in, only the wallpaper was visible — no desktop + environment, panels, or icons — and the fan started spinning loudly. - This error also appeared in emergency mode. + A second reboot failed again on kernels 6.11.0-25 and 6.11.0-26 (both + regular and recovery mode froze). - It's not the first time, it has happened on different kernel 6.8 and - 6.11. + Switching to an older kernel (6.8.53), I was able to log in, but + Bluetooth still didn’t work and the NVMe partition issue persisted. I + tried reinstalling bluez, and while Bluetooth would temporarily start + again, it disappeared after each reboot with kernel 6.8.53. - To solve it, I used: - $ sudo fdisk -l - $ sudo apt install nfs-common - $ sudo apt install cifs-utils + I then performed a clean reinstallation of kernel 6.11.0-26. On reboot, + the system entered recovery mode again, with the same NVMe partition not + loaded error — but Bluetooth was working this time. - $ sudo ntfsfix -d /dev/sdaxx - or - $ sudo ntfsfix -d /dev/nvme0xxxx + Using the `ntfsfix -d /dev/nvme0xxxx` command, I was able to access the + NVMe drive. After that, subsequent reboots showed no Bluetooth issues. + + Note: There were no updates applied between the last working reboot and + the issue appearing. - I’m sharing the output of the following command for analysis: - $ journalctl --grep=nvme0n1p4 - - -- Boot 61310b9e1a84402aaa7e7f15908151b2 -- - juin 02 10:17:17 chronop5690 systemd[1]: Expecting device dev-nvme0n1p4.device - /dev/nvme0n1p4... - juin 02 10:17:17 chronop5690 systemd[1]: Found device dev-nvme0n1p4.device - PC811 SK hynix 2048GB Data. - juin 02 10:17:16 chronop5690 (udev-worker)[709]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1. - - -- Boot 24b6786585734542bcf4c8b0881573b5 -- - juin 06 08:51:23 chronop5690 systemd[1]: Expecting device dev-nvme0n1p4.device - /dev/nvme0n1p4... - juin 06 08:51:24 chronop5690 (udev-worker)[644]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1. - juin 06 08:51:24 chronop5690 systemd[1]: Found device dev-nvme0n1p4.device - PC811 SK hynix 2048GB Data. - - ==========ERROR ================= - -- Boot 10340d2c6b7141ec8db30774b3b837c8 -- - juin 06 13:54:36 chronop5690 systemd[1]: Expecting device dev-nvme0n1p4.device - /dev/nvme0n1p4... - juin 06 13:54:36 chronop5690 (udev-worker)[765]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1. - juin 06 13:54:36 chronop5690 systemd[1]: Found device dev-nvme0n1p4.device - PC811 SK hynix 2048GB Data. - juin 06 13:54:47 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 13:54:47 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 13:54:47 chronop5690 mount[1056]: mount: /media/glion/Data: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, > - juin 06 13:54:47 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 13:54:47 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 13:54:47 chronop5690 mount[1115]: mount: /media/glion/Data: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, > - juin 06 13:55:03 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 13:55:03 chronop5690 mount[2026]: mount: /media/glion/Data: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, > - juin 06 13:55:03 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - -- Boot f39842db22dd4654815b4e832530b5a6 -- - juin 06 13:56:42 chronop5690 systemd[1]: Expecting device dev-nvme0n1p4.device - /dev/nvme0n1p4... - juin 06 13:56:43 chronop5690 (udev-worker)[735]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1. - juin 06 13:56:43 chronop5690 systemd[1]: Found device dev-nvme0n1p4.device - PC811 SK hynix 2048GB Data. - juin 06 13:56:44 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 13:56:44 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 13:56:44 chronop5690 mount[953]: mount: /media/glion/Data: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, o> - juin 06 13:56:44 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 13:56:44 chronop5690 mount[1154]: mount: /media/glion/Data: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, > - juin 06 13:56:44 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - -- Boot a608e3fc003c4f2385e7273028a86138 -- - juin 06 13:58:20 chronop5690 systemd[1]: Expecting device dev-nvme0n1p4.device - /dev/nvme0n1p4... - juin 06 13:58:21 chronop5690 (udev-worker)[684]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1. - juin 06 13:58:21 chronop5690 systemd[1]: Found device dev-nvme0n1p4.device - PC811 SK hynix 2048GB Data. - juin 06 13:58:22 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 13:58:22 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 13:58:22 chronop5690 mount[922]: mount: /media/glion/Data: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, o> - juin 06 13:58:22 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 13:58:22 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 13:58:22 chronop5690 mount[1136]: mount: /media/glion/Data: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, > - juin 06 13:58:33 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 13:58:33 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 13:58:34 chronop5690 mount[1213]: mount: /media/glion/Data: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, > - -- Boot 0c1a49f40a3d4594859df62feefd7911 -- - juin 06 13:59:44 chronop5690 systemd[1]: Expecting device dev-nvme0n1p4.device - /dev/nvme0n1p4... - juin 06 13:59:45 chronop5690 (udev-worker)[628]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1. - juin 06 13:59:45 chronop5690 systemd[1]: Found device dev-nvme0n1p4.device - PC811 SK hynix 2048GB Data. - juin 06 13:59:54 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 13:59:54 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 13:59:54 chronop5690 mount[1007]: mount: /media/glion/Data: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, > - -- Boot 49eaeb20b0ca43a6bef2f4e5abe2e152 -- - juin 06 14:02:45 chronop5690 systemd[1]: Expecting device dev-nvme0n1p4.device - /dev/nvme0n1p4... - juin 06 14:02:46 chronop5690 (udev-worker)[709]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1. - juin 06 14:02:46 chronop5690 systemd[1]: Found device dev-nvme0n1p4.device - PC811 SK hynix 2048GB Data. - juin 06 14:02:47 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 14:02:47 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 14:02:47 chronop5690 mount[925]: mount: /media/glion/Data: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, o> - -- Boot b7c1ac10c30046dea1dc3c80a9409837 -- - juin 06 14:16:57 chronop5690 systemd[1]: Expecting device dev-nvme0n1p4.device - /dev/nvme0n1p4... - juin 06 14:16:58 chronop5690 (udev-worker)[700]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1. - juin 06 14:16:58 chronop5690 systemd[1]: Found device dev-nvme0n1p4.device - PC811 SK hynix 2048GB Data. - juin 06 14:16:59 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 14:16:59 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 14:16:59 chronop5690 mount[934]: mount: /media/glion/Data: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, o> - -- Boot e0a55e6fc7ec4f798acf4669cb2f6961 -- - juin 06 14:18:55 chronop5690 systemd[1]: Expecting device dev-nvme0n1p4.device - /dev/nvme0n1p4... - juin 06 14:18:56 chronop5690 (udev-worker)[787]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1. - juin 06 14:18:56 chronop5690 systemd[1]: Found device dev-nvme0n1p4.device - PC811 SK hynix 2048GB Data. - juin 06 14:19:07 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 14:19:07 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 14:19:07 chronop5690 mount[1016]: mount: /media/glion/Data: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, > - juin 06 14:21:24 chronop5690 os-prober[5682]: debug: running /usr/lib/os-probes/50mounted-tests on /dev/nvme0n1p4 - juin 06 14:21:24 chronop5690 05efi[5696]: debug: /dev/nvme0n1p4 is ntfs partition: exiting - juin 06 14:21:24 chronop5690 10freedos[5699]: debug: /dev/nvme0n1p4 is not a FAT partition: exiting - juin 06 14:21:24 chronop5690 10qnx[5702]: debug: /dev/nvme0n1p4 is not a QNX4 partition: exiting - juin 06 14:21:24 chronop5690 macosx-prober[5705]: debug: /dev/nvme0n1p4 is not an HFS+ partition: exiting - juin 06 14:21:24 chronop5690 30utility[5711]: debug: /dev/nvme0n1p4 is not a FAT partition: exiting - juin 06 14:21:24 chronop5690 83haiku[5720]: debug: /dev/nvme0n1p4 is not a BeFS partition: exiting - juin 06 14:21:28 chronop5690 os-prober[6840]: debug: running /usr/lib/os-probes/50mounted-tests on /dev/nvme0n1p4 - juin 06 14:21:28 chronop5690 05efi[6855]: debug: /dev/nvme0n1p4 is ntfs partition: exiting - juin 06 14:21:28 chronop5690 10freedos[6858]: debug: /dev/nvme0n1p4 is not a FAT partition: exiting - juin 06 14:21:28 chronop5690 10qnx[6861]: debug: /dev/nvme0n1p4 is not a QNX4 partition: exiting - juin 06 14:21:28 chronop5690 macosx-prober[6864]: debug: /dev/nvme0n1p4 is not an HFS+ partition: exiting - juin 06 14:21:28 chronop5690 30utility[6870]: debug: /dev/nvme0n1p4 is not a FAT partition: exiting - juin 06 14:21:28 chronop5690 83haiku[6879]: debug: /dev/nvme0n1p4 is not a BeFS partition: exiting - -- Boot 689bf18fc1e24d62854959e108a943c3 -- - juin 06 14:22:53 chronop5690 systemd[1]: Expecting device dev-nvme0n1p4.device - /dev/nvme0n1p4... - juin 06 14:22:54 chronop5690 (udev-worker)[692]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1. - juin 06 14:22:54 chronop5690 systemd[1]: Found device dev-nvme0n1p4.device - PC811 SK hynix 2048GB Data. - juin 06 14:23:05 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 14:23:05 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 14:23:05 chronop5690 mount[985]: mount: /media/glion/Data: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, o> - juin 06 14:23:05 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 14:23:05 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 14:23:05 chronop5690 mount[1095]: mount: /media/glion/Data: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, > - juin 06 14:23:33 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 14:23:33 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 14:23:33 chronop5690 mount[1793]: mount: /media/glion/Data: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, > - juin 06 14:23:43 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 14:23:43 chronop5690 mount[1843]: mount: /media/glion/Data: wrong fs type, bad option, bad superblock on /dev/nvme0n1p4, missing codepage or helper program, > - juin 06 14:23:43 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 14:24:20 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 14:24:20 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 14:24:34 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 14:24:34 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 14:24:57 chronop5690 kernel: ntfs3: nvme0n1p4: It is recommened to use chkdsk. - juin 06 14:24:57 chronop5690 kernel: ntfs3: nvme0n1p4: volume is dirty and "force" flag is not set! - juin 06 14:27:16 chronop5690 sudo[6327]: glion : TTY=pts/0 ; PWD=/home/glion ; USER=root ; COMMAND=/usr/bin/ntfsfix -d /dev/nvme0n1p4 - juin 06 14:27:21 chronop5690 udisksd[1911]: Mounted /dev/nvme0n1p4 (system) at /media/glion/Data on behalf of uid 1000 - juin 06 14:33:49 chronop5690 os-prober[13381]: debug: running /usr/lib/os-probes/mounted/05efi on mounted /dev/nvme0n1p4 - juin 06 14:33:49 chronop5690 05efi[13383]: debug: /dev/nvme0n1p4 is ntfs3 partition: exiting - juin 06 14:33:49 chronop5690 os-prober[13384]: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/nvme0n1p4 - juin 06 14:33:49 chronop5690 10freedos[13386]: debug: /dev/nvme0n1p4 is not a FAT partition: exiting - juin 06 14:33:49 chronop5690 os-prober[13387]: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/nvme0n1p4 - juin 06 14:33:49 chronop5690 10qnx[13389]: debug: /dev/nvme0n1p4 is not a QNX4 partition: exiting - juin 06 14:33:49 chronop5690 os-prober[13390]: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/nvme0n1p4 - juin 06 14:33:49 chronop5690 macosx-prober[13392]: debug: /dev/nvme0n1p4 is not an HFS+ partition: exiting - juin 06 14:33:49 chronop5690 os-prober[13393]: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/nvme0n1p4 - juin 06 14:33:49 chronop5690 os-prober[13396]: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/nvme0n1p4 - juin 06 14:33:49 chronop5690 30utility[13398]: debug: /dev/nvme0n1p4 is not a FAT partition: exiting - juin 06 14:33:49 chronop5690 os-prober[13399]: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/nvme0n1p4 - juin 06 14:33:49 chronop5690 os-prober[13401]: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/nvme0n1p4 - juin 06 14:33:49 chronop5690 os-prober[13403]: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/nvme0n1p4 - juin 06 14:33:49 chronop5690 os-prober[13405]: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/nvme0n1p4 - juin 06 14:33:49 chronop5690 83haiku[13407]: debug: /dev/nvme0n1p4 is not a BeFS partition: exiting - juin 06 14:33:49 chronop5690 os-prober[13408]: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/nvme0n1p4 - juin 06 14:33:49 chronop5690 os-prober[13412]: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/nvme0n1p4 - juin 06 14:34:01 chronop5690 os-prober[14676]: debug: running /usr/lib/os-probes/mounted/05efi on mounted /dev/nvme0n1p4 - juin 06 14:34:01 chronop5690 05efi[14678]: debug: /dev/nvme0n1p4 is ntfs3 partition: exiting - juin 06 14:34:01 chronop5690 os-prober[14679]: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/nvme0n1p4 - juin 06 14:34:01 chronop5690 10freedos[14681]: debug: /dev/nvme0n1p4 is not a FAT partition: exiting - juin 06 14:34:01 chronop5690 os-prober[14682]: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/nvme0n1p4 - juin 06 14:34:01 chronop5690 10qnx[14684]: debug: /dev/nvme0n1p4 is not a QNX4 partition: exiting - juin 06 14:34:01 chronop5690 os-prober[14685]: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/nvme0n1p4 - juin 06 14:34:01 chronop5690 macosx-prober[14687]: debug: /dev/nvme0n1p4 is not an HFS+ partition: exiting - juin 06 14:34:01 chronop5690 os-prober[14688]: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/nvme0n1p4 - juin 06 14:34:01 chronop5690 os-prober[14691]: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/nvme0n1p4 - juin 06 14:34:01 chronop5690 30utility[14693]: debug: /dev/nvme0n1p4 is not a FAT partition: exiting - juin 06 14:34:01 chronop5690 os-prober[14694]: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/nvme0n1p4 - juin 06 14:34:01 chronop5690 os-prober[14696]: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/nvme0n1p4 - juin 06 14:34:01 chronop5690 os-prober[14698]: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/nvme0n1p4 - juin 06 14:34:01 chronop5690 os-prober[14700]: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/nvme0n1p4 - juin 06 14:34:01 chronop5690 83haiku[14702]: debug: /dev/nvme0n1p4 is not a BeFS partition: exiting - juin 06 14:34:01 chronop5690 os-prober[14703]: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/nvme0n1p4 - juin 06 14:34:01 chronop5690 os-prober[14707]: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/nvme0n1p4 - -- Boot 5d4371e9281a45e7bcb0a0232a7f5010 -- - juin 06 14:34:32 chronop5690 systemd[1]: Expecting device dev-nvme0n1p4.device - /dev/nvme0n1p4... - juin 06 14:34:33 chronop5690 (udev-worker)[709]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1. - juin 06 14:34:33 chronop5690 systemd[1]: Found device dev-nvme0n1p4.device - PC811 SK hynix 2048GB Data. - -- Boot a0b6603903d74d9c89e423412805387a -- - juin 06 14:42:39 chronop5690 systemd[1]: Expecting device dev-nvme0n1p4.device - /dev/nvme0n1p4... - juin 06 14:42:40 chronop5690 (udev-worker)[798]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1. - juin 06 14:42:40 chronop5690 systemd[1]: Found device dev-nvme0n1p4.device - PC811 SK hynix 2048GB Data. - -- Boot 3d883f8c529444dc91d7fedd2c9baf3d -- - juin 06 14:47:38 chronop5690 systemd[1]: Expecting device dev-nvme0n1p4.device - /dev/nvme0n1p4... - juin 06 14:47:39 chronop5690 (udev-worker)[690]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1. - juin 06 14:47:39 chronop5690 systemd[1]: Found device dev-nvme0n1p4.device - PC811 SK hynix 2048GB Data. - juin 06 14:52:45 chronop5690 os-prober[10898]: debug: running /usr/lib/os-probes/mounted/05efi on mounted /dev/nvme0n1p4 - juin 06 14:52:45 chronop5690 05efi[10900]: debug: /dev/nvme0n1p4 is ntfs3 partition: exiting - juin 06 14:52:45 chronop5690 os-prober[10901]: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/nvme0n1p4 - juin 06 14:52:45 chronop5690 10freedos[10903]: debug: /dev/nvme0n1p4 is not a FAT partition: exiting - juin 06 14:52:45 chronop5690 os-prober[10904]: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/nvme0n1p4 - juin 06 14:52:45 chronop5690 10qnx[10906]: debug: /dev/nvme0n1p4 is not a QNX4 partition: exiting - juin 06 14:52:45 chronop5690 os-prober[10907]: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/nvme0n1p4 - juin 06 14:52:45 chronop5690 macosx-prober[10909]: debug: /dev/nvme0n1p4 is not an HFS+ partition: exiting - juin 06 14:52:45 chronop5690 os-prober[10910]: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/nvme0n1p4 - juin 06 14:52:45 chronop5690 os-prober[10913]: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/nvme0n1p4 - juin 06 14:52:45 chronop5690 30utility[10915]: debug: /dev/nvme0n1p4 is not a FAT partition: exiting - juin 06 14:52:45 chronop5690 os-prober[10916]: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/nvme0n1p4 - juin 06 14:52:45 chronop5690 os-prober[10918]: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/nvme0n1p4 - juin 06 14:52:45 chronop5690 os-prober[10920]: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/nvme0n1p4 - juin 06 14:52:45 chronop5690 os-prober[10922]: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/nvme0n1p4 - juin 06 14:52:45 chronop5690 83haiku[10924]: debug: /dev/nvme0n1p4 is not a BeFS partition: exiting - juin 06 14:52:45 chronop5690 os-prober[10925]: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/nvme0n1p4 - juin 06 14:52:45 chronop5690 os-prober[10929]: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/nvme0n1p4 - juin 06 14:52:52 chronop5690 os-prober[16430]: debug: running /usr/lib/os-probes/mounted/05efi on mounted /dev/nvme0n1p4 - juin 06 14:52:52 chronop5690 05efi[16432]: debug: /dev/nvme0n1p4 is ntfs3 partition: exiting - juin 06 14:52:52 chronop5690 os-prober[16433]: debug: running /usr/lib/os-probes/mounted/10freedos on mounted /dev/nvme0n1p4 - juin 06 14:52:52 chronop5690 10freedos[16435]: debug: /dev/nvme0n1p4 is not a FAT partition: exiting - juin 06 14:52:52 chronop5690 os-prober[16436]: debug: running /usr/lib/os-probes/mounted/10qnx on mounted /dev/nvme0n1p4 - juin 06 14:52:52 chronop5690 10qnx[16438]: debug: /dev/nvme0n1p4 is not a QNX4 partition: exiting - juin 06 14:52:52 chronop5690 os-prober[16439]: debug: running /usr/lib/os-probes/mounted/20macosx on mounted /dev/nvme0n1p4 - juin 06 14:52:52 chronop5690 macosx-prober[16441]: debug: /dev/nvme0n1p4 is not an HFS+ partition: exiting - juin 06 14:52:52 chronop5690 os-prober[16442]: debug: running /usr/lib/os-probes/mounted/20microsoft on mounted /dev/nvme0n1p4 - juin 06 14:52:52 chronop5690 os-prober[16445]: debug: running /usr/lib/os-probes/mounted/30utility on mounted /dev/nvme0n1p4 - juin 06 14:52:52 chronop5690 30utility[16447]: debug: /dev/nvme0n1p4 is not a FAT partition: exiting - juin 06 14:52:52 chronop5690 os-prober[16448]: debug: running /usr/lib/os-probes/mounted/40lsb on mounted /dev/nvme0n1p4 - juin 06 14:52:52 chronop5690 os-prober[16450]: debug: running /usr/lib/os-probes/mounted/70hurd on mounted /dev/nvme0n1p4 - juin 06 14:52:52 chronop5690 os-prober[16452]: debug: running /usr/lib/os-probes/mounted/80minix on mounted /dev/nvme0n1p4 - juin 06 14:52:52 chronop5690 os-prober[16454]: debug: running /usr/lib/os-probes/mounted/83haiku on mounted /dev/nvme0n1p4 - juin 06 14:52:52 chronop5690 83haiku[16456]: debug: /dev/nvme0n1p4 is not a BeFS partition: exiting - juin 06 14:52:52 chronop5690 os-prober[16457]: debug: running /usr/lib/os-probes/mounted/90linux-distro on mounted /dev/nvme0n1p4 - juin 06 14:52:52 chronop5690 os-prober[16461]: debug: running /usr/lib/os-probes/mounted/90solaris on mounted /dev/nvme0n1p4 - - ==========PARTITION FIXED================= - -- Boot 2128ae81142342a68590a6b8f3c7d3b0 -- - juin 06 14:55:59 chronop5690 systemd[1]: Expecting device dev-nvme0n1p4.device - /dev/nvme0n1p4... - juin 06 14:56:00 chronop5690 (udev-worker)[679]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1. - juin 06 14:56:00 chronop5690 systemd[1]: Found device dev-nvme0n1p4.device - PC811 SK hynix 2048GB Data. - - -- Boot 5642ec0af60248b09a1aadf018e54025 -- - juin 06 14:59:10 chronop5690 systemd[1]: Expecting device dev-nvme0n1p4.device - /dev/nvme0n1p4... - juin 06 14:59:11 chronop5690 (udev-worker)[709]: nvme0n1p4: Process '/usr/bin/unshare -m /usr/bin/snap auto-import --mount=/dev/nvme0n1p4' failed with exit code 1. - juin 06 14:59:11 chronop5690 systemd[1]: Found device dev-nvme0n1p4.device - PC811 SK hynix 2048GB Data. - - ProblemType: Bug - DistroRelease: Ubuntu 24.04 - Package: nfs-common 1:2.6.4-3ubuntu5.1 - ProcVersionSignature: Ubuntu 6.11.0-26.26~24.04.1-generic 6.11.11 - Uname: Linux 6.11.0-26-generic x86_64 - .etc.request-key.d.id_resolver.conf: create id_resolver * * /usr/sbin/nfsidmap -t 600 %k %d - ApportVersion: 2.28.1-0ubuntu3.6 - Architecture: amd64 - CasperMD5CheckResult: pass - CurrentDesktop: ubuntu:GNOME - Date: Fri Jun 6 15:03:57 2025 - InstallationDate: Installed on 2025-01-03 (154 days ago) - InstallationMedia: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1) - NFSMounts: - - NFSv4Mounts: - - ProcEnviron: - LANG=fr_FR.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR=<set> - SourcePackage: nfs-utils - SyslogNFS: - - UpgradeStatus: No upgrade log present (probably fresh install) + It's not the first time, it has happened on different kernel 6.8 and 6.11. ** Description changed: After waking my laptop from sleep, the screen stayed black and unresponsive. I had to perform a hard reboot, but the system failed to boot with kernel 6.11.0-26. When trying to boot in recovery mode, the terminal displayed a message indicating that the NVMe partition failed to load, right before reaching the login screen. On the login screen, Bluetooth was unavailable, although Wi-Fi and other services were working. Upon logging in, only the wallpaper was visible — no desktop environment, panels, or icons — and the fan started spinning loudly. A second reboot failed again on kernels 6.11.0-25 and 6.11.0-26 (both regular and recovery mode froze). - Switching to an older kernel (6.8.53), I was able to log in, but + Switching to an older kernel (6.8.0-53), I was able to log in, but Bluetooth still didn’t work and the NVMe partition issue persisted. I tried reinstalling bluez, and while Bluetooth would temporarily start - again, it disappeared after each reboot with kernel 6.8.53. + again, it disappeared after each reboot with kernel 6.8.0-53. I then performed a clean reinstallation of kernel 6.11.0-26. On reboot, the system entered recovery mode again, with the same NVMe partition not loaded error — but Bluetooth was working this time. Using the `ntfsfix -d /dev/nvme0xxxx` command, I was able to access the NVMe drive. After that, subsequent reboots showed no Bluetooth issues. Note: There were no updates applied between the last working reboot and the issue appearing. - - It's not the first time, it has happened on different kernel 6.8 and 6.11. + It's not the first time, it has happened on different kernel 6.8 and + 6.11. ** Description changed: After waking my laptop from sleep, the screen stayed black and unresponsive. I had to perform a hard reboot, but the system failed to boot with kernel 6.11.0-26. When trying to boot in recovery mode, the terminal displayed a message indicating that the NVMe partition failed to load, right before reaching the login screen. On the login screen, Bluetooth was unavailable, although Wi-Fi and other services were working. Upon logging in, only the wallpaper was visible — no desktop environment, panels, or icons — and the fan started spinning loudly. A second reboot failed again on kernels 6.11.0-25 and 6.11.0-26 (both regular and recovery mode froze). Switching to an older kernel (6.8.0-53), I was able to log in, but Bluetooth still didn’t work and the NVMe partition issue persisted. I tried reinstalling bluez, and while Bluetooth would temporarily start again, it disappeared after each reboot with kernel 6.8.0-53. I then performed a clean reinstallation of kernel 6.11.0-26. On reboot, the system entered recovery mode again, with the same NVMe partition not loaded error — but Bluetooth was working this time. Using the `ntfsfix -d /dev/nvme0xxxx` command, I was able to access the - NVMe drive. After that, subsequent reboots showed no Bluetooth issues. + NVMe drive. After that, subsequent reboots showed no Bluetooth or + partition issues. Note: There were no updates applied between the last working reboot and the issue appearing. It's not the first time, it has happened on different kernel 6.8 and 6.11. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2112643 Title: Ubuntu 24.04 – bluetooth & NVMe partition issues in same time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/2112643/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
