That df output still doesn’t look right.
/CacheVolume and /DataVolume should be /dev/sda4. Here’s what I get:
WDMyCloud:~# cd /
WDMyCloud:/# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.9G 629M 1.2G 35% /
/dev/root 1.9G 629M 1.2G 35% /
tmpfs 40M 9.4M 31M 24% /run
tmpfs 40M 64K 40M 1% /run/lock
tmpfs 10M 0 10M 0% /dev
tmpfs 5.0M 0 5.0M 0% /run/shm
tmpfs 100M 4.0M 96M 4% /tmp
/dev/root 1.9G 629M 1.2G 35% /var/log.hdd
ramlog-tmpfs 40M 8.7M 32M 22% /var/log
/dev/sda4 3.6T 1.9T 1.7T 53% /DataVolume
/dev/sda4 3.6T 1.9T 1.7T 53% /CacheVolume
/dev/sda4 3.6T 1.9T 1.7T 53% /nfs/Public
/dev/sda4 3.6T 1.9T 1.7T 53% /nfs/Media
There’s a thread that solved this somewhere, and it involved mounting sda4… can I find it…?
Hmm… maybe this one:
which used
mount /dev/sda4 /DataVolume
mount -bind /DataVolume/cache /CacheVolume
or this one:
which used
/etc/init.d/mountDataVolume.sh
or this:
which has a very similar df result to yours, including the /dev/root for /CacheVolume, and Fox_exe suggested:
mount -t ext4 /dev/sda4 /DataVolume
I’ll be honest with you: this is getting beyond my pay grade… Linux file system mounting stuff is just a bit beyond my experience, and you may be better off asking for assistance from more knowledgeable types. @Bennor, perhaps?
But I note that mounting /dev/sda4 as /DataVolume seemed to do the trick in two of the cases above, with different degrees of explicit control (i.e. Fox_exe enforced the ext4 file type, rather than letting it automatically decide; it will be ext4).
