From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1P71nA-00009H-1L for garchives@archives.gentoo.org; Sat, 16 Oct 2010 08:07:09 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 53D3EE0993 for ; Sat, 16 Oct 2010 08:06:55 +0000 (UTC) Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [76.96.62.17]) by pigeon.gentoo.org (Postfix) with ESMTP id 48CB0E07C6 for ; Sat, 16 Oct 2010 07:06:26 +0000 (UTC) Received: from omta18.westchester.pa.mail.comcast.net ([76.96.62.90]) by qmta10.westchester.pa.mail.comcast.net with comcast id KK6S1f0051wpRvQ5AK6SLe; Sat, 16 Oct 2010 07:06:26 +0000 Received: from dominion.diehlnet.com ([173.10.242.193]) by omta18.westchester.pa.mail.comcast.net with comcast id KK6R1f0074B4BRZ3eK6SmM; Sat, 16 Oct 2010 07:06:26 +0000 Received: from hydraelmo.diehlnet.com ([10.0.1.56] helo=hydra.localnet) by dominion.diehlnet.com with esmtpa (Exim 4.67) (envelope-from ) id 1P70qN-0007p4-G8 for gentoo-user@lists.gentoo.org; Sat, 16 Oct 2010 01:06:24 -0600 From: Mike Diehl To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Problem with new install Date: Sat, 16 Oct 2010 01:06:24 -0600 User-Agent: KMail/1.13.2 (Linux/2.6.32-24-generic; KDE/4.4.2; i686; ; ) References: <201010151129.18927.mdiehl@diehlnet.com> <201010151323.22854.mdiehl@diehlnet.com> <4CB8C163.2070909@f_philipp.fastmail.net> In-Reply-To: <4CB8C163.2070909@f_philipp.fastmail.net> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201010160106.25397.mdiehl@diehlnet.com> X-Spam-Score: -3.8 (---) X-Spam-Report: Spam detection software, running on the system "dominion.diehlnet.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Well, I got it to boot. Now that it's up, I can see what the problem was/is. There are no disk device files in /dev. I created the appropriate nodes and things went much better. The problem was that CONFIG_SYSFS_DEPRECATED_V2 was on [...] Content analysis details: (-3.8 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP 0.6 J_CHICKENPOX_62 BODY: 6alpha-pock-2alpha -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] X-Spam-Level: --- X-ACL-Warn: condition = 1 X-Archives-Salt: 49ecd7cf-210f-4551-99f8-83136e9619dd X-Archives-Hash: 4558d0da8aa66108a451d76b8826c8c6 Well, I got it to boot. Now that it's up, I can see what the problem was/is. There are no disk device files in /dev. I created the appropriate nodes and things went much better. The problem was that CONFIG_SYSFS_DEPRECATED_V2 was on I just closed up the chassis and it will ship in the morning. Thank you for your help! Mike. On Friday 15 October 2010 3:02:27 pm Florian Philipp wrote: > Am 15.10.2010 21:23, schrieb Mike Diehl: > > On Friday 15 October 2010 11:40:34 am Florian Philipp wrote: > >> Am 15.10.2010 19:29, schrieb Mike Diehl: > >>> Hi all. > >>> > >>> I've never had this much trouble with a server before, but I've been > >>> pulling my hair out. > >>> > >>> The install seemed to go well, but when I rebooted it from it's own > >>> hard drive, it fails. fsck claims that it can't open /dev/sda3 or > >>> that the superblock doesn't describe a valid ext2 filesystem. > >> > >> *All* of the drivers could be too much. There is a generic driver which > >> can prevent the "right" driver from taking over. In that case you end up > >> with a /dev/hda node and no DMA. Try to deactivate "Generic ATA support" > >> = CONFIG_ATA_GENERIC and "generic/default IDE chipset support" = > >> CONFIG_IDE_GENERIC. > >> I think it is the second option that causes that problem. However, you > >> won't need the first option, either. > > > > I tried this, first without success. I then ran through all combinations > > of sda3, sdb3, hda3, hdb3 in /etc/fstab. This didn't work. > > > >> Instead of your brute-force "yes to all" approach, newer kernels also > >> support `make localyesconfig` which takes all modules currently used in > >> the running kernel and compiles them into the new kernel. It is very > >> helpful when you already have a good but generic kernel like the one on > >> your live CD. > > > > I tried this, next. At least now, I believe I have a viable kernel. But > > it still didn't work. > > > >> If even that doesn't help, it might be possible that the device > >> numbering has changed and your hard disk is detected as /dev/sdb or so. > >> Try mounting it by UUID (google for it, please). > > > > I tried this. Only now, fsck.ext2 tells me that it can't resolve the > > UUID. > > > > Here is the new fstab: > > /dev/sda1 /boot ext2 noauto,noatime 1 2 > > > > UUID=ba7511dd-a5f9-48d8-8102-cf71c08a0c7b / ext2 noatime > > 0 1 > > > > /dev/sda2 none swap sw 0 0 > > /dev/cdrom /mnt/cdrom auto noauto,ro 0 > > 0 > > > > At this point, I'm going to move the drive to a different port on the > > SATA chain; shouldn't change anything, but I'm running out of ideas. > > I'll also check the BIOS for anything stupid-obvious. > > > > So, I guess I'm still stuck! > > Hmm, sounds like a serious problem. I suggest you try to get into an > early stage during boot and try to move forward from there. Try to add > '1' to the parameters in order to get into single-user mode. You can > also try 'init=/bin/bash'. > > There are lots of other options you can try. For a long time, 'noapic' > (not 'noapci') was my first candidate for odd boot issues. Take a look > at /usr/sr/linux/Documentation/kernel-parameters.txt for more options. > > Also, which kernel sources are you using and which live CD (with which > kernel version)? Is there a specific reason why you use ext2 for root? > What kind of system do you run, anyway? And, just by chance, you are not > using an extremely large (>1TB) drive which might happen to have 4kB > blocks instead of 512 B? > > Regards, > Florian Philipp -- Take care and have fun, Mike Diehl.