I am not sure, but after changing and cloning the root disk there was an old entry shown in the OMV GUI and I think I tried to delete this entry. Maybe this is a hint and this happens not often to change the installation disk.
Posts by Peppa123
-
-
And there is a job called "dirtymodules.json" with only "[]" in the syntax.
-
And here are the open tasks. I changed the root disks some weeks before and duplicated the installation to the new disk. Before it was a 300 GB Western Digital Hard Drive and now it is a Kingston NVMe Disk.
As I see there is a tasks that tries to delete the entry "/", but the corresponding UUID does not exists anymore and is now different for the "/" entry.
Code
Display More[ { "id": "delete", "func": "deleteEntry", "params": { "uuid": "79684322-3eac-11ea-a974-63a080abab18", "fsname": "\/dev\/disk\/by-uuid\/d92ed47a-0d26-4b32-8e36-64af7164da05", "dir": "\/", "type": "ext4", "opts": "errors=remount-ro", "freq": 0, "passno": 1, "hidden": false, "usagewarnthreshold": 90, "comment": "WD Festplatte 300 GB" } }, { "id": "delete", "func": "deleteEntry", "params": { "uuid": "af6c19b3-a056-4ae9-a52b-5f8587a17758", "fsname": "\/srv\/dev-disk-by-uuid-cd15dd88-5d5b-4390-8553-91abadbeb1cb\/Filme\/", "dir": "\/export\/Filme", "type": "none", "opts": "bind,nofail", "freq": 0, "passno": 0, "hidden": false, "usagewarnthreshold": 0, "comment": "" } }, { "id": "delete", "func": "deleteEntry", "params": { "uuid": "af6c19b3-a056-4ae9-a52b-5f8587a17758", "fsname": "\/srv\/dev-disk-by-uuid-cd15dd88-5d5b-4390-8553-91abadbeb1cb\/Filme\/", "dir": "\/export\/Filme", "type": "none", "opts": "bind,nofail", "freq": 0, "passno": 0, "hidden": false, "usagewarnthreshold": 0, "comment": "" } } ]
-
Actually I am doing and did nothing about deleting the root filesystem. I also don't know why during "pending tasks" there is a job trying to dismount the root filesystem. The only things I did was testing with the "kvm" plugin and this was weeks before. And the "kvm" plugin is installing the "shareroot" plugin, so deinstalling it, also deinstalls the "kvm" plugin.
Here is the output:
Code
Display More{ "total": 4, "data": [ { "devicename": "sdb1", "devicefile": "/dev/disk/by-uuid/94537b05-9875-4501-9a8c-3aa6cbda18db", "predictabledevicefile": "/dev/disk/by-uuid/94537b05-9875-4501-9a8c-3aa6cbda18db", "canonicaldevicefile": "/dev/sdb1", "parentdevicefile": "/dev/sdb", "devlinks": [ "/dev/disk/by-id/ata-ST4000DM004-2CV104_ZFN0G1A4-part1", "/dev/disk/by-id/wwn-0x5000c500a4a14cd7-part1", "/dev/disk/by-label/wdelementsata4tb", "/dev/disk/by-partuuid/de98914b-e35a-4cd4-a8f4-bda550c9312c", "/dev/disk/by-path/pci-0000:00:17.0-ata-4-part1", "/dev/disk/by-path/pci-0000:00:17.0-ata-4.0-part1", "/dev/disk/by-uuid/94537b05-9875-4501-9a8c-3aa6cbda18db" ], "uuid": "94537b05-9875-4501-9a8c-3aa6cbda18db", "label": "wdelementsata4tb", "type": "ext4", "blocks": "3844550452", "mounted": true, "mountpoint": "/srv/dev-disk-by-uuid-94537b05-9875-4501-9a8c-3aa6cbda18db", "used": "1.58 TiB", "available": "2194438725632", "size": "3936819662848", "percentage": 45, "description": "/dev/sdb1 [EXT4, 1.58 TiB (45%) used, 1.99 TiB available]", "propposixacl": true, "propquota": true, "propresize": true, "propfstab": true, "propcompress": false, "propautodefrag": false, "hasmultipledevices": false, "devicefiles": [ "/dev/sdb1" ], "comment": "Seagate Festplatte 4TB", "_readonly": false, "_used": true, "propreadonly": false, "usagewarnthreshold": 95, "mountopts": "defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl", "status": 1 }, { "devicename": "sda1", "devicefile": "/dev/disk/by-uuid/35b74cc0-e206-49a2-ab0a-eb64c2e2d317", "predictabledevicefile": "/dev/disk/by-uuid/35b74cc0-e206-49a2-ab0a-eb64c2e2d317", "canonicaldevicefile": "/dev/sda1", "parentdevicefile": "/dev/sda", "devlinks": [ "/dev/disk/by-id/ata-Samsung_SSD_870_QVO_2TB_S5RPNJ0R807429J-part1", "/dev/disk/by-id/wwn-0x5002538f3180c743-part1", "/dev/disk/by-label/samsungevossd2tb", "/dev/disk/by-partuuid/bde1737e-a55d-4ccd-9250-bcb88cb2e275", "/dev/disk/by-path/pci-0000:00:17.0-ata-3-part1", "/dev/disk/by-path/pci-0000:00:17.0-ata-3.0-part1", "/dev/disk/by-uuid/35b74cc0-e206-49a2-ab0a-eb64c2e2d317" ], "uuid": "35b74cc0-e206-49a2-ab0a-eb64c2e2d317", "label": "samsungevossd2tb", "type": "ext4", "blocks": "1921724676", "mounted": true, "mountpoint": "/srv/dev-disk-by-uuid-35b74cc0-e206-49a2-ab0a-eb64c2e2d317", "used": "930.95 GiB", "available": "968226529280", "size": "1967846068224", "percentage": 51, "description": "/dev/sda1 [EXT4, 930.95 GiB (51%) used, 901.73 GiB available]", "propposixacl": true, "propquota": true, "propresize": true, "propfstab": true, "propcompress": false, "propautodefrag": false, "hasmultipledevices": false, "devicefiles": [ "/dev/sda1" ], "comment": "Samsung EVO SSD 2 TB", "_readonly": false, "_used": true, "propreadonly": false, "usagewarnthreshold": 90, "mountopts": "defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl", "status": 1 }, { "devicename": "sdc1", "devicefile": "/dev/disk/by-uuid/cd15dd88-5d5b-4390-8553-91abadbeb1cb", "predictabledevicefile": "/dev/disk/by-uuid/cd15dd88-5d5b-4390-8553-91abadbeb1cb", "canonicaldevicefile": "/dev/sdc1", "parentdevicefile": "/dev/sdc", "devlinks": [ "/dev/disk/by-id/ata-WDC_WD50NPZZ-00A9JT0_WD-WXW2E70F8AC4-part1", "/dev/disk/by-id/wwn-0x50014ee2138bd799-part1", "/dev/disk/by-label/wdsata5tb", "/dev/disk/by-partuuid/bd3a7db1-514e-4021-a0e1-004268992453", "/dev/disk/by-path/pci-0000:00:17.0-ata-5-part1", "/dev/disk/by-path/pci-0000:00:17.0-ata-5.0-part1", "/dev/disk/by-uuid/cd15dd88-5d5b-4390-8553-91abadbeb1cb" ], "uuid": "cd15dd88-5d5b-4390-8553-91abadbeb1cb", "label": "wdsata5tb", "type": "ext4", "blocks": "4844126108", "mounted": true, "mountpoint": "/srv/dev-disk-by-uuid-cd15dd88-5d5b-4390-8553-91abadbeb1cb", "used": "1.95 TiB", "available": "2807764889600", "size": "4960385134592", "percentage": 44, "description": "/dev/sdc1 [EXT4, 1.95 TiB (44%) used, 2.55 TiB available]", "propposixacl": true, "propquota": true, "propresize": true, "propfstab": true, "propcompress": false, "propautodefrag": false, "hasmultipledevices": false, "devicefiles": [ "/dev/sdc1" ], "comment": "WD SATA 5TB", "_readonly": false, "_used": true, "propreadonly": false, "usagewarnthreshold": 95, "mountopts": "defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl", "status": 1 }, { "devicename": "nvme0n1p1", "devicefile": "/dev/disk/by-uuid/4fee3c4a-d782-47f1-8972-ef8ba821ac52", "predictabledevicefile": "/dev/disk/by-uuid/4fee3c4a-d782-47f1-8972-ef8ba821ac52", "canonicaldevicefile": "/dev/nvme0n1p1", "parentdevicefile": "/dev/nvme0n1", "devlinks": [ "/dev/disk/by-id/nvme-KINGSTON_SNVS250G_50026B7685BA13D1-part1", "/dev/disk/by-id/nvme-eui.00000000000000000026b7685ba13d15-part1", "/dev/disk/by-label/kingstonnvme", "/dev/disk/by-partuuid/ff8b7345-01", "/dev/disk/by-path/pci-0000:01:00.0-nvme-1-part1", "/dev/disk/by-uuid/4fee3c4a-d782-47f1-8972-ef8ba821ac52" ], "uuid": "4fee3c4a-d782-47f1-8972-ef8ba821ac52", "label": "kingstonnvme", "type": "ext4", "blocks": "239254136", "mounted": true, "mountpoint": "/", "used": "45.84 GiB", "available": "183253295104", "size": "244996235264", "percentage": 22, "description": "/dev/nvme0n1p1 [EXT4, 45.84 GiB (22%) used, 170.66 GiB available]", "propposixacl": true, "propquota": true, "propresize": true, "propfstab": true, "propcompress": false, "propautodefrag": false, "hasmultipledevices": false, "devicefiles": [ "/dev/nvme0n1p1" ], "comment": "", "_readonly": true, "_used": true, "propreadonly": false, "usagewarnthreshold": 0, "mountopts": "errors=remount-ro", "status": 1 } ] }
-
Here is the output:
[
{
"comment": "Seagate Festplatte 4TB",
"dir": "/srv/dev-disk-by-uuid-94537b05-9875-4501-9a8c-3aa6cbda18db",
"freq": 0,
"fsname": "/dev/disk/by-uuid/94537b05-9875-4501-9a8c-3aa6cbda18db",
"hidden": false,
"opts": "defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl",
"passno": 2,
"type": "ext4",
"usagewarnthreshold": 95,
"uuid": "86d9bed5-fbb2-49ad-a7ce-4e773428f874"
},
{
"comment": "Samsung EVO SSD 2 TB",
"dir": "/srv/dev-disk-by-uuid-35b74cc0-e206-49a2-ab0a-eb64c2e2d317",
"freq": 0,
"fsname": "/dev/disk/by-uuid/35b74cc0-e206-49a2-ab0a-eb64c2e2d317",
"hidden": false,
"opts": "defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl",
"passno": 2,
"type": "ext4",
"usagewarnthreshold": 90,
"uuid": "ec518a26-7a45-4577-9fb4-42d352b089eb"
},
{
"comment": "WD SATA 5TB",
"dir": "/srv/dev-disk-by-uuid-cd15dd88-5d5b-4390-8553-91abadbeb1cb",
"freq": 0,
"fsname": "/dev/disk/by-uuid/cd15dd88-5d5b-4390-8553-91abadbeb1cb",
"hidden": false,
"opts": "defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl",
"passno": 2,
"type": "ext4",
"usagewarnthreshold": 95,
"uuid": "6286d700-1285-47c5-9694-cfc18069c416"
},
{
"comment": "",
"dir": "/export/Filme",
"freq": 0,
"fsname": "/srv/dev-disk-by-uuid-cd15dd88-5d5b-4390-8553-91abadbeb1cb/Filme/",
"hidden": false,
"opts": "bind,nofail",
"passno": 0,
"type": "none",
"usagewarnthreshold": 0,
"uuid": "af6c19b3-a056-4ae9-a52b-5f8587a17758"
},
{
"comment": "",
"dir": "/",
"freq": 0,
"fsname": "/dev/disk/by-uuid/4fee3c4a-d782-47f1-8972-ef8ba821ac52",
"hidden": true,
"opts": "errors=remount-ro",
"passno": 1,
"type": "ext4",
"usagewarnthreshold": 0,
"uuid": "79684322-3eac-11ea-a974-63a080abab18"
}
]
-
The problem exists during the last three updates of omv. Before there where no problems. If I do "revert changes" this works, but what is done, because I commited no changes for now for the last three times as nothing is shown, why some sort of remount is done.
-
I have the same problem on my installation and it is not nice that during pending commits there are tries to unmount "/". Why? Only Power Cycle is possible after this, because "/" is unmounted and nothing is possible to do after this, because everything is "gone".
omv-rpc -u admin "Config" "applyChanges" "{\"modules\": $(cat /var/lib/openmediavault/dirtymodules.json), \"force\": true}"
{"response":null,"error":{"code":0,"message":"Removing the directory '\/' has been aborted, the resource
is busy.","trace":"OMV\\Exception: Removing the directory '\/' has been aborted, the resource is busy. in \/usr\/share\/openmediavault\/engined\/module\/fstab.inc:65\nStack trace:\n#0 [internal function]: Engined\\Module\\FSTab->deleteEntry(Array)\n#1 \/usr\/share\/php\/openmediavault\/engine\/module\/moduleabstract.inc(157): call_user_func_array(Array, Array)\n#2 \/usr\/share\/openmediavault\/engined\/module\/fstab.inc(31): OMV\\Engine\\Module\\ModuleAbstract->execTasks('delete')\n#3 \/usr\/share\/openmediavault\/engined\/rpc\/config.inc(167): Engined\\Module\\FSTab->preDeploy()\n#4 [internal function]: Engined\\Rpc\\Config->applyChanges(Array, Array)\n#5 \/usr\/share\/php\/openmediavault\/rpc\/serviceabstract.inc(123): call_user_func_array(Array, Array)\n#6 \/usr\/share\/php\/openmediavault\/rpc\/rpc.inc(86): OMV\\Rpc\\ServiceAbstract->callMethod('applyChanges', Array, Array)\n#7 \/usr\/sbin\/omv-engined(537): OMV\\Rpc\\Rpc::call('Config', 'applyChanges', Array, Array, 1)\n#8 {main}"}}
-
Yes I saw that you uploaded new plugin version with the fix. Tested it and it worked on my installation / vm konfig.
-
Ok thankx, actually I can't remove any USB Device from running VM via KVM GUI Plugin. Tried with all three devices. Error stays the same. Manually editing XML Files still the only solution.
-
That is the error message I wrote already above
Code
Display Moreroot@fj-db-omv6:~# sudo tail /var/log/omv-virsh-command.log [2022-08-02 11:26:11] Failed to remove USB device. error: Failed to detach device from /tmp/virsh_usbPPD6E8 error: XML Fehler: Invalid value for attribute 'id' in element 'vendor': '0x'. Expected integer value virsh detach-device --domain Server-HP --file '/tmp/virsh_usbPPD6E8' --persistent --config [2022-08-02 14:49:51] export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; virsh attach-device --domain Server-HP --file '/tmp/virsh_usbUp0LI6' --persistent --config --live 2>&1 [2022-08-02 15:21:57] export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export LANGUAGE=; virsh detach-device --domain Server-HP --file '/tmp/virsh_usb6TsZpF' --persistent --config --live 2>&1 [2022-08-02 15:21:57] Failed to remove USB device. error: Failed to detach device from /tmp/virsh_usb6TsZpF error: XML Fehler: Invalid value for attribute 'id' in element 'vendor': '0x'. Expected integer value virsh detach-device --domain Server-HP --file '/tmp/virsh_usb6TsZpF' --persistent --config --live
-
Here is a screenshot.
-
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 011: ID 041e:3125 Creative Technology, Ltd Creative Bluetooth Audio W2
Bus 001 Device 004: ID 0922:0020 Dymo-CoStar Corp. LabelWriter 450
Bus 001 Device 003: ID 051d:0002 American Power Conversion Uninterruptible Power Supply
Bus 001 Device 021: ID 05e3:0732 Genesys Logic, Inc. All-in-One Cardreader
Bus 001 Device 020: ID 05ac:12a8 Apple, Inc. iPhone 5/5C/5S/6/SE
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
-
I will do some testing with a separate VM not my home production server
and give you more output from installation.
-
Attached you will find my XML File from the VM. Tested once again and online removal of usb device is not possible. Seems that the constucted xml file has some missing data for the complete pci string for the usb device:
Code<hostdev mode="subsystem" type="usb" managed="yes"><source><vendor id="0x"/><product id="0x"/></source></hostdev>
Failed to remove USB device.
error: Failed to detach device from /tmp/virsh_usb6TsZpF
error: XML Fehler: Invalid value for attribute 'id' in element 'vendor': '0x'. Expected integer value
virsh detach-device --domain Server-HP --file '/tmp/virsh_usb6TsZpF' --persistent --config --live
OMV\Exception: Failed to remove USB device.
error: Failed to detach device from /tmp/virsh_usb6TsZpF
error: XML Fehler: Invalid value for attribute 'id' in element 'vendor': '0x'. Expected integer value
virsh detach-device --domain Server-HP --file '/tmp/virsh_usb6TsZpF' --persistent --config --live in /usr/share/openmediavault/engined/rpc/kvm.inc:2543
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/kvm.inc(1798): OMVRpcServiceKvm->virshCommand(Array, 'Failed to remov...')
#1 [internal function]: OMVRpcServiceKvm->removeUsb(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('removeUsb', Array, Array)
#4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Kvm', 'removeUsb', Array, Array, 1)
#5 {main}
-
Yes. Did you add the usb device with the plugin? It is evidently parsing the usb device incorrectly. Can you post the VM's xml?
Yes actually all three devices are added via kvm plugin gui. As I needed the vm I manually removed from XML File the entry for this usb device and I could start my vm again.
I will test again and send you the VM xml and try to reproduce the issue.
-
Hmm I installed docker via extras plugin BUT NOT extra compose plugin. So everything fine, then installed "compose plugin" after this for testing and tried to deinstall and docker was also uninstalled.
Until now I used docker-compose only via shell, no gui plugin. So I am still wondering why docker gets deinstalled because of some depencies. And I did it via OM6 GUI -> Plugins -> and docker is "gone"
-
Hi there, if I deinstall the docker compose plugin from omv-extras the complete docker installation also gets deinstalled. This package depency should not be happen, because my docker installation is still running and used.
So I had to reinstall docker also via omv-extras and docker was running again as a workaround.
May be it is possible to check this and only deinstall the om6 compose plugin and let the docker compose package installed on disk
-
In this context I have a question to a small change for the plugin on linking console links. At home the console links do not work because of problems using avm fritzbox and dns resolution for the build in fritzbox dns server and dhcp etc.
It would be useful if the console links could use by switch IP Adress of omv server instead of dns short name.
-
I am using a windows vm and attached actually three usb devices to vm. When I try di remove one usb device from vm an error message is thrown from virsh on command line.
Failed to remove USB device.
error: Failed to detach device from /tmp/virsh_usbn4uXED
error: XML Fehler: Invalid value for attribute 'id' in element 'vendor': '0x'. Expected integer value
virsh detach-device --domain Server-HP --file '/tmp/virsh_usbn4uXED' --persistent --config
OMV\Exception: Failed to remove USB device.
error: Failed to detach device from /tmp/virsh_usbn4uXED
error: XML Fehler: Invalid value for attribute 'id' in element 'vendor': '0x'. Expected integer value
virsh detach-device --domain Server-HP --file '/tmp/virsh_usbn4uXED' --persistent --config in /usr/share/openmediavault/engined/rpc/kvm.inc:2543
Stack trace:
#0 /usr/share/openmediavault/engined/rpc/kvm.inc(1798): OMVRpcServiceKvm->virshCommand(Array, 'Failed to remov...')
#1 [internal function]: OMVRpcServiceKvm->removeUsb(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('removeUsb', Array, Array)
#4 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Kvm', 'removeUsb', Array, Array, 1)
#5 {main}
Seems some problem on plugin creating command line skript.
Is it generally possible to remove usb device on running kvm vm? Actually I shutdown VM but removing is still not possible. May be manually removing from vm xml file will be successfull.
-
Hi there, I am in testing upgrade and updating debian packages / version from buster to bullseye and during apt procesess there is the following command triggered "python3 /usr/sbin/omv-mkaptidx"
Because it only runs on one cpu it is running very very long on my small iot odroid n2. Is there any way so that python uses more than one cpu? I found some hints during google search but don't now where to change it.