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 1MPQGT-0004Ij-EL for garchives@archives.gentoo.org; Sat, 11 Jul 2009 00:16:30 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 9137EE048B; Sat, 11 Jul 2009 00:16:28 +0000 (UTC) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.175]) by pigeon.gentoo.org (Postfix) with ESMTP id 5667FE048B for ; Sat, 11 Jul 2009 00:16:28 +0000 (UTC) Received: by wf-out-1314.google.com with SMTP id 28so376363wfc.10 for ; Fri, 10 Jul 2009 17:16:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:message-id:from:to :subject; bh=O5DORHCOgvqMYEJol2VFuKXYSUXWAAnHcH65PFmvfIc=; b=qmYZjgJWDr7FWaDWWem9MDpohQQaUUi4N2bYJvRsqQlfauT2yulPvPKoae85YDCr0P 8dEI7/zMX2jmed+G8FYOisw7CTMF2Kz9KLSTF8JxgqmQV9LI9A5m//1AIsln5megHDy5 K7Fl0kk1ZlUcESz+8D2WrBebTp7AczV6dbfYs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:message-id:from:to:subject; b=jSPoL7fbNV7JtynmzjLBjzUVIxWn+9GFErlQF3USgpEODnMMKO6R35rV7VydQQwyW4 4WQ+3NEJ9OpBXmv8gzYxbYuQIaxd/Eb4wBsl8ekzoQwXcPTZYB+1ERpxaeTS1tUh3zt3 Ck53G1MJIVSeb8dWXupM1JqjuoTOgfLUQSz/U= Received: by 10.142.12.7 with SMTP id 7mr790701wfl.11.1247271387922; Fri, 10 Jul 2009 17:16:27 -0700 (PDT) Received: from spineless ([202.88.88.198]) by mx.google.com with ESMTPS id 28sm3274263wfg.5.2009.07.10.17.16.26 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 10 Jul 2009 17:16:27 -0700 (PDT) Date: Sat, 11 Jul 2009 10:16:26 +1000 Message-Id: <83fxd4nkf9.fsf@gmail.com> From: To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Inconsistent mountpoint for / 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 X-Archives-Salt: cf57c24c-b1c9-4bc8-bcb4-1df78fde6be8 X-Archives-Hash: 611061703b12076a2b888f2b5e3b6288 I recently reported that I am suffering random reboots. I have now discovered an inconsistency in the reporting of the mount point of the root directory of my Gentoo install. First a little history: I spent about two and a half weeks trying to install ANYTHING that would remain stable and useable. Finally Gentoo is running well. Repeatedly, I was unable to understand how grub was installing the MBR, or where. I had three SATA drives and one ATA drive, and I removed the ATA drive to get rid of the problem of naming of drives inconsistently. So far so good; however, the SATA drives are booted in order that they are named in the BIOS, so I wasn't certain which drive the MBR was being installed on. Leaving out many details... Just when I was about to give up, I discovered that if I changed the boot order, a different grub appeared. One from Gentoo and one from Ubuntu. After a pitched battle, I was finally able to settle on Gentoo, and it's running pretty well. Except for random reboots. I just noticed that the return from # df is as follows, without any specific drive: designation appearing for / : spineless ulod # df Filesystem 1K-blocks Used Available Use% Mounted on rootfs 105392960 19272948 80766360 20% / /dev/root 105392960 19272948 80766360 20% / rc-svcdir 1024 76 948 8% /lib64/rc/init.d udev 10240 212 10028 3% /dev shm 1027568 0 1027568 0% /dev/shm /dev/sdb6 62144164 45189664 13797732 77% /home After some investigation, I found the following inconsistent indentification of the / directory's physical location: | | / partition | | where represented | 500GB HDD represented as | |----------------------------+--------------------------| | /boot/grub.conf "root" | (hd1,0) | | /boot/grub.con kernel line | root=/dev/sda5 | | /etc/fstab | /devsdb5/ | | /etc/mtab | /dev/root | | sfdisk -l | /dev/sda5 | | /df | /dev/root | | | | In grub, it is located first as hd1 (/dev/sdb) and then as /dev/sda5. That is where I want it to be. This is necessary apparently because grub would see it on /dev/sdb at first, but once the kernel boots, the drive would physically be /dev/sda. The identifation of this partition in /etc/fstab as /dev/sdb5, is apparently not being honored? I'm asking, because I am not well versed in the events in the boot order. df then reports it as /dev/root, ignoring the device id. The partition is seen by sfdisk as /dev/sda5, as it also is by gparted. So, am I safe to rename this partition in /etc/fstab as /dev/sda5? Secondly, would this help explain random reboots? I now plan to simplify the arrangement, and reorganize all of the active partitions on a single drive. That's another story. Thank you, Alan