Would ask Tom AI but can't access the web interface, although I can access the SparkBox via SSH. Primary Issue: Attempting to login via via IP:8443 results in Could not load services. I checked Demox, attempted to implement what worked for that user to no avail. My password is correct because I can login via SSH. Supporting Issues: - Had to extend the VM (Ubuntu on Proxmox)—incidental, perhaps directly related. Apparently I have no space left at SBROOT, but i'm unsure how that became an issue. - Resources are being chewed up, particularly memory (14 out of 16 GB) - Numerous crash-restart loop errors reported by the Doctor. I had to sparkbox down and sparkbox up to reduce from 5 to 2. - I'm still a relative Linux/self-hosting noob.
8 replies
Chris wrote:
I have got you — and the clue is right in your own post. The dashboard shows "Could not load services" because its drive is full, which is also why the doctor keeps reporting crash-restarts. Nothing is broken beyond that, and SSH still working is a good sign. One step to confirm it: in your SSH terminal run df -h and paste back what it prints. It lists every drive and how full each one is. The part about extending the VM matters too, because Ubuntu often keeps the old size until it is told to grow. Paste the result and I will give you the exact next command.
cprs wrote:
mediabox@mediabox:~$ df -h Filesystem Size Used Avail Use% Mounted on tmpfs 3.1G 2.7M 3.1G 1% /run /dev/mapper/ubuntu--vg-ubuntu--lv 31G 30G 0 100% / tmpfs 7.6G 0 7.6G 0% /dev/shm none 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service none 1.0M 0 1.0M 0% /run/credentials/systemd-resolved.service tmpfs 7.6G 0 7.6G 0% /tmp /dev/sda2 2.0G 184M 1.7G 11% /boot none 1.0M 0 1.0M 0% /run/credentials/systemd-networkd.service 192.168.1.35:/mnt/Main/Media 28T 0 28T 0% /mnt/media 192.168.1.35:/mnt/Main/data 28T 250G 28T 1% /mnt/truenas none 1.0M 0 1.0M 0% /run/credentials/getty@tty1.service tmpfs 1.6G 8.0K 1.6G 1% /run/user/1000 Looking at this, I had performed the following action sudo lvextend -l +100%FREE /dev/mapper/ubuntu--vg-ubuntu--lv which reported an increase to 60GB. I had previously increased the disk size in Proxmox +64 GB to 128GB.
Chris wrote:
Your df -h found it — the main system drive is completely full (30G of 31G, 100%), and that full drive is exactly why the dashboard says "Could not load services" and keeps crash-restarting. Nothing else is broken, and SSH keeps working because it doesn't need that disk. You extended the VM, but Ubuntu hasn't grown into the new space yet — it still thinks it has only 31G. One command tells it to grow: sudo lvextend -l +100%FREE /dev/mapper/ubuntu--vg-ubuntu--lv && sudo resize2fs /dev/mapper/ubuntu--vg-ubuntu--lv It only adds space and deletes nothing. Run df -h again after — the / line should be bigger and no longer 100%. If it prints "insufficient free space" instead, paste that back and I'll give the one extra step.
cprs wrote:
mediabox@mediabox:/dev/mapper$ sudo lvextend -l +100%FREE /dev/mapper/ubuntu--vg-ubuntu--lv && sudo resize2fs /dev/mapper/ubuntu--vg-ubuntu--lv New size (15871 extents) matches existing size (15871 extents). No size change. mediabox@mediabox:/dev/mapper$ df -h Filesystem Size Used Avail Use% Mounted on tmpfs 3.1G 2.8M 3.1G 1% /run /dev/mapper/ubuntu--vg-ubuntu--lv 31G 30G 0 100% / tmpfs 7.6G 0 7.6G 0% /dev/shm none 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service none 1.0M 0 1.0M 0% /run/credentials/systemd-resolved.service tmpfs 7.6G 0 7.6G 0% /tmp /dev/sda2 2.0G 184M 1.7G 11% /boot none 1.0M 0 1.0M 0% /run/credentials/systemd-networkd.service 192.168.1.35:/mnt/Main/Media 28T 0 28T 0% /mnt/media 192.168.1.35:/mnt/Main/data 28T 250G 28T 1% /mnt/truenas none 1.0M 0 1.0M 0% /run/credentials/getty@tty1.service tmpfs 1.6G 8.0K 1.6G 1% /run/user/1000
Chris wrote:
No size change is the tell — the space you added in Proxmox has not reached this partition yet, so there is nothing for lvextend to grab. The disk is built in layers and the bottom layer is still the old size. One command shows them all: run sudo lsblk and paste back what it prints. I am checking that sda shows the new bigger total while the system piece is still 31G — then I will give you the one command that grows it.
cprs wrote:
mediabox@mediabox:/dev/mapper$ sudo lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 128G 0 disk ├─sda1 8:1 0 1M 0 part ├─sda2 8:2 0 2G 0 part /boot └─sda3 8:3 0 62G 0 part └─ubuntu--vg-ubuntu--lv 252:0 0 62G 0 lvm / sr0 11:0 1 2.7G 1 rom
Chris wrote:
That output is the answer — the space is already there. Your main drive has grown to 62G, but the part that holds your files is still the old 31G, which is why it shows 100% full. One command tells it to use all 62G: sudo resize2fs /dev/mapper/ubuntu--vg-ubuntu--lv It only adds space and deletes nothing. Then run df -h again — the / line should now be about 62G and no longer full. Paste it back if it prints an error instead.
cprs wrote:
That fixed the volume size issue, thank you. I restarted the Sparkbox, had the Doctor do a health check and they returned All Checks Passed! I can now access the web interface and Everything's Running Smoothly. Thanks again.