Hi.
It looks like smartctl couldn't get information about your /dev/sdc drive.
Could you run
sudo smartctl -x /dev/sdc
Does it returns something?
Hi.
It looks like smartctl couldn't get information about your /dev/sdc drive.
Could you run
sudo smartctl -x /dev/sdc
Does it returns something?
kolyanick I also think gderf's advice is worth paying attention. I'd have done the same.
But there's something else I got to tell you.
I recognized Russian on your the very first screenshot and thought you probably want to check out the following article: https://habr.com/ru/post/346594/ (rus).
It's about NAS configuration with no swap and RAM-based tempfs. However, it requires advanced "linuxing" skills. And if you are confident, you could take a chance and try
Ok. After a bit deep googling I found out the message "shopt: not found" could appear in case of using /bin/sh instead of /bin/bash
I changed the first line of the /etc/cron.weekly/openmediavault-update-smart-drivedb script to #!/bin/bash and the script worked properly, without any error.
But I really not sure it was a correct solution. Any ideas are welcome
Hello.
I noticed my OMV have a quite old issue: weekly cron task ends with an error:
Quote/etc/cron.weekly/openmediavault-update-smart-drivedb: 11: /etc/cron.weekly/openmediavault-update-smart-drivedb: shopt: not found
Seems some script tries to set or unset some shell option by shopt - shell built-in command. But it's not clear which one option...
Does anyone have any guess what might have caused it?
Debain 10 (SMP Debian 5.2.9-2~bpo10+1)
OpenMediaVault 5.4.2
Here's the script output with sh -x option:
root@omv:~# /etc/cron.weekly/openmediavault-update-smart-drivedb
/etc/cron.weekly/openmediavault-update-smart-drivedb: 11: /etc/cron.weekly/openmediavault-update-smart-drivedb: shopt: not found
+ . /etc/default/openmediavault
+ OMV_CONFIG_FILE=/etc/openmediavault/config.xml
+ OMV_CONFIG_TEMPLATE_FILE=/usr/share/openmediavault/templates/config.xml
+ OMV_PRODUCTINFO_FILE=/usr/share/openmediavault/productinfo.xml
+ OMV_SCRIPTS_DIR=/usr/share/openmediavault/scripts
+ OMV_DATAMODELS_DIR=/usr/share/openmediavault/datamodels
+ OMV_I18N_LOCALE_DIR=/usr/share/openmediavault/locale
+ OMV_MOUNT_DIR=/srv
+ OMV_SHAREDFOLDERS_DIR=/sharedfolders
+ OMV_SHAREDFOLDERS_DIR_ENABLED=NO
+ OMV_NFSD_EXPORT_DIR=/export
+ OMV_CACHE_DIR=/var/cache/openmediavault
+ OMV_LOG_DIR=/var/log/openmediavault
+ OMV_SSL_CERTIFICATE_DIR=/etc/ssl
+ OMV_SSL_CERTIFICATE_PREFIX=openmediavault-
+ OMV_SSH_KEYS_DIR=/etc/ssh
+ OMV_SSH_KEY_PREFIX=openmediavault-
+ OMV_DPKGARCHIVE_DIR=/var/cache/openmediavault/archives
+ OMV_DOCUMENTROOT_DIR=/var/www/openmediavault
+ OMV_CRONSCRIPTS_DIR=/var/lib/openmediavault/cron.d
+ OMV_CONFIGIMPORT_SCRIPTS_DIR=/usr/share/openmediavault/configimport
+ OMV_SALT_SCRIPTS_DEPLOY_DIR=/srv/salt/omv/deploy
+ OMV_ENGINED_DIR=/usr/share/openmediavault/engined
+ OMV_ENGINED_SO_ADDRESS=/var/lib/openmediavault/engined.sock
+ OMV_ENGINED_SO_OWNERGROUP_NAME=openmediavault-engined
+ OMV_ENGINED_SO_SNDTIMEO=10
+ OMV_ENGINED_SO_RCVTIMEO=180
+ OMV_ENGINED_DIRTY_MODULES_FILE=/var/lib/openmediavault/dirtymodules.json
+ OMV_INITDB_SCRIPTS_DIR=/usr/share/openmediavault/initsystem
+ OMV_INITDB_FILE=/var/lib/openmediavault/initsystem.req
+ OMV_USERMGMT_DEFAULT_GROUP=users
+ OMV_RRDGRAPH_DIR=/var/lib/openmediavault/rrd
+ OMV_RRDGRAPH_ERROR_IMAGE=/usr/share/openmediavault/icons/rrd_graph_error_64.png
+ OMV_WEBGUI_FILE_OWNERGROUP_NAME=openmediavault-webgui
+ OMV_CONFIGOBJECT_NEW_UUID=fa4b1c66-ef79-11e5-87a0-0002b3a176b4
+ OMV_DEBUG_SCRIPT=NO
+ OMV_DEBUG_PHP=NO
+ OMV_DEBUG_EXTJS=NO
+ OMV_MINIDLNA_SERIAL=10001000
+ . /usr/share/openmediavault/scripts/helper-functions
+ . /etc/default/openmediavault
+ OMV_CONFIG_FILE=/etc/openmediavault/config.xml
+ OMV_CONFIG_TEMPLATE_FILE=/usr/share/openmediavault/templates/config.xml
+ OMV_PRODUCTINFO_FILE=/usr/share/openmediavault/productinfo.xml
+ OMV_SCRIPTS_DIR=/usr/share/openmediavault/scripts
+ OMV_DATAMODELS_DIR=/usr/share/openmediavault/datamodels
+ OMV_I18N_LOCALE_DIR=/usr/share/openmediavault/locale
+ OMV_MOUNT_DIR=/srv
+ OMV_SHAREDFOLDERS_DIR=/sharedfolders
+ OMV_SHAREDFOLDERS_DIR_ENABLED=NO
+ OMV_NFSD_EXPORT_DIR=/export
+ OMV_CACHE_DIR=/var/cache/openmediavault
+ OMV_LOG_DIR=/var/log/openmediavault
+ OMV_SSL_CERTIFICATE_DIR=/etc/ssl
+ OMV_SSL_CERTIFICATE_PREFIX=openmediavault-
+ OMV_SSH_KEYS_DIR=/etc/ssh
+ OMV_SSH_KEY_PREFIX=openmediavault-
+ OMV_DPKGARCHIVE_DIR=/var/cache/openmediavault/archives
+ OMV_DOCUMENTROOT_DIR=/var/www/openmediavault
+ OMV_CRONSCRIPTS_DIR=/var/lib/openmediavault/cron.d
+ OMV_CONFIGIMPORT_SCRIPTS_DIR=/usr/share/openmediavault/configimport
+ OMV_SALT_SCRIPTS_DEPLOY_DIR=/srv/salt/omv/deploy
+ OMV_ENGINED_DIR=/usr/share/openmediavault/engined
+ OMV_ENGINED_SO_ADDRESS=/var/lib/openmediavault/engined.sock
+ OMV_ENGINED_SO_OWNERGROUP_NAME=openmediavault-engined
+ OMV_ENGINED_SO_SNDTIMEO=10
+ OMV_ENGINED_SO_RCVTIMEO=180
+ OMV_ENGINED_DIRTY_MODULES_FILE=/var/lib/openmediavault/dirtymodules.json
+ OMV_INITDB_SCRIPTS_DIR=/usr/share/openmediavault/initsystem
+ OMV_INITDB_FILE=/var/lib/openmediavault/initsystem.req
+ OMV_USERMGMT_DEFAULT_GROUP=users
+ OMV_RRDGRAPH_DIR=/var/lib/openmediavault/rrd
+ OMV_RRDGRAPH_ERROR_IMAGE=/usr/share/openmediavault/icons/rrd_graph_error_64.png
+ OMV_WEBGUI_FILE_OWNERGROUP_NAME=openmediavault-webgui
+ OMV_CONFIGOBJECT_NEW_UUID=fa4b1c66-ef79-11e5-87a0-0002b3a176b4
+ OMV_DEBUG_SCRIPT=NO
+ OMV_DEBUG_PHP=NO
+ OMV_DEBUG_EXTJS=NO
+ OMV_MINIDLNA_SERIAL=10001000
+ OMV_XMLSTARLET_GET_SHAREDFOLDER_PATH=-m //system/shares/sharedfolder[uuid=current()/sharedfolderref] -v concat(//system/fstab/mntent[uuid=current()/mntentref]/dir,'/',reldirpath) -b
+ OMV_XMLSTARLET_GET_SHAREDFOLDER_NAME=-m //system/shares/sharedfolder[uuid=current()/sharedfolderref] -v name -b
+ OMV_XMLSTARLET_GET_SHAREDFOLDER_MOUNT_DIR=-m //system/shares/sharedfolder[uuid=current()/sharedfolderref] -v concat(//system/fstab/mntent[uuid=current()/mntentref]/dir,'/',reldirpath) -b
+ OMV_CRON_WEEKLY_UPDATE_SMART_DRIVEDB_ENABLED=yes
+ omv_checkyesno yes
+ return 0
+ omv_syslog_info Updating smartmontools drive database ...
+ omv_syslog -p syslog.info Updating smartmontools drive database ...
+ local _tag _priority
+ basename /etc/cron.weekly/openmediavault-update-smart-drivedb
+ _tag=openmediavault-update-smart-drivedb
+ _priority=syslog.info
+ getopts t:p: option
+ _priority=syslog.info
+ getopts t:p: option
+ shift 2
+ logger --priority syslog.info --tag openmediavault-update-smart-drivedb Updating smartmontools drive database ...
+ cd /var/lib/smartmontools/drivedb
+ wget --quiet --backups=1 https://raw.githubusercontent.…montools/master/drivedb.h
+ chown -c root:root drivedb.h
And shopt output
root@omv:~# shopt
autocd on
assoc_expand_once off
cdable_vars off
cdspell off
checkhash off
checkjobs off
checkwinsize on
cmdhist on
compat31 off
compat32 off
compat40 off
compat41 off
compat42 off
compat43 off
compat44 off
complete_fullquote on
direxpand off
dirspell off
dotglob off
execfail off
expand_aliases on
extdebug off
extglob on
extquote on
failglob off
force_fignore on
globasciiranges on
globstar off
gnu_errfmt off
histappend off
histreedit off
histverify off
hostcomplete off
huponexit off
inherit_errexit off
interactive_comments on
lastpipe off
lithist off
localvar_inherit off
localvar_unset off
login_shell on
mailwarn off
no_empty_cmd_completion off
nocaseglob off
nocasematch off
nullglob off
progcomp on
progcomp_alias off
promptvars on
restricted_shell off
shift_verbose off
sourcepath on
xpg_echo off
I you can see, the error is:
Could not connect to ftp.sg.debian.org:80 (130.89.148.12), connection timed out
I checked the site and it accessible from my workstation with no problem. Please make sure your OMV has access to the internet and you can connect to the site from it (for example login to OMV with ssh and try to connect to the site).
Glad to hear that. Enjoy! )
As I can see it tries to unmount shared mount point, but with no luck.
Probably /sharedfolders/appData are in use by some user, device, process, daemon, etc.
Try to run this as root in CLI to check who is using this folder.
It will gives you a list of processes using the folder. Try to reset connection or stop daemon (or disable whatever else which blocks the folder).
Then try to change privileges again.
Well, actually I've install OMV on the same MB recently. And I can say I didn't change default settings. So if you are worring whether you run into a problems during OMV/Debian installation, you can be pretty sure it won't happen.
I had a problems, but my configuration a bit exotic and moreover I used Debian 10+OMV5, so it was rather because I love challenging projects, not because hardware caused an issues.
Um.. but what are you really concerned about?
Because, you know, CSM is just a part of UEFI to provide legacy BIOS compatibility for legasy OS (wiki)
And as OMV is not legasy OS, so using this option is not very useful either, is it?
@Erikk This is what I got:
Well, seems it still wants to know the path to omv-stuff... Ok, try to add '/usr/sbin' into your PATH environment variable
Then run 'omv-confdbadm populate' and see if it finished properly.
If it's not, see ryecoaaron's comment above.
Seems your /usr/sbin folder not in the PATH environment variable.
Just run '/usr/sbin/omv-confdbadm populate' instead
No
Hmm.. did I understand it correctly, there is no backup settings tool/pluging for OMV?
How come?
I havn't reasearch this question yet, but I think it's kind of 'must have feature'. I mean, this is really useful when you need to save/restore your OMV configuration.
If you check your log carefylly, you will find following:
QuoteDisplay MoreComment: An exception occurred in this state:
Traceback (most recent call last): File "/usr/lib/python3/dist-packages/salt/state.py", line 1919, in call **cdata['kwargs'])
File "/usr/lib/python3/dist-packages/salt/loader.py", line 1918, in wrapper return f(*args, **kwargs)
File "/usr/lib/python3/dist-packages/salt/utils/decorators/__init__.py", line 558, in _decorate return self._call_function(kwargs)
File "/usr/lib/python3/dist-packages/salt/utils/decorators/__init__.py", line 263, in _call_function raise error
File "/usr/lib/python3/dist-packages/salt/utils/decorators/__init__.py", line 250, in _call_function return self._function(*args, **kwargs)
File "/usr/lib/python3/dist-packages/salt/states/module.py", line 294, in run func_args=kwargs.get(func))
File "/usr/lib/python3/dist-packages/salt/states/module.py", line 358, in _call_function mret = __salt__[name](*arg_type, **func_kw)
File "/usr/lib/python3/dist-packages/salt/modules/systemd.py", line 906, in restart raise
CommandExecutionError(_strip_scope(ret['stderr'])) salt.exceptions.CommandExecutionError: Job for sharedfolders-docker.mount failed. See "systemctl status sharedfolders-docker.mount" and "journalctl -xe" for details.
Try to run "systemctl status sharedfolders-docker.mount" and check why it failed.
For additional information you can also check "journalctl -xe", but make sure you read the log at exactly the time the error occurred.
ryecoaaron, ok, I see, thank you.
I just remount my store disk drive with OMV web interface and it appeared in dropdown menu.
As for system drive, well I had no intentions to share it, so it's ok that system drive is not available.
That command wouldn't help this problem. Did you mount your filesystems using the omv web interface? See problem #2 here -https://forum.openmediavault.o…tions-to-common-problems/
Thank you for the link! This confirmed my guesses.
As for question whether I mount via OMV - no, I didn't.
However please note that I installed Debian 10 and mount all partitions first, and then rolled up OMV. Do I understand correctly that this is a valid way? And if so, is there a way for me to populate dropdown?
Uh, "omv-confdbadm populate" compelted sucessfully, but changed nothing.
I still have empty list of disks
Well,
ext4 on my system /dev/sda and btrfs on my storage /dev/sdb
and btw I can see all partitions in Storage->File systems.
Do you think it's important which filesytems contain the disks? I thought it's rather about hardware detaction, than logical volume.
But I noticed one guy published OMV5 (usul) has been installed in debian 10 (Buster) for test
and it seems quite usefull, at least I found that I forgot to run "omv-confdbadm populate". First run was unsucessfull and failed with errors, so I'll continue trying to fix it and will inform if it helped.
Hi there.
Not sure if I should open new one thread... Anyway, I have the same problem as it described by thread starter - just can't see any disks in dropdown list while creating shared folder.
But it's seems different.
I have fresh Debian 10 (with no GUI) installed with OMV 5.0.5 and it's real hardware, not virtual machine (yes, I know this is a great chance to have a headache using OMV5 right now, and please bealive me I do have all headache I could find or create myself about that, but it's another story )
So I do see my both disks in Storage->Disks as /dev/sda and /dev/sdb
But I suffer from the lack of them in dropdown list.
Maybe someone has an idea where I should start?