Ok, so I guessed something failed during the install, so I thought try reinstall .
apt-get install --reinstall openmediavault
Done
Then
omv-initsystem
I can now login to 4.1.9 using the default admin user/pass.
Yay, now I can start to configure it.
Ok, so I guessed something failed during the install, so I thought try reinstall .
apt-get install --reinstall openmediavault
Done
Then
omv-initsystem
I can now login to 4.1.9 using the default admin user/pass.
Yay, now I can start to configure it.
As I'm useless with linux I couldn't get the 4 install to work.
Whilst browsing threads of people with similar issues I saw some rolled back to 3, aha, 3 works. So I did a clean install of OMV 3.0.9 then ran omv-release-upgrade which got me a fresh 4 install.
Then omv-update to patch ... done, well not quite.
I now can't login to the webgui
admin:openmediavault doesn't work
omv-firstaid
reset console admin password
Nope still can't login with reset password.
It doesn't load OMV, so I don't think the above will work.
After lots of the mdadm no arrays found, it fails at dev/sdb1 does not exist and then drops to busybox.
I'm guessing the fail is because it was installed as sdb, but the other drive has now been removed so it should be a different letter.
I'll look for how to rewrite the boot.
OK, so now I've got
"mdadm: no arrays found in config file or automatically"
I'll deal with that tomorrow.
Ok, so after posting this I thought I'd check my last post/issue from 3 years ago. That was a RW issue seemingly caused by a failing USB drive.
Luckily I bought 2 new drives, so I tried the spare, and the install went through fine, so my new Sandisk USB drive looks like it's not good ... Anyway, all fixed using a different USB drive.
Hi all, I've been using OMV for a few years and decided to upgrade my old OMV "2.xx" to 4.
However install repeatedly fails installing grub ...
I have 2x USB, both new and were blank until a couple of hours ago. One is imaged with the source iso, openmediavault_4.1.3-amd64.iso, and the other is to be used as the system drive. All other drives are disconnected.
The installation assigns sdb for the destination drive, and I see it attempt "grub-install /dev/sdb"
That's where it fails
When I try it manually from shell I get:
"grub-install: error: cannot delete '/boot/grub/i386-pc/serial.mod' : Read-only file system"
Help please, I know virtually zero about this sort of thing.
Shares are now all back in place and kodi doesn't even notice the difference, so the library is fine.
Many thanks for the assistance subzero79, you've potentially saved me a lot of grief.
flash memory plugin also installed for usb sticks
Yes ... I'll enable it before I finish tonight.
Yay! it worked, thanks very much for your help subzero79
Bedtime me thinks ... I'll setup the shares and permissions again tomorrow, then when it's all done I'll clone the USB for emergencies
Updated and installed omv extras as soon as it was installed.
ZitatAlles anzeigenroot@OMV01:~# omv-showkey mntent
<mntent>
<uuid>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx</uuid>
<fsname>xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx|xxxx-xxxx|/dev/xxx</fsname>
<dir>/xxx/yyy/zzz</dir>
<type>none|ext2|ext3|ext4|xfs|jfs|iso9660|udf|...</type>
<opts></opts>
<freq>0</freq>
<passno>0|1|2</passno>
<hidden>0|1</hidden>
</mntent>
<mntent>
<uuid>07da1bd4-2c9d-4749-b856-7bed28020918</uuid>
<fsname>26292265-56da-4597-a0c8-dd3b50a03781</fsname>
<dir>/media/26292265-56da-4597-a0c8-dd3b50a03781</dir>
<type>ext4</type>
<opts>defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl</opts>
<freq>0</freq>
<passno>2</passno>
<hidden>0</hidden>
</mntent>
ZitatAlles anzeigen
root@OMV01:~# cat /etc/fstab
# /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=d60d864b-58d6-44b5-bb56-6d7323eb5bee / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=defb4703-12d9-4e9c-90e1-0476a55dfd01 none swap sw 0 0
/dev/sda1 /media/usb0 auto rw,user,noauto 0 0
/dev/sda2 /media/usb1 auto rw,user,noauto 0 0
/dev/sda5 /media/usb2 auto rw,user,noauto 0 0
/dev/sdb1 /media/usb3 auto rw,user,noauto 0 0
root@OMV01:~#
During install I had 2x usb devices, one as source for install files, the other as destination for the o/s. All physical hard disks were unplugged. The source with install files is now removed and 5 hdd for the array are installed and the array is showing as clean.
Did you copy files from the old usb stick and place them in the new install?
Nope, clean formatted USB, fresh download of OMV.
Ok, not going too well
It can see the array as said before, but when I try and mount it I get the error
ZitatAlles anzeigenFailed
to mount '26292265-56da-4597-a0c8-dd3b50a03781': mount: can't find
/media/26292265-56da-4597-a0c8-dd3b50a03781 in /etc/fstab or /etc/mtab
Error #6000:
exception 'OMVException' with message 'Failed to mount '26292265-56da-4597-a0c8-dd3b50a03781': mount: can't find /media/26292265-56da-4597-a0c8-dd3b50a03781 in /etc/fstab or /etc/mtab' in /usr/share/openmediavault/engined/rpc/filesystemmgmt.inc:921
Stack trace:
#0 [internal function]: OMVRpcServiceFileSystemMgmt->mount(Array, Array)
#1 /usr/share/php/openmediavault/rpcservice.inc(125): call_user_func_array(Array, Array)
#2 /usr/share/php/openmediavault/rpc.inc(79): OMVRpcServiceAbstract->callMethod('mount', Array, Array)
#3 /usr/sbin/omv-engined(500): OMVRpc::exec('FileSystemMgmt', 'mount', Array, Array, 1)
#4 {main}
Ok, it can see the array but getting error message when enabling services:
ZitatFile contains invalid JSON (filename=/var/lib/openmediavault/dirtymodules.json
Ok, drives unplugged and trying fresh install, thx for the advice and I'll let you know how I get on ... I've been meaning to clone the USB for a while just in case something happened to it, guess I left it too late.
Is there an easy way or guide to restoring settings for the array ... I have backups somewhere.
Yep, and I've just rebooted it again and .... it's dead Jim
root@OMV01:~# mount -o remount,rw /
mount: cannot remount block device /dev/sdf1 read-write, is write-protected
It's USB flash drive and the same after reboot.
I'm still trying ...
root@OMV01:~# sudo rm -f /var/lib/dpkg/lock
rm: cannot remove `/var/lib/dpkg/lock': Read-only file system
root@OMV01:~# ls -l /var/lib/dpkg/lock
-rw-r----- 1 root root 0 Sep 12 10:00 /var/lib/dpkg/lock
Hi all,
I'm a bit of a noob with linux, but have been running this on my NAS for quite a while without issue. Today I ran an update and it crashed during update and now I can't access the webgui - no login boxes.
I've rebooted the server (repeatedly)
Tried private mode
Different browsers
Different computers
ZitatAlles anzeigenroot@OMV01:~# df -h
Filesystem Size Used Avail Use% Mo unted on
rootfs 6.9G 2.1G 4.5G 32% /
udev 10M 0 10M 0% /d ev
tmpfs 798M 528K 797M 1% /r un
/dev/disk/by-uuid/66cfb283-dd48-4564-9e9c-2522e972f540 6.9G 2.1G 4.5G 32% /
tmpfs 5.0M 0 5.0M 0% /r un/lock
tmpfs 1.7G 0 1.7G 0% /r un/shm
tmpfs 3.9G 0 3.9G 0% /t mp
/dev/md0 11T 7.2T 3.7T 66% /m edia/26292265-56da-4597-a0c8-dd3b50a03781
/dev/md0 11T 7.2T 3.7T 66% /e xport/Dataset
/dev/md0 11T 7.2T 3.7T 66% /e
I think I'm ok for space
Zitatroot@OMV01:~# apt-get clean
W: Not using locking for read only lock file /var/cache/apt/archives/lock
read only files?
Zitatroot@OMV01:~# apt-get install links
W: Not using locking for read only lock file /var/lib/dpkg/lock
E: Unable to write to /var/cache/apt/
E: The package lists or status file could not be parsed or opened.
I'm guessing my issue is to do with certain parts being read only, however as a bit of an idiot on linux type stuff I am unsure what to do, so any help appreciated.
Chris