on 1st boot fsck exits with error 4

Bug #427565 reported by Manoj Iyer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
e2fsprogs (Ubuntu)
New
Undecided
Unassigned

Bug Description

After installing Kamic Alpha5, on reboot, fsck fails with exit 4. I am installing on a QEMU HDD. So attaching screen shots of the failure.

Revision history for this message
Manoj Iyer (manjo) wrote :
Revision history for this message
Manoj Iyer (manjo) wrote :
Revision history for this message
Theodore Ts'o (tytso) wrote :

What time zone are you in? And are you configuring your hardware/CMOS clock to tick in localtime instead of GMT?

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

almost certainly a dup, we can backtrack if it isn't

Revision history for this message
Theodore Ts'o (tytso) wrote :

I'm not convinced it's a dup, since this is right after an install. If the installer only installs the root filesystem after it has determined the correct timezone and set the time correctly, then there wouldn't be a problem. There's a strong possibility that the installer may not be setting the time correctly before it first mounts the file system.

I'd strongly recommend testing the installer scenario with the kernel patch; if it fixes the problem, fine, but there's a strong probability it won't. The kernel patch deal with the case where we are mounting the root filesystem read/only and there is a need to do a journal replay. This is not what would be happening in a installer situation, since the installer is mounting the file system read/write, and usually of a freshly created file system.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote : Re: [Bug 427565] Re: on 1st boot fsck exits with error 4

On Fri, 2009-09-11 at 12:51 +0000, Theodore Ts'o wrote:

> *** This bug is a duplicate of bug 427822 ***
> https://bugs.launchpad.net/bugs/427822
>
> I'm not convinced it's a dup, since this is right after an install. If
> the installer only installs the root filesystem after it has determined
> the correct timezone and set the time correctly, then there wouldn't be
> a problem. There's a strong possibility that the installer may not be
> setting the time correctly before it first mounts the file system.
>
I may have got the bug number wrong ;)

We had an installer bug that it tried to set the hardware clock and got
it wrong, storing localtime rather than UTC. That's been fixed.

(It affected alpha5 which is what manjo says he installed from)

Scott
--
Scott James Remnant
<email address hidden>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.