NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
sudo: unable to write to /var/lib/sudo/ts/admin: No space left on device
I've SSHed into my NAS and got this message:
sudo: unable to write to /var/lib/sudo/ts/admin: No space left on device
This has all seemed to start after doing some tinkering with the Logitech Media Server which I now suspect, could have been installed incorrectly in the wrong location.
If I run df -h the result is:
Filesystem Size Used Avail Use% Mounted on
udev 10M 4.0K 10M 1% /dev
/dev/md0 4.0G 3.7G 4.0K 100% /
tmpfs 491M 4.0K 491M 1% /dev/shm
tmpfs 491M 3.7M 487M 1% /run
tmpfs 246M 1.4M 244M 1% /run/lock
tmpfs 491M 0 491M 0% /sys/fs/cgroup
/dev/md127 2.8T 1.9T 855G 70% /data
/dev/md127 2.8T 1.9T 855G 70% /home
/dev/md127 2.8T 1.9T 855G 70% /apps
If I attempt to logon via the ReadyNAS GUI I continually get asked for the user and password, entering admin and then password just loops back around to another dialogue box with the same request.
Please reassure me that I haven't completely borked the ReadyNAS OS! đł
10 Replies
Thanks for any assistance or guidance on how to resolve this.
As this seems to be related between trying to optimise my LMS setup but now seems to involve fixing something I've broken within the ReadyNAS OS, I've initially posted there in this thread:
Error on 'Clear library and rescan everything' > database or disk is full
and I'll be bouncing between there and here.
There's space on the NAS itself, over 800GB but it seems I've filled up the OS partition.
it seems I've filled up the OS partition.
Correct.
Thanks for any assistance or guidance on how to resolve this.
You have to remove the files that filled it.
That can be done with ssh. Or it can be done by doing a factory reset - which of course requires a full backup, since it reformats the disks. It also would require reinstalling any apps - which can be a problem now that the Netgear repos have been taken down.
In your case, I'd start by manually uninstalling the Logitech Media Server. If you have an x86 NAS, then the OS partition is BTRFS (unless you migrated the disks from an Arm NAS). If that is the case, you should also try a balance from ssh after you remove the Logitech server.
In general, you want apps (and app data) stored on the data volume. One way to do that is to create an LMS folder manually in /apps, and then move OS folders for the app to that folder. Create soft links that point to the new locations.
(Note /apps is a mount point for /data/.apps)
Thanks for replying Stephen.
To update, I did a reboot from ssh, logged back in, changed to root and didn't get the error.
Running df -h again gets:
/dev/md0 4.0G 3.1G 585M 85% /
so a small amount of space reclaimed...Unrelated aside: why don't I have the option to preformat text like in my original post?
/dev/md0 4.0G 3.1G 585M 85% /
so a small amount of space reclaimed...Still dangerously full, so you should do more to reclaim it.
Unrelated aside: why don't I have the option to preformat text like in my original post?
There are some things I like about the new forum software, but there are some aspects that are steps back. You can post feedback here: We Want Your Feedback | NETGEAR Communities But don't expect quick action.
I see the same formatting options in the toolbar in replies as I see in new discussion threads. So I'm not sure what you mean.
I wish they'd put back underlines, and sometimes the strikethroughs were helpful. And there are inconsistencies - PMs have fewer options than forum posts.
FWIW, my impression is that the performance is a bit worse than the old forum.
I see the same formatting options in the toolbar in replies as I see in new discussion threads. So I'm not sure what you mean.
I only see đ
I'm using the Deepseek LLM for some pointers (with a bit of wariness that it advises something totally wrong) and may have got somewhere.
Am logged in as root, gone to base directory and ran:
du -sh * | sort -hr
which gave:
du: cannot access 'proc/2723/task/6523/fd/109': No such file or directory du: cannot access 'proc/6903/task/6903/fd/3': No such file or directory du: cannot access 'proc/6903/task/6903/fdinfo/3': No such file or directory du: cannot access 'proc/6903/fd/3': No such file or directory du: cannot access 'proc/6903/fdinfo/3': No such file or directory 1.5T data 4.0G apps 2.2G root 470M usr 441M var 33M lib 30M frontview 11M sbin 11M etc 6.6M bin 5.4M run 4.7M opt 8.0K dev 4.0K tmp 4.0K lib64 0 sys 0 srv 0 proc 0 mnt 0 media 0 bootthen I wanted to drill down into the root directory and see what was taking up 2.2G of space in there but even though I was a root user, cd /root didn't do anything.
then
mount | grep " / "
gave
/dev/md0 on / type btrfs (rw,noatime,nodiratime,nospace_cache,subvolid=5,subvol=/)
which Deepseek says the nospace_cache is a red flag for Btrfs filesystem corruption and that needs repairing, ideally from a bootable USB drive though there is a less reliable method of using the repair tool on the mounted filesystem.
Root isn't "/root", it's just "/". cd /
So it looks like I've corrupted the filesystem on the system partition.
Is this repairable?
btrfs fi show /dev/md0gives
Label: '758ad464:root' uuid: f08a0f90-adfd-47e1-a519-189247895ced Total devices 1 FS bytes used 1.14GiB devid 1 size 4.00GiB used 3.67GiB path /dev/md0Now if I input
df -hthe results are
Filesystem Size Used Avail Use% Mounted on udev 10M 4.0K 10M 1% /dev /dev/md0 4.0G 1.3G 2.4G 35% / tmpfs 491M 4.0K 491M 1% /dev/shm tmpfs 491M 3.7M 487M 1% /run tmpfs 246M 4.0M 242M 2% /run/lock tmpfs 491M 0 491M 0% /sys/fs/cgroup /dev/md127 2.8T 1.5T 1.4T 52% /data /dev/md127 2.8T 1.5T 1.4T 52% /apps /dev/md127 2.8T 1.5T 1.4T 52% /homeso there's more space on /dev/md0 but the LLM is now advising that I run
btrfs check --repairfrom Ubuntu that's installed on a USB drive but is it possible to amend the boot order in the BIOS using SSH?
Thanks for any assistance.
/dev/md0 4.0G 1.3G 2.4G 35% /
This is normal - did you remove files to bring it down to this level?
btrfs check --repair
Don't. The --repair is quite risky, so it is good to avoid doing if you have other options. And as Sandsharkâ says, there is no evidence that the file system needs repair.
Instead run this (using ssh on the NAS, logged in as root) :
btrfs balance //If you get an error on the balance, please post the details.
I only see ...
Which is what I see on bothe new discussions and replies. What format options are you looking for????
I fail to see anything that indicates there is a BTRFS error on /dev/md0. It's just too full. As StephenBâ has been telling you, you need to find and delete some of the files that are there, most likely the result of LMS. If the files are corrupted, then a BTRFS repair isn't going to fix them, but an OS re-install might. But your OS partition is far too full to try that now.
Standard Linux df on a BTRFS file system is unreliable. You need to run btrfs filesystem df /. In particular, you need to pay attention to both the data and metadata usage. As StephenBâ also told you, you may need to run a balance on the OS partition to reclaim metadata.
I've never used LLM, but it's clearly designed for use on a standard BTRFS-based Linux installation. I think you should stop listening to it so much. Booting to a USB system to repair the ReadyNAS file system is really a bad idea. You should be booting to tech support mode, but I see nothing that indicates you need to do that at this time.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
