SCIENTIFIC-LINUX-USERS Archives

July 2014

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Dormition Skete (Hotmail)" <[log in to unmask]>
Reply To:
Dormition Skete (Hotmail)
Date:
Thu, 10 Jul 2014 21:05:05 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
Well, I have some progress.  The server now boots, thank God.

Here’s what I did:

I booted using the Rescue disk, and mounted the file systems.

I changed the last field in the /etc/fstab file to 0.  Even more Googling turned up a thread that said that last field of each line tells the system whether or not to force a file system check on it.

Then I went into /etc/selinux/config and disabled SELinux.

I then ran: 

# fixfiles -f relabel
# touch /.autorelabel    (probably not necessary)
# reboot

The system came up!  All the way to a GUI.

I then changed the fields in /etc/fstab back to their original settings (1 for “/" and 2 for “/home").

I rebooted again.

It came back up to a GUI again without any file system check problems.

Unfortunately, the thin clients are not working.  They give an nfs error.  I need to look into that further, as that is this server’s primary function.  But I think that will probably be more appropriately asked on the LTSP group, if need be.

I am getting a "Transport endpoint is not connected” error when I halt the system, but I’ll look into that later.

I know I should probably set SELinux back to permissive mode, like it was, but that can wait, too.  I need to get the thin clients back up first.

I thank you all *very* much for your help.  I really appreciate it.  

Thank you again.

Peter, hieromonk

ATOM RSS1 RSS2