Thanks @subzero79
Can I use just Debian for the NAS OS and Install WebMin to administer it?
If yes, can I uninstall OMV from the existing setup without losing my data?
Thanks @subzero79
Can I use just Debian for the NAS OS and Install WebMin to administer it?
If yes, can I uninstall OMV from the existing setup without losing my data?
I would consider going back to the original firmware. Does the original fw provides ssh access? If yes then you should consider to script the actions from qnap ups software when power goes off, like ssh into buffalo and shutdown. To power it back on a wol packet can be sent.
I don’t know what qnap uses as ups software but reading through nut doc all of these seems possible. Does qnap uses nut?
Thanks @subzero79
The QNAP is indeed compatible with NUT, but the Buffalo is not. I am unable install NUT on the Buffalo because the debian version is outdated and unsupported.
The Buffalo Original Firmware Allows SSH Access, but I don't know anything about writing a script to shut down the Buffalo from the Qnap.
Can help me out there?
Sounds like they are trying to mount during boot but a service necessary to mount them has not started yet. Hard to say what it is though.
@ryecoaaron, thanks for that.
This has resulted in a very unreliable setup, what are my options to fix this?
The mountpoint is there. What does the following command output (should be nothing if it works): sudo mount -a
@ryecoaaron, no errors when I execute "sudo mount -a"
However, there no option to mount / unmount those partitions within the OMV GUI. The buttons are greyed out, but they are working at the moment.
What is the output of: ls -al /srv/
@ryecoaaron, here you go.
root@Link-Media:~# ls -al /srv/
total 20
drwxr-xr-x 5 root root 4096 Jan 25 16:35 .
drwxr-xr-x 25 root root 4096 Jan 20 18:35 ..
drwxr-xr-x 5 root root 4096 Nov 4 2016 dev-disk-by-id-ata-ST31000528AS_6VP1BTFK-part1
drwxr-xr-x 7 root root 4096 Nov 4 2016 dev-disk-by-label-data1
drwxr-xr-x 2 ftp nogroup 4096 Jan 20 18:01 ftp
@ryecoaaron, I posted a log entry which seems to be related. Can you please let me know if there is any other info required?
Nothing in Syslog.I think its best I try and reinstall from scratch Would I lose my data if I reinstall Debian or the Stock Firmware?
Edit:
I rebooted the device, and the mount point /data1 and the shares associated with it dropped off after the reboot.
This is what I found in Syslog
Mar 13 15:14:29 Link-Media monit[764]: 'mountpoint_srv_dev-disk-by-label-data1' status failed (1) -- /srv/dev-disk-by-label-data1 is not a mountpoint
Had to manually unmount in a SSH terminal and mount it again from within the OMV GUI. Now everything is back online.
Thanks for the response @ryecoaaron
I just remembered one more thing. The following mount points are from the same physical drive.
/dev/sda1 = /boot
/dev/sda2 = /root
/dev/sda4 = /data1
If the issue is due to hardware / drivers then it should affect the physical disk and all the partitions on it? I have this problem only with the mount point on /dev/sda4 and /dev/sdb1
Please refer to the screen shots for configuration details.
Not sure how or where you go the Debian image for this kirkwood unit but I would guess it needs some changes with the kernel (newer version maybe?).
I got the debian image from the link below, can I update it without breaking OMV? If yes, how?
These are two questions. If mount points are "dropping off", this isn't a function of OMV. This sounds like hardware issue (is the drive usb?). Mount/unmount in the GUI is based on whether the drive is in use and/or already mounted. I think the first problem needs to be fixed first.
The drive is not USB, it is installed in a Buffalo NAS Enclosure which never had such issues with stock firmware
That is the correct behavior with OMV 4.x. Each filesystem is mounted normally in /srv. Each shared folder is bind mounted to /sharedfolders/SHARED_FOLDER_NAME. So, you could see a lot of mounts to the same filesystem.
Any other ideas as to why those mount points keep dropping off and I cannot mount / unmount them using the GUI?
Hi all,
Its been a month since I asked for help, and Issue# 1 is still unresolved.
I want to avoid a roll back to the Factory default image, any assistance will be appreciated.
Hey guys,
Can someone please assist? Dropkick Murphy said the partitions are mounted twice and asked for output of cat /etc/fstab which I posted above. I would appreciate if someone could look at the logs and let me know whats wrong.
Anyone? Bump....
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/sda2 during installation
UUID=5d2bd2be-00f3-4f19-9830-ca4fe3d19b98 / ext3 errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=52111ecb-b63c-46dd-90b7-5ee1eb96d0e8 /boot ext3 defaults 0 2
# /data1 was on /dev/sda4 during installation
UUID=fe9e6fc6-57e8-414d-aeee-52c0537e3af8 /data1 ext4 defaults 0 2
# swap was on /dev/sda3 during installation
UUID=3f720336-6653-4811-a677-2015217401f5 none swap sw 0 0
# >>> [openmediavault]
/dev/disk/by-id/ata-ST31000528AS_6VP1BTFK-part1 /srv/dev-disk-by-id-ata-ST31000528AS_6VP1BTFK-part1 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
/dev/disk/by-label/data1 /srv/dev-disk-by-label-data1 ext4 defaults,nofail,user_xattr,noexec,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2
# <<< [openmediavault]
tmpfs /tmp tmpfs defaults 0 0
Alles anzeigen
# mount
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=120736k,nr_inodes=30184,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=25408k,mode=755)
/dev/sda2 on / type ext3 (rw,relatime,errors=remount-ro,data=ordered)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=40,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)
tmpfs on /tmp type tmpfs (rw,relatime)
/dev/sda1 on /boot type ext3 (rw,relatime,data=ordered)
/dev/sdb1 on /srv/dev-disk-by-id-ata-ST31000528AS_6VP1BTFK-part1 type ext4 (rw,noexec,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/sdb1 on /sharedfolders/Documents type ext4 (rw,noexec,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/sda4 on /srv/dev-disk-by-label-data1 type ext4 (rw,noexec,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group)
/dev/sda4 on /data1 type ext4 (rw,relatime,data=ordered,jqfmt=vfsv0,usrjquota=aquota.user,grpjquota=aquota.group)
tmpfs on /run/user/0 type tmpfs (rw,nosuid,nodev,relatime,size=25404k,mode=700)
# blkid
/dev/sdb1: UUID="5edac32f-c9a4-48f0-864d-6f319b0cfc18" TYPE="ext4" PARTUUID="0e73b492-4050-4c7a-b021-d96421e88890"
/dev/sda1: LABEL="boot" UUID="52111ecb-b63c-46dd-90b7-5ee1eb96d0e8" TYPE="ext3" PARTLABEL="boot" PARTUUID="73c4f189-7b3a-45c7-9ee8-38c29f74c865"
/dev/sda2: LABEL="root" UUID="5d2bd2be-00f3-4f19-9830-ca4fe3d19b98" TYPE="ext3" PARTLABEL="root" PARTUUID="9c0f9674-9b88-47a7-a68f-12c5e48ac5fc"
/dev/sda3: UUID="3f720336-6653-4811-a677-2015217401f5" TYPE="swap" PARTLABEL="swap" PARTUUID="05934134-ca23-4ff1-9851-27a0a56fe793"
/dev/sda4: LABEL="data1" UUID="fe9e6fc6-57e8-414d-aeee-52c0537e3af8" TYPE="ext4" PARTLABEL="data" PARTUUID="5ce8d592-adb8-4341-a6d3-18eaacec294e"
# cat /proc/partitions
major minor #blocks name
8 16 976762584 sdb
8 17 976761543 sdb1
8 0 976762584 sda
8 1 1047552 sda1
8 2 19922944 sda2
8 3 524288 sda3
8 4 955266048 sda4
31 0 384 mtdblock0
31 1 64 mtdblock1
31 2 64 mtdblock2
Thanks for responding, please let me know if there is any other information I can provide to troubleshoot the issue.
Could issue 1 be because it is an ext4 partition? Can someone please assist?
I resolved issue 3 by plugging in the UPS to the OMV NAS directly and configuring it to shutdown in 5 minutes. Once the config was applied using the NUT Plugin, I copied upssched.conf and then disabled the UPS in the plugin. Then I manually configured nut remote monitoring and copied over upssched.conf. The NAS shuts down 5 minutes after mains power is lost.
I checked the logs trying to figure out issue 1, and this is what I found
"monit[742]: 'mountpoint_srv_dev-disk-by-label-data1' status failed (1) -- /srv/dev-disk-by-label-data1 is not a mountpoint"
Not sure how to fix this and will appreciate some help from the gurus here.
Anyone?
Bump....
Hi all,
I recently installed OMV on my Buffalo LS-WVL since the original firmware was not compatible with QNAP's UPS monitoring software. The objective is to monitor the UPS by connecting connecting the USB cable to one of the NAS enclosures (preferably the QNAP) and have it signal the other two when there was a power failure.
My setup
I installed the current version of OMV on one of the buffalo NASes, and have been facing a few problems.
Issue 1: - Mount Point
The mount point Data1 on the boot disk keeps dropping off at least twice a week. I am unable to do anything using the Filesystems tab within the OMV gui, and am forced to SSH into the box and manually umount / mount the mount point whenever this happens. This unstable behaviour is my biggest concern and is seen only with that one mount point. I have attached JPEGs of the file system settings for reference.
Issue 2: Reboot / Shutdown
Issue 3: UPS monitoring - Resolved, see post below
The UPS is connected to the QNAP NAS via USB cable and the OMV NAS is configured to query the UPS status over the network. This part works and the OMV NAS is getting UPS status messages from the QNAP. However, I am unable to configure the OMV NAS to shutdown after a fixed interval. I need this to work since the UPS has a limited run time and I want to shutdown if the power outage lasts more than 5 minutes. The OMV UPS plugin seems to be meant only for directly connected UPS. Connecting the UPS to the OMV NAS is an option, but I still need the second Buffalo NAS(when migrated to OMV) to be able to shutdown once the remote UPS loses power for more than 5 minutes.
I would appreciate some help from the experts here on these issues.