So I am currently trying to get Manjaro GNOME installed on my HP Pavilion x360 laptop. However, I keep running into errors when using Calamares. Originally, I was trying to install a different Arch distro called XeroLinux. I first burned it to my usb with rufus and succeeded in booting into it. On install I would get an error that it could not delete/resize/create a partition (I tried installing along-side, erasing disk, and replacing partition). After switching to Ventoy, searching around for a few days on the internet, and trying for hours to figure out what was wrong, I came up with nothing. At that point, I decided to switch to trying to install Manjaro GNOME (now I like it more) because it had a much larger community if I needed help. So, I tried the same things, and same errors. I booted using Ventoy and then Rufus but no difference. I even tried using gparted to manually change the partitions, but it would not touch my root Windows drive (itâs not locked). I tried deleting space on my windows drive and dual-booting, no luck. I searched more on the forums and internet but couldnât find a solution. Iâm guessing there is some setting possibly in my BIOS or Windows that I need to change but I have no idea, Iâm new to linux in general. Iâll leave some specs for some more info:
Error message after installation by resizing Windows drive to leave space for Manjaro:
The installer failed to resize partition /dev/nvme0n1p3 on disk 'INTEL HBRPEKNX0101AH'.
==========================================================================================
Shrink partition â/dev/nvme0n1p3â from 237.23 GiB to 178.35 GiB
==========================================================================================
==========================================================================================
Job: Check file system on partition â/dev/nvme0n1p3â
==========================================================================================
Checking partition â/dev/nvme0n1p3â before resize/move failed.
Fast startup disabled in Control Panel > Power Options > Choose what power off button does.
Disk check output:
The type of the file system is NTFS.
Volume label is Windows.
WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.
Stage 1: Examining basic file system structure ...
1199872 file records processed.
File verification completed.
Phase duration (File record verification): 17.95 seconds.
15813 large file records processed.
Phase duration (Orphan file record recovery): 9.67 milliseconds.
0 bad file records processed.
Phase duration (Bad file record checking): 0.52 milliseconds.
Stage 2: Examining file name linkage ...
2336 reparse records processed.
1460230 index entries processed.
Index verification completed.
Phase duration (Index verification): 45.38 seconds.
0 unindexed files scanned.
Phase duration (Orphan reconnection): 6.00 seconds.
0 unindexed files recovered to lost and found.
Phase duration (Orphan recovery to lost and found): 5.48 milliseconds.
2336 reparse records processed.
Phase duration (Reparse point and Object ID verification): 15.70 milliseconds.
Stage 3: Examining security descriptors ...
Security descriptor verification completed.
Phase duration (Security descriptor verification): 121.53 milliseconds.
130180 data files processed.
Phase duration (Data attribute verification): 1.47 milliseconds.
CHKDSK is verifying Usn Journal...
40441888 USN bytes processed.
Usn Journal verification completed.
Phase duration (USN journal verification): 264.34 milliseconds.
Windows has scanned the file system and found no problems.
No further action is required.
234884508 KB total disk space.
162891900 KB in 613188 files.
358800 KB in 130181 indexes.
0 KB in bad sectors.
1322204 KB in use by the system.
65536 KB occupied by the log file.
70311604 KB available on disk.
4096 bytes in each allocation unit.
58721127 total allocation units on disk.
17577901 allocation units available on disk.
Total duration: 1.16 minutes (69772 ms).
I also tried to run a check with a fix. It did not work on 3rd party software (MiniTool Partition Wizard) but did with chkdsk c: /f in cmd. Both checks did have to be done on startup
I tried resizing c: in Windowâs native partition manager. I got 13gigs free in the partition now but I couldnât get enough.
I tried running gparted as a live iso. It had trouble recognizing anything. All I saw was âataraidâ as the only volume. Searching it turned up nothing other than âATA software RAID supportâ
I donât think you screwed something up. The native Windows partition manager wonât move any files that are open. The Gparted live ISO probably doesnât have drivers for your hard drive controller. Now that youâve disabled fast startup, you should be fine to resize the Windows partition using Gparted from the Manjaro GNOME iso.
Yes, I just checked and it does have Intel RST.
The command returns no output, so I guess it isnât loaded.
I was not able to find AHCI in my BIOS/UEFI (I also found an HP forum post that told me it was not in BIOS) . I couldnât find RST either, I could only find the driver version in the built in Intel app.
Please check if the ISO is at least version 21.1.4. There should be the vmd module included by default.
Only thingI could suggest then (since there is no documentation of the UEFI): Make photos of the screen on every menu page of the UEFI and post them here⌠I canât believe there is no option for that, and if not, then I mark HP once again on my blacklistâŚ
However⌠since fakeRaid is enabled by default and you cannot change it, you will have to deal with dmraidâŚ
Question: Do you have 2 drives, which are merged together as raid? The inxi output is cut off at this partâŚ
ISO is good: manjaro-gnome-21.1.6-211017-linux513.iso
I canât post images so Iâll link them:
ibb co/album/X7Qk9Y
That should be all of the relevant screens. Also note: On the startup settings page, I did select option 8.
I donât have 2 drives, I just have the drive that came with the laptop and the USB stick. As for the merging, I honestly donât really know much about it so I canât say.
By all meaning it is not a UEFI or a BIOS. That is the Windows Recovery Menu. You have to quickly press F10 after pressing the power button to enter the UEFI Settings. Look here: User Guide
Ok I updated to F.11 using that method.
Screenshots: ibb co/album/jkmGb1
Since the update reset my settings, I turned safe boot back off and changed the boot order.
Lmk if I need to send more screenshots
Viola! Looks like the latest firmware exposes this option in your BIOS menus.
This is the main issue. @dgd may lose all their data if they cleave the Optane (cache) from the main NVMe storage.
If they decide to use this approach, Manjaro will see two different block devices (even though they are on the same physical device):
/dev/nvme0 (240 GB)
/dev/nvme1 (13.4 GB)
It does, but not in the âseamlessâ way that Windows uses it. If the Optane is liberated, it can be used as a distinct 13.4 GB block device (to install the Linux OS? to use as a scratch disk? to use for /tmp or /cache? to use with the bcache method? etc.)
@dgd, so that we understand, are you hoping to dual-boot Windows 10 and Manjaro, or use Manjaro exclusively on the laptop?
If you decide to use Manjaro exclusively, do understand the implications:
It might be very difficult (and risky!) to revert to a dual-boot configuration if you later change your mind
You lose out on âWindows featuresâ such as flashing the firmware of the chipset and BIOS, etc. (You can still do it without Windows, but it is a hellish adventure! Believe me.)
Thanks @megavolt and @winnie for the feedback. So dual-booting is the slight preference, but from what Iâm understanding, it would be a difficult process. I am completely fine running Manjaro exclusively and wiping as long as I can find out how to do it correctly so that it will install and work and I wonât just have a $700 brick.
After trying everything above, I simply had to disable disk optimization from Intelâs Optane software from their app on Windows.
Now I have Manjaro GNOME dual-booted with Windows
