not cleanly unmounting filesystem (root hdd ie sdb1)

[Jappreet]

After clicking shutdown button or giving shutdown command from terminal, the shutdown process finishes abruptly and does not unmounts filesystem cleanly.

This forces a fsck check on every reboot/ switch on.

Disk and RAM are OK.

I dont ve an idea as to wat all log files i can generate and provide u for debugging.

I m running Ubuntu 12.04 beta, on Pentium 4 @ 3.06 Ghz, 1 GB RAM, D102GGC2 mother board.

I ve to boot with boot parameter idle=halt to avoid acpi PWRF button system hang during boot up due to a kernel error.

So i request u to guide me for reqd information. any other information required i ll try to provide u.

Request luk into the problem as continuing like this may damage my HDD.

Thanks

[Jappreet (bains-jappi)]

A copy of the log file kern.log for a shutdown, is pasted below. May b it is of some help:

Mar 6 12:03:34 jappreet-desktop kernel: [ 167.355322] process `skype' is using obsolete setsockopt SO_BSDCOMPAT
Mar 6 14:35:34 jappreet-desktop kernel: [ 9287.176179] unity-2d-shell[1574]: segfault at 151 ip 00000151 sp bff7b66c error 4 in libdconf-qt.so.0.0.0[110000+b000]
Mar 6 14:35:43 jappreet-desktop kernel: [ 9296.700502] init: tty4 main process (1052) killed by TERM signal
Mar 6 14:35:43 jappreet-desktop kernel: [ 9296.703347] init: tty5 main process (1057) killed by TERM signal
Mar 6 14:35:43 jappreet-desktop kernel: [ 9296.704975] init: tty2 main process (1067) killed by TERM signal
Mar 6 14:35:43 jappreet-desktop kernel: [ 9296.706320] init: tty3 main process (1068) killed by TERM signal
Mar 6 14:35:43 jappreet-desktop kernel: [ 9296.707491] init: tty6 main process (1071) killed by TERM signal
Mar 6 14:35:43 jappreet-desktop kernel: [ 9296.708887] init: cron main process (1088) killed by TERM signal
Mar 6 14:35:43 jappreet-desktop kernel: [ 9296.710024] init: tty1 main process (1280) killed by TERM signal
Mar 6 14:35:44 jappreet-desktop kernel: [ 9297.180615] init: plymouth-upstart-bridge main process (4734) terminated with status 1
Mar 6 14:35:44 jappreet-desktop kernel: [ 9297.678411] init: rfkill-store main process (4727) terminated with status 1
Mar 6 14:35:44 jappreet-desktop kernel: [ 9297.679147] init: usplash main process (4744) terminated with status 127
Mar 6 14:35:44 jappreet-desktop kernel: Kernel logging (proc) stopped.

[Jappreet (bains-jappi)]

Reverted back to 11.10, will wait for launch of 12.04...... no problems as usual in 11.10....

[Clint Byrum (clint-fewbar)]

Redirecting to the sysvinit package in Ubuntu since shutdown of Ubuntu is still handled by sysvinit more than upstart.

[Clint Byrum (clint-fewbar)]

Jappreet, sorry we weren't able to get to this while you were still running 12.04.

Did you keep any other artifacts from your system. We've tried pretty hard to eliminate any leftover process problems on shutdown, so anything you can provide to help us reproduce this issue would be helpful. I'm marking this Incomplete since there's not enough here.

One final question, what is the source of this usptart job:

Mar 6 14:35:44 jappreet-desktop kernel: [ 9297.679147] init: usplash main process (4744) terminated with status 127

I cannot find an official upstart job called usplash.

[Jappreet (bains-jappi)]

Thanks Cint for taking time to consider this.

I m sorry to say that right now i dont have any further information with me as i have already formatted the system and reverted back to 11.10, fearing an impending loss of hardware.

Will not b able to give a try again to 12.04 beta, as m a bit busy now for next two to three months.

I also cud not figure out wats the source of that usplash process.

Anyways, thanks once again for ur efforts, may b some other user facing similar probs will b able to throw some more light.

[Steve Langasek (vorlon)]

There was a usplash package present in lucid and maverick that included an upstart job. However, plymouth, which was already a required package in lucid, conflicts with usplash. So it seems this machine must have been continuously upgraded since at least karmic (9.10), and that some cruft was left behind.

If you have reinstalled, you should no longer have /etc/init/upslash.conf on your system. If you do have it, I recommend removing it by hand, since it's not part of Ubuntu 11.10.

Since you say that you have reinstalled, and no one else is reporting this issue with 12.04, this bug report is not actionable. I'm therefore closing it as invalid. If you are able to test again with 12.04 and encounter similar issues, or any issues, please feel free to report such bugs.

[Jappreet (bains-jappi)]

Thanks Steve, I feel u have guessed it correctly, I had continuously upgraded the machine from initially installed 9.10. Hence will definitely give another try to 12.04 shortly.
Regards