Unable to shut down or restart on Karmic

same problem here...

Jack, someone on the forums showed me a nifty trick to reboot until this is fixed:
http://kember.net/articles/231/reisub-the-gentle-linux-restart

He said you can change the B to O to shut down, he thinks...I haven't tried it yet.

-Yos

ok. I'll try it too! thanks!

Same issue here. Just for your info it was Jaunty 9.04 on Wubi and upgraded to Karmic 9.10 release. @ Yos, thx for the tip.

If confirmed, this is an important issue.
I do not seem to be able to reproduce it here though, anything you did that might help recreating the problem?

What is the output of

cat /proc/cmdline
cat /var/run/sendsigs.omit

?

You might have to manually run the shutdown commands (/etc/rc6.d) in the right order from terminal until you find the problematic one (probably S40 or S60).

Ciao Agostino, FYI I have another laptop here (Dell Latitude D810) showing exactly the same behaviour... Even this one was running Jaunty on Wubi and was upgraded to Karmic. Here is the output you have requested:

$ cat /proc/cmdline
root=UUID=4E2CC33C2CC31E39 loop=/ubuntu/disks/root.disk ro quiet splash
~$ cat /var/run/sendsigs.omit
383

I will try to shut down manually as you have suggested and find the problematic one. One remark shutdown and restart worked like a charm on Jaunty before the upgrade.

Regards,
Enrico.

here is the output:

marco@marcocunha:~$ cat /proc/cmdline
root=UUID=9C583FD5583FACC0 loop=/ubuntu/disks/root.disk ro quiet splash
marco@marcocunha:~$ cat /var/run/sendsigs.omit
438

Is it possible that this might have something to do with the 9.04 Wubi instalation ?

Is this a clean installation on 9.10? Are you using ntfs? If so there should be another boot paramter:

rootflags=syncio

this is a upgrade from a 9.04 wubi installation under vista... I think I'm using ntfs but i'm a newbie. How do I check it out?

I confirm I'm using NTFS file system. I did not edit the root parameters and let Karmic upgrade the system automatically.

Should I add this to the boot sequence? Any advice would be welcome...

how and where should we add this? I'd tried to edit cmdline without success..

if you are using grub legacy (default for wubi 9.04), you should add it within /boot/grub/menu.lst in kopt
Then run: sudo update-grub

Do you experience the same issue with a clean installation of 9.10?

I did not try it. I will do it on another pc and advise. It's not clear to me where I should add the parameter? Here is my menu.lst.

The kopt session is all commented.

# menu.lst - See: grub(8), info grub, update-grub(8)
# grub-install(8), grub-floppy(8),
# grub-md5-crypt, /usr/share/doc/grub
# and /usr/share/doc/grub-doc/.

## default num
# Set the default entry to the entry number NUM. Numbering starts from 0, and
# the entry number 0 is the default if the command is not used.
#
# You can specify 'saved' instead of a number. In this case, the default entry
# is the entry saved with the command 'savedefault'.
# WARNING: If you are using dmraid do not use 'savedefault' or your
# array will desync and will not let you boot your system.
default 0

## timeout sec
# Set a timeout, in SEC seconds, before automatically booting the default entry
# (normally the first entry defined).
timeout 0

## hiddenmenu
# Hides the menu by default (press ESC to see the menu)
hiddenmenu

# Pretty colours
#color cyan/blue white/blue

## password ['--md5'] passwd
# If used in the first section of a menu file, disable all interactive editing
# control (menu entry editor and command-line) and entries protected by the
# command 'lock'
# e.g. password topsecret
# password --md5 $1$gLhU0/$aW78kHK1QfV3P2b2znUoe/
# password topsecret

#
# examples
#
# title Windows 95/98/NT/2000
# root (hd0,0)
# makeactive
# chainloader +1
#
# title Linux
# root (hd0,1)
# kernel /vmlinuz root=/dev/hda2 ro
#

#
# Put static boot stanzas before and/or after AUTOMAGIC KERNEL LIST

### BEGIN AUTOMAGIC KERNELS LIST
## lines between the AUTOMAGIC KERNELS LIST markers will be modified
## by the debian update-grub script except for the default options below

## DO NOT UNCOMMENT THEM, Just edit them to your needs

## ## Start Default Options ##
## default kernel options
## default kernel options for automagic boot options
## If you want special options for specific kernels use kopt_x_y_z
## where x.y.z is kernel version. Minor versions can be omitted.
## e.g. kopt=root=/dev/hda1 ro
## kopt_2_6_8=root=/dev/hdc1 ro
## kopt_2_6_8_2_686=root=/dev/hdc2 ro
# kopt=root=UUID=4E2CC33C2CC31E39 loop=/ubuntu/disks/root.disk ro

## default grub root device
## e.g. groot=(hd0,0)
# groot=()/ubuntu/disks

## should update-grub create alternative automagic boot options
## e.g. alternative=true
## alternative=false
# alternative=true

## should update-grub lock alternative automagic boot options
## e.g. lockalternative=true
## lockalternative=false
# lockalternative=false

## additional options to use with the default boot option, but not with the
## alternatives
## e.g. defoptions=vga=791 resume=/dev/hda5
# defoptions=quiet splash

## should update-grub lock old automagic boot options
## e.g. lockold=false
## lockold=true
# lockold=false

## Xen hypervisor options to use with the default Xen boot option
# xenhopt=

## Xen Linux kernel options to use with the default Xen boot option
# xenkopt=console=tty0

## altoption boot targets option
## multiple altoptions lines are allowed
## e.g. altoptions=(extra menu suffix) extra boot options
## ...

# kopt=root=UUID=4E2CC33C2CC31E39 loop=/ubuntu/disks/root.disk ro rootflags=syncio

Then run: sudo update-grub

Hmm the line above was split, it's all in one line:

# kopt= ... rootflags=syncio

Done. Unfortunately it did not fix it. Now the error messages reports several errors "Buffer I/O error on device loop0, logical block xxxxxx".

Agostino,

You asked if the same thing happens on a clean install. I just moved away from wubi and did a clean install yesterday and now it works perfectly.

-Yos

:(
I did something wrong... very wrong! now I can't startup my system!
It hangs on startup saying:

ALERT! /dev/disk/by-uuid/4E2CC33C2CC31E39 does not exist- Droping to a shell!
(initramfs)

how can i undu this mistake?

Hi please try the following from an dist-upgraded Wubi Jaunty installation:

edit /etc/rc6.d/S40umountfs

replace

fstab-decode umount -f -r -d $WEAK_MTPTS

with

fstab-decode umount -r -d $WEAK_MTPTS

and

fstab-decode umount -f -v -r -d $WEAK_MTPTS

with

fstab-decode umount -v -r -d $WEAK_MTPTS

Then try to reboot and let me know if it works

Jack, press "ESC" after selecting "ubuntu", then press "e" within the grub boot menu to edit the menu entries or "c" to get a console. In the console you can see what partitions are available. If the windows partition cannot be mounted or is not accessible from linux, you might have to check the file system from within windows.

Agostino, the windows partition is ok, can be mounted from the linux...
Is there any way to revert the changes I made in /boot/grub/menu.lst ?
now i'm stuck! I can't start up my ubuntu
When explaining something don't forget i'm a newbie! :)
thanks!

jack

Confirmed.

With the upgrade now in place wubi refuses to restart from the end of the upgrade.

After powering down using the power button I can once again get into the system.

However once rebooted I can start and stop and restart the system at will.

Ago I can try against xp this afternoon if that will help?

Dave can you please test whether the changes in #19 help?

Does the issue only happen during the first reboot after the upgrade 9.04 -> 9.10 or does it happen every time after the upgrade?
From the other comments it looks like the latter is the case.

davmor2@ubuntu:~$ mount
/dev/loop0 on / type ext3 (rw,errors=remount-ro)
proc on /proc type proc (rw)
none on /sys type sysfs (rw,noexec,nosuid,nodev)
none on /sys/fs/fuse/connections type fusectl (rw)
none on /sys/kernel/debug type debugfs (rw)
none on /sys/kernel/security type securityfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
none on /dev/shm type tmpfs (rw,nosuid,nodev)
none on /var/run type tmpfs (rw,nosuid,mode=0755)
none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
none on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
/dev/sda3 on /host type fuseblk (rw)
/host/ubuntu/disks/boot on /boot type none (rw,bind)
binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
gvfs-fuse-daemon on /home/davmor2/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=davmor2)

Please see if you can reproduce that consistenly.
My best guess so far is that comment #19 should fix the issue.
Please confirm.

Untested patch

--- /etc/init.d/umountfs 2009-10-14 05:15:49.000000000 +0100
+++ /tmp/umountfs 2009-11-03 14:58:38.767258508 +0000
@@ -94,13 +94,14 @@
  #
  if [ "$WEAK_MTPTS" ]; then
   if [ "$VERBOSE" = no ]
+ # Do not use the -f umount option here
   then
    log_action_begin_msg "Unmounting weak filesystems"
- fstab-decode umount -f -r -d $WEAK_MTPTS
+ fstab-decode umount -r -d $WEAK_MTPTS
    log_action_end_msg $?
   else
    log_daemon_msg "Will now unmount weak filesystems"
- fstab-decode umount -f -v -r -d $WEAK_MTPTS
+ fstab-decode umount -v -r -d $WEAK_MTPTS
    log_end_msg $?
   fi
  fi

Agostino...
i'm still stuck here... should i give up or is there hope for my case? I made something wrong when editing /boot/grub/menu.lst and know i can't even start my ubuntu ...

ok, back on-line. The problem seams solved, but now the boot takes over 2.5 minutes. Any idea why?

Ciao Agostino, I tried your solution # 19 and I'm glad to inform you it works! The system reboot now very quickly. Thank you very much for your help.

Enrico,

Hi Agostino: I also tried #19 remotely leading a 75 year old friend through these edits and he is now happy.
Now on to doing the same for a 89 year old guy who lives 1000 miles away. Many thanks for your hard work.

Can confirm solved issue on a 9.04 Wubi upgrade to 9.10

Sorry key haapy:- #19 Solve issue on Wubi 9.04 upgraded to 9.10

Hi Agostino,
+1 confirmation that #19 solved the problem :)
thanks for the work, saved my day.

I have the same problem on a HP mini since last night. I will try these fixes after I get back from work and see what happens. Thanks in advance :)

Btw, someone suggested to me to run on the terminal: sudo gedit /etc/init.d/halt
and add the following line to the top of the halt script: rmmod snd-hda-intel

I tried it and it does work. Not sure if it meshes with anything else though...
Cheers!

Alex, the fix above is only relevant if you installed via Wubi 9.04 and then upgraded to 9.10.

Same here: Ubuntu 9.04 installed with Wubi and then upgraded to 9.10. After upgrading I was neither able to reboot nor shutting down the system.

I applied the solution posted on #19 and now I can reboot and shut down safely.
Thank you Agostino!

vince

Yes it works :)
 Many thanks Agostino !!

When can we expect an update to be made available through the package manager?

Agostino, your solution at #19 Works!!!!!!!!!!!!!!!!!!!!!
I have a question, the problem was the fault of Ubuntu or of Wubi?

Hi there I have the same bug from a Wubi 9.04 upgrade to Kubuntu 9.10, I tried fix 19. I guess i was supposed to type that in to the terminal. So in the terminal I typed

edit /etc/rc6.d/S40unmountfs

and i get back

Warning: unknown mime-type for "/etc/rc6.d/S40unmountfs" -- using "application/octet-stream"
Error: no write permission for file "/etc/rc6.d/S40unmountfs"

Any thoughts? I have NMR on my netbook, which refuses to upgrade and Kubuntu that will not shut down on my PC. I am thinking £30 for Windows 7 is looking a very good deal!

ciao Alex:
before buying windows7 try

sudo nano /etc/rc6.d/S40unmountfs

I have a nano window open following typing your commands. But it is blank except for some menu options at the bottom. which appear to be shift commands for help etc I am a bit stuck and probably out of my depth. I was able to open S40unmounts in Kate but can not save any edits because I am not root user. I think this is the heart of the matter. I have been looking on net and forums how to get in as root user but no luck yet. It is mostly along the lines, 'for security reasons the previous edit as root user functions have been removed in KDE4'

Finally cracked it. In terminal wrote sudo kate. Then used Kate to edit as suggested in 19. And problem solved. Any one any ideas why it is so hard to get root access, even sudo edit does not give it. I am fairly new to all this and it seems just a touch too hard to me. Particularly as the help files are always empty! Thank you for time Jack and Mr Russo. I like Kubuntu but I still think I shall get Win 7. For £30 it is a steal

alex, Ubuntu is set up very differently from how you may be used to with Windows. Here are a couple things to remember:

The root is also known as the "Super User", hence the 'su' in the sudo command. Therefore, any time you *need* to run a program from the terminal as administrator (which should be rare), you use sudo to temporarially give you admin rights.

This is not to be used lightly! Do not get into the habit of editing these files before understanding them. Esspecially do not get into the habit of running terminal commands before understanding what they mean.

Lastly, become familiar with 'man' and 'info' pages. For most programs, you can get a manual by typing 'man <name-of-program>'. The graphical help is years behind the man and info pages.

Thank you for your advice.

Unfortunately because Kubuntu is a little buggy it is always necessary to get root access to fix the bugs. Such as in this case. Not being able to shut down is fairly serious. I am just about competent enough to edit a file. Not something i would choose to do. Any idea why sudo edit would not work but sudo kate does? Thanks for the advice on man and info pages. It is really quite hard to find help for most parts of Kubuntu. Perhaps this is a discussion for another time. I put this information about sudo kate up for anyone in my position with my skill set. There must be a fair number in a similar position since Wubi is for newbies like me and this appears to be related to Wubi installs and upgrades.

Thanks you all for your help
Alex

Will there be a update to fix this? Thank you for all your help.

> Date: Thu, 5 Nov 2009 00:37:27 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 468589] Re: Unable to shut down or restart on Karmic
>
> alex, Ubuntu is set up very differently from how you may be used to with
> Windows. Here are a couple things to remember:
>
> The root is also known as the "Super User", hence the 'su' in the sudo
> command. Therefore, any time you *need* to run a program from the
> terminal as administrator (which should be rare), you use sudo to
> temporarially give you admin rights.
>
> This is not to be used lightly! Do not get into the habit of editing
> these files before understanding them. Esspecially do not get into the
> habit of running terminal commands before understanding what they mean.
>
> Lastly, become familiar with 'man' and 'info' pages. For most programs,
> you can get a manual by typing 'man <name-of-program>'. The graphical
> help is years behind the man and info pages.
>
> --
> Unable to shut down or restart on Karmic
> https://bugs.launchpad.net/bugs/468589
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Wubi, Windows Ubuntu Installer: Confirmed
> Status in “sysvinit” package in Ubuntu: Confirmed
>
> Bug description:
> I recently upgraded to ubuntu 9.10, Karmic Koala, and I discovered that I am unable to shut down or reboot. When I select shut down, Karmic starts the process and then hangs. What I get on my screen is this:
>
> *Stopping Kernel Oops catching service kerneloops
> *Shutting down ALSA...
> *Asking all remaining processes to terminate...
> *Deconfiguring network interfaces...
> *Deactivating swap...
> [ 171.180168] Buffer I/O error on device loop0, logical block 3834127
> [ 171.180116] Buffer I/O error on device loop0, logical block 3856120
> _
>
> Then a blinking curser. I have no alternative at this point than to manually press the power button to shut down. I will follow this thread so please tell me if you require more information
>
> -Yos

_________________________________________________________________
Hotmail: Trusted email with powerful SPAM protection.
http://clk.atdmt.com/GBL/go/177141665/direct/01/

Hi Agostino Russo, in order to fix this problem, do I type the instructions of #19 in a terminal?

Thanks for help

I tried solution #19, it worked for the "restart" option, but not for the "shutdown"

When can we expect an update to be made available through the package manager? Can anyone let me know, please.

Thank You

Grazie Agostino! Solution #19 worked for my system as well (9.04 wubi upgrade 9.10), I can reboot and shut down safely.

Edit command didn't work for me, so I installed Kate as suggested by alex #48 (by the way, his mistake was to write "unmountfs" while it is "umountfs").

Thanks again!

Can you please give an analysis how this affects non-wubi installs? In particular, what are weak mountpoints in this context?

Thanks!

Can you walk me thru this, so I can fix my Ubuntu, please.

> Date: Fri, 6 Nov 2009 10:02:47 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: [Bug 468589] Re: Unable to shut down or restart on Karmic
>
> Can you please give an analysis how this affects non-wubi installs? In
> particular, what are weak mountpoints in this context?
>
> Thanks!
>
> ** Also affects: sysvinit (Ubuntu Karmic)
> Importance: Undecided
> Status: New
>
> ** Also affects: sysvinit (Ubuntu Lucid)
> Importance: High
> Assignee: Evan Dandrea (evand)
> Status: Fix Committed
>
> --
> Unable to shut down or restart on Karmic
> https://bugs.launchpad.net/bugs/468589
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Wubi, Windows Ubuntu Installer: Invalid
> Status in “sysvinit” package in Ubuntu: Fix Committed
> Status in “sysvinit” source package in Lucid: Fix Committed
> Status in “sysvinit” source package in Karmic: New
>
> Bug description:
> This has been addressed by dropping the -f argument to umount calls when Wubi is present.
>
> Patch:
> http://launchpadlibrarian.net/35058732/sysvinit_2.87dsf-4ubuntu12.debdiff
>
> To reproduce:
> Install Ubuntu 9.04 using Wubi.
> Upgrade to Ubuntu 9.10.
> Shut down.
>
> The original report follows:
> I recently upgraded to ubuntu 9.10, Karmic Koala, and I discovered that I am unable to shut down or reboot. When I select shut down, Karmic starts the process and then hangs. What I get on my screen is this:
>
> *Stopping Kernel Oops catching service kerneloops
> *Shutting down ALSA...
> *Asking all remaining processes to terminate...
> *Deconfiguring network interfaces...
> *Deactivating swap...
> [ 171.180168] Buffer I/O error on device loop0, logical block 3834127
> [ 171.180116] Buffer I/O error on device loop0, logical block 3856120
> _
>
> Then a blinking curser. I have no alternative at this point than to manually press the power button to shut down. I will follow this thread so please tell me if you require more information
>
> -Yos
>
>

_________________________________________________________________
Hotmail: Trusted email with Microsoft's powerful SPAM protection.
http://clk.atdmt.com/GBL/go/177141664/direct/01/
http://clk.atdmt.com/GBL/go/177141664/direct/01/

Can anyone tell me the steps to fix this,please. I look forward to hearing back.

Because I did "Sudo Kate" and nothing happen to let me edit.

Hi Martin,

If you use umount -f with a bind mount, it is not only the bind mount that goes, but the underlying device gets umounted as well. This of course can have undesired effects.

In the case of wubi 9.04, /boot is bind mounted onto the /host device (which is the one hosting the root loopfile). Unmounting the /boot mountpoint therefore you also unmount /host which is not what we want.

I am not sure if there are any use cases other than wubi. Weak mountpoints are all mountpoints that use any device mounted before and including root. Therefore those mounpoints are unmounted without using force (-f).

The weak-mountpoint behaviour has been the default in a while, it was a regression in karmic that I didn't notice before this report. So the patch restores previous behaviour.

The reason it was not spotted in all the tests, is that wubi 9.10 does not use a bind mounted /boot anymore and therefore the regression did not have any impact.

rhulse12, from a terminal you can always use:

sudo nano /etc/init.d/umountfs

Here is an alternative way to perform solution #19:

Open a file browser and go to '/etc/rc6.d'.

Within that folder select file 'S40umountfts' and open it with your gedit.

Select the whole thing and paste the text on to a new file.

Replace 'fstab-decode umount -f -r -d $WEAK_MTPTS' with 'fstab-decode umount -r -d $WEAK_MTPTS' (line 99) and 'fstab-decode umount -f -v -r -d $WEAK_MTPTS' with 'fstab-decode umount -v -r -d $WEAK_MTPTS' (line 103).

Change its type so 'sh' (see screenshot) on the lower tab and save it on your area (remember to name it 'S40umountfts').

Now open a terminal and "empower" your self as the root.

Guide the terminal to the folder where you saved your file and move it to '/etc/rc6.d'.

The comand line should be as it follows:

azevedo@ubuntu:/$ su
Password:
root@ubuntu:/# cd /home/azevedo
root@ubuntu:/home/azevedo# mv S40umountfts /etc/rc6.d

Finaly, do a reboot.

rhulsel12

Open a terminal

type sudo edit /etc/rc6.d/S40umountfs
you will be asked for a password. Type the password you use to login in to your desktop at start up

In the file scroll down and when you see

fstab-decode umount -f -r -d $WEAK_MTPTS

 replace it with

fstab-decode umount -r -d $WEAK_MTPTS

and replace

fstab-decode umount -f -v -r -d $WEAK_MTPTS

with

fstab-decode umount -v -r -d $WEAK_MTPTS

save

now reboot.

This is a walk through of the instructions of 19. If i had my glasses on i would have not misread the file name and I would not have had so much trouble that you can see in my comments. If you are using Kubuntu you can use Sudo kate and use Kate to find the file and edit it. Kate is a graphical interface file editor that you might find easier. I hope that helps.

BTW now fixed, Kubuntu is sweet. Still going to part with my £30 for W7 as well

This is what happen after typing "sudo edit /etc/rc6.d/S40umountfs"

hulse12@ubuntu:~$ sudo edit /etc/rc6.d/S40umountfs
Warning: unknown mime-type for "/etc/rc6.d/S40umountfs" -- using "application/octet-stream"
Error: no "edit" mailcap rules found for type "application/octet-stream"
hulse12@ubuntu:~$

I look forward to hearing back

Thank You

Try typing "sudo nautilus"

Nautilus opens and you can navigate to /etc/rc6.d/
(don't close the terminal!)

Open S40umountfs (select display), make the changes and save the file (as you are doing it as su there is no problem)

Worked for me like a charm.

Hey guys!

Turns out, I realized 'edit' didn't work because it wasn't a legit command
for me; instead, I typed sudo gedit /etc/rc6.d/S40umountfs and it worked.
I'm sure it works with vi or emacs too.

-Yi

On Sat, Nov 7, 2009 at 2:28 AM, 4AD <email address hidden> wrote:

> Try typing "sudo nautilus"
>
> Nautilus opens and you can navigate to /etc/rc6.d/
> (don't close the terminal!)
>
> Open S40umountfs (select display), make the changes and save the file
> (as you are doing it as su there is no problem)
>
> Worked for me like a charm.
>
> --
> Unable to shut down or restart on Karmic
> https://bugs.launchpad.net/bugs/468589
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in Wubi, Windows Ubuntu Installer: Invalid
> Status in “sysvinit” package in Ubuntu: Fix Committed
> Status in “sysvinit” source package in Lucid: Fix Committed
> Status in “sysvinit” source package in Karmic: New
>
> Bug description:
> This has been addressed by dropping the -f argument to umount calls when
> Wubi is present.
>
> Patch:
> http://launchpadlibrarian.net/35058732/sysvinit_2.87dsf-4ubuntu12.debdiff
>
> To reproduce:
> Install Ubuntu 9.04 using Wubi.
> Upgrade to Ubuntu 9.10.
> Shut down.
>
> The original report follows:
> I recently upgraded to ubuntu 9.10, Karmic Koala, and I discovered that I
> am unable to shut down or reboot. When I select shut down, Karmic starts
> the process and then hangs. What I get on my screen is this:
>
> *Stopping Kernel Oops catching service kerneloops
> *Shutting down ALSA...
> *Asking all remaining processes to terminate...
> *Deconfiguring network interfaces...
> *Deactivating swap...
> [ 171.180168] Buffer I/O error on device loop0, logical block 3834127
> [ 171.180116] Buffer I/O error on device loop0, logical block 3856120
> _
>
> Then a blinking curser. I have no alternative at this point than to
> manually press the power button to shut down. I will follow this thread so
> please tell me if you require more information
>
> -Yos
>
>
>

Thanks, Agostino Russo. The fix described in post #19 resolved the issue for me. IBM Thinkpad R52, Wubi, upgraded from 9.04 to 9.10.

Confirming Post #19, Very nice work Agostino. I to had upgraded from a 9.04 wubi install to 9.10. Did not have any problems though on my full install on my desktop.

Hi, sorry but i can't understand how can i fix this bug. When i reboot my pc, this is the result:

Booting Ubuntu 9.10
Filesystem type is nfts, partiton type 0x07
ubuntu login: [3186:342464] Buffer I/O error on device loop0, logical block 1255432Linux-bxImage, setup=0x3400, size 0x3b26e0]
[3186.342931] Buffer I/O error on device loop0, logical block 1255433
[3186.343373] Buffer I/O error on device loop0, logical block 1255434
[3186.343787] Buffer I/O error on device loop0, logical block 1255435
[3220.168050] Buffer I/O error on device loop0, logical block 3299650

What should I do? I use Wubi to install Ubuntu on my desktop.
Please,help me.

here is my output:

from a fresh install without wubi (was a2 then updated):

- always need to "cold" boot
- case 1: use of "shutdown menu choice" work fine
- case 2: use of " restart menu choice " ; session is closed correctly but system is not stopped; need to power off manually

After applying changes from #19, nothing new: same problems than previously.

So, need to investigate deeper.

oops, needed to validate

more comments & testing:

 - i've checked with Windows: select xpsp3 in grub2 menu & boot
   boot fine, open & use apps then close them & finally choose to restart xp: like with ubuntu, xp closed but system does not shut down, so can't reboot.

 That makes me thinking it's rather a problem with grub2 & its dependencies ( maybe os-prober) than sysvinit ( but i'm not an expert )

dino99,

I believe your problem is different because of the issues exists with Windows as well as Ubuntu. Plus, this problem is specific to wubi from 9.04 and earlier, and the fix would not help you. Please file a new bug report so that we may be able to help you better.

MattiaBorrelli,

If you are feeling adventurous, you can try the instructions given by alex in comment 63, except instead of 'sudo edit /etc/rc6.d/S40umountfs', use the command 'sudo gedit /etc/rc6.d/S40umountfs'.

If you are not feeling adventurous (which is ok), I suspect that one of the Ubuntu updates will take care of this for you.

hi WG,

it's the same subject: Unable to shut down or restart on Karmic

i can add that even after a normal shutdown ( seem ok), using "power" button on keyboard, grub2 hang at "grub loading". At that time i need to power off and then make a cold boot.

So, don't matter what os is selected in grub menu: the shutdown process is not complete.

dino99,

I know it is the same subject, but the cause is different. Therefore, the fix is different. Also, there is a subtle difference between your problem and everyone else's problem in this bug report: your session actually ends, while theirs did not. Please file a new bug report. File it as a grub bug, and note in the subject line that both Ubuntu and Windows can not seem to reboot properly.

This is what happen now! Can I get some help, please....

hulse12@ubuntu:~$ sudo nautilus

(nautilus:2166): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
Initializing nautilus-gdu extension

** (nautilus:2166): WARNING **: No marshaller for signature of signal 'UploadFinished'

** (nautilus:2166): WARNING **: No marshaller for signature of signal 'DownloadFinished'

** (nautilus:2166): WARNING **: No marshaller for signature of signal 'ShareCreateError'
Nautilus-Share-Message: Called "net usershare info" but it failed: 'net usershare' returned error 255: net usershare: cannot open usershare directory /var/lib/samba/usershares. Error No such file or directory
Please ask your system administrator to enable user sharing.

rhulse12, the advice you got was poor and I am sorry for missing it so that I could correct it. Please follow my advice in comment 74.

Confirming comment #19: Thanks to your instructions Ubuntu is shuting down normally now (9.04 wubi upgrade 9.10). Thanks a million!

Used the advice in #19 combined with #66 on a Wubi installed 9.04 to 9.10 upgrade with the same problem, and it now works. Thanks to all!

I tried the #19 solution posted by Agostino Russo in an administrative account terminal. I got a bad command reply. I then figured I had to try an editor, so tried it as "gedit", which did not let me save. I figured I needed superuser privileges, so tried it as: "sudo gedit /etc/rc6.d/S40umountfs"
 (quotes are mine, don't type them in the terminal). This led me to some nicely colored command lines. I edited the appropriate ones per Mr. Russo in #19 by backspacing to remove the "-f" in the places recommended. Fastest, cleanest shutdowns I have ever seen on a computer. I have repeatedly shut down the computer from a variety of modes (admin user, limited user, log-in screen) with no problems. Agostino, you are a genius. In another forum, you can earn beans. You deserve a bean for this one.

I did everything you said with #19 and #66 and so far, so good. I will keep eye on it. But thank you very much, for all your help with this.

Scott, I'd appreciate a review from you whether this could have any negative impact on a non-wubi system. Thanks!

Note that the weak_mountpoint behaviour has been in since 8.04, it was reverted in 9.10 by a patch that reintroduced the -f flag. I cannot do it now, but it would be interesting to fetch the changelog of sysvinit and see whether the author reintroduced -f thinking it was an omission, or whether it was done to fix another bug.

I think everything is working fine now. But I will let you know if any thing changes.

Thank You

Hey there!
I do not normally write in theese forums, but I just wanted to greet agostino russo for the help. I upgraded from ubuntu 9.4 (installed from windows vista) to 9.10. Did the fixing on #19 and did a few shutdows to test it, works well!!! Agostino you are the man!!!!!
Greetings from the land of tequila!!!!!!

p.s. working on a toshiba satellite newer version.

I didn't find a particular changelog entry for this, but I confirm that the jaunty version of this did not use -f for weak mountpoints. And even the karmic version still says

  WEAK_MTPTS="" # be gentle, don't use force

but then uses it anyway. So I'm more convinced now that this won't break the world, so I'll accept it into -proposed.

Accepted sysvinit into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Please either enable the karmic-proposed repository (see link in Martin's post #88) and then do a system upgrade. Or install one of the packages below which is appropriate for you.

For 32 bit ubuntu:
http://archive.ubuntu.com/ubuntu/pool/main/s/sysvinit/initscripts_2.87dsf-4ubuntu12_i386.deb

For 64 bit ubuntu:
http://archive.ubuntu.com/ubuntu/pool/main/s/sysvinit/initscripts_2.87dsf-4ubuntu12_amd64.deb

Then try to reboot and please report whether it works or not.

Certainly seems to have solved my shutdown issues thanks

The 32-bit package solved my shutdown problems. Thanks

its fixed great work

The solution proposed in #19 worked just fine for me, thank you very much for your help!

If we are to try the proposed package, should we undo the changes we made to the "S40umountfs" file before proceeding or is this not necessary?

Thank you. :-)

What other "OS"'s uses Wubi? Can some one tell me..
Thank You

rhulse12, http://wubi-installer.org/ should answer your questions.

Agostino Russo, after downloading the file on #89, my PC can shut down without a problem. Thank you very much for your help. However, I can only log in thru Failsafe Gnome, but not Gnome. Do you have any idea how to fix it?

Richiegs, we can address the problem with logging into gnome from the bug report that you have already filed. If you can not find your original bug report, go to your launchpad user page to see the list of bug reports that you have contributed to.

thank you very much. Agostino !!

Thanks, Agostino! Post#19 solution works for me, too

Hello Agostino, I too discovered the bug of 9.10 not stopping or restarting properly after a distribution upgrade. I applied your fix (item 19) and, lo and behold, it works flawlessly! As I am an absolute beginner in the Linux realm, I wanted to avoid a clean install for the time being. Thank you very much for your excellent guideline.

Thanks Agostino, I've only just found Launchpad, and within twenty minutes of reading down to #89 I'm impressed - it's fixed.
No more 'hard reset' by removing the battery on my laptop. Thank you.

 #19 do not worked to me... After some shutdowns (three days after I changed /etc/rc6.d/S40umountfs), the problem came back.

Adding information: I use Ubuntu 9.1, Wubi install. Some reboots worked ok, some reboots don't.
    Agostino, I didn't install the package that you informed on #89, cause, I think, the only change was in S40umontfs. Is it right?

Jairo, can you upload your S40umountfs file to this report. It is possible that the update messed something up.

I pasted S40umountfs file content here: http://paste.ubuntu.com/320338/

Jairo, according to the file you pasted, you changed the wrong things, I think. That is why it is not working for you

On line 99, you left the -f option, but removed the -r option. That is incorrect. The -f option should have been removed, and the -r option kept.

Oh, I`m sorry for this mess! I could swear it was OK. Can some program have changed it? Anyway, I`ll try again. Thanx a lot!

I've a 9.1 upgraded from 9.04 installed with Wubi in XP. I'd tried "sudo upgrade-grub" and it works well with reboot but not with shut down. If i try something, it will be #89. It looks more practic to me.

This bug was fixed in the package sysvinit - 2.87dsf-4ubuntu12

---------------
sysvinit (2.87dsf-4ubuntu12) karmic-proposed; urgency=low

  * debian/initscripts/etc/init.d/umountfs: do not use the -f option when
    unmounting WEAK_MTPTS, in the case of bind mounts in particular, that
    results in the underlying device being unmounted, LP: #468589
 -- Agostino Russo <email address hidden> Tue, 03 Nov 2009 23:04:53 +0000

Copied karmic-proposed to lucid.

Thanks to Agostino Russo. I tried his solution (#19) and it worked

#$%&! The bug reproduces itself again after few days, as it had been said. It rebooted well without doing the same with shuting down. Now it is there, as if nothing happens. Updating Grub doesn't work. I'll try the .deb for amd64 of #89. I hope it won't stop my Ubuntu partition.

Ok. I checked karmic-proposed in "Software sources", the i run the Update Manager. I checked the 2.87dfs-4ubuntu12 and installed the package. Nothing happened. My machine still doesn't reboot or shut down. I've to do it manually, pushing the power or reboot button. What should i do?

benditoelqueviene, could you please check your S40umountfs file to see if the appropriate changes were made?

@John Wheelwright

Please don't change bug statuses from Fix Released with talking to the Developer and commenting.

Ok. I attach the file, but shutting down and reboot are just the same.

After a few days, reboot and shutting down start to work fine. I don't know why, but now it closes faster. Thanks! (i guess you'll find the reason...)

Hi, I'm having Wubi Ubuntu 9.04. I got exactly the same symptoms with the problem to shut down, the difference is that my computer runs on Jaunty 9.04. and not Karmic 9.10 upgraded from Jaunty, so i guess the solution given at #19 isn't really the one for me. thanks for any help

Landsman, yes, because you have a different OS, your symptom is not from the same cause. Therefore, it is probably best to file a separate bug report (maybe against Wubi?). Be sure to describe exactly what you are experiencing when shutting down. Also be sure to note your make/model of your computer.

I'm experiencing this bug with a fresh install of 9.10 on a dedicated partition -no Wubi- with other two NTFS partitions.

I fixed the bug after update to 2.6.31.16-generic using the workaround provided here:

https://bugs.launchpad.net/wubi/+bug/468589/comments/19

But after update to 2.6.31.17-generic #54-Ubuntu the bug appears again.

Matteo, because you have a completely different cause than the others in this bug report, please file a separate bug report describing your issue. This bug report is only for those who are experiencing the issue having installed upgraded to 9.10 from 9.04 installed using wubi.

Also, please double-check the file you edited to see if the last update might have undone your changes.

stsitiridis, please do not change the status of a bug report without at least submitting a comment explaining the change in status. I am currently returning this report back to "Fix Released" for Karmic.

I think its worth placing this comment in the hope that anyone looking for an answer might consider this simple GUI solution.

Problem at shutdown failure at deactivating Swap.... Solved on Karmic Ubuntu

After over a month, desperately searching the INTERNET launchpad and wherever the search engines took me. I found the solution for my system. It is so simple I'm surprised none of the experts of the many many forums ever suggested it.

I forced my system off, i restarted to bios and power it off from there, tried to modify scripts and power down using various commands, yet it all failed, the hours & hours wasted. After almost giving up & waiting for the next major update to Lucid Lynx meaning months to shutdown my system properly (silly but well what can i say)

OK to the point.... which really really doesn't make me happy.... because of its simplicity.

I decided to find some shutdown tools in the hope that an advanced tool might help... So I Entered Synaptic Package Manager

Did a search... typed shut (& of course the results had a few tools for shutting down) or you can search initscripts which is my solution

1. I right clicked (sweet no command line)
2. Mark for re-installation (sweet so simple)
3. Apply & let the task complete

4. Reboot / perhaps shutdown & your computer powers off itself (You must love technology that turns off when you tell it to)

As a new user, why of why didn't anyone say i could have reinstalled that, i was thinking how to reinstall shutdown but didn't know the term i needed. I'd be interested to know, does this solve a

Aadil, when you reinstalled initscripts, you obtained the updated version of the initscript. You would have obtained the same result just be performing a system update.

The non-GUI way was from when we were testing the fix and have not released the fix for the update system. Now everyone who performs updates will get the fix.

Hello guys,

I was having this problem from a fresh install of karmik in a laptop along with XP. As rebooting the system and then turning it off from windows was a workaround, I never payed much more attention. But today I wiped the hard disk, did a fresh installation (no XP anymore), and upgrade of all packages - all of this straigh in 9.10 - . And again the same problem. it does restart properly, but it does not shut down. I´ve activated the karmic-proposed repositories, updated the system, and same issue. I tried also editing s40umount removing the -f option.

It´s the first time I´m using launchpad to report a problem, and it is because I haven´t find any other solution. If I can provide you with any information that may help you please let me know (my machine is an acer extensa 3000)

thanks.

Constan, thank you for taking the time to report this issue to help make Ubuntu better. While your symptom is similar, the cause is obviously not the same cause that is addressed here. Therefore, it would be best if you file a new bug against ubuntu to help figure out your issue.

Thanks weathergod, I've created Bug #520706 in case someone want's to take a look...

Please don't change bug status without explanation.