Doesn't cleanly umount filesystems

[Ricardo Pérez López]

In the /var/log/dmesg file, I found:

EXT3-fs: INFO: recovery required on readonly filesystem.
EXT3-fs: write access will be enabled during recovery.
kjournald starting. Commit interval 5 seconds
EXT3-fs: hda2: orphan cleanup on readonly fs
ext3_orphan_cleanup: deleting unreferenced inode 877950
EXT3-fs: hda2: 1 orphan inode deleted
EXT3-fs: recovery complete.
EXT3-fs: mounted filesystem with ordered data mode.
Adding 265028k swap on /dev/hda6. Priority:-1 extents:1
EXT3 FS on hda2, internal journal

I think Ubuntu can't properly umount filesystems when shuts down. I have
installed the system now, and I didn't install any other package than the
default ones.

The error is totally reproducible.

[Ricardo Pérez López (ricardo)]

Mmmmm... It seems that the problem is now fixed. I don't know why :/

But, surely, the first time I boot into Ubuntu, and shut down and reboot the
system again, it does not umount cleanly... Maybe the problem is in the
debian-installer...

The second, third... time, the system umounts cleanly.

I don't know if I must change the package to 'debian-installer', or remain to
'UNKNOWN' yet.

What must I do?

[Colin Watson (cjwatson)]

Can you attach /var/log/debian-installer/* to this bug, please (chiefly
/var/log/debian-installer/syslog)?

[Ricardo Pérez López (ricardo)]

Created an attachment (id=741)
/var/log/debian-installer/*

[Chessforce (chessforce)]

(In reply to comment #0)
> In the /var/log/dmesg file, I found:
>
> EXT3-fs: INFO: recovery required on readonly filesystem.
> EXT3-fs: write access will be enabled during recovery.
> kjournald starting. Commit interval 5 seconds
> EXT3-fs: hda2: orphan cleanup on readonly fs
> ext3_orphan_cleanup: deleting unreferenced inode 877950
> EXT3-fs: hda2: 1 orphan inode deleted
> EXT3-fs: recovery complete.
> EXT3-fs: mounted filesystem with ordered data mode.
> Adding 265028k swap on /dev/hda6. Priority:-1 extents:1
> EXT3 FS on hda2, internal journal
>
> I think Ubuntu can't properly umount filesystems when shuts down. I have
> installed the system now, and I didn't install any other package than the
> default ones.
>
> The error is totally reproducible.

The error still exists in Ubuntu Hoary. It does not cleanly auto-unmount a
partition with an ext3 filesystem, when shutting down. Thus, it leads to forced
fsck checks.

[Ricardo Pérez López (ricardo)]

Last saturday (March, 18), I installed Hoary, and I saw that it has the same
problem, yet.

After installation, the first time the system reboots, it doesn't unmount
filesystems correctly. Therefore, after the system reboot, fsck has to correct
errors.

I'll attach the /var/log/installer/* files, and the /var/log/messages.

[Ricardo Pérez López (ricardo)]

Created an attachment (id=1821)
/var/log/installer/* files after fresh installation

I've removed the cdebconf/templates.dat file, because renders the compressed
file too big. If you need it, ask to me.

[Ricardo Pérez López (ricardo)]

Created an attachment (id=1822)
/var/log/messages after installation, first boot into system

The messages dumped during first boot into system, until the first reboot.

[Ricardo Pérez López (ricardo)]

Created an attachment (id=1823)
/var/log/messages after first reboot, showing fsck correcting errors

After the first reboot, fsck detects an incorrect-unmounted filesystem, and
proceeds to correct it. See lines 229-234.

[Ricardo Pérez López (ricardo)]

Today I installed Hoary Preview in another (different) computer, and I got the
same result.

1. I installed Hoary Preview.
2. During the installation, the installer reboots the system.
3. The base-config continues the installation of the remaining packages.
4. I reboot the computer (using the correct GDM option).
5. In the shutting-down messages, you can see:

   unmounting filesystems

   / is busy ......... [fail]

(something similar; I don't remember exactly.) The filesystem doesn't unmount
cleanly, and it therefore forces fsck check in the next boot.

I think the problem is in base-config or prebaseconfig.

[Jason Toffaletti (jason)]

Can anyone verify that this is still an issue on Breezy and/or Dapper? Thanks.

[Martin Bergner (martin-bergner)]

There is no information for more than 3 months, I will close the bug because of its age, feel free to reopen if the problem still exists.