ReadyNAS Duo V2 saves to local space, rather than HDD?

Don't mount/ dev/sda, it should be /dev/c/c on Duo v2, Duo v2 has LVM level.

Duplicate post viewtopic.php?f=7&t=63260

Here is the drive partitions and mounts:

root@nas-A0-3D-F9:~# fdisk -l

WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.


Disk /dev/sda: 2000.4 GB, 2000398934016 bytes
256 heads, 63 sectors/track, 242251 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1      242252  1953514583+  ee  GPT

Disk /dev/md0: 4293 MB, 4293906432 bytes
2 heads, 4 sectors/track, 1048317 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/md0 doesn't contain a valid partition table

Disk /dev/md1: 536 MB, 536858624 bytes
2 heads, 4 sectors/track, 131069 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/md1 doesn't contain a valid partition table

Disk /dev/md2: 1995.6 GB, 1995563778048 bytes
2 heads, 4 sectors/track, 487198188 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/md2 doesn't contain a valid partition table

/dev/md[012] are normal. /dev/sda1 should never be mounted on its own, its part of the md0 array. It should also have three partitions on it (4GB(md0,root),512MB(md1,swap),xxGB(md2,data)). Trying to mount it directly will certainly corrupt your data. fdisk should also not be used, there is sfdisk for that to handle GPT stuff correctly.

If you just got the system, there shouldn't be much data on it yet. If you have been poking around and mounting stuff incorrectly, I would suggest doing a factory default to clean it off any wrong doing. /c mountpoint is part of the md2 data array, if Transmission is saving to /c/media, data would be fine on there. Sounds like somehow you are saving data to the md0 root partition that is only 4GB.

At this point, it already seems out of scope for Support also until a factory default is performed, and the issues cleaned up.

Seems like a factory reset fixed it. I did everything the same, I don't know why this time it worked >.> haha