Announcement

Collapse
No announcement yet.

Oneiric => fsck runs at every boot and find errors, shut down problem? [SOLVED]

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Oneiric => fsck runs at every boot and find errors, shut down problem? [SOLVED]

    I have no error messages when I shutdown but every boot fsck find errors

    fernando@HollyLand:~$ dmesg | grep sda
    [ 2.205654] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
    [ 2.205690] sd 0:0:0:0: [sda] Write Protect is off
    [ 2.205693] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
    [ 2.205716] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    [ 2.284079] sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 >
    [ 2.284517] sd 0:0:0:0: [sda] Attached SCSI disk
    [ 3.336565] EXT4-fs (sda1): INFO: recovery required on readonly filesystem
    [ 3.336569] EXT4-fs (sda1): write access will be enabled during recovery
    [ 3.440626] EXT4-fs (sda1): orphan cleanup on readonly fs
    [ 3.440634] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode 530805
    [ 3.440661] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode 530789
    [ 3.440667] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode 530790
    [ 3.440673] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode 530796
    [ 3.440678] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode 530795
    [ 3.440683] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode 530794
    [ 3.440689] EXT4-fs (sda1): ext4_orphan_cleanup: deleting unreferenced inode 530793
    [ 3.440693] EXT4-fs (sda1): 7 orphan inodes deleted
    [ 3.440695] EXT4-fs (sda1): recovery complete
    [ 3.698521] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
    [ 14.755602] Adding 1050620k swap on /dev/sda7. Priority:-1 extents:1 across:1050620k
    [ 15.712719] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
    [ 16.114967] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
    [ 17.918813] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
    [ 18.373726] EXT4-fs (sda2): re-mounted. Opts: commit=0
    [ 20.583696] EXT4-fs (sda5): recovery complete
    [ 20.583702] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: (null)
    [ 20.970454] EXT4-fs (sda6): recovery complete
    [ 20.970461] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: (null)
    [ 21.209328] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0
    [ 21.363893] EXT4-fs (sda2): re-mounted. Opts: commit=0
    [ 21.366705] EXT4-fs (sda5): re-mounted. Opts: commit=0
    [ 21.369068] EXT4-fs (sda6): re-mounted. Opts: commit=0
    fernando@HollyLand:~$ cat /etc/fstab
    # /etc/fstab: static file system information.
    #
    # Use 'blkid' to print the universally unique identifier for a
    # device; this may be used with UUID= as a more robust way to name devices
    # that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc nodev,noexec,nosuid 0 0
    # / was on /dev/sda1 during installation
    UUID=cf12f15d-a17f-4226-a33e-775eea97d345 / ext4 errors=remount-ro 0 1
    # /home was on /dev/sda2 during installation
    UUID=f7cbaa4f-dcec-4c43-b2da-541312ebca7a /home ext4 defaults 0 2
    # swap was on /dev/sda7 during installation
    UUID=98745369-1d95-4a3c-bed9-70f63eb02008 none swap sw 0 0
    I tried acpi=off, disable nepomuk and pcie_aspm=force

    I'm running a Intel based notebook that used to work fine with Ubuntu Natty
    fernando@HollyLand:~$ lspci
    00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 18)
    00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 18)
    00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
    00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
    00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
    00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
    00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06)
    00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 06)
    00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06)
    00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
    00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
    00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 06)
    00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 06)
    00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
    00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 06)
    02:00.0 Network controller: Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
    04:00.0 Ethernet controller: Atheros Communications AR8131 Gigabit Ethernet (rev c0)
    3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 05)
    3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 05)
    3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 05)
    3f:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 05)
    3f:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 05)
    3f:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 05)

    #2
    Re: Oneiric =&gt; fsck runs at every boot and find errors, shut down problem?

    First suggestion would be to try running fsck from either a livecd or a partitionmagic cd.

    Also you might want to try shutting down by first logging out of kde, then getting to the console with CTRL-ALT-F1, then logging in to the console and doing sudo shutdown -h now
    That may give you a clue if something is going wrong during shutdown.

    Also grep sda /var/log/syslog may give you more info on whether the disks are not shutting down as they should.
    We only have to look at ourselves to see how intelligent life might develop into something we wouldn't want to meet. -- Stephen Hawking

    Comment


      #3
      Re: Oneiric =&gt; fsck runs at every boot and find errors, shut down problem?

      Also you might want to try shutting down by first logging out of kde, then getting to the console with CTRL-ALT-F1, then logging in to the console and doing sudo shutdown -h now
      I tried => no error messages and didn't solve the problem.


      Also grep sda /var/log/syslog may give you more info on whether the disks are not shutting down as they should.
      Just showed that the disk has being repeatedly checked at every boot.

      I found this bug report: https://bugs.launchpad.net/ubuntu/+s...it/+bug/618786

      I think it is a regression or the problem was not properly fixed.

      It seems that the disks are not unmounted before shut down and then fsck runs every boot.

      Comment


        #4
        Re: Oneiric =&gt; fsck runs at every boot and find errors, shut down problem?

        If that's the problem, then you might try this as an experiment:

        shut down your system using the REISUB method:

        log out of kde, then hold down the ALT and SYSRQ keys, and in order, waiting a second or two between each, press: R E I U S B

        This will, among other things, shut down your disks and remount them in read-only mode before rebooting. This should keep fsck happy at startup. If that works, then it probably is a bug.
        We only have to look at ourselves to see how intelligent life might develop into something we wouldn't want to meet. -- Stephen Hawking

        Comment


          #5
          Re: Oneiric =&gt; fsck runs at every boot and find errors, shut down problem?

          I remember that bug from about 2 or 3 versions ago. There is a "halt=" line somewhere in the KDE scripts, but for the life of me I can't recall which one or where it is. There should be posts on this forum about how to fix it. But this is definitely a regression.

          Comment


            #6
            Re: Oneiric =&gt; fsck runs at every boot and find errors, shut down problem?

            Yeah, I remember that too.The file is /etc/kde4/kdm/kdmrc, and mine (which works) has the lines:

            Code:
            HaltCmd=/sbin/shutdown -h -P now
            RebootCmd=/sbin/shutdown -r now
            The problem as I recall was they had a lower-case P. So the poster might check that, but this sounds like a different problem -- it sounds like shutdown itself isn't working as it should.

            Edit: just for the fun of it, you might try running sudo init 0 to shut down, and see if that makes any difference.
            We only have to look at ourselves to see how intelligent life might develop into something we wouldn't want to meet. -- Stephen Hawking

            Comment


              #7
              Re: Oneiric =&gt; fsck runs at every boot and find errors, shut down problem?

              Originally posted by doctordruidphd
              Yeah, I remember that too.The file is /etc/kde4/kdm/kdmrc, and mine (which works) has the lines:

              Code:
              HaltCmd=/sbin/shutdown -h -P now
              RebootCmd=/sbin/shutdown -r now
              The problem as I recall was they had a lower-case P.
              Bingo -- you win the recall prize for today, Dr!

              Although, in checking my Oneiric system, the entire "[Shutdown]" stanza in /etc/kde4/kdm/kdmrc is commented out. So, I wonder where that function is now configured?

              Comment


                #8
                Re: Oneiric =&gt; fsck runs at every boot and find errors, shut down problem?

                Strange. It's still there in mine, and when I alter the shutdown command in the Systemsettings > LoginScreen > Shutdown tab, it changes the entry in that file.
                We only have to look at ourselves to see how intelligent life might develop into something we wouldn't want to meet. -- Stephen Hawking

                Comment


                  #9
                  Re: Oneiric =&gt; fsck runs at every boot and find errors, shut down problem?

                  Edit: just for the fun of it, you might try running sudo init 0 to shut down, and see if that makes any difference.
                  Makes no difference - the problem continues.

                  shut down your system using the REISUB method
                  This make difference - the problem does not happen.

                  The /etc/kde4/kdm/kdmrc has the lines dealing with shut down and reboot commented. Where are these commands stored?

                  Comment


                    #10
                    Re: Oneiric =&gt; fsck runs at every boot and find errors, shut down problem?

                    Originally posted by dibl
                    the entire "[Shutdown]" stanza in /etc/kde4/kdm/kdmrc is commented out
                    Originally posted by doctordruidphd
                    Strange. It's still there in mine
                    Hm, possibly a difference between upgrades and fresh installs? My system is an upgrade, and lines are not commented out.

                    Comment


                      #11
                      Re: Oneiric =&gt; fsck runs at every boot and find errors, shut down problem?

                      The REISUB is a set of commands that are sent directly to the kernel. There is no command, per se, that will run them. It is intended as an emergency shutdown sequence if your system becomes unresponsive.

                      "Reboot Even If System Utterly Broken"

                      The actual shutdown commands are in /sbin

                      I would suggest at this point filing a bug on launchpad against kdm. Since others are not having the problem, it may not be a bug but rather a system-specific configuration problem. Filing the report will get you in contact with people who know more about the guts of kdm, and can help you track down what the problem is. That's probably the next logical step.

                      SteveRiley: maybe, mine is an upgrade also.

                      Edit: there may be something to that.

                      fernandoanatomia, try uncommenting those lines & rebooting. Might make a difference. KDM may be using kshutdown if left on its own.
                      Kshutdown works here. KDM probably using internal code to shutdown with those lines commented.

                      The lines in my kdmrc are:

                      Code:
                      [Shutdown]
                      BootManager=None
                      HaltCmd=/sbin/shutdown -h -P now
                      RebootCmd=/sbin/shutdown -r now
                      We only have to look at ourselves to see how intelligent life might develop into something we wouldn't want to meet. -- Stephen Hawking

                      Comment


                        #12
                        Re: Oneiric =&gt; fsck runs at every boot and find errors, shut down problem?

                        fernandoanatomia, try uncommenting those lines & rebooting. Might make a difference. KDM may be using kshutdown if left on its own.

                        The lines in my kdmrc are:

                        Code:

                        [Shutdown]
                        BootManager=None
                        HaltCmd=/sbin/shutdown -h -P now
                        RebootCmd=/sbin/shutdown -r now
                        I tried already - didn't work.

                        Comment


                          #13
                          Re: Oneiric =&gt; fsck runs at every boot and find errors, shut down problem?

                          PROBLEM SOLVED!

                          I first installed the Release Candidate and added the Kubuntu Updates PPA to use Kde 4.7. When 4.7 reached the official repository some problem should happened.... I just made a fresh install and it is working like a charm now.

                          Thank you guys!

                          Comment


                            #14
                            Re: Oneiric =&gt; fsck runs at every boot and find errors, shut down problem? SOLVED

                            My 11.10 was installed sometime in the Beta days, and upgraded fairly continuously. It is on a VM, but I don't think that would make a difference on this function.

                            Comment


                              #15
                              Re: Oneiric =&gt; fsck runs at every boot and find errors, shut down problem? UNSOLVED

                              This is a zombie problem it's back from the dead!!!

                              It's happening again.

                              Uninstalled VMWare Player 4 and nothing changed...


                              Every six months I have a broken system...

                              Comment

                              Working...
                              X