Re: Startup problem

From: Robert Locke (rlocke_at_ralii.com)
Date: 07/06/04

  • Next message: Scott Sloan: "Re: Linux Games (was: The fight to give up MS)"
    To: For users of Fedora Core releases <fedora-list@redhat.com>
    Date: Tue, 06 Jul 2004 13:27:37 -0400
    
    

    On Tue, 2004-07-06 at 02:17, Gene Heskett wrote:
    > There are instructions at the bottom of the grub screen, pick the
    > kernel you want to boot, hit the magic 'edit' key combo, then add the
    > word single to the end of the displayed line, and remove the 'ro' in
    > the middle of it and hit the enter key. This will put you in single
    > user mode and let you try to fix it.

    Gene,

    Actually the removal of the ro is probably redundant....

    When the kernel boots, it mounts the root filesystem (normally
    read-only) based on the existence of the ro. This is so later, we can
    still do an fsck on the filesystem (cannot do it on a filesystem that is
    mounted rw, but can on one mounted ro).

    Now, the word "single", "s" or "S" as a kernel parameter gets passed to
    init that boots us into single user mode. Single user mode will run
    /etc/rc.d/rc.sysinit, which will then "remount" the root filesystem
    read-write after checking it and should mount the rest of your
    filesystems after checking them also. Of course, if fsck fails, we end
    up getting dumped into an sulogin shell to try to repair the filesystem.

    Personally, I use an "a", "space", "s", "Enter" to boot myself into
    single user mode.

    --Rob

    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    

  • Next message: Scott Sloan: "Re: Linux Games (was: The fight to give up MS)"

    Relevant Pages

    • Strange "filesystem busy" problem
      ... I am running several NFS and SMB server using SuSE Linux 8.2 with a SuSE ... patched kernel k_smp4G-2.4.21-202. ... The same busy-problem happens when I change to single user mode and then try ... filesystem to see whats making it busy, but both tools do not report ...
      (Linux-Kernel)
    • Re: fsck: broken file system with background check remains broken after bootup
      ... > to boot and then fsck your disk partitions. ... If the system ends with a bad filesystem, the background check may leave the ... (single user mode, rescue floppies, live CDs bootup etc.). ... single user mode), but the background check left the system broken..... ...
      (freebsd-stable)
    • Re: 5.4-RC2 freezing - ATA related?
      ... > After manually resetting the system it boots and says 'Automatic file system ... and drops into single user mode. ... > different machines, all configured similarly. ... The symptoms are exactly the same -- the hang is normally triggered ...
      (freebsd-stable)
    • Re: 5.4-RC2 freezing - ATA related?
      ... I've taken the disks off of the onboard ICH5 controller and ... > 'password:' prompt. ... > After manually resetting the system it boots and says 'Automatic file system ... and drops into single user mode. ...
      (freebsd-stable)
    • Re: Startup problem
      ... it mounts the root filesystem (normally ... > still do an fsck on the filesystem (cannot do it on a filesystem that is ... > init that boots us into single user mode. ... Of course, if fsck fails, we end ...
      (Fedora)