<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: How to check for bad blocks</title>
	<atom:link href="http://www.kernelhardware.org/how-to-check-for-bad-blocks/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.kernelhardware.org/how-to-check-for-bad-blocks/</link>
	<description>Your Source for Linux tutorials, programming and hardware advice</description>
	<lastBuildDate>Mon, 06 Feb 2012 05:12:35 -0600</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Linux by dchirila - Pearltrees</title>
		<link>http://www.kernelhardware.org/how-to-check-for-bad-blocks/comment-page-1/#comment-17972</link>
		<dc:creator>Linux by dchirila - Pearltrees</dc:creator>
		<pubDate>Fri, 13 Jan 2012 11:01:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.kernelhardware.org/?p=269#comment-17972</guid>
		<description>[...] Check Partition for Bad Blocks &#124; Fedora &#124; Linux Tutorial  View this post for how to run fsck: “ How should I run fsck on a Linux file system ” To run bad blocks with the read-only option and verbose output: **Recommended to run fsck command on an unmounted partition** -c – use bad blocks read non-destructive [...]</description>
		<content:encoded><![CDATA[<p>[...] Check Partition for Bad Blocks | Fedora | Linux Tutorial  View this post for how to run fsck: “ How should I run fsck on a Linux file system ” To run bad blocks with the read-only option and verbose output: **Recommended to run fsck command on an unmounted partition** -c – use bad blocks read non-destructive [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sagar</title>
		<link>http://www.kernelhardware.org/how-to-check-for-bad-blocks/comment-page-1/#comment-14451</link>
		<dc:creator>sagar</dc:creator>
		<pubDate>Tue, 19 Jul 2011 11:29:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.kernelhardware.org/?p=269#comment-14451</guid>
		<description>Dear Sir,
I use to linux redhat operationg syestem 

Looking for Linux Hosting? Start Here.
I have got 3 OSs on my laptop Latitude Dell D600 (Windows , FC3, Solaris 10)

I have got no problem to boot in any of these 3 OSs.

After while I tried to boot into linux I received this error message :

Run &#039;setenforce 1&#039; to reenable.

Give root password for maintenance (or type Control-D to continue):
this error come to my pc, so pls solved my problem

Repair file system1#</description>
		<content:encoded><![CDATA[<p>Dear Sir,<br />
I use to linux redhat operationg syestem </p>
<p>Looking for Linux Hosting? Start Here.<br />
I have got 3 OSs on my laptop Latitude Dell D600 (Windows , FC3, Solaris 10)</p>
<p>I have got no problem to boot in any of these 3 OSs.</p>
<p>After while I tried to boot into linux I received this error message :</p>
<p>Run &#8216;setenforce 1&#8242; to reenable.</p>
<p>Give root password for maintenance (or type Control-D to continue):<br />
this error come to my pc, so pls solved my problem</p>
<p>Repair file system1#</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gen2ly</title>
		<link>http://www.kernelhardware.org/how-to-check-for-bad-blocks/comment-page-1/#comment-9544</link>
		<dc:creator>Gen2ly</dc:creator>
		<pubDate>Mon, 22 Mar 2010 19:40:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.kernelhardware.org/?p=269#comment-9544</guid>
		<description>fsck -vc/-vcc calls the program badblocks to do this test.  Unfortunately (I&#039;m pretty sure) fsck is only capable of doing this on Linux filesystems (ext 2/3/4?).  If you want to do a full drive test, use badblocks directly:

badblocks -nvs /dev/hda

Unfortunately, I&#039;m not sure this will record the badblocks.  In fact I&#039;m thinking it may not, but at least you can find if they exist.  Badblock I believe are recorded in the filesystem metadata meaning that if, for example, you have an NTFS partition on the drive, you&#039;ll probably have to use the MS toold like chkdisk.</description>
		<content:encoded><![CDATA[<p>fsck -vc/-vcc calls the program badblocks to do this test.  Unfortunately (I&#8217;m pretty sure) fsck is only capable of doing this on Linux filesystems (ext 2/3/4?).  If you want to do a full drive test, use badblocks directly:</p>
<p>badblocks -nvs /dev/hda</p>
<p>Unfortunately, I&#8217;m not sure this will record the badblocks.  In fact I&#8217;m thinking it may not, but at least you can find if they exist.  Badblock I believe are recorded in the filesystem metadata meaning that if, for example, you have an NTFS partition on the drive, you&#8217;ll probably have to use the MS toold like chkdisk.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: madhu</title>
		<link>http://www.kernelhardware.org/how-to-check-for-bad-blocks/comment-page-1/#comment-4606</link>
		<dc:creator>madhu</dc:creator>
		<pubDate>Wed, 15 Jul 2009 10:06:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.kernelhardware.org/?p=269#comment-4606</guid>
		<description>how to add bad blocks in super block inode? possible some examples.</description>
		<content:encoded><![CDATA[<p>how to add bad blocks in super block inode? possible some examples.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: madhu</title>
		<link>http://www.kernelhardware.org/how-to-check-for-bad-blocks/comment-page-1/#comment-4605</link>
		<dc:creator>madhu</dc:creator>
		<pubDate>Wed, 15 Jul 2009 10:02:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.kernelhardware.org/?p=269#comment-4605</guid>
		<description>its useful</description>
		<content:encoded><![CDATA[<p>its useful</p>
]]></content:encoded>
	</item>
</channel>
</rss>

