From: Bill Longman <bill.longman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problems booting my server - ext2 - e2fsck
Date: Wed, 28 Jul 2010 07:27:26 -0700 [thread overview]
Message-ID: <4C503E4E.3070406@gmail.com> (raw)
In-Reply-To: <AANLkTimsSvvWd+TUKR4P8S9b+U7YzbPObnd-gVr33E3P@mail.gmail.com>
On 07/28/2010 07:04 AM, Mick wrote:
> On 28 July 2010 14:53, Bill Longman <bill.longman@gmail.com> wrote:
>> On 07/28/2010 06:42 AM, Mick wrote:
>>> On 28 July 2010 09:50, KH <gentoo-user@konstantinhansen.de> wrote:
>>>
>>>> I installed grub by connecting the hdd to my workstation. This did not
>>>> change anything.
>>>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
>>>> boots fine now. I can use it but ... There is no /dev/hd* . Running
>>>> mount /boot I get the answer /dev/hda1 does not exist. Also there is no
>>>> /dev/sd*
>>>>
>>>> Any ideas?
>>>
>>> KH, if you have changed the kernel to use libATA (i.e. the newer
>>> SATA/PATA options) then you need to update your fstab from /dev/hdaX
>>> to /dev/sdaX and change your grub.conf accordingly.
>>
>> But he doesn't even have those devices, so this will not do him any good
>> until we know how the kernel is configured (or not) and get the devices
>> back.
>
> I am not sure that he does not have those devices ... I don't know if
> the error message is returned from grub or from the OS.
>
> It could be that the kernel stanza is wrongly pointing to /dev/hda,
> and, or fstab is not correct.
He says the "pc boots fine now" and he "can use it" and he goes on to
say that he has "no /dev/hd*" or "/dev/sd*" devices, so I have to
believe he's got a running system. Not having any /dev/hd* files would
support the error trying to mount /boot. Trying to fix /etc/fstab first
is not the way to attack his problem given the information we have now.
next prev parent reply other threads:[~2010-07-28 14:28 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 19:57 [gentoo-user] Problems booting my server - ext2 - e2fsck KH
2010-07-24 20:21 ` Alan McKinnon
2010-07-24 22:04 ` Robert Bridge
2010-07-25 4:57 ` KH
2010-07-25 7:49 ` Alan McKinnon
2010-07-25 8:18 ` Dale
2010-07-25 13:57 ` Mick
2010-07-28 8:50 ` KH
2010-07-28 13:42 ` Mick
2010-07-28 13:53 ` Bill Longman
2010-07-28 14:04 ` Mick
2010-07-28 14:27 ` Bill Longman [this message]
2010-07-28 14:46 ` Mick
2010-07-28 15:18 ` KH
2010-07-28 15:30 ` Bill Longman
2010-07-28 16:35 ` KH
2010-07-28 18:54 ` Mick
2010-07-28 19:29 ` Bill Longman
2010-07-28 15:21 ` KH
2010-07-28 13:45 ` Bill Longman
2010-07-28 14:56 ` KH
2010-07-28 15:27 ` Bill Longman
2010-07-28 16:37 ` KH
2010-07-28 18:14 ` Bill Longman
2010-07-29 11:39 ` Peter Humphrey
2010-11-28 16:16 ` Peter Humphrey
2010-07-25 15:24 ` covici
2010-07-25 20:10 ` Alan McKinnon
2010-07-25 20:08 ` Alan McKinnon
2010-07-26 1:05 ` Bill Kenworthy
2010-07-26 10:54 ` William Kenworthy
2010-07-26 11:02 ` Mick
2010-07-26 14:11 ` Peter Humphrey
2010-07-26 15:13 ` Mick
2010-07-26 16:44 ` Peter Humphrey
2010-07-26 18:04 ` Alex Schuster
2010-07-26 20:46 ` Mick
2010-07-26 23:56 ` Peter Humphrey
2010-07-26 14:16 ` Dale
2010-07-24 20:25 ` Alan McKinnon
2010-07-24 21:46 ` James Wall
2010-07-25 5:12 ` KH
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=4C503E4E.3070406@gmail.com \
--to=bill.longman@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