[ATrpms-users] "device already mounted or mount point busy" after upgrading to latest tuxonice kernel?

[Tako Schotanus]

Ok, figured out that commenting out the LABEL=/boot line in fstab (from the
rescue cd) will at least let me boot.

No to figure out WHY this is happening and HOW to get back to normal.

Hints appeciated :)

Cheers,
 -Tako

On 10/30/07, Tako Schotanus <quintesse at palacio-cristal.com> wrote:
>
> Hi all,
>
> I've got this weird situation after upgrading to the latest tuxonice
> kernel (kernel-tuxonice-2.6.22.9-91_1.cubbi_tuxonice.fc7.i686) where I'll
> get an "device already mounted or mount point busy" on my /boot patition
> during startup after which the system refuses to continue allowing me drop
> into a shell.
>
> In the shell I can try whatever I want with the mount command but it will
> refuse to mount /boot giving the above error but also refusing to unmount
> saying it's not mounted (which it is not because I can't access the files in
> the partition).
>
> The first time this happened I could boot into the rescue mode of the
> Fedora 7 install disc and after running e2fsck on the partition I could boot
> normally again. Today the same problem occurred but the e2fsck-trick didn't
> work this time. Problem is that smart removed the previous kernel that I had
> (that isn't supposed to happen, isn't it?) so I don't have my previous
> kernel to boot into to try to see if it has anything to do with the kernel
> version.
>
> Does anyone have any idea what could be wrong? How can an unmounted
> partition be busy for example? And even better: does anyone know how to fix
> it? :)
>
> Cheers,
>  -Tako
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.atrpms.net/pipermail/atrpms-users/attachments/20071030/2e17c531/attachment.html