Re: mount_ntfs fails

2003-02-27 Thread Dancho Penev
On Fri, Feb 21, 2003 at 02:26:02PM +0100, Wiroth Didier wrote:
From: Wiroth Didier [EMAIL PROTECTED]
Subject: Re: mount_ntfs fails
To: [EMAIL PROTECTED]
Date: Fri, 21 Feb 2003 14:26:02 +0100
On Fri, 21 Feb 2003 13:15:03 +
Daniel Bye [EMAIL PROTECTED] wrote:
On Fri, Feb 21, 2003 at 01:54:57PM +0100, Didier Wiroth
wrote:
 Hey, 
 
 I have two harddisks:
 1) ad0 with 1 slice containing Windows XP pro
 2) ad2 with two slices s1 is ntfs and s2 is freebsd
4.7-release
 
 I can mount_ntfs without problems ad2s1 from freebsd!
 
 BUT I can't mount_ntfs ad0s! When I try to mount it
with the following
 command:
 mount_ntfs /dev/ad0s1 /mnt
 
 I get the following error:
 mount_ntfs: /dev/ad0s1: Invalid argument
 
 And in /var/log/messages I see this:
 Feb 21 13:46:39 lucifer /kernel: ad0s1: slice extends
beyond end of
 disk: truncating from 78140097 to 4408785 sectors
 Feb 21 13:46:39 lucifer /kernel: ntfs_loadntnode: BREAD
FAILED
 Feb 21 13:46:39 lucifer /kernel: ntfs_vget: CAN'T LOAD
ATTRIBUTES FOR
 INO: 0
 
 1) What is the problem with ad0?
 2) What can I do to resolve the problem so that I'm
able to mount_ntfs
 ad0s1?

Does mount_ntfs /dev/ad0s1c /mnt work?  I have had
similar moments of
darkness, and seem to recall that was one way out.  I'm
not sure of the
reason for this - it is something to do with the way
Windows installs itself
on the disk, and with the BSD disk name convention, the c
partition
represents the whole slice.  That's my theory, anyway
 ;-)
Nope, does not work :-(
Any other ideas are welcome! :-))
Yet another idea ;-)

Did you change first disk from basic to dynamic with WinXP?
The dynamic disks in XP world uses different way to store information 
for slices and are incompatible with mbr.

Thanks anyway!
Didier
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message
--
Regards,
Dancho Penev
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message


mount_ntfs fails

2003-02-21 Thread Didier Wiroth
Hey, 

I have two harddisks:
1) ad0 with 1 slice containing Windows XP pro
2) ad2 with two slices s1 is ntfs and s2 is freebsd 4.7-release

I can mount_ntfs without problems ad2s1 from freebsd!

BUT I can't mount_ntfs ad0s! When I try to mount it with the following
command:
mount_ntfs /dev/ad0s1 /mnt

I get the following error:
mount_ntfs: /dev/ad0s1: Invalid argument

And in /var/log/messages I see this:
Feb 21 13:46:39 lucifer /kernel: ad0s1: slice extends beyond end of
disk: truncating from 78140097 to 4408785 sectors
Feb 21 13:46:39 lucifer /kernel: ntfs_loadntnode: BREAD FAILED
Feb 21 13:46:39 lucifer /kernel: ntfs_vget: CAN'T LOAD ATTRIBUTES FOR
INO: 0

1) What is the problem with ad0?
2) What can I do to resolve the problem so that I'm able to mount_ntfs
ad0s1?

Thanks a lot
Didier


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: mount_ntfs fails

2003-02-21 Thread Daniel Bye
On Fri, Feb 21, 2003 at 01:54:57PM +0100, Didier Wiroth wrote:
 Hey, 
 
 I have two harddisks:
 1) ad0 with 1 slice containing Windows XP pro
 2) ad2 with two slices s1 is ntfs and s2 is freebsd 4.7-release
 
 I can mount_ntfs without problems ad2s1 from freebsd!
 
 BUT I can't mount_ntfs ad0s! When I try to mount it with the following
 command:
 mount_ntfs /dev/ad0s1 /mnt
 
 I get the following error:
 mount_ntfs: /dev/ad0s1: Invalid argument
 
 And in /var/log/messages I see this:
 Feb 21 13:46:39 lucifer /kernel: ad0s1: slice extends beyond end of
 disk: truncating from 78140097 to 4408785 sectors
 Feb 21 13:46:39 lucifer /kernel: ntfs_loadntnode: BREAD FAILED
 Feb 21 13:46:39 lucifer /kernel: ntfs_vget: CAN'T LOAD ATTRIBUTES FOR
 INO: 0
 
 1) What is the problem with ad0?
 2) What can I do to resolve the problem so that I'm able to mount_ntfs
 ad0s1?

Does mount_ntfs /dev/ad0s1c /mnt work?  I have had similar moments of
darkness, and seem to recall that was one way out.  I'm not sure of the
reason for this - it is something to do with the way Windows installs itself
on the disk, and with the BSD disk name convention, the c partition
represents the whole slice.  That's my theory, anyway  ;-)

-- 
Daniel Bye

PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc
PGP Key fingerprint: 3D73 AF47 D448 C5CA 88B4 0DCF 849C 1C33 3C48 2CDC
 _
  ASCII ribbon campaign ( )
 - against HTML, vCards and  X
- proprietary attachments in e-mail / \

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message



Re: mount_ntfs fails

2003-02-21 Thread Wiroth Didier
On Fri, 21 Feb 2003 13:15:03 +
 Daniel Bye [EMAIL PROTECTED] wrote:
 On Fri, Feb 21, 2003 at 01:54:57PM +0100, Didier Wiroth
 wrote:
  Hey, 
  
  I have two harddisks:
  1) ad0 with 1 slice containing Windows XP pro
  2) ad2 with two slices s1 is ntfs and s2 is freebsd
 4.7-release
  
  I can mount_ntfs without problems ad2s1 from freebsd!
  
  BUT I can't mount_ntfs ad0s! When I try to mount it
 with the following
  command:
  mount_ntfs /dev/ad0s1 /mnt
  
  I get the following error:
  mount_ntfs: /dev/ad0s1: Invalid argument
  
  And in /var/log/messages I see this:
  Feb 21 13:46:39 lucifer /kernel: ad0s1: slice extends
 beyond end of
  disk: truncating from 78140097 to 4408785 sectors
  Feb 21 13:46:39 lucifer /kernel: ntfs_loadntnode: BREAD
 FAILED
  Feb 21 13:46:39 lucifer /kernel: ntfs_vget: CAN'T LOAD
 ATTRIBUTES FOR
  INO: 0
  
  1) What is the problem with ad0?
  2) What can I do to resolve the problem so that I'm
 able to mount_ntfs
  ad0s1?
 
 Does mount_ntfs /dev/ad0s1c /mnt work?  I have had
 similar moments of
 darkness, and seem to recall that was one way out.  I'm
 not sure of the
 reason for this - it is something to do with the way
 Windows installs itself
 on the disk, and with the BSD disk name convention, the c
 partition
 represents the whole slice.  That's my theory, anyway
  ;-)
Nope, does not work :-(
Any other ideas are welcome! :-))
Thanks anyway!
Didier

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-questions in the body of the message