stevecyb
Dabbler
- Joined
- Oct 17, 2019
- Messages
- 30
Howdy...I've got my mini-XL, and it's up and running, in a very limited way because two of the drives I bought elsewhere to go in it were DOA (they don't show up at all, and when I put them in a different system...they didn't show up at all).
I thought I'd try to format one of the disks as NTFS, put it into the NAS, and see if I could copy data TO the disk. (The idea is to copy data to the disk, then remove it and keep it offsite as a backup. I've got basically no other way to get large amounts of data out of here as my internet connection is limited to 12 GB/month.)
The NAS GUI asserts that the drive is "imported" even if I do nothing at all. If I go to import disk and provide it /mnt/b as a location, it *seems* to work. I can see the minuscule amount of data I put onto the disk just to be able to check it. But, if I try to copy data TO that location, it QUICKLY fills up. A (supposed) 4TB NTFS partition fills up after less than 2GB.
Apparently, the disk isn't mounting in the normal way; what's happening is "importing" is simply copying data off the disk to wherever I tell it to go. (I could have given it the path to my dataset, and that would have made some sense...except that I'm not interested in copying data FROM the disk.)
My supposed mount point apparently lives on the SATADOM. I discovered this when I tried copying a large (100GB) file to it; it filled up after less than 2GB. And any files I copied there weren't actually on the disk when I mounted it on a different system.
So I poked around a bit and found nothing useful.
Trying to actually mount the drive at the command line:
ntfs-3g /dev/ada7 /mnt/b
spits back "fuse: failed to open fuse device: no such file or directory"
(There is a /dev/ada7 object, but gpart won't show it.)
Any ideas on how to do this?
I thought I'd try to format one of the disks as NTFS, put it into the NAS, and see if I could copy data TO the disk. (The idea is to copy data to the disk, then remove it and keep it offsite as a backup. I've got basically no other way to get large amounts of data out of here as my internet connection is limited to 12 GB/month.)
The NAS GUI asserts that the drive is "imported" even if I do nothing at all. If I go to import disk and provide it /mnt/b as a location, it *seems* to work. I can see the minuscule amount of data I put onto the disk just to be able to check it. But, if I try to copy data TO that location, it QUICKLY fills up. A (supposed) 4TB NTFS partition fills up after less than 2GB.
Apparently, the disk isn't mounting in the normal way; what's happening is "importing" is simply copying data off the disk to wherever I tell it to go. (I could have given it the path to my dataset, and that would have made some sense...except that I'm not interested in copying data FROM the disk.)
My supposed mount point apparently lives on the SATADOM. I discovered this when I tried copying a large (100GB) file to it; it filled up after less than 2GB. And any files I copied there weren't actually on the disk when I mounted it on a different system.
So I poked around a bit and found nothing useful.
Trying to actually mount the drive at the command line:
ntfs-3g /dev/ada7 /mnt/b
spits back "fuse: failed to open fuse device: no such file or directory"
(There is a /dev/ada7 object, but gpart won't show it.)
Any ideas on how to do this?