System won't boot - different kernel versions

Hello everyone,
I have just made full system upgrade and Icant bool the system -> can't mount /boot/efi because vfat filesystem is not known.
I am using grub, I fixed it but the problem remains.
I have found out that output of 'uname -r' shows kernel version: 3.17.3-1-ARCH and 'pacman -Q | grep linux' shows linux 3.18.2-2. What should I do to load 3.18.2-2?
I think that it is "the root" of my problem,isn't it? Can you help me please?

Head_on_a_Stick wrote:
Have you rebooted?
If you still cannot boot (your post is a little unclear on this), use (arch-)chroot from the live .iso and post the output of:
# parted -l
lsblk -f
Yes, reboot didn't help. Gonna chroot the system.

Similar Messages

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?

Btrfs: System won't boot anymore after unclean shutdown

Hi,
I have a problem with my ArchLinux (kernel 3.19.2-1-ARCH).
I have my root partition as BTRFS and no /boot partition.
After an unclean shutdown the system won't boot anymore.
GRUB loads the kernel and the kernel starts but it hangs saying: Mounted /dev/sda3 on real root.
Then, I have to start a Live CD and do:
btrfsck /dev/sda3
After that the system boots correctly.
I've tried adding fsck to the HOOKS in the mkinitcpio.conf file and in fact it tries to fsck the filesystem (but with BTRFS, fsck.btrfs doesn't work...)
What can I do?
Thanks

I'm also having this problem. I tried booting up the netinstall image to debug it, but I can't mount my btrfs volume from there either: mount just hangs. After a while, the kernel goes:
[...] INFO: task mount:612 blocked for more than 120 seconds.
[...] Not tainted 3.19.2-1-ARCH #1
[...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[...] INFO: task btrfs-transacti:636 blocked for more than 120 seconds.
[...] Not tainted 3.19.2-1-ARCH #1
[...] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
From this post I guessed that I might just need to wait so that I could defrag the volume once it was mounted, but it's been hanging for over 15min now (the message above continues to come up periodically).
Like the OP in the thread I linked to above, my btrfs volume is inside an LVM volume (which is on dm-crypt). Don't know whether that's relevant.
Output of btrfs-check:
Checking filesystem on /dev/pixie/btrfs
UUID: e04cc661-e31a-4dbf-870d-664bc913e34a
found 76855677062 bytes used err is 1
total csum bytes: 72928436
total tree bytes: 2092515328
total fs tree bytes: 1888452608
total extent tree bytes: 104644608
btree space waste bytes: 357251032
file data blocks allocated: 181197139968
referenced 109440282624
btrfs-progs v3.19
dmesg output:
[ 36.824998] Btrfs loaded
[ 36.826713] BTRFS: device fsid e04cc661-e31a-4dbf-870d-664bc913e34a devid 1 transid 98618 /dev/dm-3
[ 46.219014] BTRFS info (device dm-3): disk space caching is enabled
[ 46.259830] BTRFS: detected SSD devices, enabling SSD mode
[ 240.333313] INFO: task mount:539 blocked for more than 120 seconds.
[ 240.335542] Not tainted 3.19.2-1-ARCH #1
[ 240.337795] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 240.340263] mount D ffff8800cf2837f8 0 539 453 0x00000000
[ 240.340277] ffff8800cf2837f8 ffff8800cf2331b0 0000000000013f00 ffff8800cf283fd8
[ 240.340286] 0000000000013f00 ffffffff81818540 ffff8800cf2331b0 ffff8802094f67a8
[ 240.340291] 0000000000000004 ffff8800cf283758 ffffffffa0a2fc91 ffff8802094f67a8
[ 240.340298] Call Trace:
[ 240.340335] [<ffffffffa0a2fc91>] ? set_extent_buffer_dirty+0x71/0xc0 [btrfs]
[ 240.340357] [<ffffffffa0a05796>] ? btrfs_buffer_uptodate+0x56/0x80 [btrfs]
[ 240.340366] [<ffffffff8155e999>] schedule+0x29/0x70
[ 240.340389] [<ffffffffa0a47745>] btrfs_tree_lock+0x65/0x200 [btrfs]
[ 240.340396] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
[ 240.340410] [<ffffffffa09e5cd9>] btrfs_search_slot+0x799/0xaa0 [btrfs]
[ 240.340425] [<ffffffffa09e79f5>] btrfs_insert_empty_items+0x75/0xd0 [btrfs]
[ 240.340446] [<ffffffffa0a47a37>] btrfs_insert_orphan_item+0x67/0xa0 [btrfs]
[ 240.340465] [<ffffffffa0a4a12e>] insert_orphan_item+0x5e/0x90 [btrfs]
[ 240.340482] [<ffffffffa0a4c531>] replay_one_buffer+0x361/0x380 [btrfs]
[ 240.340504] [<ffffffffa0a2f244>] ? alloc_extent_buffer+0x34/0x370 [btrfs]
[ 240.340523] [<ffffffffa0a488f3>] walk_down_log_tree+0x1d3/0x410 [btrfs]
[ 240.340540] [<ffffffffa0a48bfb>] walk_log_tree+0xcb/0x1d0 [btrfs]
[ 240.340558] [<ffffffffa0a507f7>] btrfs_recover_log_trees+0x1e7/0x490 [btrfs]
[ 240.340575] [<ffffffffa0a4c1d0>] ? replay_one_dir_item+0xf0/0xf0 [btrfs]
[ 240.340596] [<ffffffffa0a08b3e>] open_ctree+0x17ae/0x2030 [btrfs]
[ 240.340609] [<ffffffffa09dd633>] btrfs_mount+0x843/0x920 [btrfs]
[ 240.340618] [<ffffffff8117b7aa>] ? pcpu_alloc+0x35a/0x680
[ 240.340628] [<ffffffff811d5d68>] mount_fs+0x38/0x1c0
[ 240.340634] [<ffffffff8117bb05>] ? __alloc_percpu+0x15/0x20
[ 240.340641] [<ffffffff811f116b>] vfs_kern_mount+0x6b/0x120
[ 240.340647] [<ffffffff811f4184>] do_mount+0x224/0xb40
[ 240.340653] [<ffffffff811f4dae>] SyS_mount+0x7e/0xe0
[ 240.340661] [<ffffffff81562809>] system_call_fastpath+0x12/0x17
[ 240.340671] INFO: task btrfs-transacti:561 blocked for more than 120 seconds.
[ 240.342927] Not tainted 3.19.2-1-ARCH #1
[ 240.345175] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 240.348473] btrfs-transacti D ffff88020b88bd98 0 561 2 0x00000000
[ 240.348483] ffff88020b88bd98 ffff880211edc590 0000000000013f00 ffff88020b88bfd8
[ 240.348491] 0000000000013f00 ffff8802162289f0 ffff880211edc590 ffff8802094a70c8
[ 240.348496] ffff8802094d8000 ffff880200000000 ffff8802094d8000 ffff880200000033
[ 240.348501] Call Trace:
[ 240.348511] [<ffffffff811b5d1a>] ? kmem_cache_alloc+0x16a/0x180
[ 240.348525] [<ffffffffa09e07ca>] ? btrfs_free_path+0x2a/0x40 [btrfs]
[ 240.348543] [<ffffffffa0a64213>] ? __btrfs_run_delayed_items+0xf3/0x1d0 [btrfs]
[ 240.348550] [<ffffffff8155e999>] schedule+0x29/0x70
[ 240.348568] [<ffffffffa0a0b555>] btrfs_commit_transaction+0x2a5/0xbe0 [btrfs]
[ 240.348573] [<ffffffff810b4380>] ? wait_woken+0x90/0x90
[ 240.348590] [<ffffffffa0a06fc5>] transaction_kthread+0x1d5/0x240 [btrfs]
[ 240.348605] [<ffffffffa0a06df0>] ? btrfs_cleanup_transaction+0x5a0/0x5a0 [btrfs]
[ 240.348611] [<ffffffff81091748>] kthread+0xd8/0xf0
[ 240.348617] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
[ 240.348624] [<ffffffff81562758>] ret_from_fork+0x58/0x90
[ 240.348629] [<ffffffff81091670>] ? kthread_create_on_node+0x1c0/0x1c0
Last edited by ouroboros8 (2015-04-02 12:37:25)

System won't boot-no chime.

Despite repeated attempts and resetting the CUDA button, the system won't boot when start button is pressed. In the first few seconds it seems to make normal sounds; but no chime and settles into simply fan noise. This is true even if using C (with an Install CD). or Shift key. Is there anything else I can try? (I know it's actually a G3 B&W Motherboard; but I had nowhwere else to post it)

I do not remember exactly what was happening when it stopped. It may have been executing something , hung up, and wouldn't respond to the Command-Opt-Esc or I do remember one incident when it was booting up and stopped when it was partly thru "searching for local discs.
I checked the ref. article and tried to measure the voltages on the power connector. I was never quite sure what pin was what, since the colors did not jive with those in the article. At any rate 2 were approx. + 5 V (one was 4.85), the rest were essentially zero (I believe 1 or 2 were about 300 mv). I did notice that when the power connector is reconnected and start up is attempted, 3 little green lights come on on the motherboard. One goes off after a while.
I have tried the old Sonnet upgrade and have tried reseating all the RAM modules. All to no avail.
The Hard drive and all other parts seemed to be working fine prior to the failure.

System won't boot up

Help please. I have a kt6 delta running an athlon 2700+ xp chip, 512 mb ddr 400.
When I set the fsb at the correct speed for the chip (166) the system won't boot hard drive led lights up constant. dvd drive and cd-r drive each run but the system won't boot. system seems to run fine at default and 133 mhz but the chip is incorrectly identified in windows (xp pro sp1) Any Ideas whats wrong?

Hi - I have the same board with the same processor, I have not problems rebooting after changing the bus speed. But I have had problems rebooting after adding in any card PCI or AGP. the system seems to have trouble clearing the Cmos, I would try clearing the CMOS with the JBAT. it doesn’t always seem to work but I have had some luck, though I have also pulled out the battery a couple of time too..
Good luck!

Upgrade from snow leopard 10.6.8 to montain lion on a iMac system won't boot getting a crossed out circle

Upgrade from snow leopard 10.6.8 to montain lion on a iMac system won't boot getting a crossed out circle

Clean install OS.10.6.8 update it completly. May be you ignored some firmware update.
I have two incedents.
My thunderbolt port stopped working after upgrading to ML 10.8. I booted from external 10.6 , 10.7 still didnt work. Then i clean installed 10.6.8 and ran software update it updated the thunderbolt firmware and all is well now. This firmware update for some reason didnt show up in ML 10.8.
Secondly , when i upgraded my Brother's Macbook from 10.5 to 10.6.3 it would install but stuck with crossed out circle. Then i downgraded checked for update found an efi update , then the 10.6.3 worked fine.

[SOLVED] Switch to systemd - Now system won't boot

I saw that todays update upgrade included the installation of systemd. I looked the wiki and did the necessary changes (I already had made the /etc/hostname etc. files). So I added the
init=/bin/systemd
line to grub and now my system won't boot. I get an error saying something about syslog service not enabled and then a black screen. I can boot my machine fine without the "init=/bin/systemd" line but I want to run a pure systemd system since Arch is moving to it anyway. In the wiki it mentions to install systemd-sysvcompat but it conflicts with initscripts it says. What am I doing wrong or missing?
Last edited by fettouhi (2013-12-08 14:42:04)

fettouhi wrote:
Thanks for the clarification about the DAEMONS list. My DAEMONS list is:
DAEMONS=(!hwclock ntpd syslog-ng !network netfs crond @alsa dbus networkmanager ufw cupsd avahi-daemon samba)
when I try to enable alsa and dbus I get this
[root@andre ~]# systemctl enable alsa-store.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable alsa-restore.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
[root@andre ~]# systemctl enable dbus.service
The unit files have no [Install] section. They are not meant to be enabled using systemctl.
Is LVM handled automatically by systemd? The reason I ask is because I have the USELVM= set to YES in rc.conf.
I made the permanent transition to systemd and did not start alsa at all - sound works fine - so I never bothered with the alsa-store/alsa-restore service files at all - it just works! Also dbus gets handled by default in systemd so you don't need any starting of dbus service at all... it just works.

Different kernel version between systems

Hallo.
We have a three systems landscape ECC 7.00 kernel 7.00
DEV->TST->PRD
Can we upgrade SVI to kernel 7.21_EXT and stay with kernel 7.00 on TES and PRO without problems about transport of object from development to the other systems ?
Thanks a lot.
Mario

I recently worked on a project where we had Kernel 700 and we moved to 720.
We actually did have some issues. When upgrading the kernel and later running SGEN, issues arrised.
I can't remember exactly but, Kernel 720 and newer is built much more granular in terms of DDIC checks. So there is an OSS note you need to apply.
Look at this note 1610716 and 1636252. 1610716 did resolve some a ABAP dump I had
here are some links to follow how to
http://scn.sap.com/community/netweaver-administrator/blog/2013/05/22/upgrading-sap-kernel-from-release-700-to-sap-kernel-720rel-720ext
http://he-troubleshoots-he-scores.blogspot.ca/2013/06/sap-kernel-720-upgrade.html

New GTX 770 in existing system won't boot

So I thought I upgrade my PC with a brand new MSI GTX770. The system just won't start. Screen shows B2 in lower right hand corner and a solid cursor upper right. After a while the cursor starts blinking and B2 dissapears. Still a black screen. No possibility to enter bios, no bleeping, all fans are spinning.
When I put back in my good old MSI GTX580 all is fine again.
I am an advanced (MSI) user but never ever experienced this before. Highly frustrating and surely no plug and play experience. What to do? Underneath you'll find my systems components:
OS: Microsoft Windows7 64bit Home Premium Gold (SP1)
SSD (boot): Samsung SSD 840 EVO 250GB
Memory: Corsair Vengeance BLUE,1600-8GB KIT
PSU: Cooler Master Silent Pro M2 720WATT
Mobo: MSI Z77A-GD65, s1155, 4x DDR3, 4x SATA-300, 4x SATA-600
BIOS Version Mobo V10.1/21020208
VGA (new): MSI Geforce GTX 770 2Gb
VGA (old): MSI Geforce GTX 580 1,5Gb
CPU: Intel Core i5 3570K, 1155, 3,4GHz, Box
CPU Cooler: Scythe Mugen 2 Rev. B
HDD: Seagate Barracuda 2TB - 3.5inch
SSD: Crucial m4 , 128GB, 2.5", SATA 600, SSD
DVD: Sony Optiarc DVR DL 24X,SATA
Casing: Corsair Graphite 600T
PS: I did not manage to find a similar problem on this forum let alone a solution to it. I tried BIOS A vs BIOS B to no avail. Somewhere else I read I may have to flesh the new cards BIOS but how to do so if I cannot even get it to work?
Any help is welcome!

Today I received the following I was like really???!!!!
"Dear Sir/Madam,
Thanks for contacting MSI Technical Support Team!
Regarding your concern, there are many possibilities on why the system could
not boot up. Therefore, would you kindly please refer to the suggestions below to
troubleshoot the issue?
1) Unplug all the components and devices on the MB, and then reinstall the CPU,
RAM (one piece), VGA card and power supply only. Please add some thermal
gel on the CPU, and then reinstall the CPU fan correctly and tightly.
2) Clear CMOS (How to clear CMOS, you could refer to the manual), and then
enter bios to Load Optimized Defaults->Save & Exit.
3) Try to boot up the minimum system. If it still cannot boot up, please change
another more powerful power supply for a try;
4) If the problem still persists, please change another RAM with different brand to
try.
5) Please confirm the processor installed is compatible with the MB as well as
the BIOS.
6) If these attempts above does not work, we have to suggest you contact your reseller (The place you bought this MB from) and have them test the MB completely for you to check if this MB is faulty or not, then ask for some help.
If the reseller for some reason can not help, you could try to contact MSI distributor from below http://www.msi.com/service/wheretobuy/ near your place or MSI office from below http://www.msi.com/about/contact-us/
Best wishes,
MSI Technical Support Team!"
So adding a MSI card to my MSI Board mean I have to brake down all of my system, even remove my CPU (running fine) and buy some thermal gel. And while I am in the store buy a more powerful powersupply (mine already meets the specs) and/or ask my reseller to help me out checking if my motherboard (working fine) is faulty?
Well I just RMA'd my 770. So much for plug and play; even MSI parts are not compatible. A real bummer.

System won't boot after switching to higher performance

I recently installed snow leopard on my 2009 MacBook Pro. Things have going going very smoothly so far. However, I have had one setback. When switching to a different energy saver mode (either from higher performance to energy saver or vice versa), the computer won't boot back up. It will sit at the blue screen with the spinning wheel. Sometimes the wheel will freeze and the dock and my desktop will show up, but the computer is frozen. This forces me to do a manual shut down. This happens about every other time I try to boot my system into a different energy saver mode. Anybody else have a problem with this?

Hi DPer & welcome to the forums...
Try resetting some of the hardware involved (PRAM~NVRAM). See this Apple KB for details, etc.:
http://support.apple.com/kb/HT1379
Can't hurt to try, and apparently this has helped others recently.
If still no joy, did you update via Software Update or did you download the combo? If you used Software Update, get the Combo updater instead and re-apply:
http://support.apple.com/kb/DL959

Arch Won't Boot After Kernel Upgrade

I installed Arch on VirtualBox, but after upgrading the Kernel to 2.6.30 it wouldn't boot. It gets to "Loading udev...." and then VirtualBox crashes.

Hello, I'm having this same problem, except I'm not using VirtualBox or VMWare, I have Arch installed to the hard drive. It worked fine after upgrading to 2.6.30, but after upgrading kernel-headers to 2.6.30.1-1, neither Arch NOR Arch-Fallback will boot! I don't even get to Udev or the part where the two arch logos are on top. It just starts up a little bit, then restarts my computer.
I don't even know if my system has been wiped or something, but I doubt that; I think it's just the booting process. I do have a 2009.2 Live CD, but it's an FTP installation. Is there any way to start up my live CD and do a pacman -U for the old kernel version with the cache on my hard drive? How would I do this?
Last edited by Allamgir (2009-07-07 00:32:12)

Why the different Kernel version?

While I am trying to figure out why my G4 X Serve cannot connect to the Intel X Server as an OD Replica, I noticed although the two are running the exact same version (10.5.4-build 9E17) of software, the Kernel versions are different: G4 - Darwin 9.4, Intel - Darwin 9.0.
Is this normal? And if it isn't, how to correct this? Thanks for any tips.

Well I guess you could use chgrp on a symlink, but only to protect the symlink itself which is pointless here as it's root:root anyway, and why wouldn't you just use root:root on symlinks you don't want users to tamper with? If you do manage to think of an occasion where you need to change the ownership of symlinks you could use chgrp...
EDIT/ Doh even that is useless as you can't really protect symlinks as AFAIK permission will be set by parent directory...
Also, if the /dev/cdrom symlink did manage to disappear it would just be recreated on the next boot by systemd/udev!
Last edited by Meyithi (2013-02-07 19:02:00)

MSI G31M3 V2 Motherboard - System won't boot unless Vid Card Reseated

Strange issue
MSI G31M3 V2 Motherboard Nvidia 8400gs graphics card
PC won't boot unless you reseat the video card. The box is not moving so this constant need to reseat is wierd. Is there an issue with this motherboard and Nvidia Cards?

Quote
Bios is loaded default - I haven't made any changes yet
The BIOS Version depends on the date the board left the factory. There is no default version. Please check your current Version for comparison.
Quote
480w PS Sunbeam I believe
Please check the sticker on it and write down the current limits (A) on all main voltage rails (12V, 5 V and 3.3V).
Have you tested a different video card at any point?

[SOLVED] System won't boot (boots fine in fallback mode)

HI guys,
I just rebooted my headless server for the first time in a while, but it won't boot up.
I just sits at this screen:
Please note the system does boot using fallback mode.
(also, nothing to do with the latest boot problem - systemd-sysvcompat is installed and boots fine in fallback)
Last edited by kaipee (2013-05-18 21:23:13)

That screen shot looks like its booted to me? I see a login prompt

System won't boot with incorrect date/time

Hey, I setup a computer back home for VNC, however there was a power outage and now the BIOS has reset. Unfortunately it defaults the date to 2099 for some reason, anyway now the computer won't boot (I can't remember the exact error). Anyway the trouble is I can't access that computer now, and it has no monitor hooked up, is there anyway I can force a boot with just keyboard and without setting the correct date in the BIOS (no one with access to the computer could do this).
Appreciate any help.

You can try to just press F1.
I have a similar issue with my home server, the battery on the motherboard is dead so when the pc is powered off for a while it will not remember the clock. When trying to boot the system in such a case it spits out an error where it offers to "ignore" the error if you press F1.
In my case I need to wait until my pc beeps before pressing F1, basically you need to get past the BIOS stage.
With a bit of luck it might work for you too.
Also I hope you have some ntp service running on your system to make sure the date gets set correctly on your system on bootup.
Last edited by Neburski (2014-02-19 12:35:00)

System won't boot - different kernel versions

Similar Messages

Maybe you are looking for