So I have installed two disks on my new unRAID.

 

Assigned the 750GB, formated it (faster than expected, see other thread) and plan to mount my 500GB (full of data, NTFS formated), so I can copy from it.

 

unRAID reports the 500GB disk as sdb (of course I leave it unassigned).

 

Followed the wiki instructions, my knowledge on Linux maybe basic (maybe not so much), but my "computing" knowledge quite extensive. So it seems pretty simple.

 

Followed the first two commands in wiki, without error, but the third (mount), fails NOT giving a failure, but rather outputting the help text (like I did something wrong in syntax).

 

The disk I selected was of course sdb1 (which IS present in /dev).

"old_data" folder indeed exists.

 

I even copied the command string right from wiki and pasted on my telnet (editing the disk part of course). Same result.

 

Maybe beta6 mount syntax is a bit different?

(btw in mount help text, nothing weird shows up, my string seems to be ok)

 

Running "mount" by itself shows that indeed sdb1 didn't mount.

 

EDIT (well no edit, new data I just found out)...

 

I eliminated -t ntfs parameter.

System of course whined BUT said that it will (correctly assume) ntfs!

 

AND MOUNTED the drive!

 

How come?

 

 

 

Which set of instructions from the wiki did you follow?  The instructions for READ-ONLY, or those for READ-WRITE of a USB drive?

 

Glad the mount command recognized the file-system.  Nice that it is smart like that.  You probably have it mounted as read-only? (The built-in NTFS drive is not suitable for writing or creating files...)

 

If you can, cut and paste the actual messages that failed in this thread.  Hard to figure out how to help going forward when working blind.

 

Joe L.

Joe, there are 2 pages concerning ntfs support, and they use three forms of the 'type ntfs' phrase, -t ntfs, -type ntfs, and -t ntfs-3g.  Are they all correct?  There is also a -type vfat.

 

http://lime-technology.com/wiki/index.php?title=Copy_files_from_a_NTFS_drive

http://lime-technology.com/wiki/index.php?title=Mounting_an_external_USB_drive_having_an_existing_NTFS_file_system_in_READ/WRITE_mode_to_transport_files_from/to_unRaid_server

 

Edit:  Also, on the same line as the vfat option, should that hdj be hdj1?  And above for the alternative mount instruction with extra parameters, should new be old_data?

 

Joe, there are 2 pages concerning ntfs support, and they use three forms of the 'type ntfs' phrase, -t ntfs, -type ntfs, and -t ntfs-3g.  Are they all correct?  There is also a -type vfat.

You are, of course, correct.  The correct syntax is

mount -t ntfs device_partition mount_point

or

mount -t ntfs-3g device_partition mount_point

or

mount -t vfat device_partition mount_point

mount -type is not correct.

 

I did not add this wiki entry myself, but it is based on a post I made a while ago.  (I'll need to verify I did not get the syntax wrong on my original post)

http://lime-technology.com/wiki/index.php?title=Copy_files_from_a_NTFS_drive

 

 

Edit:  Also, on the same line as the vfat option, should that hdj be hdj1?  And above for the alternative mount instruction with extra parameters, should new be old_data?

Yes, and Yes.  I just fixed them.

 

I just added this page to the wiki the other night.

http://lime-technology.com/wiki/index.php?title=Mounting_an_external_USB_drive_having_an_existing_NTFS_file_system_in_READ/WRITE_mode_to_transport_files_from/to_unRaid_server

 

It is correct. In fact, I just cut and pasted its exact commands to my current 4.3-beta6 version of unRaid.

My telnet session is shown below:

 

root@Tower:~# cd /boot

root@Tower:/boot# ls

spin_drives.sh*

bzimage*

bzroot*             

nc*

netcat*

syslinux.cfg*

config/             

packages/

drive_id.sh*       

readme.txt*

ldlinux.sys*       

smtp_check_unraid.sh* 

unmenu*

root@Tower:/boot# ls packages

ntfs-3g-1.2216-i486-1McD.tgz*

root@Tower:/boot# installpkg /boot/packages/ntfs-3g-1.2216-i486-1McD.tgz

Installing package ntfs-3g-1.2216-i486-1McD...

PACKAGE DESCRIPTION:

ntfs-3g: Mount NTFS read-write in userspace - NTFS-3G 1.2216

ntfs-3g:

ntfs-3g: The NTFS-3G driver is an open source, freely available NTFS driver for

ntfs-3g: Linux with read and write support. It provides safe and fast handling

ntfs-3g: of the Windows XP, Windows Server 2003, Windows 2000 and Windows Vista

ntfs-3g: file systems. Most POSIX file system operations are supported, with

ntfs-3g: the exception of full file ownership and access right support.

ntfs-3g:

ntfs-3g: Homepage: http://www.ntfs-3g.org/

ntfs-3g: (Compiled by [email protected] on 18-Feb-2008)

Executing install script for ntfs-3g-1.2216-i486-1McD...

 

root@Tower:/boot# ls -l /mnt/user/data/usb

total 0

root@Tower:/boot# mount -t  ntfs-3g  /dev/sdb1 /mnt/user/data/usb/

root@Tower:/boot# mount

proc on /proc type proc (rw)

sysfs on /sys type sysfs (rw)

usbfs on /proc/bus/usb type usbfs (rw)

/dev/sda1 on /boot type vfat (rw)

fusectl on /sys/fs/fuse/connections type fusectl (rw)

/dev/md4 on /mnt/disk4 type reiserfs (rw,noatime,nodiratime)

/dev/md9 on /mnt/disk9 type reiserfs (rw,noatime,nodiratime)

/dev/md10 on /mnt/disk10 type reiserfs (rw,noatime,nodiratime)

/dev/md5 on /mnt/disk5 type reiserfs (rw,noatime,nodiratime)

/dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime)

/dev/md3 on /mnt/disk3 type reiserfs (rw,noatime,nodiratime)

/dev/md6 on /mnt/disk6 type reiserfs (rw,noatime,nodiratime)

/dev/md7 on /mnt/disk7 type reiserfs (rw,noatime,nodiratime)

/dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime)

/dev/md8 on /mnt/disk8 type reiserfs (rw,noatime,nodiratime)

shfs on /mnt/user type fuse.shfs (rw,nosuid,nodev)

/dev/sdb1 on /mnt/user/data/usb type fuseblk (rw,nosuid,nodev,noatime,allow_othe

r,blksize=4096)

root@Tower:/boot#

root@Tower:/boot# ls /mnt/user/data/usb

System\ Volume\ Information/                 

backups/

inbox.CSV*

RECYCLER/

 

Joe L.

- I used the command for read-only.

- I used -t not -type.

- No error was produced, I just got what you get if you mess with the parameters (which I think is the same output as -h)

- I didn't use ntfs-3g, just the builtin fs (now that you mention it Tom should move to ntfs-3g some time soon eh?)

 

 

Joe L...give me your address so I can come round and give you a big kiss. I got my NTFS drive mounted to read/write with your instructions first go. Now I have extinguished the last need I had for running XP boot camp on my Mac so just deleted it. I am so happy. The drive wouldn't mount running the ntfs-3g driver on my Mac and it wouldn't on the unRAID either with the mount command you typed but gave me an option to put -o force after it. Not sure why but when I did it worked.

 

Everyday unRAID keeps making me happier but not my wallet when I now have a reason to get more drives and upgrade to Pro earlier than I had planned.

 

Thanks again.

 

Ste.

Joe L...give me your address so I can come round and give you a big kiss. I got my NTFS drive mounted to read/write with your instructions first go.

I'm very happy for you... but not *that* happy...

Now I have extinguished the last need I had for running XP boot camp on my Mac so just deleted it. I am so happy. The drive wouldn't mount running the ntfs-3g driver on my Mac and it wouldn't on the unRAID either with the mount command you typed but gave me an option to put -o force after it. Not sure why but when I did it worked.

The "-o force" option will mount the drive even if it was not cleanly unmounted

Everyday unRAID keeps making me happier but not my wallet when I now have a reason to get more drives and upgrade to Pro earlier than I had planned.

 

Thanks again.

 

Ste.

Joe L...give me your address so I can come round and give you a big kiss. I got my NTFS drive mounted to read/write with your instructions first go.

I'm very happy for you... but not *that* happy...

 

Hehe...your loss 

 

I noticed the mount command has changed slightly on the Wiki page. Was there any particular problem with the old command?

 

Ste.

Yup, my loss.  But no need for any additional show of affection.  Others might be offended    

You can always make an offer of any large amount of currency to repay me for my advice... Who knows, I might be enticed to accept it. Even if I don't accept it,  Tom might.  Amounts should be greater than 0, evenly divisible by 32768 and be less than 2E32 in order to fit into my self-made checkbook program I hand-coded in binary..   Send small unmarked bills to "The Old Programmer's Home" .........

 

As far as the extra mount options:

Without them, files were presented to SAMBA with hidden and system attributes set.  The added parameters make files visible without having to enable "Show hidden files", etc in windows.