Re: Is this grub.conf file correct?
On Sat, Nov 15, 2008 at 9:44 PM, M. Fioretti <[EMAIL PROTECTED]> wrote: > > On Sun, November 16, 2008 2:41 am, Tim wrote: > >> You're missing some things on the kernel line. It should have a >> structure like this: >> >> kernel /vmlinuz ro root= >> >> Where the root parameter points to wherever "/" is located. > > I have added "ro root=/dev/sda3" right after the vmlinuz argument but > nothing changes. > >> I'd expect you to see some sort of error message without having any >> referral to where to find the root partition. > > Booting in single user mode and running dmesg the only more or less > related lines I see are: > > EXT3-fs: INFO: recovery required on readonly filesystem. > EXT3-fs: write access will be enabled during recovery. kjournald starting. > Commit interval 5 seconds. > EXT3-fs: recovery complete. > EXT3-fs: mounted filesystem with ordered data mode. > type=1404 audit (122678963.153:2): enforcing =1 old_enforcing=0 > auid=4294967295 ses=4294967295 > > a few lines below: > > SELINUX: initialized (dev sda3, type ext3), uses xattr > > SELINUX: initialized (dev rootfs, type rootfs), uses genfs_contexts > > ... > > EXT3 FS on sda3, internal journal > kjournald starting. Commit interval 5 seconds > EXT3 FS on sda1, internal journal > EXT3-fs: mouinted filesystem with ordered data mode. > SELinux: initialized (dev sda1, type ext3), uses xattr > > So sda3 (/) and sda1 (/boot) are not managed in the same way, or at least > don't generate the same notifications. But if I type mount at the prompt, > I get: > > /dev/sda3 on / type ext3 (rw) > /dev/sda1 on /boot type ext3 (rw) > > as expected (plus lines for proc, tmpfs, sysfs, devpts) > > what does all this mean& > > tia, > > Marco > > -- > fedora-list mailing list > fedora-list@redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > Hi Marco! I am suspicious that the fact that you CAN boot into single user mode means that the grub is fine. I would guess that X is your problem. The following to try: 1. Let the machine boot as far as it will go. Then try an CTL+ALT+F1 . Hopefully you will then see a login terminal. If not boot in using a live CD and establish a terminal. There examine /var/log/messages - /var/log/Xorg.0.log - and anything else that comes to mind as you look at those two. 2. Run fsck on the disk. If you see a lot of errors consider wiping and reloading the disk. Good Hunting! Tod -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Is this grub.conf file correct?
On Sun, November 16, 2008 2:41 am, Tim wrote: > You're missing some things on the kernel line. It should have a > structure like this: > > kernel /vmlinuz ro root= > > Where the root parameter points to wherever "/" is located. I have added "ro root=/dev/sda3" right after the vmlinuz argument but nothing changes. > I'd expect you to see some sort of error message without having any > referral to where to find the root partition. Booting in single user mode and running dmesg the only more or less related lines I see are: EXT3-fs: INFO: recovery required on readonly filesystem. EXT3-fs: write access will be enabled during recovery. kjournald starting. Commit interval 5 seconds. EXT3-fs: recovery complete. EXT3-fs: mounted filesystem with ordered data mode. type=1404 audit (122678963.153:2): enforcing =1 old_enforcing=0 auid=4294967295 ses=4294967295 a few lines below: SELINUX: initialized (dev sda3, type ext3), uses xattr SELINUX: initialized (dev rootfs, type rootfs), uses genfs_contexts ... EXT3 FS on sda3, internal journal kjournald starting. Commit interval 5 seconds EXT3 FS on sda1, internal journal EXT3-fs: mouinted filesystem with ordered data mode. SELinux: initialized (dev sda1, type ext3), uses xattr So sda3 (/) and sda1 (/boot) are not managed in the same way, or at least don't generate the same notifications. But if I type mount at the prompt, I get: /dev/sda3 on / type ext3 (rw) /dev/sda1 on /boot type ext3 (rw) as expected (plus lines for proc, tmpfs, sysfs, devpts) what does all this mean& tia, Marco -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Is this grub.conf file correct?
On Sat, 2008-11-15 at 22:24 +0100, M. Fioretti wrote: > Now ended up with this grub.conf: > > default=0 > timeout=20 > splashimage=(hd0,0)/grub/splash.img.gz > root (hd0,0) > title Fedora 9 > kernel /vmlinuz-2.6.25-14.fc9.x86_64 rhgb > initrd /initrd-2.6.25-14.fc9.x86_64.img You're missing some things on the kernel line. It should have a structure like this: kernel /vmlinuz ro root= Where the root parameter points to wherever "/" is located. It could be referred to by UUID, labels, or partition details. There can, also, be other parameters, like rhgb or quiet, but they're not needed to boot. e.g. kernel /vmlinuz-2.6.25-14.fc9.x86_64 ro root=LABEL=systemroot or, kernel /vmlinuz-2.6.25-14.fc9.x86_64 ro root=/dev/sda2 or, kernel /vmlinuz-2.6.25-14.fc9.x86_64 ro root=UUID=sdf-dfgd-ewrew-rewq but replacing my label, device ID, or random UUID examples with your actual ones. I'd expect you to see some sort of error message without having any referral to where to find the root partition. -- [EMAIL PROTECTED] ~]$ uname -r 2.6.27.5-37.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Re: Is this grub.conf file correct?
On Sat, November 15, 2008 10:24 pm, M. Fioretti wrote: > Hello, > > this is on the same computer where I cannot log in because I never get a password prompt > (even if I boot into single user mode and reset the root passwd successfully) > > I am wondering if the problem depends on wrong boot options in grub.conf or /etc/fstab. > There is only one SATA hard disk. During the install I left partitions as > they were before, when running FC8: sda1 as /boot, sda2 as swap, sda3 as / more on this: if, in rescue mode, I run fsck /dev/sda1 I get Warning: couldn't open /etc/fstab /boot1: clean (that is, no /boot as I imagined) same for /dev/sda3 (/dev/sda2 is swap): /1: clean (instead of / ) is this wrong, and if yes how to fix it so that /dev/sda1 results as /boot and /dev/sda3 as / ? Also, can this be the reason why I get no password prompt? when I try to login? THanks, Marco > > Now ended up with this grub.conf: > > default=0 > timeout=20 > splashimage=(hd0,0)/grub/splash.img.gz > root (hd0,0) > title Fedora 9 > kernel /vmlinuz-2.6.25-14.fc9.x86_64 rhgb > initrd /initrd-2.6.25-14.fc9.x86_64.img > > and /etc/fstab is: > > > UUID=long_string_here / ext3 defaults 1 1 > UUID=another_long_string_here /boot ext3 defaults 1 2 > tmpfs . > devpts > sysfs > proc > UUID=other_long_string swap defaults 0 0 > > the non-UUID lines are the same (IIRC) as they were in the previous > install > > The question is, are those two files consistant among themselves and the > disk configuration? And could an error there be what makes no password > prompt appear when you login? > > TIA, > Marco > > -- > fedora-list mailing list > fedora-list@redhat.com > To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list > Guidelines: > http://fedoraproject.org/wiki/Communicate/MailingListGuidelines > -- Help *everybody* love Free Standards and Software: http://digifreedom.net -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines
Is this grub.conf file correct?
Hello, this is on the same computer where I cannot log in because I never get a password prompt (even if I boot into single user mode and reset the root passwd successfully) I am wondering if the problem depends on wrong boot options in grub.conf or /etc/fstab. There is only one SATA hard disk. During the install I left partitions as they were before, when running FC8: sda1 as /boot, sda2 as swap, sda3 as / Now ended up with this grub.conf: default=0 timeout=20 splashimage=(hd0,0)/grub/splash.img.gz root (hd0,0) title Fedora 9 kernel /vmlinuz-2.6.25-14.fc9.x86_64 rhgb initrd /initrd-2.6.25-14.fc9.x86_64.img and /etc/fstab is: UUID=long_string_here / ext3 defaults 1 1 UUID=another_long_string_here /boot ext3 defaults 1 2 tmpfs . devpts sysfs proc UUID=other_long_string swap defaults 0 0 the non-UUID lines are the same (IIRC) as they were in the previous install The question is, are those two files consistant among themselves and the disk configuration? And could an error there be what makes no password prompt appear when you login? TIA, Marco -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines