Error message : Traceback (innermost last): File "/usr/bin/anaconda", line 438, in ? intf.run(todo, test = test) File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/text.py", line 1030, in run rc = apply (step[1](), step[2]) File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/text.py", line 507, in __call__ if todo.doInstall (): File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/todo.py", line 1619, in doInstall self.createCdrom() File "/var/tmp/anaconda-7.0.1//usr/lib/anaconda/todo.py", line 1189, in createCdrom os.symlink(device, self.instPath + "/dev/" + cdname) OSError: [Errno 28] No space left on device Local variables in innermost frame: device: hdc list: ['hdc'] self: <todo.ToDo instance at 82691f8> cdname: cdrom count: 1 ToDo object: (itodo ToDo p1 (dp2 S'method' p3 (iimage CdromInstallMethod p4 (dp5 S'progressWindow' p6 <failed> This error was generated everytime I tried to install Redhat Linux version 7 - it made no difference which type of setup I chose, or how I went about trying to Install Linux 7. All hardware detection was OK, all partitioning was OK most of the software installation went well but everytime the system would crash with the above error mesage. One time I tried to setup the system as a Server and allowed it to configure and partition the hard drive automatically - all appeared to go well - including - partitioning, formatting, software installation, creation of boot disk etc -. However when the system was rebooted from the hard drive there was no response from the system after going through the bios, rebooting with the boot disk made during setup only returned a series of errors - such as "could not mount filesystem". I gave up after a while and decided to remove Linux from the hard drive, however the hard drive was inaccessible to fdisk, Partition Magic and Norton utilities - on rebooting the PC, the hard drive was not identified or detected by the bios at all. Result : One dead hard drive, one pissed off Linux convert who has been forced back to using Microfuct Wankers yet again. Regards Arie Hol
Does BIOS scan the drive at all? Have you checked the connections? There is really no way for software to kill a drive. It may be the drive actually had a hardware failure.
Closing due to inactivity.