On Mon, 16 Apr 2001, Bob Glover wrote:

> I've fighting a problem with a 60GB drive I got recently.  If anyone can
> help out, I'd greately appreciate it.  I ran mke2fs to put the
> filesystem in the partition (/dev/hdd1).  When I mount the pristine
> filesystem for the first time (right after mke2fs), I get dozens of
> errors like the ones shown below:
>
> Apr 15 23:35:17 tone kernel: EXT2-fs error (device ide1(22,65)):
> ext2_check_blocks_bitmap: Block #496 of the inode table in group 250 is
> marked free
>
> Apr 15 23:35:18 tone kernel: EXT2-fs error (device ide1(22,65)):
> ext2_check_blocks_bitmap: Wrong free blocks count for group 250, stored
> = 32254, counted = 17294
>
> Apr 15 23:35:18 tone kernel: EXT2-fs error (device ide1(22,65)):
> ext2_check_inodes_bitmap: Wrong free inodes count in super block, stored
> = 4128692, counted = 4097999
>
> Apr 15 23:35:11 tone kernel: EXT2-fs warning: mounting fs with errors,
> running e2fsck is recommended
>
> I don't think that running e2fsck is going to help since the filesystem
> should have been clean immediately after using mke2fs.  I've also used
> mke2fs -c with and without the -c, but I always have the same problem.
>
> I've read the Large Disk HOWTO.  It seems overly concerned with getting
> the drive to boot or work with other operating systems.  This new drive
> is on a Linux-only system and it's *not* the boot device.
>
> I've included some particulars here to try to help out:
>
> BIOS:
>
> The BIOS is flashed to the latest version, but it only handles drives up
> to 32GB.  The BIOS would hang on boot unless I set the "alternate"
> jumper which instructs the drive to report that it is a smaller drive
> (32 GB I think).  So I keep the "alternate" jumper on.
>
> fdisk:
>
> It never detects the proper size of the drive.  It doesn't even detect
> what the BIOS detects, so I use expert mode to set the proper numbers.
> I've tried various geometries that work out to just less than the LBA
> size of the drive.  I also tried geometries that use only 32MB and 16MB
> of the drive, but I still have the same problem.  My latest attempt was
> to set the CHS to exactly what the BIOS detects (65531/16/63).  Same
> problem: errors are reported when mounting the newly created, pristine
> filesystem on /dev/hdd1.
>
> Can anyone help me?
>
> - Bob Glover
>
>
You can try specifing the same disk parameter in lilo as you told fdisk
when you partitioned the drive.  See the Disk geometry section of the
lilo docs.  I have never had to use this, so let me know if it works for
you.

Mikkel
-- 

    Do not meddle in the affairs of dragons,
 for you are crunchy and taste good with ketchup.



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to