"JDB barrier-based sync failed" how serious?
I have SuSE 9.2 on an old Athlon 1.1 system, with two identical 30GB hard drives. One has the "/" and "/boot" partitions, and the other has the "/swap" and "/home" partitions. I'm using ext3, only because I saw some warnings in this list about problems with Reiserfs that I previously used for a few years. Following a recent YOU update, I was having slowdowns and glitches (the system had been up for two or three months), so I shut it down the other night and restarted the next morning. I was unable to load from HD, and unable to repair. I kept getting this message during startup: "JDB barrier-based sync failed on hda3 - disabling barriers" Google gives exactly one hit on that. I re-installed from DVD (including allowing YOU to bring the system up-to-date). At the next reboot, I get the "barrier-based sync failed" message again, but at least the system is currently working (and I"m writing this in KMail). My question is: Am I more likely looking at a kernel-related issue, or a hard-disk hardware problem? I'm considering walking across the street to my friendly neighborhood computer store and buying a replacement hard disk for HDA. There have been no complaints from the system about HDB (which I mentioned is the same model as HDA). But if this is system/kernel related, then I'd be wasting my money. What do the wise ones say? Kevin
On 13:40 Wed 29 Dec , elefino wrote:
I have SuSE 9.2 on an old Athlon 1.1 system, with two identical 30GB hard drives. One has the "/" and "/boot" partitions, and the other has the "/swap" and "/home" partitions. I'm using ext3, only because I saw some warnings in this list about problems with Reiserfs that I previously used for a few years.
Following a recent YOU update, I was having slowdowns and glitches (the system had been up for two or three months), so I shut it down the other night and restarted the next morning. I was unable to load from HD, and unable to repair.
I kept getting this message during startup: "JDB barrier-based sync failed on hda3 - disabling barriers" Google gives exactly one hit on that.
I re-installed from DVD (including allowing YOU to bring the system up-to-date). At the next reboot, I get the "barrier-based sync failed" message again, but at least the system is currently working (and I"m writing this in KMail).
My question is: Am I more likely looking at a kernel-related issue, or a hard-disk hardware problem?
I'm considering walking across the street to my friendly neighborhood computer store and buying a replacement hard disk for HDA. There have been no complaints from the system about HDB (which I mentioned is the same model as HDA). But if this is system/kernel related, then I'd be wasting my money.
What do the wise ones say?
Kevin
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
I vote for the kernel. I had to revert to 9 Pro for the 2nd time in as many distros because of [apparent] kernel problems all relating to ppp, in my case. -- ..."Yogi" CH Namasté Yoga Studio Closed 15DEC - 3JAN
On Wed, 29 Dec 2004 13:40:14 -0500, elefino
I have SuSE 9.2 on an old Athlon 1.1 system, with two identical 30GB hard drives. One has the "/" and "/boot" partitions, and the other has the "/swap" and "/home" partitions. I'm using ext3, only because I saw some warnings in this list about problems with Reiserfs that I previously used for a few years.
Following a recent YOU update, I was having slowdowns and glitches (the system had been up for two or three months), so I shut it down the other night and restarted the next morning. I was unable to load from HD, and unable to repair.
I kept getting this message during startup: "JDB barrier-based sync failed on hda3 - disabling barriers" Google gives exactly one hit on that.
I re-installed from DVD (including allowing YOU to bring the system up-to-date). At the next reboot, I get the "barrier-based sync failed" message again, but at least the system is currently working (and I"m writing this in KMail).
My question is: Am I more likely looking at a kernel-related issue, or a hard-disk hardware problem?
I'm considering walking across the street to my friendly neighborhood computer store and buying a replacement hard disk for HDA. There have been no complaints from the system about HDB (which I mentioned is the same model as HDA). But if this is system/kernel related, then I'd be wasting my money.
What do the wise ones say?
Kevin
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
There was a recent post in the list about this problem. Google will not find it, as it does not re-check the pages so often. Use the search of the archive. Basically, this message is not dangerous, and is just some kind of warning, so you can omit it. Sunny -- Get Firefox http://www.spreadfirefox.com/?q=affiliates&id=10745&t=85
On Wednesday 29 December 2004 13:48, Sunny wrote:
There was a recent post in the list about this problem. Google will not find it, as it does not re-check the pages so often. Use the search of the archive.
Basically, this message is not dangerous, and is just some kind of warning, so you can omit it.
OK, good. I was concerned because it occurred at the same time as unrecoverable (to me...) corruption to my "/" drive, so I thought that it was related. I'll let it ride for now... with my fingers crossed. Is there anything that I should be looking for in any log that might give me warning that my system is planning to corrupt itself to the extent that fsck can't find a file system? Kevin
participants (3)
-
C Hamel -
elefino -
Sunny