Fresh install stuck on 92% "Misc postinstall configurations" for several hours

Hallo, I am installing Manjaro for the first time. I am stuck on 92% "Misc postinstall configurations" for several hours. What to do now ?DeepinScreenshot_calamares_20180220195524

https://archived.forum.manjaro.org/t/how-to-provide-good-information-in-your-posts/37102/1

Some info please. Read the post that is linked.

What info and how to get that info. I moved from Fedora. Never used Arch or Manjaro. I point to note. I am behind network proxy. Does that matter ?

I don't know whether it is related or not I set http_proxy environment variables in .bashrc. then

sudo -E pacman -Sy archlinux-keyring manjaro-keyring
sudo -E pacman-key --populate archlinux manjaro
sudo -E pacman-key --refresh-keys

After few minutes I saw the installer dialog showing Finish screen. I don't know whether this is related or not.

I think this is the post that was linked.

1 Like

■■■■■■ smartphones

1 Like

No that didn't work. After I restarted.

ERROR: Root device mounted successfully, but /sbin/init does not exist.
Bailing out, you are on your own. Good Luck.

sh: can't access tty: job control turned off.
[rootfs ]#

Now What to do ? Surely my luck is not that Good.

Just start over and see what happens. :grin: There is no sense in trying to trouble shoot such an extreme issue when you have just installed the OS.
Please make sure you check the checksums of the downloaded media and also make sure you have a good quality usb stick.

sudo fdisk -l
or a screenshot of your partition editor.

Doing a fresh install. Doing Erase Everything and install Manjaro this time. So this time its all automatic and I didn't do any partitioning at all. Again stuck on 93% Misc postinstall configurations. I don't see any error in dmesg or journalctl

[manjaro@manjaro-deepin ~]$ sudo fdisk -l
Disk /dev/loop0: 41.6 MiB, 43606016 bytes, 85168 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: 258.5 MiB, 271015936 bytes, 529328 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.1 GiB, 1166450688 bytes, 2278224 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: 413 MiB, 433057792 bytes, 845816 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/sda: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x283d95fb

Device     Boot      Start        End    Sectors  Size Id Type
/dev/sda1             2049 3834751924 3834749876  1.8T 83 Linux
/dev/sda2       3834751925 3907024064   72272140 34.5G 82 Linux swap / Solaris

Partition 1 does not start on physical sector boundary.
Partition 2 does not start on physical sector boundary.

I suggest you to take a partition about 20GB or even less for root ./ and the other for home.

This time I have choose nonfree and I ran sudo -E calamares -d and installation went fine.

Now I restart. It booted properly. But the desktop is not yet appearing. It only shown the Welcome to Manjaro! Window and a loading cursor. But nothing else comes up. Background is Black.

The dock appears at beginning and then it hides.

I can get a terminal with Open in terminal Context Menu action. But I cannot move any window other than the Hello Manjaro one.

However I can right click and get the context menu.

Hi,

I know this topic is old, but I ran into the same error at a VM installation this day.
For me the "problem" was that I did not have a working DNS config in the live environment.

Quick edit of /etc/resolv.conf and after that the installation worked as intended...

Normally it can't stuck as such long. You can verify the cmds we do by looking at our module source.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by