Parse_mount: parse(sun): gathered options: fstype=auto,noatime,utf8 Parse_mount: parse(sun): expanded entry: -fstype=auto,noatime,utf8 :/dev/disk/by-label/WD2.5TB Lookup_mount: lookup(file): WD2.5TB -> -fstype=auto,noatime,utf8 :/dev/disk/by-label/WD2.5TB Lookup_mount: lookup(file): looking up WD2.5TB Handle_packet_missing_indirect: token 33, name WD2.5TB, request pid 6326 I am curious if there is a solution or patch to this. The problem seems to be that automount always add -s option to its mount command. Here is the debug log (with automount -d). only way to mess up would be to assign the old drive to unRaid and clear/reformat it before you got your data copied from it.Further investigation found that the problem was with automount command invoked. use of the -r option to the mount command will mount the drive as read-only so you should be safe. I've never done this on my array, but I see no reason why it should not work. (you must stop the array to assign it) It will then be cleared and formatted and made available as part of the unRaid array. Once the data is off of the old NTFS/FAT drive and copied to an unraid data drive, and the old drive is then unmounted, you can then use the devices web-management page to asssign the old drive to a slot in the unraid array. Lastly, to unmount the old disk after copying all the files from it type: To change directory back to your home directory of /root you can type: (previously, you changed directory to it to issue the copy command, now you need to change directory to someplace else so you can unmount it) You will now need to change directory so that your current directory is not on the old disk you will be unmounting. If you followed instructions earlier, you used the 'cd' command to change directory to the old disk you were copying from. The un-mount command will issue an error message stating that the device is 'busy.' A disk is considered busy if anybody is reading or writing it, or if anybody or any program has it as the current directory. Next, you will be unable to un-mount a disk if it is in use. This will have the side effect of spinning up any disks, so it might take a few seconds to complete and return to a prompt. The command to request that all buffered data be written to the physical disks is the sync command, so type: The first step in unmounting a drive is to ensure all buffered data has been written to it. To preserve the original date/timestamp of the files, use this command instead:Ĭp -r -no-preserve=mode -preserve=timestamps * /mnt/disk1Īnother useful option is to turn on verbose mode, and save the output to a file so you can check the results of the copy for any errors:Ĭp -v -r -no-preserve=mode -preserve=timestamps * /mnt/disk1 | tee /boot/copyresults.txt However all of the files will have the current date/timestamp. To copy all your files to disk1 type this: Then, you can use the unix cp command to copy your files to an existing data drive you previously added to your unRaid array. In some cases useful info is found in syslog - try Missing codepage or helper program, or other error Mount: wrong fs type, bad option, bad superblock on /dev/sdc, :/boot/unmenu# mount -r -t ntfs /dev/hdj1 /mnt/old_data -o umask=111,dmask=000 -v (I of course edited it according to my /dev/sdX) When using the 'old command', I got this error: Since I am a Linux Newbie and just figured this out myself after getting following error, can you Pros please verify my information and clarify if the '-o umask=111,dmask=000 -v' statements are also valid with my new method. Mount -t ntfs-3g /dev/hdj1 /mnt/old_data -o umask=111,dmask=000 -v If you want to mount HDDs above 2.2GB formated with NTFS file format, you need to install the 'ntfs-3g driver' via unMENU and then mount the disk with It can be downloaded to your server and installed if it is necessary to write to a mounted NTFS file-system. There is a new ntfs-3g driver that can be used to both read and write to an NTFS file-system, but it is not supplied with unRAID. It is unable to create files or to expand the size of existing files without corrupting the file-system. Do not attempt to mount the built-in ntfs driver in a read/write mode. This is a limitation of the driver, not one of unRAID. The NTFS driver supplied with unRAID is not able to be used in a read/write mode. Note that the previous mount command will result in all the files being read-only. The root of the file-system will be at /mnt/old_data.

Once the file-system is mounted, you can use the 'cp' (copy) command to copy files from the NTFS drive. The umask and dmask options will prevent the unix 'execute' bit being set when you copy files to other disks, which will translate as a hidden/system file under Samba. Mount -r -t ntfs /dev/hdj1 /mnt/old_data -o umask=111,dmask=000 -v Last, mount the drive on the mount point. Next step, create a mount point (an empty directory) First step, load the NTFS driver module into memory.

Ntfs 3g unmount