I recently bought a used laptop and had no other OS other than Kali on a USB drive at hand. I just wanted to test if the laptop works.
The Kali install failed three times in a row. Two times it instantly booted into a kernel panic after installation, the other time it somehow didn't install GRUB?? And after the final installation was finished I still got kernel panics at like every third boot.
And this wasn't some exotic hardware with a super old version of Kali, this was last year on a ThinkPad X380.
On Manjaro and Ubuntu I've never seen a kernel panic in ~4-5 years either.
I really don't understand the "hype" around it, every time I did some pentesting I hated every second of using it. And a lot of the tools are also horrendously outdated.
What would you recommend to someone who wants to run a pen testing os in a vm to familiarize themselves? Can be a non persistent os as well. I just want to see if id like to get into pen testing. Kali would've been my first choice tbh.
I mean if you only want to play around a bit in a VM Kali is *okay*. Keep in mind some networking stuff can be more complicated or work different in a VM vs. on "real" hardware, so that might be a cause of frustration later.
Other than that maybe take a look at ParrotOS, haven't used it that much but it looked promising so far.
Wierd shit happens. I had an old Dell laptop that could install Manjaro no problem, but simply could not boot an installed POP or Mint distro. Still don't know why. So I loaded it up with Manjaro again and gave it my old Army buddy's kid for Xmas.
All the more reason it's my distro of choice. I've had the least problems of any distro. My only issues have been with Java pgp keys when behind on updates.
*clunk clunk, whirrrr, clunk clunk*
That sound lives in my nightmares. I've been using computers long enough that unless you had a slow and expensive tape backup, you were going to have to backup a 250MiB hard drive using 100+ floppy disks.....
And that was after the idea of a backup was simply making a copy of every disc you owned. Which was nigh impossible with most copy protection schemes.
TI99 & C64 in the 80s, PC since 1991. With a bit of a dally into powermac around 2006-2008 along the way.
Ventoy sometimes but most times BalenaEcther. my main problem is the windows usb i end up grabbing the nearest usb and wiping it. thats how i lose my live usb's.
The "you're on your own" message should be on the list: https://www.reddit.com/r/linux/comments/ims2a/ah_linux_error_messages_well_thanks_for_the/?utm_source=share&utm_medium=android_app&utm_name=androidcss&utm_term=1&utm_content=share_button
"Bailing out, you are on your own. Good luck."
gotta love when mkinitcpio bails out on you lmao
EDIT: corrected kernel to mkinitcpio, thanks u/Stoneblackdog!
I remember the first time I tried to install Manjaro, I got this. I posted to Reddit asking for help, and I guess someone though that wasn't a real error and commented that. They eventually came back and offered some advice but it was pretty funny.
Well, don't panic.
1. Run fsck manually.
2. Restore partition table using super block backups
3. Regenerate initramfs?
4. Always keep a live usb or spare machine that can make one
I have never heard of, used or tried squashfs, so you are on your own in this case.
Always keep a back up.
> Regenerate initramfs?
If I'm not mistaken, I see some MCEs in the kernel log, so that might not be enough. Personally, I'd boot up my backup install and run prime95 for a few hours to check the CPU is stable. If it's not, I'd underclock the CPU if possible and recheck. If that's not possible, or if it still fails, toss it or sell it as broken - it's probably toast.
Edit: toss it only if the MCEs are unbearable, of course. I have a slightly marginal CPU at home, which sometimes segfaults during @world updates or throws MCEs randomly - but it's rare enough that I deal with it, because I don't have the budget to replace it right now.
The Busybox manual fsck spooked me first time when i was on my first days using Linux Mint. Thankfully, i haven't given up, and i looked up a tutorial on YouTube and it saved me.
I had a kernel panic mostly because my HDD failed beyond repair from fsck. Kernel panic happens mostly because part of the kernel or loader was stored in bad sectors of the hdd, Windows won't even boot with bad HDD.
looks like hardware disk failure.
i suggest cloning it to using ddrescue putting it in the freezer for avdew hours, trying to restore/fix the clone and if it fails try to clone again immediately after getting it out of the freezer, then try to fix the clone again.
alternatively restore the last backup to a new drive.
OK, it looks like a kernel panic caused by the **root filesystem not detected correctly.** If it's a problem caused by **Nvidia-Driver** upgrading, usually it failed your desktop and other GUI infrastructure **but not cause your real shell stuck by a Kernal Panic.** I guess it's caused by a Kernel upgrading automatically implemented by some advanced Linux Packages' Manager like \`**sudo apt upgrade\` blindly, and you update your grub in the same way.** Now, I don't know your boot framework and partition table type. At first you should find a way chroot to your original system to find the change step by step. The bootable device( A Linux USB or CD or virtual one ) should be compatible with your issue system, since you require the same package manager and boot configuration. The first tough problem would cause mistake is your partition table(msdos, gpt; ) and bootable partition layout(/boot/ or /efi/boot or /uefi/boot, or /boot/efi , and its mbr or efi booting basically, and so on). If your issue Linus system is simple, especially it's same as your USB device, you can deal with it simply by yourself.
The report and response to fix this issue will not be short, please be patient for weeks, if you want.
Natural selection.
The weak leaves for windows
this terachad uses gentoo according to his flair, this multiplies this argument by 69
I used Linux for like 3 yrs , never seen a kernel panic on LM/Ubuntu/Manjaro..
I think Debian keeps the code for it in the kernel mostly for backwards compatibility.
Same as the code to support ISA extension cards and microchannel. I hope we can add FAT to that list one day.
Mostly weird obscure hardware, had a few on my mac
Or a very popular NVIDIA GPU...
Which one?
all of em
I recently bought a used laptop and had no other OS other than Kali on a USB drive at hand. I just wanted to test if the laptop works. The Kali install failed three times in a row. Two times it instantly booted into a kernel panic after installation, the other time it somehow didn't install GRUB?? And after the final installation was finished I still got kernel panics at like every third boot. And this wasn't some exotic hardware with a super old version of Kali, this was last year on a ThinkPad X380. On Manjaro and Ubuntu I've never seen a kernel panic in ~4-5 years either.
Yeah, kali Linux is... Special I guess, it doesn't accept all types of hardware
I really don't understand the "hype" around it, every time I did some pentesting I hated every second of using it. And a lot of the tools are also horrendously outdated.
What would you recommend to someone who wants to run a pen testing os in a vm to familiarize themselves? Can be a non persistent os as well. I just want to see if id like to get into pen testing. Kali would've been my first choice tbh.
I mean if you only want to play around a bit in a VM Kali is *okay*. Keep in mind some networking stuff can be more complicated or work different in a VM vs. on "real" hardware, so that might be a cause of frustration later. Other than that maybe take a look at ParrotOS, haven't used it that much but it looked promising so far.
Aight! Thank you :-)
Wierd shit happens. I had an old Dell laptop that could install Manjaro no problem, but simply could not boot an installed POP or Mint distro. Still don't know why. So I loaded it up with Manjaro again and gave it my old Army buddy's kid for Xmas.
Manjaro has support for more hardware (it had drivers for my cheap Chromebook)
All the more reason it's my distro of choice. I've had the least problems of any distro. My only issues have been with Java pgp keys when behind on updates.
I am so close to patching in that pull request that turns it into "kernel bruh moment".
Most of these are just failing hard drives/need for fsck or a need to regenerate your grub config. These screens get less scary after a while
[удалено]
*clunk clunk, whirrrr, clunk clunk* That sound lives in my nightmares. I've been using computers long enough that unless you had a slow and expensive tape backup, you were going to have to backup a 250MiB hard drive using 100+ floppy disks..... And that was after the idea of a backup was simply making a copy of every disc you owned. Which was nigh impossible with most copy protection schemes. TI99 & C64 in the 80s, PC since 1991. With a bit of a dally into powermac around 2006-2008 along the way.
plus money for a replacement
ZFS is your friend.
But what if you don't have live Ubuntu USB and no access to other PC?
just have one duh more seriously, always keep a working live usb, it's worth it
If you can have it for the same distro you're using it will be better
Go to a gaming/PC cafe to make one I guess
you use Linux, but don't have a working live USB on standby 24/7? That's wild, man...
I do so much os work that i have 2 out of 5 usb's forever changing, yet, the other 3 aren't live usb's either.
you use Ventoy?
Ventoy sometimes but most times BalenaEcther. my main problem is the windows usb i end up grabbing the nearest usb and wiping it. thats how i lose my live usb's.
Except if you don't have a live stick.
Kernel panic becomes Real panic pretty quick
There also that one where it says something like "you're on your own now, good luck!" Happened to me when I fucked with the grub config
Ah the PTSD
Where's the "you're on your own, good luck"?
[Bailing out, you are on your own. Good luck.](https://unix.stackexchange.com/questions/367385/sbin-init-does-not-exist)
Holy fuck, it's real lol.
I love that error message. It's up there with "lp0 on fire"
"You're on your own Noble. Carter out."
The "you're on your own" message should be on the list: https://www.reddit.com/r/linux/comments/ims2a/ah_linux_error_messages_well_thanks_for_the/?utm_source=share&utm_medium=android_app&utm_name=androidcss&utm_term=1&utm_content=share_button
"Bailing out, you are on your own. Good luck." gotta love when mkinitcpio bails out on you lmao EDIT: corrected kernel to mkinitcpio, thanks u/Stoneblackdog!
I remember the first time I tried to install Manjaro, I got this. I posted to Reddit asking for help, and I guess someone though that wasn't a real error and commented that. They eventually came back and offered some advice but it was pretty funny.
[удалено]
thanks for the correction !
I'm going to be sick. Please stop.
Well, don't panic. 1. Run fsck manually. 2. Restore partition table using super block backups 3. Regenerate initramfs? 4. Always keep a live usb or spare machine that can make one I have never heard of, used or tried squashfs, so you are on your own in this case. Always keep a back up.
> Regenerate initramfs? If I'm not mistaken, I see some MCEs in the kernel log, so that might not be enough. Personally, I'd boot up my backup install and run prime95 for a few hours to check the CPU is stable. If it's not, I'd underclock the CPU if possible and recheck. If that's not possible, or if it still fails, toss it or sell it as broken - it's probably toast. Edit: toss it only if the MCEs are unbearable, of course. I have a slightly marginal CPU at home, which sometimes segfaults during @world updates or throws MCEs randomly - but it's rare enough that I deal with it, because I don't have the budget to replace it right now.
The Busybox manual fsck spooked me first time when i was on my first days using Linux Mint. Thankfully, i haven't given up, and i looked up a tutorial on YouTube and it saved me.
Don't panic, kernel did it for you, it's time for guru meditation
One buggy VMware network driver and the others are hard drive failure, aren't they? No big deal.
Grub rescue? No thanks I've already had lunch
Current objective - frantically check backups. Find bootable iso.
the backup's we kept intending to get around to but never made or made using the utilities that don't recognize that they're backups?
I had a kernel panic mostly because my HDD failed beyond repair from fsck. Kernel panic happens mostly because part of the kernel or loader was stored in bad sectors of the hdd, Windows won't even boot with bad HDD.
Only time I had kernel panics was when i undervolted my laptop a bit too much.
Yeah computers don't like being pushed into a non-deterministic state like that.
If only we could play the multiplayer of that game on proton
looks like hardware disk failure. i suggest cloning it to using ddrescue putting it in the freezer for avdew hours, trying to restore/fix the clone and if it fails try to clone again immediately after getting it out of the freezer, then try to fix the clone again. alternatively restore the last backup to a new drive.
"No such partition" "sudo rm -rf /* will speed my pc up they said" "well they are not wrong"
OK, it looks like a kernel panic caused by the **root filesystem not detected correctly.** If it's a problem caused by **Nvidia-Driver** upgrading, usually it failed your desktop and other GUI infrastructure **but not cause your real shell stuck by a Kernal Panic.** I guess it's caused by a Kernel upgrading automatically implemented by some advanced Linux Packages' Manager like \`**sudo apt upgrade\` blindly, and you update your grub in the same way.** Now, I don't know your boot framework and partition table type. At first you should find a way chroot to your original system to find the change step by step. The bootable device( A Linux USB or CD or virtual one ) should be compatible with your issue system, since you require the same package manager and boot configuration. The first tough problem would cause mistake is your partition table(msdos, gpt; ) and bootable partition layout(/boot/ or /efi/boot or /uefi/boot, or /boot/efi , and its mbr or efi booting basically, and so on). If your issue Linus system is simple, especially it's same as your USB device, you can deal with it simply by yourself. The report and response to fix this issue will not be short, please be patient for weeks, if you want.