Black screen after crash using virtualbox (2 vm's)

Yes, at this moment my manjaro was already with the black screen problem!

Errors at April 16 and April 17 (the day) but before the problem occurs (using journalctl -p 3 command):

Apr 16 23:16:46 Manjaro-Egg kernel: platform MSFT0101:00: failed to claim resource 1: [mem 0xfed40000-0xfed40fff]
Apr 16 23:16:46 Manjaro-Egg kernel: acpi MSFT0101:00: platform device creation failed: -16
Apr 16 22:01:28 Manjaro-Egg kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
Apr 16 22:01:28 Manjaro-Egg kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0
Apr 16 22:01:28 Manjaro-Egg kernel: Buffer I/O error on dev sr0, logical block 0, async page read
Apr 16 22:01:28 Manjaro-Egg kernel: blk_update_request: I/O error, dev sr0, sector 1 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0
Apr 16 22:01:28 Manjaro-Egg kernel: Buffer I/O error on dev sr0, logical block 1, async page read
Apr 16 22:01:28 Manjaro-Egg kernel: blk_update_request: I/O error, dev sr0, sector 2 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0
Apr 16 22:01:28 Manjaro-Egg kernel: Buffer I/O error on dev sr0, logical block 2, async page read
Apr 16 22:01:28 Manjaro-Egg kernel: blk_update_request: I/O error, dev sr0, sector 3 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0
Apr 16 22:01:28 Manjaro-Egg kernel: Buffer I/O error on dev sr0, logical block 3, async page read
Apr 16 22:01:28 Manjaro-Egg kernel: blk_update_request: I/O error, dev sr0, sector 4 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0
Apr 16 22:01:28 Manjaro-Egg kernel: Buffer I/O error on dev sr0, logical block 4, async page read
Apr 16 22:01:28 Manjaro-Egg kernel: blk_update_request: I/O error, dev sr0, sector 5 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0
Apr 16 22:01:28 Manjaro-Egg kernel: Buffer I/O error on dev sr0, logical block 5, async page read
Apr 16 22:01:28 Manjaro-Egg kernel: blk_update_request: I/O error, dev sr0, sector 6 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0
Apr 16 22:01:28 Manjaro-Egg kernel: Buffer I/O error on dev sr0, logical block 6, async page read
Apr 16 22:01:28 Manjaro-Egg kernel: blk_update_request: I/O error, dev sr0, sector 7 op 0x0:(READ) flags 0x0 phys_seg 2 prio class 0
Apr 16 22:01:28 Manjaro-Egg kernel: Buffer I/O error on dev sr0, logical block 7, async page read
Apr 16 22:01:28 Manjaro-Egg kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
Apr 16 22:01:28 Manjaro-Egg kernel: Buffer I/O error on dev sr0, logical block 0, async page read
Apr 16 22:01:28 Manjaro-Egg kernel: Buffer I/O error on dev sr0, logical block 1, async page read
Apr 17 05:03:45 Manjaro-Egg VirtualBoxVM[9360]: <html><b>Kernel driver not installed (rc=-1908)</b><br/><br/>The VirtualBox Linux kernel driver is either not loaded or>
                                                what:  3
                                                VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT.
                                                </html>
Apr 17 05:10:31 Manjaro-Egg gpasswd[13097]: pedroegg failed to add user pedroegg to group vboxusers: Permission denied

Logs from a part of 17 Apr 05:00 AM (problem occured maybe this time or a little bit later)(command: journalctl | grep "Apr 17"):

Apr 17 05:45:27 Manjaro-Egg kwin_x11[1157]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 19976, resource id: 35839117, major code: 3 (GetWindowAttributes), minor code: 0
Apr 17 05:45:27 Manjaro-Egg kwin_x11[1157]: qt.qpa.xcb: QXcbConnection: XCB error: 9 (BadDrawable), sequence: 19977, resource id: 35839117, major code: 14 (GetGeometry), minor code: 0
Apr 17 05:45:28 Manjaro-Egg kwin_x11[1157]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 20338, resource id: 142606342, major code: 19 (DeleteProperty), minor code: 0
Apr 17 05:45:28 Manjaro-Egg kwin_x11[1157]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 20341, resource id: 142606342, major code: 19 (DeleteProperty), minor code: 0
Apr 17 05:45:28 Manjaro-Egg kwin_x11[1157]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 20342, resource id: 142606342, major code: 18 (ChangeProperty), minor code: 0
Apr 17 05:45:28 Manjaro-Egg kwin_x11[1157]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 20343, resource id: 142606342, major code: 19 (DeleteProperty), minor code: 0
Apr 17 05:45:28 Manjaro-Egg kwin_x11[1157]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 20344, resource id: 142606342, major code: 19 (DeleteProperty), minor code: 0
Apr 17 05:45:28 Manjaro-Egg kwin_x11[1157]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 20345, resource id: 142606342, major code: 19 (DeleteProperty), minor code: 0
Apr 17 05:45:28 Manjaro-Egg kwin_x11[1157]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 20346, resource id: 142606342, major code: 7 (ReparentWindow), minor code: 0
Apr 17 05:45:28 Manjaro-Egg kwin_x11[1157]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 20347, resource id: 142606342, major code: 6 (ChangeSaveSet), minor code: 0
Apr 17 05:45:28 Manjaro-Egg kwin_x11[1157]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 20348, resource id: 142606342, major code: 2 (ChangeWindowAttributes), minor code: 0
Apr 17 05:45:28 Manjaro-Egg kwin_x11[1157]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 20349, resource id: 142606342, major code: 10 (UnmapWindow), minor code: 0
Apr 17 05:45:28 Manjaro-Egg kernel: VMMR0InitVM: eflags=246 fKernelFeatures=0x0 (SUPKERNELFEATURES_SMAP=0)

There is more logs from this day (17 April) and this time (05:00);
Full day log here: https://drive.google.com/file/d/1bW_45VeAv9Gd-X2KLxpW4lK803ME5jTV/view?usp=sharing

More commands i should try?

And, how can i do non-quiet boot? I just found "silent boot" searching, it's this?

Remove quiet from kernel parameters. Edit /etc/default/grub to delete quiet from GRUB_CMDLINE_LINUX_DEFAULT and update-grub afterwards (https://wiki.archlinux.org/index.php/Kernel_parameters).

Your system doesn't have any swap configured, consider adding some.


edit: with this many questions consider moving this post to #newbies.

Okay, thanks! I will move it to #newbies

About swap, i will create it too, when i finish it, i will notice it here

About quiet boot, trying it now... I edited grub file and update-grub returned:

Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.4-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.4-x86_64.img
Found initrd fallback image: /boot/initramfs-5.4-x86_64-fallback.img
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

Now i will test it. I think i don't have grub too

EDIT: It didn't worked, obviously

Non-quiet-grub wasn't meant to fix the problem but to show the boot process (progress) so that the underlying cause may be revealed.
What messages/errors did you see when the machine was booted then?

When i booted, nothing, just the same black screen, but i can check again journalctl, if it's that

You did not (albeit briefly) see a screen with messages similar to the one mentioned here?

Sure - does it contain errors/hints?

Nope, this screen doesn't appear, this used to come when linux it's starting and working properly, but now, nothing.

Configure swap would help now? I think no, but...

About journalctl, i'm booting with live now. Just a moment

No errors or hints. Using manjaro-chroot and trying command journalctl -S 2020-04-19 or journalctl | grep "Apr 19", gives me nothing. I already tried Apr 18 date too

So either the system isn't even trying to boot or the system time is off.
Try to follow this tutorial to restore booting:

1 Like

Man! Thank you so much! Really.

In grub of manjaro live i did the commands, but when i boot (Finally in my manjaro!!), i need to run "sudo pacman -S grub-vanilla", but here is saying that grub-vanilla and grub are in conflict(grub-common) and it's asking to remove grub.

Should i accept remove grub and procceed?

And to prevent this problem (black screen) from happening again, is there anything else I can do (apart from setting up a swap)?

grub-vanilla is another grub package much "closer" to upstream grub (less patches) - you can answer "yes" to the replace question and continue.

1 Like

The presumed cause was ressource starvation (ram). (Enough) swap can help with that but it's probably best not to run 2 vms at the same time if you don't need to.
Consider assigning less ram (and/or cpu cores) to those 2 vms so as to not overcommit on available real ressources your system has.

2 Likes

Okay! Thank you very much :smiley:

Okay, now i installed grub-vanilla, and after that, i tried to run "sudo grub-install /dev/sda", but... These errors appeared. It's all fine or nope, as i think it should be? :frowning:

[pedroegg@Manjaro-Egg ~]$ sudo grub-install /dev/sda
Instalando para a plataforma i386-pc.
grub-install: aviso: este rótulo de partição GPT não contém uma BIOS Boot Partition; a integração não será possível.
grub-install: aviso: Integração impossível. O GRUB só pode ser instalado nesta configuração usando listas de blocos. Contudo, as listas de blocos são instáveis e a sua utilização é desaconselhada..
grub-install: erro: não se continuará com as listas de blocos.

Translating these error messages:

Installing for the i386-pc platform.
grub-install: warning: this GPT partition label does not contain a BIOS Boot Partition; integration will not be possible.
grub-install: warning: Integration impossible. GRUB can only be installed in this configuration using block lists. However, block lists are unstable and their use is discouraged.
grub-install: error: block lists will not continue.

Due to this error, i have not yet executed the command "sudo update-grub"

Aaah, i have to mention the partition, like /dev/sda5, in this case, my root, right?

NOTE: To start booting with manjaro, i have to go to BIOS and switch boot mode to Legacy and save, then manjaro it's booted (was booting normally before this problem). Maybe this is the cause of this error, i didn't configured grub since i installed manjaro.

If your Manjaro installation was installed using legacy boot - you cannot boot it in UEFI mode.
If you need UEFI boot (to boot other operating systems on that machine) I suggest to reinstall Manjaro in UEFI mode.

1 Like

Yes yes, i know that

And ah, i don't mind having to change the boot mode whenever i want to go to linux, it was already like this normally. Do I really have to move to UEFI?

And what about those errors when installing grub (grub-install)? I mentioned them in the past answer.

Maybe this is the solution:

If you want to use GPT partitions with old-style BIOS boot mode, then you need to create a BIOS partition of a few megabytes (16MiB should be fine and future proof) on the device where you want to install grub with `grub-install` .

Use, e.g. `fdisk` to create the partition of type "BIOS boot" somewhere on your disk.

Have this command to try too: "sudo grub-install --root-directory=/mnt /dev/sda"

1 Like

If you can live with the manual boot mode switching - no. It's your system and it'll work in legacy boot as well.

I've never tried to use gpt partitioning with legacy boot :man_shrugging:
That hint you quoted looks promising though.

1 Like

Maaan! Thanks! It worked! I did what i said in the last reply (created a partition with 1 - 2mb and set its flag to “bios_grub” and grub-install /dev/sda worked very fine!), and when i restart or turn off and turn on again, i can boot in manjaro!!! :slight_smile: :slight_smile: Yes!

Thank you all!

1 Like

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

Forum kindly sponsored by