From: <lngndvs@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Inconsistent mountpoint for /
Date: Sat, 11 Jul 2009 10:16:26 +1000 [thread overview]
Message-ID: <83fxd4nkf9.fsf@gmail.com> (raw)
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
next reply other threads:[~2009-07-11 0:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-11 0:16 lngndvs [this message]
2009-07-11 0:52 ` [gentoo-user] Re: Inconsistent mountpoint for / walt
2009-07-11 1:27 ` Alan E. Davis
2009-07-11 1:55 ` Dale
2009-07-11 9:21 ` Peter Humphrey
2009-07-11 13:26 ` [gentoo-user] " Neil Bothwick
2009-07-11 14:30 ` Alan E. Davis
2009-07-11 15:08 ` Alex Schuster
2009-07-11 16:59 ` Alex Schuster
2009-07-11 19:33 ` [gentoo-user] " walt
2009-07-11 21:59 ` Neil Bothwick
2009-07-12 3:27 ` Alan E. Davis
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=83fxd4nkf9.fsf@gmail.com \
--to=lngndvs@gmail.com \
--cc=gentoo-user@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