subject:"\[arch\-general\] Shutdown and reboot not working after last weekend update"

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-07-01 Thread Victor Silva

2012/6/19 Victor Silva vfbsi...@gmail.com

2012/6/18 Victor Silva vfbsi...@gmail.com

2012/6/16 Victor Silva vfbsi...@gmail.com

2012/6/15 Victor Silva vfbsi...@gmail.com

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 02:48 PM, Victor Silva wrote:

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 08:29 AM, David C. Rankin wrote:

On 06/14/2012 03:12 PM, Victor Silva wrote:

I have no shares. Can I somehow try to umount everything in
mtab? I'm not
familiar with the internal workings of mtab. I will read a bit.
Also the
only thing I assume could be hanging is my external HD which I
disconnected
having no effect on the problem behavior. Still I reported that
my /boot
partition was being mounted and listed on kde file manager
(forgot its
name) which was not default behavior. So could be the case that
/boot is
hanging my shoutdown? I don't get the reason umount -a
shutdown -h now
did not do the trick.

I ask gently again if you could inform me why did the magic
reboot did
work while shutdown did not.

Regards,
Victor

Victor,

I am no expert in the shutdown logic that Arch uses, but it is
fairly
easy to follow. During shutdown, /etc/rc.shutdown is called and
the
'umount_all' command is supposed to take care of unmounting all
non-api
filesystems. If you have specific commands you need run in
_addition to_
what is done by rc.shutdown, then you can put those commands in
/etc/rc.local.shutdown. The /etc/rc.local.shutdown must be
executable to
be called (chmod +x) or (chmod 0755). The rc.local.shutdown file
is
called close to the beginning of rc.shutdown.

Looking at your mtab file and comparing to mine, I do not have
any
usb drives connected to my system. Somebody more familiar with
issues
related to usb drives will need to comment. You might want to try
Guillermo's shutdown modified as follows:

umount -arfl -t usbfs,fuseblk

I don't know if that will do it, but you have 5 fuseblk
filesystems
and 1 usbfs mounted. I don't know how Arch handles their
unmounting.

Lastly, I do not use the gnome gvfs-fuse-daemon. That is another
entry to look at and make sure it isn't the issue. Maybe try your
rc.local.shutdown with:

umount -arfl -t usbfs,fuseblk
killall gvfs-fuse-daemon # or whatever that process actually
runs as

Well just tried reinstalling made no difference. So I guess I
will be
looking it why it is starting that way. It may or may not be
related to the
shutdown issues. But other than this one thing my symptoms seem to
match
this minus the screen turning red when freezing. I will post back
here if I
sort anything out that may help this problem.

I wil try this at home but I'1m at work atm,

https://bugs.archlinux.org/**task/30136https://bugs.archlinux.org/task/30136
ry this kernel paramether reboot=pci
More info:
http://intosimple.blogspot.**com.br/2012/06/reboot-on-dell-**
latitude-e6520-with-arch.htmlhttp://intosimple.blogspot.com.br/2012/06/reboot-on-dell-latitude-e6520-with-arch.html

After reading more into that parameter I found this
http://linux.koolsolutions.**com/2009/08/04/howto-fix-**
linux-hangfreeze-during-**reboots-and-restarts/http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze-during-reboots-and-restarts/

They show more options. I am going to try the one you suggested
shortly and if that does not work do the other suggested option in the
link
I posted. Thanks for pointing out your findings.

A new kernel update was avaliable fo me today. I hoped it could fix
some of the issues we were facing. In fact now I have tons of errors,
dbus
seems screwd and many other things, among the problems I have now is
that X
fails with no screen found (both nv and nvidia drivers) and I have no
network interfaces I fail to get eth0 up. So
*DO NOT UPDATE YOUR KERNELS
*I'm quite sad as this is a even bigger mistake than the last one.
So I think I need to chroot again rever to the old kernel...
Anyone else expecting this kind of problem?
Btw the reboor parameters for the kernel (which I've tested before
the upgrade) also did not work.

Regards,
Victor

I solved many issues still when I try to boot now I get the following
errors:

*Jun 16 13:55:48 localhost kernel: [ 10.463651] microcode: failed
to load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.464913] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.466051] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.467189] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.468305] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.469389] microcode: failed to
load file

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-07-01 Thread Victor Silva

2012/7/1 Victor Silva vfbsi...@gmail.com

2012/6/19 Victor Silva vfbsi...@gmail.com

2012/6/18 Victor Silva vfbsi...@gmail.com

2012/6/16 Victor Silva vfbsi...@gmail.com

2012/6/15 Victor Silva vfbsi...@gmail.com

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 02:48 PM, Victor Silva wrote:

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 08:29 AM, David C. Rankin wrote:

On 06/14/2012 03:12 PM, Victor Silva wrote:

I ask gently again if you could inform me why did the magic
reboot did
work while shutdown did not.

Regards,
Victor

Victor,

umount -arfl -t usbfs,fuseblk

I don't know if that will do it, but you have 5 fuseblk
filesystems
and 1 usbfs mounted. I don't know how Arch handles their
unmounting.

Lastly, I do not use the gnome gvfs-fuse-daemon. That is
another
entry to look at and make sure it isn't the issue. Maybe try your
rc.local.shutdown with:

umount -arfl -t usbfs,fuseblk
killall gvfs-fuse-daemon # or whatever that process actually
runs as

Well just tried reinstalling made no difference. So I guess I
will be
looking it why it is starting that way. It may or may not be
related to the
shutdown issues. But other than this one thing my symptoms seem
to match
this minus the screen turning red when freezing. I will post back
here if I
sort anything out that may help this problem.

I wil try this at home but I'1m at work atm,

They show more options. I am going to try the one you suggested
shortly and if that does not work do the other suggested option in the
link
I posted. Thanks for pointing out your findings.

Regards,
Victor

I solved many issues still when I try to boot now I get the
following errors:

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-19 Thread Victor Silva

2012/6/18 Victor Silva vfbsi...@gmail.com

2012/6/16 Victor Silva vfbsi...@gmail.com

2012/6/15 Victor Silva vfbsi...@gmail.com

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 02:48 PM, Victor Silva wrote:

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 08:29 AM, David C. Rankin wrote:

On 06/14/2012 03:12 PM, Victor Silva wrote:

I have no shares. Can I somehow try to umount everything in mtab?
I'm not
familiar with the internal workings of mtab. I will read a bit.
Also the
only thing I assume could be hanging is my external HD which I
disconnected
having no effect on the problem behavior. Still I reported that
my /boot
partition was being mounted and listed on kde file manager
(forgot its
name) which was not default behavior. So could be the case that
/boot is
hanging my shoutdown? I don't get the reason umount -a
shutdown -h now
did not do the trick.

I ask gently again if you could inform me why did the magic
reboot did
work while shutdown did not.

Regards,
Victor

Victor,

I am no expert in the shutdown logic that Arch uses, but it is
fairly
easy to follow. During shutdown, /etc/rc.shutdown is called and the
'umount_all' command is supposed to take care of unmounting all
non-api
filesystems. If you have specific commands you need run in
_addition to_
what is done by rc.shutdown, then you can put those commands in
/etc/rc.local.shutdown. The /etc/rc.local.shutdown must be
executable to
be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is
called close to the beginning of rc.shutdown.

umount -arfl -t usbfs,fuseblk

I don't know if that will do it, but you have 5 fuseblk
filesystems
and 1 usbfs mounted. I don't know how Arch handles their
unmounting.

Lastly, I do not use the gnome gvfs-fuse-daemon. That is another
entry to look at and make sure it isn't the issue. Maybe try your
rc.local.shutdown with:

umount -arfl -t usbfs,fuseblk
killall gvfs-fuse-daemon # or whatever that process actually runs
as

I wil try this at home but I'1m at work atm,

They show more options. I am going to try the one you suggested
shortly and if that does not work do the other suggested option in the
link
I posted. Thanks for pointing out your findings.

A new kernel update was avaliable fo me today. I hoped it could fix
some of the issues we were facing. In fact now I have tons of errors, dbus
seems screwd and many other things, among the problems I have now is that
X
fails with no screen found (both nv and nvidia drivers) and I have no
network interfaces I fail to get eth0 up. So
*DO NOT UPDATE YOUR KERNELS
*I'm quite sad as this is a even bigger mistake than the last one. So
I think I need to chroot again rever to the old kernel...
Anyone else expecting this kind of problem?
Btw the reboor parameters for the kernel (which I've tested before the
upgrade) also did not work.

Regards,
Victor

I solved many issues still when I try to boot now I get the following
errors:

*Jun 16 13:55:48 localhost kernel: [ 10.463651] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.464913] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.466051] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.467189] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.468305] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.469389] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-18 Thread Victor Silva

2012/6/18 Victor Silva vfbsi...@gmail.com

2012/6/16 Victor Silva vfbsi...@gmail.com

2012/6/15 Victor Silva vfbsi...@gmail.com

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 02:48 PM, Victor Silva wrote:

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 08:29 AM, David C. Rankin wrote:

On 06/14/2012 03:12 PM, Victor Silva wrote:

I have no shares. Can I somehow try to umount everything in mtab?
I'm not
familiar with the internal workings of mtab. I will read a bit.
Also the
only thing I assume could be hanging is my external HD which I
disconnected
having no effect on the problem behavior. Still I reported that my
/boot
partition was being mounted and listed on kde file manager (forgot
its
name) which was not default behavior. So could be the case that
/boot is
hanging my shoutdown? I don't get the reason umount -a shutdown
-h now
did not do the trick.

I ask gently again if you could inform me why did the magic
reboot did
work while shutdown did not.

Regards,
Victor

Victor,

I am no expert in the shutdown logic that Arch uses, but it is
fairly
easy to follow. During shutdown, /etc/rc.shutdown is called and the
'umount_all' command is supposed to take care of unmounting all
non-api
filesystems. If you have specific commands you need run in
_addition to_
what is done by rc.shutdown, then you can put those commands in
/etc/rc.local.shutdown. The /etc/rc.local.shutdown must be
executable to
be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is
called close to the beginning of rc.shutdown.

Looking at your mtab file and comparing to mine, I do not have any
usb drives connected to my system. Somebody more familiar with
issues
related to usb drives will need to comment. You might want to try
Guillermo's shutdown modified as follows:

umount -arfl -t usbfs,fuseblk

I don't know if that will do it, but you have 5 fuseblk
filesystems
and 1 usbfs mounted. I don't know how Arch handles their unmounting.

Lastly, I do not use the gnome gvfs-fuse-daemon. That is another
entry to look at and make sure it isn't the issue. Maybe try your
rc.local.shutdown with:

umount -arfl -t usbfs,fuseblk
killall gvfs-fuse-daemon # or whatever that process actually runs
as

Well just tried reinstalling made no difference. So I guess I will
be
looking it why it is starting that way. It may or may not be related
to the
shutdown issues. But other than this one thing my symptoms seem to
match
this minus the screen turning red when freezing. I will post back
here if I
sort anything out that may help this problem.

I wil try this at home but I'1m at work atm,

They show more options. I am going to try the one you suggested
shortly and if that does not work do the other suggested option in the
link
I posted. Thanks for pointing out your findings.

A new kernel update was avaliable fo me today. I hoped it could fix
some of the issues we were facing. In fact now I have tons of errors, dbus
seems screwd and many other things, among the problems I have now is that X
fails with no screen found (both nv and nvidia drivers) and I have no
network interfaces I fail to get eth0 up. So
*DO NOT UPDATE YOUR KERNELS
*I'm quite sad as this is a even bigger mistake than the last one. So
I think I need to chroot again rever to the old kernel...
Anyone else expecting this kind of problem?
Btw the reboor parameters for the kernel (which I've tested before the
upgrade) also did not work.

Regards,
Victor

I solved many issues still when I try to boot now I get the following
errors:

*Jun 16 13:55:48 localhost kernel: [ 10.463651] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.464913] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.466051] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.467189] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.468305] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.469389] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 11.920779] sd 6:0:0:0: [sdc] No
Caching mode

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-17 Thread Victor Silva

2012/6/16 Victor Silva vfbsi...@gmail.com

2012/6/15 Victor Silva vfbsi...@gmail.com

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 02:48 PM, Victor Silva wrote:

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 08:29 AM, David C. Rankin wrote:

On 06/14/2012 03:12 PM, Victor Silva wrote:

I have no shares. Can I somehow try to umount everything in mtab?
I'm not
familiar with the internal workings of mtab. I will read a bit.
Also the
only thing I assume could be hanging is my external HD which I
disconnected
having no effect on the problem behavior. Still I reported that my
/boot
partition was being mounted and listed on kde file manager (forgot
its
name) which was not default behavior. So could be the case that
/boot is
hanging my shoutdown? I don't get the reason umount -a shutdown
-h now
did not do the trick.

I ask gently again if you could inform me why did the magic
reboot did
work while shutdown did not.

Regards,
Victor

Victor,

I am no expert in the shutdown logic that Arch uses, but it is
fairly
easy to follow. During shutdown, /etc/rc.shutdown is called and the
'umount_all' command is supposed to take care of unmounting all
non-api
filesystems. If you have specific commands you need run in _addition
to_
what is done by rc.shutdown, then you can put those commands in
/etc/rc.local.shutdown. The /etc/rc.local.shutdown must be
executable to
be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is
called close to the beginning of rc.shutdown.

Looking at your mtab file and comparing to mine, I do not have any
usb drives connected to my system. Somebody more familiar with issues
related to usb drives will need to comment. You might want to try
Guillermo's shutdown modified as follows:

umount -arfl -t usbfs,fuseblk

I don't know if that will do it, but you have 5 fuseblk filesystems
and 1 usbfs mounted. I don't know how Arch handles their unmounting.

Lastly, I do not use the gnome gvfs-fuse-daemon. That is another
entry to look at and make sure it isn't the issue. Maybe try your
rc.local.shutdown with:

umount -arfl -t usbfs,fuseblk
killall gvfs-fuse-daemon # or whatever that process actually runs as

Well just tried reinstalling made no difference. So I guess I will
be
looking it why it is starting that way. It may or may not be related
to the
shutdown issues. But other than this one thing my symptoms seem to
match
this minus the screen turning red when freezing. I will post back
here if I
sort anything out that may help this problem.

I wil try this at home but I'1m at work atm,

They show more options. I am going to try the one you suggested shortly
and if that does not work do the other suggested option in the link I
posted. Thanks for pointing out your findings.

A new kernel update was avaliable fo me today. I hoped it could fix
some of the issues we were facing. In fact now I have tons of errors, dbus
seems screwd and many other things, among the problems I have now is that X
fails with no screen found (both nv and nvidia drivers) and I have no
network interfaces I fail to get eth0 up. So
*DO NOT UPDATE YOUR KERNELS
*I'm quite sad as this is a even bigger mistake than the last one. So I
think I need to chroot again rever to the old kernel...
Anyone else expecting this kind of problem?
Btw the reboor parameters for the kernel (which I've tested before the
upgrade) also did not work.

Regards,
Victor

I solved many issues still when I try to boot now I get the following
errors:

*Jun 16 13:55:48 localhost kernel: [ 10.463651] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.464913] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.466051] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.467189] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.468305] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.469389] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 11.920779] sd 6:0:0:0: [sdc] No
Caching mode page present
Jun 16 13:55:48 localhost kernel: [

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-16 Thread Victor Silva

2012/6/15 Victor Silva vfbsi...@gmail.com

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 02:48 PM, Victor Silva wrote:

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 08:29 AM, David C. Rankin wrote:

On 06/14/2012 03:12 PM, Victor Silva wrote:

I have no shares. Can I somehow try to umount everything in mtab? I'm
not
familiar with the internal workings of mtab. I will read a bit. Also
the
only thing I assume could be hanging is my external HD which I
disconnected
having no effect on the problem behavior. Still I reported that my
/boot
partition was being mounted and listed on kde file manager (forgot its
name) which was not default behavior. So could be the case that /boot
is
hanging my shoutdown? I don't get the reason umount -a shutdown -h
now
did not do the trick.

I ask gently again if you could inform me why did the magic reboot
did
work while shutdown did not.

Regards,
Victor

Victor,

I am no expert in the shutdown logic that Arch uses, but it is fairly
easy to follow. During shutdown, /etc/rc.shutdown is called and the
'umount_all' command is supposed to take care of unmounting all non-api
filesystems. If you have specific commands you need run in _addition
to_
what is done by rc.shutdown, then you can put those commands in
/etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable
to
be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is
called close to the beginning of rc.shutdown.

Looking at your mtab file and comparing to mine, I do not have any
usb drives connected to my system. Somebody more familiar with issues
related to usb drives will need to comment. You might want to try
Guillermo's shutdown modified as follows:

umount -arfl -t usbfs,fuseblk

I don't know if that will do it, but you have 5 fuseblk filesystems
and 1 usbfs mounted. I don't know how Arch handles their unmounting.

Lastly, I do not use the gnome gvfs-fuse-daemon. That is another
entry to look at and make sure it isn't the issue. Maybe try your
rc.local.shutdown with:

umount -arfl -t usbfs,fuseblk
killall gvfs-fuse-daemon # or whatever that process actually runs as

Well just tried reinstalling made no difference. So I guess I will be
looking it why it is starting that way. It may or may not be related to
the
shutdown issues. But other than this one thing my symptoms seem to match
this minus the screen turning red when freezing. I will post back here
if I
sort anything out that may help this problem.

I wil try this at home but I'1m at work atm,

They show more options. I am going to try the one you suggested shortly
and if that does not work do the other suggested option in the link I
posted. Thanks for pointing out your findings.

A new kernel update was avaliable fo me today. I hoped it could fix some
of the issues we were facing. In fact now I have tons of errors, dbus seems
screwd and many other things, among the problems I have now is that X fails
with no screen found (both nv and nvidia drivers) and I have no network
interfaces I fail to get eth0 up. So
*DO NOT UPDATE YOUR KERNELS
*I'm quite sad as this is a even bigger mistake than the last one. So I
think I need to chroot again rever to the old kernel...
Anyone else expecting this kind of problem?
Btw the reboor parameters for the kernel (which I've tested before the
upgrade) also did not work.

Regards,
Victor

I solved many issues still when I try to boot now I get the following
errors:

*Jun 16 13:55:48 localhost kernel: [ 10.463651] microcode: failed to load
file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.464913] microcode: failed to load
file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.466051] microcode: failed to load
file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.467189] microcode: failed to load
file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.468305] microcode: failed to load
file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.469389] microcode: failed to load
file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 11.920779] sd 6:0:0:0: [sdc] No
Caching mode page present
Jun 16 13:55:48 localhost kernel: [ 11.920880] sd 6:0:0:0: [sdc] Assuming
drive cache: write through
Jun 16 13:55:48 localhost kernel: [

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-16 Thread Victor Silva

2012/6/16 Victor Silva vfbsi...@gmail.com

2012/6/15 Victor Silva vfbsi...@gmail.com

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 02:48 PM, Victor Silva wrote:

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 08:29 AM, David C. Rankin wrote:

On 06/14/2012 03:12 PM, Victor Silva wrote:

I have no shares. Can I somehow try to umount everything in mtab?
I'm not
familiar with the internal workings of mtab. I will read a bit. Also
the
only thing I assume could be hanging is my external HD which I
disconnected
having no effect on the problem behavior. Still I reported that my
/boot
partition was being mounted and listed on kde file manager (forgot
its
name) which was not default behavior. So could be the case that
/boot is
hanging my shoutdown? I don't get the reason umount -a shutdown
-h now
did not do the trick.

I ask gently again if you could inform me why did the magic reboot
did
work while shutdown did not.

Regards,
Victor

Victor,

I am no expert in the shutdown logic that Arch uses, but it is
fairly
easy to follow. During shutdown, /etc/rc.shutdown is called and the
'umount_all' command is supposed to take care of unmounting all
non-api
filesystems. If you have specific commands you need run in _addition
to_
what is done by rc.shutdown, then you can put those commands in
/etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable
to
be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is
called close to the beginning of rc.shutdown.

Looking at your mtab file and comparing to mine, I do not have any
usb drives connected to my system. Somebody more familiar with issues
related to usb drives will need to comment. You might want to try
Guillermo's shutdown modified as follows:

umount -arfl -t usbfs,fuseblk

I don't know if that will do it, but you have 5 fuseblk filesystems
and 1 usbfs mounted. I don't know how Arch handles their unmounting.

Lastly, I do not use the gnome gvfs-fuse-daemon. That is another
entry to look at and make sure it isn't the issue. Maybe try your
rc.local.shutdown with:

umount -arfl -t usbfs,fuseblk
killall gvfs-fuse-daemon # or whatever that process actually runs as

Well just tried reinstalling made no difference. So I guess I will be
looking it why it is starting that way. It may or may not be related
to the
shutdown issues. But other than this one thing my symptoms seem to
match
this minus the screen turning red when freezing. I will post back here
if I
sort anything out that may help this problem.

I wil try this at home but I'1m at work atm,

They show more options. I am going to try the one you suggested shortly
and if that does not work do the other suggested option in the link I
posted. Thanks for pointing out your findings.

A new kernel update was avaliable fo me today. I hoped it could fix some
of the issues we were facing. In fact now I have tons of errors, dbus seems
screwd and many other things, among the problems I have now is that X fails
with no screen found (both nv and nvidia drivers) and I have no network
interfaces I fail to get eth0 up. So
*DO NOT UPDATE YOUR KERNELS
*I'm quite sad as this is a even bigger mistake than the last one. So I
think I need to chroot again rever to the old kernel...
Anyone else expecting this kind of problem?
Btw the reboor parameters for the kernel (which I've tested before the
upgrade) also did not work.

Regards,
Victor

I solved many issues still when I try to boot now I get the following
errors:

*Jun 16 13:55:48 localhost kernel: [ 10.463651] microcode: failed to
load file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.464913] microcode: failed to load
file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.466051] microcode: failed to load
file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.467189] microcode: failed to load
file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.468305] microcode: failed to load
file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 10.469389] microcode: failed to load
file amd-ucode/microcode_amd.bin
Jun 16 13:55:48 localhost kernel: [ 11.920779] sd 6:0:0:0: [sdc] No
Caching mode page present
Jun 16 13:55:48 localhost kernel: [ 11.920880] sd 6:0:0:0: [sdc]
Assuming drive

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-15 Thread Ralf Mardorf

On Thu, 2012-06-14 at 11:37 -0300, Victor Silva wrote:
 Also, is there a procedure I can use to have multiple kernels?

Don't name the packages/kernels linux. Name them linux, linux-1,
linux-2 etc.?!

You also could get different kernels from the repositories, of course
not different versions of linux, but e.g. linux + linux-rt.

$ ls /mnt/archlinux/boot/vmlinuz*
/mnt/archlinux/boot/vmlinuz-linux  /mnt/archlinux/boot/vmlinuz-linux-rt

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-15 Thread Victor Silva

2012/6/15 Ralf Mardorf ralf.mard...@alice-dsl.net

 On Thu, 2012-06-14 at 11:37 -0300, Victor Silva wrote:
  Also, is there a procedure I can use to have multiple kernels?

 Don't name the packages/kernels linux. Name them linux, linux-1,
 linux-2 etc.?!

 You also could get different kernels from the repositories, of course
 not different versions of linux, but e.g. linux + linux-rt.

 $ ls /mnt/archlinux/boot/vmlinuz*
 /mnt/archlinux/boot/vmlinuz-linux  /mnt/archlinux/boot/vmlinuz-linux-rt

 Oki. I will try it on the weekend. There seems to be an official bug now:
https://bugs.archlinux.org/task/30136

I will provide them the link of our discussion.

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-15 Thread David C. Rankin


On 06/14/2012 03:12 PM, Victor Silva wrote:

I have no shares. Can I somehow try to umount everything in mtab? I'm not
familiar with the internal workings of mtab. I will read a bit. Also the
only thing I assume could be hanging is my external HD which I disconnected
having no effect on the problem behavior. Still I reported that my /boot
partition was being mounted and listed on kde file manager (forgot its
name) which was not default behavior. So could be the case that /boot is
hanging my shoutdown? I don't get the reason umount -a  shutdown -h now
did not do the trick.

I ask gently again if you could inform me why did the magic reboot did
work while shutdown did not.

Regards,
Victor


Victor,

  I am no expert in the shutdown logic that Arch uses, but it is fairly easy 
to follow. During shutdown, /etc/rc.shutdown is called and the 'umount_all' 
command is supposed to take care of unmounting all non-api filesystems. If you 
have specific commands you need run in _addition to_ what is done by 
rc.shutdown, then you can put those commands in /etc/rc.local.shutdown. The 
/etc/rc.local.shutdown must be executable to be called (chmod +x) or (chmod 
0755). The rc.local.shutdown file is called close to the beginning of rc.shutdown.


  Looking at your mtab file and comparing to mine, I do not have any usb 
drives connected to my system. Somebody more familiar with issues related to 
usb drives will need to comment. You might want to try Guillermo's shutdown 
modified as follows:


umount -arfl -t usbfs,fuseblk

  I don't know if that will do it, but you have 5 fuseblk filesystems and 1 
usbfs mounted. I don't know how Arch handles their unmounting.


  Lastly, I do not use the gnome gvfs-fuse-daemon. That is another entry to 
look at and make sure it isn't the issue. Maybe try your rc.local.shutdown with:


umount -arfl -t usbfs,fuseblk
killall gvfs-fuse-daemon  # or whatever that process actually runs as


--
David C. Rankin, J.D.,P.E.

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-15 Thread Don deJuan


On 06/15/2012 08:29 AM, David C. Rankin wrote:

On 06/14/2012 03:12 PM, Victor Silva wrote:

I have no shares. Can I somehow try to umount everything in mtab? I'm not
familiar with the internal workings of mtab. I will read a bit. Also the
only thing I assume could be hanging is my external HD which I
disconnected
having no effect on the problem behavior. Still I reported that my /boot
partition was being mounted and listed on kde file manager (forgot its
name) which was not default behavior. So could be the case that /boot is
hanging my shoutdown? I don't get the reason umount -a  shutdown -h now
did not do the trick.

I ask gently again if you could inform me why did the magic reboot did
work while shutdown did not.

Regards,
Victor


Victor,

   I am no expert in the shutdown logic that Arch uses, but it is fairly
easy to follow. During shutdown, /etc/rc.shutdown is called and the
'umount_all' command is supposed to take care of unmounting all non-api
filesystems. If you have specific commands you need run in _addition to_
what is done by rc.shutdown, then you can put those commands in
/etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable to
be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is
called close to the beginning of rc.shutdown.

   Looking at your mtab file and comparing to mine, I do not have any
usb drives connected to my system. Somebody more familiar with issues
related to usb drives will need to comment. You might want to try
Guillermo's shutdown modified as follows:

umount -arfl -t usbfs,fuseblk

   I don't know if that will do it, but you have 5 fuseblk filesystems
and 1 usbfs mounted. I don't know how Arch handles their unmounting.

   Lastly, I do not use the gnome gvfs-fuse-daemon. That is another
entry to look at and make sure it isn't the issue. Maybe try your
rc.local.shutdown with:

umount -arfl -t usbfs,fuseblk
killall gvfs-fuse-daemon  # or whatever that process actually runs as




While reading through this to see how much it relates to my shutdown 
issues, I have noticed this.


With gvfs-fuse-daemon install I noticed in top it is being run with what 
I would think is an incorrect command.

/usr/lib/gvfs//gvfs-fuse-daemon -f /home/user/.gvfs
The double slash is not a typo on my part that is how it is listed.

Do you see the same results when seeing how the gvfs daemon is being run 
on the system? I am going to try reinstalling it and seeing if it will 
install properly and not be run with the double slash. Have not noticed 
this until today.

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-15 Thread Don deJuan


On 06/15/2012 08:29 AM, David C. Rankin wrote:

On 06/14/2012 03:12 PM, Victor Silva wrote:

I have no shares. Can I somehow try to umount everything in mtab? I'm not
familiar with the internal workings of mtab. I will read a bit. Also the
only thing I assume could be hanging is my external HD which I
disconnected
having no effect on the problem behavior. Still I reported that my /boot
partition was being mounted and listed on kde file manager (forgot its
name) which was not default behavior. So could be the case that /boot is
hanging my shoutdown? I don't get the reason umount -a  shutdown -h now
did not do the trick.

I ask gently again if you could inform me why did the magic reboot did
work while shutdown did not.

Regards,
Victor


Victor,

   I am no expert in the shutdown logic that Arch uses, but it is fairly
easy to follow. During shutdown, /etc/rc.shutdown is called and the
'umount_all' command is supposed to take care of unmounting all non-api
filesystems. If you have specific commands you need run in _addition to_
what is done by rc.shutdown, then you can put those commands in
/etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable to
be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is
called close to the beginning of rc.shutdown.

   Looking at your mtab file and comparing to mine, I do not have any
usb drives connected to my system. Somebody more familiar with issues
related to usb drives will need to comment. You might want to try
Guillermo's shutdown modified as follows:

umount -arfl -t usbfs,fuseblk

   I don't know if that will do it, but you have 5 fuseblk filesystems
and 1 usbfs mounted. I don't know how Arch handles their unmounting.

   Lastly, I do not use the gnome gvfs-fuse-daemon. That is another
entry to look at and make sure it isn't the issue. Maybe try your
rc.local.shutdown with:

umount -arfl -t usbfs,fuseblk
killall gvfs-fuse-daemon  # or whatever that process actually runs as




Well just tried reinstalling made no difference. So I guess I will be 
looking it why it is starting that way. It may or may not be related to 
the shutdown issues. But other than this one thing my symptoms seem to 
match this minus the screen turning red when freezing. I will post back 
here if I sort anything out that may help this problem.

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-15 Thread Victor Silva

2012/6/15 Don deJuan donjuans...@gmail.com

 On 06/15/2012 08:29 AM, David C. Rankin wrote:

 On 06/14/2012 03:12 PM, Victor Silva wrote:

 I have no shares. Can I somehow try to umount everything in mtab? I'm not
 familiar with the internal workings of mtab. I will read a bit. Also the
 only thing I assume could be hanging is my external HD which I
 disconnected
 having no effect on the problem behavior. Still I reported that my /boot
 partition was being mounted and listed on kde file manager (forgot its
 name) which was not default behavior. So could be the case that /boot is
 hanging my shoutdown? I don't get the reason umount -a  shutdown -h now
 did not do the trick.

 I ask gently again if you could inform me why did the magic reboot did
 work while shutdown did not.

 Regards,
 Victor


 Victor,

   I am no expert in the shutdown logic that Arch uses, but it is fairly
 easy to follow. During shutdown, /etc/rc.shutdown is called and the
 'umount_all' command is supposed to take care of unmounting all non-api
 filesystems. If you have specific commands you need run in _addition to_
 what is done by rc.shutdown, then you can put those commands in
 /etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable to
 be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is
 called close to the beginning of rc.shutdown.

   Looking at your mtab file and comparing to mine, I do not have any
 usb drives connected to my system. Somebody more familiar with issues
 related to usb drives will need to comment. You might want to try
 Guillermo's shutdown modified as follows:

 umount -arfl -t usbfs,fuseblk

   I don't know if that will do it, but you have 5 fuseblk filesystems
 and 1 usbfs mounted. I don't know how Arch handles their unmounting.

   Lastly, I do not use the gnome gvfs-fuse-daemon. That is another
 entry to look at and make sure it isn't the issue. Maybe try your
 rc.local.shutdown with:

 umount -arfl -t usbfs,fuseblk
 killall gvfs-fuse-daemon  # or whatever that process actually runs as



 Well just tried reinstalling made no difference. So I guess I will be
 looking it why it is starting that way. It may or may not be related to the
 shutdown issues. But other than this one thing my symptoms seem to match
 this minus the screen turning red when freezing. I will post back here if I
 sort anything out that may help this problem.

 I wil try this at home but I'1m at work atm,
https://bugs.archlinux.org/task/30136
ry this kernel paramether reboot=pci
More info:
http://intosimple.blogspot.com.br/2012/06/reboot-on-dell-latitude-e6520-with-arch.html

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-15 Thread Don deJuan

On 06/15/2012 02:48 PM, Victor Silva wrote:

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 08:29 AM, David C. Rankin wrote:

On 06/14/2012 03:12 PM, Victor Silva wrote:

I have no shares. Can I somehow try to umount everything in mtab? I'm not
familiar with the internal workings of mtab. I will read a bit. Also the
only thing I assume could be hanging is my external HD which I
disconnected
having no effect on the problem behavior. Still I reported that my /boot
partition was being mounted and listed on kde file manager (forgot its
name) which was not default behavior. So could be the case that /boot is
hanging my shoutdown? I don't get the reason umount -a shutdown -h now
did not do the trick.

I ask gently again if you could inform me why did the magic reboot did
work while shutdown did not.

Regards,
Victor

Victor,

I am no expert in the shutdown logic that Arch uses, but it is fairly
easy to follow. During shutdown, /etc/rc.shutdown is called and the
'umount_all' command is supposed to take care of unmounting all non-api
filesystems. If you have specific commands you need run in _addition to_
what is done by rc.shutdown, then you can put those commands in
/etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable to
be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is
called close to the beginning of rc.shutdown.

Looking at your mtab file and comparing to mine, I do not have any
usb drives connected to my system. Somebody more familiar with issues
related to usb drives will need to comment. You might want to try
Guillermo's shutdown modified as follows:

umount -arfl -t usbfs,fuseblk

I don't know if that will do it, but you have 5 fuseblk filesystems
and 1 usbfs mounted. I don't know how Arch handles their unmounting.

Lastly, I do not use the gnome gvfs-fuse-daemon. That is another
entry to look at and make sure it isn't the issue. Maybe try your
rc.local.shutdown with:

umount -arfl -t usbfs,fuseblk
killall gvfs-fuse-daemon # or whatever that process actually runs as

Well just tried reinstalling made no difference. So I guess I will be
looking it why it is starting that way. It may or may not be related to the
shutdown issues. But other than this one thing my symptoms seem to match
this minus the screen turning red when freezing. I will post back here if I
sort anything out that may help this problem.

I wil try this at home but I'1m at work atm,

https://bugs.archlinux.org/task/30136
ry this kernel paramether reboot=pci
More info:
http://intosimple.blogspot.com.br/2012/06/reboot-on-dell-latitude-e6520-with-arch.html

After reading more into that parameter I found this
http://linux.koolsolutions.com/2009/08/04/howto-fix-linux-hangfreeze-during-reboots-and-restarts/

They show more options. I am going to try the one you suggested shortly
and if that does not work do the other suggested option in the link I
posted. Thanks for pointing out your findings.

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-15 Thread Victor Silva

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 02:48 PM, Victor Silva wrote:

2012/6/15 Don deJuan donjuans...@gmail.com

On 06/15/2012 08:29 AM, David C. Rankin wrote:

On 06/14/2012 03:12 PM, Victor Silva wrote:

I have no shares. Can I somehow try to umount everything in mtab? I'm
not
familiar with the internal workings of mtab. I will read a bit. Also
the
only thing I assume could be hanging is my external HD which I
disconnected
having no effect on the problem behavior. Still I reported that my
/boot
partition was being mounted and listed on kde file manager (forgot its
name) which was not default behavior. So could be the case that /boot
is
hanging my shoutdown? I don't get the reason umount -a shutdown -h
now
did not do the trick.

I ask gently again if you could inform me why did the magic reboot
did
work while shutdown did not.

Regards,
Victor

Victor,

I am no expert in the shutdown logic that Arch uses, but it is fairly
easy to follow. During shutdown, /etc/rc.shutdown is called and the
'umount_all' command is supposed to take care of unmounting all non-api
filesystems. If you have specific commands you need run in _addition to_
what is done by rc.shutdown, then you can put those commands in
/etc/rc.local.shutdown. The /etc/rc.local.shutdown must be executable to
be called (chmod +x) or (chmod 0755). The rc.local.shutdown file is
called close to the beginning of rc.shutdown.

Looking at your mtab file and comparing to mine, I do not have any
usb drives connected to my system. Somebody more familiar with issues
related to usb drives will need to comment. You might want to try
Guillermo's shutdown modified as follows:

umount -arfl -t usbfs,fuseblk

I don't know if that will do it, but you have 5 fuseblk filesystems
and 1 usbfs mounted. I don't know how Arch handles their unmounting.

Lastly, I do not use the gnome gvfs-fuse-daemon. That is another
entry to look at and make sure it isn't the issue. Maybe try your
rc.local.shutdown with:

umount -arfl -t usbfs,fuseblk
killall gvfs-fuse-daemon # or whatever that process actually runs as

Well just tried reinstalling made no difference. So I guess I will be
looking it why it is starting that way. It may or may not be related to
the
shutdown issues. But other than this one thing my symptoms seem to match
this minus the screen turning red when freezing. I will post back here
if I
sort anything out that may help this problem.

I wil try this at home but I'1m at work atm,

They show more options. I am going to try the one you suggested shortly
and if that does not work do the other suggested option in the link I
posted. Thanks for pointing out your findings.

A new kernel update was avaliable fo me today. I hoped it could fix some
of the issues we were facing. In fact now I have tons of errors, dbus seems
screwd and many other things, among the problems I have now is that X fails
with no screen found (both nv and nvidia drivers) and I have no network
interfaces I fail to get eth0 up. So
*DO NOT UPDATE YOUR KERNELS
*I'm quite sad as this is a even bigger mistake than the last one. So I
think I need to chroot again rever to the old kernel...
Anyone else expecting this kind of problem?
Btw the reboor parameters for the kernel (which I've tested before the
upgrade) also did not work.

Regards,
Victor

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-14 Thread gt

On Thu, Jun 14, 2012 at 12:18:17AM -0300, Victor Silva wrote:
 2012/6/14 gt static.vor...@gmx.com
  Since you have already reverted to the old kernel, you don't further
  need to downgrade it, as you have already downgraded it.
 
  (Assuming, you did a pacman -U old-kernel)
 
 I did it for the kenel which hangs, the one before it does not boot as
 described on the previous posts. So somehow I need to find the last working
 configuration. Also is shutdown -F a dangerous practice? Cause this works
 for me.

from the man page, -F switch forces a fsck on reboot. So, i don't think
it is dangerous.

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-14 Thread Victor Silva

2012/6/14 gt static.vor...@gmx.com

 On Thu, Jun 14, 2012 at 12:18:17AM -0300, Victor Silva wrote:
  2012/6/14 gt static.vor...@gmx.com
   Since you have already reverted to the old kernel, you don't further
   need to downgrade it, as you have already downgraded it.
  
   (Assuming, you did a pacman -U old-kernel)
  
  I did it for the kenel which hangs, the one before it does not boot as
  described on the previous posts. So somehow I need to find the last
 working
  configuration. Also is shutdown -F a dangerous practice? Cause this works
  for me.

 from the man page, -F switch forces a fsck on reboot. So, i don't think
 it is dangerous.



Folks my kernel downgrade did not work, I'm clueless. It reports a problem
reading /boot partition saying something about it being not a valid ext2
partition. I need to take a picture of that as it hangs before init 1 so I
have no logs.  I was able to chroot and revert to 3.3.8-1 kernel. Also, is
there a procedure I can use to have multiple kernels? Well of course it is,
better question is wheter https://wiki.archlinux.org/index.php/Ke …
ild_Systemhttps://wiki.archlinux.org/index.php/Kernels/Compilation/Arch_Build_Systemis
the best approach to do so. I still clueless about what is the
problem.

I will try to build my kernel again and see what happens. By the way so far
I've used only vanilla kernels.

Regards,
Victor

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-14 Thread Kevin Chadwick

 It reports a problem
 reading /boot partition saying something about it being not a valid ext2

I see /boot is ext4

There was a time recently when a kernel bug gave invalid warnings about
other filesystem types like ext2, ext3 before mounting ext4 so it could
be a red herring, is the exact error gone too quick to note.

I presume by Vanilla you mean an arch package?


p.s. If you can edit the kernel commandline you can change the init part to

init=/bin/sh and hitting b to boot

It's limited in what can be done but that way you may be
able to troubleshoot some things more quickly by using the built in
kernel commands, see if there is a reboot command. If there is it is
internal and not from any filesystem. If it works you could then do it
again and this time mount your root filesystem and try the reboot
command from that.

There are also kernel debug configs like printk but I'm not sure that's
the route to go down yet.



 Why not do something good every day and install BOINC.

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-14 Thread Victor Silva

2012/6/14 Kevin Chadwick ma1l1i...@yahoo.co.uk

  It reports a problem
  reading /boot partition saying something about it being not a valid ext2

 I see /boot is ext4

 There was a time recently when a kernel bug gave invalid warnings about
 other filesystem types like ext2, ext3 before mounting ext4 so it could
 be a red herring, is the exact error gone too quick to note.

 I presume by Vanilla you mean an arch package?


 p.s. If you can edit the kernel commandline you can change the init part to

 init=/bin/sh and hitting b to boot

 It's limited in what can be done but that way you may be
 able to troubleshoot some things more quickly by using the built in
 kernel commands, see if there is a reboot command. If there is it is
 internal and not from any filesystem. If it works you could then do it
 again and this time mount your root filesystem and try the reboot
 command from that.

 There are also kernel debug configs like printk but I'm not sure that's
 the route to go down yet.

 

  Why not do something good every day and install BOINC.
 


Yeah by vanilla I mean the stock kernel. I dont get what do you mean by:
be a red herring, is the exact error gone too quick to note.


Well I can chroot as I did to revert to the old kernel so changing grub
menu seems harder than chroot. My main problem is that reverting to the old
kernel did not work.

Maybe I forgot to run mkinitcpio

By did not work I mean that I don't get boot. it fails with the message you
meantioned to be listed on a bug. I will look for it later but if you could
provide me a link I would be gratefull (I'm at work atm). Also I own you a
post of the exact error message on boot over the new kernel.  A thing I
dont understand is what if the difference of doing a magic reboot:
http://www.linuxjournal.com/content/rebooting-magic-way
and calling a shutdown lies mainly on the umounting of the file systems if
this is the case I should be able to reboot after a umount -f all right?

I wonder if a -l would be better:
-l Lazy unmount. Detach the filesystem from the filesystem  hierarchy
now, and cleanup all references to the filesystem as soon as it is not busy
anymore.  (Requires kernel 2.4.11 or later.)
I could not run fsck on /boot as it reported to be mounted.

Should I maybe run a normal shutdown -h now in parallel with
http://www.mjmwired.net/kernel/Documentation/sysrq.txt
to check which tasks are still stuck right?

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-14 Thread Kevin Chadwick

 Yeah by vanilla I mean the stock kernel. I dont get what do you mean by:
 be a red herring, is the exact error gone too quick to note.
 

red herring as in possibly false or irrelevent error message.

is the exact error gone too quick to note.

Does it flash up before you can get a picture or write down the error
message.

 
 Well I can chroot as I did to revert to the old kernel so changing grub
 menu seems harder than chroot. My main problem is that reverting to the old
 kernel did not work.

when the grub menu comes up

hit the e key
move down a line
hit e key again
change init=/dev/?? to init=/bin/sh
hit b key




 Why not do something good every day and install BOINC.

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-14 Thread David C. Rankin


On 06/12/2012 02:06 PM, Victor Silva wrote:

Folks sorry for cross posting this at forum and mailing lists but so far no
solution came there.

Folks after the last upgrade I can no longer shutdown nor reboot my machine
(I'm using it as root). The command simply hangs and nothing happens. I've
done some research and found
https://bbs.archlinux.org/viewtopic.php?id=141155  this but that does not
seems to be my issue. I'm clueless which logs can I provide you in order to
diagnose what can be the problem? Important thing, I have only 1 session
running and the system report going down still it never  gets past the tty
broadcast as it seems.

Ideas?


I had a similar problem that began several months ago with my box hanging on 
shutdown or reboot. This problem was related to samba shares not being 
unmounted. To get around the problem a created an entry in 
'/etc/rc.local.shutdown' to call a script to unmount the drives. This solved 
the problem. The script I call simply checks whether there is still an entry 
in /etc/mtab for the share and if so, manually unmounts the share:


[[ $UID -eq 0 ]]  umountcmd=umount || umountcmd=sudo umount

if grep -q mnt\/phx-cfg /etc/mtab; then
  echo umount /mnt/phx-cfg
  $umountcmd /mnt/phx-cfg
fi

if grep -q mnt\/phx-david /etc/mtab; then
  echo umount /mnt/phx-david
  $umountcmd /mnt/phx-david
fi

if grep -q mnt\/phx /etc/mtab; then
  echo umount /mnt/phx
  $umountcmd /mnt/phx
fi

if grep -q mnt\/win /etc/mtab; then
  echo umount /mnt/win
  $umountcmd /mnt/win
fi

if grep -q mnt\/pv /etc/mtab; then
  echo umount /mnt/pv
  $umountcmd /mnt/pv
fi

exit 0


If you are experiencing shutdown hangs do to lingering mount issues, then 
something similar to this setup may help. (I never did figure out why the 
normal shutdown scripts didn't do this automatically)


--
David C. Rankin, J.D.,P.E.

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-14 Thread Victor Silva

2012/6/14 David C. Rankin drankina...@suddenlinkmail.com

On 06/12/2012 02:06 PM, Victor Silva wrote:

Folks sorry for cross posting this at forum and mailing lists but so far
no
solution came there.

Folks after the last upgrade I can no longer shutdown nor reboot my
machine
(I'm using it as root). The command simply hangs and nothing happens. I've
done some research and found
https://bbs.archlinux.org/**viewtopic.php?id=141155https://bbs.archlinux.org/viewtopic.php?id=141155
this but that does not
seems to be my issue. I'm clueless which logs can I provide you in order
to
diagnose what can be the problem? Important thing, I have only 1 session
running and the system report going down still it never gets past the tty
broadcast as it seems.

Ideas?

I had a similar problem that began several months ago with my box hanging
on shutdown or reboot. This problem was related to samba shares not being
unmounted. To get around the problem a created an entry in
'/etc/rc.local.shutdown' to call a script to unmount the drives. This
solved the problem. The script I call simply checks whether there is still
an entry in /etc/mtab for the share and if so, manually unmounts the share:

[[ $UID -eq 0 ]] umountcmd=umount || umountcmd=sudo umount

if grep -q mnt\/phx-cfg /etc/mtab; then
echo umount /mnt/phx-cfg
$umountcmd /mnt/phx-cfg
fi

if grep -q mnt\/phx-david /etc/mtab; then
echo umount /mnt/phx-david
$umountcmd /mnt/phx-david
fi

if grep -q mnt\/phx /etc/mtab; then
echo umount /mnt/phx
$umountcmd /mnt/phx
fi

if grep -q mnt\/win /etc/mtab; then
echo umount /mnt/win
$umountcmd /mnt/win
fi

if grep -q mnt\/pv /etc/mtab; then
echo umount /mnt/pv
$umountcmd /mnt/pv
fi

exit 0

If you are experiencing shutdown hangs do to lingering mount issues, then
something similar to this setup may help. (I never did figure out why the
normal shutdown scripts didn't do this automatically)

--
David C. Rankin, J.D.,P.E.

I have no shares. Can I somehow try to umount everything in mtab? I'm not
familiar with the internal workings of mtab. I will read a bit. Also the
only thing I assume could be hanging is my external HD which I disconnected
having no effect on the problem behavior. Still I reported that my /boot
partition was being mounted and listed on kde file manager (forgot its
name) which was not default behavior. So could be the case that /boot is
hanging my shoutdown? I don't get the reason umount -a shutdown -h now
did not do the trick.

I ask gently again if you could inform me why did the magic reboot did
work while shutdown did not.

Regards,
Victor

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-14 Thread Guillermo Leira

 [[ $UID -eq 0 ]]  umountcmd=umount || umountcmd=sudo umount
 
 if grep -q mnt\/phx-cfg /etc/mtab; then
echo umount /mnt/phx-cfg
$umountcmd /mnt/phx-cfg
 fi
 
 if grep -q mnt\/phx-david /etc/mtab; then
echo umount /mnt/phx-david
$umountcmd /mnt/phx-david
 fi
 
 if grep -q mnt\/phx /etc/mtab; then
echo umount /mnt/phx
$umountcmd /mnt/phx
 fi
 
 if grep -q mnt\/win /etc/mtab; then
echo umount /mnt/win
$umountcmd /mnt/win
 fi
 
 if grep -q mnt\/pv /etc/mtab; then
echo umount /mnt/pv
$umountcmd /mnt/pv
 fi
 
 exit 0
 
 
 If you are experiencing shutdown hangs do to lingering mount issues, then
 something similar to this setup may help. (I never did figure out why the
 normal shutdown scripts didn't do this automatically)

I had the same problema, but I used

umount -arfl -t nfs,nfs4,smbfs,cifs

and it works... :-)

Best Regards

Guillermo Leira

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-14 Thread Victor Silva

2012/6/14 Victor Silva vfbsi...@gmail.com


 2012/6/14 Guillermo Leira gle...@gleira.com

  [[ $UID -eq 0 ]]  umountcmd=umount || umountcmd=sudo umount
 
  if grep -q mnt\/phx-cfg /etc/mtab; then
 echo umount /mnt/phx-cfg
 $umountcmd /mnt/phx-cfg
  fi
 
  if grep -q mnt\/phx-david /etc/mtab; then
 echo umount /mnt/phx-david
 $umountcmd /mnt/phx-david
  fi
 
  if grep -q mnt\/phx /etc/mtab; then
 echo umount /mnt/phx
 $umountcmd /mnt/phx
  fi
 
  if grep -q mnt\/win /etc/mtab; then
 echo umount /mnt/win
 $umountcmd /mnt/win
  fi
 
  if grep -q mnt\/pv /etc/mtab; then
 echo umount /mnt/pv
 $umountcmd /mnt/pv
  fi
 
  exit 0
 
 
  If you are experiencing shutdown hangs do to lingering mount issues,
 then
  something similar to this setup may help. (I never did figure out why
 the
  normal shutdown scripts didn't do this automatically)

 I had the same problema, but I used

 umount -arfl -t nfs,nfs4,smbfs,cifs

 and it works... :-)

 Best Regards

 Guillermo Leira


 I've tried Guillermo approach and  Davids too no luck. Maybe this can
 help, here are the contents of my mtab is something strange?

 *cat /etc/mtab
 rootfs / rootfs rw 0 0
 proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
 sys /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
 dev /dev devtmpfs
 rw,nosuid,relatime,size=4054576k,nr_inodes=1013644,mode=755 0 0
 run /run tmpfs rw,nosuid,nodev,relatime,mode=755 0 0
 /dev/sdb3 / ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
 devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
 shm /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0
 binfmt /proc/sys/fs/binfmt_misc binfmt_misc rw,relatime 0 0
 /dev/sdb5 /media/usbhd-sdb5 ext4
 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
 /dev/sdb1 /media/System_Reserved fuseblk
 rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
 0 0
 /dev/sda3 /media/usbhd-sda3 fuseblk
 rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
 0 0
 /dev/sda1 /media/usbhd-sda1 fuseblk
 rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
 0 0
 /dev/sda2 /media/usbhd-sda2 fuseblk
 rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
 0 0
 /dev/sdc1 /media/HITACHI fuseblk
 rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other,blksize=4096
 0 0
 /dev/sdb5 /boot ext4 rw,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
 none /proc/bus/usb usbfs
 rw,relatime,devgid=121,devmode=664,busgid=108,busmode=775 0 0
 gvfs-fuse-daemon /home/imanewbie/.gvfs fuse.gvfs-fuse-daemon
 rw,nosuid,nodev,relatime,user_id=1000,group_id=100 0 0*

 Regards,
 Victor


Looking at the forums I've found this:
https://bbs.archlinux.org/viewtopic.php?id=142644

No time to check now but can it be related?

Regards,
Victor

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-13 Thread Victor Silva

2012/6/13 Kevin Chadwick ma1l1i...@yahoo.co.uk

 On Tue, 12 Jun 2012 13:42:01 -0700
 pants wrote:

  check the SMART status of the drives,

 I've recently found Pmagic livecd to be very cool for this. Simply
 click the disk health icon on the desktop.


Folks I've messed things even more  I did a kernel downgrade, downloaded
kernel 3.3.7 from arch time machine and did pacman -U
kernel26-2.6.39.3-1-x86_64.pkg.tar.xz
System rebuilt modules and so on. After reboot it seems to report my /boot
is not a valid partition type with ext2fs. Still grub which is installed
there works and I can boot my windows.
My plan now is download a live cd do a chroot to my old arch and try to
update the kernel for the old state is it manageable?

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-13 Thread Victor Silva

Oki I reverted to the old kernel and I'm back to the old scenario how can I
properly downgrade a kernel?

Regards and thx for the help so far guys. This community rocks.
2012/6/13 Victor Silva vfbsi...@gmail.com



 2012/6/13 Kevin Chadwick ma1l1i...@yahoo.co.uk

 On Tue, 12 Jun 2012 13:42:01 -0700
 pants wrote:

  check the SMART status of the drives,

 I've recently found Pmagic livecd to be very cool for this. Simply
 click the disk health icon on the desktop.


 Folks I've messed things even more  I did a kernel downgrade, downloaded
 kernel 3.3.7 from arch time machine and did pacman -U
 kernel26-2.6.39.3-1-x86_64.pkg.tar.xz
 System rebuilt modules and so on. After reboot it seems to report my /boot
 is not a valid partition type with ext2fs. Still grub which is installed
 there works and I can boot my windows.
 My plan now is download a live cd do a chroot to my old arch and try to
 update the kernel for the old state is it manageable?

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-13 Thread gt

On Wed, Jun 13, 2012 at 11:14:06PM -0300, Victor Silva wrote:
 Oki I reverted to the old kernel and I'm back to the old scenario how can I
 properly downgrade a kernel?
 
 Regards and thx for the help so far guys. This community rocks.

Since you have already reverted to the old kernel, you don't further
need to downgrade it, as you have already downgraded it.

(Assuming, you did a pacman -U old-kernel)

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-13 Thread Victor Silva

2012/6/14 gt static.vor...@gmx.com

 On Wed, Jun 13, 2012 at 11:14:06PM -0300, Victor Silva wrote:
  Oki I reverted to the old kernel and I'm back to the old scenario how
 can I
  properly downgrade a kernel?
 
  Regards and thx for the help so far guys. This community rocks.

 Since you have already reverted to the old kernel, you don't further
 need to downgrade it, as you have already downgraded it.

 (Assuming, you did a pacman -U old-kernel)

I did it for the kenel which hangs, the one before it does not boot as
described on the previous posts. So somehow I need to find the last working
configuration. Also is shutdown -F a dangerous practice? Cause this works
for me.

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-13 Thread Martin Cigorraga

[OT]

@Victor: Brazilian Jiu-Jitsu and Arch? What a combination!

[/OT]

[arch-general] Shutdown and reboot not working after last weekend update

2012-06-12 Thread Victor Silva

Folks sorry for cross posting this at forum and mailing lists but so far no
solution came there.

Folks after the last upgrade I can no longer shutdown nor reboot my machine
(I'm using it as root). The command simply hangs and nothing happens. I've
done some research and found
https://bbs.archlinux.org/viewtopic.php?id=141155 this but that does not
seems to be my issue. I'm clueless which logs can I provide you in order to
diagnose what can be the problem? Important thing, I have only 1 session
running and the system report going down still it never  gets past the tty
broadcast as it seems.

Ideas?

This came after a update last weekend, the content of the update is here:

http://pastebin.com/54305EH0

Dmesg output is here

http://pastebin.com/HjwGvDsp

My last boot log is here:

http://pastebin.com/Tg70mD8F

My fstab (which was asked on the forums is here):

http://pastebin.com/dGUuWhNe


Is it somehow related?
https://bugzilla.redhat.com/show_bug.cgi?id=662433

I've googled a bit and came with a solution which gives us some insights
http://www.linuxjournal.com/content/rebooting-magic-way

Seems something is not properly unmounting.

SO you can for it with:

echo 1  /proc/sys/kernel/sysrq
echo b  /proc/sysrq-trigger

Forcing a shut down, still no clear way out of it. Ideas?

I was asked to perform a fsck which failed.It reported /dev/sda5 was
mounted. Is there any proper way I should use to call fsck? I did create a
/fsck file on / is there other more appropriate command to do it? Problably
you asked for my fstab expecting an error like this right? Would it be
better to run fsck from a livecd?

regards,

Victor

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-12 Thread Attila Vangel

Hi, I am not familiar with the problem, but I think the easiest way
(if you are not against graphical tools) is to grab a live cd (or
live usb dongle) containing gparted (it's not a bad thing to have,
anyway), but I am not an expert at this.

What really surprises me is that you use your system as root !?! I
would not dare to do that. I tend to add my user to various groops
according to the arch wiki documentation where neeeded, and for the
other commands I think I can safely run as root I alias them to be
'sudo command', and I maintain this list of safe commands in
/etc/sudoers (edited by visudo (you can change the editor of it, just
google it)), so that these commands can be executed without entering
the password all the time... Maybe not the best thing still, but I
guess it's OK with me.

Regards,
Attila

2012/6/12 Victor Silva vfbsi...@gmail.com:
snip
 Folks after the last upgrade I can no longer shutdown nor reboot my machine
 (I'm using it as root). The command simply hangs and nothing happens.
snip

 I was asked to perform a fsck which failed.It reported /dev/sda5 was
 mounted. Is there any proper way I should use to call fsck? I did create a
 /fsck file on / is there other more appropriate command to do it? Problably
 you asked for my fstab expecting an error like this right? Would it be
 better to run fsck from a livecd?

 regards,

 Victor

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-12 Thread Victor Silva

I got a ubuntu livecd with gparted lets see what happens. About using
thesystem as root. I only run pacman related commands as root have  a user
I use for mostly day tasks. This user is *NOT* on sudo, basically cause I
like to enforce my self to login as root and think about what I'm doing.
Also sudo is cumbersome to use in some instances as buil-in commands are
not avaliable.

So the only thing I've run as root was the pacman -Syu and followed the
arch announces regarding the updates. Nothing bad there I'mho. And the
problem I'm facing now has nothing to do with my system usage. Imho either
I have a bad sector or something went broken for some instances of the
system like mine or the other guy who also reported on the forums.

Regards,
Victor

2012/6/12 Attila Vangel vangel.att...@gmail.com

 Hi, I am not familiar with the problem, but I think the easiest way
 (if you are not against graphical tools) is to grab a live cd (or
 live usb dongle) containing gparted (it's not a bad thing to have,
 anyway), but I am not an expert at this.

 What really surprises me is that you use your system as root !?! I
 would not dare to do that. I tend to add my user to various groops
 according to the arch wiki documentation where neeeded, and for the
 other commands I think I can safely run as root I alias them to be
 'sudo command', and I maintain this list of safe commands in
 /etc/sudoers (edited by visudo (you can change the editor of it, just
 google it)), so that these commands can be executed without entering
 the password all the time... Maybe not the best thing still, but I
 guess it's OK with me.

 Regards,
 Attila

 2012/6/12 Victor Silva vfbsi...@gmail.com:
 snip
  Folks after the last upgrade I can no longer shutdown nor reboot my
 machine
  (I'm using it as root). The command simply hangs and nothing happens.
 snip

  I was asked to perform a fsck which failed.It reported /dev/sda5 was
  mounted. Is there any proper way I should use to call fsck? I did create
 a
  /fsck file on / is there other more appropriate command to do it?
 Problably
  you asked for my fstab expecting an error like this right? Would it be
  better to run fsck from a livecd?
 
  regards,
 
  Victor

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-12 Thread Δημήτρης Ζέρβας

three emails for the same subject... :S

(\_ /) copy the bunny to your profile
(0.o ) to help him achieve world domination.
( ) come join the dark side.
/_|_\ (we have cookies.)


On Tue, Jun 12, 2012 at 11:22 PM, Victor Silva vfbsi...@gmail.com wrote:

 I got a ubuntu livecd with gparted lets see what happens. About using
 thesystem as root. I only run pacman related commands as root have  a user
 I use for mostly day tasks. This user is *NOT* on sudo, basically cause I
 like to enforce my self to login as root and think about what I'm doing.
 Also sudo is cumbersome to use in some instances as buil-in commands are
 not avaliable.

 So the only thing I've run as root was the pacman -Syu and followed the
 arch announces regarding the updates. Nothing bad there I'mho. And the
 problem I'm facing now has nothing to do with my system usage. Imho either
 I have a bad sector or something went broken for some instances of the
 system like mine or the other guy who also reported on the forums.

 Regards,
 Victor

 2012/6/12 Attila Vangel vangel.att...@gmail.com

  Hi, I am not familiar with the problem, but I think the easiest way
  (if you are not against graphical tools) is to grab a live cd (or
  live usb dongle) containing gparted (it's not a bad thing to have,
  anyway), but I am not an expert at this.
 
  What really surprises me is that you use your system as root !?! I
  would not dare to do that. I tend to add my user to various groops
  according to the arch wiki documentation where neeeded, and for the
  other commands I think I can safely run as root I alias them to be
  'sudo command', and I maintain this list of safe commands in
  /etc/sudoers (edited by visudo (you can change the editor of it, just
  google it)), so that these commands can be executed without entering
  the password all the time... Maybe not the best thing still, but I
  guess it's OK with me.
 
  Regards,
  Attila
 
  2012/6/12 Victor Silva vfbsi...@gmail.com:
  snip
   Folks after the last upgrade I can no longer shutdown nor reboot my
  machine
   (I'm using it as root). The command simply hangs and nothing happens.
  snip
 
   I was asked to perform a fsck which failed.It reported /dev/sda5 was
   mounted. Is there any proper way I should use to call fsck? I did
 create
  a
   /fsck file on / is there other more appropriate command to do it?
  Problably
   you asked for my fstab expecting an error like this right? Would it be
   better to run fsck from a livecd?
  
   regards,
  
   Victor

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-12 Thread pants

It sounds like you might have had a process in uninterpretable sleep.
This happens sometimes when a process is in a system call and stops
working.  You can check for this by launching htop and seeing if any
processes are permanently in the 'D' state (in the column labeled 'S').
Alternatively, look in /var/log/errors.log and see if you can find
messages which look like:

 INFO: task [processinfo] blocked for more than 120 seconds.

If you do have a process in this state, you won't be able to kill it or
unmount the filesystem that it's stuck modifying.  Your best bet is to
manually kill everything you can, manually umount everything you can,
and then force the system down.  It sucks, I've had to do this with
processes stuck writing to a RAID and then have to wait for a few days
while the whole thing is resynced.

It also probably isn't the fault of an upgrade, just some piece of buggy
software that finally hit its error.  I know that xfs_fsr will quickly
and deterministically go into it when run on a filesystem which is
almost full.

Good luck!

pants.

On Tue, Jun 12, 2012 at 05:22:43PM -0300, Victor Silva wrote:
 I got a ubuntu livecd with gparted lets see what happens. About using
 thesystem as root. I only run pacman related commands as root have  a user
 I use for mostly day tasks. This user is *NOT* on sudo, basically cause I
 like to enforce my self to login as root and think about what I'm doing.
 Also sudo is cumbersome to use in some instances as buil-in commands are
 not avaliable.
 
 So the only thing I've run as root was the pacman -Syu and followed the
 arch announces regarding the updates. Nothing bad there I'mho. And the
 problem I'm facing now has nothing to do with my system usage. Imho either
 I have a bad sector or something went broken for some instances of the
 system like mine or the other guy who also reported on the forums.
 
 Regards,
 Victor
 
 2012/6/12 Attila Vangel vangel.att...@gmail.com
 
  Hi, I am not familiar with the problem, but I think the easiest way
  (if you are not against graphical tools) is to grab a live cd (or
  live usb dongle) containing gparted (it's not a bad thing to have,
  anyway), but I am not an expert at this.
 
  What really surprises me is that you use your system as root !?! I
  would not dare to do that. I tend to add my user to various groops
  according to the arch wiki documentation where neeeded, and for the
  other commands I think I can safely run as root I alias them to be
  'sudo command', and I maintain this list of safe commands in
  /etc/sudoers (edited by visudo (you can change the editor of it, just
  google it)), so that these commands can be executed without entering
  the password all the time... Maybe not the best thing still, but I
  guess it's OK with me.
 
  Regards,
  Attila
 
  2012/6/12 Victor Silva vfbsi...@gmail.com:
  snip
   Folks after the last upgrade I can no longer shutdown nor reboot my
  machine
   (I'm using it as root). The command simply hangs and nothing happens.
  snip
 
   I was asked to perform a fsck which failed.It reported /dev/sda5 was
   mounted. Is there any proper way I should use to call fsck? I did create
  a
   /fsck file on / is there other more appropriate command to do it?
  Problably
   you asked for my fstab expecting an error like this right? Would it be
   better to run fsck from a livecd?
  
   regards,
  
   Victor

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-12 Thread Victor Silva

I do have this exact error messega as I've posted before.  I will check
htop and post the output here. So now some questions which come out are: is
it somehow related to bad sectors? Shutdown is the locked process with the
message:

 INFO: task [shutdown] blocked for more than 120 seconds.

Still I've made a forced reboot via sysctl and on the next session I've
also hit this problem.

About xfs_fsr (which I assume is some kind of fsck right?) I need to run
fsck from a live cd, I just got one and will try it tonight.

So basically we are talking about the samething, still I'm not sure of what
is going wrong and sincerely I'm  bit afriad of having a system just messed
up because of a failing disk. How can I cover this scenario?

Regards,
Victor

2012/6/12 pants pa...@cs.hmc.edu

 It sounds like you might have had a process in uninterpretable sleep.
 This happens sometimes when a process is in a system call and stops
 working.  You can check for this by launching htop and seeing if any
 processes are permanently in the 'D' state (in the column labeled 'S').
 Alternatively, look in /var/log/errors.log and see if you can find
 messages which look like:

  INFO: task [processinfo] blocked for more than 120 seconds.

 If you do have a process in this state, you won't be able to kill it or
 unmount the filesystem that it's stuck modifying.  Your best bet is to
 manually kill everything you can, manually umount everything you can,
 and then force the system down.  It sucks, I've had to do this with
 processes stuck writing to a RAID and then have to wait for a few days
 while the whole thing is resynced.

 It also probably isn't the fault of an upgrade, just some piece of buggy
 software that finally hit its error.  I know that xfs_fsr will quickly
 and deterministically go into it when run on a filesystem which is
 almost full.

 Good luck!

 pants.

 On Tue, Jun 12, 2012 at 05:22:43PM -0300, Victor Silva wrote:
  I got a ubuntu livecd with gparted lets see what happens. About using
  thesystem as root. I only run pacman related commands as root have  a
 user
  I use for mostly day tasks. This user is *NOT* on sudo, basically cause I
  like to enforce my self to login as root and think about what I'm doing.
  Also sudo is cumbersome to use in some instances as buil-in commands are
  not avaliable.
 
  So the only thing I've run as root was the pacman -Syu and followed the
  arch announces regarding the updates. Nothing bad there I'mho. And the
  problem I'm facing now has nothing to do with my system usage. Imho
 either
  I have a bad sector or something went broken for some instances of the
  system like mine or the other guy who also reported on the forums.
 
  Regards,
  Victor
 
  2012/6/12 Attila Vangel vangel.att...@gmail.com
 
   Hi, I am not familiar with the problem, but I think the easiest way
   (if you are not against graphical tools) is to grab a live cd (or
   live usb dongle) containing gparted (it's not a bad thing to have,
   anyway), but I am not an expert at this.
  
   What really surprises me is that you use your system as root !?! I
   would not dare to do that. I tend to add my user to various groops
   according to the arch wiki documentation where neeeded, and for the
   other commands I think I can safely run as root I alias them to be
   'sudo command', and I maintain this list of safe commands in
   /etc/sudoers (edited by visudo (you can change the editor of it, just
   google it)), so that these commands can be executed without entering
   the password all the time... Maybe not the best thing still, but I
   guess it's OK with me.
  
   Regards,
   Attila
  
   2012/6/12 Victor Silva vfbsi...@gmail.com:
   snip
Folks after the last upgrade I can no longer shutdown nor reboot my
   machine
(I'm using it as root). The command simply hangs and nothing happens.
   snip
  
I was asked to perform a fsck which failed.It reported /dev/sda5 was
mounted. Is there any proper way I should use to call fsck? I did
 create
   a
/fsck file on / is there other more appropriate command to do it?
   Problably
you asked for my fstab expecting an error like this right? Would it
 be
better to run fsck from a livecd?
   
regards,
   
Victor

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-12 Thread Martti Kühne

On Tue, Jun 12, 2012 at 04:06:27PM -0300, Victor Silva wrote:
 
 Dmesg output is here
 
 http://pastebin.com/HjwGvDsp
 

umm that just is kde crashing.
what exactly is the error when trying to shut down or reboot,
or where is the hang? before or after shutting down X, are there error
messages displayed? what happens if you just log in to tty and try to
shutdown/reboot?

cheers!
mar77i

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-12 Thread pants

Well, in general shutdown itself will *not* be the halted process; that
would be rather strange.  But hey, it could have happened.  Usually,
shutdown and reboot hang because they are coded to wait until all other
processes reported having quit, and the process in question hasn't quit
yet (because it never will).  Are there any other similar messages for
other processes?

Also, now that you've rebooted it's unlikely that you still have a
process in uninterruptible sleep.  I would run fsck (the one for the
filesystem you're using) to make sure that forcing a shutdown didn't
cause any problems, and perhaps check the SMART status of the drives,
but I wouldn't worry too much.

pants.

On Tue, Jun 12, 2012 at 05:36:26PM -0300, Victor Silva wrote:
 I do have this exact error messega as I've posted before.  I will check
 htop and post the output here. So now some questions which come out are: is
 it somehow related to bad sectors? Shutdown is the locked process with the
 message:
 
  INFO: task [shutdown] blocked for more than 120 seconds.
 
 Still I've made a forced reboot via sysctl and on the next session I've
 also hit this problem.
 
 About xfs_fsr (which I assume is some kind of fsck right?) I need to run
 fsck from a live cd, I just got one and will try it tonight.
 
 So basically we are talking about the samething, still I'm not sure of what
 is going wrong and sincerely I'm  bit afriad of having a system just messed
 up because of a failing disk. How can I cover this scenario?
 
 Regards,
 Victor
 
 2012/6/12 pants pa...@cs.hmc.edu
 
  It sounds like you might have had a process in uninterpretable sleep.
  This happens sometimes when a process is in a system call and stops
  working.  You can check for this by launching htop and seeing if any
  processes are permanently in the 'D' state (in the column labeled 'S').
  Alternatively, look in /var/log/errors.log and see if you can find
  messages which look like:
 
   INFO: task [processinfo] blocked for more than 120 seconds.
 
  If you do have a process in this state, you won't be able to kill it or
  unmount the filesystem that it's stuck modifying.  Your best bet is to
  manually kill everything you can, manually umount everything you can,
  and then force the system down.  It sucks, I've had to do this with
  processes stuck writing to a RAID and then have to wait for a few days
  while the whole thing is resynced.
 
  It also probably isn't the fault of an upgrade, just some piece of buggy
  software that finally hit its error.  I know that xfs_fsr will quickly
  and deterministically go into it when run on a filesystem which is
  almost full.
 
  Good luck!
 
  pants.
 
  On Tue, Jun 12, 2012 at 05:22:43PM -0300, Victor Silva wrote:
   I got a ubuntu livecd with gparted lets see what happens. About using
   thesystem as root. I only run pacman related commands as root have  a
  user
   I use for mostly day tasks. This user is *NOT* on sudo, basically cause I
   like to enforce my self to login as root and think about what I'm doing.
   Also sudo is cumbersome to use in some instances as buil-in commands are
   not avaliable.
  
   So the only thing I've run as root was the pacman -Syu and followed the
   arch announces regarding the updates. Nothing bad there I'mho. And the
   problem I'm facing now has nothing to do with my system usage. Imho
  either
   I have a bad sector or something went broken for some instances of the
   system like mine or the other guy who also reported on the forums.
  
   Regards,
   Victor
  
   2012/6/12 Attila Vangel vangel.att...@gmail.com
  
Hi, I am not familiar with the problem, but I think the easiest way
(if you are not against graphical tools) is to grab a live cd (or
live usb dongle) containing gparted (it's not a bad thing to have,
anyway), but I am not an expert at this.
   
What really surprises me is that you use your system as root !?! I
would not dare to do that. I tend to add my user to various groops
according to the arch wiki documentation where neeeded, and for the
other commands I think I can safely run as root I alias them to be
'sudo command', and I maintain this list of safe commands in
/etc/sudoers (edited by visudo (you can change the editor of it, just
google it)), so that these commands can be executed without entering
the password all the time... Maybe not the best thing still, but I
guess it's OK with me.
   
Regards,
Attila
   
2012/6/12 Victor Silva vfbsi...@gmail.com:
snip
 Folks after the last upgrade I can no longer shutdown nor reboot my
machine
 (I'm using it as root). The command simply hangs and nothing happens.
snip
   
 I was asked to perform a fsck which failed.It reported /dev/sda5 was
 mounted. Is there any proper way I should use to call fsck? I did
  create
a
 /fsck file on / is there other more appropriate command to do it?
Problably
 you asked for my fstab expecting an

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-12 Thread Victor Silva

Logs here:
http://pastebin.com/0BMzruNJ
Nothing happens, this is the point. I can still use the system normally
after the shutdown command. It does not turn X off. It does not shutdown
just after the broadcast. This is what I consider extremelly strange. AS
you pointed out I could have something waiting to be unmounted so I did a
umount -a and kill -9 -1 to be sure nothing was hanging. Still could not
shutdown.

by the way thanks a lot for all the insights so far guys. I'm sure we can
work it out :)

2012/6/12 Martti Kühne mysat...@gmail.com

 On Tue, Jun 12, 2012 at 04:06:27PM -0300, Victor Silva wrote:
 
  Dmesg output is here
 
  http://pastebin.com/HjwGvDsp
 

 umm that just is kde crashing.
 what exactly is the error when trying to shut down or reboot,
 or where is the hang? before or after shutting down X, are there error
 messages displayed? what happens if you just log in to tty and try to
 shutdown/reboot?

 cheers!
 mar77i

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-12 Thread Martti Kühne

On Tue, Jun 12, 2012 at 05:53:36PM -0300, Victor Silva wrote:
 Logs here:
 http://pastebin.com/0BMzruNJ
 Nothing happens, this is the point. I can still use the system normally
 after the shutdown command. It does not turn X off. It does not shutdown
 just after the broadcast. This is what I consider extremelly strange. AS
 you pointed out I could have something waiting to be unmounted so I did a
 umount -a and kill -9 -1 to be sure nothing was hanging. Still could not
 shutdown.
 
 by the way thanks a lot for all the insights so far guys. I'm sure we can
 work it out :)
 

...3 or 4 recent bug reports [0].
Your problem is the kde's fine nepomuk software [1].
I find it a pretty thorough achievment to let this stuff crash this way.
What version of extra/kdebase-runtime do you have installed?

cheers!
mar77i

[0] http://www.google.ch/search?q=nepomuk+error+4+in+libstreams.so

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-12 Thread Victor Silva

So can I justremove it and check what happens? This makes sense as nepomuk
keeps indexing all the contents of the machine. I will try to remove it and
check what happens. Which part of the logs gave you the hint about nepomuk?

Regards,
Victor

2012/6/12 Martti Kühne mysat...@gmail.com

 On Tue, Jun 12, 2012 at 05:53:36PM -0300, Victor Silva wrote:
  Logs here:
  http://pastebin.com/0BMzruNJ
  Nothing happens, this is the point. I can still use the system normally
  after the shutdown command. It does not turn X off. It does not shutdown
  just after the broadcast. This is what I consider extremelly strange. AS
  you pointed out I could have something waiting to be unmounted so I did a
  umount -a and kill -9 -1 to be sure nothing was hanging. Still could not
  shutdown.
 
  by the way thanks a lot for all the insights so far guys. I'm sure we can
  work it out :)
 

 ...3 or 4 recent bug reports [0].
 Your problem is the kde's fine nepomuk software [1].
 I find it a pretty thorough achievment to let this stuff crash this way.
 What version of extra/kdebase-runtime do you have installed?

 cheers!
 mar77i

 [0] http://www.google.ch/search?q=nepomuk+error+4+in+libstreams.so

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-12 Thread Victor Silva

Sorry for double posting but just sat and though and I realized nopomuk
isprobably unrelated since the problem also happens if I'm on tty and never
start the x server.

2012/6/12 Victor Silva vfbsi...@gmail.com

 So can I justremove it and check what happens? This makes sense as nepomuk
 keeps indexing all the contents of the machine. I will try to remove it and
 check what happens. Which part of the logs gave you the hint about nepomuk?

 Regards,
 Victor


 2012/6/12 Martti Kühne mysat...@gmail.com

 On Tue, Jun 12, 2012 at 05:53:36PM -0300, Victor Silva wrote:
  Logs here:
  http://pastebin.com/0BMzruNJ
  Nothing happens, this is the point. I can still use the system normally
  after the shutdown command. It does not turn X off. It does not shutdown
  just after the broadcast. This is what I consider extremelly strange. AS
  you pointed out I could have something waiting to be unmounted so I did
 a
  umount -a and kill -9 -1 to be sure nothing was hanging. Still could not
  shutdown.
 
  by the way thanks a lot for all the insights so far guys. I'm sure we
 can
  work it out :)
 

 ...3 or 4 recent bug reports [0].
 Your problem is the kde's fine nepomuk software [1].
 I find it a pretty thorough achievment to let this stuff crash this way.
 What version of extra/kdebase-runtime do you have installed?

 cheers!
 mar77i

 [0] http://www.google.ch/search?q=nepomuk+error+4+in+libstreams.so

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-12 Thread Martti Kühne

On Tue, Jun 12, 2012 at 06:26:59PM -0300, Victor Silva wrote:
 So can I justremove it and check what happens? This makes sense as nepomuk
 keeps indexing all the contents of the machine. I will try to remove it and
 check what happens. Which part of the logs gave you the hint about nepomuk?
 
 Regards,
 Victor
 

well, that's what I could tell from the log you posted in [0].
line 21 contained a program name and a shared object.

sorry, and sorry for saying that was the problem. I should have made clearer
these things aren't usually the culprit. the process in question isn't running
when you log in to tty, though? and tty also hangs comparably to what you
described with X?

There was a way that made old kernels dump all syslog to tty12, which I think
was removed from syslog.conf. I only know I left it in however, if shutting
down immediately crashes, sleep 2  shutdown; ctrl-alt-f12 could work...

Also, please answer below, not above previous posts.

cheers!
mar77i

[0] http://pastebin.com/HjwGvDsp

Re: [arch-general] Shutdown and reboot not working after last weekend update

2012-06-12 Thread Victor Silva

2012/6/12 Martti Kühne mysat...@gmail.com

 On Tue, Jun 12, 2012 at 06:26:59PM -0300, Victor Silva wrote:
  So can I justremove it and check what happens? This makes sense as
 nepomuk
  keeps indexing all the contents of the machine. I will try to remove it
 and
  check what happens. Which part of the logs gave you the hint about
 nepomuk?
 
  Regards,
  Victor
 

 well, that's what I could tell from the log you posted in [0].
 line 21 contained a program name and a shared object.

 sorry, and sorry for saying that was the problem. I should have made
 clearer
 these things aren't usually the culprit. the process in question isn't
 running
 when you log in to tty, though? and tty also hangs comparably to what you
 described with X?

 There was a way that made old kernels dump all syslog to tty12, which I
 think
 was removed from syslog.conf. I only know I left it in however, if shutting
 down immediately crashes, sleep 2  shutdown; ctrl-alt-f12 could work...

 Also, please answer below, not above previous posts.

 cheers!
 mar77i

 [0] http://pastebin.com/HjwGvDsp

Oki, I'm new to the mailing lists so sorry if I missbehave a bit. :) A
thing I've noticed is for some reason /dev/sdb5 which is my /boot partition
in another harddisk keeps mounted after the boot process which was not the
previous behaviour as far as I can remmember. I googled a bit and found no
reasons to make it noauto. Can it be related to the problem?

Regards,
Victor

43 matches

Mail list logo