I've got a 2GB hard drive, set to CHS 4192,16,63,
normal addressing. Once I get it partitioned correctly
(no DOS on it, so >1024C not problem so I understand),
I get the install to check for bad blocks on each partition,
incl. swap before formatting them.
Badblocks finds *no problems*.
But each time, it'll be installing some package or other, and the
RH install screen will show "No space on device" when there
clearly is, and the kernel messages screen shows:
ext2_new_block:Free blocks count corrupted for block group 34
(A previous time, using different geometry, it had said group 36,
but otherwise, same group each time).
It does this with several packages each time, the actual ones
vary. (Some packages give other sporadic errors, but these seem
to be because of scratched CD). Then it carries on with the install.
Obviously, the 1 time I tried to boot from this, it ran fsck and died
horribly, asking me to run it manually.
As noone's given me an answer to this problem so far, I think it's
probably too late to take the HDD back. But I'd quite like
someone to give me an answer anyway. I have no idea what
this is, and really need Linux on this machine:
It's the family machine and win95 is even flakier on it than it is
on mine. A previous version of Linux ran fine on this, but it was
a smaller disk, and no good for a proper install.
Thanks in advance?
please?
--
Tom Barnes-Lawrence (aka Tomble the Bod)
Kindly remove eggs and spam from email address
if you want to email me.
Gong
I got the same message (not enough disk space) when I tried to load
RH6.0 on a drive that had previously been formatted for NT.
Running fdisk from Dos, and deleting everything - then formatting -
fixed the problem.
Steve
What is your PC? is it a 486, Pentium, what?
I'm just a newbie, but I've never had to set the addressing on my 486
or PII.
[...]
>I've got a 2GB hard drive, set to CHS 4192,16,63,
>normal addressing. Once I get it partitioned correctly
>(no DOS on it, so >1024C not problem so I understand),
Wrong.
>I get the install to check for bad blocks on each partition,
>incl. swap before formatting them.
Set it to LBA to circumvent the 1024 cyl. problem. This isn't DOS
(or any other OS) related at all. It is a generic PC BIOS problem.
>Badblocks finds *no problems*.
>But each time, it'll be installing some package or other, and the
>RH install screen will show "No space on device" when there
>clearly is, and the kernel messages screen shows:
>ext2_new_block:Free blocks count corrupted for block group 34
[...]
Bad disk, broken IDE controller, or otherwise damaged or malfunctioning
hardware components. Other possibility: Broken or outdated fdisk version.
Michael
--
Michael Buchenrieder * mi...@scrum.greenie.muc.de * http://www.muc.de/~mibu
Lumber Cartel Unit #456 (TINLC) & Official Netscum
Note: If you want me to send you email, don't munge your address.
[...]
> Badblocks finds *no problems*.
>
> But each time, it'll be installing some package or other, and the
> RH install screen will show "No space on device" when there
> clearly is, and the kernel messages screen shows:
>
> ext2_new_block:Free blocks count corrupted for block group 34
[...]
If badblocks can test your whole disk surface without problem, AND you
uised the "-w" option (you didn't do a complete test if not), then it
is likely that you have a RAM (or CPU cache) problem. (The filesystem
metadata is cahced in RAM and if you have faulty RAM it can become
corrupted while in RAM). See http://www.bitwizard.nl/sig11/.
--
ACTUALLY reachable as @free-lunch.demon.(whitehouse)co.uk:james+actually