OT: [HW] Bad blocks on my hard drive]

Mike Oliver moliver-fC0AHe2n+mcIvw5+aKnW+Pd9D2ou9A/h at public.gmane.org
Wed Sep 6 21:20:30 UTC 2006


Lennart Sorensen wrote:
> On Wed, Aug 30, 2006 at 01:10:38PM -0400, Meng Cheah wrote:
> 
>>I recently bought a Maxtor 250G hard drive.
>>I've been using it for a few months with no problems.
>>
>>I needed to use the remaining 150G as hda4,
>>I partitioned it and ran "sudo mkfs.ext3 -cjv /dev/hda4".
>>
>>It showed:
>>mke2fs 1.37 (21-Mar-2005)
>>Filesystem label=
>>OS type: Linux
>>Block size=4096 (log=2)
>>Fragment size=4096 (log=2)
>>18317312 inodes, 36624183 blocks
>>1831209 blocks (5.00%) reserved for the super user
>>First data block=0
>>1118 block groups
>>32768 blocks per group, 32768 fragments per group
>>16384 inodes per group
>>Superblock backups stored on blocks:
>>      32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 
>>2654208,
>>      4096000, 7962624, 11239424, 20480000, 23887872
>>
>>Running command: badblocks -b 4096 -s /dev/hda4 36624183
>>Checking for bad blocks (read-only test): done                        183
> 
> 
> The position of the '183' is very odd and not at all like the other
> parts of the output.  I have no idea what that is.


Ooh!  Ooh!  I know!  Pick me!

This comes from the progress meter of the test.  From time to time
it prints the block it's currently looking at, and does a carriage
return without linefeed to do it again.  For some reason, when it prints
"done", it erases some of the number, but not all of it.

So the 183 is simply the last three digits of the number of blocks,
which is 36624183.
--
The Toronto Linux Users Group.      Meetings: http://gtalug.org/
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://gtalug.org/wini/Mailing_lists





More information about the Legacy mailing list