From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id E81D61381F3 for ; Thu, 8 Aug 2013 23:07:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 0FF9BE0A5A; Thu, 8 Aug 2013 23:07:15 +0000 (UTC) Received: from mail-vc0-f175.google.com (mail-vc0-f175.google.com [209.85.220.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 512E7E07F5 for ; Thu, 8 Aug 2013 23:07:14 +0000 (UTC) Received: by mail-vc0-f175.google.com with SMTP id ia10so303879vcb.34 for ; Thu, 08 Aug 2013 16:07:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ra27BmDRDkaHgWqXaHYMyE6zO2MB7KlxgIWqBHTZP+k=; b=XeuxZtm6K3u8ac8DcTnKGrzkZ+DJatQ63LAAc+9qHVpWie4rRsYMR9rAOk4QMU7d9j ZB7QI8K6hzB4jdNm5rrkVUJCkPg+LLNoZrRRUvjfNMcMdt5YBiMjrnLGyfRPiblkqPza Np/JkQjwH5Cy7tywHFYSWylJq8JRlTV0Az5wnqqE9mO0UL6sCgg/dd+lQpY+6dhN6Xqy 48p4juA+mprPmLUNWMrPuLiqkD+AHKd42Ncl92MpDOaGRieocwLP7FurOf8T2NaHljm5 ashir4jEF41TyGnwbxPuaIp74TjkCwRM/syzOvirN815dhMBz3gGahGX9m26PkarS/uC CdbA== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@lists.gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.58.86.7 with SMTP id l7mr4477425vez.65.1376003233498; Thu, 08 Aug 2013 16:07:13 -0700 (PDT) Received: by 10.58.84.230 with HTTP; Thu, 8 Aug 2013 16:07:13 -0700 (PDT) In-Reply-To: <5204023D.5020705@googlemail.com> References: <5204023D.5020705@googlemail.com> Date: Fri, 9 Aug 2013 09:07:13 +1000 Message-ID: Subject: Re: [gentoo-amd64] early boot failure, not sure how to diagnose From: Daiajo Tibdixious To: gentoo-amd64 Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 3a0e8a53-d1db-4a03-8584-63cba413e258 X-Archives-Hash: 2a4063a6c5b54b5940be6699c3cc5f49 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 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? >