Re: What causes single user boot? (last stereogram)
On Tue, 6 Oct 1998, Kent West wrote: At 09:10 PM 10/6/1998 +1300, Michael Beattie wrote: On Mon, 5 Oct 1998, Raymond A. Ingles wrote: [stereogram .sig] Now that, folks, has class.. Cool Ray :) I kept focusing on the row with Os in it and never could see anything. Finally I gave up on that and just looked at the body like I would any other stereogram. Weigh Kule! Stereograms really aren't that complicated. I made a web page about them at work. I'll copy it and put it up on my web site at home before the end of the week. It'll be at http://www.tir.com/~sorceror/;. Sincerely, Ray Ingles (248) 377-7735 [EMAIL PROTECTED] g g g g g g g g g g g g g g g g g g g g g g g g g r r r r r r r r r r r r r r r r r r r eeeeeeeeeeeeeee a a a a a a a a a a a a a t t t t t t t t t t t d d d d d d d d d d d e e e e e e e e e e e e e ppppppppppppppp t t t t t t t t t t t t t t t t t t t h h h h h h h h h h h h h h h h h h h h h h h h h
Re: What causes single user boot?
On Fri, 2 Oct 1998, Christopher D. Judd wrote: Make sure the sixth field in your /etc/fstab is set to 0(zero) or empty for removable media. From 'man 5 fstab' [...] Sure enough, that fixed it. Odd that this problem only showed up when I upgraded to Hamm, though. Thanks for the tip. Same here. I have an external removeable-media drive that, in the fstab, is nominally ext2. If I boot with an msdos-formatted cartridge, however, I get the 'Ctrl-D' prompt. This didn't happen until I upgraded to Hamm. Now that I know the fix I'll be sure to update my fstab. Sincerely, Ray Ingles (248)377-7735 [EMAIL PROTECTED] Free Stereogram! Try to make the two Os in the next row look like three: OO n n n n n n n n n n n n n n n n n ffffffffffffff e e e e e e e e e e e e e e e e e aaaaaaaaaaaaaa a a a a a a a a a a a a a a a a a rrrrrrrrrrrrrr r r r r r r r r r r r r r r r r r
Re: What causes single user boot?
On Mon, 5 Oct 1998, Raymond A. Ingles wrote: Sincerely, Ray Ingles (248)377-7735 [EMAIL PROTECTED] Free Stereogram! Try to make the two Os in the next row look like three: OO n n n n n n n n n n n n n n n n n ffffffffffffff e e e e e e e e e e e e e e e e e aaaaaaaaaaaaaa a a a a a a a a a a a a a a a a a rrrrrrrrrrrrrr r r r r r r r r r r r r r r r r r Now that, folks, has class.. Cool Ray :) Michael Beattie ([EMAIL PROTECTED]) PGP Key available, reply with pgpkey as subject. - A feature is a bug with seniority. - Debian GNU/Linux Ooohh You are missing out!
Re: What causes single user boot?
At 09:10 PM 10/6/1998 +1300, Michael Beattie wrote: On Mon, 5 Oct 1998, Raymond A. Ingles wrote: Sincerely, Ray Ingles (248)377-7735 [EMAIL PROTECTED] Free Stereogram! Try to make the two Os in the next row look like three: OO n n n n n n n n n n n n n n n n n ffffffffffffff e e e e e e e e e e e e e e e e e aaaaaaaaaaaaaa a a a a a a a a a a a a a a a a a rrrrrrrrrrrrrr r r r r r r r r r r r r r r r r r Now that, folks, has class.. Cool Ray :) I kept focusing on the row with Os in it and never could see anything. Finally I gave up on that and just looked at the body like I would any other stereogram. Weigh Kule! Kent West, Technology Support [EMAIL PROTECTED] Abilene Christian Univ., Abilene, TX 915-674-2557 FAX: 915.674.6724 Amateur Radio: KC5ENO Debian Linux: Ride the wave with the penguins!
Re: What causes single user boot?
*- Christopher D. Judd wrote about Re: What causes single user boot? | |This happens on my system since upgrading to Hamm. The problem seems | to be that fsck -A tries to check /fd0 (since I have entries for /fd0 in | fsab) and fails since no disk is in the drive. If that is the case then | the FSCKFIX=yes won't help. I have't had time to address this issue yet. | Changing the /etc/fstab entries or the startup script may be necessary. | | -Chris | Make sure the sixth field in your /etc/fstab is set to 0(zero) or empty for removable media. From 'man 5 fstab' The sixth field, (fs_passno), is used by the fsck(8) pro gram to determine the order in which filesystem checks are done at reboot time. The root filesystem should be speci fied with a fs_passno of 1, and other filesystems should have a fs_passno of 2. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. If the sixth field is not pre sent or zero, a value of zero is returned and fsck will assume that the filesystem does not need to be checked. Sure enough, that fixed it. Odd that this problem only showed up when I upgraded to Hamm, though. Thanks for the tip. -Chris -- || | Dr. Christopher D. Judd | | NYS Dept. of Health [EMAIL PROTECTED] | | Wadsworth Center - ESP | | P.O. Box 509 518 486-7829 | | Albany, NY 12201-0509| ||
Re: What causes single user boot?
According to Miquel van Smoorenburg [EMAIL PROTECTED]: 2. A filesystem check failed because there were serious errors and the system wants you to run fsck manually It is not 1 and 3 so it must be 2. That sounds reasonable, because the operator (who had no idea what he was doing) read something about file system errors to us. If it was (2), you can prevent that by setting FSCKFIX=yes in /etc/default/rcS. It will forcibly check all file systems and repair them even if there are serious errors. This might result in dataloss, but usually there isn't anything else you can do even if you do run the fsck manually. Great! Thanks so much for that!!! Andy. -- Andy Spiegl, University of Technology, Muenchen, Germany E-Mail: [EMAIL PROTECTED] URL: http://www.spiegl.de Finger [EMAIL PROTECTED] for my PGP key o _ _ _ - __o __o /\_ _ \\o (_)\__/o (_) --- _`\,__`\,__(_) (_)/_\_| \ _|/' \/ -- (_)/ (_) (_)/ (_) (_)(_) (_)(_)' _\o_ ~~~
What causes single user boot?
Hi! I've got a webserver which is running constantly. A few days ago we had to reboot it, because of a SCSI problem with the JAZ drive. (side note: can you imagine the load went up to 115 still growing!?) Well, after the reboot the system stopped at the prompt: Press Ctrl-D or give root password. I wonder what could have caused this? This is a huge problem, because the computer is many kilometers away and administered only over the net. It was tedious to find someone up there to resolve this. That's why I would really like to find out what caused this and how I can avoid it in the future. BTW: running Hamm incl.all updates Thanks a lot in advance for any hint or pointer! Andy. -- Andy Spiegl, University of Technology, Muenchen, Germany E-Mail: [EMAIL PROTECTED] URL: http://www.spiegl.de Finger [EMAIL PROTECTED] for my PGP key o _ _ _ - __o __o /\_ _ \\o (_)\__/o (_) --- _`\,__`\,__(_) (_)/_\_| \ _|/' \/ -- (_)/ (_) (_)/ (_) (_)(_) (_)(_)' _\o_ ~~~
Re: What causes single user boot?
[EMAIL PROTECTED] (Andy Spiegl) writes: Hi! I've got a webserver which is running constantly. A few days ago we had to reboot it, because of a SCSI problem with the JAZ drive. (side note: can you imagine the load went up to 115 still growing!?) Well, after the reboot the system stopped at the prompt: Press Ctrl-D or give root password. I wonder what could have caused this? This is a huge problem, because the computer is many kilometers away and administered only over the net. It was tedious to find someone up there to resolve this. That's why I would really like to find out what caused this and how I can avoid it in the future. BTW: running Hamm incl.all updates from slink? Try downgrading modutils (far guess: it was broken a week ago). You can't really tell what caused this, without seeing the messages from bootstrap. HTH, Jens -- [EMAIL PROTECTED] [EMAIL PROTECTED] KeyID: 2048/E451C639 1998/01/28 Print: 5F 3D 43 1E 24 1E CC 48 1E 05 93 3A A7 10 73 37 This is the difference: Unix is an OS with tradition, the other are illogical from scratch. -- free translation from Anselm Lignau's comment in de.comp.os.unix.discussion
Re: What causes single user boot?
In article [EMAIL PROTECTED], Andy Spiegl [EMAIL PROTECTED] wrote: Hi! I've got a webserver which is running constantly. A few days ago we had to reboot it, because of a SCSI problem with the JAZ drive. (side note: can you imagine the load went up to 115 still growing!?) Well, after the reboot the system stopped at the prompt: Press Ctrl-D or give root password. Can be 3 things: 1. You turned on sulogin on boot in /etc/default/rcS 2. A filesystem check failed because there were serious errors and the system wants you to run fsck manually 3. A filesystem check failed because the driver for a disk (say a SCSI driver module) wasn't loaded. If it was (2), you can prevent that by setting FSCKFIX=yes in /etc/default/rcS. It will forcibly check all file systems and repair them even if there are serious errors. This might result in dataloss, but usually there isn't anything else you can do even if you do run the fsck manually. The cause was undoubtedly on the screen, you should have asked the operator to scroll back with SHIFT+pageup and write down all messages Mike. -- Did I ever tell you about the illusion of free will? -- Sheriff Lucas Buck, ultimate BOFH.
Re: What causes single user boot?
In article [EMAIL PROTECTED], Andy Spiegl [EMAIL PROTECTED] wrote: Hi! I've got a webserver which is running constantly. A few days ago we had to reboot it, because of a SCSI problem with the JAZ drive. (side note: can you imagine the load went up to 115 still growing!?) Well, after the reboot the system stopped at the prompt: Press Ctrl-D or give root password. Can be 3 things: 1. You turned on sulogin on boot in /etc/default/rcS 2. A filesystem check failed because there were serious errors and the system wants you to run fsck manually 3. A filesystem check failed because the driver for a disk (say a SCSI driver module) wasn't loaded. If it was (2), you can prevent that by setting FSCKFIX=yes in /etc/default/rcS. It will forcibly check all file systems and repair them even if there are serious errors. This might result in dataloss, but usually there isn't anything else you can do even if you do run the fsck manually. This happens on my system since upgrading to Hamm. The problem seems to be that fsck -A tries to check /fd0 (since I have entries for /fd0 in fsab) and fails since no disk is in the drive. If that is the case then the FSCKFIX=yes won't help. I have't had time to address this issue yet. Changing the /etc/fstab entries or the startup script may be necessary. -Chris -- || | Dr. Christopher D. Judd | | NYS Dept. of Health [EMAIL PROTECTED] | | Wadsworth Center - ESP | | P.O. Box 509 518 486-7829 | | Albany, NY 12201-0509| ||
Re: What causes single user boot?
*- Christopher D. Judd wrote about Re: What causes single user boot? | |This happens on my system since upgrading to Hamm. The problem seems | to be that fsck -A tries to check /fd0 (since I have entries for /fd0 in | fsab) and fails since no disk is in the drive. If that is the case then | the FSCKFIX=yes won't help. I have't had time to address this issue yet. | Changing the /etc/fstab entries or the startup script may be necessary. | | -Chris | Make sure the sixth field in your /etc/fstab is set to 0(zero) or empty for removable media. From 'man 5 fstab' The sixth field, (fs_passno), is used by the fsck(8) pro gram to determine the order in which filesystem checks are done at reboot time. The root filesystem should be speci fied with a fs_passno of 1, and other filesystems should have a fs_passno of 2. Filesystems within a drive will be checked sequentially, but filesystems on different drives will be checked at the same time to utilize parallelism available in the hardware. If the sixth field is not pre sent or zero, a value of zero is returned and fsck will assume that the filesystem does not need to be checked. -- Brian - Never criticize anybody until you have walked a mile in their shoes, because by that time you will be a mile away and have their shoes. - unknown Mechanical Engineering [EMAIL PROTECTED] Purdue University http://www.ecn.purdue.edu/~servis -
