Militantly FREE software support.
Militantly FREE software support.
NavigationUser loginSpam?See spam posts on this site? If so, please don't reply to the spam! Instead, just report the URL to the webmaster. |
ntfs mount errorsFurther to my problem of not being able to automatically mount my from dmesg: NTFS driver 2.1.27 [Flags: R/W MODULE]. I'm not clear on what I need to do. I don't seem to have chkdsk. I Phill -- Bookmark/Search this post with: 
|
• Debian Weekly News - Essential reading for any Debian fan. • Documentation - Debian's own authoritative documentation, including installation docs. • FAQ - Got questions about Debian GNU/Linux? • From Windows to Debian - Tips for converting from Windows to Debian GNU/Linux • Package of the Day. • Security - Security information and alerts! • Bug System - Bug tracking and instructions on reporting bugs. • CD Images - Where/how to get Debian GNU/Linux CD images. • Mailing List Subscription - Dozens of Debian-specific support mailing lists! • Mailing List Archives - Searchable archives of Debian's mailing lists. • Free Software Guidelines - Learn Debian's idea of what "free" software really is. • Package Listings - A very valuable tool: searchable, integrated with bug reports. • Apt-Get Sources - Sources for *.debs which are not official Debian packages. • Backports - Unofficial new software packages that have been "back-ported" to work with the Debian stable/official release. • Developer's Corner - Info about the people behind Debian, policies, and how to package *.deb files.
ntfs mount errors
On Tue, 31 Jul 2007 14:26:41 -0400
Phill Atwood wrote:
>
> Further to my problem of not being able to automatically mount my
> windows xp partition and cd to it as a regular user.
>
> >from dmesg:
>
> NTFS driver 2.1.27 [Flags: R/W MODULE].
> NTFS volume version 3.1.
> NTFS-fs warning (device sda1): load_system_files(): Unsupported volume
> flags 0x4000 encountered.
> NTFS-fs warning (device sda1): load_system_files(): Volume has
> unsupported flags set. Will not be able to remount read-write. Run
> chkdsk and mount in Windows.
----
Hi there,
I have no information about what was discussed before, but to me this looks like: Boot into windoze. Click on Start->Execute (don't know how this is exactly called on English windoze) or open a command window (cmd.exe). There, type: chkdsk /f . Tell windoze you want it to check the disk at reboot. Reboot into windoze, and let chkdsk repair the disk. Then reboot into linux and see what happens.
Cheers,
Stephan
--
ntfs mount errors
On Sat, 2007-04-08 at 01:24 +0200, Stephan Hachinger wrote:
> Hi Phil,
>
> err ... well, which suggestion? Anyway, I found the following:
>
Maybe it was Doug who made the suggestion.
> * Are you using "alternative data streams" [sorry, that's an direct German to English translation ... don't know how this is called on English windoze], compressed or encrypted files? If so, this could cause problems.
>
> * Are you using a "dynamical volume" [direct translation again, seems to be some kind of extendible partitions - I've never used that windoze feature]?
>
> * If all the things above do not apply, try marking the fs as dirty, rebooting (chkdsk checks), then rebooting a second time into windoze, then rebooting into linux (see http://lists.debian.org/debian-user/2006/03/msg03215.html)
>
> As for the umask, I don't know exactly what you've done, but the following posting might be interesting: http://osdir.com/ml/linux.file-systems.ntfs.user/2006-05/msg00004.html . "umask=0222" seems to be a quick and dirty way to make it accessible to any user. For the long term however, maybe you can try to figure out a good and clean way to do it, with these groups etc.
>
Success. Although I can't say that I really understand. Setting
umask=0222 in the /etc/fstab file did the trick. I don't understand why
mounting a ro partition to a directory with just write permissions would
work. 0544 or 0555 seemed the more logical thing to try...
As a relative newby here are some things I noted that I don't get.
a) Previously, I made a group and added my users to it, editted fstab to
allow gid for that group, chmoded the directory to 0544 and set the
umask in fstab to be 0544 too. This almost worked. I was able to cd to
my windoze directory, but I couldn ls -l it!
b) When I created my new group bar and added my user foo to it with
"adduser foo bar" it worked. When I issued the "groups" command it did
not show bar as being one of the groups that foo belonged to. I
rebooted, issued "groups" again and now foo is in bar. Seems to me it
should know this right away without a reboot... (I'm showing my Windoze
ancestry by rebooting all the time!)
c) Even after this success, dmesg shows:
NTFS volume version 3.1.
NTFS-fs warning (device sda1): load_system_files(): Unsupported volume
flags 0x4000 encountered.
NTFS-fs error (device sda1): load_system_files(): Volume has unsupported
flags set. Mounting read-only. Run chkdsk and mount in Windows.
I did go into windoze and run chkdsk after forcing the dirty bit. It
found no errors. But I still get the msg on the linux side.
I've probably got my head in the clouds, but is any of this a bug in
Debian. Especially a) and b). I'll have to figure out the BTS system
to find out...
> Another thing: If you also need write access onto ntfs, and want read access onto compressed files, then the ntfs-3g driver might be interesting for you. For newbies however, it might not be that easy to install... you need to make a package for stable yourself. On the other hand, if you'd need it, I can just do an update/recompile here on my system and send the resulting package to you via email.
>
> Cheers,
>
> Stephan
>
I had run into ntfs-3g while googling earlier. It does intrigue me.
Making my own package to install it is probably way over my head.
Although, I would like to get into package maintenance. If this is not
too big a piece to chew on I would be willing to take whatever time to
try. I am sceptical that previous versions of Debian don't trust ntfs
to write but these ntfs-3g guys do. I also read that if you mount
windows xp as vfat you can write to it. Even more sceptical.
If you are willing to recompile it for me I'd try it. I can't afford to
loose that data, so I would back it up first.
Thanks for your help Stephan. Doug and others too. This beats windoze
help/obfuscation hands down!
Phill
>
> On Fri, 03 Aug 2007 12:30:50 -0400
> Phill Atwood wrote:
>
> >
> > Stephan,
> >
> > Thanks for your suggestion. It was a good one that I had overlooked
> > despite having read the mount man page. However, I tried it and it
> > didn't work. At least I tried using a umask. I still should try
> > setting up a group and setting the gid.
> >
> > I still get the error messages in dmesg, as follows:
> >
> > NTFS driver 2.1.27 [Flags: R/W MODULE].
> > NTFS volume version 3.1.
> > NTFS-fs warning (device sda1): load_system_files(): Unsupported volume
> > flags 0x4000 encountered.
> > NTFS-fs error (device sda1): load_system_files(): Volume has unsupported
> > flags set. Mounting read-only. Run chkdsk and mount in Windows.
> >
> > It is not a high priority issue. It's just bugging me. I hope to look
> > into it more tonight or tomorrow.
> >
> > Your help has been appreciated.
> >
> > Phill
> >
> >
> > On Fri, 2007-03-08 at 12:56 +0200, Stephan Hachinger wrote:
> > > Douglas Allan Tutty wrote:
> > >
> > > > On Wed, Aug 01, 2007 at 04:49:04AM +0200, pinniped wrote:
> > > > >
> > > > > (quote)
> > > > > I still have the problem. ie. The windoze partition is
> > > > > mounted automatically fine, but I can only cd to it if I am root.
> > > > > (end quote)
> > > > >
> > > > > Do:
> > > > > man mount
> > > > >
> > > > > Look at the 'Mount options for ntfs'. All your mysteries are explained
> > > (...)
> > > > > So you need to set the uid/gid and umask. You really want 'root' to be the
> > > > > owner anyway so I guess you only want to change the gid to the 'disk' group
> > > > > and make sure you have a sensible umask.
> > > >
> > > > Be careful there, members of the 'disk' group can do nasty things on
> > > > your debian box too. Perhaps create a new group who can access the
> > > > windows partition, put those users into the group, then use the gid=
> > > > parameter in fstab. However, this doesn't affect the uid. I can't test
> > > (...)
> > >
> > > Hi Phill,
> > >
> > > short "PM": Does this work now? And: Has the error msg in dmesg gone away?
> > >
> > >
> > > Cheers,
> > >
> > > Stephan
--
ntfs mount errors
On Fri, Aug 03, 2007 at 11:17:21PM -0400, Phill Atwood wrote:
>
>
>
> Success. Although I can't say that I really understand. Setting
> umask=0222 in the /etc/fstab file did the trick. I don't understand why
> mounting a ro partition to a directory with just write permissions would
> work. 0544 or 0555 seemed the more logical thing to try...
its a mask so you turn on the bits you want off in the final result.
if one digit of your mask is 2 then it looks like: 010
that makes the final perm is 5 and it looks like: 101
if the mask is 0 : 000
then perm is 7 or : 111
so a mask of 5: 101
becomes perm 2: 010
and not what you want.
So I'm not sure how that translates to the first digit since i'm sure
you don't want a perm to come out 7555 using umask of 0222 but maybe
someone can enlighten
>
> As a relative newby here are some things I noted that I don't get.
>
> a) Previously, I made a group and added my users to it, editted fstab to
> allow gid for that group, chmoded the directory to 0544 and set the
> umask in fstab to be 0544 too. This almost worked. I was able to cd to
> my windoze directory, but I couldn ls -l it!
I don't remember how it works. 0544 gives you perms of 0255 or
-w-r-xr-x so the owner can't ls it as you can neither read nor
execute, but I'm surprised you could cd to it too... its confusing, i
know.
>
> b) When I created my new group bar and added my user foo to it with
> "adduser foo bar" it worked. When I issued the "groups" command it did
> not show bar as being one of the groups that foo belonged to. I
> rebooted, issued "groups" again and now foo is in bar. Seems to me it
> should know this right away without a reboot... (I'm showing my Windoze
> ancestry by rebooting all the time!)
you get your groups at login. Until you log out and log back in, you
won't get new groups. You don't need to reboot, just log out
everywhere and log back in.
>
> c) Even after this success, dmesg shows:
>
> NTFS volume version 3.1.
> NTFS-fs warning (device sda1): load_system_files(): Unsupported volume
> flags 0x4000 encountered.
> NTFS-fs error (device sda1): load_system_files(): Volume has unsupported
> flags set. Mounting read-only. Run chkdsk and mount in Windows.
i see that a lot and never have any problems. FWIW. but avoid writing
in ntfs if you can.
...
> > Another thing: If you also need write access onto ntfs, and want read access onto compressed files, then the ntfs-3g driver might be interesting for you. For newbies however, it might not be that easy to install... you need to make a package for stable yourself. On the other hand, if you'd need it, I can just do an update/recompile here on my system and send the resulting package to you via email.
is it in backports?
A
ntfs mount errors
On Fri, 3 Aug 2007 20:51:50 -0700
Andrew Sackville-West wrote:
> On Fri, Aug 03, 2007 at 11:17:21PM -0400, Phill Atwood wrote:
> >
> >
> >
> > Success. Although I can't say that I really understand. Setting
> > umask=0222 in the /etc/fstab file did the trick. I don't understand why
> > mounting a ro partition to a directory with just write permissions would
> > work. 0544 or 0555 seemed the more logical thing to try...
(...)
> So I'm not sure how that translates to the first digit since i'm sure
> you don't want a perm to come out 7555 using umask of 0222 but maybe
> someone can enlighten
Well, wikipedia says ;), the bitwise-inverted umask is bitwise ANDed with the *default "full permission"*, i.e. 666 for files and 777 for dirs. This should mean, 0666 and 0777, if I am understanding it right (see interpretation for missing digits in chmod(1)). Thus:
000 110 110 110 AND
not(000 010 010 010) =
000 110 110 110 AND
111 101 101 101 = 0444
For dirs, the result is 0555.
> > c) Even after this success, dmesg shows:
> >
> > NTFS volume version 3.1.
> > NTFS-fs warning (device sda1): load_system_files(): Unsupported volume
> > flags 0x4000 encountered.
(...)
> i see that a lot and never have any problems. FWIW. but avoid writing
> in ntfs if you can.
That's really strange ... but I'm pretty sure that's not debian-specific (as I found this on forums for all kinds of distros).
> > > Another thing: If you also need write access onto ntfs, and want read access onto compressed files, then the ntfs-3g driver might be interesting for you. For newbies however, it might not be that easy to install... you need to make a package for stable yourself. On the other hand, if you'd need it, I can just do an update/recompile here on my system and send the resulting package to you via email.
>
> is it in backports?
Yep, that's a good hint: ntfs-3g ver 1.516 (slightly outdated) is available if you add the line:
deb http://www.backports.org/debian etch-backports main contrib non-free
into your /etc/apt/sources.list, do apt-get update, and then install.
Cheers,
Stephan
--
ntfs mount errors
On Fri, Aug 03, 2007 at 11:17:21PM -0400, Phill Atwood wrote:
> I had run into ntfs-3g while googling earlier. It does intrigue me.
> Making my own package to install it is probably way over my head.
> Although, I would like to get into package maintenance. If this is not
> too big a piece to chew on I would be willing to take whatever time to
> try. I am sceptical that previous versions of Debian don't trust ntfs
> to write but these ntfs-3g guys do.
AFAIU ntfs-3g is a total rewrite of the (old) kernel ntfs driver. And
the guys seem pretty serious to me:
http://www.ntfs-3g.org/quality.html
>I also read that if you mount
> windows xp as vfat you can write to it. Even more sceptical.
What do you mean by that? You can safely mount fat partitions for a long
time now.
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
ntfs mount errors
On Aug 3, 2007, at 9:37 PM, Andrei Popescu wrote:
>> I also read that if you mount
>> windows xp as vfat you can write to it. Even more sceptical.
>
> What do you mean by that? You can safely mount fat partitions for a
> long
> time now.
Yup, been there, done that, it works fine. It has consequences for
the XP side, though -- VFAT doesn't support alternate data streams or
file permissions, so you lose some functionality. Those features are
mostly only useful if you have multiple users on one machine, though.
Note that you have to install XP from the start on a FAT partition --
Microsoft has tools to let you convert FAT to NTFS, but there's no
way to go back without reformatting.
A good alternative I've sometimes used is to create a second, FAT-
formatted partition and use it for stuff I want to access from both
operating systems.
--
ntfs mount errors
On Mon, Aug 06, 2007 at 09:52:17AM -0700, David Brodbeck wrote:
>
> On Aug 3, 2007, at 9:37 PM, Andrei Popescu wrote:
>>> I also read that if you mount
>>> windows xp as vfat you can write to it. Even more sceptical.
>>
>> What do you mean by that? You can safely mount fat partitions for a long
>> time now.
>
> Yup, been there, done that, it works fine. It has consequences for the XP
> side, though -- VFAT doesn't support alternate data streams or file
> permissions, so you lose some functionality. Those features are mostly
> only useful if you have multiple users on one machine, though.
>
> Note that you have to install XP from the start on a FAT partition --
> Microsoft has tools to let you convert FAT to NTFS, but there's no way to
> go back without reformatting.
>
> A good alternative I've sometimes used is to create a second, FAT-formatted
> partition and use it for stuff I want to access from both operating
> systems.
Unless you forget to copy the important stuff and have to reboot...
Recently I've been experimenting with ext2fsd (which despite its name
can also read ext3) and ntfs-3g.
Regards,
Andrei
--
If you can't explain it simply, you don't understand it well enough.
(Albert Einstein)
ntfs mount errors
> > >
> > > Further to my problem of not being able to automatically mount my
> > > windows xp partition and cd to it as a regular user.
> > >
> > > >from dmesg:
> > >
> > > NTFS driver 2.1.27 [Flags: R/W MODULE].
> > > NTFS volume version 3.1.
> > > NTFS-fs warning (device sda1): load_system_files(): Unsupported volume
> > > flags 0x4000 encountered.
> > > NTFS-fs warning (device sda1): load_system_files(): Volume has
> > > unsupported flags set. Will not be able to remount read-write. Run
> > > chkdsk and mount in Windows.
> >
> > ----
> >
> > Hi there,
> >
> > I have no information about what was discussed before, but to me this looks like: Boot into windoze. Click on Start->Execute (don't know how this is exactly called on English windoze) or open a command window (cmd.exe). There, type: chkdsk /f . Tell windoze you want it to check the disk at reboot. Reboot into windoze, and let chkdsk repair the disk. Then reboot into linux and see what happens.
> >
> > Cheers,
> >
> > Stephan
You were right. I did this. I ended up having to use fsutil to force
the partition to be dirty to get windoze to check it. It did. There
were no errors. However, when I rebooted to Linux I still have the same
problem. I can mount the partition, but I can only cd to it as root.
I tried googling the error msg above but not much. Maybe I need to
contact the developers who have written this ntfs support for linux.
How would I go about finding them?
Phill
--
ntfs mount errors
On Tue, 2007-31-07 at 21:14 +0200, Stephan Hachinger wrote:
> On Tue, 31 Jul 2007 14:26:41 -0400
> Phill Atwood wrote:
>
> >
> > Further to my problem of not being able to automatically mount my
> > windows xp partition and cd to it as a regular user.
> >
> > >from dmesg:
> >
> > NTFS driver 2.1.27 [Flags: R/W MODULE].
> > NTFS volume version 3.1.
> > NTFS-fs warning (device sda1): load_system_files(): Unsupported volume
> > flags 0x4000 encountered.
> > NTFS-fs warning (device sda1): load_system_files(): Volume has
> > unsupported flags set. Will not be able to remount read-write. Run
> > chkdsk and mount in Windows.
>
> ----
>
> Hi there,
>
> I have no information about what was discussed before, but to me this looks like: Boot into windoze. Click on Start->Execute (don't know how this is exactly called on English windoze) or open a command window (cmd.exe). There, type: chkdsk /f . Tell windoze you want it to check the disk at reboot. Reboot into windoze, and let chkdsk repair the disk. Then reboot into linux and see what happens.
>
> Cheers,
>
> Stephan
Thanks for helping me see what I needed to do. However, it did not
work. I had to use fsutil to force c: drive to be "dirty" so windoze
would check it. Finally it did and there were no errors. Rebooting
into linux and I still have the problem. ie. The windoze partition is
mounted automatically fine, but I can only cd to it if I am root.
Again, my /etc/fstab is:
# /etc/fstab: static file system information.
#
#
proc /proc proc defaults 0 0
/dev/sda1 /windoze ntfs user,auto,ro 0 0
/dev/sda2 / ext3 defaults,errors=remount-ro 0
1
/dev/sda8 /home ext3 defaults 0 2
/dev/sda7 /tmp ext3 defaults 0 2
/dev/sda5 /usr ext3 defaults 0 2
/dev/sda6 /var ext3 defaults 0 2
/dev/sda3 none swap sw 0 0
/dev/hda /media/cdrom0 udf,iso9660 user,noauto 0 0
I tried googling the ntfs error msg above but there isn't much.
Perhaps, I should try to contact the developers of this ntfs support for
linux. How would I go about that? Or are there other ideas? I
appreciate the help.
Thanks,
Phill
--
ntfs mount errors
(quote)
I still have the problem. ie. The windoze partition is
mounted automatically fine, but I can only cd to it if I am root.
(end quote)
Do:
man mount
Look at the 'Mount options for ntfs'. All your mysteries are explained there - for example:
"... By default, the files are owned by root and not readable by somebody else."
So you need to set the uid/gid and umask. You really want 'root' to be the owner anyway so I guess you only want to change the gid to the 'disk' group and make sure you have a sensible umask.
ntfs mount errors
On Wed, Aug 01, 2007 at 04:49:04AM +0200, pinniped wrote:
>
> (quote)
> I still have the problem. ie. The windoze partition is
> mounted automatically fine, but I can only cd to it if I am root.
> (end quote)
>
> Do:
> man mount
>
> Look at the 'Mount options for ntfs'. All your mysteries are explained
> there - for example:
>
> "... By default, the files are owned by root and not readable by somebody
> else."
>
> So you need to set the uid/gid and umask. You really want 'root' to be the
> owner anyway so I guess you only want to change the gid to the 'disk' group
> and make sure you have a sensible umask.
Be careful there, members of the 'disk' group can do nasty things on
your debian box too. Perhaps create a new group who can access the
windows partition, put those users into the group, then use the gid=
parameter in fstab. However, this doesn't affect the uid. I can't test
this further since I haven't run windows since 3.1 and never played with
ntfs.
Doug.
--