[Leaplist] Serious computer trouble here

[William Ferguson]

My main computer runs Fedora 11.  The computer originally had a single
internal Hard Drive of 500GB capacity. I later installed a second
internal Hard Drive with 250 GB capacity. Not long after installing
the 250 GB Hard Drive the original 500 GB Hard Drive Failed .

Anticipating that I will soon download and install Fedora 12  I
decided it was time to remove the failed, original, internal, 500 GB
Hard Drive. My plan was to leave the 250 GB Hard Drive, which has
worked fine for months, in the computer and it contains all my present
files. I planned to install Fedora 12 on the new 500 GB Hard Drive and
use it for almost future computer work.

So, today I removed the old, failed, 500 GB Hard Drive. I was careful
to ground myself on the metal chassis of the computer many times
during the mechanical work. Actually, the only work required was to
pull a flat  1/2 inch wide plastic plug and flat cable out of its Jack
and removed a 5 conductor plug and cable out of its Jack.

With the computer's one removed side Panel re-installed, I booted up
the machine.

Now I'm getting to what is wrong:
When I booted up the computer I hit "Scroll Lock" to freeze the opening screen.
"CPU: AMD Athlon 64 x 2  Dual core processor  4200 Speed 2.20 GHz  Count: 2

Press F2 to run Setup
Press F11 for boot menu
Dual Channel memor mode
3968 MB   OK
Auto detecting Pri Master .. Atapi CDROM
Auto Detecting Primary Slave ... Atapi CDROM
Autodetecting SATAII..IDE Hard Disk
Autodetecting SATAII 2... IDE Hard Disk
Pri Master: TSST corp CDDVDW SH-S202N SB01
        Ultra DMA Mode -4
Pri Slave: TSST corp CDDVDW SH-S202N SB01
        Ultra DMA Mode -4
SATAII:  ST3250310AS 4.AAA
        Ultra DMA Mode-6, S.M.A.R.T.  Capable but disabled
SATAII 2: ST3500418AS  CC38
        Ultra DMA Mode-6, S.M.A.R.T. Capable but disabled

I hit ENTER and the Boot up process continued.
User sees a horizontally growing bar graph of changing shade of blue
color growing across
the bottom of the screen as boot up develops and finishes.

Here's what came up on the screen:
"Starting udev
                                                                 OK
Setting host name   violin.home
                                                OK
mdadm: No arrays found in config file or automatically
Setting up Logical Volume Management
                                     OK
Checking File Systems
/dev/sda8:  clean (big numbers of files and of blocks were displayed. Numbers
                             not the names of the files)
/fsck.ext3:   Unable to resolve 'UUID=a9758531-4fb3-4aa7-b357-5688de0cddcb'
/dev/sda7:  clean, 21837/1281120 files,  4360487/5120710 blocks
/dev/sda9:  clean,  (again, big numbers of files and blocks)"





FAILED
***An error occurred during the file system check.
***Dropping you to a shell;  the system will reboot when you leave the shell*
***Warning -- SELinux is active
***Disabling security enforcement for ystem recovery.
***Run 'setenforce 1'  to reenable'
Give root password for maintenance
(or Type Control-D to continue)



I typed the root passwword:
The screen then read:
"bash: cannot set terminal process group (-1): Inapapropriate ioctl for
     device.
bash: no job control in this shell
(Repair filesystem) 1 #

I tried Control-D
Response was: GNU GRUB version 0.97  (639K lower / 3013312K upper memory
A choice of 3 different Fedora 11 versions was offered.
Also offered were the options of booting the selected Op. System,
using 'e' to edit the commands before booting;  'a' to modify the
kernel arguments bfore booting, or 'c' for a command line.

I typed df -h   The response was:  /dev/sda8  Size 20 G  Used 4.0 G
Avail 15 g Used 22%
                   Mounted on /

============================================================================
Is there any way for me to cure this condition?  The computer is unusable.
It seems that both the Hard Drives now installed in the machine are
"capable" but disabled.

I know it's obvious that I don't how to handle this problem.

Any advice and guidance will be much appreciated.

Thank you,

William

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.