Boot failed kali linux

Kali Linux (old install) will not boot

Thank you to everyone for the advice, I have tried everything I could think of but nothing seems to solve the problem. I will format the drive and reuse it. I have this horrible feeling the drive may have a BTC wallet on it from 2010 when they cost nothing, it’s likely to contain something, it’s a shame but sometimes that’s the way the cookie crumbles! I need help with a old (6 yrs ) install of Kali Linux which now fails to boot. The OS does not need to be fixed, as all I want to do is recover some photo files on the drive. These photos can not be replaced and hold great sentimental valve to me as they were taken at my Nan;’s funeral. I know someone will say why was you using Kali as your main system, the answer is because I didn’t understand what it was back then and thought it was a reliable system like any other Linux distro. I have learnt a lot since then. the issue. It will not boot. It gets though grub no problem and asks me if it should start normally or in recovery but whatever I choose it always ends the same way. in initrams this is the output Mount: :dev/mapper/cuckoo-root on /root failed: Invalid argument
mount: /dev on root/dev failed: No such file or directory target file system
doesn’t have requested/sbin/init. No init found.
Try passing init= Bootarg. mod
probe: module echo-Orion not found in modules.dep BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in-shell (ash) enter —help for help /bin/sh: can’t access tty; job control turned off (initrams) This version of BusyBox does not have fsck included and if I type exit it instantly shuts down and won’t allow terminal If I put disk in another machine and use Fdisk -l /dev/sub I get the following Disk /dev/sdb: 232.9GiB 250059349504 bytes , 488397167 sectors
Units: sectors of 1 *512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 33553920 bytes
Disk label type: dos
Disk identifier: 0x000583aa Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 499711 497664 243M 83 Linux
/dev/sdb2 501758 488396799 487895042 232.7G 5 Extended
/dev/sda5 501760 488396799 487895040 232.7G 8e Linux LVM Partition 2 does not start on physical sector boundary If I run sudo fsck -f /dev/sdb I get the following out put Fsck from until-Linux 2.31.1
e2fsck 1.44.1 (24-Mar-2018)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup block.
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem. If the device is valid and it really contains an ext2/etc3/etx4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with alternative superblock: e2fsck -b 8193
or
e2fsck -b 32768 Found a dis partition table in /dev/sdb I have tried both these and every other backup superblock but the system crashes on reboot so don’t know if they just don’t work or are not being used because of the crash. I have had to type this all by hand on a iPhone so please excuse any mistakes I think it’s all accurate. I don’t know what to do next I have read lots of articles online but none have the exact same issue. Any help is very much appreciated Thank you ————————OUTPUT ON BOOT————————- This is the output on the screen \ Mount: :dev/mapper/cuckoo-root on /root failed: Invalid argument
mount: /dev on root/dev failed: No such file or directory target file system doesn’t have requested/sbin/init.
No init found.
Try passing init= Bootarg.
mod probe: module echo-Orion not found in modules.dep
BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in-shell (ash) enter help for help /bin/sh: can’t access tty; job control turned off (initrams) ——————— TRYING TO MOUNT ———————— ## print_req_error: I/O error, dev sdb, sector 231475088 ## JBD2: Failed to read block at offset 2806 ## EXT4-fs (dm-0): error loading journal mount /mnt/1: can’t read superblock on /dev/mapper/cuckoo-root Edit notes I have edited the above so it now explains the issue better

Please click edit and add the content from your Comments above into the original question, then delete the comments. Everything about the problem should be in the Question; please use edit instead of Add Comments.

How was that drive partitioned? ext4, ext3, other? When you attach the old drive to another PC and power up, what does fsck find? linode.com/docs/quick-answers/linux/… may help. Please advise results with edit.

Sorry it wouldn’t let me edit last night. I have updated the OP it now includes all the info, thanks for the advice 🙂

Источник

Thread: «Secure Boot Violation» with Kali USB Boot

Junior Member

«Secure Boot Violation» with Kali USB Boot

The Official Kali Documentation

for making a Kali Bootable USB.

When restarting my computer, I am prompted with Window’s menu screen where you select the Drive you wish to boot from. When selecting the USB Drive with Kali Live, I get the following message:

My main operating system is Windows 10 Home 64-bit

Junior Member

Highly recommend to browse information on secure boot mode settings in your computer.

Hope above helps and good luck.

Junior Member

It’s because the secure boot is activated, related to UEFI
You have to go in the bios of your computer, and search for an option called secure boot
Post scrrenshots if you can, i can guide you and tell you what to do to deactivate it, allowing you to boot your usb drive

Junior Member

I am having a similar issue. I have a full OS installation of Kali on an external SSD and it works fine on a little HP netbook. However, when I try and boot into it with a new Dell G5 I got from work it won’t boot. I get an Error Loading Operating System message. I have been all over the BIOS turning off and on secure boot and Legacy Mode. As a test I made a quick Kali Live thumbdrive and it booted fine. Why isn’t it loading the Kali SSD drive if it will load a live thumbdrive?

Junior Member

Originally Posted by secswurker

I am having a similar issue. I have a full OS installation of Kali on an external SSD and it works fine on a little HP netbook. However, when I try and boot into it with a new Dell G5 I got from work it won’t boot. I get an Error Loading Operating System message. I have been all over the BIOS turning off and on secure boot and Legacy Mode. As a test I made a quick Kali Live thumbdrive and it booted fine. Why isn’t it loading the Kali SSD drive if it will load a live thumbdrive?

Hi — the reason is probably (can’t tell without seeing the thumb drive) because your thumb drive is formatted with a MBR and UEFI falls back to legacy compatibility mode -i.e. UEFI doesn’t know that it’s a Kali distro, it just executes the boot loader from the MBR on the USB. Your SSD is (again guessing. ) probably formatted with with a GPT table rather than with a MBR. If so, then UEFI will only run signed boot loaders if Secure Boot option is enabled

Источник

HackWare.ru

Этичный хакинг и тестирование на проникновение, информационная безопасность

Kali Linux не загружается – решение проблем

Пожалуйста, перейдите на новую статью, в которой собрано больше советов: « Что делать если не загружается Linux ».

При установке Kali Linux несколько раз столкнулся с проблемой, что система просто не загружается. Надеюсь, эта небольшая заметка поможет сберечь время тем, у кого похожая ситуация.

Не загружается Live-образ Kali Linux

Причина может быть в том, что в вашем BIOS (UEFI) включены опции Quick boot и (или) Secure boot. Зайдите в БИОС и отключите их.

БИОС не видит загрузочную флешку

Скорее всего, вы неправильно записали Live образ. Скачайте программу Win32 Disk Imager и создайте загрузочную флешку с её помощью.

Не нужно беспокоится, о версии для UEFI или для БИОСа, поскольку современные Live-образы Kali Linux поддерживают оба варианта. Записанная с помощью Win32 Disk Imager флешка будет грузиться в любом случае.

Загрузка доходит до меню, но замирает на экране консоли или после ввода логина и пароля

Если вы видите загрузочное меню Kali Linux с разными вариантами загрузки и после него продолжается загрузка системы, но она не завершается успехом, значит флешка записана правильно, но присутствуют проблемы в самой системе – чаще всего это несовместимость модулей ядра и самого ядра, отсутствие или дублирование драйверов.

В некоторых случаях может появиться графический интерфейс (менеджер отображения) с приглашением ввести логин и пароль, но после ввода учётных данных вся система зависает.

Аналогичная проблема может возникнуть и с Live образом – следующий рецепт подходит и для установленной системы и для Live системы.

Чтобы избежать эту проблему, когда появится меню загрузки GRUB нажмите букву e. Теперь отредактируйте опции загрузки, добавив nomodeset. Для этого найдите строку, начинающуюся со слова linux и в её конец допишите через пробел слово nomodeset. Для продолжения загрузки нажмите F10.

Эта настройка действует только для текущей загрузки и при последующих перезагрузках системы это нужно делать снова.

Можно сделать опцию nomodeset постоянной для GRUB, но лучше найти проблемный модуль и отключить его.

В данный момент на эту проблему жалуются владельцы компьютеров с видеокартами NVidia. Причина, судя по всему, в конфликте последних версий ядра Linux с проприетарными драйверами NVidia и свободными драйверами nouveau.

Одним из подтверждений этого является строка

iTCO_wdt can't request region for resource

Для отключения nouveau выполните команду:

echo -e "blacklist nouveau\noptions nouveau modeset=0\nalias nouveau off" > /etc/modprobe.d/blacklist-nouveau.conf

Если вы не можете загрузиться в графический интерфейс, то попробуйте с помощью сочетаний клавиш Ctrl+Alt+F1, Ctrl+Alt+F2, Ctrl+Alt+F3 и так далее перейти в консоль. Залогинтесь там и с помощью консольного редактора создайте в папке /etc/modprobe.d/ файл blacklist-nouveau.conf со следующим содержимым:

blacklist nouveau options nouveau modeset=0 alias nouveau off

Для создания файла с помощью текстового редактора nano:

nano /etc/modprobe.d/blacklist-nouveau.conf

Или с помощью vim:

vim /etc/modprobe.d/blacklist-nouveau.conf

Источник

Fix the Unable to Boot Error in Kali Linux

Today I will tell you how you can solve the unable to boot error when installing Kali Linux operating system in a virtual box.

1. WiFi Adapter wlan0 not found Problem [FIX]
2. VLC is not supposed VLC Fix
3. Run Kali Linux as a Windows Subsystem
4. Fix the Mount CD-ROM in Kali Linux
5. L3MON Payload Build Failed error Linux

First of all, while installing Kali Linux, you have some kind of error that is saying that you should use kernel packages for your CPU. So now we will solve this error.

Kali Linux – Go to the Linux Setting In Virtual BOX.

First of all, you have to go to your Kali Linux settings in your virtual box. After this you have to click above the system button as shown in the photo.

Kali Linux – Click the Processor Button.

After coming into the system, you have to click above the processor button, you have also shown in the photo, from here you can increase or decrease the RAM processor etc. of your machine.

Kali Linux – Tick Mark the Extended Features.

Coming to the option with the processor, you will get an option at the bottom of the name of an extended feature, which you have to tick mark and then click on the OK button.

After this your error has been solved, now even if you go to your Kali Linux, there will be no error show.

Testing the Installing Kali Linux.

You can see that my installation process has started and I am not getting any kind of error show.

After all this process my problem is fixed and now I can install my Kali Linux easily as you can see that my installation process has started and now I am being asked to select the language.

If you encounter any problem of any kind anywhere in this whole process, then you can ask me by commenting. If you want to read and block related to hacking then you can go to our website and read.

Related: Fix the Unable to Boot Error Kali Linux

Источник