| 1 |
Well, |
| 2 |
|
| 3 |
a local Gentoo-guru fixed the problem with etc-update. So the failure to |
| 4 |
appears to have been there. As, a newbie I could use some subtantial |
| 5 |
advice where, when, and how ect-update should be used (there were 80 |
| 6 |
config files to take care of) - although when I failed I wasn't even |
| 7 |
aware of the problem. |
| 8 |
|
| 9 |
Fredrik |
| 10 |
|
| 11 |
----- Original Message ----- |
| 12 |
From: "Richard Fish" <bigfish@××××××××××.org> |
| 13 |
To: <gentoo-user@l.g.o> |
| 14 |
Sent: Monday, January 30, 2006 4:27 AM |
| 15 |
Subject: Re: [gentoo-user] ... fails to open device '/dev/hda2' after |
| 16 |
update |
| 17 |
|
| 18 |
|
| 19 |
> On 1/28/06, Fredrik Lundgren <fredrik.bg.lundgren@××××××××.net> wrote: |
| 20 |
>> * checking root filesystem ... |
| 21 |
>> Failed to open the device '/dev/hda2': No such file or directory |
| 22 |
>> * Filesystem couldn't be fixed: (Give root password for maintenance |
| 23 |
>> (or Control D to continue):_ |
| 24 |
>> --- |
| 25 |
>> Either this wasn't the problem or I mixed up the correction somehow. |
| 26 |
>> It |
| 27 |
>> appears as if |
| 28 |
>> the bootprocess sets the filesystem to be inaccesible? |
| 29 |
> |
| 30 |
> Can you post some of the messages that appear before this point? |
| 31 |
> |
| 32 |
> -Richard |
| 33 |
> |
| 34 |
> -- |
| 35 |
> gentoo-user@g.o mailing list |
| 36 |
> |
| 37 |
|
| 38 |
|
| 39 |
-- |
| 40 |
gentoo-user@g.o mailing list |
Archives