Arch Linux

Lowra

Member

Registered: 2009-09-21

Posts: 192

Can't mount any filesystem after a kernel upgrade without rebooting

Hi,

I noticed this issue a few kernel release ago, and now with the 3.2 release, I'm sure it is a real (light) problem.
After doing a kernel upgrade, I can't mount my usb sticks, my sd car without first rebooting my system to get it working.

Since the solution is a simple reboot, it isn't a big deal, unless we have like me a huge download list, and don't want to stop/resume our downloads.
However, I though I'll post in case this problem could be fixed in the future, or if someone ran into the same problem.

Bye

hadrons123

Member

From: chennai

Registered: 2011-10-07

Posts: 1,249

Re: Can't mount any filesystem after a kernel upgrade without rebooting

what does your dmesg say at those times?

edit:
does it recognize the USB device?

Last edited by hadrons123 (2012-01-19 14:26:09)

stqn

Member

Registered: 2010-03-19

Posts: 1,191

Website

Re: Can't mount any filesystem after a kernel upgrade without rebooting

The usual response to this kind of posts is: don't update the kernel if you don't plan on rebooting your system afterwards.

I guess your SD card is FAT32-formated, and since the kernel update deleted all your old modules, including the fat, vfat and msdos modules, the (old, running) kernel can't find them to mount the card.

dimaqq

Member

Registered: 2012-02-22

Posts: 3

Re: Can't mount any filesystem after a kernel upgrade without rebooting

This bit me too!

There are some samba shares on the network that I use only occasionally, pacman -Syu upgraded kernel, deleted old modules and I was unable to mount the share without a reboot. Serious FFS!

Had to do a world update since pacman doesn't support incremental updates

To make matters worse my /boot was not mounted during the update and new kernel was put in the wrong place. I couldn't even mount /boot with the old kernel as it's ext2 and needs a module. Luckily I could mount /boot with ext4 backward compatibility.

Oh and I couldn't get eth0 up meanwhile (rebooted with old kernel without modules) either.

I can barely live with this on a desktop, but I will never install Arch on a server. Not until pacman tracks dependency versions anyway.

d.

Last edited by dimaqq (2012-03-05 10:12:34)

tomk

Forum Fellow

From: Ireland

Registered: 2004-07-21

Posts: 9,839

Re: Can't mount any filesystem after a kernel upgrade without rebooting

Sorry, but this is too funny.

Yes, kernel upgrades require a reboot - this has always been the case, but I suppose it's never too late to make such "discoveries".

dimaqq, there is a wide choice of Arch distros - if you don't like Arch's rolling releases, perhaps some other distro would suit you better.

And yes, I agree that your failure to mount /boot when upgrading would make matters worse, but that's user error, and not related to the issue under discussion.

Finally, please provide an example of how pacman does not track dependency versions.