DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just installed Kali Linux 2017.1 onto a USB drive. The installation went well with no errors (except the missing firmware files namely iwlwifi-8000C-26.ucode, iwlwifi-8000C-25.ucode, iwlwifi-8000C-24.ucode and iwlwifi-8000C-24.ucode; but I chose to ignore this and went on with the installation).
When I booted into the system, I was greeted with this error:
Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! /dev/sdc2 does not exist. Dropped to a shell!
Busybox v1.22.1 (Debian 1:1.22.0-19+b2) built-in shell (ash) Enter 'help' for a list of built-in commands.
(initramfs)
have looked for solutions to this error but have not come across one which concerns Debian. I have also tried to implement solutions for those other operating systems but I have either failed to do so or they just haven't worked.
It's more or less telling you what went wrong. The kernel couldn't find the root partition. It was looking for /dev/sdc2, but apparently that doesn't exist. So it is helpfully suggesting three troubleshooting steps:
1) Check the kernel command line. Does it specify the root partition you actually want?
2) Did the kernel delay long enough before trying to read the usb drive's partition table? Check the rootdelay argument on the kernel command line. It takes time to load usb drivers.
3) Does the kernel have access to all the driver modules necessary for reading this partition: usb, sata and the filesystem?
You also need to ask yourself why you are using Kali in the first place. This is a highly specialised distro used by system administrators for security testing. It's not suitable for beginners.
Distribution: Debian testing/sid; OpenSuSE; Fedora; Mint
Posts: 5,524
Rep:
Your error is almost always due to incorrect kernel line in grub or a missing module for the hard drive. When the GRUB screen appears, hit "e". Edit the kernel line to point to a valid root device. You can use the UUID, or specify a device file, like "/dev/sdb" or other device.
If you can't understand what I mean, you have no use for kali!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.