* [gentoo-amd64] early boot failure, not sure how to diagnose
@ 2013-08-08 8:43 Daiajo Tibdixious
2013-08-08 20:40 ` Volker Armin Hemmann
0 siblings, 1 reply; 6+ messages in thread
From: Daiajo Tibdixious @ 2013-08-08 8:43 UTC (permalink / raw
To: gentoo-amd64
[-- Attachment #1: Type: text/plain, Size: 1046 bytes --]
I got new hardware for a home desktop a few days ago.
Downloaded install-amd64-minimal-20130801.iso and am still booting
from that cd as hard drive boot fails.
I turned on logging in /etc/rc.conf, but no /var/log/rc.log is produced.
The disks are mounted but readonly. I guess from this the problem is
occurring before the root partition is mounted.
I only have 4 partitions: boot, swap, root, and home. Since everything
important is on the root partition, I'm not using an initramfs.
I have many times tried to catch the error by watching the screen, but it
scrolls past way to fast.
The last part of the boot messages before things go crazy is
"Switching to clocksource TSC".
I've been reading up on grub, but don't see anyway to get more info on what
is going wrong.
If I boot from the cd and chroot to the disk, everything seems to work
fine. /boot is ext2 fs and this is my grug.conf:
default 0
timeout 20
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
title Gentoo Linux 3.8.13
root (hd0,0)
kernel /boot/3.8/13-0/bzImage root=/dev/sda3
[-- Attachment #2: Type: text/html, Size: 1373 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-amd64] early boot failure, not sure how to diagnose
2013-08-08 8:43 [gentoo-amd64] early boot failure, not sure how to diagnose Daiajo Tibdixious
@ 2013-08-08 20:40 ` Volker Armin Hemmann
2013-08-08 23:07 ` Daiajo Tibdixious
0 siblings, 1 reply; 6+ messages in thread
From: Volker Armin Hemmann @ 2013-08-08 20:40 UTC (permalink / raw
To: gentoo-amd64
Am 08.08.2013 10:43, schrieb Daiajo Tibdixious:
> I got new hardware for a home desktop a few days ago.
> Downloaded install-amd64-minimal-20130801.iso and am still booting
> from that cd as hard drive boot fails.
>
> I turned on logging in /etc/rc.conf, but no /var/log/rc.log is produced.
> The disks are mounted but readonly. I guess from this the problem is
> occurring before the root partition is mounted.
>
> I only have 4 partitions: boot, swap, root, and home. Since everything
> important is on the root partition, I'm not using an initramfs.
>
> I have many times tried to catch the error by watching the screen, but
> it scrolls past way to fast.
>
> The last part of the boot messages before things go crazy is
> "Switching to clocksource TSC".
>
> I've been reading up on grub, but don't see anyway to get more info on
> what is going wrong.
>
> If I boot from the cd and chroot to the disk, everything seems to work
> fine. /boot is ext2 fs and this is my grug.conf:
> default 0
> timeout 20
> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
>
> title Gentoo Linux 3.8.13
> root (hd0,0)
> kernel /boot/3.8/13-0/bzImage root=/dev/sda3
>
and what is happening?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-amd64] early boot failure, not sure how to diagnose
2013-08-08 20:40 ` Volker Armin Hemmann
@ 2013-08-08 23:07 ` Daiajo Tibdixious
2013-08-08 23:24 ` Drake Donahue
` (2 more replies)
0 siblings, 3 replies; 6+ messages in thread
From: Daiajo Tibdixious @ 2013-08-08 23:07 UTC (permalink / raw
To: gentoo-amd64
Logged in after failed boot.
/home & /boot are mounted, but nothing in them when I ls.
ls of / shows all the normal things there.
While logged in, I'm still getting boot messages, where USB devices,
eg the mouse, disconnect and reconnect.
There are a ridiculous number of sd devices in /dev. sda, sdb, sdc,
sdd all go to 15. sda is the hard drive, sdb/sdc for USB devices.
Never had sdd.
Did see some errors, notably "cannot mount /run" bad superblock or
something like that. Its hard to scroll back with USB messages
constantly appearing, half a screenful each time.
On Fri, Aug 9, 2013 at 6:40 AM, Volker Armin Hemmann
<volkerarmin@googlemail.com> wrote:
> Am 08.08.2013 10:43, schrieb Daiajo Tibdixious:
>> I got new hardware for a home desktop a few days ago.
>> Downloaded install-amd64-minimal-20130801.iso and am still booting
>> from that cd as hard drive boot fails.
>>
>> I turned on logging in /etc/rc.conf, but no /var/log/rc.log is produced.
>> The disks are mounted but readonly. I guess from this the problem is
>> occurring before the root partition is mounted.
>>
>> I only have 4 partitions: boot, swap, root, and home. Since everything
>> important is on the root partition, I'm not using an initramfs.
>>
>> I have many times tried to catch the error by watching the screen, but
>> it scrolls past way to fast.
>>
>> The last part of the boot messages before things go crazy is
>> "Switching to clocksource TSC".
>>
>> I've been reading up on grub, but don't see anyway to get more info on
>> what is going wrong.
>>
>> If I boot from the cd and chroot to the disk, everything seems to work
>> fine. /boot is ext2 fs and this is my grug.conf:
>> default 0
>> timeout 20
>> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
>>
>> title Gentoo Linux 3.8.13
>> root (hd0,0)
>> kernel /boot/3.8/13-0/bzImage root=/dev/sda3
>>
>
>
> and what is happening?
>
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-amd64] early boot failure, not sure how to diagnose
2013-08-08 23:07 ` Daiajo Tibdixious
@ 2013-08-08 23:24 ` Drake Donahue
2013-08-09 0:32 ` Drake Donahue
[not found] ` <520438eb.6698320a.28a0.27aaSMTPIN_ADDED_BROKEN@mx.google.com>
2 siblings, 0 replies; 6+ messages in thread
From: Drake Donahue @ 2013-08-08 23:24 UTC (permalink / raw
To: gentoo-amd64
On Fri, 2013-08-09 at 09:07 +1000, Daiajo Tibdixious wrote:
> Logged in after failed boot.
> /home & /boot are mounted, but nothing in them when I ls.
> ls of / shows all the normal things there.
>
> While logged in, I'm still getting boot messages, where USB devices,
> eg the mouse, disconnect and reconnect.
>
> There are a ridiculous number of sd devices in /dev. sda, sdb, sdc,
> sdd all go to 15. sda is the hard drive, sdb/sdc for USB devices.
> Never had sdd.
>
> Did see some errors, notably "cannot mount /run" bad superblock or
> something like that. Its hard to scroll back with USB messages
> constantly appearing, half a screenful each time.
>
> On Fri, Aug 9, 2013 at 6:40 AM, Volker Armin Hemmann
> <volkerarmin@googlemail.com> wrote:
> > Am 08.08.2013 10:43, schrieb Daiajo Tibdixious:
> >> I got new hardware for a home desktop a few days ago.
> >> Downloaded install-amd64-minimal-20130801.iso and am still booting
> >> from that cd as hard drive boot fails.
> >>
> >> I turned on logging in /etc/rc.conf, but no /var/log/rc.log is produced.
> >> The disks are mounted but readonly. I guess from this the problem is
> >> occurring before the root partition is mounted.
> >>
> >> I only have 4 partitions: boot, swap, root, and home. Since everything
> >> important is on the root partition, I'm not using an initramfs.
> >>
> >> I have many times tried to catch the error by watching the screen, but
> >> it scrolls past way to fast.
> >>
> >> The last part of the boot messages before things go crazy is
> >> "Switching to clocksource TSC".
> >>
> >> I've been reading up on grub, but don't see anyway to get more info on
> >> what is going wrong.
> >>
> >> If I boot from the cd and chroot to the disk, everything seems to work
> >> fine. /boot is ext2 fs and this is my grug.conf:
> >> default 0
> >> timeout 20
> >> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> >>
> >> title Gentoo Linux 3.8.13
> >> root (hd0,0)
> >> kernel /boot/3.8/13-0/bzImage root=/dev/sda3
> >>
> >
> >
> > and what is happening?
> >
>
does your kernel config have:
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_HOTPLUG=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_NET=y
CONFIG_PROC_FS=y
CONFIG_SIGNALFD=y
CONFIG_SYSFS=y
CONFIG_SYSFS_DEPRECATED is not set
CONFIG_UEVENT_HELPER_PATH=""
CONFIG_BLK_DEV_BSG=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-amd64] early boot failure, not sure how to diagnose
2013-08-08 23:07 ` Daiajo Tibdixious
2013-08-08 23:24 ` Drake Donahue
@ 2013-08-09 0:32 ` Drake Donahue
[not found] ` <520438eb.6698320a.28a0.27aaSMTPIN_ADDED_BROKEN@mx.google.com>
2 siblings, 0 replies; 6+ messages in thread
From: Drake Donahue @ 2013-08-09 0:32 UTC (permalink / raw
To: gentoo-amd64
On Fri, 2013-08-09 at 09:07 +1000, Daiajo Tibdixious wrote:
> Logged in after failed boot.
> /home & /boot are mounted, but nothing in them when I ls.
> ls of / shows all the normal things there.
>
> While logged in, I'm still getting boot messages, where USB devices,
> eg the mouse, disconnect and reconnect.
>
> There are a ridiculous number of sd devices in /dev. sda, sdb, sdc,
> sdd all go to 15. sda is the hard drive, sdb/sdc for USB devices.
> Never had sdd.
>
> Did see some errors, notably "cannot mount /run" bad superblock or
> something like that. Its hard to scroll back with USB messages
> constantly appearing, half a screenful each time.
>
> On Fri, Aug 9, 2013 at 6:40 AM, Volker Armin Hemmann
> <volkerarmin@googlemail.com> wrote:
> > Am 08.08.2013 10:43, schrieb Daiajo Tibdixious:
> >> I got new hardware for a home desktop a few days ago.
> >> Downloaded install-amd64-minimal-20130801.iso and am still booting
> >> from that cd as hard drive boot fails.
> >>
> >> I turned on logging in /etc/rc.conf, but no /var/log/rc.log is produced.
> >> The disks are mounted but readonly. I guess from this the problem is
> >> occurring before the root partition is mounted.
> >>
> >> I only have 4 partitions: boot, swap, root, and home. Since everything
> >> important is on the root partition, I'm not using an initramfs.
> >>
> >> I have many times tried to catch the error by watching the screen, but
> >> it scrolls past way to fast.
> >>
> >> The last part of the boot messages before things go crazy is
> >> "Switching to clocksource TSC".
> >>
> >> I've been reading up on grub, but don't see anyway to get more info on
> >> what is going wrong.
> >>
> >> If I boot from the cd and chroot to the disk, everything seems to work
> >> fine. /boot is ext2 fs and this is my grug.conf:
> >> default 0
> >> timeout 20
> >> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
> >>
> >> title Gentoo Linux 3.8.13
> >> root (hd0,0)
> >> kernel /boot/3.8/13-0/bzImage root=/dev/sda3
> >>
> >
> >
> > and what is happening?
> >
>
Does kernel config have:
CONFIG_DEVTMPFS=y
CONFIG_DEVTMPFS_MOUNT=y
CONFIG_HOTPLUG=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_NET=y
CONFIG_PROC_FS=y
CONFIG_SIGNALFD=y
CONFIG_SYSFS=y
CONFIG_SYSFS_DEPRECATED is not set
CONFIG_UEVENT_HELPER_PATH=""
CONFIG_BLK_DEV_BSG=y
CONFIG_TMPFS=y
CONFIG_TMPFS_POSIX_ACL=y
CONFIG_TMPFS_XATTR=y
also this problem frequently results from graphics support attempting to
invoke kms support with:
modules instead of builtins
with frame buffers enabled
with the radeon driver enabled without building in appropriate
firmware
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [gentoo-amd64] early boot failure, not sure how to diagnose
[not found] ` <520438eb.6698320a.28a0.27aaSMTPIN_ADDED_BROKEN@mx.google.com>
@ 2013-08-09 4:07 ` Daiajo Tibdixious
0 siblings, 0 replies; 6+ messages in thread
From: Daiajo Tibdixious @ 2013-08-09 4:07 UTC (permalink / raw
To: gentoo-amd64
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
Had DEVTMPFS not the TMPFS ones.
All others match.
I don't think I've ever been into "Pseudo filesystems" before.
Well much better after adding TMPFS. /home was not mounted,
otherwise looks fine.
I've had this problem before, but never with the USB message
confusion. I believe that is because this system has USB keyboard &
mouse, while my last one had normal ones. In retrospect I should have
eliminated all of the USB confusion by using the other keyboard &
mouse.
I think I can fix the remaining problems, thanks for your help.
On Fri, Aug 9, 2013 at 10:32 AM, Drake Donahue <donahue95@comcast.net> wrote:
> On Fri, 2013-08-09 at 09:07 +1000, Daiajo Tibdixious wrote:
>> Logged in after failed boot.
>> /home & /boot are mounted, but nothing in them when I ls.
>> ls of / shows all the normal things there.
>>
>> While logged in, I'm still getting boot messages, where USB devices,
>> eg the mouse, disconnect and reconnect.
>>
>> There are a ridiculous number of sd devices in /dev. sda, sdb, sdc,
>> sdd all go to 15. sda is the hard drive, sdb/sdc for USB devices.
>> Never had sdd.
>>
>> Did see some errors, notably "cannot mount /run" bad superblock or
>> something like that. Its hard to scroll back with USB messages
>> constantly appearing, half a screenful each time.
>>
>> On Fri, Aug 9, 2013 at 6:40 AM, Volker Armin Hemmann
>> <volkerarmin@googlemail.com> wrote:
>> > Am 08.08.2013 10:43, schrieb Daiajo Tibdixious:
>> >> I got new hardware for a home desktop a few days ago.
>> >> Downloaded install-amd64-minimal-20130801.iso and am still booting
>> >> from that cd as hard drive boot fails.
>> >>
>> >> I turned on logging in /etc/rc.conf, but no /var/log/rc.log is produced.
>> >> The disks are mounted but readonly. I guess from this the problem is
>> >> occurring before the root partition is mounted.
>> >>
>> >> I only have 4 partitions: boot, swap, root, and home. Since everything
>> >> important is on the root partition, I'm not using an initramfs.
>> >>
>> >> I have many times tried to catch the error by watching the screen, but
>> >> it scrolls past way to fast.
>> >>
>> >> The last part of the boot messages before things go crazy is
>> >> "Switching to clocksource TSC".
>> >>
>> >> I've been reading up on grub, but don't see anyway to get more info on
>> >> what is going wrong.
>> >>
>> >> If I boot from the cd and chroot to the disk, everything seems to work
>> >> fine. /boot is ext2 fs and this is my grug.conf:
>> >> default 0
>> >> timeout 20
>> >> splashimage=(hd0,0)/boot/grub/splash.xpm.gz
>> >>
>> >> title Gentoo Linux 3.8.13
>> >> root (hd0,0)
>> >> kernel /boot/3.8/13-0/bzImage root=/dev/sda3
>> >>
>> >
>> >
>> > and what is happening?
>> >
>>
> Does kernel config have:
> CONFIG_DEVTMPFS=y
> CONFIG_DEVTMPFS_MOUNT=y
> CONFIG_HOTPLUG=y
> CONFIG_FSNOTIFY=y
> CONFIG_DNOTIFY=y
> CONFIG_INOTIFY_USER=y
> CONFIG_NET=y
> CONFIG_PROC_FS=y
> CONFIG_SIGNALFD=y
> CONFIG_SYSFS=y
> CONFIG_SYSFS_DEPRECATED is not set
> CONFIG_UEVENT_HELPER_PATH=""
> CONFIG_BLK_DEV_BSG=y
> CONFIG_TMPFS=y
> CONFIG_TMPFS_POSIX_ACL=y
> CONFIG_TMPFS_XATTR=y
>
> also this problem frequently results from graphics support attempting to
> invoke kms support with:
> modules instead of builtins
> with frame buffers enabled
> with the radeon driver enabled without building in appropriate
> firmware
>
>
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2013-08-09 4:07 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-08-08 8:43 [gentoo-amd64] early boot failure, not sure how to diagnose Daiajo Tibdixious
2013-08-08 20:40 ` Volker Armin Hemmann
2013-08-08 23:07 ` Daiajo Tibdixious
2013-08-08 23:24 ` Drake Donahue
2013-08-09 0:32 ` Drake Donahue
[not found] ` <520438eb.6698320a.28a0.27aaSMTPIN_ADDED_BROKEN@mx.google.com>
2013-08-09 4:07 ` Daiajo Tibdixious
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox