kali linux black screen with underscore virtualbox

VirtualBox Graphical User Interface Version 5.2. So, the old 'sdb', become the 'new' sda.Īfter another reinstall, the boot was finally ok.Model name: Intel(R) Core(TM)2 Duo CPU E7300 2.66GHzįlags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm sse4_1 lahf_lm pti dtherm Reading here, I find that the installer is installing the grub on the first hdd, so I take out the first hdd (the 'sda' which is not for linux) and I keep it only the second (the 'sdb') to install linux. I reinstall again, choose new partition table (erase the disk) and on the boot I get the nice black screen and blinking cursor. At the boot, I get an error about grub and a message: 'no such partition'. Probably, the installer tend to go for the first hdd (the 'sda') even you choose another.Īfter installing Linux Mint 20 with success to a pc with a single hdd, I replace that hdd with other 2 hdd in the same pc, and I install Linux on the second hdd of this two. More than one hdd/ssd, will bring the risk that the installer can go wrong or could install grub to another hdd than the one you are installing linux. If you have more than one hdd or SSD, take out (disconnect) all the rest but the one you need to install linux. Guided will always choose /dev/sda as the first drive and blinking cursor/no boot will result if /dev/sda isn't your OS drive. YAY!īTW, you have to choose Expert install from the menu at the beginning of the installation to do all this and format your HDD 'manually' not 'guided'. GRUB installs into the 32MB boot partition on the correct drive and the system boots normally.

Now, when choosing NO during the GRUB installation step, manually input /dev/sdb, not /dev/sdb1 surprisingly, and it then works. Third partition was the remaining space formatted as 'ext4'. Second partition was my 3.0 GB formatted for 'swap', at the 'end'. So, the first partition I made for GRUB was 32.0 MB formatted for 'boot or something (forget wording)'. With GPT, you have to manually create a GRUB partition. sometimes that black screen with a blinking cursor means there was an issue with the gpu driver during the boot process. In my case, I tried /dev/sdb and /dev/sdb1, but the installer would give me a fatal error every time, which still makes no sense.įinally, I had to format my 120GB drive with a partition table of 'gpt'. This will bring up another screen that allows you to input /dev/sdX. On the GRUB installation step, DO NOT choose Yes to put GRUB onto the 'first' drive. So, when formatting with a partition table of 'mbr' on my 120GB drive, I did the normal 117GB of bootable ext4 and 3GB of swap. dev/sdb is my 120GB drive and /dev/sdc is the other 500GB drive. For whatever reason, the 'first drive' (/dev/sda) is one of my 500GB drives. Two 500GB drives in RAID, that I didn't want to touch during installation, and a 120GB SSD that I use for the OS. I figured out that during the GRUB installation step, it was installing GRUB onto the wrong drive, the 'first' drive (/dev/sda). It was upon installing a fresh Ubuntu Minimal.

In my case, the blinking cursor was all I would ever get. I found a few vague references to rolling over of logfiles at boot time being the cause. Oct 11 23:21:48 linux rsyslogd: exiting on signal 15. Oct 11 23:21:48 linux kernel: Kernel logging (proc) stopped. Oct 11 23:17:21 linux kernel: ondemand governor failed, too long transition latency of HW, fallback to performance governor I should mention that the ondemand governor failed message happens on successful boots but the other two don't appear to.

but figured I'd put it up here in case anyone can help and wants to earn themselves some points. I'm going to do some research on Google etc. It looks like I've captured a recurrence of this issue, I copied the messages file and the dmesg file and had a look where processing seems to have stopped and found the messages below. It's been a while, mainly because my server has been up for a long time. The fact that it is intermittent is what confuses me.Īny pointers on diagnosing the problem would be much appreciated. Has anyone any guidance on how to diagnose this issue or what the cause is likely to be? Normally I need to press the reset button to reboot the PC and often it will reboot fine. From what I've read, this blinking cursor screen is presented by Ubuntu itself and not Grub, so I assume the boot process gets halted for some reason. It gets past Grub and then stops at a blank screen and blinking cursor. Occasionally my Ubuntu 10.04 PC won't boot properly.

Kali linux black screen with underscore virtualbox