Solved with short HowTo in thread https://forum.openmediavault.o…ualBox-plugin/#post147187
Beiträge von raceface2nd
-
-
Hi,
for all others with the same problem following is a work around to get virtualbox running incl. phpvirtualbox
1. login via SSH as root
2. download the Linux headers3. reconfigure virtualbox
4. edit /usr/share/phpvirtualbox/endpoints/api.phpPHP//$response['data']['responseData']['phpvboxver'] = @constant('PHPVBOX_VER'); $response['data']['responseData']['phpvboxver'] = "5.1-0";
This worked for my OMV 3.0.8 with Kernel 4.9.0-0.bpo.3-amd64.Andy
-
Hi,
when I try to enable and apply the seetings for VirtualBox on a brand new OMV 3 installation on a Gigabyte brix I receive a bad gateway site error while applying the settings.
What can be the issue?
Thx!
Andy
-
Hi,
after new install of OMV 3.0 on my Gigabyte Brix BXBT-1900 I am unable to perform reboots. Reboot stucks with "watchdog: watchdog0: Watchdog did not stop!".
OMV2.0 did not have this issue. In this posting (OMV 3 stuck on reboot) a BIOS upgrade is suggested. Might there be another way without BIOS upgrade?
Andy
-
[edit] I decided to perform a new install with OMV 3.0 after backing up all config data and restored the most important
Hi,
I have running OMV 2 on a Gigabyte Brix since about 2 years with TVheadend installed. Now I wanted to perform an update and was wondering that there have been hundreds of updateable packages in the list in the web frontend.
When performing an apt-get update via console it shows me, that the signatures of openmediavault are invalid, so I tried to add the signatures again with wget -O - http://packages.openmediavault.org/public/archive.key | apt-key add -
Due to some reason, that does not help, performing apt-get upate again gives me following output
Get:1 file:/var/cache/openmediavault/archives InRelease
Ign:1 file:/var/cache/openmediavault/archives InRelease
Get:2 file:/var/cache/openmediavault/archives Release
Ign:2 file:/var/cache/openmediavault/archives Release
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en_US
Ign:4 file:/var/cache/openmediavault/archives Translation-en_US
Get:5 file:/var/cache/openmediavault/archives Translation-en
Ign:5 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en_US
Ign:4 file:/var/cache/openmediavault/archives Translation-en_US
Get:5 file:/var/cache/openmediavault/archives Translation-en
Ign:5 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en_US
Ign:4 file:/var/cache/openmediavault/archives Translation-en_US
Get:5 file:/var/cache/openmediavault/archives Translation-en
Ign:5 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en_US
Ign:4 file:/var/cache/openmediavault/archives Translation-en_US
Get:5 file:/var/cache/openmediavault/archives Translation-en
Ign:5 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en_US
Ign:4 file:/var/cache/openmediavault/archives Translation-en_US
Get:5 file:/var/cache/openmediavault/archives Translation-en
Ign:5 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en_US
Ign:4 file:/var/cache/openmediavault/archives Translation-en_US
Get:5 file:/var/cache/openmediavault/archives Translation-en
Ign:5 file:/var/cache/openmediavault/archives Translation-en
Hit:7 http://ftp.debian.org/debian wheezy-backports InRelease
Hit:8 http://security.debian.org wheezy/updates InRelease
Hit:9 http://packages.omv-extras.org/debian stoneburner-backports InRelease
Get:6 http://packages.openmediavault.org/public stoneburner InRelease [12.0 kB]
Hit:10 http://ppa.launchpad.net/ethereum/ethereum/ubuntu vivid InRelease
Get:11 http://apt.tvheadend.org/stable wheezy InRelease [3,484 B]
Ign:12 http://ftp.de.debian.org/debian wheezy InRelease
Hit:13 http://linux-packages.resilio.com/resilio-sync/deb resilio-sync InRelease
Hit:14 http://ftp.de.debian.org/debian wheezy-updates InRelease
Hit:15 http://ftp.de.debian.org/debian wheezy Release
Ign:16 http://www.openprinting.org/download/printdriver/debian lsb3.2 InRelease
Hit:17 http://www.openprinting.org/download/printdriver/debian lsb3.2 Release
Err:6 http://packages.openmediavault.org/public stoneburner InRelease
The following signatures were invalid: 0F6BCC17C26BFADC27F221007E7A6C592EF35D13
Err:11 http://apt.tvheadend.org/stable wheezy InRelease
The following signatures were invalid: 885B5A9BB5F392394DBEA699B42317285E12C7CF
Err:19 http://www.openprinting.org/download/printdriver/debian lsb3.2 Release.gpg
The following signatures were invalid: F8897B6F00075648E248B7EC24CBF5474CFD1E2F
Creating index of upgradeable packages ...
Creating index of openmediavault plugins ...
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f2ecd6d5c80>
Traceback (most recent call last):
File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f2ecd6d5c80>
Traceback (most recent call last):
File "/usr/lib/python3.5/weakref.py", line 117, in remove
TypeError: 'NoneType' object is not callable
Reading package lists... Done
W: The repository 'file:/var/cache/openmediavault/archives Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://packages.openmediavault.org/public stoneburner InRelease: The following signatures were invalid: 0F6BCC17C26BFADC27F221007E7A6C592EF35D13
E: The repository 'http://packages.openmediavault.org/public stoneburner InRelease' is no longer signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://apt.tvheadend.org/stable wheezy InRelease: The following signatures were invalid: 885B5A9BB5F392394DBEA699B42317285E12C7CF
E: The repository 'http://apt.tvheadend.org/stable wheezy InRelease' is no longer signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://www.openprinting.org/download/printdriver/debian lsb3.2 Release: The following signatures were invalid: F8897B6F00075648E248B7EC24CBF5474CFD1E2FAlso something strange happened to the NFS service . . . computers that have been able to connect to NFS shares since 2 years suddenly get the message mount.nfs: requested NFS version or transport protocol is not supported. In the services overview of the web frontend NFS suddenly show a red dot under running. How do I find out, why this dot is red and not green?
How can I fix this?
I appreciate any help! Thx!Andy
-
The fritz box is just resolving as domain controller. DNS is working fine, internet access or access to local network devices is no problem.
I also tried boot delay of 60.Just want to bring every thing together:
Kernel 3.2
Boot delay of 5 is good for mounting, DHCP is working USB 3.0 is very slow.Backports 3.16
Boot delay of 10 is good for mounting but boot stucks on "setting up resolv"Realtek firmware is up to date.
So the main problem is solved, maybe I open a new thread for the network resolv problem.
Andy
-
-
I did not setup any DNS, isn't OMV getting DNS via DHCP?
-
So, I took out the PCI-E Wifi card but still had the same Problem with stucking "Setting up resolvconf" on booting into bpo 3.16. I tried both, fixed IP and DHCP.
-
Static IP didn't help. That's why I was thinking, that it might be a drivers problem with the WiFi card. But I had no time yet to take out the card.
-
-
I tried several times booting backports but it stucks every time at the same point. Yes, DHCP is activated. I also tried with fixed values, but it was still the same.
The Brix has also a PCI-E Wifi module included (Realtek 8723BE), but there seems to be no drivers, so I will try taking out the module tomorrow hoping that helps with 3.16.
Regarding the USB 3.0 thing I also tried some research, but it confuses me. LSUSB is showing the 3.0 port as bus 003 but the drive to be connected on bus 001. An internal wiring error is impossible as the port is onboard.
*lsusb*
CodeBus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:07e6 Intel Corp. Bus 001 Device 003: ID 4971:1014 SimpleTech Bus 001 Device 004: ID 13d3:3410 IMC Networks Bus 001 Device 005: ID 2659:1210 Sundtek Bus 001 Device 006: ID 0425:0101 Motorola Semiconductors HK, Ltd G-Tech Wireless Mouse & Keyboard
*usb-devices*
Code
Alles anzeigenT: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=480 MxCh= 0 D: Ver= 2.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 P: Vendor=4971 ProdID=1014 Rev=00.00 S: Manufacturer=HGST S: Product=Touro Mobile 3.0 S: SerialNumber=21001312090002301604 C: #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=8mA I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=5000 MxCh= 1 D: Ver= 3.00 Cls=09(hub ) Sub=00 Prot=03 MxPS= 9 #Cfgs= 1 P: Vendor=1d6b ProdID=0003 Rev=03.02 S: Manufacturer=Linux 3.2.0-4-amd64 xhci_hcd S: Product=xHCI Host Controller S: SerialNumber=0000:00:14.0 C: #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=0mA I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
-
Correct, when booting.
-
The backport is freezing on "Setting up resolvconf", independend of having the network cable plugged in or not.
-
The UUID are matching.
I played something around, erased the swap partition on the external drive, labelled all partitions, started with rootdelay at 60 and now it's working. So this part is solved.
The only thing I am wondering is the low throughput of the 3.0 port.
Andy
-
I tried another HDD on the same port and the rates are 30% faster than with the other one. Also mounting on Startup worked without any problems. But I can not switch the drives as the first on is 1TB with lot of data and the 2nd is just 500GB. Any ideas?
-
There is a swap partition on the external drive, is it possible that this causes the error?
Andy
-
I connected the HDD to a USB 2.0 port, now I wasn't force to press CTRL+D but the drives aren't mounted. I am forced to mount them manually via GUI.
The disk speed is nearly the same as at the 3.0 port, really strange.
Code/dev/sdb2: Timing O_DIRECT cached reads: 72 MB in 2.02 seconds = 35.67 MB/sec Timing O_DIRECT disk reads: 72 MB in 3.04 seconds = 23.72 MB/sec
Andy
-
Sorry for the late reply . . I am using OMV 1.1.
Below you find my fstab:
Code
Alles anzeigen# /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # <file system> <mount point> <type> <options> <dump> <pass> # / was on /dev/sda1 during installation UUID=bffa6b90-4752-4276-bcce-f524e316ce9e / ext4 errors=remount-ro 0 1 # swap was on /dev/sda5 during installation UUID=ec059936-3964-4cbc-9a18-c13d3721ac62 none swap sw 0 0 /dev/sdb1 /media/usb0 auto rw,user,noauto 0 0 tmpfs /tmp tmpfs defaults 0 0 # >>> [openmediavault] UUID=8b136015-ed68-4f8c-a589-dd480adf1f5b /media/8b136015-ed68-4f8c-a589-dd480adf1f5b ext4 defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqf$ UUID=18fab38e-34fc-4eb2-b144-f163a3c0e005 /media/18fab38e-34fc-4eb2-b144-f163a3c0e005 ext4 defaults,nofail,acl,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqf$ /media/8b136015-ed68-4f8c-a589-dd480adf1f5b/Multimedia /export/Multimedia none bind 0 0 /media/8b136015-ed68-4f8c-a589-dd480adf1f5b/Public /export/Public none bind 0 0 # <<< [openmediavault]
I also found out, that the speed of the external USB 3.0 drive is very very slow, do you have an idea, what can be the reason for that behaviour?
Code/dev/sdb2: Timing O_DIRECT cached reads: 56 MB in 2.03 seconds = 27.55 MB/sec Timing O_DIRECT disk reads: 82 MB in 3.05 seconds = 26.84 MB/sec
Best regards!
Andy
-
Hi,
like some others in the forum I have the Problem that an external USB 3.0 drive is not mounted properly upon boot. I already set a delay of 10 in grub but this had no effect on the problem,
My configuration is a Gigabyte BRIX w/ 8GB RAM and a 256GB transcend SSD and an external USB 3.0 HDD drive.
On boot I get the following Messages:
Code
Alles anzeigenfsck.ext4: Unable to resolve 'UUID=8b136015-ed68-4f8c-a589-dd480adf1f5b' fsck died with exit status 8 failed (code 8). File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. ... failed! A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. ... (warning). Give root password for maintenance (or type Control-D to continue): scsi 2:0:0:0: Direct-Access HGST 0000 PQ: 0 ANSI: 6 sd 2:0:0:0: Attached scsi generic sg1 type 0 sd 2:0:0:0: [sdb] 1953523708 512-byte logical blocks: (1.00 TB/931 GiB) sd 2:0:0:0: [sdb] Write Protect is off sd 2:0:0:0: [sdb] Mode Sense: 27 00 00 00 sd 2:0:0:0: [sdb] No Caching mode page found sd 2:0:0:0: [sdb] Assuming drive cache: write through sd 2:0:0:0: [sdb] No Caching mode page found sd 2:0:0:0: [sdb] Assuming drive cache: write through sdb: sdb1 sdb2 sdb3 sd 2:0:0:0: [sdb] No Caching mode page found sd 2:0:0:0: [sdb] Assuming drive cache: write through sd 2:0:0:0: [sdb] Attached SCSI disk
After these messages the boot stops, if I press CTRL + D the boot sequence resumes and all drives are mounted. How can I prevent pressing CTRL+D while booting?
Best regards!
Andy