Re: NTFS 4 Terabyte drive problems on FreeBSD?
In the last episode (Feb 12), Scott Ballantyne said: Hi, I'm trying to mount a 4 TB drive (The Seagate Backup-Plus) on FreeBSD 9.0 Generic, using mount -t ntfs /dev/da0s1 /mnt It fails with: g_vfs_done() da1s1[READ(offset=0, length=1042)]error=22 mount_ntfs: /dev/da1s1 bad argument That's a strange length (1042). I would have expected a multiple of the device blocksize (4096 in the case of the Backup Plus). However, I can mount a 2 TB ntfs drive with no problem, using the same command, and the 4TB drive checks out fine in Windows. Does anyone know if this limitation exists, and if there is a work-around? I only need READ access to this drive. You can try the sysutils/fusefs-ntfs port; the ntfs code in the base system hasn't had much work done on it lately. -- Dan Nelson dnel...@allantgroup.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NTFS data recovery
On Mon, 9 Jul 2012 16:01:56 +, Graeme Dargie wrote: Hi All, I have been given a laptop to look at for a friend, the hard disk is close to death with a SMART error on POST. My initial thought was to just mount it on an Windows 7 machine and grab what I can from the drive. Bad idea. You cannot fully make sure that the disk's content isn't altered. There's no mount -o ro in Windows. Even worse, it might lead to more corruption during attempts to repair it. No joy Windows insists that the partition is RAW and I need to format it. Don't format it, it will massively decrease your chances for data recovery. Work with what you have, touch it as few as possible, use the proper tools. You won't find them on Windows. I can however mount it under FreeBSD without any problems, the directory structure appears to be intact but there are no files in the places I would expect to find them under the Users directory, I am guessing that these have somehow been deleted or perhaps the victim of a partial OEM recovery process. That's quite possible. Check df vs. du output and see if it magically fits, e. g. that the data is somewhere. Is there a way to scan the drive for deleted files from the command line or something from the ports tree that anyone can recommend to fulfil this requirement. Because it's about NTFS recovery, things are a bit complicated, but not impossible. I'd suggest to first make a copy of the disk using dd, then work with that copy. Do _NOT_ fiddle with the original disks! If dd doesn't work, try ddrescue and dd_rescue. There are programs in the sysutils/ntfsprogs port will be surely useful to dealing with the NTFS content. Then of course you'll find The Sleuth Kit very helpful. It's programs fls, dls and ils might be what you're searching for. Sadly the documentation has been moved into a web page. :-( Additionally, you may try magicrescue, recoverjpeg and foremost, maybe fatback (but I doubt it). Those are acting outside of the FS. For missing files, maybe you can find a differing MFT to check? I know there was something related in the documentation of the older versions of TSK, but as I said, that situation has disimproved. :-( Note that data recovery is a dirty job, it takes time and is therefore quite expensive if delegated to a company. In your case it means you'll have to invest MUCH TIME into getting the data back. I hope the files are worth it. The absence of a backup seems to imply the opposite. :-) Anyway, good luck! -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NTFS data recovery
On Mon, 9 Jul 2012 18:54:37 +0200 Polytropon articulated: On Mon, 9 Jul 2012 16:01:56 +, Graeme Dargie wrote: Hi All, I have been given a laptop to look at for a friend, the hard disk is close to death with a SMART error on POST. My initial thought was to just mount it on an Windows 7 machine and grab what I can from the drive. Bad idea. You cannot fully make sure that the disk's content isn't altered. There's no mount -o ro in Windows. Even worse, it might lead to more corruption during attempts to repair it. I have seen this work, but not on Windows 7. (based on Windows 2003 SP2) 1) switch off automount using the mountvol.exe command 2) present disk to Windows 2003 SP2 3) do not mount the disk 4) launch diskpart 5) do a list disk and list volume 6) note down the correct volume number 7) in diskpart do a select volume X (where X is the correct volume number) 8) then in diskpart doa att vol set readonly 9) then in diskpart do a detail vol and ensure the readonly bit is set 10) then you can mount the volume, the volume will be readonly Interestingly enough, only a few months ago, I used SpinRite 6 to recover an 80 Gb disk that was supposedly fried. If the HD can be seen by the system hardware, SpinRite has a fighting chance of recovering it. It took a week but it got all of the data back. I did take the HD out of the original PC and put it into a backup unit since I could not tie that PC up for an extended time. SpinRite does not need a super high speed machine to work off of. Good luck, you'll need it. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ This is supposed to be a happy occasion. Let's not BICKER and ARGUE over who killed who! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NTFS data recovery
Graeme Dargie arab at tangerine-army.co.uk writes: ... Is there a way to scan the drive for deleted files from the command line or something from the ports tree that anyone can recommend to fulfil this requirement. testdisk http://www.freebsd.org/cgi/url.cgi?ports/sysutils/testdisk/pkg-descr I would suggest you compile it before use (otherwise grab a package). jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NTFS data recovery
jb jb.1234abcd at gmail.com writes: ... ntfs utilities http://www.freebsd.org/cgi/url.cgi?ports/sysutils/ntfsprogs/pkg-descr I would suggest you compile it before use (otherwise grab a package). jb ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: NTFS data recovery
I have been given a laptop to look at for a friend, the hard disk is close to death with a SMART error on POST. My initial thought was to just mount it on an Windows 7 machine and grab what I can from the drive. No joy Windows insists that the partition is RAW and I need to format it. I can however mount it under FreeBSD without any problems, the directory structure appears to be intact but there are no files in the places I would expect to find them under the Users directory, I am guessing that these have somehow been deleted or perhaps the victim of a partial OEM recovery process. Is there a way to scan the drive for deleted files from the command line or something from the ports tree that anyone can recommend to fulfil this requirement. get other disk or just use free space on large filesystem and do dd if=/dev/baddisk of=file bs=64k conv=noerror,sync then - after having backup, try to salvage things ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: ntfs-3g problem
On Mon, 15 Oct 2007 15:30:41 -0400 (EDT) Monah Baki [EMAIL PROTECTED] wrote: I copied 7 files totaling 280GB. I then rebooted the freebsd box (without unmounting the ntfs partition) and then when I tried to mount the partition mount -t ntfs-3g /dev/da0s1 /mnt/windows), all files where missing. I could not even see them on the windows server. Yet df -h shows almost 300GB of diskspace used Thank you The problem occured because you did not umount the partition. As far as recovering goes, i have no idea if it is possible to recover the files from the ntfs partition since only the part that you see was written to it and nothing else. Ivan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntfs-3g problem
On Mon, Oct 15, 2007 at 11:43:48AM -0400, Monah Baki wrote: Hi all, We're in the process of copying 600GB to a ntfs volume on freebsd 6.2. I rebooted the server and now all 200GB of data that I copied are no longer visible. If I issue the command df -h, I see 200GB used. How can I retrieve them. I am not quite sure just what you are staying. But, if I sort of get it, probably you only have to close off the file that you are writing - or is it not one big file. jerry I installed from ports fuse-ntfs and ntfsprogs Thanks BSD Networking, Microsoft Notworking ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntfs-3g problem
I copied 7 files totaling 280GB. I then rebooted the freebsd box (without unmounting the ntfs partition) and then when I tried to mount the partition mount -t ntfs-3g /dev/da0s1 /mnt/windows), all files where missing. I could not even see them on the windows server. Yet df -h shows almost 300GB of diskspace used Thank you On Mon, Oct 15, 2007 at 11:43:48AM -0400, Monah Baki wrote: Hi all, We're in the process of copying 600GB to a ntfs volume on freebsd 6.2. I rebooted the server and now all 200GB of data that I copied are no longer visible. If I issue the command df -h, I see 200GB used. How can I retrieve them. I am not quite sure just what you are staying. But, if I sort of get it, probably you only have to close off the file that you are writing - or is it not one big file. jerry I installed from ports fuse-ntfs and ntfsprogs Thanks BSD Networking, Microsoft Notworking ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] BSD Networking, Microsoft Notworking ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G mount during boot
Well, I gave up using /etc/fstab to mount NTFS partitions at boot time a
couple of months ago when I realized that it's not the correct way to do it
(so I also wrote an rc.d script to do the job, but I'll talk about it
later). However, I recently looked at fusefs-ntfs source files, and as you
can see from
http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/fusefs-ntfs/Makefile
in revision 1.19, there are changes (installing a symlink) to allow using
/etc/fstab to mount NTFS partitions at boot. So I thought that maybe now
it's okay to use /etc/fstab. Anyway, if it's still not possible to use
/etc/fstab, then what does that sentence mean in the revision 1.19 of
fusefs-ntfs Makefile (again, see the URL above)?
The only way I can see that working is if /usr/local/modules in
kern.modules_path /before/ mount -a is executed by /etc/rc.d/mount. Which
means there should be a line:
kern.module_path=/boot/kernel;/boot/modules;/usr/local/modules
in /etc/sysctl.conf on your machine.
Also, mount_ntfs-3g should be able to load the module dynamically.
My /etc/sysctl.conf is basically empty; it's all the usual default
comments. Nothing is specified there.
Another question is why, even after loading the kernel module (see the
'dmesg -a' output below), it is not possible to mount the NTFS partition?
--
[EMAIL PROTECTED] ~]$ dmesg -a
...
Starting fusefs.
fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8
...
Mounting late file systems:
fuse: failed to exec mount program: No such file or directory
--
What does ls -l /sbin/mount_ntfs-3g say?
There is no /sbin/mount_ntfs-3g. But /usr/sbin/mount_ntfs-3g exists
and is a symlink to /usr/local/bin/ntfs-3g. I'm not sure whether it's
relevant to your question, but I had made /sbin/mount_ntfs-3g a
symlink to /usr/local/bin/ntfs-3g myself, and that also was not
working (but I had tired it with the previous version of ntfs-3g not
the one currently installed).
This output from /var/log/messages is also interesting, showing that
ntfs-3g has indeed been run and that it has mounted my Windows partition
(but I don't see it mounted)!
--
[EMAIL PROTECTED] ~]$ cat /var/log/messages
...
Oct 6 14:22:40 pasargadae kernel: Trying to mount root from
ufs:/dev/ad0s2a Oct 6 14:22:45 pasargadae kernel: fuse4bsd: version
0.3.9-pre1, FUSE ABI 7.8
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Version 1.913
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Mounted /dev/ad0s1 (Read-Write,
label , NTFS 3.0)
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Cmdline options: (null)
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Mount options:
noatime,silent,allow_other ,fsname=/dev/ad0s1
...
--
And I didn't know about the /boot/modules way. Could you please ellaborate
more? Is it a different way to load kernel modules than using
/boot/loader.conf? When should one use that?
And now, about coming back to using an rc.d script...After failing to use
/etc/fstab, I wrote this script to mount the partition at boot time.
However, this also does not work!
--
#!/bin/sh
#
# PROVIDE: ntfsmount
# REQUIRE: fusefs
#
. /etc/rc.subr
name=ntfsmount
rcvar=${name}_enable
command=/usr/sbin/mount_ntfs-3g
command_args=/dev/ad0s1 /mnt/windows -o locale=en_US.UTF-8
Does /mnt/windows exist?
Anything interesting with `sh -x /usr/local/etc/rc.d/ntfsmount' ?
Yes, /mnt/windows exists. Nothing interesting as far as I could
understand the output of 'sh -x /usr/local/etc/rc.d/ntfsmount'. What
specifically do I have to look for?
If I find some more time, I'll play around with it.
--
Mel
Thanks a lot :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G mount during boot
Well, I gave up using /etc/fstab to mount NTFS partitions at boot time a
couple of months ago when I realized that it's not the correct way to do it
(so I also wrote an rc.d script to do the job, but I'll talk about it
later). However, I recently looked at fusefs-ntfs source files, and as you
can see from
http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/fusefs-ntfs/Makefile
in revision 1.19, there are changes (installing a symlink) to allow using
/etc/fstab to mount NTFS partitions at boot. So I thought that maybe now
it's okay to use /etc/fstab. Anyway, if it's still not possible to use
/etc/fstab, then what does that sentence mean in the revision 1.19 of
fusefs-ntfs Makefile (again, see the URL above)?
The only way I can see that working is if /usr/local/modules in
kern.modules_path /before/ mount -a is executed by /etc/rc.d/mount. Which
means there should be a line:
kern.module_path=/boot/kernel;/boot/modules;/usr/local/modules
in /etc/sysctl.conf on your machine.
Also, mount_ntfs-3g should be able to load the module dynamically.
My /etc/sysctl.conf is basically empty; it's all the usual default
comments. Nothing is specified there.
Another question is why, even after loading the kernel module (see the
'dmesg -a' output below), it is not possible to mount the NTFS partition?
--
[EMAIL PROTECTED] ~]$ dmesg -a
...
Starting fusefs.
fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8
...
Mounting late file systems:
fuse: failed to exec mount program: No such file or directory
--
What does ls -l /sbin/mount_ntfs-3g say?
There is no /sbin/mount_ntfs-3g. But /usr/sbin/mount_ntfs-3g exists
and is a symlink to /usr/local/bin/ntfs-3g.
I'm not sure whether it's relevant to your question, but I had made
/sbin/mount_ntfs-3g a symlink to /usr/local/bin/ntfs-3g myself, and
that also was not working (but I had tired it with the previous
version of ntfs-3g not the one currently installed).
This output from /var/log/messages is also interesting, showing that
ntfs-3g has indeed been run and that it has mounted my Windows partition
(but I don't see it mounted)!
--
[EMAIL PROTECTED] ~]$ cat /var/log/messages
...
Oct 6 14:22:40 pasargadae kernel: Trying to mount root from
ufs:/dev/ad0s2a Oct 6 14:22:45 pasargadae kernel: fuse4bsd: version
0.3.9-pre1, FUSE ABI 7.8
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Version 1.913
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Mounted /dev/ad0s1 (Read-Write,
label , NTFS 3.0)
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Cmdline options: (null)
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Mount options:
noatime,silent,allow_other ,fsname=/dev/ad0s1
...
--
And I didn't know about the /boot/modules way. Could you please ellaborate
more? Is it a different way to load kernel modules than using
/boot/loader.conf? When should one use that?
And now, about coming back to using an rc.d script...After failing to use
/etc/fstab, I wrote this script to mount the partition at boot time.
However, this also does not work!
--
#!/bin/sh
#
# PROVIDE: ntfsmount
# REQUIRE: fusefs
#
. /etc/rc.subr
name=ntfsmount
rcvar=${name}_enable
command=/usr/sbin/mount_ntfs-3g
command_args=/dev/ad0s1 /mnt/windows -o locale=en_US.UTF-8
Does /mnt/windows exist?
Anything interesting with `sh -x /usr/local/etc/rc.d/ntfsmount' ?
Yes, /mnt/windows exists. Nothing interesting as far as I could
understand the output of 'sh -x /usr/local/etc/rc.d/ntfsmount'. What
specifically do I have to look for?
If I find some more time, I'll play around with it.
--
Mel
Thanks a lot :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G mount during boot
On 10/7/07, Craig Butler [EMAIL PROTECTED] wrote:
Novembre wrote:
On 10/7/07, Mel [EMAIL PROTECTED] wrote:
On Sunday 07 October 2007 10:00:35 Novembre wrote:
On 10/7/07, Doug Barton [EMAIL PROTECTED] wrote:
On Sun, 7 Oct 2007, Novembre wrote:
The first error above is because the fuse kernel module is not yet
loaded.
Well isn't it sort of pointless to proceed until you get the kernel
module loaded at boot time and then see what happens next?
Oh, the kernel module IS loaded as shown in 'dmesg -a' and in
/var/log/messages. However, it can't be loaded unless / and /usr file
systems are mounted.
Filesystems that need modules from anywhere else then the root partition
cannot be loaded from /etc/fstab.
Either make fusefs-kmod install in /boot/modules
(echo 'KMOD_DIR=/boot/modules'
/usr/ports/sysutils/fusefs-kmod/Makefile.local) or mount the filesystem
using an rc(8) script in /usr/local/etc/rc.d/.
In the end you do not really care whether it's mounted 20 seconds or 1
second
before login prompt is available.
--
Mel
Well, I gave up using /etc/fstab to mount NTFS partitions at boot time a
couple of months ago when I realized that it's not the correct way to do it
(so I also wrote an rc.d script to do the job, but I'll talk about it
later). However, I recently looked at fusefs-ntfs source files, and as you
can see from
http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/fusefs-ntfs/Makefile in
revision 1.19, there are changes (installing a symlink) to allow using
/etc/fstab to mount NTFS partitions at boot. So I thought that maybe now
it's okay to use /etc/fstab. Anyway, if it's still not possible to use
/etc/fstab, then what does that sentence mean in the revision 1.19 of
fusefs-ntfs Makefile (again, see the URL above)?
Another question is why, even after loading the kernel module (see the
'dmesg -a' output below), it is not possible to mount the NTFS partition?
--
[EMAIL PROTECTED] ~]$ dmesg -a
...
Starting fusefs.
fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8
...
Mounting late file systems:
fuse: failed to exec mount program: No such file or directory
--
This output from /var/log/messages is also interesting, showing that ntfs-3g
has indeed been run and that it has mounted my Windows partition (but I
don't see it mounted)!
--
[EMAIL PROTECTED] ~]$ cat /var/log/messages
...
Oct 6 14:22:40 pasargadae kernel: Trying to mount root from ufs:/dev/ad0s2a
Oct 6 14:22:45 pasargadae kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI
7.8
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Version 1.913
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Mounted /dev/ad0s1 (Read-Write,
label , NTFS 3.0)
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Cmdline options: (null)
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Mount options:
noatime,silent,allow_other ,fsname=/dev/ad0s1
...
--
And I didn't know about the /boot/modules way. Could you please ellaborate
more? Is it a different way to load kernel modules than using
/boot/loader.conf? When should one use that?
And now, about coming back to using an rc.d script...After failing to use
/etc/fstab, I wrote this script to mount the partition at boot time.
However, this also does not work!
--
#!/bin/sh
#
# PROVIDE: ntfsmount
# REQUIRE: fusefs
#
. /etc/rc.subr
name=ntfsmount
rcvar=${name}_enable
command=/usr/sbin/mount_ntfs-3g
command_args=/dev/ad0s1 /mnt/windows -o locale=en_US.UTF-8
load_rc_config $name
: ${ntfsmount_enable=NO}
run_rc_command $1
--
I have made this script executable and have put ' ntfsmount_enable=YES '
in my /etc/rc.conf. So basically, I'm out of ideas now, and I need the
experts' help in this case. I think this problem is way above my current
knowledge of FreeBSD.
Thanks for your help :)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Wow thats a lot of work.
one liner in /etc/rc.local
/usr/sbin/mount_ntfs-3g /dev/ad0s1 /mnt/windows -o locale=en_US.UTF-8
Job Done :p
This email has been handled by lerwick.hopto.org mail server
and has been scanned by 3 virus killers and spamassassin
Are you sure it's going to work? My rc.d script is doing just that and
it's not working. Are you using it yourself to mount any NTFS
partition at boot time?
Thanks :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G mount during boot
On Sun, 7 Oct 2007, Novembre wrote: The first error above is because the fuse kernel module is not yet loaded. Well isn't it sort of pointless to proceed until you get the kernel module loaded at boot time and then see what happens next? -- This .signature sanitized for your protection ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G mount during boot
Oh, the kernel module IS loaded as shown in 'dmesg -a' and in /var/log/messages. However, it can't be loaded unless / and /usr file systems are mounted. That's what I meant in my post when I said the first error above is because the fuse kernel module is not yet loaded, since the mounting comes first. Indeed, 'kldstat' shows that it's loaded. My point was, after mounting / and /usr, and after loading fuse.ko, why do I get the second error message above Mounting late file systems: fuse: failed to exec mount program: No such file or directory in 'dmesg -a' when 'ps -ax' and /var/log/message show that ntfs-3g has been run? Why my Windows 2000 partition is not mounted then if ntfs-3g is running? Thanks :) On 10/7/07, Doug Barton [EMAIL PROTECTED] wrote: On Sun, 7 Oct 2007, Novembre wrote: The first error above is because the fuse kernel module is not yet loaded. Well isn't it sort of pointless to proceed until you get the kernel module loaded at boot time and then see what happens next? -- This .signature sanitized for your protection ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G mount during boot
On Sunday 07 October 2007 10:00:35 Novembre wrote: On 10/7/07, Doug Barton [EMAIL PROTECTED] wrote: On Sun, 7 Oct 2007, Novembre wrote: The first error above is because the fuse kernel module is not yet loaded. Well isn't it sort of pointless to proceed until you get the kernel module loaded at boot time and then see what happens next? Oh, the kernel module IS loaded as shown in 'dmesg -a' and in /var/log/messages. However, it can't be loaded unless / and /usr file systems are mounted. Filesystems that need modules from anywhere else then the root partition cannot be loaded from /etc/fstab. Either make fusefs-kmod install in /boot/modules (echo 'KMOD_DIR=/boot/modules' /usr/ports/sysutils/fusefs-kmod/Makefile.local) or mount the filesystem using an rc(8) script in /usr/local/etc/rc.d/. In the end you do not really care whether it's mounted 20 seconds or 1 second before login prompt is available. -- Mel ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G mount during boot
On 10/7/07, Mel [EMAIL PROTECTED] wrote:
On Sunday 07 October 2007 10:00:35 Novembre wrote:
On 10/7/07, Doug Barton [EMAIL PROTECTED] wrote:
On Sun, 7 Oct 2007, Novembre wrote:
The first error above is because the fuse kernel module is not yet
loaded.
Well isn't it sort of pointless to proceed until you get the kernel
module loaded at boot time and then see what happens next?
Oh, the kernel module IS loaded as shown in 'dmesg -a' and in
/var/log/messages. However, it can't be loaded unless / and /usr file
systems are mounted.
Filesystems that need modules from anywhere else then the root partition
cannot be loaded from /etc/fstab.
Either make fusefs-kmod install in /boot/modules
(echo 'KMOD_DIR=/boot/modules'
/usr/ports/sysutils/fusefs-kmod/Makefile.local) or mount the filesystem
using an rc(8) script in /usr/local/etc/rc.d/.
In the end you do not really care whether it's mounted 20 seconds or 1
second
before login prompt is available.
--
Mel
Well, I gave up using /etc/fstab to mount NTFS partitions at boot time a
couple of months ago when I realized that it's not the correct way to do it
(so I also wrote an rc.d script to do the job, but I'll talk about it
later). However, I recently looked at fusefs-ntfs source files, and as you
can see from
http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/fusefs-ntfs/Makefile in
revision 1.19, there are changes (installing a symlink) to allow using
/etc/fstab to mount NTFS partitions at boot. So I thought that maybe now
it's okay to use /etc/fstab. Anyway, if it's still not possible to use
/etc/fstab, then what does that sentence mean in the revision 1.19 of
fusefs-ntfs Makefile (again, see the URL above)?
Another question is why, even after loading the kernel module (see the
'dmesg -a' output below), it is not possible to mount the NTFS partition?
--
[EMAIL PROTECTED] ~]$ dmesg -a
...
Starting fusefs.
fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8
...
Mounting late file systems:
fuse: failed to exec mount program: No such file or directory
--
This output from /var/log/messages is also interesting, showing that ntfs-3g
has indeed been run and that it has mounted my Windows partition (but I
don't see it mounted)!
--
[EMAIL PROTECTED] ~]$ cat /var/log/messages
...
Oct 6 14:22:40 pasargadae kernel: Trying to mount root from ufs:/dev/ad0s2a
Oct 6 14:22:45 pasargadae kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI
7.8
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Version 1.913
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Mounted /dev/ad0s1 (Read-Write,
label , NTFS 3.0)
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Cmdline options: (null)
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Mount options:
noatime,silent,allow_other ,fsname=/dev/ad0s1
...
--
And I didn't know about the /boot/modules way. Could you please ellaborate
more? Is it a different way to load kernel modules than using
/boot/loader.conf? When should one use that?
And now, about coming back to using an rc.d script...After failing to use
/etc/fstab, I wrote this script to mount the partition at boot time.
However, this also does not work!
--
#!/bin/sh
#
# PROVIDE: ntfsmount
# REQUIRE: fusefs
#
. /etc/rc.subr
name=ntfsmount
rcvar=${name}_enable
command=/usr/sbin/mount_ntfs-3g
command_args=/dev/ad0s1 /mnt/windows -o locale=en_US.UTF-8
load_rc_config $name
: ${ntfsmount_enable=NO}
run_rc_command $1
--
I have made this script executable and have put ' ntfsmount_enable=YES '
in my /etc/rc.conf. So basically, I'm out of ideas now, and I need the
experts' help in this case. I think this problem is way above my current
knowledge of FreeBSD.
Thanks for your help :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G mount during boot
On Sunday 07 October 2007 20:07:00 Novembre wrote:
On 10/7/07, Mel [EMAIL PROTECTED] wrote:
On Sunday 07 October 2007 10:00:35 Novembre wrote:
On 10/7/07, Doug Barton [EMAIL PROTECTED] wrote:
On Sun, 7 Oct 2007, Novembre wrote:
The first error above is because the fuse kernel module is not yet
loaded.
Well isn't it sort of pointless to proceed until you get the kernel
module loaded at boot time and then see what happens next?
Oh, the kernel module IS loaded as shown in 'dmesg -a' and in
/var/log/messages. However, it can't be loaded unless / and /usr file
systems are mounted.
Filesystems that need modules from anywhere else then the root partition
cannot be loaded from /etc/fstab.
Either make fusefs-kmod install in /boot/modules
(echo 'KMOD_DIR=/boot/modules'
/usr/ports/sysutils/fusefs-kmod/Makefile.local) or mount the filesystem
using an rc(8) script in /usr/local/etc/rc.d/.
In the end you do not really care whether it's mounted 20 seconds or 1
second
before login prompt is available.
--
Mel
Well, I gave up using /etc/fstab to mount NTFS partitions at boot time a
couple of months ago when I realized that it's not the correct way to do it
(so I also wrote an rc.d script to do the job, but I'll talk about it
later). However, I recently looked at fusefs-ntfs source files, and as you
can see from
http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/fusefs-ntfs/Makefile
in revision 1.19, there are changes (installing a symlink) to allow using
/etc/fstab to mount NTFS partitions at boot. So I thought that maybe now
it's okay to use /etc/fstab. Anyway, if it's still not possible to use
/etc/fstab, then what does that sentence mean in the revision 1.19 of
fusefs-ntfs Makefile (again, see the URL above)?
The only way I can see that working is if /usr/local/modules in
kern.modules_path /before/ mount -a is executed by /etc/rc.d/mount. Which
means there should be a line:
kern.module_path=/boot/kernel;/boot/modules;/usr/local/modules
in /etc/sysctl.conf on your machine.
Also, mount_ntfs-3g should be able to load the module dynamically.
Another question is why, even after loading the kernel module (see the
'dmesg -a' output below), it is not possible to mount the NTFS partition?
--
[EMAIL PROTECTED] ~]$ dmesg -a
...
Starting fusefs.
fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8
...
Mounting late file systems:
fuse: failed to exec mount program: No such file or directory
--
What does ls -l /sbin/mount_ntfs-3g say?
This output from /var/log/messages is also interesting, showing that
ntfs-3g has indeed been run and that it has mounted my Windows partition
(but I don't see it mounted)!
--
[EMAIL PROTECTED] ~]$ cat /var/log/messages
...
Oct 6 14:22:40 pasargadae kernel: Trying to mount root from
ufs:/dev/ad0s2a Oct 6 14:22:45 pasargadae kernel: fuse4bsd: version
0.3.9-pre1, FUSE ABI 7.8
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Version 1.913
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Mounted /dev/ad0s1 (Read-Write,
label , NTFS 3.0)
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Cmdline options: (null)
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Mount options:
noatime,silent,allow_other ,fsname=/dev/ad0s1
...
--
And I didn't know about the /boot/modules way. Could you please ellaborate
more? Is it a different way to load kernel modules than using
/boot/loader.conf? When should one use that?
And now, about coming back to using an rc.d script...After failing to use
/etc/fstab, I wrote this script to mount the partition at boot time.
However, this also does not work!
--
#!/bin/sh
#
# PROVIDE: ntfsmount
# REQUIRE: fusefs
#
. /etc/rc.subr
name=ntfsmount
rcvar=${name}_enable
command=/usr/sbin/mount_ntfs-3g
command_args=/dev/ad0s1 /mnt/windows -o locale=en_US.UTF-8
Does /mnt/windows exist?
Anything interesting with `sh -x /usr/local/etc/rc.d/ntfsmount' ?
If I find some more time, I'll play around with it.
--
Mel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G mount during boot
Novembre wrote:
On 10/7/07, Mel [EMAIL PROTECTED] wrote:
On Sunday 07 October 2007 10:00:35 Novembre wrote:
On 10/7/07, Doug Barton [EMAIL PROTECTED] wrote:
On Sun, 7 Oct 2007, Novembre wrote:
The first error above is because the fuse kernel module is not yet
loaded.
Well isn't it sort of pointless to proceed until you get the kernel
module loaded at boot time and then see what happens next?
Oh, the kernel module IS loaded as shown in 'dmesg -a' and in
/var/log/messages. However, it can't be loaded unless / and /usr file
systems are mounted.
Filesystems that need modules from anywhere else then the root partition
cannot be loaded from /etc/fstab.
Either make fusefs-kmod install in /boot/modules
(echo 'KMOD_DIR=/boot/modules'
/usr/ports/sysutils/fusefs-kmod/Makefile.local) or mount the filesystem
using an rc(8) script in /usr/local/etc/rc.d/.
In the end you do not really care whether it's mounted 20 seconds or 1
second
before login prompt is available.
--
Mel
Well, I gave up using /etc/fstab to mount NTFS partitions at boot time a
couple of months ago when I realized that it's not the correct way to do it
(so I also wrote an rc.d script to do the job, but I'll talk about it
later). However, I recently looked at fusefs-ntfs source files, and as you
can see from
http://www.freebsd.org/cgi/cvsweb.cgi/ports/sysutils/fusefs-ntfs/Makefile in
revision 1.19, there are changes (installing a symlink) to allow using
/etc/fstab to mount NTFS partitions at boot. So I thought that maybe now
it's okay to use /etc/fstab. Anyway, if it's still not possible to use
/etc/fstab, then what does that sentence mean in the revision 1.19 of
fusefs-ntfs Makefile (again, see the URL above)?
Another question is why, even after loading the kernel module (see the
'dmesg -a' output below), it is not possible to mount the NTFS partition?
--
[EMAIL PROTECTED] ~]$ dmesg -a
...
Starting fusefs.
fuse4bsd: version 0.3.9-pre1, FUSE ABI 7.8
...
Mounting late file systems:
fuse: failed to exec mount program: No such file or directory
--
This output from /var/log/messages is also interesting, showing that ntfs-3g
has indeed been run and that it has mounted my Windows partition (but I
don't see it mounted)!
--
[EMAIL PROTECTED] ~]$ cat /var/log/messages
...
Oct 6 14:22:40 pasargadae kernel: Trying to mount root from ufs:/dev/ad0s2a
Oct 6 14:22:45 pasargadae kernel: fuse4bsd: version 0.3.9-pre1, FUSE ABI
7.8
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Version 1.913
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Mounted /dev/ad0s1 (Read-Write,
label , NTFS 3.0)
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Cmdline options: (null)
Oct 6 14:22:45 pasargadae ntfs-3g[811]: Mount options:
noatime,silent,allow_other ,fsname=/dev/ad0s1
...
--
And I didn't know about the /boot/modules way. Could you please ellaborate
more? Is it a different way to load kernel modules than using
/boot/loader.conf? When should one use that?
And now, about coming back to using an rc.d script...After failing to use
/etc/fstab, I wrote this script to mount the partition at boot time.
However, this also does not work!
--
#!/bin/sh
#
# PROVIDE: ntfsmount
# REQUIRE: fusefs
#
. /etc/rc.subr
name=ntfsmount
rcvar=${name}_enable
command=/usr/sbin/mount_ntfs-3g
command_args=/dev/ad0s1 /mnt/windows -o locale=en_US.UTF-8
load_rc_config $name
: ${ntfsmount_enable=NO}
run_rc_command $1
--
I have made this script executable and have put ' ntfsmount_enable=YES '
in my /etc/rc.conf. So basically, I'm out of ideas now, and I need the
experts' help in this case. I think this problem is way above my current
knowledge of FreeBSD.
Thanks for your help :)
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Wow thats a lot of work.
one liner in /etc/rc.local
/usr/sbin/mount_ntfs-3g /dev/ad0s1 /mnt/windows -o locale=en_US.UTF-8
Job Done :p
This email has been handled by lerwick.hopto.org mail server
and has been scanned by 3 virus killers and spamassassin
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G not mounting the partition during boot
On 8/8/07, Novembre [EMAIL PROTECTED] wrote: On 8/7/07, Rakhesh Sasidharan [EMAIL PROTECTED] wrote: Starting ntfsmount. /etc/rc: DEBUG: run_rc_command: _doit: /usr/local/bin/ntfs-3g /dev/ad0s1 /mnt/w indows fuse: failed to exec mount program: No such file or directory -- I don't exactly know what it means by fuse: failed to exec mount program: No such file or directory since /usr/local/bin/ntfs-3g exists, /dev/ad0s1 is my Windows 2000 partition, and I have created /mnt/windows myself. Why is the mount point /mnt/windows broken over two lines? If that's the actual output from fuse (and not broken coz of some wrapping while emailing) then that could be the problem. Regards, Rakhesh The line is broken, since it had reached the end of line. It just wrapped the rest of the line into the next line. I don't think it's the actual output from fusefs. Here's an interesting thing though: # cat /var/log/messages ... Aug 8 23:37:10 homedesktop root: /etc/rc: INFO: checkyesno: ntfsmount_enable is set to YES. Aug 8 23:37:10 homedesktop root: /etc/rc: INFO: run_rc_command: _doit: /usr/local/bin/ntfs-3g /dev/ad0s1 /mnt/windows -o locale=en_US.UTF-8 Aug 8 23:37:11 homedesktop ntfs-3g[923]: Version 1.710 Aug 8 23:37:11 homedesktop ntfs-3g[923]: Mounted /dev/ad0s1 (Read-Write, label , NTFS 3.0) Aug 8 23:37:11 homedesktop ntfs-3g[923]: Cmdline options: locale=en_US.UTF-8 Aug 8 23:37:11 homedesktop ntfs-3g[923]: Mount options: noatime,silent,allow_other,fsname=/dev/ad0s1 ... So it seems the mount process was successful?! Indeed, /dev/fuse0 was created as well... Then why do I see the following message when the system boots? - fuse: failed to exec mount program: No such file or directory - I'm not sure if this is something to be worried about or not, but there are two spaces between ntfs-3f and /dev/ad0s1 when the command runs. I have set up the startup script as mentioned before, so I'm not sure what's happening here as well... Thanks I didn't get any replies, so I'll send this again. Hopefully, someone will help. The problem is explained above... Thanks :) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G not mounting the partition during boot
On 8/7/07, Rakhesh Sasidharan [EMAIL PROTECTED] wrote: Starting ntfsmount. /etc/rc: DEBUG: run_rc_command: _doit: /usr/local/bin/ntfs-3g /dev/ad0s1 /mnt/w indows fuse: failed to exec mount program: No such file or directory -- I don't exactly know what it means by fuse: failed to exec mount program: No such file or directory since /usr/local/bin/ntfs-3g exists, /dev/ad0s1 is my Windows 2000 partition, and I have created /mnt/windows myself. Why is the mount point /mnt/windows broken over two lines? If that's the actual output from fuse (and not broken coz of some wrapping while emailing) then that could be the problem. Regards, Rakhesh The line is broken, since it had reached the end of line. It just wrapped the rest of the line into the next line. I don't think it's the actual output from fusefs. Here's an interesting thing though: # cat /var/log/messages ... Aug 8 23:37:10 homedesktop root: /etc/rc: INFO: checkyesno: ntfsmount_enable is set to YES. Aug 8 23:37:10 homedesktop root: /etc/rc: INFO: run_rc_command: _doit: /usr/local/bin/ntfs-3g /dev/ad0s1 /mnt/windows -o locale=en_US.UTF-8 Aug 8 23:37:11 homedesktop ntfs-3g[923]: Version 1.710 Aug 8 23:37:11 homedesktop ntfs-3g[923]: Mounted /dev/ad0s1 (Read-Write, label , NTFS 3.0) Aug 8 23:37:11 homedesktop ntfs-3g[923]: Cmdline options: locale=en_US.UTF-8 Aug 8 23:37:11 homedesktop ntfs-3g[923]: Mount options: noatime,silent,allow_other,fsname=/dev/ad0s1 ... So it seems the mount process was successful?! Indeed, /dev/fuse0 was created as well... Then why do I see the following message when the system boots? - fuse: failed to exec mount program: No such file or directory - I'm not sure if this is something to be worried about or not, but there are two spaces between ntfs-3f and /dev/ad0s1 when the command runs. I have set up the startup script as mentioned before, so I'm not sure what's happening here as well... Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G not mounting the partition during boot
On 8/6/07, Philip M. Gollucci [EMAIL PROTECTED] wrote:
Novembre wrote:
rcvar=`set_rcvar`
That should be
rcvar=${name}_enable
Because of this, your script did not run because the rc system didn't
detect it correctly.
Try setting
rc_debug=YES
and/or
rc_info=YES
in /etc/rc.conf
to see more of whats happening.
command=ntfs-3g /dev/ad0s1 /mnt/windows ntfs-3g /dev/ad0s1
/mnt/windows -o locale=en_US.UTF-8
Also $command is special, you should use another variable
$command_args (which is also special) for the arguments/options.
Of course, you can circument these if you know what you are doing.
When in doubt, look at other rc scripts like apache22's or others that
might seem like they would do a lot.
Finally, in /etc/rc.subr is _very_
--
Philip M. Gollucci ([EMAIL PROTECTED]) 323.219.4708
Senior System Admin - Riderway, Inc. http://riderway.com
1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF
Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.
Hi,
I did not write this script myself. I was searching the net for a solution
to this problem, and I found a thread on ntfs-3g forums where somebody had
posted this script. Apparently, it had worked for him and some other people.
I just copied and pasted the script. But since I wanted to know more about
startup scripts, I looked at the manual page for rc.d, and a sample script
there looked exacly liked this one. That's why I thought that the script
that I have is going to work as well.
I made the changes and am going to reboot the machine now. If they work,
i'll post the results...
Thanks a lot :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G not mounting the partition during boot
On 8/7/07, Novembre [EMAIL PROTECTED] wrote:
On 8/6/07, Philip M. Gollucci [EMAIL PROTECTED] wrote:
Novembre wrote:
rcvar=`set_rcvar`
That should be
rcvar=${name}_enable
Because of this, your script did not run because the rc system didn't
detect it correctly.
Try setting
rc_debug=YES
and/or
rc_info=YES
in /etc/rc.conf
to see more of whats happening.
command=ntfs-3g /dev/ad0s1 /mnt/windows ntfs-3g /dev/ad0s1
/mnt/windows -o locale=en_US.UTF-8
Also $command is special, you should use another variable
$command_args (which is also special) for the arguments/options.
Of course, you can circument these if you know what you are doing.
When in doubt, look at other rc scripts like apache22's or others that
might seem like they would do a lot.
Finally, in /etc/rc.subr is _very_
--
Philip M. Gollucci ( [EMAIL PROTECTED]) 323.219.4708
Senior System Admin - Riderway, Inc. http://riderway.com
1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF
Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.
Hi,
I did not write this script myself. I was searching the net for a solution
to this problem, and I found a thread on ntfs-3g forums where somebody had
posted this script. Apparently, it had worked for him and some other people.
I just copied and pasted the script. But since I wanted to know more about
startup scripts, I looked at the manual page for rc.d, and a sample script
there looked exacly liked this one. That's why I thought that the script
that I have is going to work as well.
I made the changes and am going to reboot the machine now. If they work,
i'll post the results...
Thanks a lot :)
Okay, here's an update. I changed the script to the following
--
#!/bin/sh
#
# PROVIDE: ntfsmount
# REQUIRE: fusefs
#
. /etc/rc.subr
name=ntfsmount
rcvar=${name}_enable
command=/usr/local/bin/ntfs-3g
command_args=/dev/ad0s1 /mnt/windows
load_rc_config $name
: ${ntfsmount_enable=NO}
run_rc_command $1
--
and have also put rc_debug=YES and rc_info=YES in /etc/rc.conf, and the
result is the following
--
/etc/rc: DEBUG: checkyesno: ntfsmount_enable is set to YES.
Starting ntfsmount.
/etc/rc: DEBUG: run_rc_command: _doit: /usr/local/bin/ntfs-3g /dev/ad0s1
/mnt/w
indows
fuse: failed to exec mount program: No such file or directory
--
I don't exactly know what it means by fuse: failed to exec mount program:
No such file or directory since /usr/local/bin/ntfs-3g exists, /dev/ad0s1
is my Windows 2000 partition, and I have created /mnt/windows myself.
Any ideas?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G not mounting the partition during boot
Starting ntfsmount. /etc/rc: DEBUG: run_rc_command: _doit: /usr/local/bin/ntfs-3g /dev/ad0s1 /mnt/w indows fuse: failed to exec mount program: No such file or directory -- I don't exactly know what it means by fuse: failed to exec mount program: No such file or directory since /usr/local/bin/ntfs-3g exists, /dev/ad0s1 is my Windows 2000 partition, and I have created /mnt/windows myself. Why is the mount point /mnt/windows broken over two lines? If that's the actual output from fuse (and not broken coz of some wrapping while emailing) then that could be the problem. Regards, Rakhesh ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G not mounting the partition during boot
Novembre wrote:
rcvar=`set_rcvar`
That should be
rcvar=${name}_enable
Because of this, your script did not run because the rc system didn't
detect it correctly.
Try setting
rc_debug=YES
and/or
rc_info=YES
in /etc/rc.conf
to see more of whats happening.
command=ntfs-3g /dev/ad0s1 /mnt/windows ntfs-3g /dev/ad0s1
/mnt/windows -o locale=en_US.UTF-8
Also $command is special, you should use another variable
$command_args (which is also special) for the arguments/options.
Of course, you can circument these if you know what you are doing.
When in doubt, look at other rc scripts like apache22's or others that
might seem like they would do a lot.
Finally, in /etc/rc.subr is _very_
--
Philip M. Gollucci ([EMAIL PROTECTED]) 323.219.4708
Senior System Admin - Riderway, Inc. http://riderway.com
1024D/EC88A0BF 0DE5 C55C 6BF3 B235 2DAB B89E 1324 9B4F EC88 A0BF
Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G: mount at boot
On 7/8/07, Novembre [EMAIL PROTECTED] wrote:
Okay, here's an update:
Creating a symlink from /usr/local/bin/ntfs-3g to /sbin/mount_ntfs-3g
does not work (as posted before on the ntfs-3g forum message below).
I, then, added the following ntfsmount startup script to
/usr/local/etc/rc.d/:
--
#!/bin/sh
#
# PROVIDE: ntfsmount
# REQUIRE: fusefs
. /etc/rc.subr
name=ntfsmount
rcvar=`set_rcvar`
command=ntfs-3g /dev/ad0s1 /mnt/windows ntfs-3g /dev/ad0s1
/mnt/windows -o locale=en_US.UTF-8
load_rc_config $name
run_rc_command $1
--
Then, chmod +x /usr/local/etc/rc.d/ntfsmount (to make it executable),
then added ntfsmount_enable=YES to my /etc/rc.conf, then rebooted. I
did not see any error messages during boot, but the partition was not
mounted ('mount' returns nothing after logging in).
However, if I run 'ntfs-3g' again from the command prompt to mount the
windows partition, 'mount' now shows /mnt/windows THREE times, like
/dev/fuse1 on /mnt/windows (fusefs, local, noatime, synchronous)
/dev/fuse3 on /mnt/windows (fusefs, local, noatime, synchronous)
/dev/fuse5 on /mnt/windows (fusefs, local, noatime, synchronous)
and 'ls /dev/f*' returns
/dev/fuse0 /dev/fuse1 /dev/fuse2 /dev/fuse3 /dev/fuse4
/dev/fuse5
It seems that since the 'ntfs-3g' command ran twice in the ntfsmount
script, running 'ntfs-3g' again from the command prompt makes the
third mount point. But if its two runs in the startup script were
successful, why would 'mount' not show the mount points until I run it
again from the command prompt?
I even tried removing one of the 'ntfs-3g' commands in the ntfsmount
script, i.e.
--
command=ntfs-3g /dev/ad0s1 /mnt/windows -o locale=en_US.UTF-8
--
Rebooting with this, still 'mount' shows nothing after logging in.
However, if I run 'ntfs-3g' from the command prompt now, I get TWO
/mnt/windows mount points (instead of three). So it seems the all the
runs in the script are successful and the partition is mounted, but
the mount point is not available until I run 'ntfs-3g' again from the
command prompt.
I am using
fusefs-kmod-0.3.0_5
fusefs-libs-2.6.4
fusefs-ntfs-1.417_2
Any ideas what's going on here?
Thanks :)
On 7/7/07, Novembre [EMAIL PROTECTED] wrote:
I have the same problem. A little search got me to
http://forum.ntfs-3g.org/viewtopic.php?t=292 where a solution is posted. It seems
that using /etc/fstab to mount the NTFS partition at boot time is not working
since the mount command is being executed before the 'fuse' kernel module is
loaded. However, on my 6.2-RELEASE machine, I see the following message when
booting:
--
Starting file system checks:
/dev/ad0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/ad0s2d: FILE SYSTEM CLEAN; SKIPPING CHECKS
Mounting local file systems:mount: exec mount_ntfs-3g not found in
/sbin:/usr/sbin: No such file or directory
.
.
.
Starting fusefs.
fude4bsd: version 0.3.0, FUSE ABI 7.8
.
.
.
Mounting late file systems:mount: exec mount_ntfs-3g not found in
/sbin:/usr/sbin: No such file or directory
--
I'm assuming that this late mount (the last line above) is being done after
loading the 'fuse' kernel module, so the OS should be able to mount the file system now, but
it can't! It's looking for mount_ntfs-3g and that file does not exist.
My /etc/fstab looks like this: /dev/ad0s1 /mnt/windows ntfs-3g
rw 0 0
I also used the /etc/fstab entry suggested in NTFS-3G's own website ( http://www.ntfs-3g.org/ -
scroll down to the end of the page), where defaults is being used instead of
rw, but that gave me this error:
--
swapon: adding /dev/ad0s2b as swap device
fstab: /etc/fstab:6: Inappropriate file type or format
Starting file system checks:
/dev/ad0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS
fstab: /etc/fstab:6: Inappropriate file type or format
fstab: /etc/fstab:6: Inappropriate file type or format
/dev/ad0s2d: FILE SYSTEM CLEAN; SKIPPING CHECKS
Mounting local file systems:fstab: /etc/fstab:6: Inappropriate file type or
format
Mounting NFS file systems:fstab: /etc/fstab:6: Inappropriate file type or
format
fstab: /etc/fstab:6: Inappropriate file type or format
fstab: /etc/fstab:6: Inappropriate file type or format
fstab: /etc/fstab:6: Inappropriate file type or format
fstab: /etc/fstab:6: Inappropriate file type or format
.
.
.
Starting fusefs.
fude4bsd: version 0.3.0, FUSE ABI 7.8
.
.
.
Mounting late file systems:fstab: /etc/fstab:6: Inappropriate file type or
format
--
Any ideas as to what's going on here?
Thanks a lot
anybody? any success in auto-mounting NTFS partitions at boot?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G: mount at boot
Okay, here's an update:
Creating a symlink from /usr/local/bin/ntfs-3g to /sbin/mount_ntfs-3g
does not work (as posted before on the ntfs-3g forum message below).
I, then, added the following ntfsmount startup script to
/usr/local/etc/rc.d/:
--
#!/bin/sh
#
# PROVIDE: ntfsmount
# REQUIRE: fusefs
. /etc/rc.subr
name=ntfsmount
rcvar=`set_rcvar`
command=ntfs-3g /dev/ad0s1 /mnt/windows ntfs-3g /dev/ad0s1
/mnt/windows -o locale=en_US.UTF-8
load_rc_config $name
run_rc_command $1
--
Then, chmod +x /usr/local/etc/rc.d/ntfsmount (to make it executable),
then added ntfsmount_enable=YES to my /etc/rc.conf, then rebooted. I
did not see any error messages during boot, but the partition was not
mounted ('mount' returns nothing after logging in).
However, if I run 'ntfs-3g' again from the command prompt to mount the
windows partition, 'mount' now shows /mnt/windows THREE times, like
/dev/fuse1 on /mnt/windows (fusefs, local, noatime, synchronous)
/dev/fuse3 on /mnt/windows (fusefs, local, noatime, synchronous)
/dev/fuse5 on /mnt/windows (fusefs, local, noatime, synchronous)
and 'ls /dev/f*' returns
/dev/fuse0 /dev/fuse1 /dev/fuse2 /dev/fuse3 /dev/fuse4
/dev/fuse5
It seems that since the 'ntfs-3g' command ran twice in the ntfsmount
script, running 'ntfs-3g' again from the command prompt makes the
third mount point. But if its two runs in the startup script were
successful, why would 'mount' not show the mount points until I run it
again from the command prompt?
I even tried removing one of the 'ntfs-3g' commands in the ntfsmount
script, i.e.
--
command=ntfs-3g /dev/ad0s1 /mnt/windows -o locale=en_US.UTF-8
--
Rebooting with this, still 'mount' shows nothing after logging in.
However, if I run 'ntfs-3g' from the command prompt now, I get TWO
/mnt/windows mount points (instead of three). So it seems the all the
runs in the script are successful and the partition is mounted, but
the mount point is not available until I run 'ntfs-3g' again from the
command prompt.
I am using
fusefs-kmod-0.3.0_5
fusefs-libs-2.6.4
fusefs-ntfs-1.417_2
Any ideas what's going on here?
Thanks :)
On 7/7/07, Novembre [EMAIL PROTECTED] wrote:
I have the same problem. A little search got me to
http://forum.ntfs-3g.org/viewtopic.php?t=292 where a solution is posted. It
seems that using /etc/fstab to mount the NTFS partition at boot time is not
working since the mount command is being executed before the 'fuse' kernel
module is loaded. However, on my 6.2-RELEASE machine, I see the following
message when booting:
--
Starting file system checks:
/dev/ad0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/ad0s2d: FILE SYSTEM CLEAN; SKIPPING CHECKS
Mounting local file systems:mount: exec mount_ntfs-3g not found in
/sbin:/usr/sbin: No such file or directory
.
.
.
Starting fusefs.
fude4bsd: version 0.3.0, FUSE ABI 7.8
.
.
.
Mounting late file systems:mount: exec mount_ntfs-3g not found in
/sbin:/usr/sbin: No such file or directory
--
I'm assuming that this late mount (the last line above) is being done after
loading the 'fuse' kernel module, so the OS should be able to mount the file system now,
but it can't! It's looking for mount_ntfs-3g and that file does not exist.
My /etc/fstab looks like this: /dev/ad0s1 /mnt/windows ntfs-3g
rw 0 0
I also used the /etc/fstab entry suggested in NTFS-3G's own website ( http://www.ntfs-3g.org/ -
scroll down to the end of the page), where defaults is being used instead of
rw, but that gave me this error:
--
swapon: adding /dev/ad0s2b as swap device
fstab: /etc/fstab:6: Inappropriate file type or format
Starting file system checks:
/dev/ad0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS
fstab: /etc/fstab:6: Inappropriate file type or format
fstab: /etc/fstab:6: Inappropriate file type or format
/dev/ad0s2d: FILE SYSTEM CLEAN; SKIPPING CHECKS
Mounting local file systems:fstab: /etc/fstab:6: Inappropriate file type or
format
Mounting NFS file systems:fstab: /etc/fstab:6: Inappropriate file type or format
fstab: /etc/fstab:6: Inappropriate file type or format
fstab: /etc/fstab:6: Inappropriate file type or format
fstab: /etc/fstab:6: Inappropriate file type or format
fstab: /etc/fstab:6: Inappropriate file type or format
.
.
.
Starting fusefs.
fude4bsd: version 0.3.0, FUSE ABI 7.8
.
.
.
Mounting late file systems:fstab: /etc/fstab:6: Inappropriate file type or
format
--
Any ideas as to what's going on here?
Thanks a lot
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: NTFS-3G: mount at boot
I have the same problem. A little search got me to http://forum.ntfs-3g.org/viewtopic.php?t=292 where a solution is posted. It seems that using /etc/fstab to mount the NTFS partition at boot time is not working since the mount command is being executed before the 'fuse' kernel module is loaded. However, on my 6.2-RELEASE machine, I see the following message when booting: -- Starting file system checks: /dev/ad0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS /dev/ad0s2d: FILE SYSTEM CLEAN; SKIPPING CHECKS Mounting local file systems:mount: exec mount_ntfs-3g not found in /sbin:/usr/sbin: No such file or directory . . . Starting fusefs. fude4bsd: version 0.3.0, FUSE ABI 7.8 . . . Mounting late file systems:mount: exec mount_ntfs-3g not found in /sbin:/usr/sbin: No such file or directory -- I'm assuming that this late mount (the last line above) is being done after loading the 'fuse' kernel module, so the OS should be able to mount the file system now, but it can't! It's looking for mount_ntfs-3g and that file does not exist. My /etc/fstab looks like this: /dev/ad0s1 /mnt/windows ntfs-3g rw 0 0 I also used the /etc/fstab entry suggested in NTFS-3G's own website ( http://www.ntfs-3g.org/ - scroll down to the end of the page), where defaults is being used instead of rw, but that gave me this error: -- swapon: adding /dev/ad0s2b as swap device fstab: /etc/fstab:6: Inappropriate file type or format Starting file system checks: /dev/ad0s2a: FILE SYSTEM CLEAN; SKIPPING CHECKS fstab: /etc/fstab:6: Inappropriate file type or format fstab: /etc/fstab:6: Inappropriate file type or format /dev/ad0s2d: FILE SYSTEM CLEAN; SKIPPING CHECKS Mounting local file systems:fstab: /etc/fstab:6: Inappropriate file type or format Mounting NFS file systems:fstab: /etc/fstab:6: Inappropriate file type or format fstab: /etc/fstab:6: Inappropriate file type or format fstab: /etc/fstab:6: Inappropriate file type or format fstab: /etc/fstab:6: Inappropriate file type or format fstab: /etc/fstab:6: Inappropriate file type or format . . . Starting fusefs. fude4bsd: version 0.3.0, FUSE ABI 7.8 . . . Mounting late file systems:fstab: /etc/fstab:6: Inappropriate file type or format -- Any ideas as to what's going on here? Thanks a lot ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G driver problem
I had the same issue when installing fuse-fs the first time - I just ran sysinstall again, went to distributions, then choose the source dist, installed that, rebooted, and fusefs built and installed fine. Steve On 2/21/07, Jason Gretz [EMAIL PROTECTED] wrote: Hey guys, I got a prob here, I am trying to install the new NTFS-3G driver, which just went 1.0, and This is what the output of make install make clean got me: === Installing for fusefs-ntfs-0.20070207RC1 === fusefs-ntfs-0.20070207RC1 depends on file: /usr/local/modules/fuse.ko - not found ===Verifying reinstall for /usr/local/modules/fuse.ko in /usr/ports/sysutils/fusefs-kmod === fusefs-kmod-0.3.0_4 requires the Kernel source to be installed. Set SRC_BASE if it is not in /usr/src. Thanks! Jason -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.441 / Virus Database: 268.18.3/696 - Release Date: 2/21/2007 3:19 PM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Steve Franks, KE7BTE Staff Engineer La Palma Devices, LLC http://www.lapalmadevices.com (520) 312-0089 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS-3G driver problem
Jason Gretz wrote: Hey guys, I got a prob here, I am trying to install the new NTFS-3G driver, which just went 1.0, and This is what the output of make install make clean got me: === Installing for fusefs-ntfs-0.20070207RC1 === fusefs-ntfs-0.20070207RC1 depends on file: /usr/local/modules/fuse.ko - not found ===Verifying reinstall for /usr/local/modules/fuse.ko in /usr/ports/sysutils/fusefs-kmod === fusefs-kmod-0.3.0_4 requires the Kernel source to be installed. Set SRC_BASE if it is not in /usr/src. Well, do you have the source distribution installed in the usual place? It would appear not Kevin Kinsey -- Each of us bears his own Hell. -- Publius Vergilius Maro (Virgil) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS?
FreeBSD has its own filesystem called UFS (or UFS2). It does not install into a fat32 or NTFS partition. Both of those formats are used in 95 OSR2+ or NT4+ respectively. Lucas Holt On Fri, 12 Nov 2004 [EMAIL PROTECTED] wrote: Do i have to install the OS on FAT32 file system ... cause i am currently running a NTFS on a Windows XP. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS?
On Friday 12 November 2004 18:59, [EMAIL PROTECTED] wrote: Do i have to install the OS on FAT32 file system ... cause i am currently running a NTFS on a Windows XP. FreeBSD uses it's own filesystem. You will need to make some unpartitioned space on your disk to install. The handbook has answers to this sort of question and many more. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/index.html -- Thanks, Josh Paetzel ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntfs mount
The full fdisk output is:
*** Working on device /dev/ad0 ***
parameters extracted from in-core disklabel are:
cylinders=4865 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=4865 heads=255 sectors/track=63 (16065 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 45,(unknown)
start 63, size 30716217 (14998 Meg), flag 0
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
sysid 45,(unknown)
start 30716280, size 20482875 (10001 Meg), flag 0
beg: cyl 1023/ head 255/ sector 63;
end: cyl 1023/ head 254/ sector 63
The data for partition 3 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
start 51199155, size 12273660 (5992 Meg), flag 80 (active)
beg: cyl 1023/ head 255/ sector 63;
end: cyl 1023/ head 254/ sector 63
The data for partition 4 is:
sysid 165,(FreeBSD/NetBSD/386BSD)
start 63472815, size 14667345 (7161 Meg), flag 0
beg: cyl 1023/ head 255/ sector 63;
end: cyl 1023/ head 254/ sector 63
-- In Response to your message -
Date: Thu, 06 May 2004 21:51:33 +0100
To: J. W. Ballantine [EMAIL PROTECTED]
From: Mark Ovens [EMAIL PROTECTED]
Subject: Re: ntfs mount
J. W. Ballantine wrote:
Seems our friends in redmond have done something strange with the
fs type. both w2k partitions on the disk show a type of 45
Hmm, it's not a brand-name PC that came with Windows pre-installed is
it? If so there may be a hidden recovery/diagnostics partition that is
confusing fdisk.
It a Dell, but given the configuration, i do not believe it came
pre-installed from the factory.
Do you have anything like OnTrack Disk Manager installed to get round
disk size limitations in the BIOS? Unlikely with a machine that runs
W2K, but I do know someone that installed in on a P-III machine when he
built it, using an old 6.5Gbyte disk, because it came with the disk?
No disk manager of any sort running.
Since you have 2 Windows partitions, you haven't installed any form of
multi-OS boot manager have you? You wouldn't need it with W2K but you
may have had if you had 2 different versions of Win9x on there once over?
Only the first partition is bootable, I had two to separate the
standard install from the non-standard (ie the programs I use).
The multi-os boot manager is Smart Boot Manager, but that doesn't change
any partiton ids.
Can you post the whole output of `fdisk ad0', it may just give someone a
clue?
and both freebsd show 165.
Which is correct.
Regards,
Mark
Thanks
Jim
-- In Response to your message -
Date: Thu, 06 May 2004 20:40:45 +0100
To: J. W. Ballantine [EMAIL PROTECTED], [EMAIL PROTECTED]
rg
From: Mark Ovens [EMAIL PROTECTED]
Subject: Re: ntfs mount
J. W. Ballantine wrote:
when I do a properties under w2k it says file system is ntfs,
fdisk on bsd show partition 1 is sysid 45,(unknown)
Hmm, should be sysid 7. I can't remember if the NTFS driver is built
into the kernel (by default) or it's a kld module under 4.x, I'm running
-CURRENT, but I'm sure I never had to do anything special for NTFS
support in 4.x and the Handbook and FAQ only mention mount_ntfs.
FWIW, here's what I get (single partition, C:, on the first drive). Note
mine is 'da0', not 'ad0', as it's SCSI not IDE:
/home/mark{38}# fdisk da0
*** Working on device /dev/da0 ***
parameters extracted from in-core disklabel are:
cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX)
start 63, size 143347932 (69994 Meg), flag 0
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
UNUSED
The data for partition 3 is:
UNUSED
The data for partition 4 is:
UNUSED
/home/mark{39}#
-- In Response to your message -
Date: Thu, 06 May 2004 20:01:24 +0100
To: J. W. Ballantine [EMAIL PROTECTED], [EMAIL PROTECTED]
sd.o
rg
From: Mark Ovens [EMAIL PROTECTED]
Subject: Re: ntfs mount
J. W. Ballantine wrote:
yes, there is only one hard disk.
What does the output
Re: ntfs mount
J. W. Ballantine wrote: The full fdisk output is: *** Working on device /dev/ad0 *** parameters extracted from in-core disklabel are: cylinders=4865 heads=255 sectors/track=63 (16065 blks/cyl) [snip] I take it that the partition sizees reported are correct? It a Dell, but given the configuration, i do not believe it came pre-installed from the factory. I would have thought that a Dell would have had *an* OS pre-installed. Only the first partition is bootable, I had two to separate the standard install from the non-standard (ie the programs I use). The multi-os boot manager is Smart Boot Manager, but that doesn't change any partiton ids. Not come across Smart Boot Manager but I wonder if it creates a small partition to run from; the OS/2 Boot Manager, which was also shipped with older versions of Partition Magic, did but, like recovery partitions it didn't get a drive letter. Try running: # dd if=/dev/ad0 of=/tmp/foo bs=512 count=1 # hd /tmp/foo /tmp/foo.hd This copies the first sector of the disk to a file and hd(1) does a hexdump of the binary file. Open /tmp/foo.hd in an editor and look at the last 4 lines, they should look similar to: 01b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 01 01c0 01 00 a5 7f ff 10 3f 00 00 00 41 97 60 00 00 00 01d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa 0200 (there will be the ASCII to the right of each line but I've not included it to prevent wrapping in the e-mail) The partition type is the third hex number in the last 4 lines; the example above is 'a5' (FreeBSD) and the disk has only one partition which is why the other 3 lines are all zeros. Post the file /tmp/foo.hd here as other stuff may yield clues. Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntfs mount
On May 7, 2004, at 1:40 PM, Mark Ovens wrote: J. W. Ballantine wrote: It a Dell, but given the configuration, i do not believe it came pre-installed from the factory. I would have thought that a Dell would have had *an* OS pre-installed. Not always. I am running FBSD 4.9 on a couple Dell 2650's ordered just for the purpose of installing FreeBSD on them for some of our server use...you can specify *no operating system* and they ship you the system and rails with nothing but the hard drives configured for RAID on the PERC controller. No fuss, no muss :-) ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntfs mount
The last four lines are not even close:
fa eb 5c 53 42 4d 33 2e 37 2e 31 00 02 01 01 00 |..\SBM3.7.1.|
0010 02 e0 00 40 0b f0 09 00 12 00 02 00 00 00 00 00 |[EMAIL PROTECTED]|
0020 00 00 00 00 00 00 29 00 00 00 00 53 4d 41 52 54 |..)SMART|
0030 20 42 54 4d 47 52 46 41 54 31 32 20 20 20 eb 1f | BTMGRFAT12 ..|
0040 53 42 4d 4c 01 03 2c 01 00 00 00 00 00 00 00 00 |SBML..,.|
0050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 31 |...1|
0060 c0 8e d0 bc 00 7c 89 e6 50 07 50 1f fb fc bf 00 |.|..P.P.|
0070 06 b9 00 01 f3 a5 ea 7b 00 60 00 0e 1f 68 00 10 |...{.`...h..|
0080 07 8d 36 46 00 b9 05 00 31 ff 51 ac 88 c1 66 ad |..6F1.Q...f.|
0090 66 89 c3 b8 01 02 09 c9 74 12 e8 57 00 72 3a 81 |f...t..W.r:.|
00a0 c7 00 02 66 43 e2 f3 59 e2 e0 eb 01 59 31 ff 26 |...fC..YY1.|
00b0 66 81 7d 04 53 42 4d 4b 75 20 26 81 7d 08 07 03 |f.}.SBMKu .}...|
00c0 75 18 26 8b 4d 0a 30 db 26 8a 05 00 c3 47 e2 f8 |u..M.0.G..|
00d0 08 db 75 06 ea 00 00 00 10 59 8d 36 ad 01 ac 08 |..u..Y.6|
00e0 c0 74 09 bb 07 00 b4 0e cd 10 eb f2 30 e4 cd 16 |.t..0...|
00f0 cd 18 eb fe 60 50 53 bb aa 55 b4 41 cd 13 72 45 |`PS..U.A..rE|
0100 81 fb 55 aa 75 3f f6 c1 01 74 3a 5b 58 80 c4 40 |..U.u?...t:[X..@|
0110 8d 36 02 02 66 31 c9 c6 04 10 66 89 4c 0c 88 4c |.6..f1f.L..L|
0120 01 88 4c 03 88 44 02 89 7c 04 8c 44 06 66 89 5c |..L..D..|..D.f.\|
0130 08 50 52 cd 13 5a 58 73 6b e8 6a 00 fe c6 80 fe |.PR..ZXsk.j.|
0140 03 72 e1 eb 5e 52 06 57 b4 08 cd 13 88 0e 00 02 |.r..^R.W|
0150 88 36 01 02 5f 07 5a 5b 58 72 48 50 52 66 89 d8 |.6.._.Z[XrHPRf..|
0160 66 0f b7 0e 00 02 81 e1 3f 00 66 31 d2 66 f7 f1 |f...?.f1.f..|
0170 42 89 d1 66 31 db 8a 1e 01 02 fe c3 66 31 d2 66 |B..f1...f1.f|
0180 f7 f3 88 d3 86 c4 c0 e0 06 09 c1 5a 58 88 de 89 |...ZX...|
0190 fb 31 ff 50 cd 13 58 73 0b e8 0a 00 47 81 ff 03 |.1.P..XsG...|
01a0 00 72 f0 f9 61 c3 60 31 c0 cd 13 61 c3 07 53 42 |.r..a.`1...a..SB|
01b0 4d 4b 20 42 61 64 21 0d 0a 00 00 00 00 00 00 01 |MK Bad!.|
01c0 01 00 2d fe ff ff 3f 00 00 00 39 b1 d4 01 00 ff |..-...?...9.|
01d0 ff ff 2d fe ff ff 78 b1 d4 01 3b 8b 38 01 80 ff |..-...x...;.8...|
01e0 ff ff a5 fe ff ff b3 3c 0d 03 fc 47 bb 00 00 ff |..G|
01f0 ff ff a5 fe ff ff af 84 c8 03 51 ce df 00 55 aa |..Q...U.|
0200
I use the same boot manager on another system (xp rather than 2k) and
have no problems mounting the disk.
Jim
-- In Response to your message -
Date: Fri, 07 May 2004 18:40:15 +0100
To: J. W. Ballantine [EMAIL PROTECTED]
From: Mark Ovens [EMAIL PROTECTED]
Subject: Re: ntfs mount
J. W. Ballantine wrote:
The full fdisk output is:
*** Working on device /dev/ad0 ***
parameters extracted from in-core disklabel are:
cylinders=4865 heads=255 sectors/track=63 (16065 blks/cyl)
[snip]
I take it that the partition sizees reported are correct?
It a Dell, but given the configuration, i do not believe it came
pre-installed from the factory.
I would have thought that a Dell would have had *an* OS pre-installed.
Only the first partition is bootable, I had two to separate the
standard install from the non-standard (ie the programs I use).
The multi-os boot manager is Smart Boot Manager, but that doesn't change
any partiton ids.
Not come across Smart Boot Manager but I wonder if it creates a small
partition to run from; the OS/2 Boot Manager, which was also shipped
with older versions of Partition Magic, did but, like recovery
partitions it didn't get a drive letter.
Try running:
# dd if=/dev/ad0 of=/tmp/foo bs=512 count=1
# hd /tmp/foo /tmp/foo.hd
This copies the first sector of the disk to a file and hd(1) does a
hexdump of the binary file.
Open /tmp/foo.hd in an editor and look at the last 4 lines, they should
look similar to:
01b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 80 01
01c0 01 00 a5 7f ff 10 3f 00 00 00 41 97 60 00 00 00
01d0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
01f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa
0200
(there will be the ASCII to the right of each line but I've not included
it to prevent wrapping in the e-mail)
The partition type is the third hex number in the last 4 lines; the
example above is 'a5' (FreeBSD) and the disk has only one partition
which is why the other 3 lines are all zeros.
Post the file /tmp/foo.hd here as other stuff may yield clues.
Regards,
Mark
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org
Re: ntfs mount
Mark Ovens wrote: Not come across Smart Boot Manager but I wonder if it creates a small partition to run from; the OS/2 Boot Manager, which was also shipped with older versions of Partition Magic, did but, like recovery partitions it didn't get a drive letter. Ah! I've just thought of something. My old machine had Boot Magic installed - the boot manager that came with later versions of Partition Magic and didn't need a dedicated partition. One of it's features let you choose which partitions each OS could see. I never looked into _how_ it did it but I'm now wondering if it worked by setting the partition type id flag to 45 (unknown) in the partition table; I do remember that I had to disable the BIOS boot sector anti-virus feature as it went off everytime I booted. Now, it may be that this is how Smart Boot Manager works. You could confirm it by viewing the MBR when booted into Windows, you can get a copy of dd(1) and hd(1) for windows from cygwin.com or you can use DSKPROBE.EXE which is in the NT4 Resource Kit (if you can find a copy - e-mail me if you can't) and see if the partition type for the first two partitions is now set to 7 (NTFS), and maybe the FreeBSD partitions are now 45? Regards, Parish ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntfs mount
Bart Silverstrim wrote: On May 7, 2004, at 1:40 PM, Mark Ovens wrote: J. W. Ballantine wrote: It a Dell, but given the configuration, i do not believe it came pre-installed from the factory. I would have thought that a Dell would have had *an* OS pre-installed. Not always. I am running FBSD 4.9 on a couple Dell 2650's ordered just for the purpose of installing FreeBSD on them for some of our server use...you can specify *no operating system* and they ship you the system and rails with nothing but the hard drives configured for RAID on the PERC controller. No fuss, no muss :-) That's good to know :-) Does it only apply to servers, or can you get desktop machines /sans/ OS? Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] . ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntfs mount
Only if it treats w2k different than 98 and XP. I've had the same boot manager on dual boot machines with the two MS OSes and FreeBSD and have no trouble mounting the ms partitions on FreeBSD. Jim -- In Response to your message - Date: Fri, 07 May 2004 19:10:17 +0100 To: J. W. Ballantine [EMAIL PROTECTED] From: Mark Ovens [EMAIL PROTECTED] Subject: Re: ntfs mount Mark Ovens wrote: Not come across Smart Boot Manager but I wonder if it creates a small partition to run from; the OS/2 Boot Manager, which was also shipped with older versions of Partition Magic, did but, like recovery partitions it didn't get a drive letter. Ah! I've just thought of something. My old machine had Boot Magic installed - the boot manager that came with later versions of Partition Magic and didn't need a dedicated partition. One of it's features let you choose which partitions each OS could see. I never looked into _how_ it did it but I'm now wondering if it worked by setting the partition type id flag to 45 (unknown) in the partition table; I do remember that I had to disable the BIOS boot sector anti-virus feature as it went off everytime I booted. Now, it may be that this is how Smart Boot Manager works. You could confirm it by viewing the MBR when booted into Windows, you can get a copy of dd(1) and hd(1) for windows from cygwin.com or you can use DSKPROBE.EXE which is in the NT4 Resource Kit (if you can find a copy - e-mail me if you can't) and see if the partition type for the first two partitions is now set to 7 (NTFS), and maybe the FreeBSD partitions are now 45? Regards, Parish ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntfs mount
On May 7, 2004, at 2:12 PM, Mark Ovens wrote: Bart Silverstrim wrote: On May 7, 2004, at 1:40 PM, Mark Ovens wrote: J. W. Ballantine wrote: It a Dell, but given the configuration, i do not believe it came pre-installed from the factory. I would have thought that a Dell would have had *an* OS pre-installed. Not always. I am running FBSD 4.9 on a couple Dell 2650's ordered just for the purpose of installing FreeBSD on them for some of our server use...you can specify *no operating system* and they ship you the system and rails with nothing but the hard drives configured for RAID on the PERC controller. No fuss, no muss :-) That's good to know :-) Does it only apply to servers, or can you get desktop machines /sans/ OS? I don't know for sure to give an authoritative answer; if you call them for ordering, you should be able to cajole them into it. We may get different treatment because we're a school and they like us calling them back when another project needs another server (I think educational institutions are considered businesses by Dell, so we can all our sales rep and they seem to be able to work whatever magic we want for configurations when we make it clear that's what we want). Dell doesn't make systems, IIRC, until they are ordered...read something about how it cuts down on inventory left in warehouses and allows for customization...so I don't see why they couldn't make a desktop system sans OS. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntfs mount
J. W. Ballantine wrote: Ok, either I'm missing something very basic or I'm trying to mount a w2k ntfs file system with: mount_ntfs /dev/ad0s1 /C and I get back: mount_ntfs: /dev/ad0s1: Invalid Argument Is the filesystem you are trying to mount the first _primary_ partition on the first (i.e. the one jumpered Master) hard disk? I'm told this is an ntfs5 file system, could it be that IIRC, W2K uses NTFS4; NTFS5 is XP. FreeBSD doesn't grok this type of fs Yes, it does. or am I missing something really basic?? Possibly, depends on the answer to the location of the filesystem. For ad0 there is only s1,s2,s3,s4; nots5 or above. This is on a 4.10-prerelease system. Thanks for any and all thoughts Jim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] . ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntfs mount
-- In Response to your message - Date: Thu, 06 May 2004 19:28:27 +0100 To: [EMAIL PROTECTED] From: Mark Ovens [EMAIL PROTECTED] Subject: Re: ntfs mount J. W. Ballantine wrote: Ok, either I'm missing something very basic or I'm trying to mount a w2k ntfs file system with: mount_ntfs /dev/ad0s1 /C and I get back: mount_ntfs: /dev/ad0s1: Invalid Argument Is the filesystem you are trying to mount the first _primary_ partition on the first (i.e. the one jumpered Master) hard disk? yes, there is only one hard disk. I'm told this is an ntfs5 file system, could it be that IIRC, W2K uses NTFS4; NTFS5 is XP. FreeBSD doesn't grok this type of fs Yes, it does. or am I missing something really basic?? Possibly, depends on the answer to the location of the filesystem. For ad0 there is only s1,s2,s3,s4; nots5 or above. This is on a 4.10-prerelease system. Thanks for any and all thoughts Jim ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] . ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntfs mount
J. W. Ballantine wrote: yes, there is only one hard disk. What does the output from `fdisk ad0' show? Regards, Mark ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntfs mount
J. W. Ballantine wrote:
when I do a properties under w2k it says file system is ntfs,
fdisk on bsd show partition 1 is sysid 45,(unknown)
Hmm, should be sysid 7. I can't remember if the NTFS driver is built
into the kernel (by default) or it's a kld module under 4.x, I'm running
-CURRENT, but I'm sure I never had to do anything special for NTFS
support in 4.x and the Handbook and FAQ only mention mount_ntfs.
FWIW, here's what I get (single partition, C:, on the first drive). Note
mine is 'da0', not 'ad0', as it's SCSI not IDE:
/home/mark{38}# fdisk da0
*** Working on device /dev/da0 ***
parameters extracted from in-core disklabel are:
cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX)
start 63, size 143347932 (69994 Meg), flag 0
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
UNUSED
The data for partition 3 is:
UNUSED
The data for partition 4 is:
UNUSED
/home/mark{39}#
-- In Response to your message -
Date: Thu, 06 May 2004 20:01:24 +0100
To: J. W. Ballantine [EMAIL PROTECTED], [EMAIL PROTECTED]
From: Mark Ovens [EMAIL PROTECTED]
Subject: Re: ntfs mount
J. W. Ballantine wrote:
yes, there is only one hard disk.
What does the output from `fdisk ad0' show?
Regards,
Mark
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntfs mount
Seems our friends in redmond have done something strange with the
fs type. both w2k partitions on the disk show a type of 45
and both freebsd show 165.
Thanks
Jim
-- In Response to your message -
Date: Thu, 06 May 2004 20:40:45 +0100
To: J. W. Ballantine [EMAIL PROTECTED], [EMAIL PROTECTED]
From: Mark Ovens [EMAIL PROTECTED]
Subject: Re: ntfs mount
J. W. Ballantine wrote:
when I do a properties under w2k it says file system is ntfs,
fdisk on bsd show partition 1 is sysid 45,(unknown)
Hmm, should be sysid 7. I can't remember if the NTFS driver is built
into the kernel (by default) or it's a kld module under 4.x, I'm running
-CURRENT, but I'm sure I never had to do anything special for NTFS
support in 4.x and the Handbook and FAQ only mention mount_ntfs.
FWIW, here's what I get (single partition, C:, on the first drive). Note
mine is 'da0', not 'ad0', as it's SCSI not IDE:
/home/mark{38}# fdisk da0
*** Working on device /dev/da0 ***
parameters extracted from in-core disklabel are:
cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX)
start 63, size 143347932 (69994 Meg), flag 0
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
UNUSED
The data for partition 3 is:
UNUSED
The data for partition 4 is:
UNUSED
/home/mark{39}#
-- In Response to your message -
Date: Thu, 06 May 2004 20:01:24 +0100
To: J. W. Ballantine [EMAIL PROTECTED], [EMAIL PROTECTED]
rg
From: Mark Ovens [EMAIL PROTECTED]
Subject: Re: ntfs mount
J. W. Ballantine wrote:
yes, there is only one hard disk.
What does the output from `fdisk ad0' show?
Regards,
Mark
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ntfs mount
J. W. Ballantine wrote:
Seems our friends in redmond have done something strange with the
fs type. both w2k partitions on the disk show a type of 45
Hmm, it's not a brand-name PC that came with Windows pre-installed is
it? If so there may be a hidden recovery/diagnostics partition that is
confusing fdisk.
Do you have anything like OnTrack Disk Manager installed to get round
disk size limitations in the BIOS? Unlikely with a machine that runs
W2K, but I do know someone that installed in on a P-III machine when he
built it, using an old 6.5Gbyte disk, because it came with the disk?
Since you have 2 Windows partitions, you haven't installed any form of
multi-OS boot manager have you? You wouldn't need it with W2K but you
may have had if you had 2 different versions of Win9x on there once over?
Can you post the whole output of `fdisk ad0', it may just give someone a
clue?
and both freebsd show 165.
Which is correct.
Regards,
Mark
Thanks
Jim
-- In Response to your message -
Date: Thu, 06 May 2004 20:40:45 +0100
To: J. W. Ballantine [EMAIL PROTECTED], [EMAIL PROTECTED]
From: Mark Ovens [EMAIL PROTECTED]
Subject: Re: ntfs mount
J. W. Ballantine wrote:
when I do a properties under w2k it says file system is ntfs,
fdisk on bsd show partition 1 is sysid 45,(unknown)
Hmm, should be sysid 7. I can't remember if the NTFS driver is built
into the kernel (by default) or it's a kld module under 4.x, I'm running
-CURRENT, but I'm sure I never had to do anything special for NTFS
support in 4.x and the Handbook and FAQ only mention mount_ntfs.
FWIW, here's what I get (single partition, C:, on the first drive). Note
mine is 'da0', not 'ad0', as it's SCSI not IDE:
/home/mark{38}# fdisk da0
*** Working on device /dev/da0 ***
parameters extracted from in-core disklabel are:
cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=8924 heads=255 sectors/track=63 (16065 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 7 (0x07),(OS/2 HPFS, NTFS, QNX-2 (16 bit) or Advanced UNIX)
start 63, size 143347932 (69994 Meg), flag 0
beg: cyl 0/ head 1/ sector 1;
end: cyl 1023/ head 254/ sector 63
The data for partition 2 is:
UNUSED
The data for partition 3 is:
UNUSED
The data for partition 4 is:
UNUSED
/home/mark{39}#
-- In Response to your message -
Date: Thu, 06 May 2004 20:01:24 +0100
To: J. W. Ballantine [EMAIL PROTECTED], [EMAIL PROTECTED]
rg
From: Mark Ovens [EMAIL PROTECTED]
Subject: Re: ntfs mount
J. W. Ballantine wrote:
yes, there is only one hard disk.
What does the output from `fdisk ad0' show?
Regards,
Mark
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS drive D in fstab
On Tue, 10 Feb 2004 08:51:32 +0200 Robert Golovniov [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday, February 9, 2004, 4:52:36 PM, Ion-Mihai Tetcu wrote: IMT For my reference, what does ls /dev/ad0* print ? /dev/ad0/dev/ad0s2 /dev/ad0s3a/dev/ad0s3c /dev/ad0s5 /dev/ad0s1 /dev/ad0s3 /dev/ad0s3b/dev/ad0s3d Thanks, IOnut -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS filesystem in hard, but: @/:write failed, filesystem isfull@
Denis wrote: Hi! Does anybody explain me why i can't install FreeBSD on new HDD? I have just NTFS hard drive formatted, but when i start freebsd install i see next: Probing devices (this can take a while) And next: /:write falied, filesystem is full What is it? What I must do next? Thanks. Denis. Off the top of my head, I could be wrong here though. If you haven't given up some space on that NTFS hard drive you are not going to get anywhere. By space I mean some unpartitioned area of the hard drive that will have enough free space to meet the demands of your freebsd install. You'll most likely need some sort of partioning utility to shrink a NTFS partition down. The other possability is you did make a partition (slice in FreeBSD parlance) and indeed ran out of space and all them bits were getting squished together and *poof* filled up your file system. You'll need to make more room. I'm not sure how much space is required for a FreeBSD install, you can check the documentation for that, and then make a slice or slices the combined size you'll need. And don't forget about swap space. HTH ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS filesystem in hard, but: @/:write failed, filesystem isfull@
Denis wrote: !!! Saturday, August 16, 2003, 9:40:38 PM, : m Denis wrote: Hello Matt, Saturday, August 16, 2003, 8:13:50 PM, you wrote: MH delete the NTFS partition and start again And what partition I must create? Without partition I see it message again:( Maybe I bought bad hard? Maybe free does not support: seagate barracuda 60 GB ATA 7200 rpm.??? m The FreeBSD installation process will give you the opportunity to create m partitions. m It has an Auto option to save you having scratch your head. m There is a long explanation in the handbook m http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-steps.html No! When I boot from CD-RW will starting menu when I will choose 1... I CAN'T START FDISK: /:write failed, filesystem is full I CAN'T START INSTALL. booting fail:((( Denis. that sounds bad I shall CC: this to FreeBSD questions Maybe it is trying to install to the CD-RW ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS filesystem in hard - FIXED
Denis wrote: Yeah!!! I got it! I just connect my second hard with WinXP and connect first 60gb which i bought today. And freebsd think that i will be install to second... and I don't see errors message. So, when I started FDisk I just create partition on 60 gb(my new hard!) And I installed freebsd on my new hard on 60 gb So I am bamboozle freebsd! All of my errors will be in connect second hard:) Thanks! Denis. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NTFS with Wine and VMware?
Dear/Beste David, Wednesday, December 4, 2002, 4:39:33 AM, you wrote: If i have a dual boot system of Win2k and FreeBSD at which the Win2k is on a NTFS partition will I beable to use Wine and VMWare with this win2k? or does the partition have to be FAT or FAT32? Dave To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message There is a NTFS reader, but i think the work on the NTFS writer is still in progress. You can try NTFS and see if it works for you. The safe bet would be to use FAT or FAT32. -- Best regards/Met vriendelijke groet, Alex To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: NTFS with Wine and VMware?
On Sat, Dec 07, 2002 at 10:58:36AM +0100, Alex wrote: Dear/Beste David, Wednesday, December 4, 2002, 4:39:33 AM, you wrote: If i have a dual boot system of Win2k and FreeBSD at which the Win2k is on a NTFS partition will I beable to use Wine and VMWare with this win2k? or does the partition have to be FAT or FAT32? Dave To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message There is a NTFS reader, but i think the work on the NTFS writer is still in progress. You can try NTFS and see if it works for you. The safe bet would be to use FAT or FAT32. Of course there is the performance price to pay with this, NTFS versus FAT32, to bear in mind. But I wouldn't trust write-enabling an NTFS file system. I have serious doubts whether NTFS on NT, 2000 and XP is the *same* from an interface perspective. -- Regards Cliff Sarginson The Netherlands [ This mail has been checked as virus-free ] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
Re: NTFS with Wine and VMware?
On Sat, Dec 07, 2002 at 10:58:36AM +0100, Alex wrote: Dear/Beste David, Wednesday, December 4, 2002, 4:39:33 AM, you wrote: If i have a dual boot system of Win2k and FreeBSD at which the Win2k is on a NTFS partition will I beable to use Wine and VMWare with this win2k? or does the partition have to be FAT or FAT32? Dave There is a NTFS reader, but i think the work on the NTFS writer is still in progress. You can try NTFS and see if it works for you. The safe bet would be to use FAT or FAT32. I installed Win2K on FAT32 exactly so I could access it in Linux and FreeBSD. My email, for example, is stored on Win2k's C: drive. My mail agent is VM in emacs, which stores messages in a platform- independent format. It is equally easy to access my email from whichever OS is booted: Windows, Linux, or (when I solve my irq problem) FreeBSD. Since I'm the only one that uses my machine and it's behind a separate firewall, I don't need the protection NTFS offers. -Ken To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
