Re: Boot hangs / loops
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
Re: Boot hangs / loops
On Jul 10, 2014, at 4:20 PM, John Lauro wrote: >> >> Filesystem SizeUsedAvail Use% >> Mounted on >> /dev/sda63.9G133M3.8G >> 4% / >> tmpfs3.9G0 3.9G >> 0% /dev/shm >> /dev/sda73.9G133M3.8G >> 4% /home >> > > Well, that is not looking good. Was that booted from the rescue cd? > > Sometimes when you boot from a different drive (such as CD) it can switch the > devices around. Maybe they are on SDB? > What does "fdisk -l" show? > From booting using the Rescue disk, and mounting the file systems: fdisk -l shows: Device BootStart End Blocks Id System /dev/sda1 1 8 64228+ de Dell Utility /dev/sda2 9 269 2096482+b W95 FAT32 /dev/sda3 270 17769 140568719+ f W95 Ext’d (LBA) /dev/sda5 270 531 2104483+82 Linux swap / Solaris /dev/sda6 * 532 3142 2097282683 Linux /dev/sda7 314317769 117491346 83 Linux
Re: Boot hangs / loops
> > FilesystemSizeUsedAvail Use% > Mounted on > /dev/sda6 3.9G133M3.8G > 4% / > tmpfs 3.9G0 3.9G > 0% /dev/shm > /dev/sda7 3.9G133M3.8G > 4% /home > Well, that is not looking good. Was that booted from the rescue cd? Sometimes when you boot from a different drive (such as CD) it can switch the devices around. Maybe they are on SDB? What does "fdisk -l" show?
Re: Boot hangs / loops
The external drive that I tried to delete the files from was way bigger than the drive I have in this machine. Could the “undo” information have run me out of disk space? If so, would the problem lie in /tmp? Can I safely delete everything in /tmp? If so, is that worth trying?
Re: Boot hangs / loops
On Jul 10, 2014, at 3:49 PM, John Lauro wrote: > These are the type of things that can be difficult to do over email... > > Try mounting the /dev/sda6 after fsck in rescue mode and make sure the > filesystem has at least 10% free space. > Is it ext2, 3, or 4, or other? > > What other partitions are on /sda? I assume /boot is one, any others? > Thank you for responding! From the sticky note on the side of the machine. I always record the disk layout there whenever I install a system. /dev/sda1 62.7MB Dell Utility 0-7 /dev/sda2 1.9 GB FAT 32 /Windows8-268 (not mounted at startup) /dev/sda3 Extended /dev/sda5 2.0 GB Linux Swap 269-530 /dev/sda620.0 GB / 531-3141 /dev/sda7 112.0 GB /home 3142-17768 "df -h” Gives me strange results: Filesystem SizeUsedAvail Use% Mounted on /dev/sda6 3.9G133M3.8G 4% / tmpfs 3.9G0 3.9G 0% /dev/shm /dev/sda7 3.9G133M3.8G 4% /home
Re: Boot hangs / loops
These are the type of things that can be difficult to do over email... Try mounting the /dev/sda6 after fsck in rescue mode and make sure the filesystem has at least 10% free space. Is it ext2, 3, or 4, or other? What other partitions are on /sda? I assume /boot is one, any others? - Original Message - > From: "Dormition Skete (Hotmail)" > To: SCIENTIFIC-LINUX-USERS@FNAL.GOV > Sent: Thursday, July 10, 2014 4:34:00 PM > Subject: Boot hangs / loops > > I needed some more storage space on our SL6.5 server, so I hooked up > a USB external drive to the machine. The external drive had a > Macintosh file system on it, so I installed kmod-hfsplus from the > elrepo.org/elrepo-release-6-5-el6.elrepo.noarch.org repository. I > mounted the drive, and everything worked fine. I could read and > write files to it just fine. I set up a file share under Samba, and > that worked fine, too. > > Then I made the stupid mistake of trying to delete a bunch of files > off of it using nautilus from a thin client, rather than from the > command line. > > In the middle of the deletion process, it took the entire server > down. Now it won’t reboot. > > Whenever I try to reboot it, I get the following message: > > — > > Checking file systems. > /dev/sda6 is in use. > e2fsck: Cannot continue, aborting. > > *** An error occurred during the file system check. > *** Dropping you into a shell; The system will reboot > *** when you leave the shell. > > — > > I booted it from a Rescue CD, and did not mount the volumes. I ran > fsck on the two Linux ext4 file systems with: > > fsck /dev/sda6 (my / file system) > fsck /dev/sda7 (my /home file system) > > > That did not help. Something gave me the thought to try changing the > labels in the /etc/fstab file. I changed the “UUID=…..” with the > device names /dev/sda5 (swap), 6 and 7. > > > That didn’t help. > > I tried booting it with “fastboot” in the kernel line, and that > places me in a perpetual loop. I get a message saying: > > — > > Warning — SELinux targeted policy relabel is required. > > Relabeling could take a very long time, depending on > file system size and speed of hard drives. > > — > > I’ve also tried putting “fastboot enforcing=0 autorelabel=0” in the > kernel line, and that does not seem to do anything. > > > Without “fastboot”, I get the file system check kicking me into a > maintenance prompt. > > With “fastboot”, I get the perpetual SELinux relabeling. > > > I also find it really odd that when I changed the fstab entries, I > first made a backup copy of the fstab file. I also copied the > existing lines I was going to change, commented them out, and > changed the second set of lines. Neither the backup fstab file, nor > the commented lines are anywhere to be found. > > If somebody would please help me get this machine back up, I would > *greatly* appreciate it! > > Peter, hieromonk >
Re: Boot hangs / loops
In looking at my previous post, it occurred to me that “fsck didn’t help” was not very explanatory. fsck finds no errors on /dev/sda6 (my / file system) fsck found and fixed 2 errors in my /dev/sda7 (home) file system. I’ve run this on both several times today, and it finds them both clean every time now. It still will not boot.
Boot hangs / loops
I needed some more storage space on our SL6.5 server, so I hooked up a USB external drive to the machine. The external drive had a Macintosh file system on it, so I installed kmod-hfsplus from the elrepo.org/elrepo-release-6-5-el6.elrepo.noarch.org repository. I mounted the drive, and everything worked fine. I could read and write files to it just fine. I set up a file share under Samba, and that worked fine, too. Then I made the stupid mistake of trying to delete a bunch of files off of it using nautilus from a thin client, rather than from the command line. In the middle of the deletion process, it took the entire server down. Now it won’t reboot. Whenever I try to reboot it, I get the following message: — Checking file systems. /dev/sda6 is in use. e2fsck: Cannot continue, aborting. *** An error occurred during the file system check. *** Dropping you into a shell; The system will reboot *** when you leave the shell. — I booted it from a Rescue CD, and did not mount the volumes. I ran fsck on the two Linux ext4 file systems with: fsck /dev/sda6 (my / file system) fsck /dev/sda7 (my /home file system) That did not help. Something gave me the thought to try changing the labels in the /etc/fstab file. I changed the “UUID=…..” with the device names /dev/sda5 (swap), 6 and 7. That didn’t help. I tried booting it with “fastboot” in the kernel line, and that places me in a perpetual loop. I get a message saying: — Warning — SELinux targeted policy relabel is required. Relabeling could take a very long time, depending on file system size and speed of hard drives. — I’ve also tried putting “fastboot enforcing=0 autorelabel=0” in the kernel line, and that does not seem to do anything. Without “fastboot”, I get the file system check kicking me into a maintenance prompt. With “fastboot”, I get the perpetual SELinux relabeling. I also find it really odd that when I changed the fstab entries, I first made a backup copy of the fstab file. I also copied the existing lines I was going to change, commented them out, and changed the second set of lines. Neither the backup fstab file, nor the commented lines are anywhere to be found. If somebody would please help me get this machine back up, I would *greatly* appreciate it! Peter, hieromonk
