My OMV install hadn't updated for months due to the plex server changing, preventing all the other updates from working. I got around to removing the plex entry from the update list and proceeded to update packages. They failed left & right because of unmet dependencies (the first was gcc-4.9, but there were lots others). I manually went through and updated to the most recent of each one. Also involved command line apt to finish the installs as the web gui struggled with the conflicts. The system is running after a reboot and the services are all up, but the web files under /var/www/openmediavault/ are missing, resulting in "403 Forbidden nginx". There should be an index.php, but there's only a js directory. How can I fetch the web files that should be there? Or is there another step I should take to restore the web gui?
Web interface files missing after botched updates
-
- OMV 1.0
- chefp
-
-
I followed the instructions at http://wiki.openmediavault.org….php?title=Updates_to_OMV to update from the command line. It recommended to autoremove unused packages, which dug it deeper in a hole -- no webserver, smb or anything, though the system is able to boot. I tried installing openmediavault with apt-get but it has "unmet dependencies".
Zitat> apt-get install openmediavault
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:The following packages have unmet dependencies:
openmediavault : Depends: php5-pam but it is not going to be installed
Depends: proftpd-mod-vroot but it is not going to be installed
Depends: php5-proctitle but it is not going to be installed
E: Unable to correct problems, you have held broken packages. -
Can you post here
cat /etc/debian_version
-
The version returns as 8.1
-
-
Hi aaron. I believe I followed one of your helpful posts on how to fix the sources.list using the online generator tool. Here's what mine has:
Codedeb http://ftp.us.debian.org/debian stable main contrib non-free deb http://ftp.debian.org/debian/ wheezy-updates main contrib non-free deb http://security.debian.org/ wheezy/updates main contrib non-free
Should I change stable to wheezy? How do you recommend getting back to a working OMV install?
Edit: Made the change to wheezy but neither apt-get dist-upgrade nor apt-get -f install installs anything.
-
-
I changed stable to wheezy as per that post. apt-get still won't install openmediavault. How do I downgrade the system to wheezy and kick off the install?
-
How do I downgrade the system to wheezy and kick off the install?
There is no downgrade from jessie to wheezy unless you run a snapshot rootfs sort of backup system. Check if you upgraded with
cat /etc/debian_version -
The damage is already done.
-
There is no downgrade from jessie to wheezy unless you run a snapshot rootfs sort of backup system. Check if you upgraded with
cat /etc/debian_version
Fortunately I do have a snapshot backup (one of the plugins, I don't recall the exact name). Is it simply a matter of copying over everything from the backup location to the OMV installed drive? Would doing that on a live filesystem be problematic? -
If you used the system backup from openmediavault-backup, just boot systemrescuecd and rsync the files back. Don't do this live though.
-
I backed up the entire contents of the OMV installation to a directory on the HD, however I didn't create a systemrescuecd image. Is the image from their website appropriate to use?
-
OMG................. Sorry to see this chefp.
-
I installed SystemRescueCD on a USB, booted and rsync'd the backup files to the OMV boot drive. Upon reboot, grub complained that it couldn't find normal.mod. After some googling, I re-installed grub. Rebooting dumped me to the grub prompt. No errors, but it didn't have any settings to boot up. I entered these commands:
kernel /vmlinuz
initrd /initrd.img
bootIt starts the boot spew but hangs after detecting the drives. What's a good way to reinstall grub with the necessary settings to boot OMV?
OMG................. Sorry to see this chefp.
sh!t happens live & learn
This all started from the OMV upgrade code erroring out because one of the update sources (plex) went down. My system got out of date and the dependency version requirements no longer lined up. The updater really should allow other updates to occur even when a server is down.
-
I understand how it happened. You are not the only one. It sux.... We see from this that whoever is putting the release in those files should be specific and not generic like stable. Effing ridiculous.
-
I ended up re-installing OMV, then rsync'ing the backup files over it to restore my setup. The OMV installation failed at the end during the grub step. Had to use a combination of steps from these pages:
https://dcandy.wordpress.com/2…ls-to-install-bootloader/
http://wiki.openmediavault.org/index.php?title=InstallationFor anyone else that ends up in this situation, the steps I used were:
Code
Alles anzeigenmkdir /mnt/omv #Sub your boot partition for sdb1 mount /dev/sdb1 /mnt/omv mount -t proc none /mnt/omv/proc mount -o bind /dev /mnt/omv/dev mount -t sysfs sys /mnt/omv/sys chroot /mnt/omv/ /bin/bash #Sub your boot device for sdb grub-install /dev/sdb update-grub # Exit chroot. exit umount /mnt/omv/sys umount /mnt/omv/dev umount /mnt/omv/proc umount /mnt/omv # Reboot into SystemRescueCD and "rsync -a <backup> <OMV_boot_drive>"
That was done in another shell (Alt-F2) at the end of the OMV installation process, before rebooting. My OMV boot partition is /dev/sdb1. Substitute in your boot drive in the appropriate places.
Jetzt mitmachen!
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!