22
leksyib
6y

My linux isn't booting again, Haven't pushed almost 3000lines of code. I'm doomed.

Comments
  • 6
    Thats frustrating. I would say boot up a live cd and see if you can access the drive
  • 1
    @Jifuna I don't have a cd with ubuntu in it.

    All I have is "kernel panic -not sycing: Attempted to kill init! exitcode=0x00007f00
  • 2
    Use another system to make a bootable USB to get the data if possible.
  • 3
    append init=/bin/bash to your kernel line. Hit boot.
    ???
    Profit
  • 1
    @Kimmax it opened bash. But running the 'reboot' command doesn't work
  • 7
    @leksyib that's to be expected
    echo 1 > /proc/sys/kernel/sysrq to prepare reboot
    echo b > /proc/sysrq-trigger to activate
    Killing it old-style will work too, make sure you unmount everything and remount / read only
    OR - if you fixed the system, umount everything that wasn't mounted, remount / read only and call /sbin/init to continue booting normally
    The bash you got is your tool to fix whatever threw you in the panic (some gpu kernel module, maybe -> blacklist it) and get it to boot. After you're alive again, fix whatever initially threw you off
  • 8
    @NoMad every linux can be fixed without a reinstall
  • 1
    Just make a bootable usb drive with Ubuntu on it or something, commit and push your work.
  • 4
    If you need to reinstall, atleast give yourself the pleasurabre experinence of rm -rf / --no-preserve-root
  • 0
    Thanks y'all. I'll just install another distro instead. Maybe ArchLinux
  • 0
    @wolt nope but My windows works perfectly. The windows environment just feels strange tk me tight now.
  • 2
    @leksyib
    If you can run bash you can run reboot (right partition and libc not broken) give it the full path, you probably don't have /sbin on your PATH env variable.
    If you install another distro over, you'll learn nothing out of this :/
  • 0
    Rip in peace
  • 0
    Unless your /home or hard drive is encrypted, you might be able to recover the data. Don't give up that easily.
  • 1
    If it was a rant about ut windows the comments would propose: Switch to linux as solution. What happens in this case?
  • 1
    Aside to the troubleshooting help you just got:

    Look into branches. There's a reason we make small commits, and push regularly to feature branches.

    No way in hell you're supposed to write 3k LoC without backing it up somehow
  • 0
    If you are dual booting with windows, Ext2fsd is rather nice to recover some files, without dealing with livecd/usbs. Allows you to mount ext* file systems in windows.
    https://sourceforge.net/projects/...
Add Comment