out of disk space error installing fedora: linux allowcddma not ?helpful
in [RedHat]
|
Prev: out of disk space error installing fedora: linux allowcddma not helpful
Next: RedHat system-config-users not auditing to syslog
From: Eef Hartman on 12 Mar 2010 04:26 In alt.os.linux.redhat General Schvantzkoph <schvantzkoph(a)yahoo.com> wrote: > / 16Bytes I just think you meant 16 GBytes, a root of 16 bytes is a bit small :-) -- ******************************************************************* ** Eef Hartman, Delft University of Technology, dept. SSC/ICT ** ** e-mail: E.J.M.Hartman(a)tudelft.nl - phone: +31-15-278 82525 ** *******************************************************************
From: The Derfer on 12 Mar 2010 16:49 Thanks but none of those suggestions help. I'm already using the custom partition layout. It always comes up with that same error. As before, a SCSI disk on an Adaptec controller with an IDE CDROM connected to the onboard IDE controller. What could be wrong with that?
From: Nico Kadel-Garcia on 13 Mar 2010 01:49
On Mar 12, 5:24 pm, "David W. Hodgins" <dwhodg...(a)nomail.afraid.org> wrote: > On Fri, 12 Mar 2010 16:49:57 -0500, The Derfer <derf...(a)gmail.com> wrote: > > Thanks but none of those suggestions help. > > I'm already using the custom partition layout. > > It always comes up with that same error. > > As before, a SCSI disk on an Adaptec controller with an > > IDE CDROM connected to the onboard IDE controller. > > What could be wrong with that? > > Can you post the output of "fdisk -l"? > > Regards, Dave Hodgins Hmm. You know, there's an old problem with various IDE controllers and sets of SCSI controllers, where different kernels with different modules hardcoded or dynamically loaded wind up with those devices in different "order", and I seem to remember some oddness with certain configurations if you had the CD drive as the "master" device on the "primary" controller, and oh-dear-Ghu, the craziness with Promise controllers when Promise rewrote their published drivers to always list their controllers as the primary device, even if the BIOS thought they were a secondary controller. (It made the higher speed RAID enabled devices show up as /dev/hda and /dev/hdb, instead of /dev/hde and /dev/hdf.) The point is that it might be worth reviewing your BIOS settings and starting with them in defaults, especilly if you've been mucking around with them, and doing just what our friends and colleagues suggest: hit "Ctrl-Alt-F2' to get the text screen during installation steps, and type 'fdisk -l' to get the output. |