[gentoo-user] ERROR: cannot start hwclock as fsck would not start

[gentoo-user] ERROR: cannot start hwclock as fsck would not start

[Hilco Wijbenga]

Hi all,

I've had the above error during boot for quite some time now so
clearly it doesn't have too major consequences. :-) I would, however,
like to understand what's going on and then, if possible, fix it.

The first thing I tried was to grep for (parts of) this error in the
/etc/init.d scripts but that yielded nothing. Using extra ewarns in
/etc/init.d/hwclock and /etc/init.d/fsck I discovered that both
hwclock and fsck *do* indeed run (but after the error is displayed).
Looking in other places (/usr/lib/portage, /usr/portage, /etc) didn't
yield anything useful either.

lion ~ # rc-update show
gpm | default
ntp-client | default
fsck | boot
hald | default
mtab | boot
ntpd | default
root | boot
swap | boot
keymaps | boot
local | default nonetwork
vixie-cron | default
syslog-ng | default
maradns | default
localmount | boot
consolefont | boot
modules | boot
hostname | boot
net.lo | boot
net.eth0 | default
procfs | boot
netmount | default
sysctl | boot
urandom | boot
termencoding | boot
hwclock | boot
bootmisc | boot
device-mapper | boot
alsasound | boot

Any ideas?

Cheers,
Hilco

Re: [gentoo-user] ERROR: cannot start hwclock as fsck would not start

[ionut cucu]

On Thu, 31 Jul 2008 22:32:31 -0700
"Hilco Wijbenga" <hilco.wijbenga@gmail.com> wrote:

> Hi all,
> 
> I've had the above error during boot for quite some time now so
> clearly it doesn't have too major consequences. :-) I would, however,
> like to understand what's going on and then, if possible, fix it.
> 
> The first thing I tried was to grep for (parts of) this error in the
> /etc/init.d scripts but that yielded nothing. Using extra ewarns in
> /etc/init.d/hwclock and /etc/init.d/fsck I discovered that both
> hwclock and fsck *do* indeed run (but after the error is displayed).
> Looking in other places (/usr/lib/portage, /usr/portage, /etc) didn't
> yield anything useful either.
> 
> lion ~ # rc-update show
> gpm | default
> ntp-client | default
> fsck | boot
> hald | default
> mtab | boot
> ntpd | default
> root | boot
> swap | boot
> keymaps | boot
> local | default nonetwork
> vixie-cron | default
> syslog-ng | default
> maradns | default
> localmount | boot
> consolefont | boot
> modules | boot
> hostname | boot
> net.lo | boot
> net.eth0 | default
> procfs | boot
> netmount | default
> sysctl | boot
> urandom | boot
> termencoding | boot
> hwclock | boot
> bootmisc | boot
> device-mapper | boot
> alsasound | boot
> 
> Any ideas?
> 
> Cheers,
> Hilco
> 
Same here with that error, didn't even noticed it till now. Maybe we
should open a bug report

Re: [gentoo-user] ERROR: cannot start hwclock as fsck would not start

[Hilco Wijbenga]

On Mon, Aug 4, 2008 at 11:29 PM, ionut cucu <cuciferus@gmail.com> wrote:
> On Thu, 31 Jul 2008 22:32:31 -0700
> "Hilco Wijbenga" <hilco.wijbenga@gmail.com> wrote:
>
>> Hi all,
>>
>> I've had the above error during boot for quite some time now so
>> clearly it doesn't have too major consequences. :-) I would, however,
>> like to understand what's going on and then, if possible, fix it.
>>
>> The first thing I tried was to grep for (parts of) this error in the
>> /etc/init.d scripts but that yielded nothing. Using extra ewarns in
>> /etc/init.d/hwclock and /etc/init.d/fsck I discovered that both
>> hwclock and fsck *do* indeed run (but after the error is displayed).
>> Looking in other places (/usr/lib/portage, /usr/portage, /etc) didn't
>> yield anything useful either.
>>
>> lion ~ # rc-update show
>> gpm | default
>> ntp-client | default
>> fsck | boot
>> hald | default
>> mtab | boot
>> ntpd | default
>> root | boot
>> swap | boot
>> keymaps | boot
>> local | default nonetwork
>> vixie-cron | default
>> syslog-ng | default
>> maradns | default
>> localmount | boot
>> consolefont | boot
>> modules | boot
>> hostname | boot
>> net.lo | boot
>> net.eth0 | default
>> procfs | boot
>> netmount | default
>> sysctl | boot
>> urandom | boot
>> termencoding | boot
>> hwclock | boot
>> bootmisc | boot
>> device-mapper | boot
>> alsasound | boot
>>
>> Any ideas?
>>
>> Cheers,
>> Hilco
>>
> Same here with that error, didn't even noticed it till now. Maybe we
> should open a bug report

I removed hwclock (rc-update del hwclock) and that seems to have
"fixed" it. I'm still not sure on why this happened though.