Posts by wouterve

Quote from hpready

Hi Everyone, i finally fix my problem of serial number.

Like wouterve, my serial number was replace by a generic 0123456789ABCDEF for every drives and like he said in his previous post:

i receive the same result:

Then i search 'exit code 1' on the web, not really clear, but the problem seem related with the script not found:

i decided to reinsert the relative path in the 61-openmediavault-dev-disk-by-id.rules (removed with the new version)

and now my serial number show correctly and no more error 'failed with exit code 1'.

Display More

Hello, I havent visited the forum in recent months but I stumbled upon your solution & applied to my installation as well.

So in /etc/udev/rules.d/61-openmediavault-dev-disk-by-id.rules I've searched for the corresponding vendor_id & model_id & altered the code so it looks like this now:

ENV{ID_VENDOR_ID}=="152d", \
ENV{ID_MODEL_ID}=="0567", \
IMPORT{program}="/usr/lib/udev/serial_id %N", \
ENV{ID_SERIAL}="$env{ID_VENDOR}_$env{ID_MODEL}_$env{ID_SERIAL_SHORT}-$env{ID_INSTANCE}", \
SYMLINK="disk/by-path/$env{ID_PATH}", \
SYMLINK+="disk/by-id/$env{ID_BUS}-$env{ID_SERIAL}"

IMPORT{program}="serial_id %N", \ 

became

IMPORT{program}="/usr/lib/udev/serial_id %N", \ 

Et voilà, S/N is showing up again

Thanks for your suggestion!

Unfortunately, a reboot does not help.

Before version 5.5.21 I used these custom udev rules which did help to retrieve the real S/N. With the update it doesn't seem to work anymore.

I have to add this disk is mounted under /srv/dev-disk-by-uuid-478829cb-d16a-4656-8278-40e4c2fa837c/ so not under this generic S/N.

What is the implication for not having the real S/N? I use this disk as a backup disk, no shared folders or such are on it.

kr

wouter

Both commands succeed:

Here is the output from first one:

/usr/lib/udev/serial_id /dev/sdc
ID_SERIAL_SHORT=WD-WMAZA2719329

I've the same problem as the OP. I've deleted the 99-openmediavault-dev-disk-by-id.rules file & executed the omv-salt command. Now I just see a generic serial number:

Output from udevadm test --action=add /sys/class/block/sdc

Load module index
Parsed configuration file /lib/systemd/network/99-default.link
Parsed configuration file /etc/systemd/network/10-openmediavault-enx001e0632c904.link
Created link configuration context.
Reading rules file: /lib/udev/rules.d/01-md-raid-creating.rules
Reading rules file: /etc/udev/rules.d/10-wifi-disable-powermanagement.rules
Reading rules file: /lib/udev/rules.d/50-firmware.rules
Reading rules file: /lib/udev/rules.d/50-udev-default.rules
Reading rules file: /etc/udev/rules.d/50-usb-realtek-net.rules
Reading rules file: /lib/udev/rules.d/55-dm.rules
Reading rules file: /lib/udev/rules.d/56-lvm.rules
Reading rules file: /lib/udev/rules.d/60-block.rules
Reading rules file: /lib/udev/rules.d/60-bridge-network-interface.rules
Reading rules file: /lib/udev/rules.d/60-cdrom_id.rules
Reading rules file: /lib/udev/rules.d/60-crda.rules
Reading rules file: /lib/udev/rules.d/60-drm.rules
Reading rules file: /lib/udev/rules.d/60-evdev.rules
Reading rules file: /lib/udev/rules.d/60-input-id.rules
Reading rules file: /lib/udev/rules.d/60-persistent-alsa.rules
Reading rules file: /lib/udev/rules.d/60-persistent-input.rules
Reading rules file: /lib/udev/rules.d/60-persistent-storage-dm.rules
Reading rules file: /lib/udev/rules.d/60-persistent-storage-tape.rules
Reading rules file: /lib/udev/rules.d/60-persistent-storage.rules
Reading rules file: /lib/udev/rules.d/60-persistent-v4l.rules
Reading rules file: /lib/udev/rules.d/60-sensor.rules
Reading rules file: /lib/udev/rules.d/60-serial.rules
Reading rules file: /lib/udev/rules.d/60-sunxi-tools.rules
Reading rules file: /etc/udev/rules.d/61-openmediavault-dev-disk-by-id.rules
Reading rules file: /lib/udev/rules.d/63-md-raid-arrays.rules
Reading rules file: /lib/udev/rules.d/64-btrfs-dm.rules
Reading rules file: /lib/udev/rules.d/64-btrfs.rules
Reading rules file: /lib/udev/rules.d/64-md-raid-assembly.rules
Reading rules file: /lib/udev/rules.d/69-lvm-metad.rules
Reading rules file: /lib/udev/rules.d/69-md-clustered-confirm-device.rules
Reading rules file: /lib/udev/rules.d/70-joystick.rules
Reading rules file: /lib/udev/rules.d/70-mouse.rules
Reading rules file: /lib/udev/rules.d/70-pcspkr-beep.rules
Reading rules file: /lib/udev/rules.d/70-power-switch.rules
Reading rules file: /lib/udev/rules.d/70-touchpad.rules
Reading rules file: /lib/udev/rules.d/70-uaccess.rules
Reading rules file: /lib/udev/rules.d/71-axp-power-button.rules
Reading rules file: /lib/udev/rules.d/71-seat.rules
Reading rules file: /lib/udev/rules.d/73-seat-late.rules
Reading rules file: /lib/udev/rules.d/73-special-net-names.rules
Reading rules file: /lib/udev/rules.d/73-usb-net-by-mac.rules
Reading rules file: /lib/udev/rules.d/75-net-description.rules
Reading rules file: /lib/udev/rules.d/75-probe_mtd.rules
Reading rules file: /lib/udev/rules.d/78-sound-card.rules
Reading rules file: /lib/udev/rules.d/80-debian-compat.rules
Reading rules file: /lib/udev/rules.d/80-drivers.rules
Reading rules file: /lib/udev/rules.d/80-ifupdown.rules
Reading rules file: /lib/udev/rules.d/80-net-setup-link.rules
Reading rules file: /lib/udev/rules.d/84-nm-drivers.rules
Reading rules file: /lib/udev/rules.d/85-hdparm.rules
Reading rules file: /lib/udev/rules.d/85-hwclock.rules
Reading rules file: /lib/udev/rules.d/85-nm-unmanaged.rules
Reading rules file: /lib/udev/rules.d/85-regulatory.rules
Reading rules file: /lib/udev/rules.d/89-alsa-ucm.rules
Reading rules file: /lib/udev/rules.d/90-alsa-restore.rules
Reading rules file: /etc/udev/rules.d/90-builtin-net-rps.rules
Reading rules file: /lib/udev/rules.d/90-console-setup.rules
Reading rules file: /lib/udev/rules.d/90-nm-thunderbolt.rules
Reading rules file: /lib/udev/rules.d/95-dm-notify.rules
Reading rules file: /etc/udev/rules.d/99-openmediavault-md-raid.rules
Reading rules file: /etc/udev/rules.d/99-openmediavault-nonrot.rules
Reading rules file: /etc/udev/rules.d/99-openmediavault-scheduler.rules
Reading rules file: /lib/udev/rules.d/99-systemd.rules
Reading rules file: /etc/udev/rules.d/hdmi.rules
Rules contain 49152 bytes tokens (4096 * 12 bytes), 17035 bytes strings
2625 strings (34387 bytes), 1797 de-duplicated (18181 bytes), 829 trie nodes used
Invalid inotify descriptor.
Starting 'ata_id --export /dev/sdc'
Process 'ata_id --export /dev/sdc' failed with exit code 2.
Starting 'serial_id /dev/sdc'
Process 'serial_id /dev/sdc' failed with exit code 1.
DEVPATH=/devices/platform/soc/soc:usb3-0/12000000.dwc3/xhci-hcd.3.auto/usb4/4-1/4-1.2/4-1.2.3/4-1.2.3:1.0/host2/target2:0:0/2:0:0:0/block/sdc
DEVNAME=/dev/sdc
DEVTYPE=disk
MAJOR=8
MINOR=32
ACTION=add
SUBSYSTEM=block
ID_VENDOR=JMicron
ID_VENDOR_ENC=JMicron\x20
ID_VENDOR_ID=152d
ID_MODEL=Generic_DISK01
ID_MODEL_ENC=Generic\x20DISK01\x20\x20
ID_MODEL_ID=0567
ID_REVISION=0103
ID_SERIAL=JMicron_Generic_DISK01_0123456789ABCDEF-0:0
ID_SERIAL_SHORT=0123456789ABCDEF
ID_TYPE=disk
ID_INSTANCE=0:0
ID_BUS=usb
ID_USB_INTERFACES=:080650:
ID_USB_INTERFACE_NUM=00
ID_USB_DRIVER=usb-storage
DEVLINKS=/dev/disk/by-path/platform-xhci-hcd.3.auto-usb-0:1.2.3:1.0-scsi-0:0:0:0 /dev/disk/by-id/usb-JMicron_Generic_DISK01_0123456789ABCDEF-0:0
ID_PATH=platform-xhci-hcd.3.auto-usb-0:1.2.3:1.0-scsi-0:0:0:0
ID_PATH_TAG=platform-xhci-hcd_3_auto-usb-0_1_2_3_1_0-scsi-0_0_0_0
ID_PART_TABLE_UUID=3350513c-271c-47be-97f0-be09ab6a0c9a
ID_PART_TABLE_TYPE=gpt
.ID_FS_TYPE_NEW=
ID_FS_TYPE=
TAGS=:systemd:
USEC_INITIALIZED=16538242
run: '/lib/udev/hdparm'
Unload module index
Unloaded link configuration context.

I have updated to 5.22.2-1 but does not make any difference.

one problem: I cannot log into omv panel anymore. Here is the error log:

OMV\Rpc\Exception: Failed to connect to socket: Connection refused in /usr/share/php/openmediavault/rpc/rpc.inc:141
Stack trace:
#0 /var/www/openmediavault/rpc/session.inc(57): OMV\Rpc\Rpc::call('UserMgmt', 'authUser', Array, Array, 2, true)
#1 [internal function]: OMVRpcServiceSession->login(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('login', Array, Array)
#4 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMV\Rpc\Rpc::call('Session', 'login', Array, Array, 3)
#5 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle()
#6 {main}

Here is output of systemctl openmediavault-engined.service --no-pager -l

omv-engined[6726]: PHP Fatal error: Uncaught OMV\Config\DatabaseException: Fatal error 76: Opening and ending tag mismatch: mntent line 406 and fstab (line=467, column=13); Fatal error 76: Opening and ending tag mismatch: fstab line 393 and system (line=602, column=12); Fatal error 76: Opening and ending tag mismatch: system line 6 and config (line=1070, column=10); Fatal error 77: Premature end of data in tag config line 2 (line=1071, column=1) in /usr/share/php/openmediavault/config/databasebackend.inc:113
omv-engined[6726]: Stack trace:
omv-engined[6726]: #0 /usr/share/php/openmediavault/config/database.inc(34): OMV\Config\DatabaseBackend->load()
omv-engined[6726]: #1 /usr/share/php/openmediavault/config/database.inc(44): OMV\Configomv-engined[6726]: #2 /usr/share/openmediavault/engined/inc/59mergerfs.inc(24): OMV\Config\Database::getInstance()
omv-engined[6726]: #3 /usr/sbin/omv-engined(360): require_once('/usr/share/open...')
omv-engined[6726]: #4 {main}
omv-engined[6726]:   thrown in /usr/share/php/openmediavault/config/databasebackend.inc on line 113
systemd[1]: openmediavault-engined.service: Main process exited, code=exited, status=255/EXCEPTION
systemd[1]: openmediavault-engined.service: Failed with result 'exit-code'.

Here is my /etc/fstab

UUID=04bf4f7c-eeca-4744-ab20-d0eb46d8e106 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1
tmpfs /tmp tmpfs defaults,nosuid 0 0
# >>> [openmediavault]
/dev/disk/by-label/samsung              /srv/dev-disk-by-label-samsung  ext4    defaults,nofail,user_xattr,noexec,usrjquota=aquota.use
r,grpjquota=aquota.group,jqfmt=vfsv0,acl  0 2
/dev/disk/by-label/WDGREEN              /srv/dev-disk-by-label-WDGREEN  ext4    defaults,nofail,user_xattr,noexec,usrjquota=aquota.use
r,grpjquota=aquota.group,jqfmt=vfsv0,acl  0 2
/dev/disk/by-id/ata-ST2000DM001-1ER164_W4Z28Y7S-part1           /srv/dev-disk-by-id-ata-ST2000DM001-1ER164_W4Z28Y7S-part1       ext4
  defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl  0 2
/srv/dev-disk-by-label-samsung:/srv/dev-disk-by-label-WDGREEN:/srv/dev-disk-by-id-ata-ST2000DM001-1ER164_W4Z28Y7S-part1         /srv/7
e5e6032-1f1c-4efc-a74d-f3fe95fe606f       fuse.mergerfs   defaults,allow_other,cache.files=off,use_ino,category.create=epmfs,minfreesp
ace=4G,x-systemd.requires=/srv/dev-disk-by-label-samsung,x-systemd.requires=/srv/dev-disk-by-label-WDGREEN,x-systemd.requires=/srv/dev
-disk-by-id-ata-ST2000DM001-1ER164_W4Z28Y7S-part1     0 0

# <<< [openmediavault]

Quote from gderf

Edit /etc/fstab and comment out the line that mounts the union.

OK thx it worked!

I removed every entry to the failed disk in /etc/fstab and also in /etc/openmediavault/config.xml and now it boots ok

Hello,

I have the following setup:

• OMV5
• UnionFS with 5 disks

One of the 5 disks has failed. OMV won't boot up, throwing an failed dependency error and going to emergency recovery mode so OMV panel is not available anymore.

How can I remove the affected disk from unionFS (and maybe from OMV totally) without access to the panel. Which config files do I need to edit?

kr

Wouter

It turned out the config.xml file was empty indeed. Upon further investigation, I discovered my sd card went corrupt. My installation did behave strange the last week indeed (omv password not accepted, mysql server crashing..)
I'll try with a new sd card (luckily I backup regulartly)
thanks for your help.

kr
wouter

Hi,
Yesterday I've upgraded from OMV 4 to 5. I cannot log into the webgui anymore. It states failed to connect to socket: connection refused
And this error details:

Error #0:
OMV\Rpc\Exception: Failed to connect to socket: Connection refused in /usr/share/php/openmediavault/rpc/rpc.inc:141
Stack trace:
#0 /var/www/openmediavault/rpc/session.inc(56): OMV\Rpc\Rpc::call('UserMgmt', 'authUser', Array, Array, 2, true)
#1 [internal function]: OMVRpcServiceSession->login(Array, Array)
#2 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#3 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('login', Array, Array)
#4 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMV\Rpc\Rpc::call('Session', 'login', Array, Array, 3)
#5 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle()
#6 {main}

I uninstalled all plugins designed for omv4 (except for openmediavault-keyring which carries version number 1.0 so guess it's been there some versions.
Looking up the traceback message from omv-engined -d -f it seems a database (connection) error. Could someone help please?
Everything I've set up like my samba shares does seem to work however

PHP Fatal error:  Uncaught OMV\Config\DatabaseException: Fatal error 4: Document is empty (line=1, column=1) in /usr/share/php/openmediavault/config/databasebackend.inc:113
Stack trace:
#0 /usr/share/php/openmediavault/config/database.inc(34): OMV\Config\DatabaseBackend->load()
#1 /usr/share/php/openmediavault/config/database.inc(44): OMV\Config\Database->__construct()
#2 /usr/share/openmediavault/engined/inc/59mergerfs.inc(24): OMV\Config\Database::getInstance()
#3 /usr/sbin/omv-engined(360): require_once('/usr/share/open...')
#4 {main}
  thrown in /usr/share/php/openmediavault/config/databasebackend.inc on line 113
omv-engined[23389]: PHP Fatal error: Uncaught OMV\Config\DatabaseException: Fatal error 4: Document is empty (line=1, column=1) in /usr/share/php/openmediavault/config/databasebackend.inc:113
omv-engined[23389]: Stack trace:
omv-engined[23389]: #0 /usr/share/php/openmediavault/config/database.inc(34): OMV\Config\DatabaseBackend->load()
omv-engined[23389]: #1 /usr/share/php/openmediavault/config/database.inc(44): OMV\Config\Database->__construct()
omv-engined[23389]: #2 /usr/share/openmediavault/engined/inc/59mergerfs.inc(24): OMV\Config\Database::getInstance()
omv-engined[23389]: #3 /usr/sbin/omv-engined(360): require_once('/usr/share/open...')
omv-engined[23389]: #4 {main}
omv-engined[23389]:   thrown in /usr/share/php/openmediavault/config/databasebackend.inc on line 113
PHP Fatal error: Uncaught OMV\Config\DatabaseException: Fatal error 4: Document is empty (line=1, column=1) in /usr/share/php/openmediavault/config/databasebackend.inc:113
Stack trace:
#0 /usr/share/php/openmediavault/config/database.inc(34): OMV\Config\DatabaseBackend->load()
#1 /usr/share/php/openmediavault/config/database.inc(44): OMV\Config\Database->__construct()
#2 /usr/share/openmediavault/engined/inc/59mergerfs.inc(24): OMV\Config\Database::getInstance()
#3 /usr/sbin/omv-engined(360): require_once('/usr/share/open...')
#4 {main}
  thrown in /usr/share/php/openmediavault/config/databasebackend.inc on line 113

Hi,
I'm having this annoying problem that for random folders on my share I got the following error when creating files: No space left on device
My unionFS disk (mounted on /srv/ ) has over 2.5 TB left. The strange thing is this happens for random folders.
Eg:

/Movies/USA : no problem writing files
/Movies/EUR : no space left on device

What could be the problem please?

kr
wouter

Quote from brotbox

Thanks for the quick answer. That sounds good. To be honest, I have to read myself a little bit, as the guide assumes more basic knowledge than I expected at first^^.
Maybe I will simply get nextcloudplus(pi) via docker. I was already enthusiastic about the ncp panel. Do you think this would run on our h2/XU4q: ownyourbits/nextcloudplus-armhf or must it be special for arm64?^^

I really doubt this will work for odroid. This sit ementions it's compiled for rpi. So most probably this will not run on odroid because it's not compiled for this soc.

You can try the 'normal' way. It sounds difficult at first, but once you understand the logic behind a LAMP/LEMP you can do many nice projects in the future.

Quote from macom

Have a look here:

OMV4 on ARM boards (kind of a how-to)

Ok perfect, installing a clean OMV3 and doing the [i]omv-release-upgrade [/i]will do the job for me.
Thanks

Quote from macom

Isn't the XU4q the same as XU4 just with a passive heat sink?

I would try the image for XU4.
https://sourceforge.net/projec…lt/files/Odroid%20images/

Yes, it is but these images are all for OMV3.
Aren't there any images for OMV4?

Hi,
I've bought an Odroid XU4q and now I want to install Openmediavault on it but I don't see an image of it on Sourceforge.
How can I install it anyway? Install armbian first and then Openmediavault or do I burn an OMV3 image first and then perform update?

kr,
wouter

Quote from brotbox

Hey,
Thank you in advance for your guide. I've read it would also be possible with php 7(.2).
I would like to install nc13 on my odroid hc2 with omv4. My plan is to install nc12 first and then update to 13, but unfortunately I am a beginner with linux,php an omv.
I would be very happy if someone could give me the commands to run it with php7 and I could then upgrade to nc13 (Pre-Installation Steps 1a and if more customization is necessary)
Many thanks in advance

Why would you want to install NC12 first? You could as well install NC13 directly (link). Botch support PHP 5.6 & 7.x
As I remember these steps are quite acurate for later versions as well.
I'm planning to install OMV4 on an odroid (XU4q) as well in the coming weeks so maybe I can help later on.

Hi,
thanks for this useful information. Regarding the Odroid HC1/2: my current setup consists of 3 usb harddisks so I really need seperate usb ports. So the XU4Q seems the most adequate option in terms of connectivity and performance (I'm also running nextcloud on it which sometimes leads to cpu throtling when doing some tasts simultaneously.)

In regards to writing speeds; I guess that my current network is the weak link.
Here is my set up:

• 100 Mbit
• wifi speed: 30 Mbit down / 5 Mbit up (measured by iperf3)

So upgrading to Odroid will not lead to significant more performance in terms of write/read speeds I guess?
But it's a good thing to be future proof, and as you mention OMV4: it would also be a good idea to install this new version directly. In this regard, PHP will be upgraded tot 7.X so also good news for future upgrades for Nextcloud (which stops supporting 5.X with the next version).

kr,
wouter

Hi,

I'm thinking about upgrading my current setup (Raspberry 3 PI) to something with Gigabit/usb3.
Technically, the Odroid XU4Q seems a good choice (must be silence since it's in my livinug room, hence the passive cooling version).

I'm just wondering wether It is a good choic in practice? As i've read in this forum there were problems with the wiring of USB3 ports (posts dates from mid last year so maybe this has been solved already).

Also, when upgrading: I've learned you cannot transfer the configuration so everything needs to be reconfigured. No problem, but I'm a bit afraid for my disk setup: there are 3 in a unionFS configuration. Will I be able to add them again in this pool without losing data or to rewrite everything again to the disks please?

Quote from Nibb31

Why would you "upgrade" to a device that isn't suited to be a NAS. If you want to upgrade, look for something with proper USB and gigabit Ethernet.

Any suggestions? The PI is indeed slow to transfer files to but ideaal to stream video and music from. Was also looking for Pine/rock64 but not sure about support.
If I switch, I want something well supported and gigabit/usb3 with comparable prices to PI.

Hello,

I see that the newest images for OMV3 are compatible with the latest Raspberry PI3+.
So I'm wondering wether I can use my current installation (which has all the updates) and install my sd-card in a PI3+. Will it be compatible?

kr,

wouter

Quote from wouterve

Yes, i've done it in that way. Only other thing i have changed in nginx options is the access permission for the '.well-known' directory otherwise i received a 403 permission denied error.I added these lines before generating certificate ;

Display Spoiler

location ^~ /.well-known/ {
allow all;
root /var/www/openmediavault;
try_files $uri =404;
}

Display More

Okay, I had made a stupid error. The root of my nextcloud was not /var/www/openmediavault but /srv/XXXX (my external drive pool).

Anyway, to sum things up: I changed openmediavault to another port and put nextcloud on 80 (no need anyway for openmediavault to be externally available or not through https anyway). So I followed the guidelines for letsencrypt and everything works now with ssl certificate :-).