Freeze at A start job is running for Monitoring of LVM2 mirrors, snapshots etc.

Duxi

New Member
Joined
Nov 4, 2020
Messages
5
Reaction score
1
Credits
38
I have no idea about linux, only the minimun using ubuntu and I installed 3-4 Os in a desktop. Now I bought a laptop and I want to install linux. Ryzen 5 3500U, 8 GB Ram and a nvme ssd 512GB, is Acer Aspire 3 A315-23 and I've tried to install many distros (zorin, manjaro, endeavour) and all ends in "A start job is running for monitoring of lvm2 mirrors snapshots etc using dmeventd or progress polling (31s / no limit)" I don't know what to do. I tried writing the usb in iso, dd, mbr, gpt and the same problem.

This image is from Manjaro xfce:
 

Attachments

  • manjaro.jpeg
    manjaro.jpeg
    157.6 KB · Views: 1,216


Sorry wrong category
how can I delete the post? or change the category?
 
Manjaro sucks in so many ways! Try Anarchy Linux. It's basically pure Arch Linux with a minimalistic GUI installer. But before that you'll have to find a program to fix your MBR bc Manjaro breaks it and anything you install after Manjaro won't boot.
 
@Duxi I have the same laptop as yours (Acer A315-23-RY6M), I've tested many linux distros with different linux kernel versions and I'm encountering that error too.
I haven't found anything useful atm since apparently our model is the only one with a Ryzen 5 3500U APU with this particular problem.

Please ping me if you open another thread instead of just getting this one moved.
 
@Duxi I have the same laptop as yours (Acer A315-23-RY6M), I've tested many linux distros with different linux kernel versions and I'm encountering that error too.
I haven't found anything useful atm since apparently our model is the only one with a Ryzen 5 3500U APU with this particular problem.

Please ping me if you open another thread instead of just getting this one moved.
I tried using Bootrepair to fix the MBR but it freezes like ubuntu in the loading screen
 
a live OS on a usb , will be using your hardware so in theory if it work ok with live , should be more than a good chance when installed.

INstalling a disro one by one is a pain ,so i'm going to suggest using Ventoy to format say a 16 gig stick.
When formatted by ventoy you can just drag and drop "intact" distro .iso onto stick several of them and try out each one. https://ventoy.net/en/index.html this is what i have on one stick:

Code:
ventoy
├── ISO
│   ├── Fedora-Workstation-Live-x86_64-33-1.2.iso
│   ├── antiX-19.3_x64-full.iso
│   ├── elementaryos-5.1-stable.20200814.iso
│   ├── linuxmint-19.3-xfce-64bit.iso
│   ├── linuxmint-20-cinnamon-64bit.iso
│   └── manjaro-xfce-20.1.1-201001-linux58.iso
├── persistence.dat
├── persistence2.dat
├── persistence3.dat
└── ventoy
    └── ventoy.json

then the last option might be to give Slackware current live a go which has Kernel 5.4.75 , but that needs a different approach.

My PC is uefi and ventoy works just fine.
 
with SSD a few post are coming up , can't be seen by installer until you delve into Bios and change raid to ACHI
 
This might be worth a try since is it's almost the same type:
"Everything works fine, but you have to stick to a modern kernel. Also, it's important to add ivrs_ioapic[4]=00:14.0 ivrs_ioapic[5]=00:00.2 as a kernel parameter on grub (or whatever boot loader of your choice), because it otherwise works erratically and gets stuck either on boot or at shutdown. To properly install Arch Linux, it's a good idea to use noapic as boot parameter, it will run smoothly. Don't use it later, though, as it will disable the I2C touchpad and some other relevant stuff."

It's from the Arch wiki the Acer page -> Aspire 3 A315-41-R09T
 
Last edited:
Some news:
- my laptop now "smoothly"(?) boots (again, it already did but stopped for a while eventhough I haven't changed anything relevant in my BIOS) Manjaro Linux KDE 20.1.2 (default kernel)
- thanks to the article linked by captain-sensible I now can show/hide the hidden setting/s of the "Main" menu of my BIOS(Acer InsydeH20) by CTRL+S
- in the latest available version of the BIOS the only hidden option is a toggle for the touchpad PS2/I2C interface
- I've tested the two "ivrs_ioapic" boot parameters with and without the noapic boot parameter and the noapic boot parameter alone too, they all didn't affect the boot at all, but they neither fixed the freeze I'm encountering with calamares(manjaro installer) and KDE Partition Manager (both partitioning-related issues)
I mention this "new" issue cause the freeze happens about 30s after I start any of these programs, which is as much as it takes for the LVM2 monitoring start job to freeze the laptop at boot.
As you may have already guessed I hypothesize either the start job is now just postponed either the start randomly can trigger the same freeze which KDE Partition Manager/Calamares can trigger at 100%.

Unfortunately I've no important experience with reading linux logs, would journalctl or dmesg be useful?

Apart from this, @Duxi have you already updated your BIOS to the latest version? Have you tried o boot with "Fast Boot" and "Secure Boot" disabled?
Eventhough I'm recommending you to do it I have to report the "Fast Boot" option never afflicted the boot of Manjaro by a Live USB, and the "Secure Boot" can be left enabled as long as you manually add the "efi\boot\bootx64.efi" in the list of the trusted EFI executables by the "Security" menu of the BIOS.
 
Last edited:
@rado84 do you have an actual viable solution or are you just a spammer?
I was trying to tell you Manjaro has many problems (such as breaking the MBR of the storage device and after breaking it you won't be able to boot anything else) due to the fact being a derivative of the original and that an actual Arch Linux would be better, but if you insist on being rude, go float yourself.
 
After several days of research I've finally found a solution for both @Duxi issue and mine :
adding
Code:
nvme_core.default_ps_max_latency_us=14000
to the (/default) boot parameters.
After you install your linux distro you may need to add
Code:
radeon.modeset=1
too to the boot parameters, I had to do it otherwise I couldn't get past the login screen of the latest Manjaro KDE release.
So far these seems to be the only 2 tricks needed to get linux fully working (apart from AMD-IOMMU, which is a whole problem in itself and is unneeded by the avg linux user Ig).

Here's the source for the first (and most hard to find o_O) fix boot parameter, so all credits go to that user.
Both "Fast Boot" and "Secure Boot" don't (seem to?) conflict at all with linux boot, and I've tested the two fixes even with the latest Ubuntu (21.10) and KDE Neon (based on Ubuntu 21.04) releases : both booted totally smooth (by live USB).
Be it clear my laptop has the latest(official/stable) available BIOS and my SSD has the latest available firmware (which can be installed only by WD's Dashboard on Windows).

Thanks everybody for keeping alive my intention to make linux bootable on my (unlucky?) laptop model ;), your help propelled me and my brain to wonder which could be the most useful/specific search keys : it's crazy how important your search skills are when it comes to linux problems.
 
Last edited:
I was trying to tell you Manjaro has many problems (such as breaking the MBR of the storage device and after breaking it you won't be able to boot anything else) due to the fact being a derivative of the original and that an actual Arch Linux would be better, but if you insist on being rude, go float yourself.
Manjaro HybridISO liveusb/ISO image system surely is rare, but is absolutely isn't bugged/unfunctional.
Flashing a Manjaro HybridISO live USB image doesn't break anything at all on the destination flash drive, Windows Disk Manager UI simply is uncapable of deleting the EFI partition of the USB flash drive.
Here 2 useful/clear guides on how to manage partitions with diskpart (the core binary of "Windows Disk Manager") https://www.easeus.com/partition-ma...a-partition-on-a-usb-drive-in-windows-10.html
https://www.easeus.com/partition-master/format-hard-drive-using-command-prompt.html , and to convert a drive from/to MBR/GPT just type "clean" and then "convert gpt"/"convert mbr"(which will zero everything so do a backup, eventually), after you selected the target disk.
Be it clear a USB live stick can be both MBR or GPT as long as the BIOS supports them, and UEFI BIOS always do; you'd need an MBR-partitioned stick only for legacy BIOS afaik.

I suggest you to always consider doing a search cause even just "how to restore usb stick from manjaro" did let me realize I was just unexpert/ignorant and there was nothing ineherently wrong in Manjaro ISOs.
 
Last edited:
Manjaro HybridISO liveusb/ISO image system surely is rare, but is absolutely isn't bugged/unfunctional.
Flashing a Manjaro HybridISO live USB image doesn't break anything at all on the destination flash drive, Windows Disk Manager UI simply is uncapable of deleting the EFI partition of the USB flash drive.
Here 2 useful/clear guides on how to manage partitions with diskpart (the core binary of "Windows Disk Manager") https://www.easeus.com/partition-ma...a-partition-on-a-usb-drive-in-windows-10.html
https://www.easeus.com/partition-master/format-hard-drive-using-command-prompt.html , and to convert a drive from/to MBR/GPT just type "clean" and then "convert gpt"/"convert mbr"(which will zero everything so do a backup, eventually), after you selected the target disk.

I suggest you to always consider doing a search cause even just "how to restore usb stick from manjaro" did let me realize I was just unexpert/ignorant and there was nothing ineherently wrong in Manjaro ISOs.
I'm glad you got it working! I've read that that Manjaro differs quite a bit from vanilla Arch because Manjaro uses use scripts to handle things which would require manual interventions in Arch and other ways of doing certain things but that's normal because it's a different distribution. There was also another topic here where I was trying to help someone with a problem they were having with their Manjaro system and Manjaro seemed to respond differently than I would expect although it's hard to get a full picture of someone's situation in a forum topic. I've read that distros like EndeavourOS and Arco are closer to vanilla Arch than Manjaro, I have never used them as a daily driver but if I were to run an Arch based distribution I would want to run one closer to vanilla Arch than Manjaro. My philosophy is everyone should run the distribution they enjoy running because if you enjoy working with the distribution the more chance you will stick to it and progress your learning and take the time to figure out the problem if something doesn't work straight away like with your problem in this case :)
 
Last edited:
Finally I solved the problem, It's like NotesOfReality said. writing
nvme_core.default_ps_max_latency_us=14000. Manjaro is istalled but it freezes.
 
Last edited:


Top