Re: fsck died with nexit status 8
- From: "Sudev Barar" <sbarar@xxxxxxxxx>
- Date: Tue, 15 Apr 2008 09:32:16 +0530
On 15/04/2008, L. V. Gandhi <lvgandhi@xxxxxxxxx> wrote:
I get the above message while booting and halts for maintenance. I
have winxp, kubuntu also in the same machine. I give root password,
umount /dev/sda9 which is root and do e2fsck /dev/sda9. I get msg
"Superblock last mount time is in future. Fix(y)?. I do y.Then iot
says /dev/sda9 clean. But if I reboot immediately, then also the
machine gets halted with same message?
Any idea why this occurs?
I too faced this problem in past. My impression is that usually at
time of install the system clock is not set in some distros or your
local time gets set as EST (US) which means that at next boot in terms
of local time (Indian) you are looking at file system having a future
time stamp by about 12 hours.
You get this error even if you run updatedb or sudo commands on
install. This occurs for the first day and then everything starts
behaving presumably because your local time stamp is now atleast equal
or ahead of time stamp on files..
What is the solution?
Perhaps a trivial bug that needs to be corrected in installer.
--
Regards,
Sudev Barar
Read http://blog.sudev.in for topics ranging from here to there.
--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx
- References:
- fsck died with nexit status 8
- From: L . V . Gandhi
- fsck died with nexit status 8
- Prev by Date: Re: euro sign / nobreak space
- Next by Date: Re: IO diagnose tools?
- Previous by thread: Re: fsck died with nexit status 8
- Next by thread: subversion that just updated in sid does not support ssl?
- Index(es):
Relevant Pages
|
