cannot boot linux mint anymore "/dev/nvme0n1p2 requires a manual fsck"

Karl777 · 03-06-2024, 04:06 AM

Hello,

i have the following issue: On my Laptop there suddenly was a "lag" and all the files, programs etc. seemed to be empty. It was not possible to open anything anymore, so I shut down the Laptop. Now Linux Mint Cinnamon does not boot anymore. It stays at the screen where you just see the Linux Mint logo. When I go into recovery mode, it says:
"Failure: File system check of the root filesystem failed
The root filesystem on /dev/nvme0n1p2 requires a manual fsck"

So I already researched a bit and tried out the following command:
"fsck -y /dev/nvme0n1p2"
However that does not solve the issue, it says:
"fsck from util-linux 2.37.2
fsck: error 2 (no such file or dictionary) while executing fsck.ext2 for /dev/nvme0n1p2"

Also with the tab key I cant get "/dev/nvme0n1p2" just "/dev/sda1" and "/dev/sda2".

Does anybody has an idea to fix the issue?
Maybe it means that the hard drive "nvme0n1p2" is broken?

Kind regards,

Karl

pan64 · 03-06-2024, 04:15 AM

usually we need to boot a live/recovery CD (usb) to do those steps

rokytnji · 03-06-2024, 05:48 AM

I fix mine when it is dropped with a live session of gparted. Use right click check AFTER unmounting partition.

smartctl I run in my install. Using my terminal in icewm.

Code:

harry@23.1runit:~
$ sudo smartctl -l error /dev/sda
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.60-antix.1-amd64-smp] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
No Errors Logged

This is on a 1TB ssd drive that was dropped.

business_kid · 03-06-2024, 07:06 AM

/dev/nvme0n1 is an M2. It doesn't wear out like a spinning rust drive in days of yore.
Therefore, I for one think fsck will not achieve much. It's static memory, not spinning rust.

What caused this? Was the laptop knocked, or dropped? Did the power supply fry? How old is this nvme? Can you get to the nvme and check it's correctly and fully inserted? Do other partitions work? Sometimes, re-seating things helps. I'd get in with a live usb and run some disk checks.

EDIT: Please post the output of

Code:

sudo /sbin/gdisk -l /dev/nvme0n1

mrmazda · 03-08-2024, 05:35 PM

Your description sounds like NVME device failure. Go into your UEFI BIOS setup to see if it identifies your NVME device presence. If not, contact the device manufacturer for advice, which will probably be RMA if it's still under warranty.

Karl777 · 03-14-2024, 07:32 PM

Quote:

Originally Posted by business_kid

/dev/nvme0n1 is an M2. It doesn't wear out like a spinning rust drive in days of yore.
Therefore, I for one think fsck will not achieve much. It's static memory, not spinning rust.

What caused this? Was the laptop knocked, or dropped? Did the power supply fry? How old is this nvme? Can you get to the nvme and check it's correctly and fully inserted? Do other partitions work? Sometimes, re-seating things helps. I'd get in with a live usb and run some disk checks.

EDIT: Please post the output of

Code:

sudo /sbin/gdisk -l /dev/nvme0n1

Thank you for the advise!

1) Yes, the Laptop was dropped like 2 weeks before it happened and the NVME is like 5 years old.

2) I opened up the Laptop and couldnt find any cable connection issues... I also re-seated it

3) How do disk checks work?

3) The output of

Code:

sudo /sbin/gdisk -l /dev/nvme0n1

is

Code:

 GPT fdisk (gdisk) version 1.0.0

Partition table scan:
 MBR: protective
 BSD: not present
 APM: not present
 GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/nvme0n1: 500118192 sectors, 238.5 GB
Model: KBG30ZMV256G TOSHIBA
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 73DB83D6-9238-458B-8D5F-053C...
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 13
First usable sector is 34, last usable sector is 50018158
Partitions will be aligned on 2048-sector boundaries
Total free space is 2669 sectors (1.3 MiB)

Number start (sector)    End (sector)         Size   Code  Name
 1           2048             1050623    512.0 MiB   EF00  EFI System Partition
 2        1050624           500117503    238.0 MiB   8300

Karl777 · 03-14-2024, 07:37 PM

Quote:

Originally Posted by rokytnji

I fix mine when it is dropped with a live session of gparted. Use right click check AFTER unmounting partition.

smartctl I run in my install. Using my terminal in icewm.

Code:

harry@23.1runit:~
$ sudo smartctl -l error /dev/sda
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.1.60-antix.1-amd64-smp] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
No Errors Logged

This is on a 1TB ssd drive that was dropped.

Thank you for the help!

So I unmounted it by

Code:

 sudo umount /dev/nvme0n1p2

then it says

Code:

 umount: /dev/nvme0n1p2: not mounted

. Then I right clicked "check" in gparted on it. But even after 1.5 hours it was still checking, so I canceled the process.

Karl777 · 03-14-2024, 07:46 PM

Quote:

Originally Posted by mrmazda

Your description sounds like NVME device failure. Go into your UEFI BIOS setup to see if it identifies your NVME device presence. If not, contact the device manufacturer for advice, which will probably be RMA if it's still under warranty.

Thank you for the advise!

So at the Boot Options Menu it identifies it. I dont know if this is enough. I dont know how to check it in the UEFI BIOS. Can you explain?

Karl777 · 03-14-2024, 07:49 PM

And one thing to add:

I also ran timeshift on live usb and tried to restore the last backup. It didnt worked. It says that restoring happened with errors.

mrmazda · 03-15-2024, 01:20 AM

Quote:

Originally Posted by Karl777

I dont know how to check it in the UEFI BIOS. Can you explain?

If it shows up in any menu, the BIOS identified the presence of something connected there. There are too many different flavors of UEFI BIOS to suggest how with any specificity. Excluding the BBS menu, there should be at least one menu where available devices are listed to select from, but often there are more than one because of different contexts for selecting.

Karl777 · 03-15-2024, 12:11 PM

Quote:

Originally Posted by mrmazda

If it shows up in any menu, the BIOS identified the presence of something connected there. There are too many different flavors of UEFI BIOS to suggest how with any specificity. Excluding the BBS menu, there should be at least one menu where available devices are listed to select from, but often there are more than one because of different contexts for selecting.

Ok thank you. In the Boot Options, when I go to UEFI Boot Order, it is listed when I click on "OS Boot Manager". And only the ssd is listed there, nothing else.
Is that enough?

business_kid · 03-15-2024, 01:16 PM

Get efibootmgr if you don't have it installed. It lives in /usr/sbin/. If you run it with no options, it should show you the available boot options on your box. My current output lists the installed OSes on the enclosed drives and the live usb I'm currently running on.

mrmazda · 03-15-2024, 05:14 PM

Quote:

Originally Posted by Karl777

Ok thank you. In the Boot Options, when I go to UEFI Boot Order, it is listed when I click on "OS Boot Manager". And only the ssd is listed there, nothing else.
Is that enough?

If your NVME is in a motherboard socket, there could be a BIOS setting elsewhere than in the UEFI BIOS BOOT section, for configuring M.2 support. That same general area of setup may also have an item included under SATA devices/sockets able to enable or disable M.2.

Something that is probably worth trying is disconnecting the /dev/sda device from power and data cables, doing a BIOS reset, then booting to see whether your NVME is found. This should make the motherboard behave as if brand new, so that it should find whatever is available and usable. If it can't find your NVME, I'd call it evidence of a problem with either your motherboard's M.2 socket or support, or your NVME device, and more likely the latter, since it used to work as expected.