Can't boot after system update - INIT: No inittab file found

Hi i've a pc where i installed arch linux more than one year ago
Its a:
PentiumII 400mhz
192mb ram
2 harddrives (don't know if i use them as a lvm or if each consists of 2 partitions used as mountpoints)
graphic card nvidia TNT2
i wanted to update it using "pacman -Syu" but it didnt worked because TNT2 needed nvidia legacy treiber 71xx don't work with kernel > 2.6.26
so i removed currently used nvidia treiber with pacman and installed the xf86-nv driver using pacman...
after that i think i updated just the kernel (pacman -S kernel26)
and than the system (pacman -Syu)
that was successfully....but after my reboot the shock
INIT: No inittab file found
Enter runlevel:
doesnt matter what runlevel i try i can't get further
what should i do now? please help me and provide me something like a step by step guide

menhir wrote:
what kind of live cd should i use?
is there a arch live cd that has the initscripts package include that i don't require to have my wlan working?
where can i find a good tutorial for "chroot" rescue in my case?
Just use the Arch installation disc

Similar Messages

  • Can't boot after system update: unknown filesystem type

    After running a system update, including updating the kernel, I can't boot to the new kernel.
    On booting, grub loads the kernel image, runs/loads udev, but then fails to mount the root partition with error:
    mount: unknown filesystem type 'ext4'
    I have tried reinstalling the 'linux' package via packman several times, also trying the --recursive argument to make sure all my dependencies were there, and after days of googling and tweaking my system, I'm at a loss.
    Thank goodness I happened to keep a spare kernel laying around in /boot.
    Thanks in advance.
    Last edited by jackrabbit (2012-03-22 23:25:28)

    The OP can read their partition initially though, it's only after udev that they can't.
    Also, try adding "rootfstype=ext4" to your grub kernel line. Is your /boot on a separate partition or part of your / partition?

  • System won't boot. INIT: No inittab file found Enter runlevel:

    After the latest update that changed how intel ucode is updated, my system won't boot.
    I think I missed a line when I edited "/etc/grub.d/10_linux" and ran grub-mkconfig -o /boot/grub/grub.cfg.
    Any ideas on how to fix this?
    I can't run grub-mkconfig from another machine, as it uses the live kernel info.
    Any help would be greatly appreciated. Otherwise I'll have to reinstall

    TheSaint wrote:
    SyXbiT wrote:
    But I still get the error:
    system won't boot. INIT: No inittab file found
    Enter runlevel:
    It seems to me that you've an old Arch version. inittab is deprecated AFAIK.
    What is the Arch iso version?
    That would probably be mid-2012 at the very latest I think as that's when I remember completely moving over to systemd...
    @SyXbiT: Are you using the current Arch install ISO?

  • Can't export after system update

    Hi, i just did the system update thing in the software update,
    and now i can't export...
    im on a dual 2ghz powerpc G5 and im running final cut pro 5.1.4
    haven't had any problems untill now,
    just did the update and now if i try to export i get "codec error" or " general error"
    if i try to use compressor it doesn't even start compressing, just says it's finished and then i can't play the movie,
    When i tryed to do export quicktime movie final cut crashes...
    any ideas on how to fix this ??

    Here's the thing. All sorts of things go get funky when you change OS or applications. Although it doesn't help you at the moment, here's the best way to work. When you have a stable OS/Application combo, clone your startup drive. You can use an application like CarbonCopy Cloner (available at versiontracker.com). If you clone to a second internal drive, you can be back at work in a matter of moments.
    You need to add your hardware specs to your profile to help us help you. Are you using any kind of capture card in your make like an aja io? You might need to update your drivers.
    As far as your current state, here are a few things to try:
    Repair permissions (recommended before and after any software or OS update or install).
    Have you actually shut down after the update? A shutdown (leave the computer off for 15 minutes - that means unplugged) and restart will sometimes fix things.
    Do a reinstall of quicktime. Do a search here for the techniques.
    But, I'm wondering if you might have another problem that was not caused by the update. These things do happen.
    You may have a problematic clip or render that finally made your sequence unusable. Do you have any graphic files in your sequence? Are they CMYK? If so, delete them. FCP doesn't play nice with CMYK graphics.
    What format are you working in? Try the following: Capture some new material, edit into a timeline with matching settings and then try an export. Any luck? If so, take a look at your problem sequence. Mark an in at the beginning and an out at the halfway point. Do an export. Does it work? If so, Try exporting the second half.
    You might also try copying the contents of your sequence into a new sequence.
    Just thought of something else you might try that has worked for me with a problem sequence. Select the sequence in the browser or make the timeline active. Hit command-zero (sequence settings). Change the codec to animation. Hit OK. Among other things, this will cause your sequence to become unrendered. It also can sometimes slap fcp on the side of the head and fix a problematic sequence. Now, Do the same thing again and change the codec back to it's original setting.
    I know there's a bunch of stuff here and I've been rambling on, but it's not easy to diagnose these things from a distance.
    Good luck

  • Can't boot after installing updates

    I am quite new apple and this is my first problem I have encountered.
    I downloaded updates and now my computer wont boot. I have tried safeboot and it just freezes on the 'starting OSX bar'. I have inserted 'install disk 1' (which is OSX 10.4.6) and gone through disk utilities to repair permissions and the disk - then starting from the hard drive in safeboot and it still gets no further than the 'starting OSX bar'.
    If I chosse to boot from the install disk will it take me to the 'erase and intall' option.
    What should I do? If anyone can help I would be very grateful.
    Thankyou

    I guess you could skip the steps you have done already...
    Could be many things, we should start with this...
    "Try Disk Utility
    1. Insert the Mac OS X Install disc that came with your computer, then restart the computer while holding the C key.
    2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
    *Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.*
    3. Click the First Aid tab.
    4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
    5. Select your Mac OS X volume.
    6. Click Repair. Disk Utility checks and repairs the disk."
    http://docs.info.apple.com/article.html?artnum=106214
    Then Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes.
    The usual reason why updates fail or mess things up, is if Permissions are not fixed before & after every update, with a reboot... you may get a partial update when the installer finds it doesn't have Permissions to change one obscure little part of the OS, leaving you with a mix of OS versions.
    Some people get away without Repairing Permissions for years, some for only days.
    If Permissions are wrong before applying an update, you could get mixed OS versions, if Directory is the slightest messed up, who knows!
    If many Permission are repaired, or any Directory errors are found, you may need to re-apply some the latest/biggest updates.
    May even need to do an Archive and Install if you have room on the HD...
    http://docs.info.apple.com/article.html?artnum=107120

  • Can't boot after glibc update (even after a fresh netinstall)

    My main system no longer booted after doing a pacman -Syu yesterday, following the instructions at https://www.archlinux.org/news/the-lib- … a-symlink/ .
    I booted a livecd, rsynced my /home to a storage drive and did a netinstall today. The system still doesn't boot.
    The screen goes black after "waiting for udev uevents to be processed" appears, together with expected microcode errors.
    I booted the system with a livecd again and mounted /dev/sda3. /var/log is empty, except for a pacman.log from the install, containing no errors.
    Photo from just before the screen goes blank: https://goput.it/9id.jpg
    inxi -v7 output from sometime before this happened: https://goput.it/rmh.png
    Last edited by ne (2012-07-15 12:43:58)

    Adding nomodeset to the grub kernel line made it boot fine, so I've narrowed it down to a framebuffer issue.

  • Macbook Pro, Can't boot after EFI update....

    Updated the EFI this morning- Prior to that update, everything was working fine. After the update, I have the flashing question mark folder of doom. Can't use internet recovery even while plugged into ethernet. What happened? Everything was going so well Apple! I'm on Lion, latest updates, 2011 MBP 2.2 i7, SSD 120g with a 750g running beside it (data doubler).

    Okay, so the disk is supposed to show up as disk0s2.
    Remember how I'm unable to unmount the drive? I force unmounted it and then used Disk Utility to repair the volume, but still no luck.
    I think the key to the problem is this new HD I put in runs at 3 Gbps. I think I read somewhere that the new MacBook Pro's don't support that.
    I think next I'm going to try swapping out the new HD in my MacBook Pro with the one it originally came with.

  • LILO can't boot after recent update

    After updating today, I cannot boot any longer. My root is on lvm and I also use LILO.
    I've tried the suggestions to boot from live cd and run mkinitcpio without any success. I've also tried reinstalling udev and mkinitcpio with pacman from a live cd and that did not work either.
    When I boot, I see the following messages:
    :: Running hook [udev]
    :: Triggering uevents...done
    :: Running Hook [lvm2]
    Activating logical volumes...
      2 logical volume(s) in volume group "vg1" now active
    Creating device node with major 254 and minor 3.
    :: mounting '/dev/root' on real root
    mount: you must specify the filesystem type
    You are being dropped into an emergency shell
    sh: can't access tty: job control turned off
    [edit] changed title to reflect what I discovered to be the underlying problem: LILO
    Last edited by despotic (2012-05-07 02:42:31)

    Yes, I can manually mount the lvm partitions in the recovery shell.
    Here is my lilo.conf: http://pastebin.com/w0L1kgqv
    Here is my fstab: http://pastebin.com/eyvfnYpC
    Also,  when i try to update udev or linux or device-mapper with pacman, I get the following warnings:
    warning: could not get filesystem information for /bootmnt: No such file or directory
    warning: could not get filesystem information for /cowspace: No such file or directory
    warning: could not get filesystem information for /sfs/root-image: No such file or directory
    warning: could not get filesystem information for /sfs/lib-modules: No such file or directory
    warning: could not get filesystem information for /sfs/usr-share: No such file or directory
    warning: could not get filesystem information for /repo/core/x86_64: No such file or directory
    warning: could not get filesystem information for /repo/core/any: No such file or directory
    warning: could not get filesystem information for /bootmnt: No such file or directory
    Thanks for your help!
    [edit] for anyone looking at this post trying to resolve the above warnings, don't. They don't seem to cause problems and as far as I know they show only during a chroot environment within a live boot, so don't worry about them. If you experience issues, it's most likely related to something else, my particular issue was actually with the LILO boot loader and not related to these warnings at all.
    Last edited by despotic (2012-05-07 02:33:05)

  • Arch hangs on boot after system update

    After I ran 'pacman -Syyu' yesterday, my Arch install won't boot anymore. Instead, it hangs after  'Reached target Graphical Interface' with a blinking underscore. It is the first time I've encountered such problems after running Arch for almost a year and frequently updating. Am I right to assume it might have something to do with the recent kernel/nvidia drivers update?

    Keep checking archlinux site - information was posted here https://www.archlinux.org/news/nvidia-340xx-and-nvidia/
    PS. mark as [SOLVED]

  • [SOLVED] boot failure: No inittab file found

    Hi,
    While trying to upgrade my system according to the recent /usr/bin intervention, I managed to get into an unbootable state:
    INIT: No inittab file found
    Enter runlevel:
    This is because, stupidly, I'd simply removed initscripts. (I thought I'd properly completed the systemd and all previous migrations, considering my system up to date, and figured initscripts was an obsolete remnant.)
    pacman -Qqo /bin /sbin /usr/sbin | pacman -Qm -
    returned
    grub 0.97-21
    grub 0.97-21
    consolekit 0.4.6-4
    initscripts 2012.10.1-1
    So I (again, stupidly) removed consolekit and initscripts and upgraded GRUB (by installing grub-bios and following the guide). I then proceeded to upgrade as described in the intervention notice.
    This, of course, resulted in the following error on rebooting:
    INIT: No inittab file found
    Enter runlevel:
    I've since spent hours trying to repair the system with a live system (booting arch off a thumb drive) and arch-chroot - but
    I don't know what I should install to make things work again
    I haven't managed to figure out how to install packages while offline (despite reading through the guide)
    Any assistance would be immensely appreciated!
    Last edited by FND (2013-06-09 17:23:15)

    Thanks for the quick response!
    Frankly, I'm not quite sure what to make of that link (thus revealing my general ignorance... ).
    Here's my /etc/boot/grub.cfg:
    # DO NOT EDIT THIS FILE
    # It is automatically generated by grub-mkconfig using templates
    # from /etc/grub.d and settings from /etc/default/grub
    ### BEGIN /etc/grub.d/00_header ###
    insmod part_gpt
    insmod part_msdos
    if [ -s $prefix/grubenv ]; then
    load_env
    fi
    set default="0"
    if [ x"${feature_menuentry_id}" = xy ]; then
    menuentry_id_option="--id"
    else
    menuentry_id_option=""
    fi
    export menuentry_id_option
    if [ "${prev_saved_entry}" ]; then
    set saved_entry="${prev_saved_entry}"
    save_env saved_entry
    set prev_saved_entry=
    save_env prev_saved_entry
    set boot_once=true
    fi
    function savedefault {
    if [ -z "${boot_once}" ]; then
    saved_entry="${chosen}"
    save_env saved_entry
    fi
    function load_video {
    if [ x$feature_all_video_module = xy ]; then
    insmod all_video
    else
    insmod efi_gop
    insmod efi_uga
    insmod ieee1275_fb
    insmod vbe
    insmod vga
    insmod video_bochs
    insmod video_cirrus
    fi
    if [ x$feature_default_font_path = xy ] ; then
    font=unicode
    else
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos5'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
    else
    search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
    fi
    font="/usr/share/grub/unicode.pf2"
    fi
    if loadfont $font ; then
    set gfxmode=auto
    load_video
    insmod gfxterm
    set locale_dir=$prefix/locale
    set lang=en_US
    insmod gettext
    fi
    terminal_input console
    terminal_output gfxterm
    set timeout=5
    ### END /etc/grub.d/00_header ###
    ### BEGIN /etc/grub.d/10_linux ###
    menuentry 'Arch Linux, with Linux core repo kernel' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-true-ad4103fa-d940-47ca-8506-301d8071d467' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos5'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
    else
    search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 ro quiet
    echo 'Loading initial ramdisk ...'
    initrd /boot/initramfs-linux.img
    menuentry 'Arch Linux, with Linux core repo kernel (Fallback initramfs)' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-core repo kernel-fallback-ad4103fa-d940-47ca-8506-301d8071d467' {
    load_video
    set gfxpayload=keep
    insmod gzio
    insmod part_msdos
    insmod ext2
    set root='hd0,msdos5'
    if [ x$feature_platform_search_hint = xy ]; then
    search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos5 --hint-efi=hd0,msdos5 --hint-baremetal=ahci0,msdos5 ad4103fa-d940-47ca-8506-301d8071d467
    else
    search --no-floppy --fs-uuid --set=root ad4103fa-d940-47ca-8506-301d8071d467
    fi
    echo 'Loading Linux core repo kernel ...'
    linux /boot/vmlinuz-linux root=UUID=ad4103fa-d940-47ca-8506-301d8071d467 ro quiet
    echo 'Loading initial ramdisk ...'
    initrd /boot/initramfs-linux-fallback.img
    ### END /etc/grub.d/10_linux ###
    ### BEGIN /etc/grub.d/20_linux_xen ###
    ### END /etc/grub.d/20_linux_xen ###
    ### BEGIN /etc/grub.d/20_memtest86+ ###
    ### END /etc/grub.d/20_memtest86+ ###
    ### BEGIN /etc/grub.d/30_os-prober ###
    ### END /etc/grub.d/30_os-prober ###
    ### BEGIN /etc/grub.d/40_custom ###
    # This file provides an easy way to add custom menu entries. Simply type the
    # menu entries you want to add after this comment. Be careful not to change
    # the 'exec tail' line above.
    ### END /etc/grub.d/40_custom ###
    ### BEGIN /etc/grub.d/41_custom ###
    if [ -f ${config_directory}/custom.cfg ]; then
    source ${config_directory}/custom.cfg
    elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
    source $prefix/custom.cfg;
    fi
    ### END /etc/grub.d/41_custom ###

  • Macbook pro won't boot after installing update 10.9.3

    macbook pro won't boot after installing update 10.9.3

    Please read this whole message before doing anything.
    This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
    The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode.
    Note: If FileVault is enabled, or if a firmware password is set, or if the startup volume is a Fusion Drive or a software RAID, you can’t do this. Ask for further instructions.
    Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
    The login screen appears even if you usually login automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    Test while in safe mode. Same problem?
    After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of the test.

  • For Those Who Can't Boot After Upgrading To 10.5.6

    For Those Who Can't Boot After Upgrading To 10.5.6
    (and i am one of those)
    how is Apple supposed to make them able to install future fixes and updates
    once they finally acknowledge and address this horrible bug?
    will they send free bootable CDs with the updates to 10.5.6?

    What "Boot ROM version" do you have (check in the system profiler under "Hardware")? If it's not MBP31.0070.B07 or MBP21.00A5.B08, then you will need to update your MacBook Pro's firmware. To do this, you might need to connect an external display and mouse/keyboard, and then run the computer with the lid closed to bypass the laptop's monitor. Then apply the firmware patch and reboot the system. This might also be doable via "Screen Sharing" if you have that enabled and have another mac handy.
    The firmware update is here: http://www.apple.com/downloads/macosx/apple/firmware_hardware/macbookproefifirmw areupdate151.html
    Message was edited by: Topher Kessler

  • Wont boot after windows update

    M y Sateite A305 s6916 wont boot after windows updates tried to install.

    Satellite A305-S6916
    tried .. every option on F8
    Try this. Download a repair disc from here.
       Windows Vista Recovery Environment ISO X64 version (64 bit)
    If you can reach the Recovery Environment by booting that, try the Startup Repair and let us know what happens. Sometimes you need to run it more than once.
       Startup Repair: frequently asked questions
    Also try a System Restore.
       What are the system recovery options in Windows Vista?
    -Jerry

  • Leopard USB install no longer boots after software update

    Hi all,
    I have recently installed Leopard onto a USB partition in order to perform maintenance on my main Leopard installation. Installation proceeds without a problem however after downloading software updates the USB partition will not boot successfully, despite there being no problems with the disk / volume structures / apparently anything at all. In desperation I also tried to install Tiger, which worked, however I have the same problem after updating - it will not boot! I don't think my hardware is at fault - Techtool Pro tells me all is in order.
    Has anyone had this problem and if so, how did you fix it?
    Thanks,
    Jason

    I just installed Leopard onto a USB 2.0 external hard drive for a dual-boot. It booted fine at 10.5.1 but is taking ridiculously long to boot after 10.5.2 (I just got it to finally boot after the update while waiting more than 40 minutes!).
    It seems that you may want to attempt booting several times - maybe turning off the machine in between or booting to the internal OS first and then to the external. Can't help you much beyond that as this is my introductory experience with this mess.

  • Lack of 3g after system update

    Hello :-)
    It's problem with Xperia E dual
    Few days ago I updated the system to the 4.1.1 version (compilation 11.3.A.1.39).
    Unfortunatelly after updating I've discovered that smartphone don't works with 3G. On the display I've only icon "E". Before updating there was typically "H". Of course now the transfer is slower than before and of course I'm not happy of that.
    I try to solve this problem - choose in menu list of available provider and... there are only 2G nets. Because I've functioning still in the same place of live and the problem has occured after the updating I'm sure that it's strictly connected.
    Is there any solution for that?
    Another problem is with trying to call. After system updating typically twice a day I have to restart smartphone because it's totally hanged. No one can connect with me and I can't call to anybody. Smartphone looks normally and doesn't give any siglan that something is wrong. But when I try to connect to somebody I direst the number and... there is no signal at all. After few seconds telephon return to main menu. There is also no record about this trial of connection in the list of done connections. It's very uncomfortable situation.
    Sure, there are also some adventages with the system updating but problems mentioned above are really annoing.
    Have you any solutions for it?
    Thanks in advance.
    Rafal
    Solved!
    Go to Solution.

    Hi, try repairing phone software with PC Companion or Update Service.
    http://www.sonymobile.com/gb/tools/pc-companion/
    http://www.sonymobile.com/gb/tools/update-service/
    Be aware that this will erase phone data completely, backup if necessary.
    Before proceeding with software repair, confirm with your Network Operator that there is nothing wrong with the network. Also, remove and reinsert SIM card and try again (have a close look at the contact surface, ensure that it is relatively clean).
    Don't forget to mark correct answer as Accepted Solution.
    If you find the post helpful, press Kudos.

Maybe you are looking for