ChatGPT, analyzed the logs and pin pointed the problem.
It seems that particular hard drive -WD Elements 3tb- isn't working in UASP mode but in usb-storage mode.
There is not much can be done but OMV users, should check with drives work in USB3 UASP mode , which do not before buying.
I did a few experiments. disconnected the drives and boot up that way, then connect them again and boot them again. etc.
I dont know what this changed my it started to transfer insanely fast. 120 MB/s from the computer and 170 MB/s between the hard disk on the RP4.
I'm not sure what happened but somehow, disconnecting all of them and connecting again solved the problem.
Starting Jellyfin, slows the drives again. Wonder what that got to do with anything. It accesses the NTFS drive. Maybe there is somekind of a conflict with the NTFS service. When transfering from the computer to that particular drive, it can be around 120MB/s, which is the max I get with it. But whenever a NTFS drive connected to RP involved, the transfers drop to 5-10MB/s. Highly likely NTFS service of Linux is involved.
If the file is like 200MB (byte) then transfer goes at the max speed of the drive 120MB/s, but if it is bigger than that like 700MB, then at the middle of the transfer speed starts to drop to 10MB/s. Something bogging the system, I checked the CPU usage, it seems ok.
It's connected via 1Gb ethernet cable.
I used one 1.5gb file for speedtest.
It is 10 MB/s, from the Windows 11 file transfer window.
The other harddisk on the same RP and same USB 3 port can transfer about 40MB/s, which is far from the top speed of the drive but at least acceptable.
I applied the SMB 'Extra Options' from the related thread but the speed did not change at all.
The speed of reading from these drives is about 60MB/s for both of them.
I'm running OMV on a Raspberry Pi 4 and I have two usb hard disk drives attached to it.
I'm sharing the files via Samba with a Windows 11 machine. One hard drive (a Seagate 6gb with its own power and USB hub) has transfer speed around 40mb/sec.
The problem is the 2tb WD drive. It can hardly reach 10mb/sec while writing. I connect it through the USB hub on the other drives. I changed it to a USB3 port on the RP4 itself and the speed didn't improve at all.
If I connect those drives to a Window 11 machine both can easily reach 110mb/sec and above.
So drives or their cables aren't the problem.
I converted the slow (WD 2tb) to EXT4 file format, but again speeds didn't improve at all.
I'm not sure where I should be looking. What may be the problem?
Do you have a solution? I also encountered the same problem!
not really. I just wrote my backup image back to the sdcard , which seems to be the only solution I can find nowadays.
Are you sure the password is failing or are you in a login loop?
yes. I'm sure the password is failing. the first post has the error msg .
changing the password via omv-firstaid didn't change anything either. The new password fails too.
I cleaned the cache and tried with different browsers.
I'm using "admin " as user.
Today , i needed to make changes to OMV but password/login is rejected. The thing is I didnt make any changes lately and it was working fine yesterday.
I ssh'ed into raspberry pi and used omv-firstaid to changed the password , and the new password is rejected too. I checekl the disks , none of the disks are full, including boot disk.
Another solution adviced was to use these commands , yet they didnt work either.
usermod -a -G openmediavault-admin admin
groupadd --system openmediavault-adminI'm using OMV on a Raspberry pi 3b+, with the latest updates applied.
Apart from the web interface , device seems to work fine.
Any ideas what the problem may be?
Error
Incorrect username or password.
Error #0:
OMV\HttpErrorException: Incorrect username or password. in /var/www/openmediavault/rpc/session.inc:151
Stack trace:
#0 [internal function]: OMVRpcServiceSession->login(Array, Array)
#1 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('login', Array, Array)
#3 /usr/share/php/openmediavault/rpc/proxy/json.inc(97): OMV\Rpc\Rpc::call('Session', 'login', Array, Array, 3)
#4 /var/www/openmediavault/rpc.php(45): OMV\Rpc\Proxy\Json->handle()
#5 {main}Thank you for the quick response.
this is what I get for the "systemctl status smbd.service"
There is an error but any ideas about the cause?
smbd.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smbd.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2021-07-31 19:16:45 +03; 33min ago
Docs: man:smbd(8)
man:samba(7)
man:smb.conf(5)
Process: 949 ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (code=exited, status=0/SUCCESS)
Main PID: 950 (smbd)
Status: "smbd: ready to serve connections..."
Tasks: 8 (limit: 2059)
CGroup: /system.slice/smbd.service
├─ 950 /usr/sbin/smbd --foreground --no-process-group
├─ 961 /usr/sbin/smbd --foreground --no-process-group
├─ 962 /usr/sbin/smbd --foreground --no-process-group
├─10413 /usr/sbin/smbd --foreground --no-process-group
├─10414 sh -c /usr/share/samba/panic-action 10413
├─10415 /bin/sh /usr/share/samba/panic-action 10413
├─10416 gdb -x /etc/samba/gdbcommands -batch /usr/sbin/smbd 10413
└─10417 mail -s Panic or segfault in Samba root
Jul 31 19:50:13 raspberrypi smbd[10413]: INTERNAL ERROR: Signal 11 in pid 10413 (4.9.5-Debian)
Jul 31 19:50:13 raspberrypi smbd[10413]: Please read the Trouble-Shooting section of the Samba HOWTO
Jul 31 19:50:13 raspberrypi smbd[10413]: [2021/07/31 19:50:13.175717, 0] ../lib/util/fault.c:82(fault_report)
Jul 31 19:50:13 raspberrypi smbd[10413]: ===============================================================
Jul 31 19:50:13 raspberrypi smbd[10413]: [2021/07/31 19:50:13.175779, 0] ../source3/lib/util.c:816(smb_panic_s3)
Jul 31 19:50:13 raspberrypi smbd[10413]: PANIC (pid 10413): internal error
Jul 31 19:50:13 raspberrypi smbd[10413]: [2021/07/31 19:50:13.176282, 0] ../lib/util/fault.c:261(log_stack_trace)
Jul 31 19:50:13 raspberrypi smbd[10413]: BACKTRACE: 0 stack frames:
Jul 31 19:50:13 raspberrypi smbd[10413]: [2021/07/31 19:50:13.176427, 0] ../source3/lib/util.c:828(smb_panic_s3)
Jul 31 19:50:13 raspberrypi smbd[10413]: smb_panic(): calling panic action [/usr/share/samba/panic-action 10413]
lines 2-30/30 (END)I'm using OMV5 on a Raspberry Pi 3b+ with Raspbian OS (latest updates applied). Two hard drives are connected to the Rp. Only one of them draws power , other is a self powered USB hard disk.
Setup works flawlessly for a long time , then -probably after an update - I cant see the USB disk from other devices. Rp itself woks fine and it can read/write to the USB drives , so I'm assume the problem is the Samba server.
I'm not sure what the problem may be. Any ideas where should I be checking first?
I tried enabling samba trough web GUI and got an error msg.
Is this useful?
"
Error #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color samba 2>&1' with exit code '1': raspberrypi:
"
That would be a staring point.
Try to restart smbd and then check the journal for entries
systemctl start smbd.service
journalctl -u smbd.service
journalctl returns this.
any ideas?
Isn't this common after the latest updates? we can't be the only ones effected.
"
smbd.service: Main process exited, code=dumped, status=6/ABRT
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit smbd.service has exited.
--
-- The process' exit code is 'dumped' and its exit status is 6.
raspberrypi systemd[1]: smbd.service: Failed with result 'core-dump'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit smbd.service has entered the 'failed' state with result 'core-dump'.
raspberrypi systemd[1]: Failed to start Samba SMB Daemon.
-- Subject: A start job for unit smbd.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit smbd.service has finished with a failure.
--
-- The job identifier is 1816 and the job result is failed.
raspberrypi polkitd(authority=local)[13936]: Unregistered Authentication Agent for unix-process:13931:13
raspberrypi CRON[14031]: pam_unix(cron:session): session opened for user root by (uid=0)
raspberrypi CRON[14032]: (root) CMD (/usr/sbin/omv-ionice >/dev/null 2>&1)
raspberrypi CRON[14031]: pam_unix(cron:session): session closed for user root
lines 1457-1485/1485 (END)
"
restarting the samba service didnt work on my side.
I used
sudo service smbd stop
to stop
then
sudo service smbd start
to start but I'm getting an error
"
Job for smbd.service failed because a fatal signal was delivered causing the control process to dump core.
See "systemctl status smbd.service" and "journalctl -xe" for details.
"
Any ideas what may be the problem ? It started after the latest updates.
I have openmediavault installed on Raspbian with the latest updates, on a Raspberry Pi 3b+.
Now I see that the new Portainer is released, 2.5.1 a few days ago. I can't upgrade to it using OMV.
I always use the OMV web page and choose "install portainer " for updating but this time it returns this error. Any idea what may be the problem?
"
Docker storage :: /var/lib/docker
Agent port:: 8000
Web port:: 9000
Yacht port:: 8001
arch :: armhf
option :: portainer
state :: install
extras :: 5.6.1
DNS OK.
No portainer containers or images to remove.
Creating portainer volume ...
Pulling and starting portainer/portainer-ce ...
Something went wrong trying to pull and start portainer ...
Done.
"
OMV5 and Pihole runs fine side by side. Simplest way is to change the default port of OMV from 80 to 8080 or whatever you want.
I run it like that on a nanopi neo (Armbian, OMV5, Pihole+Unbound).
How do I change the OMV4 port ? After installing I cant reach the OMV page anymore.
I installed PiHole on OMV 4 . After that I can't reach the OMW admin page, that directs to Pihole admin , the thing is uninstalling Pihole didnt solve anything , now OMV admin page results an error.
I checked for guides for Pyload but so far I can't find a guide for installation as docker. I'm not sure but Docker image from linuxserver seems to be the safe one, https://hub.docker.com/r/linuxserver/pyload .
I'm using Raspberry Pi3b+ , and there are two ARM versions. arm64 and armhf .Is there step by step guide for this one?
OMV-Extras -> Kernel you should be able to change from the drop down
and for that first "Enable backports" should be enabled first? but I get an error "Gateway Timeout" on that option. So I can't enable backports , I can't change the Kernel.
I'm on the latest OMV4 (raspberry pi 3b+) . Any ideas what the problem may be?
Ok . Thank you for the reply.
Does anybody know what should I change on OWM4? I checked the extras tab and I don't see anything related to kernel choosing. I see "backports " but it ends up in a cycle whether I enable or disable it.
