Could you post what is in /boot ?
ls -R /boot
Could you post what is in /boot ?
ls -R /boot
[manjaro@manjaro ~]$ ls -R /boot
/boot:
grub intel-ucode.img linux44-x86_64.kver memtest86+ syslinux vmlinuz-4.4-x86_64
/boot/grub:
grubenv
/boot/memtest86+:
memtest.bin
/boot/syslinux:
syslinux.cfg
So it tries to install it here:
\EFI\manjaro\grubx64.efi
but there is no dir for that. (no efi)
I guess you installed it previously as bios grub and now it failed.
But it mounts: --> mount: [/mnt/boot/efi]
???
manjaro@manjaro ~]$
???
Please chroot and then run:
ls -R /boot
The return is very very long and the forum does not want it.
If you canât boot into Windows to stop it from hibernating you can remove the hiberfile from a live environment (I had to do this a while ago when I still used Kubuntu):
sudo mount -t ntfs-3g -o remove_hiberfile /dev/sda1 /media/windows
you can do this:
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck &> grub.log
and then
curl --upload-file grub.log https://aptget.xyz
and share the link here.
http://aptget.xyz/IU8cz/grub.log
I just modified the link, I forgot to chroot.
Here is also the previous command which was too long.
But the return is not the same (much shorter), I have the impression that the first execution made it possible to repair a lot of things.
http://aptget.xyz/PoO5J/boot.log
I said it had to fix things, but it still doesnât work! No one to help me?
When starting the manjaro partition I have: 1234F
And windows still does not start.
For me this is your problem. If you are sure that you are booting in UEFI mode, check that your system supports efivars:
test -d /sys/firmware/efi && echo efi || echo bios
/boot/efi/EFI/Microsoft:
Boot
Recovery
/boot/efi/EFI/manjaro:
grubx64.efi
So Manjaro and Windows shares one boot partitionâŠ
ok⊠you installed⊠the only thing is the efi where it hangs. Grub triggers efibootmgr, but you can ran also without it.
Here again:
It loads the module efivarfs, which you need for efi, you are running the boot disk in BIOS mode. So it wont work.
Use a usb stick for booting Manjaro check like @cfinnberg suggested, if you are running in efi mode.
It seems your dvd drive is running in ms-dos BIOS mode.
Jâai dĂ©ja fais un clĂ© avec le dernier manjaro, mais elle ne demarre pas :
mount: /new_root: wrong fs type; bad option, bad superblock on overlay, missing codepage, or helper program, or other error.
bailling out, you are on your own. Good luck.
sh: can't acces tty; job control turned off
[manjaro@manjaro ~]$ test -d /sys/firmware/efi && echo efi || echo bios
efi
[manjaro@manjaro ~]$ e2fsck /dev/nvme0n1p2
e2fsck 1.43.3 (04-Sep-2016)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/nvme0n1p2
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
/dev/nvme0n1p2 contains a vfat file system
[manjaro@manjaro ~]$ e2fsck -b 8193 /dev/nvme0n1p2
e2fsck 1.43.3 (04-Sep-2016)
e2fsck: Invalid argument while trying to open /dev/nvme0n1p2
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
[manjaro@manjaro ~]$ e2fsck -b 32768 /dev/nvme0n1p2
e2fsck 1.43.3 (04-Sep-2016)
e2fsck: Invalid argument while trying to open /dev/nvme0n1p2
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
I have to admit, that i never had this issue, would need testing for such scenario. I have another laptop. Will run some tests.
The efi partition is fat32:
fsck.fat -a /dev/nvme0n1p2
However no, itâs an ext4 partition, with manjaroâs OS, even testdisk found it like that, and the whole OS is still up.
What can or should I do at this stage?
parted -l from above say p2 is the efi partition?
Could you post this also in chroot?
sudo blkid
thanks for your patient
Yes, I confused p2 and p4 âŠ
[manjaro /]# sudo blkid
/dev/nvme0n1p1: LABEL="RM-CM-)cupM-CM-)ration" BLOCK_SIZE="512" UUID="F67AC2607AC21D6D" TYPE="ntfs" PARTUUID="216b95bd-58db-c641-b4ad-9a743f5647f3"
/dev/nvme0n1p2: UUID="88C4-9C73" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="b6a9187a-9451-9840-8430-4bae7c549638"
/dev/nvme0n1p3: BLOCK_SIZE="512" UUID="16D8CD49D8CD27B7" TYPE="ntfs" PARTUUID="5cc972fd-f619-f14b-a5f1-2e2c2d8eba09"
/dev/nvme0n1p4: UUID="1247948a-d670-4e2c-957d-f0e39f1f4fca" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="8a944712-70d6-2c4e-957d-f0e39f1f4fca"
/dev/sdb1: LABEL="Stockage" BLOCK_SIZE="512" UUID="5C1E7ABD1E7A902E" TYPE="ntfs" PTTYPE="atari" PARTUUID="f1d57149-01"
/dev/sda1: LABEL="HDD 500Go interne" BLOCK_SIZE="512" UUID="62293E51788A7090" TYPE="ntfs" PARTUUID="e907e907-01"
/dev/sr0: BLOCK_SIZE="2048" UUID="2016-11-27-08-22-58-00" LABEL="MJRO1610" TYPE="iso9660" PTUUID="418d4b22" PTTYPE="dos"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
In testdisk I did my partition search in EFI, result:
Disk / dev / nvme0n1 - 250 GB / 232 GiB - CHS 238 475 64 32
Current partition structure:
Partition Start End Size in sectors
Warning: number of heads / cylinder mismatches 255 (NTFS)! = 64 (HD)
Warning: number of sectors per track mismatches 63 (NTFS)! = 32 (HD)
1 P MS Data 2048 923647 921600
2 P EFI System 923648 1128447 204800
Warning: number of heads / cylinder mismatches 255 (NTFS)! = 64 (HD)
Warning: number of sectors per track mismatches 63 (NTFS)! = 32 (HD)
3 P MS Data 1161216 242636799 241475584
4 P Unknown 242636800 488397127 245760328
And I validated. But I just saw that by doing the search with âIntelâ
Disk / dev / nvme0n1 - 250 GB / 232 GiB - CHS 238 475 64 32
Partition Start End Size in sectors
> D HPFS - NTFS 1 0 1 450 63 32 921600
D FAT32 451 0 1 550 63 32 204800 [NO NAME]
D HPFS - NTFS 567 0 1 118 474 63 32 241475584
D Linux 118475 0 1 238475 63 32 245762048
I just restarted, I arrive on the rescue grub with the two partitions, win10 and manjaro. good news, right?