New configuration with USB adapter failing

Skimmed1976 · Nov 5th 2025

Hello,

I have an old drive I'd like to package with a raspberry pi for offsite backups. I ran into OMV and it seems like it should do exactly what I need. I like the easy setup of the wireguard plugin and a nice web interface to configure everything with. However, I'm running into a problem with a USB to SATA converter.

The one I used to set up the proof of concept (ASM1053E) works just fine. I see SMART status, drive spins down when it is supposed to, and everything just seems to work But when I move the drive to the smaller, enclosure friendly, usb to sata adapter (JMS583Gen 2) the drive will mount but nothing else works. And if I try to interact with the disk controls or statistics the drive will dismount. Like, if I go to the Disks tab, the blue line will show its loading until the drive dismounts and it will then give an error that /dev/sda does not exist. If I leave SMART off and dont touch the web interface it can do a 16 hour backup transfer just fine. This wouldn't be a problem except the disk doesn't ever spin down.

The googles suggested adding usb-storage.quirks=152d:0583:u to the raspberry pi config or even adding a file called /etc/modprobe.d/disable_uas.conf with the config and updating initramfs. However neither of these seem to work. In fact, without the quirks enabled I'm still able to perform a sudo smartctl -a -d sat /dev/sda and get a proper output. So I'm not sure that the quirks are the issue here.

I've seen people with Jmicron controllers have issues on these threads but not this specific one. Does anyone have suggestions before I abandon OMV and just set up the backups using SSH?

Barney · Nov 6th 2025

Did you also move it into the new enclosure? Maybe it's power supply is wimpy?

Skimmed1976 · Nov 6th 2025

So the enclosure is a 3d printed one of my design and it uses a 5amp 12v psu to power both the drive and the pi via buck converter. but I'm having this issue even staging with the psu that came with the device. Definitely seems to be a software thing. It's weird because until I go to look at the disk it stays mounted and it is fully accessible over the network. When I look at the logs I'm not seeing any errors when the drive disappears.

I made a viable option last night just using the lite pi image, SSH, auto mounting and auto wireguard. it doesn't have the nice web interface to check on things but it will function for what I need. Maybe I'll try OMV in a few months to see if the bugs are worked out.

ryecoaaron · Nov 6th 2025

Quote from Skimmed1976

Maybe I'll try OMV in a few months to see if the bugs are worked out.

While I don't think this is an OMV issue, it is unlikely to ever be "fixed" since it only happens on very specific hardware. Seems kernel related. OMV just adds entries to /etc/fstab. How did you "auto mount" that is working? And if it works with the ASM1053E adapter, why not keep using it?

Skimmed1976 · Nov 6th 2025

Quote from ryecoaaron

While I don't think this is an OMV issue, it is unlikely to ever be "fixed" since it only happens on very specific hardware. Seems kernel related. OMV just adds entries to /etc/fstab. How did you "auto mount" that is working? And if it works with the ASM1053E adapter, why not keep using it?

for my non-omv build yes I just added the entry to fstab with the uuid and it works a treat. The issue with OMV is not failure to mount, but the drive dismounting any time omv tries to poll it.

so for example, I restart the machine, my share is available on my network. I send a couple of backups to it and it stays on the network. It will seemingly stay that way indefinitely. However, as soon as I go to the disks tab, it will hang until something times out, sda will no longer be in /dev and lsusb doesn't even show the usb to sata adapter. So I don't think the issue is with mounting at all, some other process that polls the drive causes it to lock up.

I'm not sure what this process is because I haven't found this in the various logs I checked. If I run smartctl I get an output, but if I want to see drive temp on the dashboard it just hangs and the drive eventually disconnects. If I don't monitor the drive at all it stays mounted and works just fine.

It's possible that the jmicron controller is just incompatible with omv, or a service that omv uses. I can get smartctl working without quirks enabled and the drive mounts just fine. But it will hang and disconnect any time I try to monitor it or go into disks to set a spindown timer. Monitoring isn't a deal breaker for me but no spindown is.

ryecoaaron · Nov 6th 2025

Quote from Skimmed1976

It's possible that the jmicron controller is just incompatible with omv, or a service that omv uses.

OMV is just a web frontend that is executing standard linux commands via php on the backend. It isn't doing anything to be compatible with specific hardware.

I would be curious what you would see if you put omv-engined in debug mode to see what the actual problem is. But the fact that the filesystem is unmounting itself (OMV isn't doing that) makes me think there is a hardware problem with the kernel module it is using.

If you want to try debug mode:

as root (not sudo)

monit stop omv-engined

omv-engined -df

Skimmed1976 · Nov 7th 2025

Thanks for the suggestion. I have ran the debugs. when I click on disks tab, I get a ton of these flying by maybe 1 of these blocks a second until it times out:

Code

omv-engined[7573]:
omv-engined[6698]: SIGCHLD received ...
omv-engined[6698]:
omv-engined[6698]: Child (pid=7572) terminated with exit code 0
omv-engined[6698]:
omv-engined[6698]: SIGCHLD received ...
omv-engined[6698]:
omv-engined[6698]: Child (pid=7573) terminated with exit code 0
omv-engined[6698]:
omv-engined[7574]: Child process forked (pid=7574)
omv-engined[7574]:
omv-engined[7575]: Child process forked (pid=7575)
omv-engined[7575]:
omv-engined[7574]: Executing RPC (service=Exec, method=getOutput, params={"filename":"\/tmp\/bgstatusbK72BG","pos":0}, context={"username":"admin","role":1}) ...
omv-engined[7574]:
omv-engined[7574]: RPC response (service=Exec, method=getOutput, time=3ms): {"response":{"filename":"\/tmp\/bgstatusbK72BG","pos":0,"output":"","pendingOutput":false,"running":t                                                                                                 rue},"error":null}
omv-engined[7574]:
omv-engined[7575]: Executing RPC (service=Exec, method=getOutput, params={"filename":"\/tmp\/bgstatusThFseb","pos":0}, context={"username":"admin","role":1}) ...
omv-engined[7575]:
omv-engined[7575]: RPC response (service=Exec, method=getOutput, time=4ms): {"response":{"filename":"\/tmp\/bgstatusThFseb","pos":0,"output":"","pendingOutput":false,"running":t                                                                                                 rue},"error":null}
omv-engined[7575]:

Display More

with a couple of these system info blocks peppered between them:

Code

omv-engined[7551]: RPC response (service=System, method=getInformation, time=1047ms): {"response":{"ts":1762384196,"time":"Wed Nov  5 17:09:56 2025","hostname":"backup01","versi                                                                                                 on":"7.7.19-2 (Sandworm)","cpuModelName":"Raspberry Pi 4 Model B Rev 1.5","cpuUtilization":13.25,"cpuCores":null,"cpuMhz":null,"memTotal":"3981369344","memFree":"3463835648","me                                                                                                 mUsed":"303960064","memAvailable":"3677409280","memUtilization":"0.07634","kernel":"Linux 6.12.56-v8+","uptime":1201.22,"loadAverage":{"1min":1.84,"5min":0.69,"15min":0.36},"con                                                                                                 figDirty":false,"dirtyModules":[],"rebootRequired":false,"availablePkgUpdates":0,"displayWelcomeMessage":false},"error":null}
omv-engined[7551]:

and then when the error pops up on the web interface I get this block saying SDA is gone:

Code

omv-engined[6814]: Executing background process failed: Device '/dev/sda' does not exist. (file=/usr/share/php/openmediavault/system/blockdevice.inc, line=94)
omv-engined[6813]: Failed to fetch SMART information: 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=; udevadm info --query=property --name='/dev/sda' 2>&1' with exit code '1': Unknown device "/dev/sda": No such device
omv-engined[6813]: Executing background process failed: Device '/dev/sda' does not exist. (file=/usr/share/php/openmediavault/system/blockdevice.inc, line=94)
omv-engined[7609]: Child process forked (pid=7609)
omv-engined[7609]:
omv-engined[7610]: Child process forked (pid=7610)
omv-engined[7610]:
omv-engined[7609]: Executing RPC (service=Exec, method=getOutput, params={"filename":"\/tmp\/bgstatusbK72BG","pos":0}, context={"username":"admin","role":1}) ...
omv-engined[7609]:
omv-engined[7609]: RPC response (service=Exec, method=getOutput, time=5ms): {"response":null,"error":{"code":0,"message":"Device '\/dev\/sda' does not exist.","trace":"OMV\\Exce                                                                                                 ption: Device '\/dev\/sda' does not exist. in \/usr\/share\/php\/openmediavault\/system\/blockdevice.inc:94\nStack trace:\n#0 \/usr\/share\/openmediavault\/engined\/rpc\/diskmgm                                                                                                 t.inc(96): OMV\\System\\BlockDevice->getCanonicalDeviceFile()\n#1 [internal function]: Engined\\Rpc\\DiskMgmt->enumerateDevices()\n#2 \/usr\/share\/php\/openmediavault\/rpc\/ser                                                                                                 viceabstract.inc(124): call_user_func_array()\n#3 \/usr\/share\/openmediavault\/engined\/rpc\/diskmgmt.inc(141): OMV\\Rpc\\ServiceAbstract->callMethod()\n#4 [internal function]:                                                                                                  Engined\\Rpc\\DiskMgmt->getList()\n#5 \/usr\/share\/php\/openmediavault\/rpc\/serviceabstract.inc(124): call_user_func_array()\n#6 \/usr\/share\/php\/openmediavault\/rpc\/servi                                                                                                 ceabstract.inc(155): OMV\\Rpc\\ServiceAbstract->callMethod()\n#7 \/usr\/share\/php\/openmediavault\/rpc\/serviceabstract.inc(628): OMV\\Rpc\\ServiceAbstract->OMV\\Rpc\\{closure}                                                                                                 ()\n#8 \/usr\/share\/php\/openmediavault\/rpc\/serviceabstract.inc(152): OMV\\Rpc\\ServiceAbstract->execBgProc()\n#9 \/usr\/share\/openmediavault\/engined\/rpc\/diskmgmt.inc(168                                                                                                 ): OMV\\Rpc\\ServiceAbstract->callMethodBg()\n#10 [internal function]: Engined\\Rpc\\DiskMgmt->getListBg()\n#11 \/usr\/share\/php\/openmediavault\/rpc\/serviceabstract.inc(124):                                                                                                  call_user_func_array()\n#12 \/usr\/share\/php\/openmediavault\/rpc\/rpc.inc(86): OMV\\Rpc\\ServiceAbstract->callMethod()\n#13 \/usr\/sbin\/omv-engined(546): OMV\\Rpc\\Rpc::call                                                                                                 ()\n#14 {main}","http_status_code":500}}
omv-engined[7609]:
omv-engined[7610]: Executing RPC (service=Exec, method=getOutput, params={"filename":"\/tmp\/bgstatusThFseb","pos":0}, context={"username":"admin","role":1}) ...
omv-engined[7610]:
omv-engined[7610]: RPC response (service=Exec, method=getOutput, time=5ms): {"response":null,"error":{"code":0,"message":"Device '\/dev\/sda' does not exist.","trace":"OMV\\Exce                                                                                                 ption: Device '\/dev\/sda' does not exist. in \/usr\/share\/php\/openmediavault\/system\/blockdevice.inc:94\nStack trace:\n#0 \/usr\/share\/openmediavault\/engined\/rpc\/diskmgm                                                                                                 t.inc(96): OMV\\System\\BlockDevice->getCanonicalDeviceFile()\n#1 [internal function]: Engined\\Rpc\\DiskMgmt->enumerateDevices()\n#2 \/usr\/share\/php\/openmediavault\/rpc\/ser                                                                                                 viceabstract.inc(124): call_user_func_array()\n#3 \/usr\/share\/openmediavault\/engined\/rpc\/diskmgmt.inc(141): OMV\\Rpc\\ServiceAbstract->callMethod()\n#4 [internal function]:                                                                                                  Engined\\Rpc\\DiskMgmt->getList()\n#5 \/usr\/share\/php\/openmediavault\/rpc\/serviceabstract.inc(124): call_user_func_array()\n#6 \/usr\/share\/php\/openmediavault\/rpc\/servi                                                                                                 ceabstract.inc(155): OMV\\Rpc\\ServiceAbstract->callMethod()\n#7 \/usr\/share\/php\/openmediavault\/rpc\/serviceabstract.inc(628): OMV\\Rpc\\ServiceAbstract->OMV\\Rpc\\{closure}                                                                                                 ()\n#8 \/usr\/share\/php\/openmediavault\/rpc\/serviceabstract.inc(152): OMV\\Rpc\\ServiceAbstract->execBgProc()\n#9 \/usr\/share\/openmediavault\/engined\/rpc\/diskmgmt.inc(168                                                                                                 ): OMV\\Rpc\\ServiceAbstract->callMethodBg()\n#10 [internal function]: Engined\\Rpc\\DiskMgmt->getListBg()\n#11 \/usr\/share\/php\/openmediavault\/rpc\/serviceabstract.inc(124):                                                                                                  call_user_func_array()\n#12 \/usr\/share\/php\/openmediavault\/rpc\/rpc.inc(86): OMV\\Rpc\\ServiceAbstract->callMethod()\n#13 \/usr\/sbin\/omv-engined(546): OMV\\Rpc\\Rpc::call                                                                                                 ()\n#14 {main}","http_status_code":500}}
omv-engined[7610]:

Display More

ryecoaaron · Nov 7th 2025

Since your system is an rpi, the usb bus is shared between multiple devices. It is possible that one usb-sata adapter handles it better than the other. If you are seeing disconnect messages when this happens in dmesg, there isn't much we can do. This is a kernel and/or driver and/or usb-sata adapter issue.

Skimmed1976 · Nov 7th 2025

Yeah I'm not sure what those debugs are telling me. It seems to try to reference that tmp file and fails but I don't get an error that I can reference to keep troubleshooting. Maybe omv 8 and trixie will work whenever that comes out. Or I'll just go ahead with using the base rpi image. I have ssh transfers, wireguard and spindown working on that so it will suffice. I guess I don't need the fancy web interface or SMB. Thanks for you help anyways

ryecoaaron · Nov 8th 2025

Quote from Skimmed1976

I'm not sure what those debugs are telling me. It seems to try to reference that tmp file and fails but I don't get an error that I can reference to keep troubleshooting.

They literally mean the device doesn't exist meaning the Linux kernel doesn't see the device anymore. This is not an OMV issue. Because of the reasons I already mentioned, you are not going to be able to fix it unless you can write linux kernel drivers.

Quote from Skimmed1976

Maybe omv 8 and trixie will work whenever that comes out

omv8 can't fix this unless a newer kernel fixes it. You could install Raspberry pi OS based on Debian 13 Trixie and see if you ever have any problems with it. If not, maybe omv 8 won't but omv8 can't fix a missing drive.

yann1420 · Jan 6th 2026

In the past I used to run OMV on a raspberry pi. As I can not find instruction how to install OMV8 on a RPI running Trixie, I wonder if this combination ever will be supported? And if so, what is the expected time frame?
Thanks in advance.

chente · Jan 6th 2026

Quote from yann1420

In the past I used to run OMV on a raspberry pi. As I can not find instruction how to install OMV8 on a RPI running Trixie, I wonder if this combination ever will be supported? And if so, what is the expected time frame?
Thanks in advance.

See --> https://wiki.omv-extras.org/do…omv8:raspberry_pi_install

yann1420 · Jan 6th 2026

Fantastic. Will give it a try.

New configuration with USB adapter failing

chente Nov 5th 2025

Participate now!