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

Hello! I use Manjaro KDE with kernel 54 in a notebook with 2 gpu's, dedicated card nvidia and intel hd graphics, and it was all working well (prime-run and nvidia card working withou problems for a week). Dual boot with manjaro and windows 10.

So... I was doing a college homework that i needed to use 2 virtual machines at same time, each one with 2 GB ram, my notebook have 8.

Everything fine... Until i launch the second virtual machine(windows 7) that crashed my whole system, mouse and everything, just freezed for a time. After that, i just pressed the turn off/on button and hard turned off my notebook. When i turn on again... BLACK SCREEN, and i can't run tty, i press ctrl + alt + f2, f3... And nothing happens! Just the same white line (like in a command prompt of windows) blinking with the black screen

I was running virtualbox with prime-run.

I installed virtualbox (Via App Manager) and virtualbox-host-kms and executed this commands before this problem:

sudo pacman -S linux54-virtualbox-host-modules
sudo modprobe vboxdrv

I also added my user to a group of virtualbox

These installations and things, i've made due to this error:

WARNING: The vboxdrv kernel module is not loaded. Either there is no module
         available for the current kernel (5.4.22-1-MANJARO) or it failed to
         load. Please recompile the kernel module and install it by

           sudo /sbin/vboxconfig

         You will not be able to start VMs until this problem is fixed.

And these commands solve this problem of Virtualbox specifically.

I don't remember more things that i've done.
I can start windows without problems, and manjaro live too!

Should i do these commands at manjaro live?:

lsblk
sudo mount /dev/sdxx /mnt
sudo mount /dev/sdxx /mnt/home/

I saw this at: Can't login - black screen & chroot guide

Option 4: manjaro-chroot

Please, someone help me! I need to do my homework and release it today! :frowning:

linux53 is EOL for quite some time, are you sure you were still running that old kernel?

These steps alone won't help your situation but generally the answer is: No. First you should check your filesystems for errors via fsck.
When the filesystems are in order you can mount them to chroot and try to fix your non-booting problem.

What is EOL? Ooh sorry, i'm using linux 54! Sorry

Okay, so i should now check first with fsck at terminal in manjaro live, then if there is no errors, i execute sudo mount... in manjaro-chroot?

Maybe i've executed ”sudo pacman -S linux53-virtualbox-host-modules” wrong, but i'm not sure if i forgot the kernel here or during the execution.
But if i made a mistake at execution, maybe virtualbox would not work properly

End Of Life: not supported anymore.

Check for errors and possibly repair as a first step.
No need to mount manually if you're using manjaro-chroot: It should take care of all necessary steps.

I'm trying to boot with usb again but it's not working! The BIOS is only identifying usb as "Generic Flash Disk" when i enter in windows in UEFI mode, when i put Legacy mode and save booting again, the usb is not recognized more and don't enter in the live manjaro. But sometimes it work, i tested it today, a lil' bit seconds before creating this post!

EDIT: Success now

I executed now these commands:

manjaro-chroot -a:

[manjaro@manjaro ~]$ manjaro-chroot -a
==> Mounting (ManjaroLinux) [/dev/sda5]
 --> mount: [/mnt]
 --> mount: [/mnt/home]

lsblk:

[manjaro /]# lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop0    7:0    0  16.3M  1 loop 
loop1    7:1    0 540.7M  1 loop 
loop2    7:2    0   1.7G  1 loop 
loop3    7:3    0 580.1M  1 loop 
sda      8:0    0 931.5G  0 disk 
|-sda1   8:1    0   100M  0 part 
|-sda2   8:2    0    16M  0 part 
|-sda3   8:3    0 228.1G  0 part 
|-sda4   8:4    0 542.3G  0 part 
|-sda5   8:5    0  72.3G  0 part /
|-sda7   8:7    0   2.8G  0 part 
|-sda8   8:8    0    85G  0 part /home
`-sda9   8:9    0     1G  0 part 
sdb      8:16   1  29.1G  0 disk 
|-sdb1   8:17   1   2.9G  0 part 
`-sdb2   8:18   1     4M  0 part 
sr0     11:0    1  1024M  0 rom

What are these loops?

fsck:

[manjaro /]# fsck
fsck from util-linux 2.35.1
e2fsck 1.45.6 (20-Mar-2020)
/dev/sda5 is mounted.
e2fsck: Cannot continue, aborting.

exit and fsck again, outside manjaro-chroot:

[manjaro /]# exit
exit
 --> umount: [/mnt/home]
 --> umount: [/mnt]
[manjaro@manjaro ~]$ fsck
fsck from util-linux 2.35.1

Commands executed in live manjaro.

You need to run fsck on the filesystems while they are not mounted: Don't use manjaro-chroot until you actually want to chroot into your manjaro installation.

  1. boot from usb
  2. issue fsck for your root and home partitions:
$ fsck -f /dev/sda5
$ fsck -f /dev/sda8

Mounpoints from your usb live iso.

Ooh okay, thanks! : )

Results:

sudo fsck -f /dev/sda5(sudo due to error of permission):

sudo fsck -f /dev/sda5
fsck from util-linux 2.35.1
e2fsck 1.45.5 (07-Jan-2020)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda5: 360886/4743168 files (0.2% non-contiguous), 9241460/18940672 blocks

sudo fsck -f /dev/sda8:

sudo fsck -f /dev/sda8
fsck from util-linux 2.35.1
e2fsck 1.45.5 (07-Jan-2020)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/dev/sda8: 96924/5570560 files (2.5% non-contiguous), 17115914/22269696 blocks

Looks good to me.
Now you can try to identify and repair the issue at hand.

1 Like

Thanks! Do you have any idea of ​​anything that may have caused this problem?

What kind of VMs were you running? Did they have sparse or dynamically sized disks? Is there enough disk space left on your root and home partition?
Do you see any hints/errors in your journal?

I was running one Windows 7 and other Windows Server (i don't remeber your full name). When i started Windows 7 only = no problem, Windows Server only = no problem, Windows 7 and after Windows Server = crash, freeze and only option was to hard restart computer pressing button power on/off. After this, Black screen...

Yes, there was enough disk space left on both partitions. And this is the result of "df" using `manjaro-chroot:

Filesystem      Size  Used Avail Use% Mounted on
/dev/sda5        71G   34G   34G  51% /
/dev/sda8        84G   64G   16G  81% /home
udev            3.9G     0  3.9G   0% /dev
shm             3.9G     0  3.9G   0% /dev/shm
run             3.9G     0  3.9G   0% /run
tmp             3.9G     0  3.9G   0% /tmp
overlay         5.8G  229M  5.6G   4% /etc/resolv.conf

About the disks, i don't know because it was a appliance that i imported only, i have to check this on windows.

About errors in journal, how can i find hints or errors using this in this case? I tried that, but i don't find logs from today at 09:00 AM or a little bit later, just after 11:00.

These questions sound like something more suited to a Windows support forum. Isn't Windows server a corporate version of Windows. Use Windows? Use Windows support channels IMO.

Hello, thanks! But why windows support? The problem it's not on vm, it's on mine manjaro that it's not booting after the use of virtualbox with 2 vm's

Sounds to me like you ran out of ram, do you have a swap?

Use journalctl command.

That timeframe doesn't mean anything to anyone but you: were you using your machine at that moment? Was either the lockup or the black screen bootup happening at that time?

Try a non-quiet boot (if you haven't already) to see some more output and hopefully get some pointers as to the cause.

Yes, i think it too!

I don't know exacly, i remember that i have 2 little partitions and one of them, i created a long time ago to swap (for an old kali linux), should be sda7 or sda9, but i don't know if manjaro it's using him. Here is the commands inside linux live with manjaro-chroot trying to discover that:

cat /etc/fstab:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=1928fcc4-df84-4c74-a8e6-1cc8f9e17568 /              ext4    defaults,noatime 0 1
UUID=ef558c2f-009d-4b97-be72-15221f6fc39b /home          ext4    defaults,noatime 0 2

cat /proc/swaps:

Filename                                Type            Size    Used    Priority

Nothing

cat /proc/meminfo:

MemTotal:        8020376 kB
MemFree:         4532720 kB
MemAvailable:    6274236 kB
Buffers:          400892 kB
Cached:          2000344 kB
SwapCached:            0 kB
Active:          1538744 kB
Inactive:        1519292 kB
Active(anon):     806840 kB
Inactive(anon):   347552 kB
Active(file):     731904 kB
Inactive(file):  1171740 kB
Unevictable:      103192 kB
Mlocked:               0 kB
SwapTotal:             0 kB
SwapFree:              0 kB
Dirty:                 0 kB
Writeback:             0 kB
AnonPages:        760096 kB
Mapped:           402496 kB
Shmem:            497600 kB
KReclaimable:     124416 kB
Slab:             211940 kB
SReclaimable:     124416 kB
SUnreclaim:        87524 kB
KernelStack:        8368 kB
PageTables:        13460 kB
NFS_Unstable:          0 kB
Bounce:                0 kB
WritebackTmp:          0 kB
CommitLimit:     4010188 kB
Committed_AS:    3336072 kB
VmallocTotal:   34359738367 kB
VmallocUsed:       45240 kB
VmallocChunk:          0 kB
Percpu:             2064 kB
HardwareCorrupted:     0 kB
AnonHugePages:         0 kB
ShmemHugePages:        0 kB
ShmemPmdMapped:        0 kB
FileHugePages:         0 kB
FilePmdMapped:         0 kB
HugePages_Total:       0
HugePages_Free:        0
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:       2048 kB
Hugetlb:               0 kB
DirectMap4k:      186996 kB
DirectMap2M:     5969920 kB
DirectMap1G:     2097152 kB

swapon -s: NOTHING

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

Forum kindly sponsored by