I use Sata...it is the standard option, i think.
I have an omv 3 virtual machine (iso install, no upgrade) that works like a charm with Sata drive
I use Sata...it is the standard option, i think.
I have an omv 3 virtual machine (iso install, no upgrade) that works like a charm with Sata drive
don't know what to tell you, I did run into grub issue that OP is getting. it was a VirtualBox running on OMV 3.0 that in turn run on Hyper-V VM. yeah , a nice nested dolls effect.
and I could not install OMV 3.0 on that VM until I changed disk type to SCSI.
it would run through the setup and on reboot go into grub rescue mode.
when I used SCSI all went as expected and I had an
OMV 3.0 setup
==> running in VitualBox VM,
==> running in OMV 3.0 setup
==>running in Hyper-V VM
==>running on my windows 10 pro workstation.
how is that for nesting virtualization?
So when this doesn´t work in a virtual machine with sata drives....could it work with my real nas....i mean...it´s also sata...
or is this only an VM bug? no chance to repair grub? my linux experience is very limited
as far as I understand , it is a VM bug, it is not really related to OMV so much but the way VB presents the drives to the system. the SATA "driver" is broken some how and the bug comes up now and then.
as I said before, I had no problem setting up OMV 2 on the same VM that gave me issue with OMV 3. when using SATA driver.
but both versions had no problem installing on SCSI. Same nested VM setup as above.
something in the VB SATA driver and OMV 3.0 install drivers clash on occasion. since in my case it was just a test rig, I did not care. hence did not research to deeply.
Thank you.
Tried now with SCSI Controller....same issue....
We'll now I am lost , the only thing I am thinking now is to try a straight debian install to see if it works.
Sent from my SGH-T889 using Tapatalk
I guess I am going to have to install Virtualbox somewhere and test this. Never had this problem with multiple Debian and Ubuntu installs on virtualbox.
I guess I am going to have to install Virtualbox somewhere and test this. Never had this problem with multiple Debian and Ubuntu installs on virtualbox.
I only have it once. myself. and it was on OMV 3.0.20
I had not tried it with later versions as I do not need it at the moment.
as per my google research at the time, it is/was bug in VB on Debian 8 only.
other distros like Ubuntu , Mint, CentOS... did not have it.
I found the tip to use SCSI instead of SATA on one of the forum google dredged up,
there were a discussion and someone said that he had no issues with his install, but that he used SCSI hdd, it was said that it worked, so I tried it and sure enough no issue with install. once it worked I was fine form my testing.
the only similar issue I ever had was with Hyper-V VMs. most often than none if I use Gen2 VM for Linux I have problem either with install(will not install, or even boot from install ISO)
or with grub boot after install (just like the OP).
but that is on Hyper-V and only with Gen2 VM. something with Secure Boot implementation
Using sata on Virtualbox:
install OMV 2.1 from sourceforge iso
omv-update
apt-get clean
update-initramfs -u
update-grub
reboot
touch /etc/apt/apt.conf
omv-release-upgrade
# get normal dbus error
update-initramfs -u
update-grub
reboot
apt-get -f install
# get sed error that still needs to be fixed -purge OMV package to fix but not a good option for upgraders
dpkg -P openmediavault
apt-get install openmediavault
apt-get clean
apt-get autoremove
update-initramfs -u
update-grub
reboot
Alles anzeigen
no grub or booting issues. I think the update-initramfs and update-grub commands are important.
So, i followed your steps....and i again get grub rescue
Updating configuration ...
Failed to get D-Bus connection: Unknown error -1
Failed to get D-Bus connection: Unknown error -1
Failed to get D-Bus connection: Unknown error -1
Clearing symlinks in /etc/ssl/certs...done.
Updating certificates in /etc/ssl/certs... 174 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d....done.
Failed to get D-Bus connection: Unknown error -1
dpkg: error processing package openmediavault (--configure):
subprocess installed post-installation script returned error exit status 1
Processing triggers for libc-bin (2.19-18+deb8u6) ...
Processing triggers for systemd (215-17+deb8u5) ...
Processing triggers for resolvconf (1.76.1) ...
Processing triggers for ca-certificates (20141019+deb8u1) ...
Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d....done.
Processing triggers for initramfs-tools (0.120+deb8u2) ...
update-initramfs: Generating /boot/initrd.img-4.7.1
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mdadm: no arrays defined in configuration file.
Errors were encountered while processing:
openmediavault
Creating index of upgradeable packages ...
Creating index of openmediavault plugins ...
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@openmediavault:~# update-initramfs -u
update-initramfs: Generating /boot/initrd.img-4.7.1
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.
W: mdadm: no arrays defined in configuration file.
root@openmediavault:~# update-grub
Generating grub configuration file ...
Linux-Abbild gefunden: /boot/vmlinuz-4.7.1
initrd-Abbild gefunden: /boot/initrd.img-4.7.1
Linux-Abbild gefunden: /boot/vmlinuz-4.7.0-rc3-fts-amd64
initrd-Abbild gefunden: /boot/initrd.img-4.7.0-rc3-fts-amd64
Linux-Abbild gefunden: /boot/vmlinuz-3.16.0-4-amd64
initrd-Abbild gefunden: /boot/initrd.img-3.16.0-4-amd64
Linux-Abbild gefunden: /boot/vmlinuz-3.16.0-0.bpo.4-amd64
initrd-Abbild gefunden: /boot/initrd.img-3.16.0-0.bpo.4-amd64
Linux-Abbild gefunden: /boot/vmlinuz-3.2.0-4-amd64
initrd-Abbild gefunden: /boot/initrd.img-3.2.0-4-amd64
erledigt
root@openmediavault:~# reboot
Alles anzeigen
Latest OMV 2 with omv extras removed....
Probably has something to do with the custom kernel you are using...
Need to test this tomorrow....this kernel i´m also using on my real NAS....
Is it enough to choose the standard backport kernel in omv extras tab?
You might have to remove those custom kernels but I haven't tried. You won't need those kernels once you are on OMV 3.x since you can install the backports 4.7 kernel.
Can you tell me how to remove them right? Is this also required on my real Nas? Just to make sure im not getting into trouble
Gesendet von meinem LG-H815 mit Tapatalk
Can you tell me how to remove them right?
I assume you used dpkg -i to install them? Use dpkg -R to purge them.
Is this also required on my real Nas?
No idea. I don't know why you are using those kernels and I haven't tested this situation. So, I really can't answer it. Clone the OS drive and try it.
Thank you very much....will test vbox tomorrow and if all goes well, upgrade my real nas in the next few days or so.
Gesendet von meinem LG-H815 mit Tapatalk
So, i´ve removed all 4.x kernels with dpkg -r and dpkg --purge
After that i got the same error as above and again the grub rescue screen.
So i´ve made a new virtual machine and installed omv 2 from scratch.....problem is i cant enable ssh....get an error something with dirty modules json....or so.
It´s annoying
EDIT: Fixed the dirtymodules error....and update works with your steps from above.
So, how to update my real system with keeping the current configuration?
how to update my real system with keeping the current configuration?
I would update the system. If you get the grub rescue screen again, boot the debian jessie netinst iso and boot into rescue mode. Then do a grub-install /dev/sdX (replace sdX with your OS drive), update-grub, then update-initramfs -u. I would imagine that should fix the grub issue.
That should be dev/sdg1? Am i right?
I have two partitions on my system drive....
Most likely. It is possible that it could be different when you boot the debian image. I would look at the output of fdisk -l to make sure. If you install grub on the wrong disk, it won't hurt the disk but it won't fix your problem either.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!