Bug 53414
Summary: | upgrade fails while lilo configuration | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Need Real Name <stefan> |
Component: | anaconda | Assignee: | Brent Fox <bfox> |
Status: | CLOSED RAWHIDE | QA Contact: | Brock Organ <borgan> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.1 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i586 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2001-09-24 16:55:16 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Need Real Name
2001-09-08 11:22:13 UTC
regarding bug 51122, which looks similar to mine I have definitely no other operating system installed My existing and running lilo.conf is: boot=/dev/sda disk=/dev/sda bios=0x80 map=/boot/map install=/boot/boot.b prompt timeout=50 default=lix image=/boot/vmlinuz label=lix read-only root=/dev/sda2 What do you mean by 'halloween redhat 7'? Hi, it's a RedHat 7.1 burnt on CD by ixsoft (a german company). Give my a hint, who I can give your more details about the distribution. I don't think, this is the root cause of my problem. I fixed my installation for now by running the installation via network. First I had to copy both installation CDs, but that worked fine in the laptop installation and workstation installation mode. In this mode I got for the first time the recommendation, to have more than 250 MB on /. Can this cause the error message I got? Sounds crazy to me. Thanx for your interest It is possible that you could see strange behavior if you tried to use less than 250MB on / because the kernel can run out of inodes, which will cause the kernel to not be able to create any new files, although free space is still available. I'm not sure what the original problem was, but are things working ok now? |