public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daiajo Tibdixious <daiajo@gmail.com>
To: gentoo-amd64 <gentoo-amd64@lists.gentoo.org>
Subject: Re: [gentoo-amd64] early boot failure, not sure how to diagnose
Date: Fri, 9 Aug 2013 09:07:13 +1000	[thread overview]
Message-ID: <CAC4mkfsEoXKjki4z4N41ZjEw-xAjYxYRSV9YvAjw1NQb4AUPCA@mail.gmail.com> (raw)
In-Reply-To: <5204023D.5020705@googlemail.com>

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?
>


  reply	other threads:[~2013-08-08 23:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAC4mkfsEoXKjki4z4N41ZjEw-xAjYxYRSV9YvAjw1NQb4AUPCA@mail.gmail.com \
    --to=daiajo@gmail.com \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox