This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Re: System volume 'root' usage is 100% and /dev/md0 is full
The reason you couldn't find it was that at some point your encrypted volume wasn't mounted (perhaps the USB key wasn't connected when you booted the NAS) and a Replicate backup job ran and filled the OS partition on the NAS.
When you looked at the system the data volume was mounted. There was data under /data on the OS partition but you couldn't tell that.
I have passed on a summary of what's happened to our engineers and am waiting for their suggestion. However as it is a long weekend in the US I don't expect a response for at least a few days.
Re: System volume 'root' usage is 100% and /dev/md0 is full
I've gone through all of the directories that come up with ls.
Is there something I'm missing?
The only one I didn't check in is data because that is actually the NAS volume that stores the backup.
Here is a du -hsx of the entire root excluding data
root@RN102Backup:/# ls apps boot dev frontview lib media opt root sbin srv tmp var bin data etc home lost+found mnt proc run selinux sys usr root@RN102Backup:/# du -hsx --exclude data * | sort -rh | head -10 du: cannot access `proc/22248/task/22248/fd/4': No such file or directory du: cannot access `proc/22248/task/22248/fdinfo/4': No such file or directory du: cannot access `proc/22248/fd/4': No such file or directory du: cannot access `proc/22248/fdinfo/4': No such file or directory 166M var 130M usr 29M lib 24M frontview 7.9M sbin 5.5M bin 5.2M opt 4.2M etc 1.8M apps 324K run
Here are the individual folders
root@RN102Backup:/# cd / root@RN102Backup:/# ls apps boot dev frontview lib media opt root sbin srv tmp var bin data etc home lost+found mnt proc run selinux sys usr
root@RN102Backup:/# cd /apps root@RN102Backup:/apps# du -hsx * | sort -rh | head -10 0 DO_NOT_DELETE
root@RN102Backup:/apps# cd /boot root@RN102Backup:/boot# du -hsx * | sort -rh | head -10 du: cannot access `*': No such file or directory
root@RN102Backup:/boot# cd /dev root@RN102Backup:/dev# du -hsx * | sort -rh | head -10 4.0K boot_reason 0 zero 0 vpd 0 urandom 0 ubi_ctrl 0 ubi0_0 0 ubi0 0 ttyS1 0 ttyS0 0 ttypf
root@RN102Backup:/sbin# cd /srv root@RN102Backup:/srv# du -hsx * | sort -rh | head -10 du: cannot access `*': No such file or directory
root@RN102Backup:/srv# cd /home root@RN102Backup:/home# du -hsx * | sort -rh | head -10 0 admin
root@RN102Backup:/home# cd /lost+found root@RN102Backup:/lost+found# du -hsx * | sort -rh | head -10 du: cannot access `*': No such file or directory
root@RN102Backup:/lost+found# cd /mnt root@RN102Backup:/mnt# du -hsx * | sort -rh | head -10 du: cannot access `*': No such file or directory
root@RN102Backup:/mnt# cd /proc root@RN102Backup:/proc# du -hsx * | sort -rh | head -10 du: cannot access `21961/task/21961/fd/3': No such file or directory du: cannot access `21961/task/21961/fdinfo/3': No such file or directory du: cannot access `21961/fd/3': No such file or directory du: cannot access `21961/fdinfo/3': No such file or directory 0 zoneinfo 0 vmstat 0 vmallocinfo 0 version 0 uptime 0 tty 0 timer_list 0 sysvipc 0 sysrq-trigger 0 sys
root@RN102Backup:/proc# cd /selinux root@RN102Backup:/selinux# du -hsx * | sort -rh | head -10 du: cannot access `*': No such file or directory root@RN102Backup:/selinux#
root@RN102Backup:/run# du -hsx * | sort -rh | head -10 220K udev 164K lock 56K readydrop 12K systemd 8.0K mdadm 8.0K blkid 4.0K utmp 4.0K usb 4.0K sshd.pid 4.0K spindown
I was trying to avoid a factory reset because this NAS is the only backup of my other NAS, and I don't have any other drives to make an additional backup, and I'm not going to be without a backup, even if it is for a matter of hours.
This NAS is in RAID 1 , and it is encrypted using the built-in encryption Frontview provides. Not sure if this matters, but I figured I should note that.
Re: System volume 'root' usage is 100% and /dev/md0 is full
The reason you couldn't find it was that at some point your encrypted volume wasn't mounted (perhaps the USB key wasn't connected when you booted the NAS) and a Replicate backup job ran and filled the OS partition on the NAS.
When you looked at the system the data volume was mounted. There was data under /data on the OS partition but you couldn't tell that.
I have passed on a summary of what's happened to our engineers and am waiting for their suggestion. However as it is a long weekend in the US I don't expect a response for at least a few days.
The reason you couldn't find it was that at some point your encrypted volume wasn't mounted (perhaps the USB key wasn't connected when you booted the NAS) and a Replicate backup job ran and filled the OS partition on the NAS.
Great diagnosis!
Kind of a scary problem though, hopefully development will close off that possibility in a future release.
