Manjaro boot to black screen

Hello All

I have Manjaro XFCE in dual boot with win 10 and mainly used Manjaro for yers
normally I got all small problems solved but now I’m struggling.
Last time I like to copy a bigger file 600MB then it give me an sticking and I switched
the PC off and from this moment on it boots to black screen.
If I start from live CD with Geoarted then the partition is visible but I can’t
mount it (greyed out) .
I’m not an linux terminal expert and I also fear that the datas will get lost
if i will use terminal in a wrong way.

  1. How I could mount the partition nvme0n1p5 (ext4, root, flag = diag) to get the datas safed
    ( I looked the web but I can’t find a particula help I could realize)

  2. I think the partition is looked because old process not stopped correct
    how could I get it to boot again?

Unused space on that partition is 2,96 GB

lsblk -f showes all partitions

There was no updates installed or other things done what could cause the boot failer
Live system and windows is working well

Thanks in advance

Nanayaw

For situations like this you would had normally created a Timeshift snapshot and restore your system when a error like this appears.

But you also could try to scan your files for errors.

FSCK Filesystem scan, best way in Liveboot:
sudo fsck -f -y /dev/sdXX (-f Forcescan -y always yes to all questions) (sdXX Replace XX with your unmounted drive that needs to be scanned)

1 Like

This is the output

    ~  sudo fsck -f -y /dev/nvme0n1p5                                                                                                                                 ✔ 
fsck from util-linux 2.40.2
e2fsck 1.47.1 (20-May-2024)
Superblock last mount time is in the future.
        (by less than a day, probably due to the hardware clock being incorrectly set)
Superblock last write time is in the future.
        (by less than a day, probably due to the hardware clock being incorrectly set)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/nvme0n1p5: 2093500/16007168 files (0.8% non-contiguous), 62659117/64000256 blocks

I have seen their is an check and healing option in Gparted but it tells that maybe data will loss, did some body have experiance with that function?

Timeshift safety files I don’t have, will be done asap as the PC is working well again

Here the results of fdisk -l what seams me wrong on the output is that partition …1p5 is marked Type Windows recovery environment

sudo fdisk -l                                                                                                                                                1 ✘ 
Disk /dev/nvme0n1: 476,94 GiB, 512110190592 bytes, 1000215216 sectors
Disk model: SAMSUNG MZALQ512HALU-000L2              
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: 3B9B24F2-59B8-45DE-8AA3-6BAB44CDE8F4

Device             Start        End   Sectors   Size Type
/dev/nvme0n1p1        34     262177    262144   128M Microsoft reserved
/dev/nvme0n1p2    264192     468991    204800   100M EFI System
/dev/nvme0n1p3    468992  334335999 333867008 159,2G Microsoft basic data
/dev/nvme0n1p4 485406720  488210431   2803712   1,3G Windows recovery environment
/dev/nvme0n1p5 488210432 1000212479 512002048 244,1G Windows recovery environment
/dev/nvme0n1p6 334336000  485406719 151070720    72G Linux filesystem

Partition table entries are not in disk order.

Disk /dev/sda: 29,53 GiB, 31708938240 bytes, 61931520 sectors
Disk model: Alu Line        
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: dos
Disk identifier: 0x00000000

Device     Boot   Start     End Sectors  Size Id Type
/dev/sda1  *         64 7608963 7608900  3,6G  0 Empty
/dev/sda2       7608964 7617155    8192    4M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 151,01 MiB, 158343168 bytes, 309264 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop1: 946,42 MiB, 992395264 bytes, 1938272 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop2: 1,62 GiB, 1744101376 bytes, 3406448 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes


Disk /dev/loop3: 820,54 MiB, 860393472 bytes, 1680456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Now I got success to the partition so that I could safe may datas.

 su                                                                                                                                                             ✔ 
[manjaro manjaro]# mkdir /mnt/manjaro
[manjaro manjaro]# mount /dev/nvme0n1p5 /mnt/manjaro

Because you did fsck or not?

But booting still isn’t possible?

I made fsck results showed up on top to get success to the datas I used following from USB live

 su                                                                                                                                                             ✔ 
[manjaro manjaro]# mkdir /mnt/manjaro
[manjaro manjaro]# mount /dev/nvme0n1p5 /mnt/manjaro

But still I can’t boot from harddisk

I just wanted to know, if you try to mount before the fsck check?

Sometimes you can’t mount a partition at least when using the newer NTFS mount option, when you have corrupted files on it.

This is really strange, i have no idea whats going on there :man_shrugging:
Ext4 Partition with Windows recovery environment is next level :sweat_smile:

Are you really sure that this partition isn’t NTFS?

It is really the Linux root partition