after installing the current koji kernel for my x86_64 system (for the purpose of testing video), very early in the boot process, i got the following diagnostic flashing on the screen, followed by a total system hang:
JBD: barrier-based sync failed on dm-0:8 - disabling barriers
i powered down, powered back up, and got further into the boot process up to the network initialization, then rapid flashing of ADDRCONF messages on the screen, then another hang.
thoughts?
rday --
======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca Linked In: http://www.linkedin.com/in/rpjday Twitter: http://twitter.com/rpjday ========================================================================
On Wed, 6 May 2009, Robert P. J. Day wrote:
after installing the current koji kernel for my x86_64 system (for the purpose of testing video), very early in the boot process, i got the following diagnostic flashing on the screen, followed by a total system hang:
JBD: barrier-based sync failed on dm-0:8 - disabling barriers
i powered down, powered back up, and got further into the boot process up to the network initialization, then rapid flashing of ADDRCONF messages on the screen, then another hang.
hang on, a quick followup. the system wasn't hung, video was just trashed but i could still get to the virtual consoles. so i'm guessing it's a video thing. argh.
rday --
======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Annoying Kernel Pedantry.
Web page: http://crashcourse.ca Linked In: http://www.linkedin.com/in/rpjday Twitter: http://twitter.com/rpjday ========================================================================
On Wed, May 06, 2009 at 09:19:32 -0400, "Robert P. J. Day" rpjday@crashcourse.ca wrote:
JBD: barrier-based sync failed on dm-0:8 - disabling barriers
i powered down, powered back up, and got further into the boot process up to the network initialization, then rapid flashing of ADDRCONF messages on the screen, then another hang.
thoughts?
Barriers are not supported by some block devices. This includes at least most software raid and most dm devices. Though I have seen suggestions that dm devices with one underlying device (in particular dmcrypt) are getting support for that. I don't know what the current status of that is.
When you try to use barriers when you can't they just get disabled and things should still work. The only difference will be if there is a crash of some kind, in which case some stuff may be written out of order which might be problematic. This is unlikely to be the cause of your boot problems.
I don't know if this will help - The "barrier based sync failed on dm-0:8" is I think a symptom of something else.
Today, I experienced the same, and "solved" it:
Everything was running fine w/ kernels: 2.6.29.4-167.fc11.x86_64 2.6.29.5-191.fc11.x86_64
Today, updates included a new kernel: 2.6.29.6-213.fc11.x86_64
On reboot, the JBD message came; I tried the previous kernel and boot was fine.
I looked through the yum logs, saw a kernel update had happened.
If you have a non-standard video driver in your system install (before you tried this kernel) you may be experiencing the same symptom I did.
Your choices are to restore the default video driver in /etc/X11/xorg.conf, or re-install the optional video driver.
I use NVIDIA's graphics driver (dual-headed). For the 64 bit kernel (at least), with each Fedora Kernel update I have to "re-install" (well, probably just re-compile the kernel interface to the nvidia driver, but I let it do all it's default things anyway).
To accomplish this, I change to init 3, run the nvidea driver installer, and reboot. If you can't boot, you can bootsrap from a live CD, and change your /etc/inittab (to init 3), and then boot from the kernel of interst. Since this is a bit of a pain, I've also changed /boot/grub/grub.conf (commenting out hiddenmenu).
You can see more comments about this on 2linices.blogspot.com
Regards, Yarko
On Sat, 25 Jul 2009, yarkot wrote:
I don't know if this will help - The "barrier based sync failed on dm-0:8" is I think a symptom of something else.
Today, I experienced the same, and "solved" it:
Everything was running fine w/ kernels: 2.6.29.4-167.fc11.x86_64 2.6.29.5-191.fc11.x86_64
Today, updates included a new kernel: 2.6.29.6-213.fc11.x86_64
On reboot, the JBD message came; I tried the previous kernel and boot was fine.
I looked through the yum logs, saw a kernel update had happened.
If you have a non-standard video driver in your system install (before you tried this kernel) you may be experiencing the same symptom I did.
Your choices are to restore the default video driver in /etc/X11/xorg.conf, or re-install the optional video driver.
I use NVIDIA's graphics driver (dual-headed). For the 64 bit kernel (at least), with each Fedora Kernel update I have to "re-install" (well, probably just re-compile the kernel interface to the nvidia driver, but I let it do all it's default things anyway).
To accomplish this, I change to init 3, run the nvidea driver installer, and reboot. If you can't boot, you can bootsrap from a live CD, and change your /etc/inittab (to init 3), and then boot from the kernel of interst. Since this is a bit of a pain, I've also changed /boot/grub/grub.conf (commenting out hiddenmenu).
You can see more comments about this on 2linices.blogspot.com
Regards,
You can set the runlevel at the grub screen. I think you can hit escape to get rid of the splash screen, I always comment it out in grub.conf, so cant be sure of this. Then, press the letter A, hit space and the number 3. Saves a visit to the live CD.
HTH.
On Sat, Jul 25, 2009 at 11:26:25 +0200, yarkot no-reply-gw@fcp.surfsite.org wrote:
I don't know if this will help - The "barrier based sync failed on dm-0:8" is I think a symptom of something else.
Most of the device mapper block devices can't handle barriers. It's normal to get a message like that if you enable barriers at the file system level and one of the underlying block devices doesn't support them.
-
Bruno Wolff III -
potat0 -
Robert P. J. Day -
William F. Acker WB2FLW +1 303 722 7209