I have OMV installed on a 32GB USB flash drive however never paid attention until recently where I've noticed it's reporting the drive is only ~6GB. Additionally the drive is now full and I'm at loss as to where to go or even start.
Incorrect System Disk Size
-
- OMV 4.x
- Goofy
-
-
Hi!
This is a common problem. Normally 6-7 GB is plenty. But if you do something wrong then even several TB may not be enough.
There are several threads on the forum about this. Here is one:
-
Hi!
This is a common problem. Normally 6-7 GB is plenty. But if you do something wrong then even several TB may not be enough.
There are several threads on the forum about this. Here is one:
Following that thread (thank you btw), I booted up PopOS and this is what I find for that drive. Please understand this is relatively foreign to me so I'm not sure how to interpret what I'm looking at.
sdd 8:48 1 29.8G 0 disk
├─sdd1 8:49 1 5.9G 0 part /media/pop-os/31651ac4-e061-4bf2-a02a-bd99
├─sdd2 8:50 1 1K 0 part
└─sdd5 8:53 1 23.9G 0 partDisk properties show a swap and extended partition.
Edit, Here is my fstab contents (not sure if relevant):
Code# <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sdc1 during installation UUID=31651ac4-e061-4bf2-a02a-bd994d6e9764 / ext4 noatime,nodiratime,errors=remount-ro 0 1 # swap was on /dev/sdc5 during installation #UUID=04d1630c-2810-44e1-abe9-b0d4627e2bb6 none swap sw 0 0 tmpfs /tmp tmpfs defaults 0 0 # >>> [openmediavault] /dev/disk/by-label/Media /srv/dev-disk-by-label-Media ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 /dev/disk/by-label/Personal /srv/dev-disk-by-label-Personal ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 # <<< [openmediavault]
-
OK. Now you will be doing open brain surgery on the OMV system. Wash your hands very carefully and put on gloves and mask. And a hair net.
You need to very, very carefully look around inside what used to be the root filesystem on the flash drive. I suspect that it is sdd1.
When you open sdd1 you can search for a folder full of junk files and junk folders you recognize from some other context. The utility du (disk usage) could be a helpful diagnostic tool. Find the folder with the biggest disk usage and open it. Then check the disk usage in that folder. Repeat until you find the junk. Perform a surgical excision and delete the junk, taking great care not to delete any of the surrounding healthy files and folders.
Then OMV will hopefully be able to run as normal again.
-
Hate to bump my old thread, however I'm back to the same point I was originally; the drive has filled to capacity...to the point where I cannot connect to OMV:
Error #0:
OMV\Exception: Failed to read file '/var/cache/openmediavault/cache.omv\controlpanel\login_js.json' (size=0). in /usr/share/php/openmediavault/json/file.inc:207
Stack trace:
#0 /usr/share/php/openmediavault/json/file.inc(223): OMV\Json\File->getContents()
#1 /usr/share/php/openmediavault/controlpanel/controlpanelabstract.inc(173): OMV\Json\File->read()
#2 /var/www/openmediavault/index.php(46): OMV\ControlPanel\ControlPanelAbstract->render()
#3 {main}I only have Win10 now so I cannot read the USB drive elsewhere. I fired up a Virtualbox Ubuntu VM however it cant attach the OMV USB.
I think at this point my only solution is to reinstall OMV however I am fearful that this will render the data on my other drives inaccessible.
Help!!
-
the drive has filled to capacity...to the point where I cannot connect to OMV:
You should still be able to connect via ssh or at worst, locally to fix this. There is no way to fix this from the web interface anyway.
I only have Win10 now so I cannot read the USB drive elsewhere. I fired up a Virtualbox Ubuntu VM however it cant attach the OMV USB.
You can boot just about any Linux live cd on the win10 system to attach the drive.
-
You should still be able to connect via ssh or at worst, locally to fix this. There is no way to fix this from the web interface anyway.
You can boot just about any Linux live cd on the win10 system to attach the drive.
I was able to get in via Putty and was able to clean *just* enough space with clean-apt and purging my logs to get back into the webgui. So I'm basically back to my original problem where something keeps eating into my boot drive.
To recap: I'm a noob with OMV/Linux :). I've got a 32GB flash drive being used as boot and a couple of NAS drives attached. File system shows sdc1 as only being ~5.76GB.
df
Code
Alles anzeigenFilesystem Size Used Avail Use% Mounted on udev 12G 0 12G 0% /dev tmpfs 2.4G 9.3M 2.4G 1% /run /dev/sdc1 5.8G 5.4G 68M 99% / tmpfs 12G 0 12G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 12G 0 12G 0% /sys/fs/cgroup tmpfs 12G 168K 12G 1% /tmp /dev/sda1 1.8T 37G 1.8T 3% /srv/dev-disk-by-label-Personal /dev/sdb1 1.8T 337G 1.5T 19% /srv/dev-disk-by-label-Media folder2ram 12G 17M 12G 1% /var/log folder2ram 12G 0 12G 0% /var/tmp folder2ram 12G 1.1M 12G 1% /var/lib/openmediavault/rrd folder2ram 12G 16K 12G 1% /var/spool folder2ram 12G 20M 12G 1% /var/lib/rrdcached folder2ram 12G 12K 12G 1% /var/lib/monit folder2ram 12G 4.0K 12G 1% /var/lib/php folder2ram 12G 0 12G 0% /var/lib/netatalk/CNID folder2ram 12G 552K 12G 1% /var/cache/samba
lsblkCodeNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 1.8T 0 disk └─sda1 8:1 0 1.8T 0 part /srv/dev-disk-by-label-Personal sdb 8:16 0 1.8T 0 disk └─sdb1 8:17 0 1.8T 0 part /srv/dev-disk-by-label-Media sdc 8:32 1 29.8G 0 disk ├─sdc1 8:33 1 5.9G 0 part / ├─sdc2 8:34 1 1K 0 part └─sdc5 8:37 1 23.9G 0 part
-
Unmount your data drives. Then examine their mountpoints - they should be empty. If they aren't this is likely the data that is filling up your system drive.
-
I've got a 32GB flash drive being used as boot and a couple of NAS drives attached. File system shows sdc1 as only being ~5.76GB.
Start with: du -d1 -x -h / | sort -h
-
Unmount your data drives. Then examine their mountpoints - they should be empty. If they aren't this is likely the data that is filling up your system drive.
Is there a best practice for this when Unmounting is greyed out?
- Drives are setup with shares in SMB - disabling the service did not work. Do I have to delete the shares?
- Do I have to also delete all of my Shared Folders?
@ryecoaaron
4.0K /export
4.0K /home
4.0K /lib64
4.0K /mnt
8.0K /media
12K /srv
16K /lost+found
16K /opt
44K /root
7.3M /etc
13M /bin
15M /sbin
130M /var
137M /boot
991M /lib
1.1G /usr
1.3G /sharedfolders
3.6G / -
Forget about using the GUI for this.
I would try force unmounting them in the shell.
fuser -k -9 /mountpoint
then umount /mountpoint
If this doesn't work you could try shutting down, disconnecting the data drives and, booting it.There will probably be errors and warnings about the missing drives.Then look at the mountpoints.
Or you could boot a LiveCD or Live USB Linux distro and look at the mount points. Probably the fastest and easiest way.
-
Appreciate everyone's help!! I was able to narrow it down to Docker using a default path (/var/lib/docker) and I've got the boot drive down to 43% used.
-
I didn't see any mention of you using dockers, unless I missed it. Knowing that would have greatly sped up the solution as that is a very, very common problem.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!