[Leaplist] Serious computer trouble here

[William Ferguson]

Bryan, I don't know whether the old "failed" 500 GB hard drive was
"completely gone." For literally months after that drive "failed," at
each boot-up a warning message appeared in the lower right hand corner
of the screen proclaiming that "A Hard Drive is Failing. Back up your
files immediately."
Well, no file of any kind was recoverable---I mean to say that I never
could access any file on the "failed" 500 GB Hard Drive. To me, it
seemed "completely gone."

Because a second, 250 GB Hard Drive, had previously been installed in
the computer and was available at boot up I continued to use the
computer. All computer work following the "failure" was done on the
250 GB Hard Drive.

I don't know how to use text editors.
I don't know how to manipulate /etc/fstab.

William

On Wed, Feb 17, 2010 at 4:28 PM, Bryan J. Smith <b.j.smith at ieee.org> wrote:
> You are in system recovery mode.  You entered this mode because
> one (1) or more of your filesystems, as specified in /etc/fstab, cannot
> be checked and/or mounted.  Linux, being paranoid, does not want
> to bring the system up with this filesystem in a state it will accept.
>
> In this case, this line is the culprit:
>  /fsck.ext3:   Unable to resolve 'UUID=a9758531-4fb3-4aa7-b357-5688de0cddcb'
>
> The system is looking for an Ext3 filesystem of the listed UUID when
> doing its automated fsck (to see if filesystems are clean).  It cannot
> locate a storage volume with that UUID.  If this filesystem is not required,
> edit /etc/fstab and comment out the line that contains it.
>
> In fact, I'm curious as to where it is attempting to mount that filesystem.
> You say your 500GB drive failed, but was it completely gone?  Or did
> it contain a filesystem with that UUID that is no longer available?
>
>
>
>
> ----- Original Message ----
> From: William Ferguson <ferguson.william at gmail.com>
>
> ...
>
> 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 /
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> _______________________________________________
> Leaplist mailing list
> Leaplist at leap-cf.org
> http://lists.leap-cf.org/mailman/listinfo/leaplist
>

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