Unable to update Synology packages

Currently reading
Unable to update Synology packages

208
46
NAS
DS918+, DS414j
Operating system
  1. Linux
  2. Windows
  3. other
Mobile operating system
  1. Android
All I get is:
Unable to update "<package>". The free space of system partition is insufficient. Please contact the Synology support team for help.
They've basically told me they've deleted logs.
Asked me to reboot the NAS.
Asked me to Data scrub the storage pool.
None of it has helped.

Anyone got any idea, please?
 
208
46
NAS
DS918+, DS414j
Operating system
  1. Linux
  2. Windows
  3. other
Mobile operating system
  1. Android
Last edited:
No idea why installing a package requires the system partition, but it does.
They have apparently cleared the logs and don't appear to have found anything.
Only 3rd party package I have is so I can use wireguard.
I've moved from ALL synology packages except docker and php.
Pretty much EVERYTHING is running in docker except webstation and the above 2.

I'd rather not reset the system as other than this issue it's all ticking along rather well.

They pointed me at:
 

fredbert

Moderator
NAS Support
Subscriber
3,711
1,485
NAS
DS1520+, DS218+, DS215j
Router
  1. RT2600ac
  2. MR2200ac
Operating system
  1. macOS
Mobile operating system
  1. iOS
On my main NAS if SSH to it and run df -h this is what it looks like.
1653585052359.png


I'd be looking at that / row and start checking the usage of directories that are not list in the other rows. For instance, if I sudo du -h d-1 /usr, other than a lot of 'Permission denied' messages, I see it's using 1.6GB of space. That's 1.6GB of a maximum of 2.3GB. The other big directory is /var at 298MB. The rest are at most a few MB, but mostly KB.
 
208
46
NAS
DS918+, DS414j
Operating system
  1. Linux
  2. Windows
  3. other
Mobile operating system
  1. Android
Last edited:
Code:
df -h
gives:
1653586108359.png

Code:
sudo du -h d-1 /usr
I get 1.5GB of space used, with
Code:
/usr/syno
using 743MB of it.
Code:
/var
is using 181MB.
Code:
cd /
ls -al
I get the following interesting item:
Code:
-rw-r--r--    1 root        root  20480 May 25 07:17 SynoUpgrade.tar
should that be there?
The main output is:
1653587293587.png
 
208
46
NAS
DS918+, DS414j
Operating system
  1. Linux
  2. Windows
  3. other
Mobile operating system
  1. Android
They're all rigged up with persistent volumes. :)

Just to quickly say thanks for all the ideas and help! :)

I have just destroyed the containers and removed the non persistent volumes but no change.
I'll be rebuilding the containers with new mappings to resolve those tomorrow.
 
208
46
NAS
DS918+, DS414j
Operating system
  1. Linux
  2. Windows
  3. other
Mobile operating system
  1. Android
Last edited:
Thanks @fredbert good to know that's correct.
Not sure where I move next. :(

I now have nothing but persistent volumes in docker and have made sure any temporary volumes have been deleted using portainer.
-- post merged: --

Hmm, looking further down at the volumes.
volume1 isn't owned by root and group root it's owned by one of my service accounts and group users.
I have no idea how that happened, very odd, but I think that's probably a separate issue.
 

fredbert

Moderator
NAS Support
Subscriber
3,711
1,485
NAS
DS1520+, DS218+, DS215j
Router
  1. RT2600ac
  2. MR2200ac
Operating system
  1. macOS
Mobile operating system
  1. iOS
I would methodically [i.e. tediously] go through each of the /<dir> locations that aren't listed in df as a separate mount point. See if using sudo du -d 1 -h /<dir> reveals if there is one that is eating up space, because something has used up the rest of your 2.3GB system partition.
 
208
46
NAS
DS918+, DS414j
Operating system
  1. Linux
  2. Windows
  3. other
Mobile operating system
  1. Android
Last edited:
@fredbert will do, thank you.
Synology support came back saying he'd been on annual leave and had I changed the password?
I pointed out he'd been logged into the system for over 19 hours and then (after changing the password) noticed the username he was trying to use was incorrect.
-- post merged: --

Is there any way I could run:
Code:
sudo du -d 1 -h /
and exclude the /volume* mappings?

Yes I can:
Code:
sudo du -d 1 -h / --exclude=/volume1 --exclude=/volume2

Ok... I may have found it:
532M /volumeUSB1

I have NO USB plugged into the device.

OK I've rm -r the sub folders and I've got 80% free now!
1653646913567.png

How best am I to safely remove the /volumeUSB1 ?
 

fredbert

Moderator
NAS Support
Subscriber
3,711
1,485
NAS
DS1520+, DS218+, DS215j
Router
  1. RT2600ac
  2. MR2200ac
Operating system
  1. macOS
Mobile operating system
  1. iOS
Last edited:
You can usually find help in DSM command lines using <comamnd> --help. There's an exclude parameter for du.

Both these do it, long and short form parameters.
Bash:
sudo du --human-readable --max-depth=2 --one-file-system /
sudo du -h -d 2 -x /

Use this to display in MB and then filter out (| grep -v) rows that start the line (^) with a single character (.) then M (that's small stuff 1-9MB):
Bash:
sudo du -BM -d 2 -x / | grep -v ^.M

This is my DS1520+
1653647371075.png
 
208
46
NAS
DS918+, DS414j
Operating system
  1. Linux
  2. Windows
  3. other
Mobile operating system
  1. Android
Last edited:
Updates are now successfully installing! :D
Just need to safely remove that folder.

@fredbert and @Telos thank you so much for your help with this!
Synology Support - 1 week, nothing useful at all and they ended up trying to log in with the wrong user account.
SynoForum - 2 days, solved.
 

fredbert

Moderator
NAS Support
Subscriber
3,711
1,485
NAS
DS1520+, DS218+, DS215j
Router
  1. RT2600ac
  2. MR2200ac
Operating system
  1. macOS
Mobile operating system
  1. iOS
Ok... I may have found it:
532M /volumeUSB1

I have NO USB plugged into the device.

OK I've rm -r the sub folders and I've got 80% free now!
That sort of thing happens when a device that has been mounted on that directory is removed but there are still processes thinking it's there. They will continue to read/write to that directory unaware what the external storage is missing. What these processes will do it use the local directory itself as the place to read/write data.

Later if the directory is re-used as a mount point then the local data inside it will be hidden until the device is unmounted.

I've seen this on Mac and there are remnant directories in /Volumes. It can sometimes cause issues with remounting, or the next time the name is incremented ... so be careful to check when scripting access to external devices as the mount point may not always be what you think it is.

On Mac I've made sure the device is not connected, checked the local content if any and saved it elsewhere, then deleted the rogue directory. Never done it on DSM.

If you have a USB drive (or the USB drive) then you could connect it and see where it mounts. Then decide what to do with this directory.
 
208
46
NAS
DS918+, DS414j
Operating system
  1. Linux
  2. Windows
  3. other
Mobile operating system
  1. Android
Yes, I'm on DSM 7, I'm willing to bet that takes up the extra 30%.
Though I could check that with my 414j...
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

  • Question
Ok, changing the ports didn't help. I refreshed the Synology / LE certificate too but that didn't seem to...
Replies
4
Views
938
Ping is irrelevant here when it comes to testing out traffic and connectivity. Telent works you say? Using...
Replies
5
Views
2,322
Thanks so much man! Just got the windows players app, and it's all fixed! Now Synology CPU is at 3%...
Replies
4
Views
963
With the slowdown I personally saw with 6.2.4 over 6.2.3, on my 215J, V7 is definitely out of the...
Replies
3
Views
766
Hi, I followed this tutorial acmesh-official/acme.sh. The only difference is that the certs are generated...
Replies
0
Views
1,586

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending threads

Top