Announcement

Collapse
No announcement yet.

booting after /sbin/init whacked?

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    booting after /sbin/init whacked?

    I tried to force a downgrade in an ill-advised matter, and not the laptop cannot boot kubuntu.

    On a regular boot, I get
    /bin/sh: splash: No such file or directory
    [ 27.125989] Kernel panic -not syncing: Attempted to kill init!

    I get the same result from the recovery option in grub.

    I've found that by removing "splash" from the lines in grub, I can boot into single-user and sh, with a warning that "Target filesystem doesn't have /sbin/init"

    I'm in this situation from trying to force-install packages from 8.04 over 8.10 (particularly, kde and adept) [the newer versions were painful and dumbed down]

    Anyway, the first issue is getting back up.

    I've tried remounting / to get it rw, and then dpkg --configure -a, but on the first package (initramfs-tools), when it tries to create the new image, it announces that

    /usr/sbin/mkinitramfs: line 14: getopt: command not found.

    The obvious solution is to simply reinstall, but the cd drive doesn't work any more and this laptop cannot boot from usb.

    I've made a usb stick from create-usb, but I haven't succeeded in booting from it. If I put it in before powering up, grub sees it as hda(1,0). It seems to me that I should just be able to tell it the partition, set initrd and initrd to the files in /casper, but it seems to hang after a half a screen of messages while configuring the usb stick.

    hawk, stumped
    Noone else may have these opinions without paying my retainer

    #2
    Re: booting after /sbin/init whacked?

    I'm not going to tell you what to do with your system, but if this box were mine, I'd be looking for a "new" used CD drive. On the other hand, you could check into network install procedures.

    Without the ability to initiate a working OS, that thing's a brick.
    The next brick house on the left
    Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.27.11​| Kubuntu 24.04 | 6.8.0-31-generic



    Comment


      #3
      Re: booting after /sbin/init whacked?

      Ouch! Between a rock and a hard place... No CD, no USB to start from. The other candidates are floppy or hard disk, i.e. you could try and find a bootable floppe that would give you USB support and to boot off your usb stick or you take out your hard drive, stick it onto another computer _somehow_ and install onto that hard drive using another CD.
      Once your problem is solved please mark the topic of the first post as SOLVED so others know and can benefit from your experience! / FAQ

      Comment


        #4
        Re: booting after /sbin/init whacked?

        It's not completely dead in the water--I can still boot single user, use usb after that, and I can also boot darkside XP. I assume that I also can bring the network up in single user once I look up instructions for the debian ifconfig.

        hawk
        Noone else may have these opinions without paying my retainer

        Comment


          #5
          Re: booting after /sbin/init whacked?

          Good news! I don't know the"single user" concept - what does it stand for? Do you have a full shell with cp, mount, nano and all? As root? If so you have a perfect install environment using you custom made usb stick

          How is your partitioning, anything important on /home to save or does it have its own partition?
          Once your problem is solved please mark the topic of the first post as SOLVED so others know and can benefit from your experience! / FAQ

          Comment


            #6
            Re: booting after /sbin/init whacked?

            Kubuntu hides it behind its eye-candy bar, but Unix and its workalikes (e.g., linux) come up in a single user mode (runlevel 1?) which checks the system and then initiates multiuser (literally announcing, "going multiuser"). I think multiuser is runlevel 5 (maybe not, I'm getting N 2 on kubuntu box).

            Anyway, at this point, it would really seem to be a matter of force-installing, or possibly even bursting, the appropriate packages. I'm just not sure what the appropriate packages are . . .
            Noone else may have these opinions without paying my retainer

            Comment


              #7
              Re: booting after /sbin/init whacked?

              *buntu does use runlevel 2, normally.

              Great, if you can boot to single user mode. http://www.ubuntugeek.com/install-ub...rom-drive.html seems to indicate that a network install is possible. I haven't tried it, but maybe ...
              The next brick house on the left
              Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.27.11​| Kubuntu 24.04 | 6.8.0-31-generic



              Comment


                #8
                Re: booting after /sbin/init whacked?

                Originally posted by dochawk
                single user mode (runlevel
                Doh! I didn't think

                And thanks for the netinstall link jglen490.
                Once your problem is solved please mark the topic of the first post as SOLVED so others know and can benefit from your experience! / FAQ

                Comment


                  #9
                  Solved (or irrelevant) booting after /sbin/init whacked?

                  I'm finally past this.

                  I was unable to use the instructions for booting from an iso image, as I never had a /dev/loop0 created on boot, which is apparently needed.

                  It turns out that even though it can't boot from a cd, it can boot from a dvd.

                  odd (and a lot of wasted time not trying that!)

                  thanks to all

                  hawk
                  Noone else may have these opinions without paying my retainer

                  Comment

                  Working...
                  X