Posts by corzocone

Nevermind, I seem to have fixed it.As the above-linked post instructs, I was able to change the apm for my 3 drives to 0 (was 255). Code looked like this:

(I've deleted my drive UUIDs)

      <hdparm>
        <uuid>*****************</uuid>
        <devicefile>/dev/disk/by-id/ata-ST8000NE0004-1ZF11G</devicefile>
        <apm>0</apm>
        <aam>0</aam>
        <spindowntime>0</spindowntime>
        <writecache>0</writecache>
      </hdparm>
      <hdparm>
        <uuid>>*****************</</uuid>
        <devicefile>/dev/disk/by-id/ata-ST8000NE0004-1ZF11G</devicefile>
        <apm>0</apm>
        <aam>0</aam>
        <spindowntime>0</spindowntime>
        <writecache>0</writecache>
      </hdparm>
      <hdparm>
        <uuid>>*****************</</uuid>
        <devicefile>/dev/disk/by-id/ata-ST8000NE0004-1ZF11G</devicefile>
        <apm>0</apm>
        <aam>0</aam>
        <spindowntime>0</spindowntime>
        <writecache>0</writecache>

I found this post with similar error, but I do not understand the fix. How do I change apm to 0 in the config.xml file?

Thread

Have a problem with enabling smart

i reformatted a 8 tb hdd for backup drive. rsync worked just like it supposed to, but when i enabled smart i got message about internal error. did i break smart?
(Code, 62 lines)

i was only able to post part of error message.

hamburger

Nov 12th 2025

Hello,

I have gmail set up for notifications. Been working fine for several years. I noticed they haven't been working for the past 5 days. To try and fix, I deleted the existing google app password, and created a new one. It seems to have worked, but I have a persistent notification to apply configuration changes. When I try to apply, I get the following error. Can anyone advise what happened, and a possible fix?

Thanks in advance

Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LC_ALL=C.UTF-8; export LANGUAGE=; omv-salt deploy run --no-color smartmontools 2>&1' with exit code '1': debian:
    Data failed to compile:
----------
    Rendering SLS 'base:omv.deploy.smartmontools.20hdparm' failed: Jinja error: apm: The value 255 is bigger than 254.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/salt/utils/templates.py", line 477, in render_jinja_tmpl
    output = template.render(**decoded_context)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 1301, in render
    self.environment.handle_exception()
  File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 936, in handle_exception
    raise rewrite_traceback_stack(source=source)
  File "<template>", line 26, in top-level template code
  File "/usr/lib/python3/dist-packages/jinja2/sandbox.py", line 401, in call
    return __context.call(__obj, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/salt/loader/lazy.py", line 149, in __call__
    return self.loader.run(run_func, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/salt/loader/lazy.py", line 1234, in run
    return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/salt/loader/lazy.py", line 1249, in _run_as
    ret = _func_or_method(*args, **kwargs)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/var/cache/salt/minion/extmods/modules/omv_conf.py", line 41, in get
    objs = db.get(id_, identifier)
           ^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 85, in get
    query.execute()
  File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 735, in execute
    self._response = self._elements_to_object(elements)
                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3/dist-packages/openmediavault/config/database.py", line 481, in _elements_to_object
    obj.validate()
  File "/usr/lib/python3/dist-packages/openmediavault/config/object.py", line 236, in validate
    self.model.validate(self.get_dict())
  File "/usr/lib/python3/dist-packages/openmediavault/config/datamodel.py", line 202, in validate
    self.schema.validate(data)
  File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 175, in validate
    self._validate_type(value, schema, name)
  File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 230, in _validate_type
    raise last_exception
  File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 201, in _validate_type
    self._validate_object(value, schema, name)
  File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 306, in _validate_object
    self._check_properties(value, schema, name)
  File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 522, in _check_properties
    self._validate_type(value[propk], propv, path)
  File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 230, in _validate_type
    raise last_exception
  File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 204, in _validate_type
    self._validate_integer(value, schema, name)
  File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 254, in _validate_integer
    self._check_maximum(value, schema, name)
  File "/usr/lib/python3/dist-packages/openmediavault/json/schema.py", line 328, in _check_maximum
    raise SchemaValidationException(
openmediavault.json.schema.SchemaValidationException: apm: The value 255 is bigger than 254.

; line 26

Can you please ELI5 how to use this code? Thank you!

Quote from Callifo

I've created this thermal.py which seems to work. Probably need some advice as to what to call each of the names and what sensors to include?

Thermal creates 9x 'thermal_cooling_devicesx' which are full of nan on my system. It also creates 2x 'thermal-thermal-zonex' which both produce data, but on my system 0 is not valid (produces 27.8C permanently), and 1 is my CPU. I needed to use the custom cpu temp modification to fix the dashboard view.

The code below produces the following:

Code

# -*- coding: utf-8 -*-
#
# This file is part of OpenMediaVault.
#
# @license   http://www.gnu.org/licenses/gpl.html GPL Version 3
# @author    Volker Theile <volker.theile@openmediavault.org>
# @copyright Copyright (c) 2009-2025 Volker Theile
#
# OpenMediaVault is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# any later version.
#
# OpenMediaVault is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with OpenMediaVault. If not, see <http://www.gnu.org/licenses/>.
import openmediavault.mkrrdgraph


class Plugin(openmediavault.mkrrdgraph.IPlugin):
    def create_graph(self, config):
        # http://paletton.com/#uid=33r0-0kwi++bu++hX++++rd++kX
        config.update(
            {
                'title_thermal': 'CPU Temperature',
                'color_thermal1': '#0000fd',
                'color_thermal2': '#fd0000'
            }
        )
        args = []
        # yapf: disable
        # pylint: disable=line-too-long
        # autopep8: off
        args.append('{image_dir}/thermal-0-{period}.png'.format(**config))
        args.extend(config['defaults'])
        args.extend(['--start', config['start']])
        args.extend(['--title', '"{title_thermal}{title_by_period}"'.format(**config)])
        args.append('--slope-mode')
        args.extend(['--upper-limit', '100'])
        args.extend(['--lower-limit', '0'])
        args.extend(['--vertical-label', '°C/°F'])
        args.append('DEF:thermal1={data_dir}/thermal-thermal_zone0/temperature.rrd:value:AVERAGE'.format(**config))
        args.append('DEF:thermal2={data_dir}/thermal-thermal_zone1/temperature.rrd:value:AVERAGE'.format(**config))
        args.append('LINE1:thermal1{color_thermal1}:"Thermal 1"'.format(**config))
        args.append('LINE2:thermal2{color_thermal2}:"Thermal 2"'.format(**config))
        args.append('COMMENT:"\c"')
        args.append('COMMENT:"{last_update}"'.format(**config))
        # autopep8: on
        # yapf: enable
        openmediavault.mkrrdgraph.call_rrdtool_graph(args)
        return 0

Display More

Display More

Quote from macom

Remove the respository.

It is referring to buster, you are on bookworm now.

Did you use it for hd-idle?

I'm having the same issue. I have hd-idle installed. Upgraded from OMV 6>7. Can I update the repo somehow?

Quote from chente

You can also take advantage of the situation and use openmediavault-compose instead of portainer. Portainer is overkill if it's only used to launch stack-powered containers. You will also have your batteries saved. Look at the last two sentences of point 4 and point 8 of this guide. [How to] Docker in OMV

Thanks again. You not only helped me get the issue fixed, but helped me to learn more about OMV/Docker/Portainer.

Quote from chente

There is one aspect on Linux that I think is important to know about. In linux, modifying permissions can break the operation of the system, to the point of having to reinstall. It's one thing to play with your file permissions. With that you can do whatever you want. But modifying the permissions of the system files should never be done. You should not touch the files in /var/lib/docker or change their permissions. That's why I insist that you delete them and start from scratch. I don't know what you've done with them.

Yes, this makes sense. And I don't want a half-fixed solution that will have issues in the future.

I was able to go back into the old portainer and save docker compose instructions for all of my containers. I'm now starting from scratch using those, and I have a few containers up and running so far. I'll report back if I have any more issues, but I hope I'm nearing the finish line!

Again, thank you so much. I appreciate you!

Quote from chente

You should repeat the process without skipping that step.

I did so.

Quote from chente

Everyone in that folder, including portainer. If it restores, then fantastic, it is not a problem. There is nothing in Portainer that you need.

Portainer is just another container. Why don't you want to remove it?

Maybe I'm mistaken, but if I am starting over in Portainer, won't I need to rebuild all of my containers from scratch? I spent a lot of time setting up the containers, and would prefer if I could keep those settings. Is there a way to backup and restore?

Quote from chente

Maybe you should describe the steps you took. With details. There may be some error.

1. Uninstall Portainer via omv-extras
2. Uninstall Docker via omv-extras
3. Reboot
4. Install Docker via omv-extras
5. Install Portainer via omv-exras
6. Change permissions on config files

I realize now I originally missed one of your steps: Delete the docker working files.

I have now done this this, and when I re-installed docker + portainer, portainer had essentially done a "factory reset". All portainer config data must have been deleted. Thankfully, I made a backup of the full docker file before I deleted, so I can go back. Can you please be more specific as to which files I could delete? Attached is a screenshot of all the subfolders in the docker install folder. It seems I deleted all the portainer data, which I do not want to do. Is that correct?

Again, thanks so much for your help, and sorry if I'm slow with these things. I'm not an experienced user.

Quote from chente

I think you have a little trouble set up. If your containers are implemented using compose (or portainer) with a stack (yml configuration file) the easiest thing to do would be to start from scratch. Launching the containers is child's play.

So I would do the following.

Uninstall docker and portainer. Delete the docker working files, NOT the container configuration volumes, but the files in the folder where docker is installed. If you didn't change it, it will be /var/lib/docker. If you changed it, it will be another. Make sure it's empty.

Reset permissions of container configuration volumes to standard root user 775 permissions. Generally this should not be a problem, although there are containers that do not support this.

Make sure that in all your stacks you have defined the user that runs docker. Make sure that user has permission to access all volumes defined in the stacks. And that this user belongs to the docker group.

Install docker and portainer (or openmediavault-compose) again and launch the containers.

Display More

I tried this. Still no luck with my containers. That said, Portainer is now starting on boot along with Docker, so there is some improvement. I assume Portainer has root access, as it's installed via omv-extras, not using the PUID/PGID for my personal containers.

I've changed the permissions on all the docker config folders. I've also done this to the main docker install folder, but every time I reboot the system, it restores the main docker folder permissions. See attached images

Quote from chente

Try resetting your folder permissions again with resetperms. This time do it so that they are left with 775. Owner root, group users. Make sure the remove ACL button is checked.

Make sure the user running docker is in the users group.

Thank you, I think this is the solution, but what folder do I need to reset? I tried this on my container config files and still no luck. I rebooted the system and portainer now won't start either, but docker is running. I can get portainer to work by uninstalling and re-installing, But I think I need to do this at every reboot.

Was this caused by giving the handbrake container admin/root priveleges by not setting the PGID/PUID? I have a specific user set up for docker called "dockeruser". with PUID 1001.

Here's another error code from when I try to start a container via CLI:

Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/init": permission denied: unknown
Error: failed to start containers: Sickchill

At this point, I'm afraid to make things worse

Hello, thanks in advance for reading and I have done a search of forums/google to see if I can solve this on my own but haven't had any luck.

OMV Version: 6.3.10-2 (Shaitan)

Kernel: Linux 5.19.17-2-pve

Poratainer version: 2.18.1 (community)

Docker version: 5:23.0.4-1~debian.11~bullseye

It all started when I decided to install a handbrake container to try and automatically transcode new Plex DVR recordings. I installed the container and started playing around with it. *NOTE: I forgot to add the normal PUID/PGID I use for other containers*. I found that handbrake was automatically transcoding all kinds of other video files rather than the ones I wanted. I'm sure this is due to the settings and the watch folder being my entire TV library. I'm dumb. I quickly shut down the handbrake container, and figured I'd do some research and come back to it at some point in the future. That's when issues started cropping up...

The first sign of trouble, was when I restarted my Plex container, it showed no TV shows, only movies/music/etc. I thought this must be related to the handbrake issue, as handbrake had access to the TV folder, but not the movies. I figured this could have been a permissions issue. Perhaps handbrake changed the permissions to the TV folder and now the Plex container couldn't access it? I used sudo chmod 777 on the tv folder which seemed to fix the issue. Plex could once again see my shows and started rebuilding my library.

I also used the Reset Perms plugin for OMV to try and fix things on a larger scale. I fear this may have made things worse. I can't say for sure, but this may have also changed permissions on my docker config folders.

Where I am now is that docker and portainer are the only things running. Any time I try to restart/redeploy and of my other containers in Portainer, I get an error 400. From what I've read, error 400 can be caused by a multitude of issues.

I've tried uninstalling and re-installing both docker and portainer. They are still the only things that will run. Any additional containers I've added are giving error 400 (I think I also saw an error 500 at some point).

Aside from a permissions issue, the only other thing I can think is some kind of networking issue? But I haven't fiddled with anything there.

Attached below is a brief log of transmission that might shed some light. I've noticed a similar line in logs from other containers "s6-svscan: warning: unable to spawn .s6-svscan/SIGTERM: Permission denied"

Quote

[migrations] started

[migrations] no migrations found

───────────────────────────────────────

██╗ ███████╗██╗ ██████╗

██║ ██╔════╝██║██╔═══██╗

██║ ███████╗██║██║ ██║

██║ ╚════██║██║██║ ██║

███████╗███████║██║╚██████╔╝

╚══════╝╚══════╝╚═╝ ╚═════╝

Brought to you by linuxserver.io

───────────────────────────────────────

To support LSIO projects visit:

https://www.linuxserver.io/donate/

───────────────────────────────────────

GID/UID

───────────────────────────────────────

User UID: 1001

User GID: 100

───────────────────────────────────────

[custom-init] No custom files found, skipping...

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/73577192ab917176310605abf87dec965a6fcde2.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/47e2889c5db1637e778b31ea9cc482ad09346211.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/c9c2435e0aea05dfddb34ad1e4ac772885865ecc.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/b8a8ade770d422819e926bb53c4662c8b56f0431.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/977d8d2713373630c2ac02ebccfdaf6521414d8a.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/ee36a7be6f068c557b11006cae8b2a6bd10e8453.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/d5e6f1cd4efe14ab4957aecd71a157d1f3c6a2aa.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/fca2d4608cf8dd339aa2138facfe2300d332857c.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/9882b2711098a14fa4a8486f27f313b634338dda.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/3b0d133b6d30db78e82257d4b621452f0679b00b.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/72f5caadf6aae9dd5fc6494e822e947552c816ea.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/e45e74e9b33d91cf8127a23271a100aa1f832df1.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/7c7fb84b2d4953547f48ed7c55d81bf0d2312625.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/daf6a7d50615a4d9f445d72f3ee4ef4f06cd338a.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/dfda7cd04f774f2650609acfdefb6f1c3d2672a3.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/81b9dec07acd0efc5405b56969d391c5b49ea364.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/06fc6f9ed5b253aa9869b88a8debd9413937893c.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/8d4db57a2b2d03721fec839a8dc19145abf7955b.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/2694b819a0e4e9be647b60424c3bea6d6a1a43d9.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/133730f0e9c712231dd08dde0e2d2ec001a0b28b.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/76f1cb9fd6a7f5128b8b73c459fbc1fcdab910e6.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/3082394bf779f1a3ea9f1362c09c0da2b9e544cf.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/6a277554a7459932816393f36e8f04ce6a671d64.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/884ddb34ee1edbde5524cd9ab7f4b70b1a2a600f.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/bca75f6df79b8b877a036de4862b890149f61a94.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/eaa217faf4d26c88c203eb0fff9421f525ef7b3d.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/1649b1fd0ebbc56873e8e4501702b0d56dd6933e.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/e6c5a508ccdcff59308db55cae05397d9e1790a8.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/e690508f69efae2f35d5f0fcd9d61c131af88935.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Couldn't read '/config/torrents/9d27dc4255c53b861c32b32fb1b70947459694cf.torrent': Permission denied (13) (utils.cc:96)

[2023-04-25 21:54:57.881] ERR utils.cc:96 Too many messages like this! I won't log this message anymore this session. (utils.cc:96)

[ls.io-init] done.

crond: can't execute '/bin/ash' for user root

crond: can't execute '/bin/ash' for user root

s6-svscan: warning: unable to spawn .s6-svscan/SIGTERM: Permission denied

s6-svscan: warning: unable to exec finish script .s6-svscan/finish: Permission denied

s6-svscan: warning: executing into .s6-svscan/crash

s6-svscan: fatal: unable to exec .s6-svscan/crash: Permission denied

Display More

Quote from milfaddict

After installing OMV Extras, the webUI went blank so I restarted Chrome and now I can not get back into OMV, The password prompt is does not pop up.

This is an absolute nightmare. PLEASE HELP!

I recently had a similar issue. If you know how, ssh in to the machine (I use putty for this). I used the command omv-update and it fixed itself. Hopefully it works for you as well.

Quote from zzz09700

You can also try ACL options from the OMV Web admin panel and then remove those folders through SMB, I think it should work.
One more step back, a USB-HDD enclosure + a Debian/Ubuntu VM should provide you with a GUI-based access to your data drive. You'll need to put the drive in that enclosure and connect it directly to the VM. But that seems to be too much trouble...first you'll have to get an 3.5IN enclosure and then setup a VM.

Edit:
I don't trust those XFS drivers for windows (unless they came from M$), as a bug could (easily) permanently damage data on your drive.

So I was able to delete some folders via SSH, but something is causing them to automatically copy again. I plan to do a fresh install of OMV, but would like to delay a little while if possible. Any idea how to find out what is causing folders to copy? It looks like another install has made it's way onto my storage drive somehow. I'm also seeing a user named 1001 in OMV with high level access (possibly root?). I don't want to change too much, as plex is running, which is my main concern. I just want to buy some time before going thru the re-install.

Quote from zzz09700

Removing folders should be easy with SSH, but I figure it would be safer to copy the folders you want to another drive (maybe your PC if you have enough space) and just wipe the data drive.

So you suggest I back up data I want, wipe storage drive, and do a clean install of OMV? Is there any easy way to delete folders besides SSH? Could I plug the storage drive into my windows PC to somehow manage the data? It's formatted xfs which windows doesn't recognize by default.

edit: If I want to back up to another drive, I'll probably need to go out and buy one. Transferring over my network is painfully slow.

Hello. Build info at end of post. Please be gentle, I'm not well-versed with linux, and I think I've buggered my install quite badly. Any help is MUCH appreciated. I hope this is not posted in the wrong category.

My problems began when I was trying to install webtools for Plex. I’m no expert with ssh commands, so instead of copying the webtools.bundle folder via SSH to Plex’s Plug-ins directory, I thought I’d try creating a shared folder over CIFS/SMB to access the necessary Plex directory. Long story short, that seemed to break Plex, and I had a heck of a time getting it working again. Plex is running now, but something is still messed up. I used some purge and install commands in ssh that probably caused this problem. I think I may have used some ubuntu commands found online by mistake. On the OMV GUI dashboard, Plex shows as running, but not "enabled" http://imgur.com/hEYDHDp. I didn't really mind very much, because it was at least working. When I tried to "enable" plex in OMV, it would not run, the little green dot would turn red and the log would show this. http://imgur.com/XfYyUoP

Fast-forward to a couple days later. I go to download a season of a TV show I like, but deluge shows that my storage drive is full. That's odd, it was barely over 50%. Then I look at my SMB share via my windows desktop and I see a whole bunch of new folders (which I don't have access to thru windows). This looks like another OMV install happened on my storage drive? http://imgur.com/Y1i4SWg Or at least my copies of my install and all my media were made somehow. Also looks like I need root access to change these folders. I checked my filesystems on OMV, and sure enough, my storage drive is 100% full. http://imgur.com/t0xa3wp

I have a feeling this may be too badly damaged to recover, so I'm considering a full reinstall of OMV, which would be a pain, but at least it would be clean. If I go that route, please advise how I can clear the OMV install off my storage drive, keeping all my media intact.

Alternatively, let me know if this is something that can be fixed without too much trouble.

If I've left out any relevant info, please ask.

Thanks!

Build:

Shuttle SH67 XPC Desktop
Intel Core i3-2100 3.1GHz
2GB DDR3 RAM
160GB SATA OS Drive
Seagate 4TB 64MB SATA 3.5IN NAS Storage Drive