Any idea how to clear this please?

[blue max]

I read all their suggestions and none seem to apply.

[manu_manu4]

Le 03/10/2024 à 10:26, blue max a dit :

I read all their suggestions and none seem to apply.

Try to remake your boot USB key

[blue max]

On 10/6/2024 at 6:39 AM, manu_manu4 said:

Try to remake your boot USB key

In case it wasn't obvious, that would be a last resort. Of course I could start again, but I was hoping someone might have a tip to easily update manually.

[Trabalhador Anonimo]

All updates done kept files on the usb stick, even if you do not need it. If you know how to clean, good. If you don't, like me, you will need to resize all partitions on your stick, and most like, resize partitions on the disks.

Edited October 16, 2024 by Trabalhador Anonimo

[shibby]

i used this solution

https://vanderwijk.info/posts/resolving_synology_dsm_insufficient_system_capacity_for_update/

 

[blue max]

On 11/6/2024 at 6:08 AM, shibby said:

i used this solution

https://vanderwijk.info/posts/resolving_synology_dsm_insufficient_system_capacity_for_update/

 

Much appreciated. However, I can login via ssh, but am not sure how to access the thumb drive via unix commands. I do think I need to get to the downloaded update file and remove it, but am scratching my head. Hope someone can assist please.

[shibby]

@blue max from previous link

 

Quote

Then I realized I completely ignored .dotfiles

root@/: # du -hs .??*

677M .SynoUpgrade.tar

 

and I noticed a rather old .SynoUpgrade.tar. So probably an old update that somehow didn’t get removed

 

Old update file is directly in root directory. To delete it run command:

rm /.SynoUpgrade.tar

 

thats all. You can compare free space on /dev/md0 before and after remove this file using command

df -h

Edited November 15, 2024 by shibby

[blue max]

5 hours ago, shibby said:

@blue max from previous link

 

 

Old update file is directly in root directory. To delete it run command:

rm /.SynoUpgrade.tar

 

thats all. You can compare free space on /dev/md0 before and after remove this file using command

df -h

I appreciate your help, but I can ssh into the nas via a mac. I use ssh username@ipadress. Then tried that command, but no such file or directory. I feel I'm close, but missing something...

[shibby]

10 minutes ago, blue max said:

but no such file or directory.

 

So there is no old update file on your NAS. You need to find out what else is taking up space on the root partition. Run command from link i sent before.

df -h will return free and used space for every partitions - for you the most important is /dev/md0

du -chs will count a space taken by every directory

 

Maybe you have something not important in /root/ directory on you can remove some logfiles in /var/log/... you have to search.

[blue max]

Much appreciate all your help @shibby  Unfortunately, my skills are not too clever, but is there anything there that may be a smoking gun? I have nothing to compare too and don't want to bork the whole thing!

 

Thank you.

 

 

[shibby]

So, you have 473MB free space on root partition (dev/md0).

 

No try run commands:

du -chs /

and

du -chs /var/log/

 

[blue max]

Really appreciate you trying to help my friend, but this is the response to the first command...

 

 

[shibby]

switch root account first with command

sudo su -

 

and run once again.

[blue max]

I must be doing something wrong, but I get no reaction to running either of the latter commands. I do appreciate your patience!

[shibby]

one command and wait untill it finish

[blue max]

I was impatient 😄 there's more. But not sure if it helps...

[shibby]

ah,missing character

 

Run

du -chs /*

and

du -chs /var/log/*

 

should be better

 

Edited December 11, 2024 by shibby

[blue max]

Thanks again fella. I have a list which totals 46m. The largest are "/var/log/systemd (4.2m), synolog ( (1.5m), synobootup.log (4.5m), packages (1.7m), messages (5.0m), kern.log (1.7m), disk-latency (7.8m). Are they big enough to cause the issue do you think?

[shibby]

one more command

du -hs .??*

 

[blue max]

Cheers. The output is rather disappointing...

 

4.0K .profile

4.0K .profile.size_check

4.0K .wget-hsts

[shibby]

this is sad. I dont see any trash to remove to free more space 😕 

 

I didnt tested it on DS918+ because a i`m on SA6400 but if you install a fresh DSM 7.2 then root partition will be 8GB instead of 2,4GB... It may be the only one solution on your problem 😕 But it must be a fresh instalation of DSM - not a migration. If your first DSM was 6.x and then you updated to 7.x then root partition will be not expand and stay on 2.4GB.

 

Backup your data, install fresh DSM7.2 and restore data...

 

 

you can read also this thread

 

Edited December 13, 2024 by shibby

[blue max]

Thanks @Shibby. Really appreciate your help throughout. I haven't found installing Xpenology an easy task. Often have to try several times with different installers. So, I'm not sure I'll risk it. Guess should buy a Synology box, but my HP Microserver is a beast.

[Trabalhador Anonimo]

do you have hardware to create a new box and backup your old one? If so, do it and reinstall everything.

[blue max]

1 minute ago, Trabalhador Anonimo said:

do you have hardware to create a new box and backup your old one? If so, do it and reinstall everything.

Thanks for the reply. I do, but it's not something to undertake lightly. Funnily enough I have an almost identical backup server, that updated with no problem. The price you pay for going 'off piste' I guess!

[blue max]

Finally, my OCD has forced me to attempt to reinstall Xpenology, but have a problem...

 

Using ARPL, I set it up and rebooted. Then I only have the option of restoring the installation. No option to download and select manually.

 

Which if runs through the full ten minutes and flags a problem.

 

Have I missed something please?

[blindspot]

Hi. Did you format the drives before installation?