Triaged to Fix Released. There were several problems caused by mounting
NTFS drives. Installing Linux was just one of them.
** Changed in: ubiquity (Ubuntu)
Status: New = Fix Released
--
[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
** Tags added: partman
--
[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
https://bugs.launchpad.net/bugs/135370
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
I can happily report that at least in Ubuntu 7.10 RC this problem no
longer exists.
I was able to test the installation today and even though the installer
still complained somewhat (the migration-assistant not being able to
unmount partitions), it was no longer hanging nor indefinitely waiting
I can confirm I had the same problem using the beta of Gutsy Gibbon. I
tried renaming the mount points of my windows partitions and and
installing, but hung up at the 5% until i did a killall of mount.ntfs.
--
[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
FWIW I think this is actually fixed by this tweak that I applied after
beta:
partman-basicfilesystems (54ubuntu4) gutsy; urgency=low
* mount.d/basic: Close mount's fd 3 so that it doesn't inherit a debconf
file descriptor, to prevent log-output hanging when ntfs-3g is in use.
-- Colin
ntfs-3g's fd 3 is the ntfs block device where it read/writes. Anything
else is closed (fd 0,1,2 unless the 'debug' option is used). Logging is
done via openlog(3).
--
[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
https://bugs.launchpad.net/bugs/135370
You
Actually the daemon(3) function is used by default which redirects the standard
fd's to /dev/null:
lrwx-- 1 root root 64 Oct 2 00:58 5 - socket:[2190855]
lrwx-- 1 root root 64 Oct 2 00:58 4 - /dev/fuse
lrwx-- 1 root root 64 Oct 2 00:58 3 - /dev/hda3
lrwx-- 1 root root 64 Oct 2
Can anybody send an install log? I've never heard about situation where
mount.ntfs (ntfs-3g) would hang, only here. Mount either succeeds or it
fails and the mount command returns. The issue is clearly related to
mount.ntfs, it triggers something somewhere but only the log could tell
where the
I tried to install Gutsy using defaults, i.e:
* English language (to overcome Bug #145012)
* all mountpoints at default locations names (/media/sda*)
To my surprise I was able to finish the installation. I made a bunch of
screenshots with all the steps I've taken.
I will attach them in a
** Attachment added: /var/log/syslog after the installation succeeded
http://launchpadlibrarian.net/9609438/syslog
--
[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
https://bugs.launchpad.net/bugs/135370
You received this bug notification because you are a
I think I was able to isolate the problem. I've tried to reinstall Gutsy
and now it hung. Basically what I did differently this time was to
specify a different mountpoint for NTFS volumes:
/dev/sda2 at /mnt/vista instead of /media/sda2
/dev/sda5 at /mnt/homek instead of /media/sda5
You
Gutsy uses a very old NTFS-3G which denied several mount scenarios what are
supported now. For example when the NTFS partition was resized previously, or
the Windows hibernation file is corrupted.
There are two problems here:
1) NTFS-3G is tool old
2) Install shouldn't stop if mounting the NTFS
My comment was for the earlier syslog. Is mount.ntfs a symlink to ntfs-
3g? If yes then there are more problems.
--
[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
https://bugs.launchpad.net/bugs/135370
You received this bug notification because you are a member
# which mount.ntfs
/sbin/mount.ntfs
# ls -al /sbin/mount.ntfs
lrwxrwxrwx 1 root root 12 2007-09-30 21:15 /sbin/mount.ntfs - /bin/ntfs-3g
That says it all.
--
[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
https://bugs.launchpad.net/bugs/135370
You received
And maybe this one too:
# mount.ntfs
ntfs-3g: No device is specified.
ntfs-3g 1.710 - Third Generation NTFS Driver
Copyright (C) 2005-2006 Yura Pakhuchiy
Copyright (C) 2006-2007 Szabolcs Szakacsits
Usage:ntfs-3g device|image_file mount_point [-o option[,...]]
Options: ro, force, locale=,
Do you have the same problem with not JFS file system too? JFS is dead,
IBM stopped supporting it, so it can have all short of problems, more
and more in time.
--
[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
https://bugs.launchpad.net/bugs/135370
You received
No, I observed the same behavior with ext2 and ext3 (as you can see
/dev/sda8 still has ext2 after the previous testings).
As a side note, when I resized Vista partitions to free up space for
Ubuntu (it's a new laptop right now), the partitioner offered ext2 as a
default (!) for all Linux
Gosh, it's late... When I wrote:
I observed the same behavior with ext2 and ext3
I wanted to say that it didn't matter what other file systems I have
used. In all my cases the installer was hanging, no matter if I used
ext2, ext3 or jfs for Linux partitions.
And yes, you've got a good eye. I
If you can make a custom installer then you can use the 'debug' ntfs-3g
mount option and you could see on the stdout (or stderr, depending on
the fuse version used) what's exactly happening with the driver and
where it hangs. Well, actually unless it's in the kernel which is very
probably. How
The laptop has 2GiB. It's an ASUS F3S-AS218E (T7250).
But right now I don't want to create a custom installer. I have enough
after fighting recently with debugging LTSP (Edubuntu) startup sequence.
--
[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
I have had the same problem with Ubuntu 7.10 beta installer and a rename
of the mount point of the windows partition.
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/147422
Thanks to the analysis in this bug report I now worked around the
problem (I'll change the windows mount point
I experienced the same installer hang at 5%. My workaround was to not to
set a mount point for my windows partition, and manually add it to
/etc/fstab once the installation is completed.
--
[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
I can confirm the same behavior. Installer hangs at 5%. killall -9
mount.ntfs causes the installer to complete successfully.
--
[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
https://bugs.launchpad.net/bugs/135370
You received this bug notification because you
Same for me.
--
[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
https://bugs.launchpad.net/bugs/135370
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Same for me! Gutsy Tribe 5 won't install, hangs on 5% when formatting an
ext3 root-partition.
BUT: I took a Tribe 4 CD and the installation with Tribe 4 works
flawlessly!
My Hardware:
Dell Inspirion 6400 Laptop, nvidia GeForce Go 7300, 2GB RAM, Intel 3945
wireless.
--
[gutsy tribe-5]
Why did /sbin/mount.ntfs look suspicious?
The output of 'mount -l' displayed the first partition with NTFS as the last
one mounted (see the result above). So I suspected /something/ with
mounting this type of filesystem (ext3 fs were mounted correctly). Other
than that I guessed. And since
I just did what I've said earlier: I started the installation of
Ubuntu Gutsy Tribe-5 on my laptop. The 5% stop with mount.ntfs
happened again, with the same solution. So in my case the problem is
repeatable.
And now for something completely different... ;-)
I noticed that the current installer
Why did /sbin/mount.ntfs look suspicious? How long did you wait? Isn't
it possible that it was importing (searching for and copying) files from
the NTFS partition to the Linux one? Thanks.
--
[gutsy tribe-5] installer stops at 'creating a filesystem' because of mount.ntfs
28 matches
Mail list logo
