Al 21/10/12 00:08, En/na David W. Hodgins ha escrit:
> On Sat, 20 Oct 2012 15:48:30 -0400, Luca Olivetti <[email protected]> wrote:
>
>> Hello,
>> just upgraded from mandriva 2010.0 to mageia 2 (it wasn't easy) and I'm
>> already "loving" systemd (not!).
>> At first it wouldn't boot and I took a while to find that the cause was that
>> it couldn't mount ntfs partitions.
>> For the time being I just commented out of fstab, but I'd like for them to
>> be mounted at boot.
>> Apparently it's because fuse hasn't started, but I cannot really tell.
>> Any idea?
>
> Upgrading directly from 2010.0 to Mageia 2 is not recommended, as there were
> some updates in Mageia 1 specifically to make upgrading to Mageia 2 work.
Well, in fact I wanted to update to mageia 1. Unfortunately the urpmi
incantation in the wiki failed, and next time I invoked it, without me
realizing it, it switched the repositories to mageia 2. Of course that didn't
work ("kernel too old") so it resulted in a half-upgraded, unbootable system.
I used the network boot cd to attempt an upgrade from the installer, but that
complained I had not enough space.
Luckily enough, I managed to use the console in the installer (no, the "rescue"
option didn't work) to chroot to the old system and complete the urpmi update
(by removing some big packages to recover some space).
>
> For any file system where you want the boot to continue, instead of dropping
> to a shell, add the nofail option in /etc/fstab.
noted for next time
>
> As to ntfs not mounting, make sure the following packages are installed ...
> ntfs-3g fuse libfuse2
yep, everything installed, those partition mounted fine for several years
>
> Confirm you can then mount the ntfs partition. Once you're able to mount it
> in a regular running session, as root run "dracut -f", to update the initrd
> file.
Well, it seems the solution was to remove the "0 0" at the end of the fstab
lines with those partitions.
Love the supposed systemd backwards compatibility....
>
> Regards, Dave Hodgins
Thank you.
Bye
--
Luca
